A common topology allows messages to flow between MQ and a client MQe queue manager. This cannot happen directly, but requires an intermediate bridge-enabled MQeQueue manager. The client can then be a small footprint device with no knowledge of MQ. If you start with the configuration we have above, the following additions are needed to allow a client (MQeMoonQM, on a device called moon) to communicate with MQ, as shown in the following diagram:
The following have been added:
The topology is more readily seen as message routes, as shown in the following diagram:
Messages can be pushed to MQ by using a via connection to chain remote queues, as shown in the following diagram:
Here we have added a via connection, to route messages destined for MQSaturnQM vian MQeEarthQM, and we have added a remote queue definition for MQSaturnQ@MQSaturnQM. The messages can now flow from the client to MQ, as shown in the following diagram:
This topology is more easily understood as a collection of message routes, as shown in the following diagram: