| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Borker and JMS |
« View previous topic :: View next topic » |
| Author |
Message
|
| novice |
 Posted: Thu Dec 14, 2006 1:09 am Post subject: Borker and JMS |
 |
|
Apprentice
Joined: 20 Jun 2005
Posts: 37
|
hello experts!
i've some questions, statements about message broker and jms funcitonality. are they correct? thanks for any comments.
a jsm-message within mq is a mq-message with an mqrfh2.
mqinput/output nodes can read and write jms-messages.
in wmb 6.0 there are some new nodes: jmsinput/output, jms2mqtransform, ...
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2.
the perfromance of the native mq-api is a lot better than the jms-api. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Dec 14, 2006 1:31 am Post subject: Re: Borker and JMS |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| novice wrote: |
hello experts!
i've some questions, statements about message broker and jms funcitonality. are they correct? thanks for any comments.
a jsm-message within mq is a mq-message with an mqrfh2. |
Yes.
| novice wrote: |
mqinput/output nodes can read and write jms-messages.
|
Yes.
| novice wrote: |
in wmb 6.0 there are some new nodes: jmsinput/output, jms2mqtransform, ...
|
Not quite. There's a Java node, an MQGet node and increased capabilities to perform transformations via XSLT. Along with lots of other good stuff.
| novice wrote: |
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2.
|
I don't understand the question. If a message is from a different JMS provider how did it end up on an MQ queue?
| novice wrote: |
the perfromance of the native mq-api is a lot better than the jms-api. |
Simplistic. There's some support packs with performance information. Message size, logging and handling have a far greater impact on performance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mq4you |
| Posted: Thu Dec 14, 2006 1:40 am Post subject: |
|
|
Novice
Joined: 27 Nov 2006
Posts: 11
|
| Quote: |
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2.
I don't understand the question. If a message is from a different JMS provider how did it end up on an MQ queue?
|
i thought, that the jms-input node can act as a jms-client that can read messages from any jms-provider. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 14, 2006 1:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mq4you wrote: |
| Quote: |
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2.
I don't understand the question. If a message is from a different JMS provider how did it end up on an MQ queue?
|
i thought, that the jms-input node can act as a jms-client that can read messages from any jms-provider. |
Fair point, but why? Why use another provider in a Websphere environment?
(To which I imagine the answer is "why not?"  )
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mq4you |
| Posted: Thu Dec 14, 2006 1:53 am Post subject: |
|
|
Novice
Joined: 27 Nov 2006
Posts: 11
|
| Quote: |
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2.
I don't understand the question. If a message is from a different JMS provider how did it end up on an MQ queue?
i thought, that the jms-input node can act as a jms-client that can read messages from any jms-provider.
Fair point, but why? Why use another provider in a Websphere environment?
(To which I imagine the answer is "why not?" )
|
i) the broker could act as a jms-bridge between different jms-providers.
ii) if the jms-message are in a mq-queue. why do i have to use the jms-input node, i can use the mq input node  |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Dec 14, 2006 1:56 am Post subject: Re: Borker and JMS |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi novice,
| novice wrote: |
| a jsm-message within mq is a mq-message with an mqrfh2. |
Not necessarily....if you use JMS nodes, which i see you are aware of, the MQMD and MQRFH2 headers dont exist...only JMSTransport Headers do...and if you use the transform node, then the JMS header is converted to MQMD and MQRFH2...
| novice wrote: |
| mqinput/output nodes can read and write jms-messages. |
It will pick and put the message as an MQ message(perhaps with an MQRFH2), but then u cant call that message a jms message, can u...
| novice wrote: |
in wmb 6.0 there are some new nodes: jmsinput/output, jms2mqtransform, ...
these nodes are usefull when i want to read with the broker jms-messages from a different jms-provider than mq. otherwhise i could read the message with normal mqinput-node. in that case i do have to know how jms-header and properties are mapped into mqmd and mqrfh2. |
No, if your sender is talking in jms, then I suggest you also use jms to pick the message, and similar at output side...
you better have a very good idea of how jms headers are being mapped to mqmd and vice-versa...coz not all are mapped one to one...unluckily, I am not offered the notes on internal working too, so i can't tell you how it does work...maybe someone in Hursley could help you.
| novice wrote: |
| the perfromance of the native mq-api is a lot better than the jms-api. |
This one I cant answer yet, our flows are not too huge, so don't show much of a performance difference....
Regards. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 14, 2006 4:04 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| a jsm-message within mq is a mq-message with an mqrfh2. |
I have to disagree with this statement.
An MQ JMS message MAY have an MQRFH2 header. It does not HAVE to have one. This is where all the stuff with targetClient comes to bear (read up on it in the using java manual)
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
|
|
|
|
