wood burning stoves 2.0
The moose likes Websphere and the fly likes Why JMS and not MQBase Java??? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Why JMS and not MQBase Java???" Watch "Why JMS and not MQBase Java???" New topic

Why JMS and not MQBase Java???

mahadevan raja
Ranch Hand

Joined: Apr 11, 2001
Posts: 96
hi all,
i have a major problem,I have implemented JMS in Websphere 4.0.2,The JMS Provider is the IBM MQSeries v5.2.
Everything is working fine.On running the jsp in which i have used the MQSeries classes for JMS,the message is put to the corresponding queue,based on the JNDI references and lookups.Forget it.
Now i have a doubt.Why shud i use this JMS,when i can do the same thing using MQBase Java,even using this i can put or get message into a remote or local queue.
Why shud i go for such a complex procedure of creating a resource reference in AAT,mapping it,and all those stuffs.
I dont understand,
Cud anyone plz explain y JMS is given so much importance.
I know that WAS4.0 follows the J2ee standards,and thus according to the standard,v use JMS,but what is the exact technical reason.
Plz help me.
Thanx in advance.

SPECIALIST-WCSV5.1 Implementation.<br />SYSTEMS EXPERT-WAS4.0 Administration
Kyle Brown
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
Besides the obvious standards issues you point out, the major reason is that only the JMS classes provide the transactional tie into the EJB transaction manager. If you use the base MQ classes your MQ puts and gets will NOT participate in the 2phase commit transaction with your database resources.

Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
I agree. Here's the link: http://aspose.com/file-tools
subject: Why JMS and not MQBase Java???
It's not a secret anymore!