A Client Services Platform configuration can reside within any project in the workspace, however, it is suggested that a project, such as a General Project, be created as the location where the platform configuration is saved.
To create a General Project, follow these steps:
- Select File -> New -> Project -> General -> Project and click Next.
- Enter the project name, then select Finish.
To create a platform configuration, follow these steps:
- Select File -> New -> Other -> Client Services -> Client Services Platform and click Next.
- Enter or select the parent folder. The parent folder name is the name of the project where the platform configuration will reside.
- Enter or select a file name for the platform configuration. For a new file, the file name extension defaults to .xpdplatform. If you are opening an existing file with an extension of .product, you will be prompted to save the file with a .xpdplatform extension.
- Select Finish.
- When the file is created, it will be opened by default in the editor. Subsequently, the file can be opened using the standard Eclipse techniques of double clicking the file, or right-clicking the file name and selecting Open With > Client Services Platform Editor from the context menu displayed.
- The information contained in the platform configuration is displayed within the Client Services Platform Editor on three pages. The three pages are labeled Overview, Configuration, and Launcher. To select a page, click on the page name. The information on all three pages should be filled in before attempting to export the platform configuration.
- On the Overview page :
- Select the Target configuration.
- Select Add to open the Feature List Selection dialog and add additional features. The list selection dialogs have two tabs with the first tab listing features that are required, enabled, or available as defined by the target configuration chosen.
The first tab also provides a Select Available button and a Select Enabledbutton, which enables you to include the optional (unselected enabled or available) features for the current target selected.
The second tab of the Feature List Selection dialog contains the rest of the features that were found by Eclipse, but are not on the first tab of this dialog. Only features not already selected for the platform are displayed.
- On the Configuration page:
- Specify the Personality, Application ID, or Product ID.
- Optionally, specify a product name.
- A config.ini file is created by default, which is used by the runtime during startup. Users can replace this file with their own custom config.ini file in the workspace by selecting Use an existing config.ini file and selecting it using the Browse button.
- On the Launching page:
- Select the tab that corresponds to the platform you are using.
- Select the JRE or Execution Environment to be set for the runtime.
- Enter the program arguments, VM arguments, and bootstrap entries on the platform tab that corresponds to the Target Environment. Selecting the platform tab that corresponds to the Target Environment will provide a set of recommended values. For example, a typical program argument is -console, and a typical VM argument is -Xdump:heap.
- Save the configuration.
To export and test your generated configuration, refer to Exporting a Client Services platform
In previous releases of Lotus
® Expeditor for Devices, the Enterprise Management Agent was dependent on the com.ibm.rcp.agentprefs
fragment to provide platform restart capabilities. This fragment has GUI dependencies, which is unfavorable if you want to run a smaller configuration of Lotus
Expeditor in a headless environment. In this release, Lotus
Expeditor provides another platform restart mechanism so that the Enterprise Management Agent can fully run without any GUI dependencies. If you use Platform Builder to create a GUI platform with Enterprise Management Agent, include the com.ibm.rcp.agentprefs
feature. If you are creating a platform with Enterprise Management Agent, but without GUI features, you should include the com.ibm.rcp.nongui.agentapp
For details on the Client Services Platform Editor, refer to Client Services Platform Editor
Parent topic: Creating client runtime images