Home Page › Forums › BizTalk 2004 – BizTalk 2010 › serialized Dataset as message……
- This topic has 2 replies, 1 voice, and was last updated 8 years, 11 months ago by
community-content.
-
AuthorPosts
-
-
September 26, 2006 at 8:21 AM #15847
Hello,
I am just starting out designing my first Biztalk app…..and I'm stuck at the first hurdle….I have messages being sent around a system as serialized datasets….I want biztalk to receice these messages….split them into their individual records…process each individual message (using the rules engine)….and then somehow gather the resultant messages together and send them to some other system.
First problem is….how do I get Biztalk to 'understand' the dataset….naively I wondered whether an XSD used to strongly type the dataset could act as a schema…..this doesn't really make sense in my head.
Help?
Advice?
-
September 28, 2006 at 11:19 AM #15885
Greetings,
Your problem is a complex one, so I'll address the individual problems you've raised one by one.
First, you ask how to make BizTalk understand your dataset. You have an XSD used to strongly type the dataset, this is good. What you need to do is add that XSD to your BizTalk project. This will get compiled as a Schema and can act as the definition of the message structure of BizTalk.
Next you ask how to split the individual records, process each, and gather them back at the end. This is a very normal programmers view of the world, but isn't a particularly easy thing to do in BizTalk. It can be done, but it is not a novice task at all. The process of splitting your message into individual records for processing will require you to create and envelope schema. There are some great resources at http://weblogs.asp.net/jan/archive/2004/03/07/85259.aspx which tell you how to do such a thing. Once you've done that, to gather them all back together becomes the trick. Assuming that order is important you'll want to implement a sequential convoy to do this. This can be learned about here : http://www.biztalkgurus.com/Samples/Sequential-Convoy-Orchestration.html
Now, let me give you some advice, it is generally the best practice to try and build your architecture so that each message processing through BizTalk can stand on its own. That it does not have to be matched with other messages before sending and the like. Spend some time to consider if your architecture can be modified to allow for that. Sometimes it can't (EDI Batching is an example), but most times it can. I can't tell you which position you are in because I don't know your problem.
Tim Rayburn
http://www.TimRayburn.Net-
September 29, 2006 at 2:25 AM #15894
Thanks for replying……
I'm not sure if the xsd will work as a schema for the dataset….my (mis?)understanding, is that xsd's can be used as schema's for xml files, and used to generate datasets, but an application expecting xml based on an xsd wont know what's hit it if a dataset turns up….
Things have moved on though….I have abandoned using an orchestration to process these messages….basically I got to the conclusion you have given me…..what I'm really after is using the rules engine to process messages, and it's much easier to wire some c# code up to a policy than do it via an orchestration…..
documentation seems a bit thin on the ground for designing rules……
any advice in this line?
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.