Best practices for standard, dynamic, and open MBeans

WAS v8.5 > Administer applications and their environment > Use the administrative clients > Use administrative programs (JMX) > Extend the WAS administrative system with custom MBeans
Best practices for standard, dynamic, and open MBeans

This topic discusses recommended guidelines for standard, dynamic, and open MBeans.
The underlying interface for the WebSphere Application Server administrative service is AdminService. Remote access occurs through the AdminControl scripting object.
WAS v8.5 provides a special runtime collaborator that we use with standard, dynamic or open custom MBeans to register the custom MBeans with the WAS administrative service. The standard, dynamic, and open MBeans display in the administrative service as model MBeans. The administrative service uses the capabilities available to MBeans that are registered with the administrative service.
The MBean registration and capabilities are as follows:
MBean registration and capabilities. Examine the registration and capabilities for an MBean type.

MBean type Registered with: Capabilities
Model, and optionally standard, dynamic, or open WAS administrative service Local access is through the WAS administrative service or the MBean server. Remote access is through the WAS administrative service, and WAS security.
Standard, dynamic, or open MBean server Local access is through the WAS administrative service or the MBean server on the distributed platform. Remote access is through the WAS administrative service, the JMX Remote API (JSR 160) client code, and WAS security.

Related

Create and registering standard, dynamic, and open custom MBeans

+
Search Tips | Advanced Search

MBean type	Registered with:	Capabilities
Model, and optionally standard, dynamic, or open	WAS administrative service	Local access is through the WAS administrative service or the MBean server. Remote access is through the WAS administrative service, and WAS security.
Standard, dynamic, or open	MBean server	Local access is through the WAS administrative service or the MBean server on the distributed platform. Remote access is through the WAS administrative service, the JMX Remote API (JSR 160) client code, and WAS security.