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

Before using this tool, perform the following tasks:

• Create and sign any new Eclipse features that you want to add to the Lotus Notes install media kit.
• Place the new features and plug-ins JAR files in the features and plugins update site subdirectories (updateSite\features and updateSite\plugins).
• Create and validate the new SITE.XML site manifest file (updateSite\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 this 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 media kit.
• The updatesSite\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 into 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.

1. Extract the ADDTOKIT.ZIP file 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 Lotus 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.

Customizing the installer process
Customizing Notes installation using the install manifest
Customizing the Notes install manifest to add or modify access to Eclipse features

Glossary