Follow the instructions in this section to install the IBM
® Device Runtime Environment (DRE), a separately available product.
Device Runtime Environment product contains two features that are applicable to the Lotus
® Expeditor Client platform. The first is the J2SE Core JVM Feature, which provides the Java
™ 2 SE 6.0 VM capabilities. The second feature is the JavaServer Faces Feature, an alternative to the Apache MyFaces support.
To use either of these components, you must install them into the Lotus
Installing DRE components into the Lotus Expeditor Client
Install the DRE using either the Install/Update UI or using the provisioning manifest. The Install/Update UI is useful for installing a DRE into only one runtime, but for automation purposes, you should consider using the provisioning manifest.
To install DRE components using the Update Manager UI:
- Start the Lotus Expeditor Client. Then select File -> Application -> Install
- From the Install/Update (Feature Updates) dialog, select Search for new features to install. From the Install (Update Sites to Visit) dialog, create a new Update site definition.
Select a New Remote Site if the DRE has been made available using a Web site. Otherwise, select a New Local Site. Browse to the location of the DRE (CD-ROM drive letter or location where it might have been unzipped on a mapped drive letter or mount), then select updates/client. Select Finish.
When the Install (Search Results) dialog appears, select the Core JVM Feature – J2SE feature, then select Next. (You can also select the JavaServer Faces (JSF) feature at this point). If the license terms are agreeable, select I accept the terms in the license agreement, then select Next. Then select Finish to complete the installation.
A dialog informing you that the feature is not signed might appear. Select Install on this dialog to continue.
- To perform a more automated installation of the DRE, you can either customize the provisioning manifest for install (Customizing basic installation) or use the ProvisioningApplication to install the DRE using a provisioning manifest (Using the provisioning manifest).
For example, you could use the following provisioning manifest contents in file C:\core.jvm.feature-j2se.xml:
<installfeature id="core.jvm.feature-j2se" required="true">
is the CD-ROM drive containing the DRE CD-ROM.
You would then invoke the provisioning application to install the DRE in addition to the DesktopEE VM that is already installed:
rcplauncher –application com.ibm.rcp.provisioning.application.ProvisioningApplication
–provisioningOperation provision C:\core.jvm.feature-j2se.xml
Alternatively, you can choose to only install the Core JVM Feature – J2SE during the initial installation.
You can update the install.xml provisioning manifest to include the feature definition as above (and remove the com.ibm.rcp.jvm.feature definition that refers to the version 1.0.0.x of the jvm feature).
Changing to a different runtime and class library
Although you can install both virtual machines (DesktopEE and Java
2 SE 6.0) into the Lotus
Expeditor Client, only one VM is active for the platform. To switch the active VM, you must use the Application Management UI to switch the VMs. To do so, select File
-> Application Management
. Expand the /rcp/eclipse site, and locate the Core JVM Feature
. Select this feature, then select the task Replace with another version
. This will open a dialog prompting you to select another version of the feature. You can switch from DesktopEE to J2SE, or J2SE or DesktopEE using this method.
Understanding the VM packaging
The VM that implements the Java
specifications is packaged as a feature.
All VM features are child features of the parent feature com.ibm.rcp.jvm. The major version number represents an entirely different VM provider. For instance, the Lotus
Expeditor Client ships with Desktop EE VM and is major version 1. This scheme allows for seamless upgrade of a VM and also allows the switching of VMs using the update manager.
The VM properties are located in the VM plug-in file jvm.properties. The launcher dynamically adds these properties to the launch command. This method assures that the VM plug-in defines the properties that it needs.
property can be used on the command line. However, if you need additional VM properties, you are responsible for adding them.
Parent topic: Changing the virtual machine