ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » Difference between JMS AND WebSphere MQ

Post new topic  Reply to topic
 Difference between JMS AND WebSphere MQ « View previous topic :: View next topic » 
Author Message
Java_Problem
PostPosted: Tue Oct 28, 2008 1:08 pm    Post subject: Difference between JMS AND WebSphere MQ Reply with quote

Newbie

Joined: 16 Jul 2008
Posts: 9

Hello All,

This may be a very simple question for folks who are doing this stuff then me who just got into this. I have been reading about JMS and WebSphere MQ in particular and have few basic questions:

1. What is MQ Series? Is it same as WebSphere MQ Series. If so, why we have 2 difference API's. If not, what is the use of one over another

2. What is simple clear difference between JMS and WebSphere MQ APIs. WebSphere MQ Series mentions that I can use JMS API to connect to it, then what is WebSphere MQ API meant for.

3. Sun website says that you can use JMS API to connect to JMS Provider. In this case, a simple Java program can use JMS API to connect to JMS Provider. Are they mentioning about J2EE Application Server as Provider. My understanding is all JMS Provider must have to implement JMS API - correct

This is what my understading is that - WebSphere MQ Series is a product that implements JMS API and in order to connect to it you need the client jars (WebSphere specific). There is nothing related to JMS API that you have to write - but again, I may be wrong

Please help on these question

Thanks a lot
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Oct 28, 2008 1:56 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

1.) Yes you have 2 different APIs. The manipulation possibilities are not equal across the 2 different APIs.

2) One is JMS compliant the other isn't.

3) Correct. Not all JMS providers are a J2EE appserver but the J2EE appserver should be able to link to any JMS provider.

To connect you will have to use the JMS API so yes you have to write code. You don't have to write any of the implementation code that's provided in the jars.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
masteringmq
PostPosted: Thu Oct 30, 2008 12:45 am    Post subject: Reply with quote

Master

Joined: 20 Oct 2008
Posts: 200

Please read intercommunicational manual or google for details.
Back to top
View user's profile Send private message
zpat
PostPosted: Thu Oct 30, 2008 12:53 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

JMS is simply a layer which itself uses the underlying MQ API (MQI).

The entire world does not use Java. JMS is Java only.

In Java there is the choice of using MQI or JMS.
Back to top
View user's profile Send private message
gs
PostPosted: Thu Oct 30, 2008 12:57 am    Post subject: Reply with quote

Master

Joined: 31 May 2007
Posts: 254
Location: Sweden

masteringmq wrote:
Please read intercommunicational manual or google for details.


Not really, intercommunication describes communication between MQ series applications.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Thu Oct 30, 2008 6:58 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

Quote:
1. What is MQ Series? Is it same as WebSphere MQ Series. If so, why we have 2 difference API's. If not, what is the use of one over another


Version 1 to 5.2 of the IBM messages product was known as "MQSeries", but from version 5.3 onwards it was rebranded by IBM as "WebSphere MQ", to fit in with the new WebSphere suite of products.

The API is the same. In procedural languages (eg. C, COBOL) the API is called the "MQI".

Quote:
2. What is simple clear difference between JMS and WebSphere MQ APIs. WebSphere MQ Series mentions that I can use JMS API to connect to it, then what is WebSphere MQ API meant for.


JMS is an messaging paradigm that can use various providers. MQ has been implemented as one of those providers, to provide a JMS interface into the messaging style of MQ.

The program design style and coding of using JMS and the MQ API (MQI or Java MQ classes) is quite different.

Quote:
3. Sun website says that you can use JMS API to connect to JMS Provider. In this case, a simple Java program can use JMS API to connect to JMS Provider. Are they mentioning about J2EE Application Server as Provider. My understanding is all JMS Provider must have to implement JMS API - correct


Yes, but you don't need an app server to use the MQ JMS provider.
_________________
Glenn
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » Difference between JMS AND WebSphere MQ
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.