Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond
Home » BizTalk Server » BizTalk 2004 » BizTalk 2004 Forum » two activable receive shapes in a orchestration

two activable receive shapes in a orchestration

BizTalk 2004

This group is for all content related to BizTalk Server 2004. This includes a forum, samples, videos, labs, whitepapers, and tools. Most of the content here also applies to other versions of BizTalk beyond 2004.
Sitewide Application Navigation
Details
  • 9 Replies
  • 0 Subscribers
  • Postedover 7 years ago
Options

two activable receive shapes in a orchestration

  • rated by 0 users
  • This post has 9 Replies |
  • 0 Followers
  • Posted by
    on Fri, Apr 28 2006 1:37 PM
    dear friends,

    Is it possible to have two receive shapes in a orchestration?If yes,how to do it?If no,what is the other solution?

    I want my orchestration to do the following.
    1) In folder A i receive a flat file and i tranform the flat file into 1 XML document and i want put in folder B.
    2)i want to split the XML document in folder B,into different XML doc and i want to put in folder C.

    can anybody help me?
  • Posted by
    on Fri, Apr 28 2006 1:40 PM
    [quote user=\"kavitha\"]dear friends,

    Is it possible to have two receive shapes in a orchestration?If yes,how to do it?If no,what is the other solution?

    I want my orchestration to do the following.
    1) In folder A i receive a flat file and i tranform the flat file into 1 XML document and i want put in folder B.
    2)i want to split the XML document in folder B,into different XML doc and i want to put in folder C.

    can anybody help me?


    I'm not sure why you want to do this from a single orchestration. Seems like both operations are completely unrelated to each other.
    In fact, if there is no other processing here, you could accomplish all of that using a messaging only approach by just routing messages around ports.

    http://winterdom.com/
  • Posted by
    on Fri, Apr 28 2006 1:53 PM
    both operations are related to each other because i want to convert 1 flat file in folder A to many XML doc in folder C.I like to do this in the same project.

    flat file (folder A) which gives 1 XML doc (folder B) which in turn splits the XML doc in folder B and puts many XML doc in folder C.

    Any idea

    kavitha
  • Posted by
    on Fri, Apr 28 2006 1:56 PM
    [quote user=\"kavitha\"]both operations are related to each other because i want to convert 1 flat file in folder A to many XML doc in folder C.I like to do this in the same project.

    flat file (folder A) which gives 1 XML doc (folder B) which in turn splits the XML doc in folder B and puts many XML doc in folder C.

    Any idea

    kavitha


    In the same project does not mean a single orchestration, necessarily. The only way you could accomplish this with a single orchestration would be through correlation, but it seems like this might be complex in your scenario (but only you can judge that).

    http://winterdom.com/
  • Posted by
    on Fri, Apr 28 2006 2:10 PM
    Thanks for your fast reply.

    Can u explain me in detail : In fact, if there is no other processing here, you could accomplish all of that using a messaging only approach by just routing messages around ports.

    kavitha
  • Posted by
    on Fri, Apr 28 2006 2:19 PM
    [quote user=\"kavitha\"]Thanks for your fast reply.

    Can u explain me in detail : In fact, if there is no other processing here, you could accomplish all of that using a messaging only approach by just routing messages around ports.

    kavitha


    You could set it up like this:

    1- Create a receive port with a FILE receive location on folder A that contains your custom receive pipeline with the FF disassembler. Let's call this Receive Port A_RP. This will receive your flat file and publish an XML message to the message box.

    2- Set up a new Send Port with the file adapter to folder B. Now, add a filter expression to this port with the term \"BTS.ReceivePortName = A_RP\". This will cause all messages being published from receive port A_RP to be routed to this port, which means your XML message generated from the Flat File will be saved on this folder. You could potentially apply a map either here or on the original A_RP to retrieve it.

    3- Set up a new Receive Port (let's call it B_RP) with a FILE receive location on folder B. You'll configure this with your Receive Pipeline that uses the XML disassembler properly configured with your Envelope and Document schemas so debatching can occurr.

    4- Set up a new Send port with the file adapter to folder C, and set up a filter expression \"BTS.ReceivePortName=B_RP\".

    That's it.

    http://winterdom.com/
  • Posted by
    on Sat, Apr 29 2006 4:26 AM
    Tomas,
    The only problem with this scenario is you will lose the document in folder B as it will be deleted by the file adapter on the B_RP receive port.

    It would as simple to use the FFDASM to debatch the message on A_RP.
  • Posted by
    on Sat, Apr 29 2006 12:14 PM
    [quote user=\"greg.forsythe\"]Tomas,
    The only problem with this scenario is you will lose the document in folder B as it will be deleted by the file adapter on the B_RP receive port.

    It would as simple to use the FFDASM to debatch the message on A_RP.


    Greg,

    that's true, but it seemed to me the poster was only interested in the final result anyway, but I might be wrong about that.

    Doing the debatching directly using the FFDASM sounds like a good idea as well, if his format allows.

    http://winterdom.com/
  • Posted by Anonymous
    on Mon, May 1 2006 3:29 PM
    thanks everybody for the replies.
    can u explain me what is debatching directly using the FFDASM.
    Edit tags
    Edit
  • Posted by
    on Mon, May 1 2006 3:50 PM
    [quote user=\"Anonymous\"]thanks everybody for the replies.
    can u explain me what is debatching directly using the FFDASM.


    It basically means you can get the Flat File Disassembler to split the incoming flat file into multiple XML messages (one per record), similar in concept to how the XML Disassembler can do (though they work very differently). This would save a step in your processing logic.

    Stephen W Thomas has several examples and documents on this topic, here are a few relevant ones:

    http://geekswithblogs.net/sthomas/archive/2004/12/17/17965.aspx
    http://www.biztalkgurus.com/Samples/Flat-File-Disassembler-Pipeline.html
    http://www.biztalkgurus.com/Labs/Sequentail-Message-Convoy-Flat-File.html

    http://winterdom.com/
    • Reply
    • Page 1 of 1 (10 items)