This section provides information about the creation and the contents of the Lotus® Expeditor workspace.
The workspace is used to store data in between platform launches, and also contains the configuration area for the platform. The configuration area stores information related to the applications and features installed in the platform.
The initial workspace is created during the initial install. The install program first installs a minimal set of features and plug-ins into the installation directory. These features are then used to launch the platform for the first time. During this first time launch, the initial workspace is created. The initial workspace and configuration are created based on the contents of the provisioning manifest. All of the features defined in the provisioning manifest are installed and enabled, and the resulting configuration information is stored in the workspace.
In multiple user environments, when additional workspaces are created following the initial workspace creation, the features installed during the initial workspace creation are used. With respect to the feature life cycle, this means that the features are not installed again but are only enabled. If you are providing your own features and they contain install handlers, they should perform most of the required work on the configure and unconfigure operations. For more information, see Understanding feature life cycle
On Windows, if the platform installation is performed using the System account, the initial workspace will be located in <install dir>\\rcp\\systemdata
. If the platform installation is performed by an administrator, the initial workspace will be located, by default, in %APPDATA%\\Lotus\\XPD
. On Linux, the initial workspace will always be located in <install dir>/rcp/systemdata
Two system properties defined in the .config/rcpinstall.properties file in the workspace provide specific information for the launcher to determine what happens when launching the platform.
Associates a version of the workspace with an installed version of the platform. Upon launch, the value of rcp.install.id
is compared with the value of the rcp.install.id
in the <install_dir
/rcp/rcplauncher.properties file. If these values are different, it is assumed that the workspace does not match the installed platform. See Reusing an existing workspace
for more information.
Defines the version of the workspace configuration that is used. On launch, the value of the provisioning.manifest.version
is compared with the value of the provisioning.manifest.version
property in the <install_dir
/rcp/rcplauncher.properties file. If these values are different, then it is assumed that the provisioning manifest defined by the rcplauncher.properties file is more recent and needs to be applied to the workspace. The launcher than launches the platform using the ProvisioningApplication to perform the operations defined in the provisioning manifest. See Using the Provisioning application
for more information.
As the platform definition contains features associated with specific locales, only those features that apply to the current locale will be enabled. For example, if you launch the platform using the German locale de
, the only features that will be enabled are those without a specific locale filter and those features that contain the filter specifying de
as a specific locale. In a multiple user scenario, you must first install all locale-related features prior to users creating a new workspace.
Parent topic: Launching the Lotus Expeditor on the desktop: XPD621