Synchronous message delivery

Synchronous message delivery is similar to the asynchronous case described above, but the queue manager involvement in intermediate hops takes place at a much lower level, involving the transporter and connections. An end-to-end connection is established, using the adapters defined in the protocol specifications at each intermediate node, to identify the next link. At the end of the last link, where no further relevant file descriptors exist, the message gets passed to the higher layers of the queue manager for processing. Thus the sending node does not queue the message but passes it along the connection, through intermediate hops, and then gives it to the destination queue manager to place it on the target queue.

The link into MQ uses a bridge queue on the gateway, which transforms the message into an MQ format. This mechanism means that synchronous MQe style messaging from a device is possible to MQ, with the connection terminating at the gateway. The message is delivered in real time from the gateway, through a client channel, to an MQ server. From there its destination can require it to be routed asynchronously along MQ message channels.

In a similar manner, a device capable of only synchronous messaging can send messages to an asynchronous MQe queue, provided that a suitable intermediary is available.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.