Enabling user-initiated update with EUM

To allow users to install or update custom or third-party Eclipse features and plug-ins into an existing Notes® installation, you can enable display of the Eclipse update manager user interface. By default, the Eclipse update manager (EUM) is not displayed. You can enable the EUM using either Domino® Desktop policy or a plugin_customization.ini file setting.

About this task

The Eclipse update manager (EUM) method, which requires user-initiated install and update for deploying plug-ins to an existing client installation, has been superseded by the client management process available with widgets and the centrally managed widget catalog. That process is described in the topic Deploying and managing client plug-ins with widgets and the widget catalog.

It is not suggested that you use EUM to deploy and manage plug-ins. Instead, deploy plug-ins to clients using a centrally managed widget catalog method.

Using Domino® policy

About this task

You can set the following policy to enable EUM.


  1. Using the Domino® Administrator client, open the Desktop Policy Settings document.
  2. On the Basics tab, locate the Provisioning section.
  3. In the Allow user initiated updates field, click Enable.

Using an Eclipse preference

About this task

You can add the following line to the user's plugin_customization.ini file (install_dir\framework\rcp\plugin_customization.ini after install or deploy\plugin_customization.ini before install) to enable EUM.


Additional step to access and use the feature

About this task

In a multi-user Notes® install, users must open the Application Management panel in Notes® and enable the feature.


  1. Click File > Application > Application Management.
  2. For each feature to be enabled, select the feature, then click Enable.

    Enable multiple features one at a time.

    Despite being prompted to restart after every action, you can enable multiple features before restarting.

  3. Allow the client to restart when you are prompted.

    Once restarted, you can use the feature.

Specifying a default multi-user install directory with EUM

About this task

In a multi-user installation, installing a feature using EUM places that feature in the (install_dir)\framework\shared\eclipse directory. For example, if you log in as a non-administrative user, and install a feature using EUM, that feature is installed to (install_dir)\framework\shared\eclipse directory and available to all users in that multi-user installation.

Note: Using the EUM method you need administrator privileges to update features in the Notes\framework directory. However, you do not need administrator privileges if you are installing or updating features to the workspace\applications directory. Note that the applications directory is located in the user's workspace directory.

All features, when installed by a non-administrative user in a Notes® multi-user install, are installed to the install_dir\framework\shared\eclipse directory by default. You can override this default for a particular feature by having the feature's application developer specify a colocation-affinity attribute. To limit a user's ability to install a feature, the deployer can specify a colocation-affinity attribute with the ID "com.ibm.rcp.site.anchor.shared.feature". The resultant site for a deployer would still be the shared site, chosen because the colocation-affinity selects that site. A user attempting to install the feature would have the feature installation fail, since the site specified by the colocation-affinity is not accessible.