The managed settings framework allows you control over the runtime behavior of client applications by letting you set the values of the settings that the applications are reading out of the Eclipse preference store.
If you also designate these settings as read-only, any changes that the client applications make to the settings are prevented or are later overwritten with your values, depending on how the client accesses the settings. If the client program knows about managed settings and accesses them through the ManagedSettings Eclipse preference scope, any changes to read-only settings are prevented. For other plug-ins, which access the settings in the traditional way, changes can occur but are later overwritten with your values. Updates are run regularly to add any of your new settings or settings changes to the preference store on the client.
The managed settings framework can retrieve policy, preferences, or any other name and value pairs from any back-end system for which there exists a managed settings provider. Providers contain the knowledge of the specific back-end system. Lotus
® Expeditor includes providers to retrieve settings both from Portal Policy Manager and from an XML file residing on an HTTP server. If there is no provider available for your back-end system, you can write your own. See Adding a managed settings provider
for more information.
You can manage client settings by completing the following procedures:
Parent topic: Managing client configurations
- Specifying settings
- Configuring providers
- (Optional) Setting the managed settings update schedule
- Ensuring that the managed settings plug-in gets started
You can specify the desired values of client setting using the back-end administration system of your choice.
To plug in to the managed settings framework, the back-end management system that populates the Eclipse preference store with the settings for the application must have a corresponding managed settings provider.
Configuring the managed settings update schedule
The framework uses a scheduled background job to call each provider and tell it to retrieve updated settings from its associated back-end systems and then pass them to the framework to update the values stored on the client.
Ensuring that the managed settings plug-in gets started
For your settings to be applied to the client, the plug-in com.ibm.rcp.managedsettings
must be started at runtime.