This section describes how to provide high availability for the data and communications in Microsoft BizTalk Server when integrating disparate systems and applications. BizTalk Server separates the data from the hosts that process the data, enabling you to resolve availability issues by scaling the databases and hosts independently.
Demonstrating High Availability
High availability for BizTalk Server focuses on recovering functional components that might disrupt availability in a BizTalk Server deployment.
To demonstrate high availability in BizTalk Server, you have to apply failure and measure the product's effectiveness in recovery. A highly available BizTalk Server deployment makes errors and failures transparent to external applications and systems, and makes sure that all services continue functioning correctly with minimal disruption.
Designing for High Availability
Designing a BizTalk Server deployment that provides high availability involves implementing redundancy for each functional component involved in an application integration or business process integration scenario. BizTalk Server simplifies the implementation of these scenarios by conceptually separating the data from the hosts that process the data. So providing high availability for BizTalk Server involves running multiple host instances and clustering the BizTalk Server databases, as follows:
Architecture for BizTalk Hosts BizTalk Server lets you separate hosts and run multiple host instances to provide high availability for key functions such as receiving messages, processing orchestrations, and sending messages. These hosts do not require any additional clustering or load-balancing mechanism because BizTalk Server automatically distributes workload across multiple computers through host instances. However, hosts running the receive handler for the HTTP and SOAP adapters require a load-balancing mechanism such as Network Load Balancing (NLB) to provide high availability.
Architecture for BizTalk Server databases High availability for the BizTalk Server databases typically consists of two or more database computers configured in an active/passive server cluster configuration. These computers share a common disk resource (such as a RAID5 SCSI disk array or storage area network) and use Windows Clustering to provide backup redundancy and fault tolerance.
Highly-available environments are, by nature, multi-computer environments. When configuring BizTalk Server in a multi-computer environment you must use domain user groups and accounts.
Because BizTalk Server is built on Microsoft Windows Server 2008 SP2 or Windows Server 2008 R2, and Microsoft SQL Server 2008, make sure that you deploy these products with high availability before configuring hosts for BizTalk Server. The following links include information about providing high availability for these underlying products:
High Availability – Always On Technologies, available at http://go.microsoft.com/fwlink/?LinkId=130376.
This whitepaper describes high availability features that are available with SQL Server 2008.
High Availability Solutions Overview, available at http://go.microsoft.com/fwlink/?LinkId=130377.
Introduces several high-availability solutions for SQL Server 2008 that improve the availability of servers or databases.
Windows Deployment Services Step-by-Step Guide, available at http://go.microsoft.com/fwlink/?LinkId=130379.
Contains step-by-step guidance for how to use the Windows Deployment Services role in Windows Server 2008.
Windows Server 2003 Deployment Kit: Planning Server Deployments, available at http://go.microsoft.com/fwlink/?LinkId=24433.
This book provides information about planning server storage, and information about designing and deploying file servers, print servers, and terminal servers in medium and large organizations.
Increasing Availability for BizTalk Server, available at http://go.microsoft.com/fwlink/?LinkId=130457.
Section of the BizTalk Server Operations Guide that describes ways you can increase the availability of your BizTalk Server system.