Difference between revisions of "Documentation/Administration Guide/Restricting functionality"
From Apache OpenOffice Wiki
(→Creating a Command Configuration File) |
|||
Line 1: | Line 1: | ||
<!-- {{DISPLAYTITLE: Restricting Functionality in {{OOo}}}} --> | <!-- {{DISPLAYTITLE: Restricting Functionality in {{OOo}}}} --> | ||
− | {{Documentation/AdminGuideTOC/v2}} | + | {{Documentation/AdminGuideTOC/v2 |
+ | |ShowPrevNext=block | ||
+ | |ShowPrevPage=block | ||
+ | |ShowNextPage=block | ||
+ | |PrevPage=Documentation/Administration Guide/Customizing the UI | ||
+ | |NextPage=Documentation/Administration Guide/LDAP Access | ||
+ | }} | ||
{{Documentation/Abstract|You can restrict the functionality of {{OOo}} program modules for individual users, groups, or across a network. If you want, you can also 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 a {{OOo}} program.}} | {{Documentation/Abstract|You can restrict the functionality of {{OOo}} program modules for individual users, groups, or across a network. If you want, you can also 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 a {{OOo}} program.}} | ||
Revision as of 11:10, 14 September 2007
- Apache OpenOffice Basic Macros and Libraries
- Apache OpenOffice Extension Manager
- Adding Template Files to an Apache OpenOffice Installation
- Adding AutoText Files to an Apache OpenOffice Network Installation
- Deactivating the Apache OpenOffice Registration Wizard
- Accessing Email Clients
- Customizing the User Interface
- Restricting Functionality in Apache OpenOffice
- Accessing Apache OpenOffice User Profiles on an LDAP Server
Creating a Command Configuration File
The creation of a command configuration file is a three-step process:
- Determine the command names of the features that you want to restrict
- Create an XML configuration file
- Copy the configuration file to the appropriate location in the Apache OpenOffice installation directory
To Create a Command Configuration File
- Determine the UNO Command Names for the feature(s) that you want to restrict.
- In a text editor, create an XML configuration file.
- Ensure that the file has the following structure
- Create a separate node for each feature that you want to restrict.
- In each node, replace the term CommandName with the command name of the feature.
- Save the file as 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 Commands.xcu file disables the ability to customize menus in Apache OpenOffice. To apply this restriction to all users, copy the file to the <SO network dir>/share/registry/data/org/openoffice/Office directory.
<?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></programlisting>
For a list as well as a description of command names, see [Index of UNO Command Names for Apache OpenOffice]. .
To Apply a Command Configuration File
You can apply a command configuration file to Apache OpenOffice on Solaris, Linux, and Windows.
- Exit all Apache OpenOffice applications.
On Windows, ensure that you exit the Apache OpenOffice 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:
<SO network 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:
<SO 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 Apache OpenOffice
Content on this page is licensed under the Public Documentation License (PDL). |