Best practices for standard, dynamic, and open MBeans

Best practices for standard, dynamic, and open MBeans

This article discusses recommended guidelines for standard, dynamic, and open MBeans.
The underlying interface for the WAS administrative service is AdminService. Remote access occurs through the AdminControl scripting object.
For WAS V5, the MBean registration and capabilities are as follows:

MBean type Registered with: Capabilities
Model WAS administrative service Local access is through the WAS administrative service or the MBean server. Remote access is through the WebSphere Application Server 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.

Best practice: For V6, you can optionally register standard, dynamic, and open custom MBeans with the WebSphere Application Server administrative service to take advantage of the capabilities that in V5 are available only to model MBeans.bprac
V6 introduces a special run-time 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.
For WAS V6, 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 WebSphere Application Server 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 application programming interface (API) (JSR 160) client code, and WebSphere Application Server security.

Related tasks

Creating and registering standard, dynamic, and open custom MBeans

MBean type	Registered with:	Capabilities
Model	WAS administrative service	Local access is through the WAS administrative service or the MBean server. Remote access is through the WebSphere Application Server 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.