| Author |
Message
|
| ninja |
 Posted: Mon Nov 16, 2009 8:18 am Post subject: FileInput Parsed Record Sequence |
 |
|
Newbie
Joined: 21 Jul 2009
Posts: 8
|
Hi all,
I know there are already some posts regarding this topic but I still not understand completely how to use this feature.
I'm using broker 6.1 and I want to split a file configuring the FileInput node.
So I'm trying to avoid the compute node to perform the splitting.
My input message (XML) has the following structure:
<flow>
<data>
</data>
<data>
</data>
...
<data>
</data>
</flow>
Obviously I'd like to split these XML in many XML messages with the "data" element as root.
Using the "parsed record sequence" how can the broker understand which is the message to be splitted?
What do I have to put in the message set: the structure of the complete file or only of the part to be splitted?
Thanks in advance. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 16, 2009 8:45 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Could you explain why you want to avoid the use of a Compute Node?
Also,
Have you tried anything out before you asked your question?
With many questions asked in this forum, there is often more than one answer. If you find something that works then go with it.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ninja |
| Posted: Tue Nov 17, 2009 5:19 am Post subject: |
|
|
Newbie
Joined: 21 Jul 2009
Posts: 8
|
No particular reason, smdavies99.
It was my first time using FileInput node and I checked if somebody here managed to configure the "parsed record sequence" option.
Anyway. since this flow was urgent I had to use the alternative solution.
If I have time I'll try again to configure this node and I'll put the solution here.
Regards. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 17, 2009 6:15 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I'd like to split these XML in many XML messages with the "data" element as root. |
I don't think that's possible. Parsed Record Sequence can only operate on a file which consists of a sequence of entire messages ( with no envelope like the '<flow>' tag). |
|
| Back to top |
|
|
| ninja |
| Posted: Tue Nov 17, 2009 6:23 am Post subject: |
|
|
Newbie
Joined: 21 Jul 2009
Posts: 8
|
So this node can process only files with a simple structure. Now I understand why I couldn't configure it properly 
Thanks kimbert. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 17, 2009 6:34 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| btw, the development team are already aware of this limitation. If enough customers want that kind of flexibility, it might get added. Use your IBM rep or this forum to make yourself heard. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 19, 2009 9:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You could maybe do this as a simplified TDS model, with "<flow>" as a header record and '</flow>" as a trailer, and then define a tagged-delimited body with "<data>" and "</data>" as tags and delimiters and a blob in between.
I'm sure it's a bad idea for various reasons, but it might be doable.
I amend this to say that it's probably better to use "<flow>" and "</flow>" as group indicators and terminators than as header and trailer records. |
|
| Back to top |
|
|
|
|
