The enablejvm command enables you to configure your application server or a specific profile to use the IBM® Technology for Java Virtual Machine, by choosing either option 11 or option 12 of the IBM Developer Kit for Java.
IBM i 6.1 | IBM i 7.1 |
---|---|
The IBM version of Java Platform, Standard Edition 6 32-bit JVM (5761JV1 option 11) | The IBM version of Java Platform, Standard Edition 6 32-bit JVM (5761JV1 option 11) |
The IBM version of Java Platform, Standard Edition 6 64-bit JVM (5761JV1 option 12 ) | The IBM version of Java Platform, Standard Edition 6 64-bit JVM (5761JV1 option 12 ) |
By default, the product uses the IBM version of the Java SE 6 32-bit JVM.
For more information about where to run this command, see the Using command-line tools topic.
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.
The command syntax is as follows:
enablejvm [options]
The following options are available for the enablejvm command:
If the SOAP protocol is enabled, the enableJVM command uses the SOAP protocol. If the SOAP protocol is not enabled but the IPC protocol is enabled, the command uses the IPC protocol. If neither the SOAP nor the IPC protocol are enabled, then the command uses the RMI protocol.
You must provide the administrative user name and password with the enableJVM command for each profile that contains a federated node or deployment manager node in a cell with security enabled. If you do not specify the -user and -password parameters, the enableJVM command might fail or stop processing. The topic on configuring security with scripting provides connector protocol specific instructions on how to save user name and password values.
When enabling the JVM for a deployment manager, only the deployment manager server is enabled. None of the managed nodes of the deployment manager are enabled to use the specific JVM version.
The following examples demonstrate correct syntax:
enablejvm -jvm std32 [-profile profile_name]
enablejvm -jvm std64 [-profile profile_name]
If you did not specify the -profile parameter on the enablejvm invocation, restart any servers (such as node agents, deployment managers, and application managers) 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 effect.
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 Java SE 6 32-bit JVM. Therefore, after you enable a profile to use the IBM Java SE 6 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 than the 32-bit JVM three gigabyte Java heap size limit. Review all of your Java heap settings in the administrative console and either change or eliminate them as appropriate.