The Expeditor Client uses the J2SE runtime environment by default. On Windows
®, if you would instead like to use an existing Java
™ 1.5 or 1.6-based virtual machine on your system during the installation of the Expeditor Client, you must use the EXTERNAL_JVM_LOCATION
®, the internally packaged J2SE virtual machine is always installed. Upgrading from previous platforms where an external JVM was used will now result in the internal JVM being used. The EXTERNAL_JVM_LOCATION
property is not available on Linux
for Expeditor Client 6.2.1.
property must point to a valid IBM
® or Sun JVM, version 1.5 or 1.6, and must also point to the Java
) that you wish to use. The installation of Expeditor Client validates this JVM to ensure that it is a supported JVM. Expeditor Client does not allow an installation using unsupported JVMs.
Expeditor Client supports the following external JVMs:
- Sun J2SE 5.0
- Sun Java SE 6.0
- IBM J2SE 5.0
- IBM Java 6.0
- DesktopEE 6.5
, you can set the EXTERNAL_JVM_LOCATION
property either as a command-line property or within a transform.
To set it as a command-line property, use:
setupwin32.exe /v"EXTERNAL_JVM_LOCATION=\"<absolute path to Java executable on system>\""
To set it within a transform, you must add the EXTERNAL_JVM_LOCATION
property and give it a value of:
<absolute path to Java executable on system>
If you wish to utilize the default JVM on your system (and not provide an exact location to the java
executable) you may set EXTERNAL_JVM_LOCATION=SYSTEM_JVM
. Expeditor Client validates the system JVM to ensure that it is a supported version before installing.
When installing a platform and using an external JVM, only upgrades which also use an external JVM are supported. Upgrading a platform that does not use an external JVM to one that uses an external JVM is not supported. Similarly, upgrading a platform that uses an external JVM to one that does not use an external JVM is not supported.
Parent topic: Changing the virtual machine