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:
  • Configure a connection on the SERVER23QM :
    Connection Name/Target queue manager:
    SERVICEXQM
    Description:
    Alias definition to enable SERVER23QM to receive messages sent to SERVICEXQM
    Channel:
    "null"
    Network Adapter:
    "null"
    Network adapter options:
    "null"
  • Create a local queue on the SERVER23QM queue manager:
    Queue Name:
    SERVICEXQ
    Queue Manager:
    SERVER23QM
    The server-side application takes messages from this queue, and process them, sending messages back to the client.
an MQe 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 1. 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. an MQe 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.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.