Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Dividing a message into seperate records
- This topic has 5 replies, 1 voice, and was last updated 9 years, 2 months ago by
community-content.
-
AuthorPosts
-
-
February 15, 2007 at 12:08 AM #17674
hi everybody,
i have a scenario where i receive a message that contains multiple records. each record representing a payment that needs to be validated. i need to retreive each record alone, insert in into the database and return a record that holds info about the inserted record. finally i want to gorup all my return results (records) into a single output message.
theoratically i know that i should use envelopes. but although i have already used envelopes, i feel that the above scenario is somewhat complex for a biztalk beginner ): can anyone please giude me maybe to a sample similar to my case.
thanks in advance
-
February 15, 2007 at 12:28 AM #17675
I supposeu shoud not use Envelope Debatching.
Better u use Orchestration and use any one of the debaching methods.
Nodelist,Xpath,Component.
The trick here is assembling the ouput and sending it to source.
You can use xml document to club all outputs and load it in a message and send it bck.
-
February 16, 2007 at 4:41 AM #17698
hi NISHIL, and thanks for your reply…
can you please calrify why you do not prefer using envelopes?
and if not envelopes, are you suggesting that i can pass the message to a .net component where i can handle all my needs there (hitting the database, getting the results, and forming my output message)?
thanks and best regards,
-
February 17, 2007 at 3:28 AM #17711
And here are many other solutions:
http://biztalkland.blogspot.com/2005_03_06_biztalkland_archive.html
-
February 17, 2007 at 3:33 AM #17712
More than envelope processing, in this scenario, assembling the output is the key as Nishil mentioned. With envelope processing you'll have difficulty in correlating each of the records once you split them and update your DB.
You need not use a .NET component as well. You can do it with biztalk components itself. Refer to example "Looping through each employee record" at this link: http://msdn2.microsoft.com/en-us/library/ms935658.aspx.
You can slightly modify the looping process to assemble the output from your DB.
You may already know, but these two articles are good from Jeff and Stephen Thonas:
http://codebetter.com/blogs/jeff.lynch/articles/128664.aspx
http://geekswithblogs.net/sthomas/archive/2004/10/25/13269.aspx
-
February 17, 2007 at 10:30 PM #17714
thanx a lot, the URLs are really helpful
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.