| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| swann |
 Posted: Wed Nov 09, 2011 4:30 pm Post subject: JMS queue |
 |
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
Hi Friends,
To my understanding that you create a Initial context and include the connection factors and destinations, to connect to the specified queue on a QM for a java application.Now the application will contact jndi space (with specified Connection factors and destinations)and ultimately puts a message to a queue in QM.Now what is the concept of a "JMS queue".Why do some people will map it with mq queue.For example a creating a jms queue from a existing mq objects.What does this mean and why do we need a jms queue when a application is able to connect the QM placing messages.Answers will be greatly appreciated |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Nov 09, 2011 5:09 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
JMS is a general-purpose messaging service. JMS does not require WMQ software.
For those that choose to use it, WMQ is a JMS provider. For a message created by a JMS application to be put to (or consumed from) a WMQ queue, there must be WMQ-compliant object definitions.
Yes, the JMS app needs to be able to connect to the queue-manager instance; but the app also needs to open a named queue object. A qmgr can have a few, dozens, or hundreds of queues.
Does this help?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 09, 2011 5:52 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
JMS is a standard that defines a set of mechanisms for programs to interact with a messaging provider.
JMS is not a messaging provider, nor can it be used without a messaging provider.
It's an API, not a tool or a server.
JMS is useful for applications that wish to comply with JEE standards and use JEE services, including Message Driven Beans. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Nov 09, 2011 6:07 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I am corrected.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 09, 2011 10:09 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To be more specific to the OP's question:
- As stated by mqjeff JMS is an API that allows you to interact in a provider independent way with a JMS compliant messaging provider.
- JNDI is a service that allows you to map known JMS Objects to the provider specifics. It acts as a level of indirection and allows you access through the JMS API, instead of having to use the provider's native (JMS compliant) API.
As an example:
In JMS a WMQ queue can be "mapped" unto a JMS queue object in more than one manner:
- Using the JNDI layer: Queue myq = (Queue) ctx.lookup("myqueue");
- Using the URI layer: session.createQueue("queue://QMGR/QUEUENAME?attribute=value");
- Using base attribution: session.createQueue("QUEUENAME");
- Using web services / soap notation ...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
