Using queue manager aliases

Aliases can be used for WebSphere MQ Everyplace queue managers, and can be used by application programs, to provide a level of indirection between the application and the real object.

The following examples illustrate some of the ways that aliasing can be used with queue managers.

Examples of queue manager aliasing

Addressing a queue manager with several different names

Suppose you have a queue manager SERVER23QM on the server SAMPLEHOST, listening on port 8082. You have an application SERVICEX that accesses this queue manager, and wants to refer to the queue manager as SERVICEXQM. This can be achieved using an alias for the queue manager as follows:

A WebSphere MQ Everyplace application can now put messages to the SERVICEXQ on either the SERVER23QM queue manager, or the SERVICEXQM queue manager. In either case, the message will arrive on the SERVICEXQ.

Figure 8. Addressing a queue manager with two different names

Diagram showing a queue manager, SERVER23QM, with a connection or target queue manager called SERVICEXQM and a local queue called SERVICEXQ. A WebSphere MQ Everyplace application puts messages to the SERVICEXQ on either the SERVER23QM or the SERVICEXQM queue manager.

If the SERVICEXQ queue is moved to another queue manager, the connection alias can be set up on the new queue manager, and the applications do not need to be changed.

Different routings from one queue manager to another
Using the scenario just described, an WebSphere MQ Everyplace queue manager on a mobile device (MOBILE0058QM) can now access the SERVICEXQ queue in a number of different ways. Two examples are described here:


© IBM Corporation 2002. All Rights Reserved