Notes on incrementally enabling and disabling BAM
- When configuring BAM Tools for the first time for an existing BizTalk Group, the BizTalk Service must be restarted after BAM Tools configuration is complete. This is so that TDDS can be updated with the new connection string information for the BAMPrimaryImportTable database.
- If BAM Alerts is enabled or changed after BAM Portal has been configured, BAM Portal configuration should be run again in order to register SQL NS for the portal. Note that BAM Portal configuration must be re-run (re-configured without changes) on the server that hosts the BAM Portal website.
- Removing BAM Tools from a group and/or un-configuring BAM Tools does not automatically un-configure BAM Portal. This ensures that the portal is not un-configured when other groups are still using it, which occurs when multiple BizTalk groups point to the same BAM databases. Accordingly, to remove BAM Tools from a group and un-configure BAM Portal, follow these steps:
1. Un-configure BAM Portal (Actions > Unconfigure Features... > BAM Portal).
2. Remove BAM Tools from the BizTalk Group (On the BAM Tools page, select the Remove checkbox).
3. Un-configure BAM Tools from the local machine (Actions > Unconfigure Features... > BAM Tools).