| Author |
Message
|
| DELLIPIZ |
 Posted: Tue Apr 18, 2006 7:18 am Post subject: Receiving and sending JMS messages with WMQI 2.1 |
 |
|
Acolyte
Joined: 08 Oct 2003
Posts: 70
|
Hi,
We have an existing WMQI flow that takes XML data and transforms it into Legacy.
In the past whenever we had someone send a JMS message, it would fail in our WMQI flow and if I looked at the exception queue, the extra jms 'stuff' would appear as garbage.
To get rid of this 'extra stuff', we had the sending application change the TARGCLIENT from JMS to MQ and this worked.
However, now we have an application that is insisting on sending the message as JMS.
What do I need to do to be able to successfully parse this message???
Also, now that I need to create a JMS output message, what values do I need to set and how do I do that?
Thanks in advance for your help!!!!
Lori |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 18, 2006 7:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The extra "jms" stuff is the MQRFH2 header.
WMQI can parse this just fine.
Your WMQI code, however, may not be expecting it to be there.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| DELLIPIZ |
| Posted: Tue Apr 18, 2006 7:44 am Post subject: |
|
|
Acolyte
Joined: 08 Oct 2003
Posts: 70
|
Hi again,
So what do I need to put in my WMQI code to be able to handle this header.
Thanks!
-Lori |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 18, 2006 7:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's more a matter of making sure your flow can ignore it.
So the question is, why does your flow fail when the header is there?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Apr 18, 2006 8:09 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| In the past whenever we had someone send a JMS message, it would fail in our WMQI flow and if I looked at the exception queue, the extra jms 'stuff' would appear as garbage. |
What was the cause of the exception? The only issue I can see with the presence of the MQRFH2 header is if it contains an mcd folder, which would override the MQInput node properties that describe the characteristics of the incoming message. |
|
| Back to top |
|
|
| DELLIPIZ |
| Posted: Tue Apr 18, 2006 9:18 am Post subject: |
|
|
Acolyte
Joined: 08 Oct 2003
Posts: 70
|
Hey,
I was just reading some more and it does seem like I need to change my Input node to either JMSStream or JMSMap.
Is there a way to handle BOTH regular XML and JMS messages within one flow?
-Lori |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 18, 2006 9:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You only need to use JMSMap or JMSStream if the application is sending JMSMap messages or JMSStream messages.
You can handle XML messages and JMSMap and JMSStream and XML messages that have MQRFH2 headers and TDS messages and CWF messages and MIME messages and IDOC messages and every other possible type of message all in one flow.
Your flow just has to be smart enough not to assume that the message is one thing or another, and examine the message and then do the appropriate thing for that message type.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Tue Apr 18, 2006 9:33 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Set the message domain to BLOB on the MQInput node, and use an RCD node when you determine the format of the message. |
|
| Back to top |
|
|
|
|
