The enablejvm command allows you to configure your application server or a specific profile to use one of the IBM® versions of a Java™ virtual machine (JVM) that is supported on IBM i.
IBM i 5.4, and higher | IBM i 6.1, and higher |
---|---|
IBM i Java Developer Kit 6.0 JVM, also known as classic JVM, (V5R4(5722JV1) V6R1(5761JV1) option 10) | IBM i Java Developer Kit 6.0 JVM, also known as classic JVM, (V5R4(5722JV1) V6R1(5761JV1) option 10) |
The IBM version of Java Platform, Standard Edition (J2SE) 6.0 32-bit JVM ( V5R4(5722JV1) V6R1(5761JV1) option 11) | The IBM version of Java Platform, Standard Edition (J2SE) 6.0 32-bit JVM ( V5R4(5722JV1) V6R1(5761JV1) option 11) |
The IBM version of the Java Platform, Standard Edition 6.0 64-bit JVM ( 5761JV1 option 12 ) |
By default, the product uses the IBM version of the J2SE 6.0 32-bit JVM.
The IBM i 6.1 is the last release on which the IBM i Java Developer Kit 6.0 JVM is supported.
For more information about where to run this command, see the Using command line tools topic.
Starting with Fix Pack 7.0.0.7, only the target
JVM must be installed.
WebSphere® Application Server, Network Deployment Considerations:
For any profile (node) that is part of a WebSphere Application Server, 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.
profile_root/properties/soap.client.props
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.
enablejvm [options]
The following options are available for the enablejvm command:
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, you must restart any servers that belong to the profile that was changed before the change takes affect.
The -Xms or -Xmx Java arguments are used to change the initial Java heap size or the maximum Java heap size for an application server. If you previously used the administrative console to add either the -Xms or -Xmx Java arguments to the Generic JVM arguments setting for an application server, these settings might not be appropriate or even valid for the IBM version of the J2SE 6.0 32-bit JVM. Therefore, after you enable a profile to use the IBM version of the J2SE 6.0 32-bit JVM, the first time that you start an application server under that profile, the application server might fail because either of these Java heap size settings is greater then the 32-bit JVM three gigabyte Java heap size limit. You should review all of your Java heap settings in the administrative console and either change or eliminate them as appropriate.