Run an administrative command using the wsadmin tool.
You can start the scripting client without having a server running by using...
-conntype NONE
AdminTask commands are available in both connected and local modes. If a server is currently running, IBM recommends not running 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, you 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, you 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. Do not run a scripting client in local mode on a node machine.
NodeGroupCommands group
The addNodeGroupMember command adds a member to a node group. Nodes can be members of more than one node group. The command does validity checking to ensure the following:
The target object is the node group where the member will be created. This target object is required.
Batch mode example usage:
$AdminTask addNodeGroupMember WBINodeGroup {-nodeName WBINode}
AdminTask.addNodeGroupMember('WBINodeGroup', '[-nodeName WBINode]')
Interactive mode example usage:
$AdminTask addNodeGroupMember {-interactive}
AdminTask.addNodeGroupMember ('[-interactive]')
SIBWebServices group
Adds the configuration for an inbound port to an inbound service. This command fails if:
The object name of the inbound service to which the port will be added.
Batch mode example usage:
set inPort [$AdminTask addSIBWSInboundPort $inService {-name "MyServiceSoap" -endpointListener "SOAPHTTP1" -node "MyNode" -server "server1"}]
inPort = AdminTask.addSIBWSInboundPort(inService, '[-name MyServiceSoap -endpointListener SOAPHTTP1 -node MyNode -server server1]')
Interactive mode example usage:
$AdminTask addSIBWSInboundPort {-interactive}
AdminTask.addSIBWSInboundPort ('[-interactive]')
SIBWebServices group
The addSIBWSOutboundPort command adds the configuration for an outbound port to an outbound service.
The object name of the outbound service for which the port will be associated.
Batch mode example usage:
set outPort [$AdminTask addSIBWSOutboundPort $outService {-name "MyServiceSoap" -node "MyNode" -server "server"}]
outPort = AdminTask.addSIBWSOutboundPort(outService, '[-name MyServiceSoap -node MyNode -server server]')
Interactive mode example usage:
$AdminTask addSIBWSOutboundPort {-interactive}
AdminTask.addSIBWSOutboundPort ('[-interactive]')
SIBAdminCommands group
Use this command to add a server or a cluster to a SIB bus.
None
Batch mode example usage:
$AdminTask addSIBusMember {-bus busname -node nodename -server servername -description text}
AdminTask.addSIBusMember('[-bus busname -node nodename -server servername -description "text"]')
Interactive mode example usage:
WSGateway group
The addWSGWTargetService command adds a target to a gateway service. You must specify the targetService parameter or the targetDestination parameter.
Object name of the GatewayService object
Batch mode example usage:
set gwTarget [$AdminTask addWSGWTargetService $gwService {-name "AnotherTarget" -targetService "AnotherService"}]
gwTarget=AdminTask.addWSGWTargetService(gwService, '[-name AnotherTarget -targetService AnotherService]')
Interactive mode example usage:
$AdminTask addWSGWTargetService {-interactive}
AdminTask.addWSGWTargetService ('[-interactive]')
ManagedObjectMetadata group
Compares the WebSphere Application Server (WAS) version given a node that you specify and an input version.
None
Batch mode example usage:
$AdminTask compareNodeVersion {-nodeName node1 -version 5}
AdminTask.compareNodeVersion('[-nodeName node1 -version 5]')
Interactive mode example usage:
$AdminTask compareNodeVersion {-interactive}
AdminTask.compareNodeVersion ('[-interactive]')
Interactive mode example usage:
SIBWebServices group
Connects an end point listener to a bus.
Object name of the end point listener that you want to create.
Batch mode example usage:
set busConn [$AdminTask connectSIBWSEndpointListener $epl {-bus "MyBus"}]
busConn = AdminTask.connectSIBWSEndpointListener(epl, '[-bus MyBus]')
Interactive mode example usage:
$AdminTask connectSIBWSEndpointListener {-interactive}
AdminTask.connectSIBWSEndpointListener ('[-interactive]')
JCA management group
Create a Java 2 Connector (J2C) resource adapter under the scope that you specify.
J2CResourceAdapter_object_ID
Batch mode example usage:
$AdminTask copyResourceAdapter $ra [subst {-name newRA -scope $scope}]
AdminTask.copyResourceAdapter(ra, '[-name newRA -scope scope]')
Interactive mode example usage:
$AdminTask copyResourceAdapter {-interactive}
AdminTask.copyResourceAdapter ('[-interactive]')
ServerManagement group
Create a new application server.
Node name (optional)
Batch mode example usage:
$AdminTask createApplicationServer ndnode1 {-name test1 -templateName default}
AdminTask.createApplicationServer(ndnode1, '[-name test1 ]', '[-templateName default]')
Interactive mode example usage:
$AdminTask createApplicationServer {-interactive}
AdminTask.createApplicationServer ('[-interactive]')
ServerManagement group
Creates a new application server template.
None
Batch mode example usage:
$AdminTask createApplicationServerTemplate {-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template"}
AdminTask.createApplicationServerTemplate('[-templateName newTemplate -serverName server1 -nodeName ndnode1 -description "This is my new template"]')
Interactive mode example usage:
$AdminTask createApplicationServerTemplate {-interactive}
AdminTask.createApplicationServerTemplate ('[-interactive]')
ChannelFrameworkManagement group
Create a new chain of transport channels that are based on a chain template.
The instance of the transport channel service under which the new chain is created. (ObjectName, required)
Batch mode example usage:
$AdminTask createChain (cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml# TransportChannelService_1) {-template WebContainer (templates/chains|webcontainer-chains.xml#Chain_1) -name trialChain1 }
$AdminTask createChain (cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml# TransportChannelService_1) {-template WebContainer (templates/chains|webcontainer-chains.xml#Chain_1) -name trialChain1 -endPoint (cells/rohitbuildCell01/ nodes/rohitbuildCellManager01|serverindex.xml#EndPoint_3) }
AdminTask.createChain('cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml# TransportChannelService_1', '[-template "WebContainer (templates/chains|webcontainer-chains.xml#Chain_1)" -name trialChain]')
AdminTask.createChain('cells/rohitbuildCell01/nodes/rohitbuildCellManager01/ servers/dmgr|server.xml#TransportChannelService_1', '[-template "WebContainer(templates/chains|webcontainer-chains. xml#Chain_1)" -name trialChain -endPoint "(cells/ rohitbuildCell01/nodes/rohitbuildCellManager01|serverindex.xml#EndPoint_3)"]')
Interactive mode example usage:
ClusterConfigCommands
Create a new server cluster. A server cluster consists of a group of application servers that are referred to as cluster members. Optionally, a replication domain can be created for the new cluster, and an existing server can be included as the first cluster member.
None
Batch mode example usage:
$AdminTask createCluster { -clusterConfig {{cluster1 true}}}
$AdminTask createCluster { -clusterConfig {{cluster1 true}} -replicationDomain {{true}}}
$AdminTask createCluster { -clusterConfig {{cluster1 true}} -convertServer {{server1 node1 "" "" ""}}}
AdminTask.createCluster('[-clusterConfig [[cluster1 true]]]')
AdminTask.createCluster('[-clusterConfig [[cluster1 true]] -replicationDomain [[true]]]')
AdminTask.createCluster('[-clusterConfig [[cluster1 true]] -convertServer [[server1 node1 "" "" ""]]]')
Interactive mode example usage:
ClusterConfigCommands
Create a member of a server cluster. A cluster member is an application server that belongs to a cluster. If this is the first member of the cluster, specify a template to use as the model for the cluster member. The template can be either a default server template, or an existing application server
clusterObjectID - The configuration object ID of the cluster to which the new member will belong. If you do not specify the configuration ID, specify the clusterName parameter. You can obtain the object name programmatically through Java using the WAS ConfigService API or through wsadmin scripting using the AdminConfig object.
Batch mode example usage:
$AdminTask createClusterMember {-clusterName cluster1 -memberConfig {{node1 member1 "" "" true false}} -firstmember {{ serverTemplateName "" "" "" ""}}}First member creation using server and node for template:
$AdminTask createClusterMember {-clusterName cluster1 -memberConfig {{node1 member1 "" "" true false}} -firstmember {{ "" node1 server1 "" ""}}}Second member creation:
$AdminTask createClusterMember {-clusterName cluster1 -memberConfig {{node1 member2 "" "" true false}}}
AdminTask.createClusterMember('[-clusterName cluster1 -memberConfig [[node1 member1 "" "" true false]] -firstMember [[serverTemplateName "" "" "" ""]]]')First member creation using server and node for template:
AdminTask.createClusterMember('[-clusterName cluster1 -memberConfig [[node1 member1 "" "" true false]] -firstMember [["" node1 server1 "" ""]]]')Second member creation:
AdminTask.createClusterMember('[-clusterName cluster1 -memberConfig [[node1 member2 "" "" true false]]]')
Interactive mode example usage:
$AdminTask createClusterMember {-interactive}
AdminTask.createClusterMember ('[-interactive]')
CoreGroupManagement group
Create a new core group. The core group that you create contains no members.
None
Batch mode example usage:
$AdminTask createCoreGroup {-coreGroupName MyCoreGroup}
AdminTask.createCoreGroup('[-coreGroupName MyCoreGroup]')
Interactive mode example usage:
$AdminTask createCoreGroup {-interactive}
AdminTask.createCoreGroup ('[-interactive]')
CoreGroupBridgeManagement group
Create a default core group access point for the core group that you specify and adds it to the default access point group. If the default access point group does not exist, the command creates a default access point group.
Core group bridge settings object for the cell. (ObjectName, required).
Batch mode example usage:
$AdminTask createCoreGroupAccessPoint (cells/ rohitbuildCell01|coregroupbridge.xml# CoreGroupBridgeSettings_1) "-coreGroupName DefaultCoreGroup"
AdminTask.createCoreGroupAccessPoint('cells/ rohitbuildCell01|coregroupbridge.xml#CoreGroupBridgeSettings_1', '[-coreGroupName DefaultCoreGroup]')
Interactive mode example usage:
$AdminTask createCoreGroupAccessPoint {-interactive}
AdminTask.createCoreGroupAccessPoint ('[-interactive]')
Interactive mode example usage:
$AdminTask createDefaultCGAP {-interactive}
AdminTask.createDefaultCGAP ('[-interactive]')
ServerManagement group
Step: ConfigProcDef
Create a new generic server in the configuration. A generic server is a server that the WAS manages, but did not supply. The createGenericServer command provides an additional step, ConfigProcDef, that you can use to configure the parameters that are specific to generic servers.
None
Batch mode example usage:
$AdminTask createGenericServer jim667BaseNode {-name jgeneric -ConfigProcDef {{"/usr/bin/myStartCommand" "arg1 arg2" "" "" "/tmp/workingDirectory" "/tmp/stopCommand" "argy argz"}}}
AdminTask.createGenericServer(jim667BaseNode, '[-name jgeneric -ConfigProcDef [[/usr/bin/myStartCommand "arg1 arg2" "" "" /tmp/workingDirectory /tmp/StopCommand "argy argz"]]]')
Interactive mode example usage:
$AdminTask createGenericServer {-interactive}
AdminTask.createGenericServer ('[-interactive]')
Interactive mode example usage:
$AdminTask createGenericServerTemplate {-interactive}
AdminTask.createGenericServerTemplate ('[-interactive]')
JCA management group
Create a Java 2 Connector (J2C) activation specification under a J2C resource adapter and the attributes that you specify. Use the messageListenerType parameter to indicate the activation specification that is defined for the J2C resource adapter.
J2CResourceAdapter_object_ID
Batch mode example usage:
$AdminTask createJ2CActivationSpec $ra {-name J2CActSpec -jndiName eis/ActSpec1 -messageListenerType javax.jms.MessageListener }
AdminTask.createJ2CActivationSpec(ra, '[-name J2CActSpec -jndiName eis/ActSpec1 -messageListenerType javax.jms.MessageListener]')
Interactive mode example usage:
$AdminTask createJ2CActivationSpec {-interactive}
AdminTask.createJ2CActivationSpec ('[-interactive]')
JCA management group
Create an administrative object under a resource adapter with attributes that you specify. Use the administrative object interface to indicate the administrative object that is defined in the resource adapter.
J2CResourceAdapter_object_ID
Batch mode example usage:
$AdminTask createJ2CAdminObject $ra {-adminObjectInterface fvt.adapter.message.FVTMessageProvider -name J2CA01 -jndiName eis/J2CA01}
AdminTask.createJ2CAdminObject(ra, '[-adminObjectInterface fvt.adapter.message.FVTMessageProvider -name J2CA01 -jndiName eis/J2CA01]')
Interactive mode example usage:
$AdminTask createJ2CAdminObject {-interactive}
AdminTask.createJ2CAdminObject ('[-interactive]')
JCA management group
Create a Java 2 connection factory under a Java 2 resource adapter and the attributes that you specify. Use the connection factory interfaces to indicate the connection definitions that are defined for the Java 2 resource adapter.
J2CConnectionFactory object ID
Batch mode example usage:
$AdminTask createJ2CConnectionFactory $ra {-connectionFactoryInterfaces javax.sql.DataSource -name J2CCF1 -jndiName eis/J2CCF1}
AdminTask.createJ2CConnectionFactory(ra, '[-connectionFactoryInterfaces javax.sql.DataSource -name J2CCF1 -jndiName eis/J2CCF1]')
Interactive mode example usage:
$AdminTask createJ2CConnectionFactory {-interactive}
AdminTask.createJ2CConnectionFactory ('[-interactive]')
NodeGroupCommands group
The createNodeGroup command creates a new node group. A node group consists of a group of nodes that are referred to as node group members. Optionally, you can create a short name and a description for the new node group.
The node group name to be created. This target object is required.
Batch mode example usage:
Interactive mode example usage:
$AdminTask createNodeGroup {-interactive}
AdminTask.createNodeGroup ('[-interactive]')
NodeGroupCommands group
The createNodeGroupProperty command creates custom properties for a node group.
The name of the node group. This target object is required.
Batch mode example usage:
$AdminTask createNodeGroupProperty WBINodeGroup {-name Channel -value "channel1"}
AdminTask.createNodeGroupProperty('WBINodeGroup', '[-name Channel -value channel1]')
Interactive mode example usage:
$AdminTask createNodeGroupProperty {-interactive}
AdminTask.createNodeGroupProperty ('[-interactive]')
SIBAdminCommands group
Use this command to create a SIB destination.
None
Batch mode example usage:
$AdminTask createSIBDestination {-bus busname -name destname -type TopicSpace}
AdminTask.createSIBDestination('[-bus busname -name destname -type TopicSpace]')
Interactive mode example usage:
$AdminTask createSIBDestination {-interactive}
AdminTask.createSIBDestination ('[-interactive]')
SIBAdminCommands group
Use the createSIBEngine command to create a new
messaging engine for a bus member.
None
Batch mode example usage:
$AdminTask createSIBEngine {-bus busname -node nodeName -server severname}
AdminTask.createSIBEngine('[-bus busname -node nodeName -server severname]')
Interactive mode example usage:
$AdminTask createSIBEngine {-interactive}
AdminTask.createSIBEngine ('[-interactive]')
SIBJMSAdminCommands group
Use the createSIBJMSActivationSpec command to create a SIB JMS activation specification.
Scope of the SIB JMS resource adapter to which you want to add the activation specification.
Batch mode example usage:
$AdminTask createSIBJMSActivationSpec $ra {-name specname -jndiName specname}
AdminTask.createSIBJMSActivationSpec(ra, '[-name specname -jndiName specname]')
Interactive mode example usage:
$AdminTask createSIBJMSActivationSpec {-interactive}
AdminTask.createSIBJMSActivationSpec ('[-interactive]')
SIBJMSAdminCommands group
Use the createSIBJMSConnectionFactory command to create a generic, queue or topic SIB JMS connection factory.
Scope of the SIB JMS resource adapter to which you want to add the SIB JMS connection factory.
Batch mode example usage:
$AdminTask createSIBJMSConnectionFactory $ra {-name connectionfactory_name -jndiName jndi_name}
AdminTask.createSIBJMSConnectionFactory(ra, '[-name connectionfactory_name -jndiName jndi_name]')
Interactive mode example usage:
$AdminTask createSIBJMSConnectionFactory {-interactive}
AdminTask.createSIBJMSConnectionFactory ('[-interactive]')
SIBJMSAdminCommands group
Use the createSIBJMSQueue command to create a SIB JMS queue.
Scope of the SIB JMS resource adapter to which you want to add the SIB JMS queue.
Batch mode example usage:
$AdminTask createSIBJMSQueue $ra {-name queue_name -jndiName jndi_name -queueName queue_name}
AdminTask.createSIBJMSQueue(ra, '[-name queue_name -jndiName jndi_name -queueName queue_name]')
Interactive mode example usage:
$AdminTask createSIBJMSQueue {-interactive}
AdminTask.createSIBJMSQueue ('[-interactive]')
SIBJMSAdminCommands group
Use this command to create a SIB JMS topic.
Scope of the SIB JMS resource adapter to which you want to add the SIB JMS topic.
Batch mode example usage:
$AdminTask createSIBJMSTopic $ra {-name topic_name -jndiName jndi_name -topicName topic_name -topicSpace topicspace_name}
AdminTask.createSIBJMSTopic(ra, '[-name topic_name -jndiName jndi_name -topicName topic_name -topicSpace topicspace_name]')
Interactive mode example usage:
$AdminTask createSIBJMSTopic {-interactive}
AdminTask.createSIBJMSTopic ('[-interactive]')
SIBAdminCommands
Use this command to create a SIB mediation.
None
Batch mode example usage:
$AdminTask createSIBMediation {-bus bus_name -mediationName mediation_name -handlerListName handlerList_name}
AdminTask.createSIBMediation('[-bus bus_name -mediationName mediation_name -handlerListName handlerList_name]')
Interactive mode example usage:
$AdminTask createSIBMediation {-interactive}
AdminTask.createSIBMediation ('[-interactive]')
SIBWebServices group
The createSIBWSEndpointListener command creates an end point listener object with no SIBWS bus connection property objects.
Object name of the server where the end point listener will be created.
Batch mode example usage:
set epl [$AdminTask createSIBWSEndpointListener $server {-name "soaphttp1" -urlRoot "http://myserver.com/wsgwsoaphttp1" -wsdlUrlRoot "http://myserver.com/wsgwsoaphttp1"}]
epl = AdminTask.createSIBWSEndpointListener(server, '[-name soaphttp1 -urlRoot http://myserver.com/wsgwsoaphttp1 -wsdlUrlRoot http://myserver.com/wsgwsoaphttp1]')
Interactive mode example usage:
$AdminTask createSIBWSEndpointListener {-interactive}
AdminTask.createSIBWSEndpointListener ('[-interactive]')
SIBWebServices group
The createSIBWSInboundService command creates a new inbound service object that represents a protocol attachment that service requesters use. If you specify the UDDIReference option, the wsdlLocation option is assumed to be a UDDI service key in the following format, where each n is a hex digit: nnnnnnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnn.
The object name of the messaging bus within which the service will be created.
Batch mode example usage:
set inService [$AdminTask createSIBWSInboundService $bus {-name "MyService" -destination $destName -wsdlLocation "http://myserver.com/MyService.wsdl"}]
inService = AdminTask.createSIBWSInboundService(bus, '[-name MyService -destination destName -wsdlLocation http://myserver.com/MyService.wsdl]')
Interactive mode example usage:
$AdminTask createSIBWSInboundService {-interactive}
AdminTask.createSIBWSInboundService ('[-interactive]')
SIBWebServices group
The createSIBWSOutboundService command creates a new outbound service object that represents a protocol attachment to a service provider. This command requires the identification of a single service element within a WSDL document.
The object name of the messaging bus within which the service is created.
Batch mode example usage:
set outService [$AdminTask createSIBWSOutboundService $bus {-name "MyService" -wsdlLocation "http://myserver.com/MyService.wsdl"}]
outService = AdminTask.createSIBWSOutboundService(bus, '[-name MyService -wsdlLocation http://myserver.com/MyService.wsdl]')
Interactive mode example usage:
$AdminTask createSIBWSOutboundService {-interactive}
AdminTask.createSIBWSOutboundService ('[-interactive]')
SIBAdminCommands
Use this command to create a new bus on the current node.
None
Batch mode example usage:
$AdminTask createSIBus {-bus busname -description text -secure True -mediationsAuthAlias name -protocol protocol -discardOnDelete False}
AdminTask.createSIBus('[-bus busname -description "text" -secure True -mediationsAuthAlias name -protocol protocol -discardOnDelete False]')
Interactive mode example usage:
None
Define a server type.
None
Batch mode example usage:
$AdminTask createServerType {-version version -serverType serverType -createTemplateCommand name -createCommand name}
AdminTask.createServerType('[-version version -serverType serverType -createTemplateCommand name -createCommand name]')
Interactive mode example usage:
$AdminTask createServerType {-interactive}
AdminTask.createServerType ('[-interactive]')
None
The createTCPEndPoint command creates a new named end point that you can associate with a TCP inbound channel.
Parent instance of the TransportChannelService that contains the TCPInboundChannel. (ObjectName, required)
Batch mode example usage:
$AdminTask createTCPEndPoint (cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml#TransportChannelService_1) {-name Sample_End_Pt_Name -host rohitbuild.raleigh.ibm.com -port 8978}
AdminTask.createTCPEndPoint('cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TransportChannelService_1', '[-name Sample_End_Pt_Name -host rohitbuild.raleigh.ibm.com -port 8978]')
Interactive mode example usage:
$AdminTask createTCPEndPoint {-interactive}
AdminTask.createTCPEndPoint ('[-interactive]')
UnmanagedNodeCommands group
Use the createUnmanagedNode command to create a new unmanaged node in the configuration. An unmanaged node is a node that does not have a node agent or a deployment manager. Unmanaged nodes can contain Web servers, such as IBM HTTP Server.
None
Batch mode example usage:
$AdminTask createUnmanagedNode {-nodeName myNode -hostName myHost -nodeOperatingSystem linux}
AdminTask.createUnmanagedNode('[-nodeName jjNode -hostName jjHost -nodeOperatingSystem linux]')
Interactive mode example usage:
$AdminTask createUnmanagedNode {-interactive}
AdminTask.createUnmanagedNode ('[-interactive]')
WSGateway group
The createWSGWGatewayService command creates a new GatewayService with associated InboundService and TargetService objects. Configuration of the InboundPort and OutboundService/Port that is associated with these objects is done using separate commands.
ObjectName of the gateway instance which the gateway service is created
Batch mode example usage:
set gwService [$AdminTask createWSGWGatewayService $wsgw {-name MyGatewayService -targetService MyService}]
gwService = AdminTask.createWSGWGatewayService(wsgw, '[-name MyGatewayService -targetService MyService]')
Interactive mode example usage:
$AdminTask createWSGWGatewayService {-interactive}
$AdminTask createWSGWGatewayService ('[-interactive]')
WSGateway group
The createWSGWProxyService command creates a new proxy service with an associated inbound service and a target service object with an associated outbound service. Configuration of the inbound port objects that are associated with the inbound service is done using separate commands.
The object name of the gateway instance within which the proxy service is created.
Batch mode example usage:
set proxyService [$AdminTask createWSGWProxyService $wsgw {-name MyProxyService -node MyNode -server server1}]
proxyService = AdminTask.createWSGWProxyService(wsgw, '[-name MyProxyService -node MyNode -server server1]')
Interactive mode example usage:
$AdminTask createWSGWProxyService {-interactive}
AdminTask.createWSGWProxyService ('[-interactive]')
ServerManagement group
Use the createWebServer command to create a Web server definition. This command is a two-step process. The first step creates a Web server definition using a template. The parameters of the second step configure the Web server definition properties. Web server definitions generate and propagate the plugin-config.xml file for each Web server. For IBM HTTP Server only, you can use the Web server definitions allow you to administer and configure IBM HTTP Server Web servers using the administrative console. These functions include: Start, Stop, View logs, View and Edit configuration files.
None
Parameters for IBM HTTP Server administration server running with an unmanaged or remote Web server (installed on machine different from WAS)
Batch mode example usage:
$AdminTask createWebServer {-name web1 -serverConfig {{webPort WebserverInstallRoot PluginInstallRoot Configuration_file_name Windows_Server_Name errorLogPath accessLogPath WebProtocol}} -remoteServerConfig {{AdminPort UserID Password AdminProtocol}}
AdminTask.createWebServer('[-name web1 -serverConfig [[webPort WebserverInstallRoot PluginInstallRoot Configuration_file_name Windows_Server_Name errorLogPath accessLogPath WebProtocol]] -remoteServerConfig [[AdminPort UserID Password AdminProtocol]]]')where -serverConfig is second step of the command.
where -remoteServerConfig is 3rd step of the command These parameters are only necessary if the IBM HTTP Server Web server is installed on a machine remote from WebSphere.
Interactive mode example usage:
ChannelFrameworkManagement group
The deleteChain command deletes an existing chain and, optionally, the transport channels in the chain.
The chain to be deleted. (ObjectName,required)
Batch mode example usage:
$AdminTask deleteChain trialChain1(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#Chain_1093554462922)
$AdminTask deleteChain trialChain(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#Chain_1093554378078) {-deleteChannels true}
AdminTask.deleteChain('trialChain1(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TransportChannelService_1)')
AdminTask.deleteChain('trialChain1(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TransportChannelService_1)', '[-deleteChannels true]')
Interactive mode example usage:
ClusterConfigCommands
The deleteCluster command deletes the configuration of a server cluster. A server cluster consists of a group of application servers that are referred to as cluster members. When a server cluster is deleted, all of its members are deleted.
Delete the configuration of an individual cluster member.
clusterObjectID - The configuration object ID of the cluster to be deleted. If the cluster's object ID is not specified, then the clusterName parameter must be specified. The object name can be obtained programmatically through Java using the WebSphere ConfigService API, or through wsadmin scripting using the AdminConfig object.
Batch mode example usage:
$AdminTask deleteCluster { -clusterName cluster1 }
$AdminTask deleteCluster { -clusterName cluster1 -replicationDomain {{true}}}
AdminTask.deleteCluster('[-clusterName cluster1]')
AdminTask.deleteCluster('[-clusterName cluster1 -replicationDomain [[true]]]')
Interactive mode example usage:
ClusterConfigCommands
The deleteClusterMember command deletes the configuration of a cluster member. A cluster member is an application server that belongs to a server cluster.
Delete the configuration of a cluster.
memberObjectID - The configuration object ID of the cluster member to be deleted. If this is not specified, then the clusterName, memberNode and memberName parameters must be specified. The object name can be obtained programmatically via Java using the WebSphere ConfigService API, or via wsadmin scripting using the AdminConfig command.
Batch mode example usage:
$AdminTask deleteClusterMember {-clusterName cluster1 -memberNode node1 -memberName member1}
$AdminTask deleteClusterMember {-clusterName cluster1 -memberNode node1 -memberName member2 -replicationEntry {{true}}}
AdminTask.deleteClusterMember('[-clusterName cluster1 -memberNode node1 -memberName member1]')
AdminTask.deleteClusterMember('[-clusterName cluster1 -memberNode node1 -memberName member2 -replicationEntry [[true]]]')
Interactive mode example usage:
$AdminTask deleteClusterMember -interactive
AdminTask.deleteClusterMember ('[-interactive]')
CoreGroupManagement group
The deleteCoreGroup command deletes an existing core group. The core group that you specify must not contain any members. You cannot delete the default core group.
None
Batch mode example usage:
$AdminTask deleteCoreGroup {-coreGroupName MyCoreGroup}
AdminTask.deleteCoreGroup('[-coreGroupName MyCoreGroup]')
Interactive mode example usage:
$AdminTask deleteCoreGroup {-interactive}
AdminTask.deleteCoreGroup ('[-interactive]')
CoreGroupBridgeManagement group
The deleteCoreGroupAccessPoints command deletes all the core group access points that are associated with a group that you specify.
Core group bridge settings object for the cell. (ObjectName, required)
Batch mode example usage:
$AdminTask deleteCoreGroupAccessPoints (cells/ rohitbuildCell01|coregroupbridge.xml# CoreGroupBridgeSettings_1) "-coreGroupName DefaultCoreGroup"
AdminTask.deleteCoreGroupAccessPoints('(cells/rohitbuildCell01|coregroupbridge.xml#CoreGroupBridgeSettings_1)', '[-coreGroupName DefaultCoreGroup]')
Interactive mode example usage:
$AdminTask deleteCoreGroupAccessPoints {-interactive}
AdminTask.deleteCoreGroupAccessPoints ('[-interactive]')
SIBAdminCommands
Use the deleteSIBDestination command to delete a bus destination. This command deletes the named destination of the named bus and deletes all related message points.
None
Batch mode example usage:
$AdminTask deleteSIBDestination {-bus busname -name destname}
AdminTask.deleteSIBDestination('[-bus busname -name destname]')
Interactive mode example usage:
$AdminTask deleteSIBDestination {-interactive}
AdminTask.deleteSIBDestination ('[-interactive]')
SIBAdminCommands
Use the deleteSIBEngine command to delete the default or named bus messaging engine from the named SIB bus. A server can have one messaging engine only. When you use this command to delete a messaging engine from a server, the engine name is not required. A cluster can have more than one messaging engine so the name of the engine must be supplied.
None
Batch mode example usage:
$AdminTask deleteSIBEngine {-bus busname -node nodeName -server severname}
AdminTask.deleteSIBEngine('[-bus busname -node nodeName -server severname]')
Interactive mode example usage:
$AdminTask deleteSIBEngine {-interactive}
AdminTask.deleteSIBEngine ('[-interactive]')
SIBJMSAdminCommands
Use the deleteSIBJMSActivationSpec command to delete an activation specification.
None
Batch mode example usage:
$AdminTask deleteSIBJMSActivationSpec {-name specname}
AdminTask.deleteSIBJMSActivationSpec('[-name specname]')
Interactive mode example usage:
$AdminTask deleteSIBJMSActivationSpec {-interactive}
AdminTask.deleteSIBJMSActivationSpec ('[-interactive]')
SIBJMSAdminCommands
Use the deleteSIBJMSConnectionFactory command to delete SIB JMS connection factories.
None
Batch mode example usage:
$AdminTask deleteSIBJMSConnectionFactory {-name factory_name}
AdminTask.deleteSIBJMSConnectionFactory('[-name factory_name]')
Interactive mode example usage:
$AdminTask deleteSIBJMSConnectionFactory {-interactive}
AdminTask.deleteSIBJMSConnectionFactory ('[-interactive]')
SIBJMSAdminCommands
Use the deleteSIBJMSQueue command to delete a JMS queue.
None
Batch mode example usage:
$AdminTask deleteSIBJMSQueue {-name queue_name}
AdminTask.deleteSIBJMSQueue('[-name queue_name]')
Interactive mode example usage:
$AdminTask deleteSIBJMSQueue {-interactive}
AdminTask.deleteSIBJMSQueue ('[-interactive]')
SIBJMSAdminCommands
Use the deleteSIBJMSTopic command to delete a JMS topic.
None
Batch mode example usage:
$AdminTask deleteSIBJMSTopic {-name topic_name}
AdminTask.deleteSIBJMSTopic('[-name topic_name]')
Interactive mode example usage:
$AdminTask deleteSIBJMSTopic {-interactive}
AdminTask.deleteSIBJMSTopic ('[-interactive]')
SIBAdminCommands
Use this command to delete the named mediation from the named bus.
None
Batch mode example usage:
Interactive mode example usage:
$AdminTask deleteSIBMediation {-interactive}
AdminTask.deleteSIBMediation ('[-interactive]')
SIBWebServices group
The deleteSIBWSEndpointListener command deletes the configuration of a an end point listener. This command fails if inbound port objects are associated with the end point listener.
Object name of the end point listener that you want to delete.
Batch mode example usage:
$AdminTask deleteSIBWSEndpointListener $epl
AdminTask.deleteSIBWSEndpointListener(epl)
Interactive mode example usage:
$AdminTask deleteSIBWSEndpointListener {-interactive}
AdminTask.deleteSIBWSEndpointListener ('[-interactive]')
SIBWebServices group
The deleteSIBWSInboundService command deletes an inbound service object and any associated inbound port objects.
The object name of the inbound service object that you want to delete.
Batch mode example usage:
$AdminTask deleteSIBWSInboundService $inService
AdminTask.deleteSIBWSInboundService(inService)
Interactive mode example usage:
$AdminTask deleteSIBWSInboundService {-interactive}
AdminTask.deleteSIBWSInboundService ('[-interactive]')
SIBWebServices group
The deleteSIBWSOutboundService command deletes an outbound service object and any associated outbound port objects. Resources that are associated with the outbound service or outbound ports, for example, WS-Security configuration, are disassociated from the outbound service but the outbound ports are not deleted.
Object name of the outbound service object that you want to delete.
Batch mode example usage:
$AdminTask deleteSIBWSOutboundService $outService
AdminTask.deleteSIBWSOutboundService(outService)
Interactive mode example usage:
$AdminTask deleteSIBWSOutboundService {-interactive}
AdminTask.deleteSIBWSOutboundService ('[-interactive]')
SIBAdminCommands
The deleteSIBus command deletes the named SIB bus, all SIB mediations and all SIB destinations that are owned by the bus.
None
Batch mode example usage:
Interactive mode example usage:
ServerManagement group
Delete a server.
None
Batch mode example usage:
$AdminTask deleteServer {-serverName server_name -nodeName node}
AdminTask.deleteServer('[-serverName server_name -nodeName node]')
Interactive mode example usage:
ServerManagement
Delete a server template. You cannot delete templates that are defined by the system. You can only delete server templates that you created. This command deletes the directory that hosts the server template.
The name of the template to delete. (ObjectName, required)
Batch mode example usage:
$AdminTask deleteServerTemplate template_name(templates/serverTypes/APPLICATION_SERVER/servers/newTemplate|server.xml#Server_1105015708079)
AdminTask.deleteServerTemplate(template_name(templates/serverTypes/APPLICATION_SERVER/servers/newTemplate|server.xml#Server_1105015708079))
Interactive mode example usage:
$AdminTask deleteServerTemplate {-interactive}
AdminTask.deleteServerTemplate ('[-interactive]')
WSGateway group
The deleteWSGWGatewayService command deletes a gateway service. It deletes the gateway destination, the corresponding reply destination, the inbound service, the inbound port enablement objects, and all of the associated target service objects. This command does not delete the destinations that are associated with the target services.
Object name of the gateway service object
Batch mode example usage:
$AdminTask deleteWSGWGatewayService $gwService
AdminTask.deleteWSGWGatewayService(gwService)
Interactive mode example usage:
$AdminTask deleteWSGWGatewayService {-interactive}
AdminTask.deleteWSGWGatewayService ('[-interactive]')
WSGateway group
The deleteWSGWProxyService command deletes a proxy service that includes the proxy destinations, outbound service, outbound ports, inbound service, and inbound port enablement objects.
Object name of the ProxyService object
Batch mode example usage:
$AdminTask deleteWSGWProxyService $proxyService
AdminTask.deleteWSGWProxyService(proxyService)
Interactive mode example usage:
$AdminTask deleteWSGWProxyService {-interactive}
AdminTask.deleteWSGWProxyService ('[-interactive]')
SIBWebServices group
The disconnectSIBWSEndpointListener command disconnects an end point listener from a bus.
Object name of the end point listener to be disconnected.
Batch mode example usage:
$AdminTask disconnectSIBWSEndpointListener $epl {-bus "MyBus"}
AdminTask.disconnectSIBWSEndpointListener(epl,'[-bus MyBus]')
Interactive mode example usage:
$AdminTask disconnectSIBWSEndpointListener {-interactive}
AdminTask.disconnectSIBWSEndpointListener ('[-interactive]')
CoreGroupManagement group
The doesCoreGroupExist command returns a boolean value that indicates if the core group that you specify exists.
None
Batch mode example usage:
$AdminTask doesCoreGroupExist {-coreGroupName MyCoreGroup}
AdminTask.doesCoreGroupExist('[-coreGroupName MyCoreGroup]')
Interactive mode example usage:
$AdminTask doesCoreGroupExist {-interactive}
AdminTask.doesCoreGroupExist ('[-interactive]')
Configuration archiveOperations group
Export the server configuration to a node that is defined in the configuration archive.
The exportServer command virtualizes the server configuration and exports a server to a configuration archive. This process breaks any existing associations between the server configurations in the configuration archive and the configurations in the system. This process also removes applications from the server that you specify, breaks the relationship between the server that you specify and the core group of the server, cluster, or SIBus membership. The exportServer command exports the metadata file of the node where the server resides. You can use this information later when you import the configuration archive to verify that the target node is compatible to the node from which you are exporting the server.
None
Batch mode example usage:
$AdminTask exportServer {-archive c:\myServer.ear -nodeName node1 -serverName server1}
AdminTask.exportServer('[-archive c:\myServer.ear -nodeName node1 -serverName server1]')
Interactive mode example usage:
configuration archiveOperations group
Use the exportWasprofile command to export the entire cell configuration to a configuration archive.
None
Batch mode example usage:
$AdminTask exportWasprofile {-archive c:\myCell.ear}
AdminTask.exportWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
$AdminTask exportWasprofile {-interactive}
AdminTask.exportWasprofile ('[-interactive]')
CoreGroupManagement group
The getAllCoreGroupNames command returns a string that contains the names of all of the existing core groups
None
Batch mode example usage:
Interactive mode example usage:
$AdminTask getAllCoreGroupNames {-interactive}
AdminTask.getAllCoreGroupNames ('[-interactive]')
CoreGroupManagement group
The getCoreGroupNameForServer command returns the name of the core group in which the server that you specify is currently a member.
None
Batch mode example usage:
$AdminTask getCoreGroupNameForServer {-nodeName myNode -serverName myServer}
AdminTask.getCoreGroupNameForServer('[-nodeName myNode -serverName myServer]')
Interactive mode example usage:
$AdminTask getCoreGroupNameForServer {-interactive}
AdminTask.getCoreGroupNameForServer ('[-interactive]')
CoreGroupManagement group
The getDefaultCoreGroupName command returns the name of the default core group.
None
Batch mode example usage:
Interactive mode example usage:
$AdminTask getDefaultCoreGroupName {-interactive}
AdminTask.getDefaultCoreGroupName ('[-interactive]')
ManagedObjectMetadata group
The getMetadataProperties command obtains all metadata for the node that you specify.
None
Batch mode example usage:
$AdminTask getMetadataProperties {-nodeName node1}
AdminTask.getMetadataProperties('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getMetadataProperties {-interactive}
AdminTask.getMetadataProperties ('[-interactive]')
ManagedObjectMetadata group
The getMetadataProperty command obtains metadata with the specified key for the node that you specify.
None
Batch mode example usage:
$AdminTask getMetadataProperty {-nodeName node1 -propertyName com.ibm.websphere.baseProductVersion}
AdminTask.getMetadataProperty ('[-nodeName node1 -propertyName com.ibm.websphere.baseProductVersion]')
Interactive mode example usage:
$AdminTask getMetadataProperty {-interactive}
AdminTask.getMetadataProperty ('[-interactive]')
CoreGroupBridgeManagement group
The getNamedTCPEndPoint command returns the port associated with the bridge interface that you specify. The port that is returned is the one that is specified on the TCP inbound channel of the transport channel chain for bridge interface that you specify.
The bridge interface object for which the port will be listed. (ObjectName, required)
Batch mode example usage:
$AdminTask getNamedTCPEndPoint (cells/rohitbuildCell01| coregroupbridge.xml#BridgeInterface_2)
AdminTask.getNamedTCPEndPoint('(cells/rohitbuildCell01|coregroupbridge.xml#BridgeInterface_2)')
Interactive mode example usage:
$AdminTask getNamedTCPEndPoint {-interactive}
AdminTask.getNamedTCPEndPoint ('[-interactive]')
ManagedObjectMetadata group
The getNodeBaseProductVersion command returns the version of the WAS for a node that you specify. This command only returns the version for a distributed installation of the product.
None
Batch mode example usage:
$AdminTask getNodeBaseProductVersion {-nodeName node1}
AdminTask.getNodeBaseProductVersion('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getNodeBaseProductVersion {-interactive}
AdminTask.getNodeBaseProductVersion ('[-interactive]')
ManagedObjectMetadata group
The getNodeMajorVersion command returns the major version of the WAS for a node that you specify. This command returns the version for a distributed installation of the product only.
None
Batch mode example usage:
$AdminTask getNodeMajorVersion {-nodeName node1}
AdminTask.getNodeMajorVersion('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getNodeMajorVersion {-interactive}
AdminTask.getNodeMajorVersion ('[-interactive]')
ManagedObjectMetadata group
The getNodeMinorVersion command returns the minor version of the WAS for a node that you specify. This command only returns the version for a distributed installation of the product only.
None
Batch mode example usage:
$AdminTask getNodeMinorVersion {-nodeName node1}
AdminTask.getNodeMinorVersion('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getNodeMinorVersion {-interactive}
AdminTask.getNodeMinorVersion ('[-interactive]')
ManagedObjectMetadata group
The getNodePlatformOS command returns the operating system name for a node that you specify.
None
Batch mode example usage:
$AdminTask getNodePlatformOS {-nodeName node1}
AdminTask.getNodePlatformOS('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getNodePlatformOS {-interactive}
AdminTask.getNodePlatformOS ('[-interactive]')
ManagedObjectMetadata group
The getNodeSysplexName command returns the sysplex name for a node that you specify.
None
Batch mode example usage:
$AdminTask getNodeSysplexName {-nodeName node1}
AdminTask.getNodeSysplexName('[-nodeName node1]')
Interactive mode example usage:
$AdminTask getNodeSysplexName {-interactive}
AdminTask.getNodeSysplexName ('[-interactive]')
ServerManagement group
The getServerType command returns the type of the server that you specify.
None
Batch mode example usage:
$AdminTask getServerType {-serverName test2 -nodeName ndnode1}
AdminTask.getServerType('[-serverName test2 -nodeName ndnode1]')
Interactive mode example usage:
None
The getTCPEndPoint command obtains the named end point that is associated with either a TCP inbound channel or a chain that contains a TCP inbound channel.
TCPInboundChannel, or containing chain, instance that is associated with a NamedEndPoint. (ObjectName, required)
Batch mode example usage:
$AdminTask getTCPEndPoint TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TCPInboundChannel_1)
$AdminTask getTCPEndPoint DCS(cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml#Chain_3)
AdminTask.getTCPEndPoint('TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TCPInboundChannel_1)')
AdminTask.getTCPEndPoint('DCS(cells/rohitbuildCell01/nodes/ rohitbuildCellManager01/servers/dmgr|server.xml#Chain_3)')
Interactive mode example usage:
Configuration archiveOperations group
Import a server that resides in a configuration archive to the system. This command imports all the server scope configurations defined in the configuration archive to system configuration.
None
Batch mode example usage:
$AdminTask importServer {-archive c:\myServer.ear -nodeInArchive node1 -serverInArchive server1}
AdminTask.importServer('[-archive c:\myServer.ear -nodeInArchive node1 -serverInArchive server1]')
Interactive mode example usage:
None
The help command provides a summary of the help commands and ways to invoke an administrative command.
None
None
The help command provides a list of available administrative commands if the option string is -commands or administrative command groups if the option string is -commandGroups. Valid options include -commands and -commandGroups.
None
None
If you provide the step name, this command provides help information for a given step of an administrative command. Otherwise, it provides help information for a given admin command or administrative command group. The stepName parameter is optional.
None
$AdminTask help createJ2CConnectionFactory
AdminTask.help('createJ2CConnectionFactory')
configuration archiveOperations group
Use the importWasprofile command to import a cell configuration in the configuration archive to the system. Only a base single server configuration is supported for this command.
None
Batch mode example usage:
$AdminTask importWasprofile {-archive c:\myCell.ear}
AdminTask.importWasprofile('[-archive c:\myCell.ear]')
Interactive mode example usage:
$AdminTask importWasprofile {-interactive}
AdminTask.importWasprofile ('[-interactive]')
MangedObjectMetadata group
The isNodeZOS command tests if a node that you specify is running on the z/OS platform. This command does not apply to distributed platforms or to WAS-Express.
None
Batch mode example usage:
Interactive mode example usage:
JCA management group
List the administrative object interfaces that are defined under the resource adapter that you specify.
J2CResouce adapter object ID
Batch mode example usage:
ChannelFrameworkManagement group
The listChainTemplates command displays a list of templates that you can use to create chains in this configuration. All templates have a certain type of transport channel as the last transport channel in the chain.
None
Batch mode example usage:
$AdminTask listChainTemplates {}
$AdminTask listChainTemplates "-acceptorFilter WebContainerInboundChannel"
AdminTask.listChainTemplates()
AdminTask.listChainTemplates('[-acceptorFilter WebContainerInboundChannel]')
Interactive mode example usage:
$AdminTask listChainTemplates {-interactive}
AdminTask.listChainTemplates ('[-interactive]')
ChannelFrameworkManagement group
The listChains command lists all the chains that are configured under a particular instance of the transport channel service.
The instance of the transport channel service under which the the chains are configured. (ObjectName, required)
Batch mode example usage:
$AdminTask listChains (cells/rohitbuildCell01/nodes/ rohitbuildNode01/servers/server2|server.xml# TransportChannelService_1093445762328)
$AdminTask listChains (cells/rohitbuildCell01/nodes/ rohitbuildNode01/servers/server2|server.xml# TransportChannelService_1093445762328) {-acceptorFilter WebContainerInboundChannel}
$AdminTask listChains (cells/rohitbuildCell01/nodes/ rohitbuildNode01/servers/server2|server.xml# TransportChannelService_1093445762328) {-endPointFilter WC_adminhost}
AdminTask.listChains('(cells/rohitbuildCell01/nodes/rohitbuildNode01/servers/server2|server.xml#TransportChannelService_1093445762328)')
AdminTask.listChains('(cells/rohitbuildCell01/nodes/rohitbuildNode01/servers/server2|server.xml#TransportChannelService_1093445762328)', '[-acceptorFilter WebContainerInboundChannel]')
AdminTask.listChains('(cells/rohitbuildCell01/nodes/rohitbuildNode01/servers/server2|server.xml#TransportChannelService_1093445762328)', '[-endPointFilter WC_adminhost]')
Interactive mode example usage:
JCA management group
List all of the connection factory interfaces that are defined under the Java 2 connector resource adapter that you specify.
J2CResourceAdapter object ID
Batch mode example usage:
$AdminTask listConnectionFactoryInterfaces $ra
AdminTask.listConnectionFactoryInterfaces(ra)
CoreGroupBridgeManagement group
The listCoreGroups command returns a collection of core groups that are related to the core group that you specify.
The name of the core group for which the related core groups will be listed. (String, required)
Batch mode example usage:
$AdminTask listCoreGroups DefaultCoreGroup "-cgBridgeSettings (cells/rohitbuildCell01|coregroupbridge.xml# CoreGroupBridgeSettings_1)"
AdminTask.listCoreGroups('DefaultCoreGroup', '[-cgBridgeSetting (cells/rohitbuildCell01|coregroupbridge.xml#CoreGroupBridgeSettings_1)]')
Interactive mode example usage:
CoreGroupBridgeManagement group
The listEligibleBridgeInterfaces command returns a collection of node, server, and transport channel chain combinations that are eligible to become bridge interfaces for the specified core group access point.
The core group access point object for which bridge interfaces will be listed. (ObjectName, required)
Batch mode example usage:
$AdminTask listEligibleBridgeInterfaces CGAP_DCG_2 (cells/rohitbuildCell01|coregroupbridge.xml# CoreGroupAccessPoint_1089636614062)
AdminTask.listEligibleBridgeInterfaces('CGAP_DCG_2(cells/rohitbuildCell01|coregroupbridge.xml# CoreGroupAccessPoint_1089636614062)')
Interactive mode example usage:
$AdminTask listEligibleBridgeInterfaces {-interactive}
AdminTask.listEligibleBridgeInterfaces ('[-interactive]')
JCA management group
List the activation specifications that are contained under the resource adapter and message listener type that you specify.
J2CResourceAdapter object ID
Batch mode example usage:
$AdminTask listJ2CActivationSpecs $ra {-messageListenerType javax.jms.MessageListener}
AdminTask.listJ2CActivationSpecs(ra, '[-messageListenerType javax.jms.MessageListener]')
JCA Management group
List administrative objects that contain the administrative object interface that you specify.
J2C ResourceAdapter object ID
Batch mode example usage:
$AdminTask listJ2CAdminObjects $ra {-adminObjectInterface fvt.adaptor.message.FVTMessageProvider}
AdminTask.listJ2CAdminObjects(ra, '[-adminObjectInterface fvt.adaptor.message.FVTMessageProvider]')
JCA management group
List the Java 2 connector connection factories under the resource adapter and connection factory interface that you specify.
J2C ResourceAdapter object ID
Batch mode example usage:
$AdminTask listJ2CConnectionFactories $ra {-connectionFactoryInterface javax.sql.DataSource}
AdminTask.listJ2CConnectionFactories(ra, '[-connectionFactoryInterface javax.sql.DataSource]')
UnmanagedNodeCommands group
Use the listManagedNodes command to list the managed nodes, nodes that have a node agent defined, in a configuration.
None
Batch mode example usage:
JCA Management group
List the message listener types that are defined under the resource adapter that you specify.
J2C ResourceAdapter object ID
Batch mode example usage:
NodeGroupCommands group
The listNodeGroupProperties command displays all of the custom properties of a node group.
The target object is name of the node group. This target object is required.
Batch mode example usage:
$AdminTask listNodeGroupProperties WBINodeGroup
AdminTask.listNodeGroupProperties('WBINodeGroup')
Interactive mode example usage:
$AdminTask listNodeGroupProperties {-interactive}
AdminTask.listNodeGroupProperties ('[-interactive]')
NodeGroupCommands group
The listNodeGroups command returns the list of node groups from the configuration repository. You can pass an optional node name to the command that returns the list of node groups where the node resides.
The target object is name of the node. This target object is optional.
Batch mode example usage:
$AdminTask listNodeGroups $AdminTask listNodeGroups nodeName
AdminTask.listNodeGroups AdminTask.listNodeGroups('nodeName')
Interactive mode example usage:
NodeGroupCommands group
The listNodes command displays all of the nodes in the cell.
The target object is name of the node group. This target object is optional.
Batch mode example usage:
Interactive mode example usage:
SIBAdminCommands
Use the listSIBDestinations command to get a list of SIB destinations of the named type that is owned by a named SIB bus. If no type is named, all the destinations that are owned by the named bus are listed.
None
Batch mode example usage:
$AdminTask listSIBDestinations {-bus busname -name destname -type Queue}
AdminTask.listSIBDestinations('[-bus busname -name destname -type Queue]')
Interactive mode example usage:
$AdminTask listSIBDestinations {-interactive}
AdminTask.listSIBDestinations ('[-interactive]')
SIBAdminCommands
Use the listSIBEngines command to get a list of bus messaging engines. Supplying only the bus parameter will results in a list of all the engines that are associated with the named bus. Supplying only the node and server parameters results in a list of all the engines owned by the named node and server. Supplying only the cluster parameter results in a list of all the engines that are owned by the named cluster. All other parameter combinations are illegal.
None
Batch mode example usage:
$AdminTask listSIBEngines {-bus busname -node nodeName -server severname}
AdminTask.listSIBEngines('[-bus busname -node nodeName -server severname]')
Interactive mode example usage:
SIBJMSAdminCommands
Interactive mode example usage:
$AdminTask listSIBJMSActivationSpecs {-interactive}
AdminTask.listSIBJMSActivationSpecs ('[-interactive]')
SIBJMSAdminCommands
Use the listSIBJMSConnectionFactories command to list all of the JMS connection factories for the default messaging provider at the scope that you specify.
None
If you do no specify the type option, this command will return only the unified JMS connection factories at the scope that you specified.
Batch mode example usage:
$AdminTask listSIBJMSConnectionFactories {-type queue}
AdminTask.listSIBJMSConnectionFactories('[-type queue]')
Interactive mode example usage:
$AdminTask listSIBJMSConnectionFactories {-interactive}
AdminTask.listSIBJMSConnectionFactories ('[-interactive]')
SIBJMSAdminCommands
Use the listSIBJMSQueues command to list all the JMS queues for the default messaging provider at the specified scope.
None
Batch mode example usage:
SIBJMSAdminCommands
The listSIBJMSTopics command lists all the JMS topics for the default messaging provider at the specified scope.
None
Batch mode example usage:
SIBAdminCommands
The listSIBMediations command lists the mediations on a named SIB bus.
None
Batch mode example usage:
$AdminTask listSIBMediations {-bus bus_name}
AdminTask.listSIBMediations('[-bus bus_name]')
Interactive mode example usage:
$AdminTask listSIBMediations {-interactive}
AdminTask.listSIBMediations ('[-interactive]')
SIBAdminCommands
The listSIBusMember command lists all of the servers and the clusters that are members of the named SIB bus.
None
Batch mode example usage:
$AdminTask listSIBusMembers {-bus bus_name}
AdminTask.listSIBusMembers('[-bus bus_name]')
Interactive mode example usage:
$AdminTask listSIBusMembers {-interactive}
AdminTask.listSIBusMembers ('[-interactive]')
SIBAdminCommands
The listSIBuses command lists all the SIB buses in the cell.
None
Batch mode example usage:
None
The listSSLRepertoires command lists all of the
Secure Sockets Layer (SSL) configuration instances that you can associate with an SSL inbound channel.
SSLInboundChannel instance for which the SSLConfig candidates are listed.
Batch mode example usage:
$AdminTask listSSLRepertoires SSL_3(cells/rohitbuildCell01/ nodes/rohitbuildNode01/servers/server2|server.xml#SSLInbound Channel_1093445762330)
AdminTask.listSSLRepertoires('SSL_3(cells/rohitbuildCell01/nodes/rohitbuildNode01/servers/server2|server.xml#SSLInboundChannel_1093445762330)')
Interactive mode example usage:
$AdminTask listSSLRepertoires {-interactive}
AdminTask.listSSLRepertoires ('[-interactive]')
ServerManagement group
The listServers command returns a list of servers.
None
Batch mode example usage:
$AdminTask listServers {-serverType APPLICATION_SERVER -nodeName ndnode1}
AdminTask.listServers('[-serverType APPLICATION_SERVER -nodeName ndnode1]')
Interactive mode example usage:
ServerManagement group
List server templates.
None
Batch mode example usage:
$AdminTask listServerTemplates {-version 6.0.0.0 -serverType APPLICATION_SERVER}
AdminTask.listServerTemplates('[-version 6.0.0.0 -serverType APPLICATION_SERVER]')
Interactive mode example usage:
$AdminTask listServerTemplates {-interactive}
AdminTask.listServerTemplates ('[-interactive]')
ServerManagement group
Display all the current server types. For example, APPLICATION_SERVER, WEB_SERVER, GENERIC_SERVER.
The node name for which you want to list the valid types. For example, the types that are only valid on z/OS will appear on a z/OS node. (String, optional)
Batch mode example usage:
Interactive mode example usage:
$AdminTask listServerTypes {-interactive}
AdminTask.listServerTypes ('[-interactive]')
Interactive mode example usage:
$AdminTask listTAMSettings {-interactive}
AdminTask.listTAMSettings ('[-interactive]')
None
The listTCPEndPoints command lists all the named end points that can be associated with a TCP inbound channel.
TCPInboundChannel instance for which named end points candidates are listed. (ObjectName, required)
Batch mode example usage:
$AdminTask listTCPEndPoints TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml# TCPInboundChannel_1)
$AdminTask listTCPEndPoints TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml# TCPInboundChannel_1) {-excludeDistinguished}
$AdminTask listTCPEndPoints TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TCPInboundChannel_1) {-excludeDistinguished -unusedOnly}
AdminTask.listTCPEndPoints('TCP_1(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TCPInboundChannel_1)', '[-excludeDistinguished]')
AdminTask.listTCPEndPoints('TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml# TCPInboundChannel_1)', '[-excludeDistinguished]')
AdminTask.listTCPEndPoints('TCP_1(cells/rohitbuildCell01/nodes/rohitbuildCellManager01/servers/dmgr|server.xml#TCPInboundChannel_1)', '[-excludeDistinguished -unusedOnly]')
Interactive mode example usage:
$AdminTask listTCPEndPoints {-interactive}
AdminTask.listTCPEndPoints ('[-interactive]')
None
The listTCPThreadPools command lists all of the thread pools that can be associated with a TCP inbound channel or TCP outbound channel.
TCPInboundChannel or TCPOutboundChannel instance for which ThreadPool candidates are listed. (ObjectName, required)
Batch mode example usage:
$AdminTask listTCPThreadPools TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml# TCPInboundChannel_1)
AdminTask.listTCPThreadPools('TCP_1(cells/rohitbuildCell01/ nodes/rohitbuildCellManager01/servers/dmgr|server.xml# TCPInboundChannel_1)')
Interactive mode example usage:
$AdminTask listTCPThreadPools {-interactive}
AdminTask.listTCPThreadPools ('[-interactive]')
UnmanagedNodeCommands group
Use the listUnmanagedNodes command to list the unmanaged nodes in a configuration.
None
Batch mode example usage:
Interactive mode example usage:
$AdminTask listUnmanagedNodes {-interactive}
AdminTask.listUnmanagedNodes ('[-interactive]')
SIBAdminCommands
Use the mediateSIBDestination command to mediate a bus destination. The bus, destination, and mediation definitions must exist prior to using this command. The destination must not be mediated already.
None
Batch mode example usage:
$AdminTask mediateSIBDestination {-bus busname -name destname -mediationName mediationName}
AdminTask.mediateSIBDestination('[-bus busname -name destname -mediationName mediationName]')
Interactive mode example usage:
$AdminTask mediateSIBDestination {-interactive}
AdminTask.mediateSIBDestination ('[-interactive]')
NodeGroupCommands group
The modifyNodeGroup command modifies the configuration of a node group. The node group name cannot be changed. However, its short name and description are supported. Also, its node membership can be modified.
The target object is the node group name. This target object is required.
Batch mode example usage:
$AdminTask modifyNodeGroup WBINodeGroup {-shortName WBIGroup -description "Default node group"}
AdminTask.modifyNodeGroup WBINodeGroup('[-shortName WBIGroup -description "WBI" node group]')
Interactive mode example usage:
$AdminTask modifyNodeGroup {-interactive}
AdminTask.modifyNodeGroup ('[-interactive]')
NodeGroupCommands group
The modifyNodeGroupProperty command modifies custom properties for a node group
The name of the node group. This target object is required.
Batch mode example usage:
$AdminTask modifyNodeGroupProperty WBINodeGroup {-name Channel -value "channel1"}
AdminTask.modifyNodeGroupProperty('WBINodeGroup', '[-name Channel -value channel1]')
Interactive mode example usage:
$AdminTask modifyNodeGroupProperty {-interactive}
AdminTask.modifyNodeGroupProperty ('[-interactive]')
SIBAdminCommands
Use the modifySIBDestination command to modify the attributes of a SIB destination. The bus and name parameters are used to identify the SIB destination and cannot be modified.
None
Batch mode example usage:
$AdminTask modifySIBDestination {-bus busname -name destname}
AdminTask.modifySIBDestination('[-bus busname -name destname]')
Interactive mode example usage:
$AdminTask modifySIBDestination {-interactive}
AdminTask.modifySIBDestination ('[-interactive]')
SIBAdminCommands
Use the modifySIBEngine command to modify the attributes of a bus messaging engine. The bus, node, server, cluster, and engine parameters are used to identify the engine and cannot be modified. A server can have one messaging engine only. When using this command to modify a messaging engine from a server, the engine name is not required. However, because a cluster can have more than one messaging engine, the engine name must be supplied.
None
Batch mode example usage:
$AdminTask modifySIBEngine {-bus busname -node nodeName -server severname}
AdminTask.modifySIBEngine('[-bus busname -node nodeName -server severname]')
Interactive mode example usage:
$AdminTask modifySIBEngine {-interactive}
AdminTask.modifySIBEngine ('[-interactive]')
SIBJMSAdminCommands
Use the modifySIBJMSActivationSpec command to modify the properties of an activation specification.
None
Batch mode example usage:
$AdminTask modifySIBJMSActivationSpec {-name specname -propertyList propertyList}
AdminTask.modifySIBJMSActivationSpec('[-name specname -propertyList propertyList]')
Interactive mode example usage:
$AdminTask modifySIBJMSActivationSpec {-interactive}
AdminTask.modifySIBJMSActivationSpec ('[-interactive]')
SIBJMSAdminCommands
Use the modifySIBJMSConnectionFactory command to modify a unified JMS connection factory at the current scope.
None
Batch mode example usage:
$AdminTask modifySIBJMSConnectionFactory {-name factory_name -jndiName jndi_name}
AdminTask.modifySIBJMSConnectionFactory('[-name factory_name -jndiName jndi_name]')
Interactive mode example usage:
$AdminTask modifySIBJMSConnectionFactory {-interactive}
AdminTask.modifySIBJMSConnectionFactory ('[-interactive]')
SIBJMSAdminCommands
Use the modifySIBJMSQueue command to modify a unified JMS queue at the current scope.
None
Batch mode example usage:
$AdminTask modifySIBJMSQueue {-name queue_name -jndiName jndi_name -queueName queue_name}
AdminTask.modifySIBJMSQueue('[-name queue_name -jndiName jndi_name -queueName queue_name]')
Interactive mode example usage:
$AdminTask modifySIBJMSQueue {-interactive}
AdminTask.modifySIBJMSQueue ('[-interactive]')
SIBJMSAdminCommands
Use the modifySIBJMSTopic command to modify the JMS topic at the current scope.
None
Batch mode example usage:
$AdminTask modifySIBJMSTopic {-name topic_name -jndiName jndi_name -topicName topic_name -topicSpace topicspace_name}
AdminTask.modifySIBJMSTopic('[-name topic_name -jndiName jndi_name -topicName topic_name -topicSpace topicspace_name]')
Interactive mode example usage:
$AdminTask modifySIBJMSTopic {-interactive}
AdminTask.modifySIBJMSTopic ('[-interactive]')
SIBAdminCommands
Use this command to modify the attributes of a SIB mediation.The bus and mediationName parameters identify the mediation and cannot be modified.
None
Batch mode example usage:
$AdminTask modifySIBMediation {-bus bus_name -jndiName jndi_name}
AdminTask.modifySIBMediation('[-bus bus_name -mediationName mediation_name]')
Interactive mode example usage:
$AdminTask modifySIBMediation {-interactive}
AdminTask.modifySIBMediation ('[-interactive]')
SIBAdminCommands
The modifySIBus command to modifies the attributes of the named bus. The bus parameter identifies the bus to modify, and is not used to change the name of the bus.
None
Batch mode example usage:
$AdminTask modifySIBus {-bus busname -description text -secure True -mediationsAuthAlias name -protocol protocol -discardOnDelete False}
AdminTask.modifySIBus('[-busbusname -description "text" -secure True -mediationsAuthAlias name -protocol protocol -discardOnDelete False]')
Interactive mode example usage:
SIBAdminCommands
The modifySIBusMember command modifies the attributes of the bus member identified by the bus, node, server, and cluster parameters.
None
Batch mode example usage:
$AdminTask modifySIBusMember {-bus busname -node nodename -server servername -description text}
AdminTask.modifySIBusMember('[-bus busname -node nodename -server servername -description "text"]')
Interactive mode example usage:
$AdminTask modifySIBusMember {-interactive}
AdminTask.modifySIBusMember ('[-interactive]')
CoreGroupManagement group
The moveClusterToCoreGroup command moves all of the servers in a cluster that you specify from a core group to another core group. All of the servers in a cluster must be members of the same core group.
None
Batch mode example usage:
$AdminTask moveClusterToCoreGroup {-source OldCoreGroup -target NewCoreGroup -clusterName ClusterOne}
AdminTask.moveClusterToCoreGroup('[-source OldCoreGroup -target NewCoreGroup -clusterName ClusterOne]')
Interactive mode example usage:
$AdminTask moveClusterToCoreGroup {-interactive}
AdminTask.moveClusterToCoreGroup ('[-interactive]')
CoreGroupManagement group
The moveServerToCoreGroup command moves a server to a core group that you specify. When the server is added to the core group that you specify, it is removed from the core group where it originally resided.
None
Batch mode example usage:
$AdminTask moveServerToCoreGroup {-source OldCoreGroup -target NewCoreGroup -nodeName myNode -serverName myServer}
AdminTask.moveServerToCoreGroup('[-source OldCoreGroup -target NewCoreGroup -nodeName myNode -serverName myServer]')
Interactive mode example usage:
$AdminTask moveServerToCoreGroup {-interactive}
AdminTask.moveServerToCoreGroup ('[-interactive]')
SIBWebServices group
The publishSIBWSInboundService command publishes the WSDL document for the inbound service and the associated ports to the registry and the business that is defined by the UDDIPublication object.
The object name of the inbound service object.
Batch mode example usage:
$AdminTask publishSIBWSInboundService $inService {-uddiPublication "MyUddi"}
AdminTask.publishSIBWSInboundService(inService, '[-uddiPublication MyUddi]')
Interactive mode example usage:
$AdminTask publishSIBWSInboundService {-interactive}
AdminTask.publishSIBWSInboundService ('[-interactive]')
Interactive mode example usage:
SIBWebServices group
The refreshSIBWSInboundServiceWSDL command loads the WSDL document from the WSDLLocation parameters of the inbound service and locates the WSDLLocation-specified service element. If the service element is not present, this command fails. If the outbound ports are not a subset of the ports in the loaded WSDL document, this command fails.
If the WSDL is retrieved through a proxy, the server on which the command is running must have the system properties that identify the proxy server set correctly.
The object name of the inbound service object.
Batch mode example usage:
$AdminTask refreshSIBWSInboundServiceWSDL $inService
AdminTask.refreshSIBWSInboundServiceWSDL(inService)
Interactive mode example usage:
$AdminTask refreshSIBWSInboundServiceWSDL {-interactive}
AdminTask.refreshSIBWSInboundServiceWSDL ('[-interactive]')
SIBWebServices group
The refreshSIBWSOutboundServiceWSDL command loads the WSDL document from the WSDLLocation parameters of the outbound service and locates the WSDLLocation-specified service element. If the service element is not present, this command fails. If the outbound ports are not a subset of the ports in the loaded WSDL document, this command fails.
If the WSDL will be retrieved through a proxy, the server on which the command is running must have the system properties that identify the proxy server set correctly.
The object name of the outbound service object.
Batch mode example usage:
$AdminTask refreshSIBWSOutboundServiceWSDL $outService
AdminTask.refreshSIBWSOutboundServiceWSDL(outService)
Interactive mode example usage:
$AdminTask refreshSIBWSOutboundServiceWSDL {-interactive}
AdminTask.refreshSIBWSOutboundServiceWSDL ('[-interactive]')
NodeGroupCommands group
The removeNodeGroup command removes the configuration of a node group. You can remove a node group if it does not contain any members. Also, the default node group cannot be removed.
The name of the node group to be removed. This target object is required.
Batch mode example usage:
Interactive mode example usage:
$AdminTask removeNodeGroup {-interactive}
AdminTask.removeNodeGroup ('[-interactive]')
NodeGroupCommands group
The removeNodeGroupMember command removes the configuration of a node group member.
The target object is the node group containing the member to be removed. This target object is required.
Batch mode example usage:
$AdminTask removeNodeGroupMember WBINodeGroup {-nodeName WBINode}
AdminTask.removeNodeGroupMember('WBINodeGroup', '[-nodeName WBINode]')
Interactive mode example usage:
$AdminTask removeNodeGroupMember {-interactive}
AdminTask.removeNodeGroupMember ('[-interactive]')
NodeGroupCommands group
The removeNodeGroupProperty command removes custom properties of a node group.
The name of the node group. This target object is required.
Batch mode example usage:
$AdminTask removeNodeGroupProperty WBINodeGroup {-name Channel}
AdminTask.removeNodeGroupProperty('WBINodeGroup', '[-name Channel]')
Interactive mode example usage:
$AdminTask removeNodeGroupProperty {-interactive}
AdminTask.removeNodeGroupProperty ('[-interactive]')
SIBWebServices group
The removeSIBWSInboundPort command removes the configuration of an inbound port.
The object name of the inbound port object that you want to remove.
Batch mode example usage:
Interactive mode example usage:
$AdminTask removeSIBWSInboundPort {-interactive}
AdminTask.removeSIBWSInboundPort ('[-interactive]')
SIBWebServices group
The removeSIBWSOutboundPort command removes the configuration of an outbound port. If the port that you delete is the default port for the outbound service, one of the remaining ports, if any, is chosen as the new default. Resources that are associated with the outbound port, for example, WS-Security configuration, are disassociated from the outbound port, but not deleted.
The object name of the outbound port object that you want to remove.
Batch mode example usage:
$AdminTask removeSIBWSOutboundPort $outPort
AdminTask.removeSIBWSOutboundPort(outPort)
Interactive mode example usage:
$AdminTask removeSIBWSOutboundPort {-interactive}
AdminTask.removeSIBWSOutboundPort ('[-interactive]')
SIBAdminCommands
The removeSIBusMember command removes a server or a cluster from a SIB bus. This command also deletes all SIB messaging engines that are associated with the bus, all queue points and publication points that are owned by those engines, and all queue point references and publication point references that refer to the deleted queue points and publication points.
None
Batch mode example usage:
$AdminTask removeSIBusMember {-bus busname -node nodename -server servername}
AdminTask.removeSIBusMember('[-bus busname -node nodename -server servername]')
Interactive mode example usage:
$AdminTask removeSIBusMember {-interactive}
AdminTask.removeSIBusMember ('[-interactive]')
UnmanagedNodeCommands group
Use the removeUnmanagedNode command to remove an unmanaged node from the configuration.
None
Batch mode example usage:
$AdminTask removeUnmanagedNode {-nodeName myNode }
AdminTask.removeUnmanagedNode('[-nodeName myNode]')
Interactive mode example usage:
$AdminTask removeUnmanagedNode {-interactive}
AdminTask.createUnmanagedNode ('[-interactive]')
WSGateway group
The removeWSGWTargetService command removes a target service from the gateway service. The destinations that are associated with the target service are not deleted. If the target service that you remove is the default target service, the default is set to the first target service in the set or cleared if none are left.
The object name of the TargetService object.
Batch mode example usage:
$AdminTask removeWSGWTargetService $gwTarget
AdminTask.removeWSGWTargetService(gwTarget)
Interactive mode example usage:
$AdminTask removeWSGWTargetService {-interactive}
AdminTask.removeWSGWTargetService ('[-interactive]')
SIBWebServices group
The setDefaultSIBWSOutboundPort command updates the default outbound port for an outbound service.
The object name of the outbound service whose default port you want to update.
Batch mode example usage:
$AdminTask setDefaultSIBWSOutboundPort $outService {-name "MyServiceSoap"}
AdminTask.setDefaultSIBWSOutboundPort(outService, '[-name MyServiceSoap]')
Interactive mode example usage:
$AdminTask setDefaultSIBWSOutboundPort {-interactive}
AdminTask.setDefaultSIBWSOutboundPort ('[-interactive]')
SIBAdminCommands
Use the showSIBDestination command to get the attribute names and values of a SIB destination. The bus and name parameter identify the SIB destination whose attributes are required.
None
Batch mode example usage:
$AdminTask showSIBDestination {-bus busname -name destname}
AdminTask.showSIBDestination('[-bus busname -name destname]')
Interactive mode example usage:
$AdminTask showSIBDestination {-interactive}
AdminTask.showSIBDestination ('[-interactive]')
SIBAdminCommands
Use the showSIBEngine command to get the attribute names and values of a SIB messaging engine that belongs to a given bus member. If the bus member is a server, only the bus, node, and server parameters are required. A server has one engine only, so the engine parameter is not necessary. If the bus member is a cluster, the bus, cluster, and engine parameters must be supplied, because a cluster can have more than one engine.
None
Batch mode example usage:
$AdminTask showSIBEngine {-bus busname -node nodeName -server severname}
AdminTask.showSIBEngine('[-bus busname -node nodeName -server severname]')
Interactive mode example usage:
SIBAdminCommands
The showSIBJMSActivationSpec command shows details about a JMS activation specification.
None
Batch mode example usage:
$AdminTask showSIBJMSActivationSpec {-bus bus_name -mediationName mediation_name}
AdminTask.showSIBJMSActivationSpec('[-bus bus_name -mediationName mediation_name]')
Interactive mode example usage:
$AdminTask showSIBJMSActivationSpec {-interactive}
AdminTask.showSIBJMSActivationSpec ('[-interactive]')
SIBJMSAdminCommands
The showSIBJMSConnectionFactory command shows details about a JMS connection factory.
None
Batch mode example usage:
$AdminTask showSIBJMSConnectionFactory {-name factory_name}
AdminTask.showSIBJMSConnectionFactory('[-name factory_name]')
Interactive mode example usage:
$AdminTask showSIBJMSConnectionFactory {-interactive}
AdminTask.showSIBJMSConnectionFactory ('[-interactive]')
SIBJMSAdminCommands
Use the showSIBJMSQueue command to show the details about a JMS queue.
None
Batch mode example usage:
$AdminTask showSIBJMSQueue {-name queue_name}
AdminTask.showSIBJMSQueue('[-name queue_name]')
Interactive mode example usage:
$AdminTask showSIBJMSQueue {-interactive}
AdminTask.showSIBJMSQueue ('[-interactive]')
SIBJMSAdminCommands
The showSIBJMSTopic command shows the details for a JMS topic.
None
Batch mode example usage:
$AdminTask showSIBJMSTopic {-name topic_name}
AdminTask.showSIBJMSTopic('[-name topic_name]')
Interactive mode example usage:
$AdminTask showSIBJMSTopic {-interactive}
AdminTask.showSIBJMSTopic ('[-interactive]')
SIBAdminCommands
Use the showSIBMediation command to get the attribute names and values of a SIB mediation.
None
Batch mode example usage:
$AdminTask showSIBMediation {-bus bus_name -mediationName mediation_name}
AdminTask.showSIBMediation('[-bus bus_name -mediationName mediation_name]')
Interactive mode example usage:
$AdminTask showSIBMediation {-interactive}
AdminTask.showSIBMediation ('[-interactive]')
SIBAdminCommands
Use the showSIBus command to get the attribute names and values of a SIB bus.
None
Batch mode example usage:
Interactive mode example usage:
SIBAdminCommands
Use the showSIBusMemeber command to get the attribute names and values of a SIB bus member.
None
Batch mode example usage:
$AdminTask showSIBusMember {-bus busname -node nodename -server servername}
AdminTask.showSIBusMember('[-bus busname -node nodename -server servername]')
Interactive mode example usage:
$AdminTask showSIBusMember {-interactive}
AdminTask.showSIBusMember ('[-interactive]')
ServerManagement group
The showServerInfo command returns the information for a server that you specify.
The configuration ID of the server. (required)
Batch mode example usage:
$AdminTask showServerInfo server1(cells/WAS00Network/nodes/ndnode1/servers/server1|server.xml)
AdminTask.showServerInfo(server1(cells/WAS00Network/nodes/ndnode1/servers/server1|server.xml))
Interactive mode example usage:
ServerManagement group
The showServerTypeInfo command displays information about a specific server type.
A server type. For example, APPLICATION_SERVER. (String, required)
Batch mode example usage:
$AdminTask showServerTypeInfo APPLICATION_SERVER
AdminTask.showServerTypeInfo(APPLICATION_SERVER)
Interactive mode example usage:
$AdminTask showServerTypeInfo {-interactive}
AdminTask.showServerTypeInfo ('[-interactive]')
ServerManagement group
Display the metadata information for a specific server template.
The server type, for example, APPLICATION_SERVER. (String, required)
Batch mode example usage:
$AdminTask showTemplateInfo default(templates/servertypes/APPLICATION_SERVER/servers/default|server.xml) {isSystemTemplate true} {name default} {com.ibm.websphere.baseProductVersion 6.0.0} {description {The WebSphere Default Server Template}} {com.ibm.websphere.baseProductMinorVersion 0.0} {com.ibm.websphere.baseProductMajorVersion 6} {com.ibm.websphere.nodeOperatingSystem {}} {isDefaultTemplate true}
AdminTask.showTemplateInfo(default(templates/serverTypes/APPLICATION_SERVER/servers/default|server.xml)) '[[isSystemTemplate true] [com.ibm.websphere.baseProductVersion 6.0.0] [name default] [com.ibm.websphere.baseProductMinorVersion 0.0] [description The WebSphere Default Server Template] [isDefaultTemplate true] [com.ibm.websphere.nodeOperatingSystem] [com.ibm.websphere.baseProductMajorVersion 6]]'
Interactive mode example usage:
$AdminTask showTemplateInfo {-interactive}
AdminTask.showTemplateInfo ('[-interactive]')
Interactive mode example usage:
SIBAdminCommands
Use the unmediateSIBDestination command to unmediate the named destination on the named bus. Unmediating a destination removes the association between a SIB destination and a SIB mediation.
None
Batch mode example usage:
$AdminTask unmediateSIBDestination {-bus bus_name -destinationName destination_name}
AdminTask.unmediateSIBDestination('[-bus bus_name -destinationName destination_name]')
Interactive mode example usage:
$AdminTask unmediateSIBDestination {-interactive}
AdminTask.unmediateSIBDestination ('[-interactive]')
SIBWebServices group
The unpublishSIBWSInboundService command removes the WSDL document for the inbound service, including the ports from the registry and the business that is defined by the UDDI publication object.
The object name of the inbound service object.
Batch mode example usage:
$AdminTask unpublishSIBWSInboundService $inService {-uddiPublication "MyUddi"}
AdminTask.unpublishSIBWSInboundService(inService, '[-uddiPublication MyUddi]')
Interactive mode example usage:
$AdminTask unpublishSIBWSInboundService {-interactive}
AdminTask.unpublishSIBWSInboundService ('[-interactive]')
None
The updateAppOnCluster command can be 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,
when a SOAP connector is used, and in the sas.client.props file,
when a RMI connector is used.
This command is not supported in local mode.
None
Batch mode example usage:
$AdminTask updateAppOnCluster {-ApplicationNames app1}
$AdminTask updateAppOnCluster { -ApplicationNames app1 -timeout 600}
AdminTask.updateAppOnCluster('[-ApplicationNames app1]')
AdminTask.updateAppOnCluster('[-ApplicationNames app1 -timeout 600]')
Interactive mode example usage:
$AdminTask updateAppOnCluster -interactive
AdminTask.updateAppOnCluster ('[-interactive]')