HTTP Adapter – Handling a Response

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › HTTP Adapter – Handling a Response

Viewing 1 reply thread
  • Author
    Posts
    • August 18, 2009 at 2:44 PM #23053
      community-content

        I’ve followed the HTTP Solicit-Response example from the SDK and got it working up to handling the response.  Using WireShark I can see that a response of 200 to returned from the url I am sending to, however the response is a string, not an xml document.

        Must the response be in the form of an xml document?  If the response can be a string, how do I handle the return value so that it’s available to an orchestration?

      • August 19, 2009 at 4:53 AM #23057
        community-content

          Yes you can handle the returned string.
          You can use a flat file disassembler in the receiving pipeline to turn it into an Xml document. This would be useful if the string contained a number of fields that you want to split out.

          You could possibly use a pass-thru pipeline and declare an orchestration message of type System.String and receive this message. Never tried this.

          You could even write your own pipeline component to convert the string into some message format.

          • August 20, 2009 at 11:30 AM #23072
            community-content

              Thanks for the reply.

              I’ve implemented a receive pipline with a Flat File Disassembler and within the orchestration can access the content that is in the body of the HTTP response.

              So now I need to access the return code from the response, how can I do that? 

              • August 20, 2009 at 2:28 PM #23076
                community-content

                  You could try the HTTP.ResponseStatusCode message property. Not sure if it makes it into the HTTP.InboundHttpHeaders message property

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