Certain MQe resources – queues, queue managers and connections – can have aliases, other names by which they can be known. In order to facilitate administration, the MQe JMX interface re-registers MBeans which have aliases under an object name corresponding to the alias. Thus for example if the JMX interface is used to add an alias myAlias to an application queue myQueue, the queue MBean is actually registered twice,
com.ibm.MQe_<OwningQMName>_ApplicationQueues:name=myQueue
and once with object name com.ibm.MQe_<OwningQMName>_ApplicationQueues:name=myAlias, type=alias, resourceName=myQueue@<OwningQMName>.
This means that the administrator does not have to be aware of the real name of the resource in order to administer it via JMX.
Likewise, when aliases are removed from resources, the corresponding ObjectName is de-registered.
One side-effect of this practice is that if a user chooses to create and register some MQe MBeans without using the helper method createMQeMBeans(), this may result in an inconsistent picture where some resources are registered with alias names while others are not. This enforces the argument for using the helper method to create and register all MQe MBeans.