Receiving messages
Configure the queue manager to receive messages from other queue managers. Ensure that unintentional name resolution does not occur.
Figure 1. Receiving messages directly, and resolving alias queue manager name
As well as arranging for messages to be sent, the system administrator must also arrange for messages to be received from adjacent queue managers. Received messages contain the physical name of the destination queue manager and queue in the transmission header. They are treated exactly the same as messages from a local application that specifies both queue manager name and queue name. Because of this, we need to ensure that messages entering your system do not have an unintentional name resolution carried out. See Figure 1 for this scenario.
For this configuration, prepare:
- Message channels to receive messages from adjacent queue managers
- A queue manager alias definition to resolve an incoming message flow, ‘QMB_priority’, to the local queue manager name, ‘QMB’
- The local queue, ‘QA_norm’, if it does not already exist
Receiving alias queue manager names
The use of the queue manager alias definition in this illustration has not selected a different destination queue manager. Messages passing through this local queue manager and addressed to ‘QMB_priority’ are intended for queue manager ‘QMB’. The alias queue manager name is used to create the separate message flow.
Parent topic:
WebSphere MQ distributed-messaging techniques
ic10840_
Home
