Envelope and SOAP adapter

Home Page Forums BizTalk 2004 – BizTalk 2010 Envelope and SOAP adapter

Viewing 1 reply thread
  • Author
    Posts
    • #14903

      You need to create the [i:db58ebdc04]envelope[/i:db58ebdc04] and[i:db58ebdc04] document [/i:db58ebdc04]schemas.
      Create an orchestration to receive a [i:db58ebdc04]document[/i:db58ebdc04] message.
      Run the Biztalk Web Service Publishing wizard and publish the [i:db58ebdc04]envelope[/i:db58ebdc04] schema as an web service
      If you publish the orchestration as a web service, the wsdl generated will expect a message of the same type that will be received by the orchestration which is [i:db58ebdc04]document[/i:db58ebdc04].

      • #14904

        You have set up the send port to subscribe to the messages published by the receive port. The message will pass directly from the receive port to the send port with no orchestration involved

        You need to remove the send port filter, bind the orchestration receive port to the physical receive port and the orchestration send port to the physical send port.

    • #14902

      Hi greg.forsythe,

      I did exactly what you described. I made my receive Port as SOAP transport (for example: receive port name is RECV_Soap) and Send Port as File Transport. If I don’t set the Send Port filter (BTS.ReceivePortName == \”RECV_Soap\”), I won’t be able to receive the SOAP XML envelope. One other odd thing is that I always receive the XML output (from the SEND port) exactly as SOAP envelop as if the message has not gone through any orchestration manipulation.

      Please Help!!
      Thank you.

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