INSTALLING


Client feature deployment
There are several ways to deploy Notes® client features and plug-ins to users, including a customized add-on installer, a deployment widget and source widget catalog, and a customized Notes install kit. For all methods, the feature or plug-in to be deployed should be properly signed before deployment.

After you have created or obtained a new third-party or custom Eclipse-based feature and set of plug-ins, there are several ways to install it for your Notes users.


Limiting feature install and update and composite application update

You can determine which update sites a user can obtain features from using a variety of options including a server managed update site list, which can optionally be specified as the only site list from which the user can obtain updates.

For information, see the topics Limiting feature install and update and Specifying available update sites.

Creating features and plug-ins

Regardless of how you make third-party or custom features and plug-ins available for Notes installation or update, you must first create or obtain the feature, create an install manifest to describe what is to be installed and place the new features and plug-in JAR files correctly in an update site directory along with a site index. Tools such as the IBM Lotus Expeditor integrated development environment (IDE) help automate the Eclipse feature development process for you.

You should also specify feature and plug-in security settings for signing, and can specify additional information such as a list of valid sites from which to obtain install and update information, and some security settings, using a plugin_customization.ini file.

For information, see the topic Managing client plug-in deployment.

Signing features and plug-ins

Prior to making a new third-party or custom Eclipse-based feature available for Notes installation or update, you must correctly sign the feature. Once signed, you must also include signing information in the plugin_customization.ini file that accompanies the install manifest.

For information, see Signing custom or third-party features and plug-ins for install and update.

Related concepts
Client feature deployment
Customizing Notes using plugin_customization.ini
Managing client plug-in deployment
Creating a new feature
Installing a new feature using the Notes install kit
Specifying available update sites
Limiting feature install and update with update sites
Configuring component update for composite applications
Creating and using a traditional third-party installer

Related tasks
Customizing Notes install for features and plug-ins on Windows and Mac
Deploying client plug-ins with widgets and the widget catalog
Adding new features to the Notes install kit using addToKit (Macintosh)
Signing custom or third-party features and plug-ins for install and update
Creating a customized add-on installer