Lotus Domino Administrator 8.5 Help - Customizing Notes install for Linux RPM or DEB

NOTES CLIENT INSTALLATION AND UPGRADE

Customizing Notes install for Linux RPM or DEB
Use this procedure to add custom features to an install or remove features from an install.

In this example, the install manifest is /etc/ibm/<Platform RPM/DEB name>/install.xml and the platform RPM/DEB name is ibm_lotus_notes. This example assumes you are using the Notes 8.5 ibm_lotus_notes-8.5.i586.rpm or ibm_lotus_notes-8.5.i586.deb package and the default install directory /opt/ibm/lotus/notes.

For related information, and for rpm and deb package names for all Notes 8.5 stream releases, see "Installing and upgrading Notes on Linux."

1. Put a valid install.xml file in the existing /etc/ibm/ibm_lotus_notes/ directory.

The contents of install.xml in the install kit override the contents of /opt/ibm/lotus/notes/framework/rcp/deploy/install.xml.

The install.xml file must contain all features, including the Lotus-supplied features already in rpm or deb package plus any customized features you want to add to the installer. Use the install.xml provided with the Notes install kit for formatting.

For the RPM or DEB platform (ibm_lotus_notes-8.5.i586.rpm or ibm_lotus_notes-8.5.i586.deb) the Notes install manifest is located at /opt/ibm/lotus/notes/framework/rcp/deploy/install.xml or externally as an override to the default location at /etc/ibm/<Platform RPM/DEB name>/install.xml.

2. Put a valid updatesite folder in the /etc/ibm/ibm_lotus_notes/ directory.

The new updatesite folder should contain customized features and corresponding plugins. For the features already in RPM or DEB package, you do not need a new updatesite folder. All JAR files in the updatesite/plugins and updatesite/features folders must be signed.

3. Optionally customize the supplied plugin customization file.

You can customize the plugin_customization.ini file to set default preferences for plug-ins. This file is a java.io.Properties format file. The plugin_customization.ini file can be in the RPM/DEB as /opt/ibm/lotus/notes/framework/rcp/plugin_customization.ini or externally at /etc/ibm/<

Platform RPM/DEB name

>/plugin_customization.ini.

Note The supplied plugin_customization contains the following statements because the Notes installer requires that all features be signed by certain Notes trusted signatures.

com.ibm.rcp.security.update/UNSIGNED_PLUGIN_POLICY=PROMPT

com.ibm.rcp.security.update/UNTRUSTED_SIGNATURE_POLICY=PROMPT

4. Provide keystore files for signing.

Note

Features and plug-ins installed as part of the Notes install kit must be properly signed.

The security keystore files can be located in the RPM/DEB at /opt/ibm/lotus/notes/framework/rcp/deploy/.keystore* or externally at /etc/ibm/<Platform RPM/DEB name>/.keystore*. Keystore files can be updated using Platform RPM/DEB.

5. Put the customized plugin_customization.ini (if used) and /.keystore* files in the /etc/ibm/ibm_lotus_notes/ directory.

6. Run the customized RPM or DEB Notes installer.

run '# rpm -i ibm_lotus_notes-8.5.i586.rpm"

run '$ sudo dpkg -i ibm_lotus_notes-8.5.i586.deb"

Addon RPM or DEB

You can use the same process flow as documented above for Addon RPM/DEBs. The install manifest (install.xml file) can be located in the RPM or DEB kit as /opt/ibm/lotus/notes/framework/rcp/deploy/install.<addon name>.xml and /opt/ibm/lotus/notes/framework/rcp/deploy/uninstall.<addon name>.xml or be located externally as an override to the default location at /etc/ibm/<Addon RPM/DEB name>/install.<addon name>xml and /etc/ibm/<Addon RPM name>/uninstall.<addon name>xml.

For related information, and for rmp and deb package names for all Notes 8.5 stream releases, see "Installing and upgrading Notes on Linux."

For Notes Addons (ibm_lotus_activities-8.5.i586.rpm or ibm_lotus_activites-8.5.i586.deb, for example, {name}=ibm_lotus_activities)

1. Put a valid install.{name}.xml file and uninstall.{name}.xml file in the '/etc/ibm/{name}/' directory on the computer on which you'll be installing.

The new files will override the existing, installed files in the /opt/ibm/lotus/notes/framework/rcp/deploy directory.

The install.{name}.xml and uninstall.{name}.xml files should contain {name} features. The features include those already in a supplied rpm or deb package plus any third party or custom features you want to install or uninstall now.

Note For an example of an install.{name}.xml file, see the /opt/ibm/lotus/notes/framework/rcp/deploy/install{name}.xml file.

Note For an example of an uninstall.{name}.xml file see /opt/ibm/lotus/notes/framework/rcp/deploy/uninstall{name}.xml file.

2. Put a valid updatesite folder under '/etc/ibm/{name}' directory.

The new updatesite will contain your third party or custom features and corresponding plugins.

Note You do not need a new updatesite folder for features already in a supplied RPM or DEB package.

As part of this step, you'll need to do the following:

Create a custom plugin_customization.ini file.

The optional plugin_customization.ini file is used to set default values for preferences defined by plug-ins. This file is a java.io.Properties format file. Typically this file is used to set the values for preferences that are published as part of a plugin's public API.

The plugin customization file can be located within the RPM/DEB as /opt/ibm/lotus/notes/framework/rcp/plugin_customization.ini or be located externally as an override to the default location at /etc/ibm/<Addon Platform RPM/DEB name>/plugin_customization.ini.

Provide keystore files.

Security keystores for the platform can be provided using one or more of these optional files. Keystore files can be updated using Addon Platform RPM/DEB.

The keystore files can be located within the RPM/DEB at /opt/ibm/lotus/notes/framework/rcp/deploy/.keystore* or be located externally as an override to the default location at /etc/ibm/<Addon Platform RPM/DEB name>/.keystore*.

3. Put your plugin_customization.ini /'.keystore*' under /etc/ibm/{name}, if you want to override the one in the rpm or deb package.

The plugin_customization.ini file in the install kit will be merged with the plugin_customization.ini file currently in the /opt/ibm/lotus/notes/framework/rcp/deploy/ directory on the computer on which you'll be installing.

Note Your custom or third party features must be signed with a Notes trusted signature or you must manually remove the following two lines from the plugin_customization.ini file in your custom kit before install and then add these two lines back to the deployed plugin_customization.ini file after installation is complete.

com.ibm.rcp.security.update/UNSIGNED_PLUGIN_POLICY=PROMPT

com.ibm.rcp.security.update/UNTRUSTED_SIGNATURE_POLICY=PROMPT

4. Install the rpm or deb using the following sample as reference.

run '# rpm -i ibm_lotus_activities-8.5.i586.rpm'

run '$ sudo dpkg -i ibm_lotus_activities-8.5.i586.deb'

Note Using an external location override allows the deployer to define the set of features to be installed or enabled during installation.

Related topics

Customizing the Notes install kit

Understanding the Eclipse update site

Eclipse files and folders in the install kit

Reducing the Notes install kit size

Considerations for installing and deploying Notes on Linux