ObjectName, Attribute, and AttributeList

WebSphere Application Server scripting commands use the underlying Java Management Extensions (JMX) classes, ObjectName, Attribute, and AttributeList, to manipulate object names, attributes and attribute lists.

WebSphere Application Server ObjectNames uniquely identify running objects. ObjectNames consist of the following:

• The domain name WebSphere.

• Several key properties, for example:

  • type - Indicates the type of object that is accessible through the MBean. For example, ApplicationServer, EJBContainer

  • name - Represents the display name of the particular object. For example, MyServer

  • node - Represents the name of the node on which the object runs

  • process - Represents the name of the server process in which the object runs

  • mbeanIdentifier - Correlates the MBean instance with corresponding configuration data

When ObjectNames classes are represented by strings, they have the following pattern:

[domainName]:property=value[,property=value]*

For example, you can specify WebSphere:name=My Server, type=ApplicationServer,node=n1,* to specify an appserver named My Server on node n1. (The asterisk is a wild card character, used so that you do not have to specify the entire set of key properties.) The AdminControl commands that take strings as parameters expect strings that look like this example when specifying running objects (MBeans). You can obtain the ObjectName for a running object with the getObjectName command.

Attributes of these objects consist of a name and a value. You can extract the name and value with the getName and getValue methods available in the javax.management.Attribute class. You can also extract a list of attributes.

    

 

---