locked
Best practices for BizTalk communication to partners over the internet RRS feed

  • Question

  • Hi all,

    I'm rather new to BizTalk but we are currently in the process of making some design decissions. For our new EAI layer, we have choosen BizTalk. We need to communicate with partners over the internet. Most communication will be done via SOAP or SFTP. At our company we already have a DMZ in place.

    What is the best practice to handle the SOAP communication with our partners? We have been looking at 2 scenarios:

    1. Publish the BizTalk orchestrations as WCF services and give partners access to these WCF services
    2. Add a separate web server to the DMZ that transforms the incomming SOAP messages to files. Outgoing mesages to our partners would come from BizTalk.

    Since I don't have a lot of experience I would like to have some feedback on this. One advantage that I see for solution 2 is that the partner is not impacted when our BizTalk application is down. One of the disadvantages is that theire will be delays.

    Thanks in advance,

    Geert


    Geert Verhoeven (http://geertverhoeven.blogspot.com)
    Thursday, November 4, 2010 5:53 PM

Answers

  • No, not really because you would need to implement every change on the WCF services again on the second server. The advantage of an ISA server that it represents always the correct WCF service as soon as it's been deployed on your internal BizTalk server.
    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://pi.hauth.me

    Thursday, November 4, 2010 6:55 PM

All replies

  • Hi Geert,

     

    I have two suggestions for you:

    The most common solution today is putting an ISA proxy in the DMZ and making all WCF services available to the outer world via a secured https connection. There is no way of deploying the WCF services to another server and noone wants a BizTalk server in the DMZ. So the ISA server is the best way for this.

    But looking at Azure AppFabric Messaging Bus you could use this technique. Create a connection point in Azure for HTTP oder HTTPS and on the other side connect you BizTalk using the net tcp relay bindings delivered with BizTalk 2010. Richard has a good blog post to start with here: http://seroter.wordpress.com/2009/07/19/sending-messages-from-azure-service-bus-to-biztalk-server-2009/


    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://pi.hauth.me

    Thursday, November 4, 2010 6:18 PM
  • Hi Oliver,

    Thanks for the help. Azure is not a possible solution for us since this will be the core of our company and we expect a high load. Also we prefer to have everything within our own datacenter.

    But the ISA solution is definitely something I will look at. So you don't prefer the solution which puts an additional server in the DMZ that passes the incomming messages as files? Also, with the WCF services, do you mean the published orchestrations or passthrough WCF services?

    Geert


    Geert Verhoeven (http://geertverhoeven.blogspot.com)
    Thursday, November 4, 2010 6:32 PM
  • No, not really because you would need to implement every change on the WCF services again on the second server. The advantage of an ISA server that it represents always the correct WCF service as soon as it's been deployed on your internal BizTalk server.
    If you like my post or consider it as a valid answer, please use the buttons to show me - Oliver

    http://pi.hauth.me

    Thursday, November 4, 2010 6:55 PM