NOTES CLIENT INSTALLATION AND UPGRADE
You must also properly add the feature to the install kit. Be sure that the new or third-party feature is signed before attempting to add it to the Notes install kit. All features must be properly signed in order to be installed. For information about signing, see "Signing custom or third-party features and plug-ins for install and update."
The Notes install manifest Document Type Definition (DTD) differs from the standard Eclipse or IBM® Lotus® Expeditor install or provisioning manifest DTD. For example, the Notes install manifest contains at least four unique attributes that the Expeditor manifest does not; namely "required," "default," "show," and "description."
Note The Notes install manifest uses a unique DTD that adheres to Eclipse conventions but is somewhat nonstandard. The Expeditor install manifest adheres to the DTD conventions described in "Provisioning manifest DTD" in IBM® Lotus® Expeditor help at the Lotus Expeditor information center or in the Lotus Expeditor wiki.
installfeature element
The attributes that determine if the "installfeature" name appears on the Notes feature installation panel are "default," "required," and "show."
The required attributes for each "installfeature" element are described below:
Note The "default" attribute is ignored when re-running the installer and is ignored on upgrade unless the "installfeature" did not exist in the previously installed offering. This allows the installer to display the state (installed or not installed) of the "installfeature" that was available in the previously installer offering.
The required attributes for each "feature" element are described below:
Note A version value can consist of four parts -- major.minor.service.qualifier.
version="version="3.0.0" match="perfect"
This is a three or four part value associated with the feature to be installed. It has dependency with the "match" value in determining whether to install the feature. It also has future dependency on the match value when determining whether to update the installed feature.
The version attribute holds these main values -- major.minor.service release.qualifier. The following example shows version 3.0.0 with the "20070309-1700" qualifier representing a named build or other qualifier value:
version="3.0.0.20070300-1700"
A sample custom feature is shown below.
<installfeature default="false" id="ISVExample1" name="YourToolA" required="false" show="true" version "3.0.0.20070309-1700">
<requirements>
<feature download-size="72457" id="com.abx.yourtoolabxz.tools.feature" match= "perfect" size="227855" url="${installer.root}/updateSite.zip" version="3.0.0.20070309-1700"/>
Related topics