BAM Setup and Configuration https://docs.microsoft.com/archive/blogs/kkuo/feed.xml Blog for BizTalk Server 2006 Wed, 17 Apr 2019 03:24:23 GMT en-US hourly 1 Two new articles on BAM Configuration https://docs.microsoft.com/archive/blogs/kkuo/two-new-articles-on-bam-configuration Tue, 13 Jun 2006 17:38:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/06/13/two-new-articles-on-bam-configuration/ I've posted two new articles on BAM Configuration:

 

BAMTools Configuration error:  https://blogs.msdn.com/kkuo/articles/630026.aspx

Configuration Log FYI:  https://blogs.msdn.com/kkuo/articles/630024.aspx

]]> BAMTools Configuration error: Login failed for user '<domainuser>'. https://docs.microsoft.com/archive/blogs/kkuo/bamtools-configuration-error-login-failed-for-user-domainuser Tue, 13 Jun 2006 17:34:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/06/13/bamtools-configuration-error-login-failed-for-user-domainuser/ If you have this error message during BAM Tools configuration:

 

Microsoft (R) Business Activity Monitoring Utility Version 3.5.1409.0

Copyright (C) 2006 Microsoft Corporation.  All rights reserved.

 

ERROR: Failed to set up BAM database(s).

The database cannot be found.

Cannot open database requested in login 'BAMPrimaryImport'. Login fails.

Login failed for user '<domain\user>'.

 

Trace Young provided the solution for this error:

 

Possibly because of the following (from a 2004 KB)?

 

This behavior occurs if an .mdf file or an .ldf file already exists in the \Program Files\Microsoft SQL Server\MSSQL\data folder of your SQL Server that has the same name as the .mdf file or the .ldf file that the BizTalk Server 2004 Configuration Wizard is trying to create. The names of the .mdf file and the .ldf file that are created for the databases are derived from the name of the database that is specified in the BizTalk Server 2004 Configuration Wizard with an .mdf and an .ldf extension appended.

]]> Configuration Log FYI https://docs.microsoft.com/archive/blogs/kkuo/configuration-log-fyi Tue, 13 Jun 2006 17:33:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/06/13/configuration-log-fyi/

Location

Unless specified on the command line with the /l flag, the configuration log is located at %temp%\ConfigLog(MM-DD-YYYY HHhMMmSSs).log (MM-DD-YYYY HHhMMmSSs are the date and time that configuration was started).

 

Creation

The log is created immediately when BizTalk Server Configuration is started (instead of when the product is being configured).  It is written to while the user interacts with the UI, as well as during configuration.

 

Reading the log for BAM Configuration

The process flow for configuration generally follows the pattern:

 

1.  Building feature XML:  UI information is gathered.  Search for “Building feature XML for: <Feature Name>”.*

2.  Validating feature:  Data fields in the UI are validated.  This step is repeated whenever a field changes.  Search for “Validating feature: <Feature Name>”.

3.  Configuring/Unconfiguring feature:  Features whose data fields where changed in step 2 are configured (“Configuring feature: <Feature Name>”), or features selected for unconfiguration by the user are unconfigured (“Unconfiguring feature: <Feature Name>”).  Then, go to step 1.

 

* where <Feature Name> is “MOT”, “BAMTools”, or “BAMPortal”.

 

For more information on validation/configuration/unconfiguration errors, search for “error <Feature Name>”.

]]> 1 new article on BAM Configuration troubleshooting https://docs.microsoft.com/archive/blogs/kkuo/1-new-article-on-bam-configuration-troubleshooting Mon, 06 Mar 2006 19:55:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/03/06/1-new-article-on-bam-configuration-troubleshooting/ I've posted one new article on BAM Configuration troubleshooting:

BAM Runtime (MOT):  https://blogs.msdn.com/kkuo/articles/544910.aspx

]]> Troubleshooting in BAM Runtime (MOT) Configuration https://docs.microsoft.com/archive/blogs/kkuo/troubleshooting-in-bam-runtime-mot-configuration Mon, 06 Mar 2006 19:50:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/03/06/troubleshooting-in-bam-runtime-mot-configuration/ Q1.  When is BAM Runtime (MOT) configured?

A1.  BAM Runtime (MOT) is automatically configured when BizTalk Runtime is configured.

 

Q2.  How do I turn off BAM Runtime (MOT) Configuration?

A2.  In <INSTALL DIRECTORY>\ConfigMain.xml, delete the following:

 

…

    <Feature MSIFeatureName="MOT,BusActSvcs,BAMPortal,AdminTools,Development,BizTalkExplorer,HwsWebService" Name="WMI" ProductCode="{FFF25E7A-A7F7-4b10-9B70-042A6734D806}" ConfigObjProgID="MSEBiz.BtsCfg" DependentFeatures="Engine,BTSCfg;EDI;HwsRuntime;HwsWebService;BAMTools;BAMPortal;BusActSvcsTPM" SubscribedFeatures="BAMTools;BAMPortal;HwsRuntime;HwsWebService;EDI;RulesEngine">

…

    <Feature MSIFeatureName="Engine" Name="Engine,BTSCfg" ProductCode="{FFF25E7A-A7F7-4b10-9B70-042A6734D806}" ConfigObjProgID="MSEBiz.BtsCfg" DependentFeatures="" AdditionalFeatures="HwsBaseAssemblies;MOT;Engine">

…

    <Feature Name="MOT" ProductCode="{FFF25E7A-A7F7-4b10-9B70-042A6734D806}" ConfigObjProgID="MSEBiz.BAMConfigWizExt" DependentFeatures="">

    </Feature>

…

 

Then, re-start configuration.

]]> 2 new articles on BAM configuration https://docs.microsoft.com/archive/blogs/kkuo/2-new-articles-on-bam-configuration Wed, 18 Jan 2006 18:11:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/01/18/2-new-articles-on-bam-configuration/ I've posted two new articles on BAM Configuration:

Configuring Multiple BizTalk Groups to the same BAM Databases - https://blogs.msdn.com/kkuo/articles/514554.aspx
Notes on incrementally enabling and disabling BAM - https://blogs.msdn.com/kkuo/articles/514029.aspx

]]> Configuring Multiple BizTalk Groups to the same BAM Databases https://docs.microsoft.com/archive/blogs/kkuo/configuring-multiple-biztalk-groups-to-the-same-bam-databases Wed, 18 Jan 2006 17:53:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/01/18/configuring-multiple-biztalk-groups-to-the-same-bam-databases/ This article discusses how to configure multiple BizTalk Server Groups to point to the same BAM Databases.

1.  Configure a BizTalk Group, ‘A’.
2.  For Group A, configure BAM (Tools, Analysis, Alerts, Portal, etc) as one normally would for a single-group scenario.
3.  Configure a BizTalk Group, ‘B’.
4.  For Group B, open BizTalk configuration.
5.  Navigate to the BAM Tools page and enable BAM Tools.
6.  On the BAM Tools page, change the BAM databases to be the same names as the databases configured for Group A (Step 2).
7.  Navigate to the BAM Alerts page.
8.  On the BAM Alerts page, change the SMTP server, file location, server, and prefix fields to be the same values as configured for Group A (Step 2).
9.  On the BAM Alerts page, change the BAM Notification Services User to have a blank user name and password.

Note:  The user name and password should be blank because the true value of these fields is only discernable on the machine when BAM Alerts was originally configured.

10.  Navigate to the BAM Portal page and enable BAM Portal.  If you configure BAM Portal in Step 2, then all of the fields on the page will be read-only and blank.

Note:  The fields on the page are read-only and blank because there is a one-to-one relationship between the BAM Primary Import Table database and the BAM portal.  Multiple BizTalk groups therefore share the same BAM portal when configured against the same BAM databases.

Note that the steps for configuring BAM Analysis, Alerts, and Portal are optional.

]]> Notes on incrementally enabling and disabling BAM https://docs.microsoft.com/archive/blogs/kkuo/notes-on-incrementally-enabling-and-disabling-bam Tue, 17 Jan 2006 18:40:00 GMT https://blogs.msdn.microsoft.com/kkuo/2006/01/17/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).

     

    ]]>         2 new articles on BAM Multi-Machine Configuration https://docs.microsoft.com/archive/blogs/kkuo/2-new-articles-on-bam-multi-machine-configuration Tue, 11 Oct 2005 18:19:00 GMT https://blogs.msdn.microsoft.com/kkuo/2005/10/11/2-new-articles-on-bam-multi-machine-configuration/ I've posted two new articles on BAM Multi-Machine Configuration:

    BAM Tools:  https://blogs.msdn.com/kkuo/articles/479801.aspx
    BAM Portal:  https://blogs.msdn.com/kkuo/articles/479839.aspx

    ]]>         Multi-machine Minimal Installation for BAM Portal Configuration https://docs.microsoft.com/archive/blogs/kkuo/multi-machine-minimal-installation-for-bam-portal-configuration Tue, 11 Oct 2005 17:29:00 GMT https://blogs.msdn.microsoft.com/kkuo/2005/10/11/multi-machine-minimal-installation-for-bam-portal-configuration/ This article discusses the minimum pre-requisites for configuring the BAM Portal in a multi-machine scenario.

    Portal Minimal Install for SQL 2K SP4 and 2K5

    ]]>