NOTES CLIENT INSTALLATION AND UPGRADE
Note You can control feature update using a list of available update sites, called a default update site list. This list can optionally be treated as a whitelist (approved site list), to control exactly which update sites can be used for feature install and update.
Domino administrators can control feature update, using the server Configuration Settings document and the provisioning setting in the Domino Desktop policy settings document, to restrict the places a user can obtain new or updated features. Administrator control to remotely manage feature install and update site capabilities and settings, such that changes are reflected on the client, are as below:
Note If you use the File - Application - Install menu option, your selections are stored in a BOOKMARKS.XML file on your client system for possible use during feature install and update. The BOOKMARKS.XML file is not used for composite applications, only feature install and update. You may also find update site settings in the PLUGIN_CUSTOMIZATION.INI file on your client system, which can be edited manually either before or after Notes install. Settings on the server Configuration Settings document override update site settings in both of these files.
-- You can also update existing features from the default site specified in the feature's FEATURE.XML file, provided that the FEATURE.XML is physically resident on your client system.
Note The FEATURE.XML file is not used for initial feature install; only feature update.
Note Although Expeditor allows for automatic feature and component update, Notes does not. All feature and composite application update in Notes must be user-initiated. If referencing Expeditor documentation, make note of this difference in behavior.
Note If a composite application definition (CA XML) has been updated it can trigger a feature update if that CA XML requests a new feature version.
Server Configuration Settings document options
The server Configuration Settings document contains a Client Upgrade tab, on which you can use the Provisioning tab to add, remove, edit, and disable or enable update sites, as well as determine update site availability.
Provisioning settings are enabled
The "Provisioning settings are enabled" option is an overall Enable/Disable field, which is disabled by default.
Note that settings on the Configuration Settings document will override settings that may exist in the PLUGIN_CUSTOMIZATION.INI file or BOOKMARKS.XML file on the user's client system, or that may have been pushed to the client previously from this or another server Configuration Settings document.
If you enable this option with the all provisioning choices for the document disabled, then you can install from a composite application (CA XML) or the Update Manager user interface but you will be prevented from performing any feature updates. If you later disable the overall provisioning option, then you can install from a composite application (CA XML) or the Update Manager user interface and you can also do feature update from FEATURE.XML. This is the initial default configuration.
You can check the sites that you want to include in the install or update operations. All sites specified in the default site list are available for your selection.
New, Edit, and Delete
You can add new sites to the default site list, edit the server name or URL of a site already present in the site list, or delete a site from the default site list.
Allow client updates only from these sites and Use update site specified in feature
The two options at the bottom of the page work as described below. A definition of each is provided below, however the meaning of both options can change when they are used in combination with one another, as is described immediately following the definitions below.
Note If you are using the Eclipse update manager (EUM) and enable the whitelist setting, some options on the "Update sites to visit" page will be masked, such as New Remote Site, New Local Site, and New Archived Site.
Note All features contain an embedded update site URL in their .JAR file (FEATURE.XML). This value is typically the location from which the feature was initially installed and it acts as a default update site.
Note The "Allow client updates only from these sites" setting takes precedent over the "Use update site specified in Feature" setting. If "Allow client updates only from these sites" is enabled, the update site in the FEATURE.XML file must be resident in the default update site list to be used for update.