Limiting feature install and update with update sites

Provisioning settings are available on the Client Upgrade tab in the Domino® Administrator server Configuration Settings document. This capability is specific to the Eclipse Update Manager (EUM).

One way of installing and updating third-party features or Notes® sidebar plug-ins is the Eclipse update manager (EUM), which is a user-initiated tool. Alternatively, widgets can be used for automat install and update. For information about provisioning features and plug-ins to an existing Notes® installation, see Deploying client plug-ins with widgets and the widget catalog in the related links. While EUM requires the user to "pull" an install or update, the widgets deployment method enables an administrator to push an install or update without user intervention.

Custom features and plug-ins can be installed as part of Notes® install or using an add-on installer; these methods are described in this guide.

For related information, see Specifying available update sites.

Note: Features installed or upgraded using the Notes® installer are only available for upgrade using the Notes® installer.
  • An update site can be either a traditional Eclipse update site or a Notes® NSF-based update site, which is based on the supplied UPDATESITE.NTF template.
  • Feature update can occur if the feature version at the update site is higher than the installed feature version.
  • Using the Provisioning tab options on the server Configuration Settings document, you can create and allow use of a default list of update sites, allow update from the default update site embedded in the feature (FEATURE.XML) or composite application definition (CA XML), or limit feature update to a specific update site list, referred to as a whitelist.