If you have a properly signed new or third-party feature, and have added its "installfeature" information to the Notes install manifest (INSTALL.XML), you must also add the feature's update site information to the install kit prior to installing or upgrading Notes.

Using the addToKit tool, you can copy the signed contents of a customized, zipped update site (features subdirectory, plugins subdirectory and SITE.XML file) and install manifest file to the IBM® Lotus® Notes® install kit structure. The addToKit tool is available as a Microsoft® Windows® executable (apps\Utility\addToKit.exe).

Note If the addToKit tool is not available, you can manually add your feature to the Notes install kit using Notes install kit conventions. Be sure that the contents of the feature update site are signed before attempting to add it to the Notes install kit. All features must be signed to be installed.

After you update the content of your zipped update site directory, place it at the same level as the Notes install kit structure and use the addToKit tool to copy your source files into the install kit's structure.

Before using the addToKit tool, perform the following tasks:

• Create and sign any new Eclipse™ features that you want to add to the Notes install kit.
• Place the new features and plug-ins JAR files in the features and plugins update site subdirectories (updateSite.zip\features and updateSite.zip\plugins).
• Create and validate the new SITE.XML site manifest file (updateSite.zip\site.xml).
• Create and validate the new INSTALL.XML install manifest in the deploy directory (deploy\install.xml).

The following information is helpful when using the addToKit tool:

• There is no validation capability with the addToKit tool so be sure that your XML is validated and your "installfeature" ID attribute values are unique.
• You can run the addToKit tool with or without arguments.
• The <addTokitPath> must contain a deploy directory and zipped updateSite directory that matches the format of the Lotus Notes install kit.
• The updatesSite.zip\site.xml and deploy\install.xml information is merged from the <addTokitPath> to the <destKit> path and the plug-ins and features are copied over. The files in <addTokitPath> are added to the existing kit; they are appended to the destination SITE.XML and INSTALL.XML files.
• Running the tool with no arguments copies files to a temporary directory. If you do not specify a source path <.\addTokitPath> in the command line, the default source path is .\addToKit. If you do not specify a destination path <destKit>, the default destination path is the current working directory. The .\addToKit value should be the default source path.
• Before running this tool, place your signed features and plug-ins correctly in the update site directory and update the SITE.XML and INSTALL.XML files in their correct directories. Zip the update site directory.

Command line arguments are available. For example, when you run the following command, information from <kitPath> is merged into the kit that is in the same directory as the ADDTOKIT.EXE file.

addToKit.exe [-dhnV] <kitPath>

addToKit.exe c:\addToKit c:\temp\notes8abx.w32

<kitPath> defaults to addToKit/.

-d Turn debugging on.

-h Print command line option usage.

-n Run the utility as a dry run.

-V Print version information.

The procedure for using the ADDTOKIT tool is as below.

1. Extract ADDTOKIT.ZIP into the temporary directory in which your files reside, for example, c:\temp\notes8abx.w32. This zip file contains the directory addToKit, which contains your zipped update site directory (UPDATESITE.ZIP), and your deploy (deploy) directory.

2. Copy the ADDTOKIT.EXE into the same temporary directory.

3. Open a command window, change to the directory in which the addToKit tool resides, and run the tool, preferably with the source path and target path arguments, using the following format:

addToKit.exe <addTokitPath>

In this format, <addTokitPath> is the source path containing the source UPDATESITE.ZIP file and deploy directory and <destkit> is the target directory in which your Notes installation resides.

The source update site is an update site directory containing the features subdirectory, plugins subdirectory, and SITE.XML file. The deploy directory contains the updated INSTALL.XML file. The format of the source update site directory zip file and deploy directory must match the format of the target update site directory zip file and deploy directory.

Eclipse files and folders in the install kit
Customizing the Notes install kit to add or remove Eclipse features
Signing custom or third-party features and plug-ins for install and update
Understanding the Eclipse update site
Removing features from the Notes install kit using a supplied tool
Installing a new feature using the Notes install kit
Deploying client plug-ins with widgets and the widget catalog

Glossary