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.

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 will either be prevented or be subsequently 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. Lotus Notes® 8.0 includes a provider to retrieve policies from Domino® using the Notes® client. If there is no provider available for your back-end system, you may write your own. See Adding a managed settings provider for more information.

Note: Managed settings will not work when using Portal 6.0.1. Portal 6.0 or Portal 6.0.1.1 must be used.