MQ Connector example

The following is an example of how MQ Connector might work. MQ Connector adapts its behavior to the existing WebSphere® MQ definition that will be different for each environment. For instance, it is not mandatory to have two channels defined as in this example. They are only needed if two queue managers are used.

The MQ Connector service puts messages in a local queue to be sent to a remote queue manager. The local queue manager has definitions for a transmission queue and a channel.

To send and receive messages, the queue manager has two channels defined, as shown in the following figure (where they are identified as SERVER.TO.HOST and HOST.TO.SERVER):

Diagram illustrating MQ Connector service queue manager needs two channels to be defined to send and receive messages

The HOST.TO.SERVER channel is of type server-requested, because the MQ Connector service starts the channel and the sender terminates the call. The local queue in the MQ Connector service, shown here as replyToQ, receives responses from the host.

An application can send data using WebSphere MQ in the following two ways:
To receive data, the application has the following two options: