MQSeries.net :: View topic

Vitor · Posted: Mon Oct 05, 2015 4:56 am Post subject:

WAS 8.5 and WMQv7.5

Here's a basic question for people:

We use a hub-and-spoke queue manager topology for applications that don't have heavy duty messaging requirements. We have a number of queue managers that act as hubs, and applications connect via a SVRCONN with all the usual security features to a given hub.

To increase resilience and scale load, we're putting the connections through an F5 so that the applications now connect to thisapp.vitorisawesome.com(2414) and this resolves to either qmgr1.vitorisawesome.com or qmgr2.vitorisawesome.com(2414) in the usual way.

I'm being told by some of our WAS based applications that this won't work in WAS because "the WAS admin console" requires you to enter a queue manager name as well as a host name and port number, and for 50% of the connection requests they'll end up on the wrong queue manager. When asked to prove this, they provided some kind of Java-looking log with a lot of 2059 errors in it.

So is it the case that WAS can only connect to a single named queue manager, like CICS on z/OS? If so, what solutions have others used to provide resilience other than one WAS instance per queue manager with the code identically deployed to each?
_________________
Honesty is the best policy.
Insanity is the best defence.