Managing messaging engines with administrative commands

You can use these commands to manage messaging engines.

About this task

These commands provide an alternative to using the administrative console or using the more complex syntax of wsadmin and Jython.

Procedure

  1. Open a wsadmin command session in local mode. For example:
    wsadmin -conntype none -lang jython

    [IBM i] The wsadmin scripting client is run from Qshell. For more information, see Configuring Qshell to run WebSphere scripts using wsadmin scripting.

  2. Type AdminTask.command, where command is the command format as indicated in the related reference topics.
    For example:
    wsadmin>AdminTask.listSIBusMembers('[-bus bus1 ]')   
    [cells/cell01/buses/bus1|sib-bus.xml#SIBusMember_1092155259869]
    [cells/cell01/buses/bus1|sib-bus.xml#SIBusMember_1092159844593] 
    [cells/cell01/buses/bus1|sib-bus.xml#SIBusMember_1092160253751]
    
    wsadmin>AdminTask.listSIBEngines('[-bus bus1 ]') 
    'node01.server1-bus1(cells/cell01/nodes/node01/servers/server1|sib-engines.xml#
    SIBMessagingEngine_1212163145962)\r\n 
    node02.server2-bus2(cells/cell01/nodes/node02/servers/server2|sib-engines.xml#
    SIBMessagingEngine_1212163146273)'
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 17, 2014 10:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=tjk_cmnds
File name: tjk_cmnds.html