Input and output folder

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Input and output folder

Viewing 1 reply thread
  • Author
    Posts
    • December 14, 2005 at 7:11 AM #12524
      community-content

        hi

        Can i use one folder as output of one orchestration and input of another orchestration?

        I have to consume result returned by one orchestration in another orchestration. So is it possible for me?

        Thanks

      • December 14, 2005 at 9:11 AM #12525
        community-content

          Look at using ‘Direct’ for passing data from one orchestration to another. I have to admit that I have not got the hang of it yet but the clue is in the port wizard. I think that you may have to filter on the receive shape in the second orchestration to get the subscription. I think that there are samples out there but I cant remember where. If I find one I will post.
          🙂

          • December 15, 2005 at 2:23 PM #12526
            community-content

              Hi

              We have used [b:ccb5b97a7e]Direct Binding [/b:ccb5b97a7e]in order to connect two orchestration. In this case we have use Looping structure in first orchestration and whatever output of one orchestration is given as a input to another orchestration.

              In second orchestration program we have used SQL adapter to call stored procedure. It takes input correctly but gives me error as
              [b:ccb5b97a7e]Publishing a batch of \”1\” message to message box database for the transfer adapter \”SQL\”[/b:ccb5b97a7e]

              Could you tell me how to overcome that error?

              Thanks in advanced

              • December 15, 2005 at 10:41 PM #12527
                community-content

                  So your second Orchestration gets started?

                  Sounds like a problem with the SQL Adapter. Are you sure that is set up correctly?

                  • December 14, 2005 at 10:07 AM #12528
                    community-content

                      With an input/output folder orchestration 1 publishes the message in the MesssageBox. A send port subscribes to this message and writes it to a file. A receive location reads the file and publishes to the MessageBox where orchestration 2 subscribes to the message.
                      Apart from the overhead of doing this you may hit file contention issues if your files are large.
                      Having orchestration 2 subscribe to the message published by orchestration 1 cuts out unnecessary work.
                      This is achieved by using Direct ports.
                      Care must be taken when using direct ports. If you declare a direct port in an orchestration by default it will subscribe to every message that matches the message type declared in the receive shape. You can add filters to that receive shape to subscribe to a subset of messages. You can filter on any promoted property in the message context.

                      • December 16, 2005 at 2:39 AM #12529
                        community-content

                          This error message is usually the first of a number of errors in the event log.
                          What other errors are in the event log

              • Author
                Posts
              Viewing 1 reply thread
              • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.