NOTES CLIENT INSTALLATION AND UPGRADE

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 IBM® Lotus® 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 IBM® Lotus® Domino® desktop policy or a plugin_customization.ini file setting.

Note This 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.

Policy

Set the following policy to enable EUM.

1. Using the IBM® Lotus® Domino® Administrator client, open the Desktop policy settings document.

2. On the Basics tab, locate the Provisioning section at the bottom of the document.

3. In the Allow user to do user initiated updates field, click Enable to allow user-initiated updates or Disable to prevent user-initiated updates.

Preference

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

In a multi-user Notes install, after the user has used EUM she must open the Application Management panel in Notes and enable the feature, as below.

1. Click File - Application - Application Management.

2. For each feature to be enabled, select the feature, then click Enable.


3. Allow the client to restart when you are prompted.
For related information, see Expeditor client topics in the Lotus Expeditor Wiki or IBM Lotus Expeditor Information Center.

Specifying a default multi-user install directory with EUM

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.

For related information, see colocation-affinity value topics in the Lotus Expeditor Wiki or IBM Lotus Expeditor Information Center.

Related topics