You can configure EAServer to use the JDK versions described in “JDK versions”. For each JDK version, you can install the JDK, use an existing installation, or not use that JDK version at all.
The parameters in Table 3-5 allow you to configure the EAServer installation to use JDK installations that are already in place, rather than installing JDKs with the EAServer installation.
Parameter |
Specifies |
|---|---|
-W SilentEASJDK13installed.value |
Whether to use an existing JDK 1.3 installation
to run servers. To use an existing installation, set this parameter
to |
-W SilentEASJDK13Location.value |
If you are using an existing JDK 1.3 installation, the location where it is installed. Verify the version and patch level of the specified JDK as described in “JDK versions”. |
-W SilentEASJDK14installed.value |
Whether to use an existing JDK 1.4 installation
to run servers with. To use an existing installation, set this parameter
to |
-W SilentEASJDK14Location.value |
If you are using an existing JDK 1.4 installation, the location where it is installed. Verify the version and patch level of the specified JDK as described in “JDK versions”. |
To install a JDK from your install image, enable the feature parameter for that JDK and include the required files in your image, as listed in Table 3-6.
Parameter |
Specifies |
Comments |
|---|---|---|
-P EASJDK.active |
Whether to install any JDKs from the install image. |
Must be set to True or the next three parameters are ignored. |
-P EASJDK13_server.active |
Whether to install JDK 1.3 |
To install, your image must have the file SupportNT/EAS_jars/EAS_jdk13.jar. |
-P EASJDK14_server.active |
Whether to install JDK 1.4 |
To install, your image must have the file SupportNT/EAS_jars/EAS_jdk14.jar. |
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
