Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond
Home » BizTalk Server » BizTalk Blogs » Stephen W. Thomas BizTalk MVP » Envelope Processing on Send and Receive Ports

Envelope Processing on Send and Receive Ports

BizTalk Blogs

This group is for blogs related to BizTalk Server. This includes Community Syndicated blogs and Stephen W. Thomas’s blog.
Sitewide Application Navigation
Options
Monthly Archive List
Archives
Tags

Stephen W. Thomas BizTalk MVP

Insight and guidance on BizTalk, AppFabric, and related Microsoft technologies.

Envelope Processing on Send and Receive Ports

Rate This
Sun, Aug 22 2004 8:25 AM
  • Comments 3
Have you looked at the SDK example working with Envelopes in BizTalk 2004 for Flat Files and tried to get it to work with XML Documents?  Well, I did and I found it a little trickier than I expected.

Key Take Home Points:

- De-Batching / Envelope Processing for XML Document must take place on the Receive Port.  I have not been able to get it to work on the Send Port, but I am still trying.

- Properties can be promoted from the Header and demoted to the single messages

- No custom pipelines are required for Receive Port Processing as long as the Root Node Name and Namespace are unique throughout your entire deployed solutions.

DOWNLOAD: Get the sample here!

Set-up is easy, just unzip the SampleEnvelopes folder and put it on your C: drive.  Then, build and deploy the SampleEnvelopes project. I use early binding so the send and receive ports will be created for you. 

 

To run the sample, drop the start messages named StartFileInbound.xml into c:\SampleEnvelopes\In_Inbound.  You will get 3 messages in the Out_Inbound folder for each start message.  Also, note that the Orchestration will run 3 times.  Plus, I promote and demote Header information to show how it can be passed into the single messages.  If all else fails, read the ReadMe.txt file.

 

Take Away: Once you get the hang of XML Envelopes in BizTalk 2004 they can be a powerful tool for easy document splitting.

, , ,
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Post
  • PeterJ
    Fri, Dec 28 2007 8:37 AM

    Very clear example thanks, but I have a slightly different structure of the XML which is causing me headaches :

    In my example, the "record" node is missing

    <StartBatch>

     <Header>

       <BatchID>K305</BatchID>

       <Sender>Food Mart</Sender>

     </Header>

     <Record>---------missing

     <Message>

       <ID>101</ID>

       <Batch></Batch>

       <Sender></Sender>

     </Message>

     <Message>

       <ID>102</ID>    

       <Batch></Batch>

       <Sender></Sender>

     </Message>

     <Message>

       <ID>103</ID>

       <Batch></Batch>

       <Sender></Sender>

     </Message>

     </Record> ------ missing

    </StartBatch>

    & so I can't process my XML. Can this technique still be used.

  • Mon, Jan 7 2008 7:55 AM

    It has been a while since I worked with Envelopes but if I remember correctly, you should still be able to split out the messages.  Just set your Body XPath on the root node.  This should break out all your message nodes.  On the down side, it will also break out your Header node so you’ll need a way to handle it.

    Hope this is clean enough.

    Stephen W. Thomas

  • David Grospelier
    Fri, Mar 6 2009 2:32 AM

    Hello,

    In the beginning of your post you wrote that you was not able to make the debatching working on the send pipeline (with the XMLAssembler component).

    Is it always true ?

Page 1 of 1 (3 items)