none
Propagating SOAP:Fault through HTTP Receive Location/HTTP Send Port scenario. RRS feed

  • General discussion

  • Hi.

    I have a very simple setup:

    • A client posting data to the BizTalk Server.
    • A 2-way HTTP Receive Location: http://server1/BTSHTTPReceive.dll
    • A 2 way HTTP Send Port: http://server2/service.asmx
    • A simple filter on the send port, which picks up messages submitted on the receive port.

    Now, if the service on server2 cannot authenticate the client sending data to the receive location (credentials contained in the soap-header) it returns an HTTP status code 500 - Internal Server Error and a SOAP:Fault message. However, this message is not routed back to the client but instead interpreted by the BizTalk Server.

    Is there a simple way to return the full message + status code to the client?

    Or do I have to consider using WCF-adapters instead? The problem with using WCF-adapters in my simple subscription based scenario is, that the credentials in the soap:header are stripped by the BizTalk Server on receive and are not forwarded to the service on server2. I really would like to keep it as simple as possible, without using Orchestrations or custom pipelines.

    Thank you,

    /Jakob Borg

    Friday, August 20, 2010 10:36 AM

All replies

  • Hi jaffse,

    So, when the server 2 fails to authenticate the client, it hydrates the orchestration? Doy ou have control over server2 - I mean you can change configuration settings on server 2?

     


    Luis Diego Rojas. http://icomparable.blogspot.com
    MCP, MCTS Biztalk Server
    Monday, August 23, 2010 2:56 PM