Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Forums Home > BizTalk Server Forums > BizTalk Server General > BAM Alerts in multicomputer biztalk configuration problem
Ask a questionAsk a question
Search Forums:
 

AnswerBAM Alerts in multicomputer biztalk configuration problem

  • Tuesday, November 03, 2009 1:13 PMamarax Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello everybody. I'm trying to configure BAM Alerts in multicomputer environment. Fist biztalk server configures well, but when I try to configure BAM Alerts for second server I got error message for "Prefix for Alerts Database"  and "SQL Server for Alerts" fields

    "The Database BAMAlertsNSMain already exists on <SqlServerName>. Please specify different database name or select a different server (BAMTools)"

    I only found post in internet to leave account field empty when configuring BAM Alerts for existing alerts database but it doesn't help.

    I also can configure NS services manually through nscontrol.exe console and register NS windows services through sc.exe but it doesn't display in biztalk configuration console - it looks like BAM Alerts isn't configured. And some features like notification folder and mail server address left unpopulated on this second biztalk server

    Does anyone have an idea how to configure BAM Alerts in multicomputer environment appropriately?

    thanks!

     

Answers

  • Wednesday, November 18, 2009 11:59 AMamarax Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Yes, I followed this instruction, it didn't work.
    Finally I discovered the problem. The problem is that BAM alerts configuration is somehow transparent from one biztalk host instance to another. If you unconfigure BAM Alerts on first machine it will be unconfigured on the second and vice versa. So just pay attention to both servers in case of problems with BAM configuration.

    And also unconfigure feature actually doesn't unregister or delete NS instances and DBs. use nscontrol delete/unregister to completely remove all configuration artefacts from DB and biztalk servers before reconfigure BAM Alerts and try to follow this mentioned instruction.
    • Marked As Answer byamarax Wednesday, November 18, 2009 11:59 AM
    •  
     

All Replies

  • Wednesday, November 04, 2009 1:36 AMTariq Majeed Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi,

    Did you follow the below instructions from installation guide while configuring BAM tools on your second computer.  Please verify that you did not miss anything.

    When configuring the subsequent BizTalk groups, do the following in the BizTalk Server Configuration Wizard:

    a.   Select BAM Tools and then select the Enable Business Activity Monitoring tools and Enable Analysis Services for BAM aggregations check boxes.

    b.   Change the Server Name and Database Name of the BAM data stores to match the same names used when configuring the first BizTalk group.

    c.   Select BAM Alerts and then select the Enable SQL Notification Services for BAM alerts check box.

    d.   Change the service account for BAM Alerts to have a blank user name and password.

    e.   Change the BAM Alerts SMTP Server, BAM Alerts File Location, SQL Server for Alerts Database, and Prefix for Alerts Database Names to match the same names used when configuring the first BizTalk group.

    Note:

    The same Primary Import Tables (PIT) can be used but with different BAM Archive, BAM Analysis, and Star Schema databases. However, this will affect all groups pointing to the same PIT.

    3.   Select BAM Portal, and then select the Enable BAM Portal check box.

    Note:

    All the fields on this screen are read-only because there is a one-to-one relationship between the BAM Primary Import database and the BAM portal. Multiple BizTalk groups share the same BAM portal when configured against the same BAM databases.

    4.         Click Apply Configuration.

    Regards,

    Tariq Majeed
    Please mark it as answer if it helps
     
  • Wednesday, November 18, 2009 11:59 AMamarax Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Yes, I followed this instruction, it didn't work.
    Finally I discovered the problem. The problem is that BAM alerts configuration is somehow transparent from one biztalk host instance to another. If you unconfigure BAM Alerts on first machine it will be unconfigured on the second and vice versa. So just pay attention to both servers in case of problems with BAM configuration.

    And also unconfigure feature actually doesn't unregister or delete NS instances and DBs. use nscontrol delete/unregister to completely remove all configuration artefacts from DB and biztalk servers before reconfigure BAM Alerts and try to follow this mentioned instruction.
    • Marked As Answer byamarax Wednesday, November 18, 2009 11:59 AM
    •