We are currently using WebSphere MQ to fetch data from mainframes and at times face issues on the MQ side.
I would like to know if there is someway to circumvent MQ and use JMS instead to fetch data from mainframes. We use WebSphere Application Server 6.0.2.
Sorry but JMS is only a driver interface not a queue manager implementation.
Between JMS and a queue manager there is the same difference than between JDBC and a database.
LLP, Andrea
What types of issues are you facing with WebSphere MQ? How are you accessing it, and what do you mean by "circumvent MQ and use JMS?" Do you mean remove queueing all-together, or just find a different way to access the queues (or are you looking to replace WebSphere MQ with a different JMS provider?)
Sorry for all the questions, just want to clarify :)
WebSphere MQ does support JMS.
Thanks for the response. Here is the clarification.
One big issue - is lack of MQ skills. Currently MQ is a black box and we use API's to call MQ queue manager. Ideally we are looking at eliminating something as complicated as MQ (more to do with our skill level) and use JMS to communicate with MQ. YES - i am looking at replacing MQ with a JMS provider that comes along with WAS.
WebSphere MQ does support JMS - true. Then again, we don't have full control over MQ to "manage" it.
Of course you can use JMS on the java side which will end up wrapping calls to MQ. You just have to be careful about message headers. Replacing MQ with another messaging infrastructure is dependent on what the mainframe can talk to, since I imagine you don't have much control over that, right? MQ is often chosen because of it's support by IBM's mainframe systems.
Greg