Setting up the clients

Each client must have a remote queue definition to the MQ queue. If multiple bridge queues are being used on the gateway, an alias is needed on the remote queue definition so that any application putting messages using a client gets the correct path to the MQ queue. This also helps as applications do not have to be aware of the clients putting to different queues.

For example, if three clients existed, each putting to separate bridge queues, b1, b2, and b3, all remote queue definitions could have an alias of b. Any application putting to the clients can then simply put to queue b. This allows changes in the underlying network without having to make any changes to the application.

To utilize all the bridge queues created on the gateway, and therefore achieve optimal message throughput, the bridge queues should be equally divided amongst all the clients. Therefore, if there are 50 bridge queues and 5000 clients, 100 clients should create a remote queue definition to bridgeq1, another 100 should create a remote queue definition to bridgeq2 and so on.


Terms of use | WebSphere software

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