The enablejvm command allows you to configure your application
server or a specific profile to use the to use the IBM® J2SE 5.0 32-bit JVM. By default, the
application server configured to use the i5/OS® Java™ Developer Kit 5.0 JVM (also known as
the "classic" JVM).
For more information about where to run this command, see the Using
command line tools article.
Before you can run the
enablejvm command, ensure that you meet all
the following criteria:
- You have i5/OS release
V5R4M0 installed.
- You have installed the Portable Application Solution Environment (PASE)
product. If it is not already installed, install the PASE product, which is
option 33 of the i5/OS operating system and is included with the media
for i5/OS V5R4M0
and higher.
- You have installed the IBM J2SE 5.0 32-bit Java Developers Kit option. This is option
8 of product 5722JV1 (IBM Developer Kit for Java) and is included with the media for i5/OS V5R4M0
and higher.
- You have installed the latest group PTF for Java. The group PTF number is SF99291. If
SF99291 is already installed, but you installed PASE or 5722JV1 option 8 afterwards,
load and apply the group PTF again to ensure you have all necessary PTFs.
Network Deployment Considerations:
For any profile (node) that is part of
a Network Deployment cell, the deployment manager for the node must be running
when the enablejvm script attempts to update the profile. When enabling
the JVM for a node, invoke the enablejvm command from the bin directory of
the product install to which the node belongs. Alternatively, you can invoke
the enablejvm command from the profile's bin directory where the profile is
the profile containing the node you want to update.
If your deployment manager has administrative
security enabled, you must provide the administrative user name and password
in the soap.client.props file for the node you are enabling:
- Edit the following file:
profile_root/properties/soap.client.props
- Specify the administrative user name and password for the com.ibm.SOAP.loginUserid
and com.ibm.SOAP.loginPassword properties, respectively.
- Save the file.
- Encode the password in the file using the PropFilePasswordEncoder script
located in the app_server_root/bin directory
for the product:
PropFilePasswordEncoder
profile_root/properties/soap.client.props
com.ibm.SOAP.loginPassword
When enabling the JVM for a deployment
manager, only the deployment manager server is enabled. None of the nodes
which are managed by the deployment manager are enabled to use the specific
JVM.
Syntax
The command syntax is as follows:
enablejvm [options]
Parameters
The following options are available for
the enablejvm command:
- -jvm jvm_version
- This is a required parameter. jvm_version must be one
of the following:
- std32. This specifies the application server to use the IBM J2SE 5.0 32-bit
JVM.
- classic. This specifies the application server to use the i5/OS Java Developer
Kit 5.0 JVM.
- -profile profile_name
- This is an optional parameter. If you do not specify the -profile parameter,
the script enables the product to use the J2SE 5.0 JVM and also updates any
existing profiles to use the JVM.
Usage scenario
The following examples demonstrate
correct syntax:
enablejvm -jvm std32 [-profile profilename]
If you did not specify the -profile parameter on the enablejvm invocation,
restart any servers (node agents, deployment
managers, application managers, etc.) which are running. If you did specify
the -profile parameter on the enablejvm invocation, restart any servers
which belong to the profile that was changed.