| Configuration for custom MBean.
When a Custom MBean is loaded, the object name specified via
the 'ObjectNameInConfig' Attribute is used. The JMX Domain
will always be {@link #JMX_DOMAIN}.
If there is a name specified in 'ObjectNameInConfig' eg
"name=name1", that name is used and the name as returned
by {@link #getName} is not used within the ObjectName.
Note the following:
- The MBean is dynamically registered or deregistered upon enabling it.
- If an MBean is created with a certain ObjectName, a property "server=<server-name>"
is added to the ObjectName's representation, when the MBean is being registered with
the MBeanServer. The "server-name" above refers to the name of the application server instance.
If you deploy it to the admin server ifself, then the property added is: "server=server".
- If an ObjectName is not specified, then an ObjectName is created by the server.
- The MBean domain name for a custom MBean is user .
Questions
-
When setEnabled( true/false ) is called, are custom MBeans dynamically
loaded and unloaded? Document this here.
-
How to obtain the ObjectName for the runtime MBean that
this config specifies?
-
Are runtime MBeans loaded only in the DAS, or in each server?
What about the Node Agent? If they are loaded per server,
what is put into the ObjectName to distinguish them?
-
All these either/or cases are confusing. We should restrict
the object-name Attribute to properties, prohibit a 'name'
property, and require a 'type' property--my opinion--Lloyd
|
