| Next Page
This topic describes how to start the Lotus® Expeditor Client, how the daemon process works, and how an existing process is joined if a new personality is requested.
See Configuring the platform launcher for details on available commands.
Starting the Lotus Expeditor Client
During installation of the Lotus Expeditor Client a new desktop icon titled Expeditor 6.2 will be created, which can be used to start the Lotus Expeditor Client.
Additionally, you can launch the Lotus Expeditor Client from the command line. By default, no arguments are required, but additional arguments can be provided. For a list of the supported command line arguments, see Configuring the platform launcher. On Linux® systems, if the Lotus Expeditor Client has been installed to the default directory, use the following command
to launch the client:
On Windows® systems, if the Lotus Expeditor Client has been installed to the default directory, use the following command to launch the client:
This section describes how the daemon works and how and existing process is joined when using a new personality.
When the Lotus Expeditor is running, you can execute commands from outside of the Expeditor user interface through the use of an Expeditor daemon. These commands are treated as additional arguments to the main rcplauncher executable. When an rcplauncher process is invoked with these additional commands and an Lotus Expeditor is already running, the rcplauncher process will use the daemon and inform the Lotus Expeditor to execute these commands instead of bringing up another full instance of the Lotus Expeditor and then invoking the commands within the new environment.
You can invoke additional personalities that will join the currently running Lotus Expeditor environment rather than creating another full instance. This is done using the daemon discussed in the previous section and is done to help conserve system resources.
As an example, let's examine an office productivity suite of applications containing a word processor and a spreadsheet application. Each of these applications may be separate desktop icons, both of which use the rcplauncher executable but provide a different personality via the -personality parameter. Initially, the user needs to work on some spreadsheet data to generate the necessary data for a letter to be written so the user launches the spreadsheet. When nearing completion of the spreadsheet work, the user decides to begin work on the letter to ensure the layout will lend well to the data to be included, so the user now launches the word processing application. The rcplauncher process will recognize the Lotus Expeditor is already running with the spreadsheet personality and will
not invoke another full instance. Instead, the rcplauncher process will use the daemon and have the currently running Lotus Expeditor open a new window, using the new word processing personality.
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.
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
- 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.
This section details how existing workspaces are handled.
Workspaces will reused if the value of the rcp.install.id property in the rcpinstall.properties does not match the value of rcp.install.id property in the rcplauncher.properties.
This situation will generally occur if a workspace pre-exists on a system, and a new install of Lotus Expeditor occurs.
If the launcher determines that the workspace does
not match the installed version of the platform based on the rcp.install.id property, the launcher will take the following actions:
- The .config/platform.xml file will be copied to the workspace root and renamed to platform.xml.old.
- The .config directory is backed up.
- A new rcpinstall.properties will be created from the contents of the rcpinstall.properties supplied in the com.ibm.rcp.base plug-in.
- The ProvisioningApplication will be launched to create a new workspace:
- The ProvisioningApplication will read the provisioning manifest defined by the rcplauncher.properties file and will attempt to create a new workspace using the features already installed on the file system, just as if the workspace had not previously existed.
- The ProvisioningApplication will read the platform.xml.old file that was created and will attempt to enable each of the features included in the user applications site.
- The ProvisioningApplication will read the provisioning manifest and will attempt to enable each of the features included in the shared site.
- The ProvisioningApplication will exit and the launcher will restart the installed platform.
This topic describes how to start the Lotus Expeditor Client from a network drive.
When the Lotus Expeditor Client has been installed onto a shared network drive, no
icons are created or available for users to do the initial launch of the Lotus Expeditor Client. The initial launch must be performed by locating the rcplauncher.exe (Windows) or rcplauncher (Linux) program, and starting the program.
For example, on Windows, if you have a network drive X: that contains the directory X:\Expeditor, switch to the X:\Expeditor\rcp directory, and start the rcplauncher.exe program. The workspace will be created in the normal location. As part of the initial creation of the workspace, icons will be added to the desktop to enable subsequent launches to occur using the shortcuts.
In the event that the drive letter that refers to the network drive changes after the initial launch, the created icons will no longer allow you to launch the Lotus Expeditor Client.
If the drive letter is permanently changed, you can update the shortcut to change the launch location.
The default workspace location is computed based upon the operating system and the defined user.
If your workspace needs to be located at an alternative location, then start the launcher by specifying the "-data" parameter. For example, if you want to store a workspace on a USB drive connected to the system on drive G:, you can start the Lotus Expeditor by specifying rcplauncher -data G:\workspace. As this is a non-standard location for the workspace, you must either update the shortcut used to launch the Lotus Expeditor, or always use a console or Run menu to launch the Lotus Expeditor.
The same workspace can be referenced from different locations. For example,
if the workspace is created on a USB-drive, it may attach as drive G: on one
machine, and as D: on another. You will need to launch the Lotus Expeditor and specifically identify the data directory on each launch.
See Overriding the workspace directory location for more information.
Use the CAI protocol to launch IBM® Lotus Expeditor.
Composite Applications are URL-addressable with URLs beginning
with CAI:. This is known as the Composite Application Infrastructure (CAI) protocol. For the browser to understand the CAI protocol, CAI must be registered with the operating system. In Windows, the registry file cai_register.reg is part of the IBM Lotus Expeditor installation. IBM Lotus Expeditor contains information to be written to the Windows registry. In Linux, a similar technology, called GConf, is used to register CAI with the operating system. On a multi-user installation, the first time the Lotus Expeditor Client is run by each user, this registration (enablement) is executed.
Thereafter, when a URL beginning with CAI:/ is used in the browser, IBM Lotus Expeditor will open (if not already open) and load the specified composite application. See Creating client runtime images for more information. In addition, links starting with CAI: that are included inside document types which support links on the operating system will also be enabled, resulting in IBM Lotus Expeditor opening and loading the specified composite application.
Within IBM Lotus Expeditor, use the Edit - Previous Page
Copy As menu items (enabled when a composite application is opened) to create these CAI:/ links.
| Next Page