Best 'High Available' BizTalk Server Configuration. RRS feed

  • General discussion

  • For a blend for applications wherein a couple of applications exposing web API and some of them triggered from SQL and routing outbound messages to third party servers such as SFTP.

    To create an 'highly available' and a 'performant' environment, I could think of the configuration stated below.

    1. 'N' BizTalk nodes sharing 'BizTalk Group'.

    2. For Applications exposed as WCF services/Web API's, an NLB configured over the server nodes routing network traffic to appropriate servers.

    3. Optionally, unless required, multiple windows servers should be clustered enabling clustering at host level for adapters viz. FTP,SFTP,POP3,SQL,SAP,MSMQ; to ensure transaction consistency for the said adapters.


    Happy to look for better suggestions.

    Monday, October 8, 2018 11:55 AM

All replies

  • That is the official recommendation.   

    But have you actually defined a need for a highly available and performant environment.  e.g. you've been told that there isn't allowed to be much of a down time or you've measured the throughput of a single BizTalk Server and it isn't sufficient for the expected message load?

    If the answer to the above is no, then just have single BizTalk node and save yourself some hassle and cost of opperation/licencing.  If needed it is possible to add a second BizTalk node later on.   

    Monday, October 8, 2018 6:06 PM
  • Thanks Colin!
    Yes, that's a requirement for higher environments i.e UAT and PROD. Also, single node doesn't suffice the tested message load.
    Wednesday, October 10, 2018 6:42 AM