Difference between revisions of "EN/documentation/administration guide/restricting functionality"
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
<section begin=title /><noinclude>{{DISPLAYTITLE:</noinclude>Restricting Functionality in {{OOo}}<noinclude>}}</noinclude><section end=title /> | <section begin=title /><noinclude>{{DISPLAYTITLE:</noinclude>Restricting Functionality in {{OOo}}<noinclude>}}</noinclude><section end=title /> | ||
+ | {{BreadCrumbL10n}} | ||
{{Documentation/AdminGuideTOC/v2 | {{Documentation/AdminGuideTOC/v2 | ||
Line 5: | Line 6: | ||
|ShowPrevPage=block | |ShowPrevPage=block | ||
|ShowNextPage=block | |ShowNextPage=block | ||
− | |PrevPage= | + | |PrevPage=EN/documentation/administration_guide/customizing_the_ui |
|NextPage=EN/documentation/administration_guide/ldap_access | |NextPage=EN/documentation/administration_guide/ldap_access | ||
}} | }} | ||
Line 114: | Line 115: | ||
The configuration is applied when you restart {{OOo}} | The configuration is applied when you restart {{OOo}} | ||
− | {{InterWiki Languages AdminGuide|articletitle= | + | {{InterWiki Languages AdminGuide|articletitle=EN/documentation/administration_guide/restricting_functionality}} |
{{PDL1}} | {{PDL1}} |
Latest revision as of 16:06, 30 March 2012
- Custom OpenOffice.org Basic Macros and Libraries
- OpenOffice.org Extension Manager
- Adding Template Files to an OpenOffice.org Installation
- Adding AutoText Files to an OpenOffice.org Network Installation
- Deactivating the OpenOffice.org Registration Wizard
- Accessing Email Clients
- Customizing the User Interface
- Restricting Functionality in OpenOffice.org
- Accessing OpenOffice.org User Profiles on an LDAP Server
You can restrict the functionality of OpenOffice.org program modules for individual users, groups, or across a network. You can apply different restrictions to different users. You can also create a command configuration file in XML format to restrict the availability of menu commands in an OpenOffice.org program.
Creating a Command Configuration File
The creation of a command configuration file is a three-step process:
- Determine the command names of the features you want to restrict.
- Create an XML configuration file.
- Copy the configuration file to the appropriate location in the OpenOffice.org installation directory.
To Create a Command Configuration File
- Determine the UNO Command Names for the feature that you want to restrict.
- In a text editor, create an XML configuration file.
- Use the following file structure.
- Create a separate node for each feature you want to restrict.
- In each node, replace the term CommandName with the command name of the feature.
- Save the file with the name Commands.xcu.
<?xml version="1.0" encoding="UTF-8" ?>
<oor:node oor:name="Commands" oor:package="org.openoffice.Office"
xmlns:oor="http://openoffice.org/2001/registry"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<node oor:name="Execute">
<node oor:name="Disabled">
<node oor:name="CommandName" oor:op="replace">
<prop oor:name="Command">
<value>CommandName</value>
</prop>
</node>
</node>
</node>
</oor:node>
The Commands.xcu file uses the following schema:
<?xml version='1.0' encoding='UTF-8'?>
<oor:component-schema oor:name="Commands"
oor:package="org.openoffice.Office" xml:lang="en-US"
xmlns:oor="http://openoffice.org/2001/registry"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<templates>
<group oor:name="CommandType">
<prop oor:name="Command" oor:type="xs:string"/>
</group>
</templates>
<component>
<group oor:name="Execute">
<set oor:name="Disabled" oor:node-type="CommandType"/>
</group>
</component>
</oor:component-schema>
The following example Commands.xcu file disables the ability to customize menus in OpenOffice.org.
<?xml version="1.0" encoding="UTF-8" ?>
<oor:node oor:name="Commands"
oor:package="org.openoffice.Office"
xmlns:oor="http://openoffice.org/2001/registry"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<node oor:name="Execute">
<node oor:name="Disabled">
<node oor:name="ConfigureDialog" oor:op="replace">
<prop oor:name="Command">
<value>ConfigureDialog</value>
</prop>
</node>
<node oor:name="ConfigureToolboxVisible" oor:op="replace">;
<prop oor:name="Command">
<value>LoadToolBox</value>
</prop>
</node>
</node>
</node>
</oor:node>
To apply this restriction to all users, copy the file to the network-install-dir/share/registry/data/org/openoffice/Office directory.
For a list of command names and their descriptions, see Index of UNO Command Names for OpenOffice.org.
To Apply a Command Configuration File
You can apply a command configuration file to OpenOffice.org on the Solaris, Linux, and Windows platforms.
- Exit all OpenOffice.org applications.
On Windows, ensure that you exit the OpenOffice.org Quickstarter in the system tray. - Copy the Commands.xcu file to the appropriate directory.
- To apply the configuration to all users on the network, copy the Commands.xcu file to the following directory:
network-install-dir/share/registry/data/org/openoffice/Office - To apply the configuration to a specific user on the network, copy the Commands.xcu file to the following directory:
workstat-dir/user/registry/data/org/openoffice/Office
- To apply the configuration to all users on the network, copy the Commands.xcu file to the following directory:
The configuration is applied when you restart OpenOffice.org
Content on this page is licensed under the Public Documentation License (PDL). |