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:

Table 1. V5 MBean registration and capabilities

MBean type Registered with: Capabilities
Model WAS admin service Local access is through the WAS administrative service or the MBean server. Remote access is through the WAS admin 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, optionally register standard, dynamic, and open custom MBeans with the WAS admin service to take advantage of the capabilities that in Version 5 are available only to model MBeans
Version 6 introduces a special run-time collaborator that you use with standard, dynamic or open custom MBeans to register the custom MBeans with the WAS admin service. The standard, dynamic, and open MBeans display in the admin service as model MBeans. The admin 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:

Table 2. V6 MBean registration and capabilities

MBean type Registered with: Capabilities
Model, and optionally standard, dynamic, or open WAS admin service Local access is through the WAS administrative service or the MBean server. Remote access is through the WAS admin 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 Java Management Extensions (JMX) Remote API (JSR 160) client code, and WAS security.

Related tasks

Create and registering standard, dynamic, and open custom MBeans

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