Aliasing on the sending side

Using this method of routing, the receiving queue manager does not know that the sending queue manager has given it an alias name. The aliasing is confined to the sending queue manager only.

On the mobile device:
  • Create a connection from MOBILE0058QM to the SERVER23QM queue manager:
    Connection name
    SERVER23QM
    Network Adapter parameter
    Network:SAMPLEHOST:8082
  • Create an alias called SERVICEXQM for queue manager SERVER23QM

When a message is sent from the mobile device application to the SERVICEXQM queue manager, MQe maps the SERVICEXQM name to SERVER23QM in the connection , and sends the message to the SERVER23QM queue manager.

If the Mobile58QM then wished to send its messages to a different server queue manager, Server24QM, it would remove the alias SERVICEXQM from the Server23QM connection, and add it to a Server24QM connection. This has no impact on the receiving queue managers, or the sending applications.

Figure 1. Addressing a queue manager with two different names
Diagram showing how to address a queue manager that has two names, one being an alias. The sending queue manager can put messages to another queue manager by giving the receiving queue manager an alias. The receiving queue manager does not know that the sending queue manager has given it an alias.

Terms of use | WebSphere software

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