ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » parsing large MRM message

Post new topic  Reply to topic
 parsing large MRM message « View previous topic :: View next topic » 
Author Message
psandip
PostPosted: Wed Mar 28, 2012 4:59 am    Post subject: parsing large MRM message Reply with quote

Novice

Joined: 11 Aug 2006
Posts: 17

Hi All,

I have a requirement where we need to parse TDS message which maybe upto 40MB in file size and split it into multiple XML's for each line of record. Is there any best practice on how to do this? Any suggestion will be appreciated.

Regards,
Sandeep.
_________________
With Best Regards,
Sandeep
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Mar 28, 2012 5:06 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

First, upgrade to v8 and use DFDL instead of TDS in MRM.

Baring that, look at the large message handling sample.
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Mar 28, 2012 5:26 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

The upgrade to v8 would be great, but is not a requirement.

This document shows how to do it using the ( deprecated ) XML parser for input and output:
http://www-128.ibm.com/developerworks/websphere/library/techarticles/0505_storey/0505_storey.html

You can do the same trick, but use MRM TDS on the input side and XMLNSC for the output side. Do not use MRM XML for the output side of the flow. MRM XML gives no advantages at all over XMLNSC.
Back to top
View user's profile Send private message
psandip
PostPosted: Wed Mar 28, 2012 5:45 am    Post subject: Reply with quote

Novice

Joined: 11 Aug 2006
Posts: 17

thanks for your reply guys....

mqjeff,
Upgrading to v8 is not something i can suggest...v7 has been decided by the solution architects and designers...



kimbert,
Thanks for the link. I am going through it. Actually the input is not in TDS format...input is an XML file which has a CDATA section which can be very large to take the file size to 40MB....and the data in CDATA is tagged delimited....so i said input is in TDS...i hope the scenario doesn't differ.. lol
_________________
With Best Regards,
Sandeep
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Mar 28, 2012 5:47 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fax20230_.htm
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Mar 28, 2012 8:00 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
input is an XML file which has a CDATA section which can be very large to take the file size to 40MB....and the data in CDATA is tagged delimited
In that case, watch out for line feed character normalization in your TDS data. The XML processor will collapse all cr/lf pairs to a single lf.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » parsing large MRM message
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.