Biztalk high availability configuration method (Failover cluster + Server Load balancer)

Thank you very much for the two articles written by [chnking ].Biztalk 2009InWindows 2008 r2EnvironmentHigh Availability (clusterCluster)Deployment
OfArticleThe write is very detailed. As long as you do it step by step, it will not be a problem.

Recently, I also made a note based on the [chnking] Article.

My environment is host

CPU	I5-2300
Ram	8g
HD	500g
motherboard	Asus h67p
System	Windows 7 Professional 64bit
Virtual Machine	VMware station 7.1.4

 

4 Virtual Machine Environments

Windows Server 2003 R2 (SP2)

SQL 2005 Enterprise Edition (SP2)

Biztalk 2006 r2

One domain controller, two virtual SQL + BizTalk clusters, one separately installed BizTalk, and added extensions to BizTalk Group

Configure the cluster IP Address

No	Host	IP	Purpose	Description
1	adser	192.168.1.254	domain control
2	svr1	192.168.2.100	heartbeat
3		192.168.1.100	host node IP address
4	svr2	192.168.2.101	heartbeat
5		192.168.1.101	host node IP address
6	Bizcluster	192.168.1.99	Biztalk cluster IP Address	the same IP address can be used in a Windows Cluster
7	dtccluster	192.168.1.99	IP address of the DTC cluster
8	msmqcluter	192.168.1.99	MSMQ cluster IP address
9	sqlcluster	192.168.1.99	SQL cluster IP address
10	ssocluster		BizTalk cluster sharing
11	BizTalk host		BizTalk cluster sharing

 

Biztalk failover Cluster

According to the methods provided by [chnking], it is easy to configure the BizTalk cluster successfully,

This is the BizTalk AP mode. When a node encounters a problem, the system automatically transfers the node to another node.

Biztalk Load Balancing Mode

Biztalk has two load balancing modes,

One is completely automatically implemented by the system, that is, the AA mode. A BizTalk host corresponds to multiple host instances running at the same time, and the load is automatically rated on each physical host.

There is also a division of labor for processing. One host is responsible for receiving, one is responsible for sending, and the other is responsible for process processing. Of course, the so-called one can also be multiple

Add the BizTalk Group of the above two failover clusters to the third server (node), and naturally add n servers.

Install a new virtual machine, install BizTalk, add it to the domain, and configure BizTalk as the second in the cluster. After the configuration is successful (You need to exit the original two BizTalk instances from the cluster ),

 

Create a host for sending and receiving

With the host, you can choose to transfer the load to the selected service when creating the sending and receiving ports.