Assigning Eclipse preference settings using a desktop policy

You can use a Desktop Settings document to add or remove Eclipse preferences used by Notes® or other Expeditor client application such as Symphony®.

About this task

Eclipse preferences are name value pairs in the format of pluginID/preferenceID=preferenceValue. Using this technique, you to push an Eclipse preference name value pair to the user's local Eclipse preference store.

The Domino® desktop policy settings document Custom Settings tab contains a Managed Settings option, which enables you to specify Eclipse preferences using the pluginID/preferenceID=preferenceValue format.

Note: Notes® uses the managed settings provider com.ibm.notes.managedsettings.provider to interact with Domino® policy using the dynamic configuration (DynConfig) construct; which checks policy when Notes® starts a session with its home mail server.
Note: The client message Notes Configuration Settings refreshed indicates that the DynConfig process has applied and updated user policies.

The user's local Eclipse preference store is updated when policy refresh occurs.

Do the following to push an Eclipse preference value pair to a Notes® user.

Procedure

  1. Using the Notes® or Administrator client, open the Domino® Directory (NAMES.NSF) on the Domino® server.
  2. Click the People & Groups tab, and open the Settings view.
  3. Click Add Settings, open the Desktop Settings tab, and click the Custom Settings tab.
  4. Click Managed Settings.
  5. Click Edit List to open a panel that enables you to add the Eclipse pluginID/preferenceID=preferenceValue value pair(s).
  6. Click Item and enter the preferenceID used by the plug-in.
  7. Click Value, enter the value to assign to the preferenceID. The Value entry equates to the preferenceValue.
  8. Click Plug-in name and specify the plug-in to be deployed to the Notes® client using either a widget deployment method, Notes® install kit, or Eclipse add-on installer. The Plug-in name entry equates to the Eclipse pluginID.
  9. Enable the Enforce option to push the value pair to overwrite any other previously set value for the setting.
  10. Click Add/Modify Value.
    Note: To remove a known name/value pair, specify the applicable name pair in the Item and Value fields and click Remove.
    Note: The Add these managed settings to user's desktops section of the panel displays values in a different syntax (preferenceName=prefValue; pluginID), than the Eclipse standard (pluginID/preferenceID=preferenceValue).
  11. Click OK and then click Save & Close.

Alternative -- Configuring an Eclipse managed setting using Domino® Designer

About this task

While still a valid method for deployment, the following method is simplified by using the Custom Settings > Managed Settings options on the desktop policy settings document introduced in Domino® 8.5.

To use a policy document to assign an Eclipse managed setting value to Notes® users, use Domino® Designer to add new fields to the desktop policy settings document. For related information, see information on designing fields in the IBM® Domino® Designer 9.0.1 Social Edition Help .

The following example allows you to set an Eclipse managed setting that designates whether Single Sign On for instant messaging is enabled for Notes® client users. This is an actual setting that is already under policy control and can be viewed in Domino® Designer.

Procedure

  1. In Domino® Designer, create a new field and assign it the same name as the name of the setting whose value you want to set. For example, assign the name IM_Enable_SSO. For the field values of IM_Enable_SSO, use the keywords Enable and Disable whose values map to true and false respectively.
  2. Create a computed text field named $qual_Number, where Number is an integer. Enable the Allow multiple values option. For example, create a field named $qual_009. Verify that the field name is unique and does not exist anywhere else on the form. Use the following format:
    "PlugInName":"SettingName"

    where PlugInName is the name of the Eclipse plug-in that the setting pertains to and SettingName is the setting name. For example, in our example we would use 

    "com.ibm.collaboration.realtime.community.sametime":"IM_ENABLE_SSO"
    Note: To set multiple settings for the same plug-in, use the following format:
     "PluginName":"SettingName1":"SettingName2":"SettingName3"