Skip to content

Latest commit

 

History

History
59 lines (38 loc) · 6.51 KB

creating-a-highly-available-biztalk-server-environment.md

File metadata and controls

59 lines (38 loc) · 6.51 KB
description title ms.custom ms.date ms.service ms.reviewer ms.suite ms.topic
Learn more about: Creating a Highly Available BizTalk Server Environment
Creating a Highly Available BizTalk Server Environment
06/08/2017
biztalk-server
article

Creating a Highly Available BizTalk Server Environment

This section describes how to provide high availability for the data and communications in Microsoft [!INCLUDEbtsBizTalkServerNoVersion] when integrating disparate systems and applications. [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] focuses on recovering functional components that might disrupt availability in a [!INCLUDEbtsBizTalkServerNoVersion] deployment.

To demonstrate high availability in [!INCLUDEbtsBizTalkServerNoVersion], you have to apply failure and measure the product's effectiveness in recovery. A highly available [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] deployment that provides high availability involves implementing redundancy for each functional component involved in an application integration or business process integration scenario. [!INCLUDEbtsBizTalkServerNoVersion] simplifies the implementation of these scenarios by conceptually separating the data from the hosts that process the data. So providing high availability for [!INCLUDEbtsBizTalkServerNoVersion] involves running multiple host instances and clustering the [!INCLUDEbtsBizTalkServerNoVersion] databases, as follows:

  • Architecture for BizTalk Hosts [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] 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 [!INCLUDEbtsBizTalkServerNoVersion] 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.

Note

Highly-available environments are, by nature, multi-computer environments. When configuring [!INCLUDEbtsBizTalkServerNoVersion] in a multi-computer environment you must use domain user groups and accounts.

Because [!INCLUDEbtsBizTalkServerNoVersion] is built on Microsoft [!INCLUDEbtsWinSvr2k8] or [!INCLUDEbtsWinSvr2k8R2], and Microsoft SQL Server 2008, make sure that you deploy these products with high availability before configuring hosts for [!INCLUDEbtsBizTalkServerNoVersion]. The following links include information about providing high availability for these underlying products:

In This Section

See Also

Sample BizTalk Server High Availability Scenarios Using Windows Server Cluster to Provide High Availability for BizTalk Server Hosts2