Publish/subscribe response from solicit-response send port

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Publish/subscribe response from solicit-response send port

Viewing 1 reply thread
  • Author
    Posts
    • July 6, 2008 at 5:47 PM #20076
      community-content

        All,

        I’ve got a solicit-response send port <SendPort1>, wich subscribes messages from MessageBox and runs a stored procedure (SQL adapter). The SP returns a response, which I want to publish to a MessageBox and subscribe by another send port <SendPort2>.

        But I want it to be done without orchestration. I tried to subscribe by port name using BTS.ReceivePortName=<SendPort1> in filter of <SendPort2>. It just does not work. I’ve got a route exception error.

        I tested the <SendPort1> by adding an archive component in receive pipeline – it returns a response with correct XML inside. It seems to me that the solicit-response <SendPort1> just does not publish the response to the MessageBox.

        I remember, I saw an article somewhere, explaining how to configure send/receive ports to get it working, bu cannot find it again.

        Nick

      • July 6, 2008 at 6:13 PM #20077
        community-content

          I found it out.

          It was so simple and I spent too much time to figure it out. So, for anyone else looking for the same solution, here is a trick:

          Use BTS.SPName property instead of BTS.ReceivePortName.

          Thanks to Saravana Kumar and his article http://www.digitaldeposit.net/blog/2006/12/biztalk-2006-soap-adapter-web-service.html

          Nick.

          • July 7, 2008 at 1:52 AM #20078
            community-content

              Nick,

              You could have also have subscribed to any of the promoted properties on the response message – BTS.MessageType (Namespace # Root Node Name) springs to mind in the first instance.

              Rgds, Nick.

              • July 9, 2008 at 5:25 PM #20103
                community-content

                  Hi Nick,

                  Thanks for that. I knew that was the best way, but in that particular case it was necessary to subscribe by port name.

                  Regards,
                  Nick

              • March 31, 2010 at 1:42 PM #24495
                community-content

                  I don’t know if someone will reply but I have a probleme with the same context:

                  The SQL adapter raised an error : The message does not have a valid correlation token.

                  Can someone help me?

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