MQSeries.net :: View topic

dc01bb

I'm curious how other shops handle this issue which has become somewhat thorny for us.

We have an existing network of MQ Queue managers that service a number of Websphere Application Servers on AIX and Windows, that allow communication with our legacy applications on a z/OS back end. MQ WorkFlow came on the scene more recently, and we've had issues getting it to integrate into our production environment the way it makes sense to us. Workflow seems rather heavyhanded and inflexible in the way it wants to install and configure itself.

Some facts:

- each system hosting a WAS instance has a local queue manager on it so that it can gain the best performance using Java Bindings type connections.
- the Websphere Java applications would like to coordinate all their work between the Queue Manager allowing communication with the z/OS backend, as well as with the Workflow.
- Workflow seems bent on having to have its own queue manager and not wanting to integrate itself into an existing queue manager, which would be our preference. No one has given me any sort of adequate answer on why this is.

Am I the only MQ administrator that feels that Workflow should be able to integrate itself into an existing MQ queue manager network? And similarly dis-integrate (I really like this word in reference to Workflow!) itself from an MQ Queue Manager network when you uninstall a configuration?

Thoughts? Comments? Rants?
_________________
IBM Certified Specialist - MQSeries