FreeKB - IBM WebSphere Java SDK
IBM WebSphere - Java SDK

SDK stands for software development kit. Before you update a dmgr, node agent, or application server to use a certain version of Java SDK, you must first install the version of Java that you want to use.

If you are not sure what versions of Java SDK you have installed, the managesdk -listAvailable command can be used.

${WAS_INSTALL_ROOT}/bin/managesdk.sh -listAvailable
. . .
CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.7_64
CWSDK1005I: SDK name: 1.8_64
CWSDK1001I: Successfully performed the requested managesdk task.

 

If you need to identify the full build version of Java, the java command with the -version option can be used.

${WAS_INSTALL_ROOT}/java/bin/java -version   

java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 8.0.5.37 - pxa6480sr5fp37-20190618_01(SR5 FP37))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190617_419755 (JIT enabled, AOT enabled)
OpenJ9   - 354b31d
OMR      - 0437c69
IBM      - 4972efe)
JCL - 20190606_01 based on Oracle jdk8u211-b25

 

The managesdk -listEnabledProfileAll command can be used to list the version of Java SDK being used by the profile, node, and servers. The managesdk -enableProfile command can be used to update a profile, node, and servers to use a certain version of Java SDK, and the managesdk -setNewProfileDefault command can be used to update a profile, node, and servers to use a certain version of Java SDK by default. 

${WAS_INSTALL_ROOT}/bin/managesdk.sh -listEnabledProfileAll

CWSDK1004I: Profile Profile01 :
CWSDK1006I: PROFILE_COMMAND_SDK = 1.7_32
CWSDK1008I: Node Node01 SDK name: 1.7_32
CWSDK1009I: Server Server01 SDK name: 1.8_32
CWSDK1009I: Server Server02 SDK name: 1.8_32
CWSDK1001I: Successfully performed the requested managesdk task.

 

The managesdk -getCommandDefaults command can be used to list the version of Java SDK that are being used by commands. The managesdk -setCommandDefaults command can be used to update commands to use a certain version of Java SDK by default. 

${WAS_INSTALL_ROOT}/bin/managesdk.sh -getCommandDefault
. . .
CWSDK1006I: COMMAND_DEFAULT_SDK: 1.7_64
CWSDK1001I: Successfully performed the requested managesdk task.

 

 


dmgr (using the web console)

  1. In the dmgr web console, select System administration > Deployment manager.
  2. Select the Java SDKs.
  3. To update the dmgr, select one of the available Java SDKs and select Make Default.
  4. Select Save.
  5. Restart the dmgr for this change to take effect.

 

node agent (using the web console)

  1. In the dmgr web console, select System administration > Node agents.
  2. Select a node agent.
  3. Select the Java SDKs.
  4. To update the node agent, select one of the available Java SDKs and select Make Default.
  5. Select Save.
  6. Synchronize the node.
  7. Restart the node for this change to take effect.

 

application server (using the web console)

  1. In the dmgr web console, select Server > Server Types > WebSphere application servers.
  2. Select an applicaton server.
  3. Select the Java SDKs.
  4. To update the application server, select one of the available Java SDKs and select Make Default.
  5. Select Save.
  6. Synchronize the node.
  7. Restart the application server for this change to take effect.

 

In this example, version 1.7_64 is being used.

 


SystemOut.log

After you restart the dmgr, node agent, or application server, Java version and Java Home in SystemOut.log should contain the version of Java being used (Java 8, 64-bit in this example).

Java version = 1.8.0
Java Home = ${WAS_INSTALL_ROOT}/java_1.8_64/jre

 



Add a Comment




We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.




Please enter 34371 in the box below so that we can be sure you are a human.




Comments

Web design by yours truely - me, myself, and I   |   jeremy.canfield@freekb.net   |