| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DFDL Parser and Mapping Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| harry123 |
 Posted: Tue Feb 05, 2013 9:06 am Post subject: DFDL Parser and Mapping Node |
 |
|
Newbie
Joined: 30 Oct 2012
Posts: 9
|
Hi All,
I am new to message broker and experimenting with DFDL parser and mapping node.
I have created a message model of CSV text and tested with the sample data file. The parsing completed successfully.
Now I have included a mapping node in my flow, and selected the same .xsd file as my I/P and O/P. I used auto map to map I/P to O/P, and selected the O/P parser as XMLNSC.
I have connected the O/P to MQ Output queue and deployed. I didn't receive any errors, but I don't see the O/P in my O/P queue. The message is still in my I/P queue.
Can some one please help me where did I go wrong.
Thanks,
Harry |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Feb 05, 2013 10:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Feb 05, 2013 11:08 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Message Broker is a complex product, so you will need to learn some basic facts to become competent. In that respect, it's not quite as simple as learning a new programming language. Keep on experimenting, though - just make sure to do the background reading as well.
This is what is probably happening:
- the input node is parsing your input message using the DFDL parser, being guided by your DFDL xsds.
- The message is being propagated to the Mapping node
- The Mapping node is creating a new message tree from the old one, and propagating that tree to the Output node.
- The output node has attempted to convert the message tree to a bit stream using the XMLNSC parser. While doing this it has encountered an error, and the message has been rolled back all the way to the input node. Your Catch terminal on the input node is not connected, so the only safe course of action is for the input node to put it back onto the queue with the retry count bumped up by 1.
Best way to diagnose this is to take a user trace. If you're not quite ready for that, attach the message flow debugger. Either way, Windows Event Viewer will contain the full text of the error ( assuming that you are on a Windows machine ). |
|
| 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
|
|
|
|
