A ‘Vanilla’ BizTalk installation is an installation of the BizTalk binaries on a server. Vanilla does not include configuration, management, rules or content databases. This document assumes you have run 'configframework /u' to remove the BizTalk configuration (see the post titled “Removing a BizTalk Configuration“ for details).
Note: You must restore a BizTalk server to vanilla to apply a different configuration file. The steps are outlined below.
Remove SQL Server Databases
The following list includes the default names for each of the SQL Server databases; if your installation used another naming convention, replace this list with your own:
- BAMPrimaryImport (BAM Primary Import database)
- BAMStarSchema: (Star Schema database)
- BizTalkDTADb (BizTalk Tracking database)
- BizTalkEDIDb (BizTalk EDI database)
- BizTalkHwsDb (HWS Administration database)
- BizTalkMgmtDb (Configuration database)
- BizTalkMsgBoxDb (BizTalk MessageBox database)
- BizTalkRuleEngineDb (Rule Engine database)
- TPM (Trading Partner Management database)
- BAMAnalysis (BAM Analysis database)
- BizTalkAnalysisDb (Tracking Analysis Server database)
- BizTalkEDIDb (BizTalk Base EDI database)
Note: Enterprise Single-Sign is omitted from this list and is addressed below.
Remove MSSQL Analysis Services Cubes
The following list includes the default names for each of the Analysis Services cubes; if your installation used another naming convention, replace this list with your own:
- BAMAnalysis
- BizTalkAnalysisDB
Remove BizTalk SQL Server Maintenance Jobs
BizTalk Configuration installs a series of database maintenance operations on a server. Remove the following jobs from the SQL Server:
- Backup BizTalk Server
- CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
- MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
- MessageBox_Message_Cleanup_BizTalkMsgBoxDb
- MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
- PurgeSubscriptionsJob_BizTalkMsgBoxDb
- TrackedMessages_Copy_BizTalkMsgBoxDb
- TrackingSpool_Cleanup_BizTalkMsgBoxDb
Remove BizTalk SQL Server Logins
BizTalk Configuration associates several Windows users to SQL logins. Remove the following logins (or their equivalents, if you gave them different names) from SQL Server:
- Domain\BizTalk Application Users
- Domain\BizTalk BAS Web Services Group
- Domain\BizTalk Isolated Host Users
- Domain\BizTalk Server Administrators
- Domain\BTServiceBASWeb
- Domain\BTServiceHWF
- Domain\BTServiceREU
- Domain\EDI Subsystem Users
- Domain\SSO Administrators
Determine Action for the Enterprise Single Sign-On Database
The Enterprise Single Sign-On database (default name SSODB) merits special attention.
- If the current server is the only server in the BizTalk group, SSODB can be removed when restoring the server to a vanilla state.
- If the current server is number 2-n of the BizTalk group, do not remove SSODB.
- If the current server is the first server in the group, it holds the master secret in SSODB. You can remove SSODB and restore the master secret from a backup (see the “Backing Up the Master Secret” post).
Note: do not remove SSODB unless you have specific needs for its removal, or are relocating the master secret to another database in the enterprise.