INSTALLING
You must also properly add the new or third-party feature to the install kit.
CAUTION: All features must be properly signed in order to be installed as part of a Notes install or upgrade.
See the related topics for information on signing.
The Notes install manifest Document Type Definition (DTD) differs from the standard Eclipse or Expeditor install or provisioning manifest DTD. For example, the Notes install manifest contains at least four unique attributes: "required," "default," "show," and "description."
See the related topics for information on provisioning.
installfeature element
The attributes that determine if the "installfeature" name appears on the Notes feature installation panel are "default," "required," and "show."
The following list describes the required attributes for each "installfeature" element:
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 following list describes the required attributes for each "feature" element:
Note: A version value can consist of four parts -- major.minor.service.qualifier.
For example, the following attributes allow installation only if the version value in the update site and site.xml file is 3.0.0.
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 "20100309-1700" qualifier representing a named build or other qualifier value:
version="3.0.0.20100300-1700"
The following is a sample custom feature.
<installfeature default="false" id="ISVExample1" name="YourToolA" required="false" show="true" version "3.0.0.20100309-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.20100309-1700"/>
Related concepts Eclipse files and folders in the Notes install kit
Related tasks Customizing Notes install for features and plug-ins on Windows and Mac Signing custom or third-party features and plug-ins for install and update Adding and removing components from the Notes install kit using UpdateSiteMgr Updating a widget-deployed client feature or plug-in Customizing a Notes install kit to set certifier and trust defaults
Related reference Validating your customized Notes install kit
Related information Provisioning manifest DTD