Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator examples
Example: Identifying running objects using wsadmin.sh
Overview
Use the AdminControl object to interact with running MBeans. In the WAS, MBeans represent running objects. We can interrogate the MBean server to see the objects it contains.
To see running MBean objects...
### Jacl
$AdminControl queryNames *
### Jython
print AdminControl.queryNames('*')If the client attaches to a stand-alone WAS, the list contains MBeans that run on that server.
If the client attaches to a node agent, the list contains MBeans that run in the node agent and MBeans that run on all application servers on that node.
If the client attaches to a dmgr, the list contains MBeans that run in the dmgr, all of the node agents communicating with that dmgr, and all application servers on the nodes served by those node agents.
The list that the queryNames command returns is a string representation of JMX ObjectName objects. For example:
WebSphere:cell=MyCell,name=TraceService,mbeanIdentifier=TraceService, type=TraceService,node=MyNode,process=server1
This example represents a TraceServer object that runs in server1 on MyNode.
The single queryNames argument represents the ObjectName object for which you are searching. The asterisk ("*") in the example means return all objects, but it is possible to be more specific. As shown in the example, ObjectName has two parts: a domain, and a list of key properties. For MBeans created by the WAS, the domain is WebSphere. If you do not specify a domain when you invoke queryNames, the scripting client assumes the domain is WebSphere. This means that the first example query above is equivalent to:
### Jacl
$AdminControl queryNames WebSphere:*
### Jython
print AdminControl.queryNames('WebSphere:*')includes the following key properties for the ObjectName object:
- name
- type
- cell
- node
- process
- mbeanIdentifier
These key properties are common. There are other key properties that exist. We can use any of these key properties to narrow the scope of the queryNames command.
This example returns a list of all MBeans that represent server objects running on the node myNode. The, * at the end of the ObjectName object is a JMX wildcard designation.
### Jacl
If you enter the following:
$AdminControl queryNames WebSphere:type=Server,node=myNode,*
### Jython
print AdminControl.queryNames('WebSphere:type=Server,node=myNode,*')
### Jacl
$AdminControl queryNames WebSphere:type=Server,node=myNode
### Jython
print AdminControl.queryNames('WebSphere:type=Server,node=myNode')....you get an empty list back because the argument to queryNames is not a wildcard. There is no Server MBean running that has exactly these key properties and no others.
To see all the MBeans representing applications running on a particular node, invoke the following example:
### Jacl
Use the wsadmin scripting AdminControl object for scripted administration
$AdminControl queryNames WebSphere:type=Application,node=myNode,*
### Jython
print AdminControl.queryNames('WebSphere:type=Application,node=myNode,*')