+

Search Tips   |   Advanced Search

Commands for the AdminTask object using wsadmin scripting

Use the AdminTask object to run administrative commands with the wsadmin tool.

Administrative commands are loaded dynamically when we start the wsadmin tool. The administrative commands available for you to use, and what we can do with them, depends on the edition of the product that we use.

We can start the scripting client without having a server running using the -conntype NONE option with the wsadmin tool. The AdminTask administrative commands are available in both connected and local modes. If a server is currently running, it is not recommended to run the AdminTask commands in local mode because any configuration changes made in local mode are not reflected in the running server configuration and vice versa. If you save a conflicting configuration, we can corrupt the configuration.

In a deployment manager environment, configuration updates are available only if a scripting client is connected to a deployment manager. When connected to a node agent or a managed application server, we cannot update the configuration because the configuration for these server processes are copies of the master configuration, which resides in the deployment manager. The copies are created on a node machine when a configuration synchronization occurs between the deployment manager and the node agent. Make configuration changes to the server processes by connecting a scripting client to a deployment manager. To change a configuration, do not run a scripting client in local mode on a node machine because this is not supported.

Configuration note: With the Jacl scripting language, the subst command enables us to substitute a previously set value for a variable in the command. For example:

set nodeparm "node1"
$AdminTask setJVMMaxHeapSize [subst {-serverName server1 -nodeName $nodeparm -maximumHeapSize 100}]

AdminTask commands...

The following AdminTask commands are available but do not belong to a group:


createTCPEndPoint

Create a new endpoint that we can associate with a TCP inbound channel.

Target object: Parent instance of the TransportChannelService containing the TCPInboundChannel. (ObjectName, required)

Required parameters:

Optional parameters: None.

Sample output

The command returns the object name of the endpoint created.

Examples

Batch mode example usage:

Interactive mode example usage:


getTCPEndPoint

Obtain the named end point associated with either a TCP inbound channel or a chain containing a TCP inbound channel.

Target object: TCPInboundChannel, or containing chain, instance associated with a NamedEndPoint. (ObjectName, required)

Required parameters

None.

Optional parameters: None.

Sample output

The command returns the object name of an existing named end point associated with the TCP inbound channel instance or a channel chain.

Examples

Batch mode example usage:

Interactive mode example usage:


help

Provide a summary of the help commands and ways to invoke an administrative command. Use wildcard characters (*) or Java regular expressions (.*) in the command syntax to customize the search query.

Target object: None.

Optional parameters

Sample output

The command returns general command information for the AdminTask object.

Examples

Batch mode example usage:

The following command examples return general help information for the AdminTask object:

The following command examples display each command for the AdminTask object:

The following command examples return detailed command information for the createJ2CConnectionFactory command for the AdminTask object:

The following examples demonstrate the use of the wildcard character (*) to return each command containing the create string:

The following examples demonstrate the syntax to use regular Java expressions (.*):


listTCPEndPoints

List all the named end points that can be associated with a TCP inbound channel.

Target object: TCP Inbound Channel instance for which named end points candidates are listed. (ObjectName, required)

Required parameters: None.

Optional parameters

Sample output

The command returns a list of object names for the eligible named end points.

Examples

Batch mode example usage:

Interactive mode example usage:


listTCPThreadPools

List all of the thread pools that can be associated with a TCP inbound channel or TCP outbound channel.

Target object: TCPInboundChannel or TCPOutboundChannel instance for which ThreadPool candidates are listed. (ObjectName, required)

Required parameters

None.

Optional parameters: None.

Sample output

The command returns a list of eligible thread pool object names.

Examples

Batch mode example usage:

Interactive mode example usage:


updateAppOnCluster

Used to synchronize nodes and restart cluster members for an application update that is deployed to a cluster. After an application update, this command can be used to synchronize the nodes without stopping all the cluster members on all the nodes at one time. This command synchronizes one node at a time. Each node is synchronized by stopping the cluster members on which the application is targeted, performing a node synchronization operation, and restarting the cluster members.

This command might take more time than the default connector timeout period, depending on the number of nodes that the target cluster spans. Be sure to set proper timeout values in the soap.client.props file in the profile_root/properties directory, when a SOAP connector is used; in the sas.client.props file, when a JSR160RMI connector or an RMI connector is used; and in the ipc.client.props file when an IPC connector is used.

This command is not supported in local mode.

Target object: None.

Required parameters

Optional parameters:

Sample output

The command does not return output.

Examples

Batch mode example usage:

Interactive mode example usage:


  • wsadmin AdminTask