+

Search Tips   |   Advanced Search

AdminSDKCmds

Use commands in the AdminSDKCmds group in the Jython or Jacl scripting languages to manage software development kit configurations.

Use the commands in the AdminSDKCmds group for the AdminTask object, we can see what software development kits are not used by a node, get or set the default software development kit (SDK) for a node, and get or set an SDK for a server.

The AdminSDKCmds commands include:

Every WebSphere Application Server version and operating system has a default SDK. The name of an SDK installed at a particular computer location must be unique. On workstations, the default SDK is installed in a directory name that starts with ${WAS_HOME}/java for 64-bit operating systems; for example, ${WAS_HOME}/java, or ${WAS_HOME}/java_8.0_64.

(iSeries) For the OS/400 operating system, the software development kits are part of the operating system installation and are not part of the WAS installation. For the OS/390 operating system, symbolic links to the software development kits are in ${WAS_HOME}/java* directories.

The AdminSDKCmds wsadmin commands pertain to SDKs used by nodes or servers. To list and change the default SDK for a profile, use the managesdk command-line utility.


getNodeDefaultSDK

Return the values of the default SDK for a node. The returned values include the Java home and SDK name.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


getSDKVersion

Run the getSDKVersion command to return the version number of the software development kit in use.

To get the SDK version in use in the cell, do not specify values for -nodeName, -serverName, or -clusterName.

Target object: None

Required parameters: None

Optional parameters:

Batch mode example usage

Interactive mode example usage


getServerSDK

Return the values of the software development kit for a server. If a valid SDK value is set for the server, the returned values include the Java home and SDK name of the default SDK for the server.

If no SDK value is set for the server, the command returns nothing for the Java home value because a variables.xml file does not exist for the server or a JAVA_HOME entry does not exist in the variables.xml file. For the SDK name value, the command returns the node SDK name because the node SDK is the default SDK for a server when a valid SDK has not yet been set using the setServerSDK command.

Target object: None

Required parameters:

Optional parameters:

Batch mode example usage

Interactive mode example usage


getUnusedSDKsOnNode

Run the getUnusedSDKsOnNode command to return a list of the names of software development kits that a node is not using.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


setNodeDefaultSDK

Assign a default software development kit for a node. For the command, specify either the SDK Java home or the SDK name, but not both.

Target object: None

Required parameters:

Optional parameters:

To set a node default SDK, specify the required -nodeName parameter with either -javahome or -sdkName. Both the -javahome and -sdkName parameters are optional but specify either one of the parameters.

To clear all SDK settings for all servers on a node, specify the required -nodeName parameter with either -javahome or -sdkName and with the optional -clearServerSDKs parameter set to true.

Batch mode example usage

Interactive mode example usage


setServerSDK

Assign a software development kit for a server. The command creates a variables.xml file for the server that designates the SDK. For the command, specify either the cluster or both the node and server. Optionally specify either the SDK Java home or the SDK name, but not both.

To clear the server SDK assignment, do not specify values for SDK Java home or the SDK name. For example, if server1 is assigned SDK 8.0_64, run setServerSDK without the -javahome and -sdkName parameters to have no SDK assigned for server1.

If we change the server SDK, ensure that the options and properties for the Java command are compatible with the new SDK. See Configuring the JVM. Target object: None

Required parameters: None

Optional parameters:

Batch mode example usage

Interactive mode example usage

  • wsadmin AdminTask
  • Configure the JVM
  • ManagedObjectMetadata
  • Commands for the AdminTask object
  • managesdk command