This MBean will be uploaded to the Application Server.
The MBean will be accessed by the Application Server using this path.
You must provide the path to the JAR file if your MBean is not yet deployed.
This Name should be unique for a given domain as the namespace for MBeans is shared with that for Java EE applications and modules. Therefore, you should not use the name of a deployed enterprise application for creating an MBean. The default name is the MBean's implementation class name.
Specifies the javax.management.ObjectName of the MBean. The ObjectName must be unique within the target specified, as is the case with the name of the MBean. The uniqueness is required because at runtime the MBeans are registered with their ObjectName and not names.
The default ObjectName is of the format: user:type= implementation-class-name,name=implementation-class-name >. The user is the name of the JMX Domain where these MBeans will be registered. No other JMX domain name is allowed.
This is the ObjectName that will be stored in the Application Server domain's configuration. At runtime though, when the MBean is registered in the MBeanServer, an identifying property, server=name_of_the_target_server_instance is inserted in the ObjectName.
This property is not persisted. It is a runtime artifact only.