Clustering Receiving Hosts

BizTalk Server provides functionality that allows you to configure a BizTalk Host as a clustered resource within a Windows Server cluster group. Host cluster support is provided to support high availability for integrated BizTalk receive adapters that should not be run in multiple host instances simultaneously, such as the FTP or SFTP receive handler or, under certain circumstances, the POP3 receive handler. Host cluster support is also provided to ensure transactional consistency for messages sent or received by the MSMQ adapter in scenarios that require that the MSMQ service is clustered.

Note

Host clustering is available only with BizTalk Server Enterprise Edition.

Note

Before you can cluster a BizTalk Host you must have configured at least two BizTalk Server computers in a BizTalk group as members of a Windows Server cluster. For more information about configuring a Windows Server cluster, see Windows Server 2008 Clustering Documents, Whitepapers, Webcasts, Groups (https://go.microsoft.com/fwlink/?LinkId=156818).

BizTalk Host cluster support is available to provide high availability for some of the integrated BizTalk adapters: the FTP adapter, the SFTP adapter, the MSMQ adapter, the POP3 adapter, the SQL adapter, and the SAP adapter. Host cluster support is also provided so that there is high availability for running a single instance of an adapter for purposes of ordered delivery.

All of the BizTalk adapter handlers can be run in a clustered host, but there is no benefit from running adapter handlers in a clustered host except as described below. If your processing requirements include any of the scenarios described in the section below, then you should run adapter handlers in a clustered host. For detailed steps of setting up BizTalk Server clusters, see BizTalk Server Clustering.

Scenarios for Running Adapter Handlers in Clustered Hosts

If your processing requirements include any of the scenarios listed below, then you should run adapter handlers in a clustered host.

See Also

Scaling Out Receiving Hosts Scaling Out Processing Hosts Scaling Out Sending Hosts