You can use this check list as a guide to answer the question, “I’ve configured BizTalk Server, now what?” It includes items that new BizTalk environments may miss.
- Configure the Backup BizTalk Server SQL Agent job. This job backs up BizTalk databases and makes disaster recovery possible. It also helps maintain database sizes—such as the BizTalkMsgBoxDb size—by doing a full backup daily, backing up the transaction log, and truncating the transaction log.
How to Configure the Backup BizTalk Server Job
- Configure the DTA Purge and Archive SQL Agent job. This job helps maintain the BizTalkDTADb database by purging (and archiving) older data.
How to Configure the DTA Purge and Archive Job
Archiving and Purging the BizTalk Tracking Database
- Create a dedicated Tracking host. The Tracking host moves tracking data from the BizTalkMsgBoxDb database to the BizTalkDTADb database. Because of performance implications, the Tracking host should only be used for this function.
Configuring a Dedicated Tracking Host
- Separate receive locations into a host, separate orchestrations into a host, and separate send ports into a host. If there is an orchestration that might use high memory, put it into its own host.
Providing High Availability for BizTalk Hosts
- Check Group Membership. Determine who will administer BizTalk (stop/start a host, add a receive location, enable/disable tracking) and who needs access to monitor BizTalk (start/stop an application, query in Group Hub). Give the users the appropriate rights in BizTalk Server and in SQL Server.
Managing BizTalk Server Security
Minimum Security User Rights
- Deploy any applications, and bind the artifacts to the correct host.
- Determine if tracking needs to be enabled on the orchestrations, send ports, receive ports, schemas and pipelines. If this data will not be needed, disable tracking.
How to Disable Tracking
- Get to know the various tools available to help:
BizTalk Server Best Practices Analyzer V1.2 - English
BizTalk Server Documenter
BizTalk MessageBox Viewer
