Query server state using scripting

Use the wsadmin tool and scripting to query server states.

When querying the server state, the following command steps return a value of STARTED if the server is started. If the server is stopped, the command does not return a value.

In a WebSphere Application Server, Network Deployment environment, you also can query for the server status from the deployment manager. If the server is active, the command returns the STARTED return value. If the server is stopped, the command returns the STOPPED return value. If the server is down there is no MBean server and completeObjectName will be returned as an empty string. Trying to use an empty string for the completeObjectName in any MBean server API (including AdminControl in wsadmin) would result in an error.

Query the server state

• Identify the server and assign it to the server variable. The following example returns the server MBean that matches the partial object name string:

  • Jacl:
    set server [$AdminControl completeObjectName cell=mycell,node=mynode, name=server1,type=Server,*]

  • Jython:
    server = AdminControl.completeObjectName('cell=mycell,node=mynode,name=server1,type=Server,*')
    print server

  Example output:

  WebSphere:cell=mycell,name=server1,mbeanIdentifier=server.xml#Server_1,type=Server,node=mynode,process=server1,processType=ManagedProcess

  If the server is stopped, the completeObjectName command returns an empty string ( ' ' ).

• Query for the state attribute. In addition to using the previous step, we can also query for the server state attribute. For example:
  • Jacl:
    $AdminControl getAttribute $server state

  • Jython:
    print AdminControl.getAttribute(server, 'state')

  The getAttribute command returns the value of a single attribute.

  Example output:

  STARTED

wsadmin AdminControl

Start the wsadmin scripting client

Commands for the AdminControl object