The scenario outlined in this document gives you a basic example of how to setup BAM (Business Activity Monitoring) in a multi-computer environment. This articles applies to BizTalk Server 2010 and BizTalk Server 2013.
This scenario uses a single physical server that runs on Windows Server Hyper-V. On this platform, you host three virtual machines (Server 1,
Server 2 and Server 3) having the same operating system. The following table describes the roles of three servers that are used in this scenario.
BizTalk Runtime Server
BizTalk BAM Server
When you configure SSO server settings and BizTalk Group in the BizTalk Server Configuration tool, BizTalk Server typically creates four databases (BizTalk Server Management database, MessageBox databases, Tracking database, and SSO database) on the SQL
Server that hosts the configuration database.
BizTalk BAM Server (Server 2): The BizTalk BAM Server has the major BizTalk Server BAM components installed and configured. The BAM components depend on SQL Server components. Therefore, they must also be installed on this server. One important
thing to note is that the BAM Server has to be a BizTalk member server in a BizTalk Group. This means that it has to join a BizTalk group.
The following table describes the BizTalk Server 2010 and SQL Server 2008 R2 software components that you have to install in Server 1, Server 2 and Server 3.
As a part of multi-computer environment, while configuring BizTalk Runtime Server (Server 1) and BizTalk BAM Server (Server 2) you need to select the Custom Configuration option in the BizTalk Server Configuration tool.
Consider the following before you configure BAM:
You must use domain accounts for a multi-server BizTalk Server configuration. BizTalk Server supports domain group and user accounts in both single and multiple computer configurations.
To use domain accounts for a multi-server BizTalk Server configuration, you must do that following:
To make it easier to explain the security configuration, this document uses a fictitious domain name called “Contoso”, and the password is pass@word1 for all the accounts. You must replace them with the actual domain name and password during the installation
and configuration. A default installer account called “BTSlabs” is used to configure the servers/workstations.
The following table lists the Windows groups the domain administrator needs to create for the SQL Server configuration in Server 3. These group accounts can be either global domain accounts or universal domain accounts.
This is the service account for running BizTalk Server service.
BizTalk Server service.
To facilitate transactions between SQL Server and BizTalk Server, you must enable TCP/IP and Named Pipes in SQL Server (Server 3).
To enable TCP/IP and Named Pipes
To facilitate transactions between all the three servers (Server 1, Server 2 and Server 3), you must enable Microsoft Distributed Transaction Coordinator (MS DTC) and configure Windows Firewall with Advanced Security on all
the three servers. To enable MS DTC and configure Windows Firewall with Advanced Security:
To configure BizTalk Runtime Server (Server 1)
Database server name
Server 3 (the host name of the SQL Server)
Contoso\SSOService (Typically a generic BizTalk Server service account is used here. Because you only configure SSO, the SSO Service account is used here.)
Enterprise Single Sign-ON Service: Account
SSO Administrator(s): Windows Group
Create In-Process Host and Instance
BizTalk Host Instance Account
BizTalk Host Instance Account: password
To configure BizTalk BAM Server (Server 2)
Server 3 (the host name of the SQL Server where the master secret server is configured)
Service credential: User name
Service credential: Password
Enable Enterprise Single Sign-On on this computer
Join an existing SSO system
Data stores: Server Name
Enable BizTalk Server Group on this computer
Join an existing BizTalk Group
BizTalk Management Database: Server Name
Server 3 (the host name of the SQL Server)
Register the BizTalk Server runtime components
Enable Business Activity Monitoring tools
Enable Analysis Services for BAM aggregations
BAM Primary Import Database: Server Name
Server 3 (the SQL Server host name)
Enable SQL Notification Services for BAM alerts
BAM Alerts SMTP Server
(the SMTP server that will be used to send the BAM alerts.)
Enable BAM Portal
BAM Management Web Service user
BAM Application Pool Account
Read suggested related topics: