|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
|
|
JMS vs MQSeries java |
« View previous topic :: View next topic » |
Author |
Message
|
fanningpj |
Posted: Tue Dec 04, 2001 6:56 am Post subject: |
|
|
Newbie
Joined: 03 Dec 2001 Posts: 7
|
I have been asked to take a JMS application and see if I can add features for MQSeries using IBM's proprietary API (which is new to me).
It's seems to me that there are few if any benefits of using the proprietary API. Have I got this wrong, ie are there any features that are not supported via JMS?
Also, can messages enqueued using JMS be readily dequeued by non-JMS applications? The JMS elements in the message header will just be ignored, presumably.
I'd be grateful to hear anyone thoughts on these issues.
[ This Message was edited by: fanningpj on 2001-12-04 06:57 ] |
|
Back to top |
|
|
middlewareonline |
Posted: Tue Dec 04, 2001 9:47 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001 Posts: 73
|
Depends what you want to achive. One of the advantages of using JMS API is to change underlying messaging middleware without affecting your code. One the otherhand product specific API's deal more closely with the message header. Otherwise you have to see the JMS header/property mapping to propriatary header. Keep in mind with the MQ API you could do things like Report Options, which is NOT available with JMS API.
Rajesh
MiddlewareOnline.COM
_________________ ---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
Back to top |
|
|
ewan_withers |
Posted: Wed Dec 05, 2001 4:51 am Post subject: |
|
|
Newbie
Joined: 04 Dec 2001 Posts: 3
|
Hi,
Answers to your questions:
1. In terms of actual function, there isn't much that the Java MQI supports that isn't in there in the JMS. The only thing that springs to mind is the recently-introduced transaction coordination with databases from the MQQueueManager object. Anything you want to do with the Java MQI you should be able to do in JMS without too much trouble.
2. Messages queued by JMS applications can be dequeued by non-JMS applications by setting the Destination's TargetClient value to JMSC.MQJMS_CLIENT_NONJMS_MQ. This forces the JMS Sender to strip off the MQRFH2 from the message, leaving only the normal MQMD and the message data.
Hope this helps
Ewan |
|
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
|
|
|
|