| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Handling TDS message w/Mapping Node |
« View previous topic :: View next topic » |
| Author |
Message
|
| vinod_sri |
 Posted: Fri Jun 29, 2007 1:05 pm Post subject: Handling TDS message w/Mapping Node |
 |
|
Apprentice
Joined: 10 Dec 2003
Posts: 42
Location: Atlanta
|
Hello Folks,
The input message has several tags like TAG100, 110 200, 210 and so on and each tag has several data elements. These tags can be repeated N no of times and they can be anywhere in the message. Now, the requirement is to prune the message by deleting unwanted tags and prepare a new message. Here, I am using the same message set for both the source and the target messages. Here I used the element delimiter for this Tag as <SOH> and Tag Delimiter as <STX>. Using Mapping Node
I am able to send the message with only selected tags, to the target queue. But TAG0000 (Please see the message for this Tag) is being sent with no elements. The reason is TAG0000 is ended right after the first empty element (<SOH><STX>). The subsequent elements for this Tag are placed with no specific Tag title. Please go through the highlighted part in red color in the sample message.
So, the TAG0000 and its associated elements are now seperated as two different entities. I explained to the customer that the TAG0000 should only be ended after the last child of this Tag. But they say that its my dept's responsibility to fix it.
I tried to write an esql: user defined function to increment the array count by 1 to access the tag's child elements. It is not working.
Can you plese help me by suggesting me any feasible solution??
Sample message,
GDSFE0011N0Mark_Shipment_as_Load_Ready_Closed3400722BC2DTXBOT7SAAATAG0000200604211033GCSSMessageBrokerONBKG12.0
TAGT100TW9N0BOT7SAAAT2CP0BOT7SAAANNTAG0100C2DTXBOT7SAAAO1Order Handling1Active3Ordinary Transport Order2006-04-11 02.39.23.529858DBGCSS2006-04-21 08.52.51.526133DSM0132006-04-21 08.52.51.526133DSM0131MSL2006-04-11 02.39.23.529858DBGCSS2006-04-21 08.51.59.776010DSM013Y1Booking ConfirmationBasic2006-04-11 02.39.23.529858DBGCSSP15GCSS1CY4SD11Desktop2006-04-29N10Transdoc InvoicingY2006-04-11 02.39.23.529858YNNPKKTXBOT7SAAAUSD2006-04-29 15.00.00.000000P179South and Central East Asia - Pacific SouthWestMAEUTAG0110CD5TXBOT7SAAAO1Booking Management
Thanks
Vinod |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Jun 29, 2007 2:56 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Let me just check that I understand...
- The message consists of tagged complex elements. These are delimited by STX.
- The members of each complex element have no tags, and they are delimited by SOH.
- Most elements start with a tag, then SOH, then the members ( delimited by more SOH as required), then finish with STX ( the outer delimiter )
- TAG0000 does it differently. It starts with the tag, then SOH, then STX, then the members ( delimited by SOH).
Is that correct?
By the way, it's hard to read your message because SOH and STX look the same in a browser. Might be better to choose alternative delimiters when posting examples. |
|
| Back to top |
|
|
| vinod_sri |
| Posted: Sat Jun 30, 2007 12:50 pm Post subject: |
|
|
Apprentice
Joined: 10 Dec 2003
Posts: 42
Location: Atlanta
|
Hi Kimbert,
You did understand the message correctly. As you observed, TAG0000 is constructed in a different way. <STX> should be the at the end of the last element of TAG0000. But there are two <STX>, of which one occurs right after the first element of the TAG0000, as if the tag is ended right there.
The messageSet is able to parse the message with no errors. The messageset looks like
ABCD_XYZ.mxsd --- Messages ---> ABCD_EVENT_MSG (follows list local elements for header information) ---> ABCD_data ---> TAG_RECORD(0, unbounded) has all the actual data elements -- first element is for TAG name followed by other local elements..
Since, Changing the Tag structure is not in my control I have to find a way to process the message.
Please share with me if you have any solution for it.
Thanks,
vinod |
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Jun 30, 2007 1:28 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi vinod,
If the message is being parsed without errors, what is the problem? Is the message tree incorrect in some way?
| Quote: |
| first element is for TAG name followed by other local elements. |
Why not set Data Element Separation = Tagged Delimited? |
|
| 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
|
|
|
|
