The administration queue does not understand how to perform administration of individual resources. This knowledge is encapsulated in each resource and its corresponding message.
In Java, there is a hierarchy of administration message types. For certain operations, the exact type of administration message is required, for example, to create a Home Server 'queue' you need a Home Server Queue administration message. For other operations, a more general administration message is appropriate, for example, to enquire upon a home server queue, you can use a queue administration message, or a remote queue administration message. If in doubt, use the exact type of administration message.
The following messages are provided for administration of WebSphere MQ
Everyplace resources:
Table 3. Administration messages
Message name | Purpose |
---|---|
MQeAdminMsg | an abstract class that acts as the base class for all administration messages |
MQeAdminQueueAdminMsg | provides support for administering the administration queue |
MQeConnectionAdminMsg | provides support for administering connections between queue managers |
MQeHomeServerQueueAdminMsg | provides support for administering home-server queues |
MQeQueueAdminMsg | provides support for administering local queues |
MQeQueueMangerAdminMsg | provides support for administering queue managers |
MQeRemoteQueueAdminMsg | provides support for administering remote queues |
MQeStoreAndForwardQueueAdminMsg | provides support for administering store-and-forward queues |
MQeCommunicationsListenerAdminMsg | provides support for administering communications listeners |
These base administration messages are provided in the com.ibm.mqe.administration package. Other types or resource can be managed by subclassifying either MQeAdminMsg or one of the existing administration messages. For instance, an additional administration message for managing the WebSphere MQ bridge is provided in the com.ibm.mqe.mqbridge package.
In the C codebase, all messages are MQeFields instances. This applies to admin messages and the admin message types are distinguished by a special field inserted into the fields object. The user has to create an admin message of the appropriate type from scratch, inserting all of the required fields described later in this chapter. Alternatively, for local administration, use the native administration API (see chapter 3). The native codebase can respond correctly to all administration messages but the native administration API is usually used for local administration. For these reasons, most of the examples in this chapter relate to the Java codebase only.