This topic applies only on the IBM i operating system.

enablejvm command

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.

The following table indicates which JVM versions are supported on which IBM® i releases.
Table 1. Support for JVM versions in IBM i releases. The following table describes the support for JVM versions in IBM i releases.
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.

Before you can run the enablejvm command, ensure that you meet all the following criteria:
  1. Unless you have Fix Pack 7.0.0.7 or higher installed, the IBM i system, on which you have the product installed, must have at least two of the supported JVMs installed. If your system has only one JVM installed, there is no reason to run the enablejvm command.

    Starting with Fix Pack 7.0.0.7, only the target JVM must be installed.

  2. The Portable Application Solution Environment (PASE) product is installed on your IBM i system. Both the IBM version of the J2SE 6.0 32-bit JVM and the IBM version of the J2SE 6.0 64-bit JVM require this product. If this product is not already installed, install the PASE product which is option 33 of the IBM i operating system, and is included with the media for IBM i 5.4 and higher.

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.

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. enablejvm doesl not process the request if the target jvm_version is not installed. jvm_version must be one of the following supported versions:
  • classic. When this value is entered, the application server is configured to use the IBM i Java Developer Kit 6.0 JVM. This value is valid if you are running the product on IBM i Version 6.1 or lower.
  • std32. When this value is entered, the application server is configured to use the IBM version of the J2SE 6.0 32-bit JVM.
  • std64. When this value is entered, the application server is configured to use the IBM version of the J2SE 6.0 64-bit JVM. This value is valid if you are running the product on IBM i Version 6.1 or higher.
-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 that is specified for jvm_version. The script also updates any existing profiles to use this JVM. New profiles inherit the JVM settings of the product at the time that they are created. If you do specify the -profile parameter, only the profile specified by profile_name is updated to use the JVM that is specified for jvm_version.

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, 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.




Related tasks
Using command line tools
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=rxml_enablejvm
File name: rxml_enablejvm.html