aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes JMS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS" Watch "JMS" New topic
Author

JMS

raj joe
Ranch Hand

Joined: Mar 17, 2005
Posts: 99
What is the difference between Sun's JMS API and WebSphere MQ API?
Many people usually say that Sun's JMS is an interface and MQ JMS is an implementation of that for IBM WebSphere MQ.
But my question is why should i buy IBM MQ-Series when i can use JMS which should be supported by all J2EE application Servers including websphere application server.

any help will be appreciated
Maarten de Heus
Greenhorn

Joined: Jan 30, 2006
Posts: 9
Hello Raj

The JMS API is indeed an interface. You will still need some implementation for it. A J2EE server must provide an implementation. But this will not always solve your problems.

The J2EE server's implementation of JMS will only provide you with queues within the J2EE server. When you need to communicate outside of your J2EE server you need some extra plumbing.

Websphere MQ is known for its multi-platform/multi OS implementation. If you need to communicate with lots of applications on lots of different OS'es, you might consider Websphere MQ.

At the company I work for, we use WebLogic in combination with Websphere MQ. For J2EE internal communication we use WebLogic JMS queues. When we need to talk to "outside" systems (like our mainframe or to systems from other companies) we use WebSphere MQ.

Hope this helps...

greetings,
Maarten
raj joe
Ranch Hand

Joined: Mar 17, 2005
Posts: 99
Thanks Maarten
Can you please highlight on some features in MQ that will not be available in app server JMS implemetation.

Secondly ,I have two application with Weblogic App Server , I am trying to use JMS to communicate between these application which are physically residing on different machines.Is this fine OR do I need MQ here.


Raj[/qb]
[ April 13, 2006: Message edited by: raj joe ]
Maarten de Heus
Greenhorn

Joined: Jan 30, 2006
Posts: 9
Rai,

Communicating between WLS servers should not be a problem. You can use a WLS message bridge to "cross the gap".

MQ comes in when you need to talk to "other" applications written in Cobol or C++ , etc. running on other OS-es like a mainframe.

greetz,
Maarten
raj joe
Ranch Hand

Joined: Mar 17, 2005
Posts: 99
Originally posted by Maarten de Heus:
Rai,

Communicating between WLS servers should not be a problem. You can use a WLS message bridge to "cross the gap".

MQ comes in when you need to talk to "other" applications written in Cobol or C++ , etc. running on other OS-es like a mainframe.

greetz,
Maarten



Maarten , just to understand the second point.Assume I have two application one residing on XP (j2ee application running on IBM websphere app server) and other on mainframe(Cobol application).Now I have to requirement to send daat from j2ee java application to get that updated in a mainframe DB.

Now my J2ee appplication produces a JMS message and adds to the Q defined in the app server.
Can i not have a IBM webpshere app server running on a mainframe and have the MDB listing to the Q created in my J2EE application app server instance.The MDB then uses some JCA to update the data to the mainframe DB.

Will this approach work?
How does any MQ help in this case?
[ April 21, 2006: Message edited by: raj joe ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JMS