Checklist: Configuring BizTalk Server
Follow these steps when preparing BizTalk Server for use in a BizTalk Server production environment.
| Steps | Reference |
|---|---|
| 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. |
| Make sure you adhere to and understand the maximum practical limits of memory usage for a BizTalk host instance. | Maximum Practical Limits of Memory Usage of a 32-bit BizTalk Host Instance |
| 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. |
| Setting SOAP, HTTP, and HTTP-based WCF Adapters Concurrent Connections | Apply IIS Configuration Settings |
| 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 BizTalk Server application deployments. | 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 - Managing Applications |
| Predefine processes for resubmitting messages and restarting workflows. | Establish and document a procedure to check for suspended service instances and take appropriate actions. In most BizTalk Server environments, this should be performed as a part of the daily maintenance of your BizTalk Server environment. For more information about performing daily maintenance checks, see Checklist: Performing Daily Maintenance Checks. |
| Define escalation paths for issues that may be encountered in a BizTalk Server environment. | - Determine roles and responsibilities - Define escalation process and paths - Define “short-circuit” processes and paths when necessary for “critical situation” scenarios - Define an escalation path for vendor issues, including Microsoft, other software vendors, hardware vendors (for example, servers, SAN, switches) |
| Adhere to certain considerations when using BizTalk Server on a 64-bit Windows operating system | Considerations While Using BizTalk Server on a 64-bit Windows Operating System |
| Adhere to the best practices for BizTalk Server settings. | Best Practices for BizTalk Server Settings |