Best practices 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.

The product provides a special runtime collaborator that we use with standard, dynamic or open custom MBeans to register the custom Beans 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 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. (ZOS) Remote access is also through z/OS system extensions.
Standard, dynamic, or open	MBean server	Local access is through the WAS administrative service or the MBean server on the distributed platform. (ZOS) Local access is only through the MBean server. Remote access is through the WAS administrative service, the Java Management Extensions (JMX) Remote API (JSR 160) client code, and WAS security.

Create and registering standard, dynamic, and open custom MBeans