In Most of the Project development, BAM is always chosen as second phase. In Existing BizTalk Project, BAM will add as an additional layer to the solution.
In this blog We are explaning about BAM installation in Multi server Environment. The below BAM installation steps assumes that BizTalk is already installed and configured. To install BAM on BizTalk Servers, we need to again run the BizTalk server setup file on all BizTalk Servers and follow the below steps
Note: The Log on User account to install and configure BAM should have admin rights on SQL server and Biztalk both.
- When we run the set-up file, below page will be popup.
- Click on Install Microsoft BizTalk Server 2013 R2
- Select Modify as below:
- Select Portal Component along with all others Component, which had already installed on the machine.
Note: Please select all components which are already installed otherwise It will remove those component from the BizTalk Server and then we need to install all the components again.
- Select all BAM Component in Additional Software as Below:
- Click Next and install.
As a part of multi-computer environment, while configuring BAM, we need to select the Custom Configuration option in the BizTalk Server Configuration tool on each Biztalk Server in the group.
Here we assume that Biztalk Server is already installed and configured, we just need to add BAM Tool and BAM portal Configuration on the BizTalk Server. BAM also requires the following:
- SQL Server Analysis Services (SSAS)
- SQL Server Integration Services (SSIS)
- SQL Server Database Mail or SQL Server Notification Services (SSNS)
To configure BAM
- Click Start, point to All Programs, point to Microsoft BizTalk Server, and then click BizTalk Server Configuration.
- In the left pane, click BAM Tools, and then enter or select the following values:
|Enable Business Activity Monitoring tools||(selected)|
|Enable Analysis Services for BAM aggregations||(selected)|
|BAM Primary Import Database: Server Name||the SQL Server host name|
|BAM Primary Import Database: Database Name||the default name is BAMPrimaryImport|
|BAM Archive Database: Server Name||the SQL Server host name|
|BAM Archive Database: Database Name||the default name is BAMArchive|
|BAM Analysis Database: Server Name||the SQL Server host name|
|BAM Analysis Database: Database Name||the default name is BAMAnalysis|
|BAM Star Schema Database: Server Name||the SQL Server host name|
|BAM Star Schema Database: Database Name||the default name is BAMStarSchema|
Screenshot as below:
Note: The service account used for the OLAP service should have db_datareader permissions on the BAM Star Schema database.
- In the left pane, click BAM Alerts, and then enter or select the following values (Optional).
BAM alerts require SQL Server Database Mail , and BAM tools to be enabled.
|Enable SQL Notification Services for BAM alerts||(selected)|
|BAM Alerts SMTP Server||(the SMTP server that will be used to send the BAM alerts.)|
|BAM Alerts File Location||(the network share that will be used to store the BAM alerts.)|
Note : We must manually create this share before BAM alerts can store the files.
|SQL Server for Alerts Databases||the name of the SQL Server|
|Prefix for Alerts Database Names||(a prefix that will be used for the alerts databases)|
Note: Do not install BAM Alerts unless you have a SMTP server available and planning to use BAM Alerts feature. SKIP installation of BAM Alerts by Unchecking the box in case it is already checked.
- In the left pane, click BAM Portal, and then enter or select the following values. In case you have not created domain groups for BAM , create the below three domain groups to control access to BAM:
- (domain)\BAM Portal Users
|Enable BAM Portal||(selected)|
|BAM Management Web Service user||(domain)\BAMMgmtWSUser|
|BAM Application Pool Account||(domain)\BAMAppPoolUser|
|BAM Portal Users||(domain)\BAM Portal Users|
|BAM Portal Web Site||Default Web Site|
Note: BAM Management Web Service user and BAM Application Pool Account can be service account but service account will have admin access on BizTalk server.
Screen Shot as below which uses a Bam Portal users group as everyone which is not recommended in production environments and create a separate “BAM Portal Users” in domain.
- Click Apply Configuration.
- On the Summary page, to apply the configuration, click Next.
- Verify that the Configuration Result is Success, and then click Finish.
- Close Microsoft BizTalk Server 2013 R2 Configuration.
2. BAM Portal Configuration
After BAM Configuration with BizTalk Server Configuration. We need to check BAM Portal and config setting (if Require) on IIS.
Select BAM in Left side and open Authentication in Right side of IIS window as mentioned below screenshot:
Now Select Window Authentication and Click on Provider.. as mentioned in Below Screenshot.
Note: Only Enable ASP.NET Impersonation and Windows Authentication.
Select NTLM and Click Move Up Button. NTLM should be the first in the list of Providers
When we browse BAM Portal, it will open as below:
Note: BAM Portal works on Internet Explorer. For Chrome , a separate Extension IE tab is required.
|Installation of BAM||http://go.microsoft.com/fwlink/p/?LinkID=208597|
|Installation of BizTalk||https://msdn.microsoft.com/en-us/library/jj248681.aspx|
|Installation & Configuration Issue||https://blog.sandro-pereira.com/tag/bam/|