Most of the preference sets you use are automatically installed with the Lotus® Expeditor. If additional preference sets are required, you can install them using the Portlet's import capability.
When you import a preference set, a new policy type containing the default values is created.
Creating a new policy value set for your custom plug-ins or the plug-ins provided with the Lotus Expeditor allows you to centrally manage Eclipse preferences from the server. See Developing Applications for Lotus Expeditor
for instructions on creating new preference sets.
Your company has service centers in different regions of the country and you want to automate which service center the employees in your company should access based on where they live. You can create your own plug-in that uses an Eclipse preference to contain a value based on their location:
You can write an XML template containing this preference. You would install the template, along with a personalization rule based on the employee's location that is assigned as the policy type. The final step would be to create child policies based on the personalization rule. This would allow the service center to be automatically assigned.
Follow these steps to import a new preference set on the server. These steps assume that you have been provided an XML template in the Policy Type Editor for Preferences schema.
- Use a browser to access Administration -> Resource Policies -> Rich Client Templates.
- On the portlet drop-down menu in the Portlet header bar, click Configure to enter configuration mode.
- Click Browse to navigate through the local file system and select the XML template file.
- Select the file, and click Import. The XML template is validated and saved in the Portlet settings. The policy type is created.
You can now access the policy type using Administration
-> Resource Policies
- If your new policy type does not appear, you can either click on one of the policy types and click on the Policy Types link at the top of the page or log off the Portal server and log back on.
- To delete a user-defined template, you must use Policy Editor XMLAccess Scripts, which are described in "Sample Policy XML configuration files" in the WebSphere Portal information center. It is recommended that you remove the policy type if you uninstall a user-defined template. If you uninstall the Policy Type Editor, templates are deleted but the policy types are not deleted. You cannot edit the policy type unless you reload the template even after re-installing the Policy Type Editor. It is recommended that you save templates in another location.
Parent topic: Managing Rich Client Preferences using the Policy Type Editor for Eclipse Preferences: XPD621