IBM MQ distributed queuing techniques

IBM MQ distributed queuing techniques

The subtopics in this section describe techniques that are of use when planning channels. These subtopics describe techniques to help you plan how to connect your queue managers together, and manage the flow of messages between our applications.
For message channel planning examples, see:

Message channel planning example for UNIX, Linux , and Windows
Message channel planning example for IBM® i
Message channel planning example for z/OS®
Message channel planning example for z/OS using queue sharing groups

Message flow control
Message flow control is a task that involves the setting up and maintenance of message routes between queue managers. It is important for routes that multi-hop through many queue managers. This section describes how we use queues, alias queue definitions, and message channels on your system to achieve message flow control.
Putting messages on remote queues
We can use remote queue definition objects to resolve a queue name to a transmission queue to an adjacent queue manager.
Choosing the transmission queue
We can use a remote queue definition to allow a different transmission queue to send messages to the same adjacent queue manager.
Receiving messages
We can configure the queue manager to receive messages from other queue managers. You must ensure that unintentional name resolution does not occur.
Passing messages through your system
We can pass messages through your system in three ways - using the location name, using an alias for the queue manager, or selecting a transmission queue.
Separating message flows
We can use a queue manager alias to create separate message flows to send messages to the same queue manager.
Concentrating messages to diverse locations
We can concentrate messages destined for various locations on to a single channel.
Diverting message flows to another destination
We can redefine the destination of certain messages using queue manager aliases and transmission queues.
Sending messages to a distribution list
We can use a single MQPUT call to have an application send a message to several destinations.
Reply-to queue
We can create a complete remote queue processing loop using a reply-to queue.
Networking considerations
In a distributed-queuing environment, because message destinations are addressed with just a queue name and a queue manager name, certain rules apply.
Return routing
Messages can contain a return address in the form of the name of a queue and queue manager. This return address form can be used in both a distributed-queuing environment and a clustering environment.
Managing queue name translations
When you create a queue manager alias definition or a remote queue definition, the name resolution is carried out for every message carrying that name. This situation must be managed.
Channel message sequence numbering
The channel uses sequence numbers to assure that messages are delivered, delivered without duplication, and stored in the same order as they were taken from the transmission queue.
Loopback testing
Loopback testing is a technique on non- z/OS platforms that allows you to test a communications link without actually linking to another machine.
Route tracing and activity recording
We can confirm the route a message takes through a series of queue managers in two ways.
Parent topic: Configure distributed queuing

Related tasks

Configure distributed queuing

Related information

Channels
Introduction to message queuing
Distributed queuing and clusters
Example configuration information