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.

The product provides a special runtime collaborator that you use with standard, dynamic or open custom MBeans to register the custom MBeans with the WebSphere Application Server 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:

Table 1. 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	WebSphere Application Server administrative service	Local access is through the WebSphere Application Server administrative service or the MBean server. Remote access is through the WebSphere Application Server administrative service, and WebSphere Application Server security.
Standard, dynamic, or open	MBean server	Local access is through the WebSphere Application Server administrative service or the MBean server on the distributed platform. Remote access is through the WebSphere Application Server administrative service, the Java™ Management Extensions (JMX) Remote application programming interface (API) (JSR 160) client code, and WebSphere Application Server security.