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.

For WebSphere Application Server Version 5, the MBean registration and capabilities are as follows:

Table 1. Version 5 MBean registration and capabilities. Examine the registration and capabilities for an MBean type.
MBean type Registered with: Capabilities
Model 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.Remote access is also through z/OS® system extensions.
Standard, dynamic, or open MBean server Local access is through the WebSphere Application Server administrative service or the MBean server on the distributed platform. Local access is only through the MBean server.
Best practice: For Version 6, 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 Version 5 are available only to model MBeans.bprac

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 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 WebSphere Application Server Version 6, the MBean registration and capabilities are as follows:

Table 2. Version 6 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. Remote access is also through z/OS system extensions.
Standard, dynamic, or open MBean server Local access is through the WebSphere Application Server administrative service or the MBean server on the distributed platform. Local access is only through the MBean server. 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.



Related tasks
Creating and registering standard, dynamic, and open custom MBeans
Concept topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=rjmxSDOMbean
File name: rjmx_sdo_mbean.html