Architectures based on multiple queue managers
We can use distributed message queuing techniques to create an IBM MQ architecture involving the configuration and use of multiple queue managers.
Before we plan the IBM MQ architecture, familiarize yourself with the basic IBM MQ concepts. See IBM MQ Technical overview.
An IBM MQ architecture can be changed, without alteration to applications that provide services, by adding additional queue managers.
Applications can be hosted on the same machine as a queue manager, and then gain asynchronous communication with a service hosted on another queue manager on another system. Alternatively, applications accessing a service can connect as clients to a queue manager that then provides asynchronous access to the service on another queue manager.
Routes that connect different queue managers and their queues are defined using distributed queuing techniques. The queue managers within the architecture are connected using channels. Channels are used to move messages automatically from one queue manager to another in one direction depending on the configuration of the queue managers.
For a high level overview of planning an IBM MQ network, see Designing distributed queue manager networks.
For information about how to plan channels for the IBM MQ architecture, see IBM MQ distributed queuing techniques.
Distributed queue management enables you to create and monitor the communication between queue managers. For more information about distributed queue management, see Introduction to distributed queue management.
- Plan for distributed queues and clusters
We can manually connect queues hosted on distributed queue managers, or we can create a queue manager cluster and let the product connect the queue managers for you. To choose a suitable topology for the distributed messaging network, we need to consider we requirements for manual control, network size, frequency of change, availability and scalability.- Plan for distributed publish/subscribe network
We can create a network of queue managers where subscriptions created on one queue manager will receive matching messages published by an application connected to another queue manager in the network. To choose a suitable topology, we need to consider we requirements for manual control, network size, frequency of change, availability and scalability.Parent topic: Plan an IBM MQ architecture
Related tasks
Related information