Best Practices for Configuring BizTalk Server
This topic lists best practices that you should follow as you perform operational readiness procedures for BizTalk Server.
Configure BizTalk hosts and host instances
Separate sending, receiving, processing, and tracking functionality into multiple hosts. This provides flexibility when configuring the workload and enables you to stop one host without affecting other hosts.
For more information, see Configuring Hosts and Host Instances.
Configure a dedicated tracking host
Use a dedicated host that does nothing but host tracking. This prevents hosting tracking from having an impact on the performance of other BizTalk artifacts running in the same host. It also allows you to stop other hosts without interfering with tracking.
The tracking host should be run on at least two computers running BizTalk Server (for redundancy in case one fails).
For more information, see Configuring a Dedicated Tracking Host.
Implement a BizTalk application upgrade and versioning strategy
If you need to support long-running orchestrations, and/or you need to perform BizTalk application deployments with no BizTalk application downtime, then you need to implement and practice a solid, end-to-end BizTalk Server versioning strategy for the different versioning scenarios.
If you need to support long-running orchestrations, side-by-side deployments, or no-downtime upgrades, then you should implement an assembly versioning and packaging strategy that includes factoring.
For more information, see Upgrading and Versioning Strategies for Applications.
Script your BizTalk application deployment
BizTalk application deployments should be scripted where possible. You should document with detailed steps anything that you do not script.
For more information, see Using Scripts to Deploy Applications.