The Expeditor Client installation process consists of two steps: installation of core platform files and provisioning of additional components. Depending on the desired install configuration (user or multiuser), differing sets of components are provisioned to the product from update sites.
The set of components to be provisioned is defined within a provisioning manifest, which is processed by the installer and platform provisioning system. The file must be named install.xml
and be located in a deploy/ directory located in the same location as the installer executable
The Expeditor Client CD includes a provisioning manifest for each of these install configurations. You cannot modify these files because they reside on the CD. However, if the contents of the install directory were copied to a read-write file system (as in the case of a Web download scenario), then the files can be modified to have each of these install configurations include a customized set of components.
Modifying these provisioning manifests from their shipped states could result in an invalid platform installation.
During the installation process, the provisioning manifest is processed (replacing any supported variables) and copied to <product destination>/rcp/deploy/install.xml
The location of this file is then passed to the platform provisioning component to begin the provisioning process.
The Expeditor platform defines a default set of features that will be provisioned during the initial installation. The list of features can be updated prior to installation to either remove features that are not desired, or to add custom or application specific features.
In all configurations, the launcher (rcplauncher.exe) reads the rcplauncher.properties to determine the provisioning.manifest.version property, and compares to the version currently specified in the rcpinstall.properties. If the version in rcplauncher.properties is greater than the version in the rcpinstall.properties file, then launcher will start the platform provisioning application to update the platform based upon the provisioning manifest (specified in the rcplauncher.properties).
In the multiuser platform configuration, the provisioning manifest is therefore used as the basis for creating the new workspace for every user.
By updating the provisioning manifest contents, and the provisioning.manifest.version, the launcher will start the provisioning application to process the provisioning manifest.
While the provisioning manifest can be directly updated on the system, the preferred model for distributing a new manifest is to use the mergemanifest command provided by the Global Install Handler. The install handler provides a mechanism to deploy a new provisioning manifest and to merge it with the existing manifest present on the system. This enables the deployment of a subset of new changes that will be merged into the existing manifest without requiring the specification of an entire file.
The mergemanifest command is also used to deliver a new version of the provisioning manifest, such as occurs during an upgrade of the existing platform.
Understanding the merge processing for the provisioning manifest: XPD621
The provisioning manifest generally serves two purposes. During the initial installation, the provisioning manifest provides instructions for the install program to specify the options available for installation, and also specifies the features that need to be installed during the initial provisioning. Subsequent to the install, the provisioning manifest is used during the construction of new workspaces to provide the initial configuration for those workspaces.
Provisioning manifest DTD: XPD621
The provisioning manifest is an XML file that lists the features to be installed during the provisioning portion of the install process.
Parent topic: Deploying features to the platform: XPD621