In a distributed-queuing environment, a transmission queue and channel are the focal point for all messages to a location whether the messages originate from applications in your local system, or arrive through channels from an adjacent system. This is shown in Figure 19 where an application is placing messages on a logical queue named 'QA_norm'. The name resolution uses the remote queue definition 'QA_norm' to select the transmission queue 'QMB', and adds a transmission header to the messages stating 'QA_norm at QMB'.
Messages arriving from the adjacent system on 'Channel_back' have a transmission header with the physical queue name 'QA_norm at QMB', for example. These messages are placed unchanged on transmission queue QMB.
The channel moves the messages to an adjacent queue manager.
If you are the WebSphere MQ system administrator, you must:
In a clustering environment, you only need to define a cluster-receiver channel at the local queue manager. You do not need to define a transmission queue or a remote queue object. For information about this, see the WebSphere MQ Queue Manager Clusters book.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
dave2 |