Friday 21 June 2013

Configuration of BizTalk Business Solution across Global Organization

There are four approaches that are helpful in spreading your business processes globally. These are Log Shipping to Warm Standby, independent BizTalk server groups, the geologically isolated servers in the same BizTalk group and BizTalk Database Stretch Failover Cluster approach. The Log Shipping to Warm Standby approach can be followed without any difficulty and you can spread the business processes internationally quite speedily.
Another one is the independent BizTalk server groups. This comprises of two different groups, both of them executing the business processing for varied applications. If you incorporate load balancing from a hardware alternative you obtain the extra advantage of ensured complete utilization of your infrastructure. 
Then there is also to have the geologically isolated servers in the same BizTalk group. The real negative aspect is the layoff between the SQL server and the BizTalk servers administering the databases. By making use of the rapid speed dedicated links, one can overcome this problem. The link that is weak here is the SQL Server. If this link is lost, then the link with the BizTalk will also most probably be lost, thus affecting the BizTalk server performance. If the network connection is fast, you will be able to log ship across it and get a hold of somewhat okay idleness.
The last one and the most innovative is the BizTalk Database Stretch Failover Cluster approach that is the solution for the major concern of the geographic redundancy of the BizTalk development server, which is the SQL Server. SAN mirroring is the means for this that must be synchronous and hold up atomic synchronous writes. This is an awfully costly approach as it demands that both the networks must run on fiber speeds and merchant specific mirroring attributes in your SAN. 

No comments:

Post a Comment