| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem in understanding bytesmessage arriving at MQInput? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Tommaso |
 Posted: Fri Jun 19, 2009 7:48 am Post subject: Problem in understanding bytesmessage arriving at MQInput? |
 |
|
Newbie
Joined: 19 Jun 2009
Posts: 2
|
Hi all,
I have a problem in understanding how to set up a MQInput node.
A client sends a bytesmessage to a queue, where this MQInput node is listening. The content of the bytesmessage itself is an xml structure.
E.g.
"<?xml version="1.0"?>
<trx>
<routing>booklet</routing>
...." in bytesmessage, "0100101011101011110...".
The client cannot send something else, just bytesmessages.
What I cannot figure out at the moment is, how should the "Message Type" in the Properties under "Input Message Parsing" look like?
Currently I have imported an XSD as a "Message Definition File", which has the structure of the xml I am expecting. The "Message Domain" is "MRM" for binary, text and XML.
Now my problem is to understand, how should the length of the fields be and how does the parser know, how many bytes are which <tag>value</tag>? The value can vary, for example in the above example, <routing> can be "booklet", "creditCard", ...!
How would this be set up? 
I would really appreciate a helping hand pointing me in the right direction.
Thanks in advance,
Tommaso |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Jun 19, 2009 8:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Set the Message Domain to XMLNSC.
Everything else will be handled. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 19, 2009 9:33 am Post subject: Re: Problem in understanding bytesmessage arriving at MQInpu |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Tommaso wrote: |
| how should the length of the fields be and how does the parser know, how many bytes are which <tag>value</tag>? |
Because you've imported an xsd file that describes it? And the nice people at IBM use a very clever parser.
If you quote the message set in the node, this is sorted.
It's also much easier to follow the suggestion of my illustrious associate when reading XML & use the XMLNSC domain.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Tommaso |
| Posted: Sun Jun 21, 2009 8:09 am Post subject: |
|
|
Newbie
Joined: 19 Jun 2009
Posts: 2
|
Hello,
thank you both very much.
I thought about that XMLNSC, but I think, that I did not understand it 100%.
Nevertheless, that is a point to start and go on.
Ciao,
Tommaso |
|
| 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
|
|
|
|
