The route that a message takes through a WebSphere MQ Everyplace network can depend upon many resources (queues, connection definitions, listeners and so on). These need to be correctly set up, often in pairs whose settings need to be complementary. Failure to set up the correct resources, or setting certain of their values incorrectly can result in failure to deliver messages. Since the task of setting up a network that correctly routes messages can initially appear complex, the current chapter describes the theory underlying message resolution.
The document begins by introducing the notation used in diagramming the WebSphere MQ Everyplace network topology, and then shows message resolutions of increasingly complex nature. Along the way certain terms are surreptitiously defined to describe the process of message resolution. At the end of the document the terms are consolidated into a complete description of message resolution that encapsulates all the complexity.
A common source of confusion when discussing WebSphere MQ Everyplace is the differentiation between a local queue that exists on a remote machine (or queue manager), and a local definition of that queue on the remote machine. Both of these entities are commonly referred to as 'remote queue's. In order to disambiguate these, the term 'remote queue reference' will always be used to describe a local definition of a queue that resides on another (remote) machine (or queue manager).