| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dynamic delimiter |
« View previous topic :: View next topic » |
| Author |
Message
|
| francoisvdm |
 Posted: Tue Jun 21, 2011 12:40 am Post subject: Dynamic delimiter |
 |
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Is it possible to change the delimiter as used by the File Input and File Read nodes dynamically? I have files coming in that defines the delimiter to use for the file as one of the first bytes in the file. So...I want to use the same node to process multiple different flat files, with different layouts and delimiters.
Thanks
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jun 21, 2011 12:59 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I don't think the FileInput node can do that.
The MRM parser can deal with dynamic delimiters for standards like HL7 and X12, but cannot pick up a single delimiter in the way that you need it to. Shame, because otherwise Parsed Record Sequence might have been a solution.
Anybody else have a more constructive contribution? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 21, 2011 1:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is the range of delimiters known, fixed, and relatively small? i.e. is there any correlation between the actual delimiter and the type or structure of the message?
If this is the case, I would use the first delimiter as a Tag or as a Message Key/Identity and then MRM can use that to resolve the choice.
If this is not the case, that you have something like MIME where the sending application is free to choose whatever it wants as a delimiter, then you can't do this with any of the parsers that currently ship with message broker, to the best of my knowledge. kimbert says you can with Hl7 and X12, so I'll trust that much, but otherwise. |
|
| Back to top |
|
|
| vairavan |
| Posted: Mon Aug 15, 2011 9:41 am Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
| Quote: |
| If this is the case, I would use the first delimiter as a Tag or as a Message Key/Identity and then MRM can use that to resolve the choice. |
Could you please explain me this little deeper?
I did not understand the first delimiter as a Tag and How MRM can resolve the choice.
Greatly appreciate your response. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 15, 2011 9:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
A tag is a fixed piece of data.
MRM can use Tagged-Delimited or Tagged-Fixed length models, under the TDS parser. As part of building the message tree, it will match the value of a Tag property against the relevant part of the message bitstream. If it matches, then it knows which element (complex or simple) the following portion of the bitstream belongs to - because that's what a tag *does*... it *tags* the following data. |
|
| 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
|
|
|
|
