You can use the wsadmin tool and scripting to query server
states.
Before you begin
Before starting this task, the wsadmin tool must be running.
See the topic about starting the wsadmin scripting client using wsadmin
scripting for more information.
About this task
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. Perform the following steps
to query the server state:
Procedure
- Identify the server and assign it to the server variable.
The following example returns the server MBean that matches
the partial object name string:
Using Jacl:
set server [$AdminControl completeObjectName cell=mycell,node=mynode,
name=server1,type=Server,*]
Using 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, you can also query for the server state
attribute. For example:
Using Jacl:
$AdminControl getAttribute $server state
Using Jython:
print AdminControl.getAttribute(server, 'state')
The
getAttribute command returns the value of a single
attribute.