Multiple pull route

It is generally more efficient to use a multiple pull message route as this requires the same number of resource definitions, but will handle all the traffic for the MQe queue manager. This is done using a Remote queue manager alias on MQ (effectively a remote queue where the target queue name is the same as the target queue manager name), as shown in the following diagram:

Figure 1. A multiple pull message route

Message resolution works as before, but now messages for any queue on MQeEarthQM will be moved, making this a multiple pull message route, as shown in the following diagram:

Figure 2. Multiple pull route, expressed using message route schema


Terms of use | WebSphere software

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