Message flow between a service integration bus and a IBM MQ network

An application connects to a bus, which is its local bus, and can exchange messages with other applications that connect to the same bus. To exchange messages with applications that connect to a IBM MQ network, you need a WebSphere® MQ 鏈結 that connects the local bus to a foreign bus that represents a IBM MQ network.

Applications that send a message to a queue in a IBM MQ queue manager or queue-sharing group can do so directly by configuring a IBM MQ server definition, or indirectly by using a IBM MQ 鏈結. This topic describes the message flow for a IBM MQ 鏈結.

With a IBM MQ 鏈結, there is a gateway messaging engine on the service integration bus and a gateway queue manager on the IBM MQ network.

Applications that are connected to the local bus send messages to a destination on a foreign bus. The messaging engine that the sending application is connected to on the local bus queues the messages on its link transmitter queue. Service integration flows the messages from the link transmitter queue to the corresponding known link transmitter queue in the gateway messaging engine. Messages then flow to a single sender channel transmitter queue, ready for transmission across the IBM MQ 鏈結.

The sender channel transmitter transmits messages over the IBM MQ 鏈結 to a gateway queue manager or (for IBM MQ for z/OS® only) a queue-sharing group on the remote IBM MQ network.

The IBM MQ network appears as a foreign bus to the service integration bus and the service integration bus appears as a queue manager to the IBM MQ network.

The following figure illustrates an example of the message flow from a service integration bus to a IBM MQ network over a IBM MQ 鏈結.

Figure 1. Message flow between a service integration bus and a IBM MQ network
This figure is described in the surrounding text.

指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:10
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cjc0051_
檔名:cjc0051_.html