This topic applies only on the i5/OS operating system.

enablejvm command

The enablejvm command allows you to configure your application server or a specific profile to use the IBM Technology for Java Virtual Machine instead of the classic JVM. The IBM Technology for Java Virtual Machine is available in both 32-bit and 64-bit versions (options 8 and 9 of IBM Developer Kit for Java).

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 as it applies to your system:

By default, the application server is configured to use the i5/OS Java Developer Kit 5.0 JVM (also known as the "classic" JVM). The enablejvm command only operates in 32-bit mode in this case.

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:
  1. Edit the following file:

    profile_root/properties/soap.client.props

  2. Specify the administrative user name and password for the com.ibm.SOAP.loginUserid and com.ibm.SOAP.loginPassword properties, respectively.
  3. Save the file.
  4. 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.
  • std64. This specifies the application server to use the IBM J2SE 5.0 64-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:

i5/OS release V5R4M0
enablejvm -jvm std32 [-profile profilename]
enablejvm -jvm classic [-profile profilename]
i5/OS release V6R1M0 (32-bit)
enablejvm -jvm std32 [-profile profilename]
i5/OS release V6R1M0 (64-bit)
enablejvm -jvm std64 [-profile profilename]
Note: 64-bit use of the enablejvm command only applies to i5/OS release V6R1M0 or higher.

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.




Related tasks
Using command line tools
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=rxml_enablejvm
File name: rxml_enablejvm.html