BAM Installation and Configuration Guide

Microsoft Corporation
Published: May 2008

Summary
This document provides guidelines for installing and configuring Microsoft BizTalk Server 2006
in a multi-server environment with the Business Activity Monitoring (BAM) component in
consideration. This guide can also be used as a reference for installing and configuring BAM on a
single BizTalk Server.

Copyright
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. Unless otherwise noted, the companies, organizations, products, domain
names, e-mail addresses, logos, people, places, and events depicted in examples herein are
fictitious. No association with any real company, organization, product, domain name, e-mail
address, logo, person, place, or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without limiting the rights under
copyright, no part of this document may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), or for any purpose, without the express written permission of Microsoft
Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual
property rights covering subject matter in this document. Except as expressly provided in any
written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, BizTalk, SQL
Server, and Excel are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
All other trademarks are property of their respective owners.

Contents
BAM Installation and Configuration Guide......................................................................................5
Overview..................................................................................................................................... 5
Considerations When Installing and Configuring BAM................................................................5
Deployment Topology............................................................................................................... 5
Understanding BAM Components............................................................................................ 6
Security and Accounts.............................................................................................................. 7
Step 1: Installing and Configuring the SQL Server Runtime Environment (System
Administrator)........................................................................................................................... 7
Hardware Requirements.......................................................................................................... 8
Software Requirements............................................................................................................ 9
Domain Accounts..................................................................................................................... 9
Installation and Configuration Tasks.......................................................................................10
Task 1.1: Add Windows Component..................................................................................10
Task 1.2: Configure MS DTC............................................................................................. 11
Task 1.3: Install the SQL Server 2005................................................................................12
Task 1.4: Install SQL Server 2005 SP2..............................................................................14
Task 1.5: Install the BizTalk Server Enterprise Single Sign-On Component.......................14
Task 1.6: Configure the Master Secret Service..................................................................15
Step 2: Installing and Configuring BizTalk Server Runtime Environment (System Administrator)
............................................................................................................................................... 17
Hardware Requirements........................................................................................................ 18
Software Requirements.......................................................................................................... 18
Domain Accounts................................................................................................................... 18
Installation and Configuration Tasks.......................................................................................20
Task 2.1: Add Windows Components................................................................................20
Task 2.2: Configure MS DTC............................................................................................. 20
Task 2.3: Install BizTalk Server.......................................................................................... 21
Task 2.4: Configure BizTalk Server....................................................................................22
Step 3: Installing and Configuring BizTalk BAM Server Runtime Environment (System
Administrator)......................................................................................................................... 24
Hardware Requirements........................................................................................................ 25
Software Requirements.......................................................................................................... 25
Domain Accounts................................................................................................................... 25
Installation and Configuration Tasks.......................................................................................26
Task 3.1: Add Windows Component..................................................................................26
Task 3.2: Configure MS DTC............................................................................................. 27
Task 3.3: Install Microsoft Office Excel 2007......................................................................27
Task 3.4: Install the SQL Server 2005 SSIS and SSNS Components................................28
Task 3.5: Install SQL Server 2005 SP2..............................................................................29

Task 3.6: Install the BizTalk Server....................................................................................30

Task 3.7: Configure BizTalk Server....................................................................................30
Task 3.8: Configure SSIS................................................................................................... 33
Step 4: Installing and Configuring Web Server Runtime Environment (System Administrator).34
Hardware Requirements........................................................................................................ 35
Software Requirements.......................................................................................................... 35
Domain Accounts................................................................................................................... 35
Installation and Configuration Tasks.......................................................................................36
Task 4.1: Add Windows Components................................................................................37
Task 4.2: Install SQL Server 2005......................................................................................37
Task 4.3: Install SQL Server 2005 SP2..............................................................................38
Task 4.4: Install BizTalk Server.......................................................................................... 39
Task 4.5: Configure BizTalk Server....................................................................................40
Step 5: Installing and Configuring Business Analysts Workstation..........................................41
Hardware Requirements........................................................................................................ 41
Software Requirements.......................................................................................................... 41
Installation and Configuration Tasks.......................................................................................41
Task 5.1: Install MSXML 4.0 Service Pack 2......................................................................41
Task 5.2: Install Office Excel..............................................................................................42
Task 5.3: Install BizTalk Server BAM Client.......................................................................43
Task 5.4: Enable BAM Add-in from Excel...........................................................................43
Step 6: Installing and Configuring BizTalk Server Application Developers Workstation...........44

BAM Installation and Configuration Guide

Last updated: May 26, 2008
This document provides guidelines for installing and configuring Microsoft BizTalk Server 2006
R2 in a multi-server environment with the Business Activity Monitoring (BAM) component in
consideration. This guide can also be used as a reference for installing and configuring BAM on a
single BizTalk Server.

Overview
Business Activity Monitoring (BAM) is a collection of tools that allows you to manage
aggregations, alerts, and profiles to monitor relevant business metrics. BAM gives you end-to-end
visibility into your business processes, providing accurate information about the status and results
of various operations, processes, and transactions so you can address problem areas and
resolve issues within your business. The BAM Framework provides an easy, real-time,
transaction-consistent way to monitor heterogeneous business applications, and to present data
for SQL queries and aggregated reports (OLAP). Through queries and aggregations, you can
include not only the data that is present during the running business process, but also the state
and the dynamics of the running business process, independent of how the business is
automated.
For more information about BAM see BizTalk Server help file at http://go.microsoft.com/fwlink/?
LinkId=118648, and Business Activity Monitoring (BAM) poster at http://go.microsoft.com/fwlink/?
LinkId=120003.

Considerations When Installing and Configuring

BAM
The following should be considered when installing BAM.

Deployment Topology
It is easier to understand BAM, the installation and configuration process, and dependencies by
splitting into the following three BizTalk Server environments:

Runtime environment: A basic BizTalk Server runtime environment includes one Windows
Server computer with Internet Information Services (IIS) services, SQL Server, and BizTalk
Server. This is not a typical configuration for large BizTalk Server solution deployments. In
this document, the runtime environment is a composition of four Windows Servers, including
one SQL Server, one BizTalk Server, one BizTalk BAM Server, and one Web Server.
The BizTalk BAM Server has the major BizTalk Server BAM components installed and
configured. The BAM components depend on SQL Server SSIS and SSNS, so they also

need to be installed on this server. The main reason for separating a dedicated BizTalk BAM
Server is to make the instruction flexible. In practice, you can have a dedicated BAM Server,
or merge it with the SQL Server or the Web server or the BizTalk Server. One important thing
to note is the BAM Server has to be a BizTalk member server in a BizTalk Group, which
means it has to join a BizTalk group.
A basic highly available BizTalk Server runtime environment consists of a SQL cluster with
two or more nodes, a BizTalk Server group with two or more BizTalk Servers, and a group of
NLB Web servers. To focus on the BAM installation and configuration subject, this guide
doesnt cover either the cluster configuration or the BizTalk group configuration. For more
information on clustering SQL Server and configuring BizTalk Server group, see BizTalk
Server2006 R2 Administration Tutorials at http://go.microsoft.com/fwlink/?LinkId=118355.

Design time environment: There are 3 roles involved during the BAM development and
deployment process. These roles are business analyst, BizTalk Server administrator, and
BizTalk Server application developer. A business analyst and BizTalk Server application
developer typically have their own workstations. The BizTalk Server administrator usually
uses the runtime environment to deploy applications. This guide provides the instructions for
configuring the runtime environment as well as the workstations for business analyst and
developer.

Usage time environment: After a BAM solution is implemented and deployed, business endusers can view the reports generated by various reporting tools. These tools include BAM
Portal (an ASP.NET application), SQL Server Reporting Services, Microsoft
PerformancePoint Monitoring Server, and custom BAM reporting applications.

Understanding BAM Components

The following is a list of BAM components and their purposes:
Category

BAM Component

Purpose

Server

Portal Components

Business Activity
Monitoring

Provides real-time,
Web Server
end-to-end visibility into
a business process. It
consists of the
following components:
activity searches,
aggregations, and alert
manager.

Additional Software

BAM Alert Provider

for Notification
Services

Provides BAM alerts.

BizTalk BAM Server

Additional Software

BAM Client

Provides client side

software that allows
business users to work

Business analyst
workstation

Category

BAM Component

Purpose

Server

with BAM feature.

Additional Software

BAM Eventing

Installs necessary
software for the BAMEventing Interceptors
for Windows Workflow
Foundation and
Windows
Communication
Foundation. It also
installs the BAM Event
API that is used to
send events to the
BAM database from
custom applications.

Not installed on any

server/workstation
specified in this guide.

Security and Accounts

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.

You must manually create the groups and the user accounts before you configure BizTalk
Server. The BizTalk Server Configuration Manager cannot create domain groups.

After creating domain groups and/or user accounts, add user accounts to the proper groups
according to the group affiliations in Windows Groups and User Accounts.

Use <DomainName>\<UserName> when specifying domain account information in the

BizTalk Server Configuration Manager.

There is a Domain group section under each environment configuration in this document. It
explains the accounts needed for configuring that server or workstation. To make it easier to
explain the security configuration, this guide use 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 BTInstaller is used to configure the servers/workstations.

Step 1: Installing and Configuring the SQL Server

Runtime Environment (System Administrator)
BizTalk Server 2006 relies heavily on SQL Server 2000 or SQL Server 2005 for data persistence.
SQL Server 2005 has five services: Database Services, Analysis Services (SSAS), Reporting
Service (SSRS), Notification Services (SSNS), and Integration Services (SSIS). In addition to
Database Services required by the BizTalk Server core functions, BAM also requires SSAS,
7

SSNS, and SSIS. SSNS and SSIS must be installed on the BizTalk Server where the BAM
component is installed.
In this guide, Database Services and SSAS are installed on the SQL Server; SSIS and SSNS are
installed on the BizTalk BAM Server. SSRS is not required by BizTalk Server or the BAM
component, however, it is a powerful reporting tool. Because SSRS depends on Internet
Information Services (IIS), this guide installs SSRS on the Web Server.
Note
This guide only provides the instructions to install SQL Server 2005. For the instructions
of installing SQL Server 2000, see Installing and Configuring Microsoft BizTalk Server
2006 R2 on Windows Server 2003.doc at http://go.microsoft.com/fwlink/?linkid=81041.
To provide high availability for the BizTalk Server 2006 databases, use Windows Cluster service
to configure two or more database computers that are running SQL Server to create a server
cluster. Installing and configuring SQL Server failover cluster is out of the scope of this guide. For
instructions to create a SQL Server failover cluster, see BizTalk Server 2006 Administration
Tutorials at http://go.microsoft.com/fwlink/?LinkId=118355, or Installing and Configuring BizTalk
Server in a Multicomputer Environment at http://go.microsoft.com/fwlink/?linkid=81041.
This guide also chooses to install the master secret service on the SQL Server. A master secret
service is a critical part of the overall Microsoft BizTalk Server 2006 infrastructure. It is used to
provide an encryption key for the Enterprise Single Sign-On (SSO) services on each of the
BizTalk Servers to secure port configuration data. Master secret server is a server running the
SSO service, which has an additional component for managing and supplying the encryption key.
When the master secret service is down, the SSO services on the BizTalk Servers are not able to
retrieve the encryption key to decrypt the port configuration, and the BizTalk Servers can not
function. Because the master secret service plays a critical role, we recommend clustering the
master secret service. A typical solution is to create an additional SSO service cluster resource in
the SQL Server Failover Cluster group (virtual server). Clustering the master secret server is out
of the scope of this guide. However this document provides the instructions to install and
configure master secret server on the SQL Server instead of the BizTalk Server so you
understand the procedure of installing and configuring master secret server on a separate server
from BizTalk Server. For detailed instructions about clustering master secret server, see BizTalk
Server 2006 Administration Tutorials at http://go.microsoft.com/fwlink/?LinkId=118355.

Hardware Requirements
The SQL Server must meet the minimum hardware requirements for running Microsoft SQL
Server 2005. For more information, see Hardware and Software Requirements for Installing SQL
Server 2005 at http://go.microsoft.com/fwlink/?linkid=71734.

Software Requirements
This guide is based on Windows Server 2003 with Service Pack 2. For more information about
the additional operating system supported by SQL Server 2005, see Hardware and Software
Requirements for Installing SQL Server 2005 at http://go.microsoft.com/fwlink/?linkid=71734.
8

Other than the software requirements specified in the SQL Server 2005 documentation, BizTalk
Server 2006 R2 also requires SQL Server 2005 Service Pack 2 and Microsoft Distributed
Transaction Coordinator (MS DTC).

Domain Accounts
The following table lists the Windows groups the domain administrator needs to create for the
SQL Server configuration. These group accounts can be either global domain accounts or
universal domain accounts.
Group Name (suggested)

Purpose

SSO Administrators

The SSO administrator account is a highly

privileged account in the BizTalk SSO system.

SSO Affiliate Administrators

This group account includes the administrators

of certain SSO affiliate applications. This group
is only used if you use the account mapping
function of SSO; however, the account is
required during SSO configuration.

The following table lists the domain accounts for the domain administrator to create for the SQL
Server configuration. The domain administrator must ensure the accounts are members of the
group indicated.
Account Name

Type

Member of Group

Purpose

User

SSO
Administrator
s

Domain
Users

This account with administrative rights is

required for installing and configuring SQL
Server. Rights can be revoked or the account
disabled as soon as setup and configuration
are complete.

Local
Administrator
s

Domain
Users

(suggested)

BTInstaller

SQLService

Service

This is the service account for running SQL

Server Database Services. This account
needs to be granted the Log on as service
user right. The SQL Server installer program
grants the permissions automatically during
the installation.
There are 4 services that come with the
Databases Services component and the
9

Account Name

Type

Member of Group

Purpose

(suggested)

Analysis Services component: SQL Server,

SQL Server Agent, Analysis Services, and
SQL Browser. For more information about
these services, see SQL Server Books Online
at http://go.microsoft.com/fwlink/?
LinkId=120004. In this guide, the SQLService
account is used as the service account for all 4
services.
SSOService

Service

SSO
Administrator
s

Domain
Users

This is the service account for running the

SSO service.

Installation and Configuration Tasks

The instructions in this guide are based on Windows Server 2003 with Service Pack 2. Windows
Server 2003 Service Pack 1 is the minimum requirement for installing SQL Server 2005.
The following tasks need to be performed on the SQL Server:

Task 1.1: Add Windows Component

Task 1.2: Configure MS DTC

Task 1.3: Install the SQL Server 2005

Task 1.4: Install SQL Server 2005 SP2

Task 1.5: Install the BizTalk Server Enterprise Single Sign-On Component

Task 1.6: Configure the Master Secret Service

You must log on as Contoso\BTInstaller or a user with the same access credentials to configure
the SQL Server.

Task 1.1: Add Windows Component

In this task, you install MS DTC. MS DTC comes with Windows Server 2003, however, it is not
installed, by default.
What is this for and why do I need this?
MS DTC is required to run BizTalk Server. Most BizTalk Server runtime operations require MS
DTC support to ensure that the operations are transactionally consistent. If MS DTC transaction
support is not available, then the associated BizTalk Server runtime operations cannot proceed.
The components of BizTalk Server commonly affected when MS DTC transaction support is not

10

configured correctly include (but are not limited to) the Single Sign-On Service, BizTalk host
instances, and any SQL Server instances that are connected to by BizTalk Server.
MS DTS requires additional configuration, which is performed in the next task.
Estimated time to complete: 5 minutes
To add/remove the MS DTC Windows component
1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click Application Server, and then click Details.
4. Select Enable network DTC access, and then click OK.
5. Click Next.
6. Click Finish.

Task 1.2: Configure MS DTC

In this task, you configure MS DTC.
What is this for and why do I need this?
In the last task, you installed MS DTC. MS DTC requires additional configuration, and the
configuration must be identical on all the SQL Servers and BizTalk Servers.
Estimated time to complete: 5 minutes
To configure MS DTC
1. Click Start, point to Administrative Tools, and then click Component Services.
2. Expand Component Services, expand Computers, right-click My Computer, and then
click Properties.
3. On the MS DTC tab, under Transaction Configuration, click Security Configuration.
4. From Security Configuration, select the following values, and then click OK.
Name

Value

Network DTC Access

(selected)

Allow Inbound

(selected)

Allow Outbound

(selected)

No Authentication Required

(selected)

Enable Transaction Internet Protocol(TIP) (selected)

Transactions
DTC Logon Account: Account

NT Authority\NetworkService

Note
11

Enable Mutual Authentication Required if all remote machines are running

Windows Server 2003 SP1 or XP SP2 or higher, and are configured with Mutual
Authentication Required; enable Incoming Caller Authentication Required if
running MS DTC on a cluster; enable No Authentication Required if remote
machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2; enable
TIP Transactions if running the BAM Portal. For more information, see
Troubleshooting Problems with MS DTC at http://go.microsoft.com/fwlink/?
linkid=101609.
5. To confirm restarting MS DTC service, click Yes.
6. Click OK twice.

Task 1.3: Install the SQL Server 2005

In this task, you install the Database Services and Analysis Services (SSAS) components of SQL
Server 2005.
What is this for and why do I need this?
BizTalk Server relies on SQL Server Database Services. The BizTalk Server BAM component
also requires SSAS, SSIS and SSNS. SSIS & SSNS are installed on the BizTalk BAM Server.
The other major SQL Server 2005 component is SSRS. It is optional for running BAM, and is
installed on the Web server in this guide.
Estimated time to complete: 50 minutes
To install SQL Server 2005
1. Insert the SQL Server 2005 installation disk into the CD-ROM drive. If the SQL
Server 2005 Setup page does not appear, double-click default.hta located in the
Servers folder.
2. From the Start splash screen, click Server components, tools, Books Online, and
samples.
3. On the End User License Agreement page, click I accept the licensing terms and
conditions, and then click Next.
4. On the Installing Prerequisites page, click Install, and then click Next.
5. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.
6. On the System Configuration Check page, ensure there are no errors before you
continue, and then click Next. If you dont plan to install SSRS on the SQL Server, you
can ignore the IIS Feature Requirement warning.
7. On the Registration Information page, type your name and company, and then click
Next.
8. On the Components to Install page, select only Database Services and Analysis
Services, and then click Next.
Note
SQL Server Management Studio is handy on the SQL Server. To install it, click
12

Advanced, expand Client Components, and then select Management Tools.

Important
Make sure to select the failover cluster checkboxes if you intend to cluster SQL
Server Database Services and Analysis Services.
9. On the Instance Name page, either use the default instance name or enter a custom
instance name. If you dont know what to select, click Default instance, and then click
Next.
10. On the Service Account page, enter or select the following values, and then click Next.
Name

Value

Customize for each service account

(clear)

Use a domain user account

(selected)

Username

SQLSerivce

Password

pass@word1

Domain

Contoso

SQL Server

(selected)

SQL Server Agent

(selected)

Analysis Services

(selected)

SQL Browser

(optional)

Important
BizTalk Server relies on several SQL jobs to purge its databases. SQL Server
Agent is the service used to execute the SQL jobs. It is important to make sure
the SQL Server Agent is running.
11. On the Authentication Mode page, click Windows Authentication Mode, and then
click Next.
12. On the Collation Settings page, select the appropriate collation. If you dont know which
to select, leave the defaults, and then click Next.
13. On the Report Server Installation Options page, click Install the default
configuration, and then click Next. You only see this screen if you choose to install
SSRS on the SQL Server. This guide installed SSRS on the Web server.
14. On the Error and Usage Report Settings page, we recommend you send feedback to
Microsoft. If you dont want to, leave the defaults, and then click Next.
15. On the Ready to Install page, review the information, and then click Install.
16. On the Setup Progress page, after setup has finished, click Next.
17. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.
13

18. Reboot the computer.

Task 1.4: Install SQL Server 2005 SP2

In this step, you install SQL Server 2005 Service Pack 2.
What is this for and why do I need this?
SQL Server 2005 Service Pack 2 is the minimum requirement by BizTalk Server 2006 R2. The
minimum requirement for BizTalk Server 2006 is SQL Server 2005 SP1.
Estimated time to complete: 30 minutes
To install SQL Server 2005 SP2
1. Open SQLServer2005SP2-KB921896-x86-ENU.exe. The file name can be different
depending on the language and the types of CPU.
2. On the Welcome page, click Next.
3. On the License Terms page, select I accept the agreement, and then click Next.
4. On the Feature Selection page, make sure all the features are selected, and then click
Next. If you cannot select MSSQLServer and Database Services, make sure the
current node is the active node.
5. On the Authentication page, click Next.
6. On the Remote User Account page, enter the account information for domain user, and
then click Next.
7. On the Error and Usage Reporting Settings page, click Next.
8. On the Running Processes page, ignore the computer reboot warning and click Next.
9. On the Ready to Install page, click Install.
10. On the Installation Progress page, click Next.
11. On the Installation Complete page, click Next.
12. On the Additional Information page, click Finish.
13. Reboot the SQL Server computer.

Task 1.5: Install the BizTalk Server Enterprise Single Sign-On Component
In this task, you install the BizTalk Server Enterprise Single Sign-On (SSO) component.
What is this for and why do I need this?
SSO is a critical part of the BizTalk runtime architecture for securing port configuration data.
Without it, BizTalk Server cannot decrypt the port configuration information. This task is to install
the component. You must configure the component in the next task.
Estimated time to complete: 10 minutes
To install the BizTalk SSO components
1. Run setup.exe to install BizTalk Server 2006 R2.
14

2. On the Start page, click Install Microsoft BizTalk Server 2006 R2 on this computer.
3. On the Customer Information page, enter information in the User name box, the
Organization box, and the Product key box, and then click Next.
4. On the License Agreement page, read the license agreement, select Yes, I accept the
terms of the license agreement, and then click Next.
5. On the Component Installation page, clear all the check boxes, and only select the
following components under the Additional Software, and then click Next.

Enterprise Single Sign-On Administration Module

Enterprise Single Sign-On Master Secret Server

6. On the Redistributable Prerequisites page, click Automatically install the

redistributable prerequisites from the web, and then click Next.
Note
The SQL Server must have an Internet connection to download and install the
redistributable prerequisites automatically. Otherwise you can consider using the
other available options.
7. On the Summary page, click Install.
8. On the Installation Completed page, clear the Launch BizTalk Server Configuration
check box, and then click Finish.

Task 1.6: Configure the Master Secret Service

In this task, you configure SSO on the SQL Server.
What is this for and why do I need this?
Configuring the master secret server has three parts: creating the SSO database, assigning the
SSO service account, and backing-up the master secret.
On the SQL Server, you create a new SSO system. When a new SSO system is created, a SSO
database is also created. All the SSO services on other BizTalk Servers in the same BizTalk
group share the same SSO database. When you configure SSO in other member BizTalk
Servers, you must select the Join an existing SSO system option
Estimated time to complete: 5 minutes
To configure the master secret server
1. Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then
click BizTalk Server Configuration.
2. On the Microsoft BizTalk Server 2006 Configuration page, choose Custom
Configuration, enter the following values, and then click Configure.

15

Name

Value

Database server name

(the host name of the SQL Server)

User name

Contoso\SSOService (Typically a generic

BizTalk Server service account is used
here. Because you only configure SSO, the
SSO Serivce account is used here.)

Password

pass@word1

3. In the left pane, click Enterprise SSO.

4. In the right pane, enter or select the following values:
Name

Value

Enable Enterprise Single Sign-ON on this

computer

(checked)

Create a new SSO system

(selected)

SSO Database: Server Name

(the host name of the SQL Server)

SSO Database: Database Name

(the default name is SSODB)

Enterprise Single Sign-ON Service:

Account

Contoso\SSOService

SSO Administrator(s): Windows Group

Contoso\SSO Administrators

SSO Affiliate Administrators(s): Windows

Group

Contoso\SSO Affiliate Administrators

5. In the left pane, click Enterprise SSO Secret Backup. The Enterprise SSO secret is very
critical. You must back it up to a file. It is a good practice to burn the key into a CD and
store the CD in a safe place.
6. In the right pane, enter the password and the backup file location.
7. Click Apply Configuration.
8. On the Summary page, to apply the configuration, click Next.
9. Verify that the Configuration Result is Success, and then click Finish.
10. Close Microsoft BizTalk Server 2006 Configuration.
After all the tasks are completed, it is a good practice to go over the application event logs and
they system event logs to make sure there is no error related to either the installation or the
related services. The following services are started automatically by the installers. You must
confirm they are up running:

Enterprise Single Sign-On Service

16

SQL Server

SQL Server Agent

SQL Server Analysis Services

SQL Server Browser

Step 2: Installing and Configuring BizTalk Server

Runtime Environment (System Administrator)
Each BizTalk Server is associated with one and only BizTalk group. The BizTalk group is a unit of
organization that usually represents an enterprise, department, hub, or other business unit that
requires a contained BizTalk Server implementation. The BizTalk group has a one-to-one
relationship with a Configuration database. The Configuration database stores configuration
information for the BizTalk group and the servers in that group. This configuration information
specifies part of the message-processing logic for the servers and where this logic will physically
run. When the first BizTalk Server is configured, you must choose the Create a new BizTalk
Group option, and the Configuration database is created. For the consecutive BizTalk Servers
you must choose the Join the existing BizTalk Group, so all the BizTalk Servers in the BizTalk
Group share the same Configuration database and you can administer each server from the
administration console.
BizTalk Server 2006 provides great flexibility in addressing high availability because you can
strategically dedicate logical hosts to run specific areas of functionality such as receiving and
sending messages or processing orchestrations. A BizTalk host is a logical container within a
BizTalk Server group that can house BizTalk Server items, such as adapter handlers, receive
locations (including pipelines), and orchestrations. You typically group items that have similar
scale properties into a particular host. After you create a host (a logical container), you can add
physical BizTalk Server computers (host instances) to the host. A host instance runs as an NT
Service on the designated BizTalk Server. For each host, you can have only one instance of a
particular BizTalk Server computer. However, you can have instances of a particular host on one
or more computers, and you can have instances of different hosts on a particular computer. A
basic high availability BizTalk Server setup includes two BizTalk Servers, and a host instance of
each host on each of the BizTalk Server. Configuring a BizTalk group with multiple BizTalk Server
is outside the scope of this guide. For more information about configuring BizTalk groups, see
Microsoft BizTalk Server 2006 Administration Tutorials at http://go.microsoft.com/fwlink/?
LinkId=118355.

Hardware Requirements
The BizTalk Server must meet the minimum hardware requirements for running Microsoft BizTalk
Server 2006. For more information, see the Hardware Requirement section in Installing and
Configuring BizTalk Server 2006 R2 on Windows Server 2003 at http://go.microsoft.com/fwlink/?
linkid=81041.

17

Software Requirements
The BizTalk Server must meet the minimum software requirements for running Microsoft BizTalk
Server 2006. For more information about the BizTalk Server software requirements, see the
Software Requirements section in Installing and Configuring BizTalk Server 2006 R2 on
Windows Server 2003 at http://go.microsoft.com/fwlink/?linkid=81041.

Domain Accounts
The following table lists the Windows groups the domain administrator needs to create for the
BizTalk Server configuration. These group accounts can be either global domain accounts or
universal domain accounts.
Group Name (suggested)

Purpose

BizTalk Server Administrators

Has the least privileges necessary to

perform administrative tasks.

Can deploy solutions, manage applications,

and resolve message processing issues.

To perform administrative tasks for

adapters, receive and send handlers, and
receive locations, the BizTalk Server
Administrators must be added to the Single
Sign-On Affiliate Administrators.

BizTalk Server Operators

Has a low privilege role with access only to

monitoring and troubleshooting actions.

BizTalk Application Users

The default name of the first In-Process

BizTalk Host Group created by
Configuration Manager.

Use one BizTalk Host Group for each InProcess host in your environment.

Includes accounts with access to InProcess BizTalk Hosts (hosts processes in

BizTalk Server, BTSNTSvc.exe).

The default name of the first Isolated

BizTalk Host Group created by
Configuration Manager. Isolated BizTalk
hosts not running on BizTalk Server, such
as HTTP and SOAP.

Use one BizTalk Isolated Host Group for

each Isolated Host in your environment.

BizTalk Isolated Host Users

18

The following table lists the domain accounts for the domain administrator to create for the SQL
Server configuration. The domain administrator must ensure the accounts are members of the
group indicated.
Account Name

Type

Member of Group

Purpose

User

SSO
Administrators

BizTalk Server
Administrators

Domain Users

Local
Administrators

This account with

administrative rights is
required for installing
and configuring BizTalk
Server. Rights can be
revoked or the account
disabled as soon as
setup and configuration
are complete.

(suggested)

BTInstaller

BTService

Service

Domain Users

This is a generic
BizTalk Server service
account. If you dont
want to create
dedicated accounts for
the various BizTalk
Server services, you
can use it.

BTServiceHost

Service

BizTalk Application
Users

Domain users

This is the service

account for running
BizTalk Server service.

BizTalk Isolated
Host Users

Domain Users

BTServiceHostIso

Service

This is the service

account for running
BizTalk Server service.

Installation and Configuration Tasks

The instructions in this guide are based on Windows Server 2003 with Service Pack 2. Service
pack 1 is the minimum requirement for BizTalk Server 2006.
The following tasks need to be performed on the BizTalk Server:

Task 2.1: Add Windows Components

Task 2.2: Configure MS DTC

Task 2.3: Install BizTalk Server

Task 2.4: Configure BizTalk Server

19

You must log on as Contoso\BTInstaller or a user with the same access credentials to configure
the BizTalk Server.

Task 2.1: Add Windows Components

In this task, you install MS DTC and IIS.
What is this for and why do I need this?
MS DTC is required by BizTalk Server. MS DTC requires additional configuration, which will be
performed in the next step.
IIS is required to host some isolated BizTalk Server adapters.
Estimated time to complete: 5 minutes
To add the IIS and MS DTC Windows components
1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click Application Server, and then click Details.
4. Select Enable network DTC access, and Internet Information Services, and then click
OK.
5. Click Next.
6. Click Finish.

Task 2.2: Configure MS DTC

In this task, you configure MS DTC.
What is this for and why do I need this?
MS DTC is required by BizTalk Server. MS DTC must also be configured identically from all the
BizTalk Server, and the SQL Servers.
Estimated time to complete: 5 minutes
To configure MS DTC
1. Click Start, point to Administrative Tools, and then click Component Services.
2. Expand Component Services, expand Computers, right-click My Computer, and then
click Properties.
3. On the MS DTC tab, under Transaction Configuration, click Security Configuration.
4. From Security Configuration, select the following values, and then click OK.

20

Name

Value

Network DTC Access

(selected)

Allow Inbound

(selected)

Allow Outbound

(selected)

No Authentication Required

(selected)

Enable Transaction Internet Protocol(TIP) (selected)

Transactions
DTC Logon Account: Account

NT Authority\NetworkService

Note
Enable Mutual Authentication Required if all remote machines are running
Windows Server 2003 SP1 or XP SP2 or higher, and are configured with Mutual
Authentication Required; enable Incoming Caller Authentication Required if
running MS DTC on a cluster; enable No Authentication Required if remote
machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2; enable
TIP Transactions if running the BAM Portal. For more information, see
Troubleshooting Problems with MS DTC at http://go.microsoft.com/fwlink/?
linkid=101609.
5. To confirm restarting MS DTC service, click Yes.
6. Click OK twice.

Task 2.3: Install BizTalk Server

In this task, you install BizTalk Server.
What is this for and why do I need this?
The BizTalk Server installation occurs in two parts. This task is the first part that copies the
necessary files to the local machine to prepare for server installation. This design is to prevent
taking time to reinstall components when an error occurs.
You install all of the default BizTalk Server components with the exception of Business Activity
Monitoring under Portal Components. This is the BAM Portal. BAM Portal will be installed and
configured on the Web server.
Estimated time to complete: 30 minutes
To install the BizTalk Server
1. Run setup.exe to install BizTalk Server 2006 R2.
2. On the Start page, click Install Microsoft BizTalk Server 2006 R2 on this computer.
3. On the Customer Information page, enter information in the User name box, the
Organization box, and the Product key box, and then click Next.
21

4. On the License Agreement page, read the license agreement, select Yes, I accept the
terms of the license agreement, and then click Next.
5. On the Component Installation page, keep the default selections, but clear Portal
Components, and then click Next.
6. On the Redistributable Prerequisites page, click Automatically install the
redistributable prerequisites from the web, and then click Next.
Note
You must have an Internet connection to download and install the redistributable
prerequisites automatically. Otherwise you can consider using the other options.
7. On the Summary page, click Install.
8. On the Installation Completed page, clear Launch BizTalk Server Configuration
check box, and then click Finish.

Task 2.4: Configure BizTalk Server

In this task, you configure BizTalk Server.
What is this for and why do I need this?
This is the second part of the BizTalk Server installation process. It launches the BizTalk Server
Configuration to configure and install the selected BizTalk Server components on the local
machine.
Estimated time to complete: 15 minutes
To configure BizTalk Server
1. Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then
click BizTalk Server Configuration.
2. On the Microsoft BizTalk Server 2006 Configuration page, choose Custom
Configuration, enter the following values, and then click Configure.
Name

Value

Database server name

(the host name of the SQL Server where

the master secret server is configured.)

Service credential: User name

Contoso\BTService

Service credential: Password

pass@word1

3. In the left pane, click Enterprise SSO. In the details pane, enter or select the following
values:

22

Name

Value

Enable Enterprise Single Sign-On on this

computer

(checked)

Join an existing SSO system

(selected)

Data stores: Server Name

(the host name of the SQL Server)

Data stores: Database Name

(the default SSO database name is

SSODB)

Windows service: Account

Contoso\SSOService

Windows service: password

pass@word1

When you configure the SSO service on the SQL Server, you choose the Create a new
SSO system. That creates the SSO database that is shared by all the BizTalk Servers in
the group.
4. In the left pane, click Group. In the details pane, enter the following values:
Name

Value

Enable BizTalk Server Group on this

computer

(checked)

Create a new BizTalk Group

(selected)

BizTalk Management Database: Server

Name

(the host name of the SQL Server)

BizTalk Management Database: Database (the default name is BizTalkMgmtDb)

Name
BizTalk MessageBox Database: Server
Name

(the host name of the SQL Server)

BizTalk MessageBox Database: Server

Name

(the default name is BizTalkMsgBoxDb)

BizTalk Tracking Database: Server Name

(the host name of the SQL Server)

BizTalk Tracking Database: Database

Name

(the default name is BizTalkDTADb)

BizTalk Administrators Group

Contoso\BizTalk Server Administartors

BizTalk Operators Group

Contoso\BizTalk Server Operators

You select the Create a new BizTalk Group option to create a new group and its
Configuration database.
23

5. In the left pane, click BizTalk Runtime, and then enter or select the following values:
Name

Value

Register the BizTalk Server runtime

components

(selected)

Create In-Process Host and Instance

(selected)

Host name:

(the default name is

BizTalkServerApplication)

Create Isolated Host and Instance

(selected)

Isolated Host name:

(the default name is

BizTalkServerIsolatedHost)

BizTalk Host Instance Account

Contoso\BTServiceHost

BizTalk Host Instance Account:

password

pass@word1

BizTalk Isolated Host Instance Account

Contoso\BTServiceHostIso

BizTalk Isolated Host Instance Account:

password

pass@word1

BizTalk Host Users Group

Contoso\BizTalk Application Users

BizTalk Isolated Host Users Group

Contoso\BizTalk Isolated Host Users

6. Click Apply Configuration.

7. On the Summary page, to apply the configuration, click Next.
8. Verify that the Configuration Result is Success, and then click Finish.
9. Close Microsoft BizTalk Server 2006 Configuration.

Step 3: Installing and Configuring BizTalk BAM

Server Runtime Environment (System
Administrator)
This guide chooses to install the BizTalk Server BAM components on a dedicated Windows
server. There are no specific requirements where to install the BAM components. They can be
installed on the SQL Server, the BizTalk Server, or the Web server. The BAM server has to be a
BizTalk group member server.

24

Hardware Requirements
The BizTalk BAM Server must meet the minimum hardware requirements for running Microsoft
BizTalk Server 2006. For more information, see the Hardware Requirements section in Installing
and Configuring BizTalk Server 2006 R2 on Windows Server 2003 at
http://go.microsoft.com/fwlink/?LinkId=81041.

Software Requirements
The BizTalk BAM Server must meet the minimum software requirements for running Microsoft
BizTalk Server 2006. For more information, see the Software Requirements section in Installing
and Configuring BizTalk Server 2006 R2 on Windows Server 2003 at
http://go.microsoft.com/fwlink/?LinkId=81041.
Other software requirements include Microsoft Office Excel 2007, and SQL Server 2005 SSIS
and SSNS.

Domain Accounts
The following table lists the domain accounts for the domain administrator to create for the
BizTalk BAM Server configuration. These accounts have been created when configuring SQL
Server and BizTalk Server.
Account Name

Type

Member of Group

Purpose

User

Domain Users

Local administrators

SSO Administrators

This account with

administrative rights is
required for installing
and configuring SQL
Server. Rights can be
revoked or the account
disabled as soon as
setup and configuration
are complete.

Domain Users

SSO Administrators

Domain Users

(suggested)

BTInstaller

SSOService

BTService

Service

Service

This is the service

account for running
SSO service.
This is a generic BizTalk
Server service account.
In this section, it is used
as the service account
for running the BAM
Notification Service.

25

Installation and Configuration Tasks

The instructions of this guide are based on Windows Server 2003 with Service Pack 2. Windows
Server 2003 Service Pack 1 is the minimum requirement for installing SQL Server 2005.
The following tasks need to be performed on the BizTalk BAM Server:

Task 3.1: Add Windows Component

Task 3.2: Configure MS DTC

Task 3.3: Install Microsoft Office Excel 2007

Task 3.4: Install the SQL Server 2005 SSIS and SSNS Components

Task 3.5: Install SQL Server 2005 SP2

Task 3.6: Install the BizTalk Server

Task 3.7: Configure BizTalk Server

Task 3.8: Configure SSIS

You must log on as Contoso\BTInstaller or a user with the same access credentials to configure
the BizTalk BAM Server.

Task 3.1: Add Windows Component

In this task, you add MS DTC.
What is this for and why do I need this?
MS DTC is required by running BizTalk Server. MS DTC requires additional configuration that you
will do in the next task.
Estimated time to complete: 5 minutes
To add the MS DTC Windows components
1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click Application Server, and then click Details.
4. Select Enable network DTC access, and then click OK.
5. Click Next.
6. Click Finish.

Task 3.2: Configure MS DTC

In this task, you configure MS DTC.
What is this for and why do I need this?
In the last task, you installed MS DTC. MS DTC requires additional configuration, and the
configuration must be identical on all the SQL Servers and BizTalk Servers.
Estimated time to complete: 5 minutes

26

To configure MS DTC
1. Click Start, point to Administrative Tools, and then click Component Services.
2. Expand Component Services, expand Computers, right-click My Computer, and then
click Properties.
3. On the MS DTC tab, under Transaction Configuration, click Security Configuration.
4. From Security Configuration, select the following values, and then click OK.
Name

Value

Network DTC Access

(selected)

Allow Inbound

(selected)

Allow Outbound

(selected)

No Authentication Required

(selected)

Enable Transaction Internet Protocol(TIP) (selected)

Transactions
DTC Logon Account: Account

NT Authority\NetworkService

Note
Enable Mutual Authentication Required if all remote machines are running
Windows Server 2003 SP1 or XP SP2 or higher, and are configured with Mutual
Authentication Required; enable Incoming Caller Authentication Required if
running MS DTC on a cluster; enable No Authentication Required if remote
machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2; enable
TIP Transactions if running the BAM Portal. For more information, see
Troubleshooting Problems with MS DTC at http://go.microsoft.com/fwlink/?
linkid=101609.
5. To confirm restarting MS DTC service, click Yes.
6. Click OK twice.

Task 3.3: Install Microsoft Office Excel 2007

In this task, you install Microsoft Office Excel 2007.
What is this for and why do I need this?
This is the server where BizTalk Server administrators run BAM Manager command line utility
(bm.exe). BAM Manager needs Excel to parse .xls or .xlsx files before it can update the BAM
Primary Import database.
Note
Excel 2003 is also supported.
Estimated time to complete: 15 minutes
27

To install Microsoft Office Excel 2007

1. Insert the Office 2007 installation disk into the CD-ROM drive.
2. From Choose the installation you want, click Customize.
3. Click Installation options tab.
4. Click Microsoft Office Excel, select Run from My Computer, and set the rest Not
Available.
5. Click Install Now.
6. Click OK twice.

Task 3.4: Install the SQL Server 2005 SSIS and SSNS Components
In this task, you install the SSIS and SSNS components of SQL Server 2005.
What is this for and why do I need this?
BizTalk Server BAM components depends on SSIS and SSNS.
Estimated time to complete: 20 minutes
To install SQL Server 2005
1. Insert the SQL Server 2005 installation disk into the CD-ROM drive. If the SQL
Server 2005 Setup page does not appear, double-click default.hta located in the
Servers folder.
2. From the Start splash screen, click Server components, tools, Books Online, and
samples.
3. On the End User License Agreement page, click I accept the licensing terms and
conditions, and then click Next.
4. On the Installing Prerequisites page, click Install, and then click Next.
5. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.
6. On the System Configuration Check page, ensure that there are no errors before you
continue, and then click Next.
7. On the Registration Information page, type your name and company, and then click
Next.
8. On the Components to Install page, select only Integration Services and Notification
Services, and then click Next.
Note
SQL Server Management Studio is handy on the SQL Server. To install it, click
Advanced, expand Client Components, select Management Tools.
9. On the Error and Usage Report Settings page, leave the defaults, and then click Next.
10. On the Ready to Install page, review the information, and then click Install.
11. On the Setup Progress page, after setup has finished, click Next.
12. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.
28

13. Reboot the computer.

Task 3.5: Install SQL Server 2005 SP2

In this step, you install SQL Server 2005 Service Pack 2. SQL Server 2005 Service Pack 2 is the
minimum requirement by BizTalk Server 2006 R2. The minimum requirement by BizTalk Server
2006 is SP1.
What is this for and why do I need this?
BizTalk Server 2006 R2 requires SQL Server 2005 SP2.
Estimated time to complete: 20 minutes
To install SQL Server 2005 SP2
1. Open SQLServer2005SP2-KB921896-x86-ENU.exe. The file name can be different
depending on the language and the types of CPU.
2. On the Welcome page, click Next.
3. On the License Terms page, select I accept the agreement, and then click Next.
4. On the Feature Selection page, make sure all the features are selected, and then click
Next. If you cannot select MSSQLServer and Database Services, make sure the
current node is the active node.
5. On the Authentication page, click Next.
6. On the Remote User Account page, enter the account information for domain user, and
then click Next.
7. On the Error and Usage Reporting Settings page, click Next.
8. On the Running Processes page, ignore the computer reboot warning and click Next.
9. On the Ready to Install page, click Install.
10. On the Installation Progress page, click Next.
11. On the Installation Complete page, click Next.
12. On the Additional Information page, click Finish.
13. Reboot the SQL Server computer.

Task 3.6: Install the BizTalk Server

To configure a BAM server, you must first install two SQL Server dependencies, SSIS and SSNS.
The two BizTalk Server components required are Server Runtime and BAM Alert Provider for
SQL Notification Services.
What is this for and why do I need this?
The Server Runtime component is the minimum requirement for a BizTalk Server. A BAM server
must be a BizTalk Server. If this component is not installed, and this server is not configured as a
BizTalk Server in the BizTalk Group, you dont have the option to configure BAM tools and BAM
alerts.
29

The BAM Alert Provider for SQL Notification Services component is to provide BAM alerts.
Estimated time to complete: 15 minutes
To install the BizTalk Server runtime and BAM components
1. Run setup.exe to install BizTalk Server 2006 R2.
2. On the Start page, click Install Microsoft BizTalk Server 2006 R2 on this computer.
3. On the Customer Information page, enter information in the User name box, the
Organization box, and the Product key box, and then click Next.
4. On the License Agreement page, read the license agreement, select Yes, I accept the
terms of the license agreement, and then click Next.
5. On the Component Installation page, select only the following two components, and
then click Next.

Server Runtime (without the child elements)

BAM Alert Provider for SQL Notification Services

6. On the Redistributable Prerequisites page, click Automatically install the

redistributable prerequisites from the web, and then click Next.
Note
You must the Internet connection to download and install the redistributable
prerequisites automatically. Otherwise you can consider using the other options.
7. On the Summary page, click Install.
8. On the Installation Completed page, clear the Launch BizTalk Server Configuration
check box, and then click Finish.

Task 3.7: Configure BizTalk Server

In this task, you configure BizTalk Server, including the BAM component.
What is this for and why do I need this?
This is the second part of the BizTalk Server installation process. It launches the BizTalk Server
Configuration to configure and install the selected BizTalk Server components on the local
machine.
Estimated time to complete: 10 minutes
To configure BizTalk BAM Server
1. Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then
click BizTalk Server Configuration.
2. On the Microsoft BizTalk Server 2006 Configuration page, choose Custom
Configuration, enter the following values, and then click Configure.

30

Name

Value

Database server name

(the host name of the SQL Server where

the master secret server is configured)

Service credential: User name

Contoso\BTService

Service credential: Password

pass@word1

3. In the left pane, click Enterprise SSO. In the details pane, enter or select the following
values:
Name

Value

Enable Enterprise Single Sign-On on this

computer

(checked)

Join an existing SSO system

(selected)

Data stores: Server Name

(the host name of the SQL Server for

BizTalk Server)

Data stores: Database Name

(the default SSO database name is

SSODB)

Windows service: Account

Contoso\SSOService

Windows service: password

pass@word1

4. In the left pane, click Group. In the details pane, enter the following values:
Name

Value

Enable BizTalk Server Group on this

computer

(checked)

Join an existing BizTalk Group

(selected)

BizTalk Management Database: Server

Name

(the host name of the SQL Server)

BizTalk Management Database: Database (the default name is BizTalkMgmtDb)

Name
5. In the left pane, click BizTalk Runtime, and then enter or select the following values:

31

Name

Value

Register the BizTalk Server runtime

components

(cleared)

6. In the left pane, click BAM Tools, and then enter or select the following values:
Name

Value

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)

7. In the left pane, click BAM Alerts, and then enter or select the following values:
Note
BAM alerts require SSNS installed on the local computer, and BAM tools to be
enabled.

32

Name

Value

Enable SQL Notification Services for

BAM alerts

(selected)

Windows service

Contoso\BTService

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
You 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)

8. Click Apply Configuration.

9. On the Summary page, to apply the configuration, click Next.
10. Verify that the Configuration Result is Success, and then click Finish.
11. Close Microsoft BizTalk Server 2006 Configuration.

Task 3.8: Configure SSIS

In this task, you configure the SSIS to use the msdb database on a remote SQL Server.
What is this for and why do I need this?
By default, the Integration Services service is configured to manage packages that are stored in
the msdb database in a local, default instance of Database Engine. To manage packages that are
stored in a named instance or a remote instance of the Database Engine, or in multiple instances
of the Database Engine, you have to modify the configuration file. For example, you can create
additional root folders of the type, SqlServerFolder, to manage packages in the msdb database of
multiple instances of the Database Engine.
You can also modify the configuration file to allow packages to continue running if the service
stops, to display additional root folders in Object Explorer, or to specify a different folder or
additional folders in the file system to be managed by Integration Services service.
The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile
specifies the location and name for the configuration file that Integration Services service uses.
The default value of the registry key is C:\Program Files\Microsoft SQL Server\90\DTS\Binn\
MsDtsSrvr.ini.xml. You can update the value of the registry key to use a different name and
location for the configuration file.
33

Important
You must restart the Integration Services after modifying registry or the configuration file.
Estimated time to complete: 5 minutes
To configure the Integration Services
1. Open a Command Prompt.
2. Change directory to %ProgramFiles%\Microsoft SQL Server\90\DTS\Binn
3. Execute the following command:
notepad MsDtsSrvr.ini.xml

4. In Notepad, update the text inside the <ServerName> tag to the host name of the SQL
Server.
5. In Notepad, save the changes.
6. From the Command Prompt, execute the following command:
net stop MsDtsServer

7. From the Command Prompt, execute the following command:

net start MsDtsServer

Step 4: Installing and Configuring Web Server

Runtime Environment (System Administrator)
There are two major components running on the Web Server: one is the BAM Portal and the
other is SQL Server Reporting Services (SSRS).
The BAM portal is a Web-based feature that consists of a collection of ASP.NET 2.0 pages. It
provides real-time, end-to-end visibility into a business process. Business end-users use the BAM
portal to monitor Key Performance Indicators (KPIs), which measure progress toward a business
goal, as well as other information about their business process. Business analysts use the BAM
portal to oversee the creation of observation models, which are high-level definitions of the
visibility requirements within the business process. Administrators use it for a variety of monitoring
activities, including monitoring the health of the business process management system. You can
customize BAM to enhance the performance and experience for your users.
Microsoft SQL Server 2005 Reporting Services (SSRS) delivers enterprise, Web-enabled
reporting functionality so you can create reports that draw content from a variety of data sources,
publish reports in various formats, and centrally manage security and subscriptions. You can use
SSRS to report aggregated data as well as real-time data.
You can also install Microsoft Office PerformancePoint Server 2007 on the Web server to build
highly visual and interactive scorecards and dashboards that can keep you up to date on what is
happening and how it relates to the overall performance of your organization. The applications
functionality goes beyond simple monitoring and enables you to seamlessly move to analyzing
and understanding why things are happening. You can zero in on off-target key performance
indicators (KPIs) and quickly take steps to bring about change. PerformancePoint Server 2007
34

provides you with two ways to display critical information: scorecards and dashboards. Installing
and configuring PerformancePoint Monitoring Server is not covered in this guide.

Hardware Requirements
The Web server must meet the minimum hardware requirements for running Microsoft BizTalk
Server 2006 R2. For more information, see the Hardware Requirement section in Installing and
Configuring BizTalk Server 2006 R2 on Windows Server 2003 at http://go.microsoft.com/fwlink/?
linkid=81041.

Software Requirements
The Web server must meet the minimum software requirements for running Microsoft BizTalk
Server 2006 R2. For more information, see the Software Requirements section in Installing and
Configuring BizTalk Server 2006 R2 on Windows Server 2003 at http://go.microsoft.com/fwlink/?
linkid=81041.

Domain Accounts
The following table lists the Windows groups for the domain administrator to create for the SQL
Server configuration. These group accounts can be either global domain accounts or universal
domain accounts.
Group Name (suggested)

Purpose

BAM Portal Users

Has access to BAM Portal Web site.

The following table lists the domain accounts for the domain administrator to create in the domain
controller for the SQL Server configuration. The domain administrator must ensure the accounts
are members of the group indicated.
Account Name

Type

Member of Group

Purpose

User

Domain Users

Local
administrators

SSO
Administrators

BizTalk Server
Administrators

This account with

administrative rights is required
for installing and configuring
BizTalk Server. Rights can be
revoked or the account
disabled as soon as setup and
configuration are complete.

(suggested)

BTInstaller

SQLService

Service

Domain Users

This is the service account for

running SQL Server services.

BTService

Service

Domain Users

This is a generic BizTalk

35

Account Name

Type

Member of Group

Purpose

(suggested)

Server service account. If you

dont want to create dedicated
accounts for the various
BizTalk Server services, you
can use this account.
BAMMgmtWSUser

BAMAppPoolUser

User

User

Domain Users

IIS_WPG

Domain Users

IIS_WPG

User account for BAM

Management Web service
(BAMManagementService) to
access various BAM
resources. BAM Portal calls
BAMManagementService to
retrieve information about user
credentials, activities, views,
alerts, and configuration
information. BAM metadata is
thus secured by restricting
back-end access to the
account used by the BAM
Management Web service logon.
Application pool account for
BAMAppPool which hosts BAM
Portal Web site

Installation and Configuration Tasks

The instructions of this guide are based on Windows Server 2003 with Service Pack 2. Windows
Server 2003 Service Pack 1 is the minimum requirement for install BizTalk Server 2006.
The following tasks need to be performed on the Web Server:

Task 4.1: Add Windows Components

Task 4.2: Install SQL Server 2005

Task 4.3: Install SQL Server 2005 SP2

Task 4.4: Install BizTalk Server

Task 4.5: Configure BizTalk Server

You must log on as Contoso\BTInstaller or a user with the same access credentials to configure
the Web Server.

36

Task 4.1: Add Windows Components

In this task, you add the Internet Information Services components.
What is this for and why do I need this?
BAM portal is an ASP.NET application. It requires IIS.
Estimated time to complete: 5 minutes
To add the IIS Windows component
1. Click Start, point to Control Panel, and then click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. Click Application Server, and then click Details.
4. Select Internet Information Services, and then click OK.
5. Click Next.
6. Click Finish.

Task 4.2: Install SQL Server 2005

In this task, you install SSRS, and SSNS client components.
What is this for and why do I need this?
SSRS provides additional reporting functionality for BAM.
BAM Portal requires SSNS Server component or client component. If these arent installed on the
server, you cant configure the Web site for BAM portal.
Estimated time to complete: 20 minutes
To install SQL Server 2005 SSRS and SSNS client component
1. Insert the SQL Server 2005 installation disk into the CD-ROM drive. If the SQL
Server 2005 Setup page does not appear, double-click default.hta located in the
Servers folder.
2. On the Start splash screen, click Server components, tools, Books Online, and
samples.
3. On the End User License Agreement page, click I accept the licensing terms and
conditions, and then click Next.
4. On the Installing Prerequisites page, click Install, and then click Next.
5. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.
6. On the System Configuration Check page, ensure that there are no errors before you
continue, and then click Next.
7. On the Registration Information page, type your name and company, and then click
Next.
8. On the Components to Install page, click Advanced.
9. On the Feature Selection page, click Reporting Services, and then select Will be
37

installed on local hard drive.

10. On the Feature Selection page, expand Notification Services, click Client
Components, and then select Will be installed on local hard drive.
11. On the Feature Selection page, click Next.
12. On the Instance Name page, click Default instance, and then click Next.
13. On the Service Account page, enter or select the following values, and then click Next.
Name

Value

Use a domain user account

(selected)

Username

SQLService

Password

pass@word1

Domain

Contoso

Reporting Services

(selected)

14. On the Report Server Installation Options page, click Next.

15. On the Error and Usage Report Settings page, click Next.
16. On the Ready to Install page, click Install.
17. On the Setup Progress page, click Next.
18. On the Completing Microsoft SQL Server 2005 Setup page, click Finish.

Task 4.3: Install SQL Server 2005 SP2

In this step, you install SQL Server 2005 Service Pack 2.
What is this for and why do I need this?
BizTalk Server 2006 R2 requires SQL Server 2005 SP2.
Estimated time to complete: 20 minutes
To install SQL Server 2005 SP2
1. Open SQLServer2005SP2-KB921896-x86-ENU.exe. The file name can be different
depending on the language and the types of CPU.
2. On the Welcome page, click Next.
3. On the License Terms page, select I accept the agreement, and then click Next.
4. On the Feature Selection page, make sure all the features are selected, and then click
Next. If you cannot select MSSQLServer and Database Services, make sure the
current node is the active node.
5. On the Authentication page, click Next.
6. On the Remote User Account page, enter the account information for domain user, and
38

then click Next.

7. On the Error and Usage Reporting Settings page, click Next.
8. On the Running Processes page, ignore the computer reboot warning and click Next.
9. On the Ready to Install page, click Install.
10. On the Installation Progress page, click Next.
11. On the Installation Complete page, click Next.
12. On the Additional Information page, click Finish.
13. Reboot the SQL Server computer.

Task 4.4: Install BizTalk Server

In this task, you install the BizTalk Server BAM Portal component.
What is this for and why do I need this?
The BizTalk Server installation occurs in two parts. This task is the first part that copies the
necessary files to the local machine to prepare for server installation.
Estimated time to complete: 20 minutes
To install the BizTalk Server BAM Portal Component
1. Run setup.exe to install BizTalk Server 2006 R2.
2. On the Start page, click Install Microsoft BizTalk Server 2006 R2 on this computer.
3. On the Customer Information page, enter information in the User name box, the
Organization box, and the Product key box, and then click Next.
4. On the License Agreement page, read the license agreement, select Yes, I accept the
terms of the license agreement, and then click Next.
5. On the Component Installation page, clear all the selections, expand Portal
Components, and then select Business Activity Monitoring. Click Next to continue.
6. On the Redistributable Prerequisites page, click Automatically install the
redistributable prerequisites from the web, and then click Next.
Note
You must have an Internet connection to download and install the redistributable
prerequisites automatically. Otherwise you can consider using the other options.
7. On the Summary page, click Install.
8. On the Installation Completed page, clear Launch BizTalk Server Configuration
check box, and then click Finish.

Task 4.5: Configure BizTalk Server

In this task, you configure BizTalk Server, including the BAM component.
What is this for and why do I need this?
39

This is the second part of the BizTalk Server installation process. It launches the BizTalk Server
Configuration to configure and install the selected BizTalk Server components on the local
machine.
Estimated time to complete: 10 minutes
To configure BizTalk Server
1. Click Start, point to All Programs, point to Microsoft BizTalk Server 2006, and then
click BizTalk Server Configuration.
2. On the Microsoft BizTalk Server 2006 Configuration page, choose Custom
Configuration, enter the following values, and then click Configure.
Name

Value

Database server name

(the host name of the SQL Server where

the master secret server is configured.

Service credential: User name

Contoso\BTService

Service credential: Password

pass@word1

3. In the left pane, click Group. In the details pane, enter the following values:
Name

Value

Enable BizTalk Server Group on this

computer

(checked)

BizTalk Management Database: Server

Name

(the host name of the SQL Server)

BizTalk Management Database: Database (the default name is BizTalkMgmtDb)

Name
4. In the left pane, click BAM Portal, and then enter or select the following values:
Name

Value

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

5. Click Apply Configuration.

40

6. On the Summary page, to apply the configuration, click Next.

7. Verify that the Configuration Result is Success, and then click Finish.
8. Close Microsoft BizTalk Server 2006 Configuration.

Step 5: Installing and Configuring Business

Analysts Workstation
Business analysts create BAM activities and BAM views. This is done from Excel. Other than
Excel, the BizTalk Server BAM client component is also required. The BAM client includes an
Excel Add-in.

Hardware Requirements
The same hardware requirements as Office 2007 or Office 2003.

Software Requirements
The same software requirements as Office 2007 or Office 2003.

Installation and Configuration Tasks

The instructions are based on Windows Vista.
The following tasks need to be performed on the business analysts workstation:

Task 5.1: Install MSXML 4.0 Service Pack 2

Task 5.2: Install Office Excel

Task 5.3: Install BizTalk Server BAM Client

Task 5.4: Enable BAM Add-in from Excel

You must log on with an account with local administrator credentials to configure the workstation.

Task 5.1: Install MSXML 4.0 Service Pack 2

In the following procedure, you install Microsoft MSXML 4.0 Service Pack 2 (SP2). MSXML 4.0
SP2 can be downloaded at http://go.microsoft.com/fwlink/?LinkId=52926. It is a complete
replacement of MSXML 4.0 and MSXML 4.0 Service Pack 1 (SP1).
What is this for and why do I need this?
MSXML 4.0 SP2 is required by Excel to export a BAM definition to an XML file.
Note

If you dont have MSXML 4.0 SP2, you will get the following error message when you
export a BAM definition to an XML file from Excel.

ActiveX component cant create object.

Estimated time to complete: 10 minutes

41

To install MSXML 4.0 SP2

1. Run msxml.msi.
2. On the Open File Security Warning page, click Run.
3. On the welcome screen, click Next.
4. On the End-User License Agreement page, click I accept the terms in the License
Agreement, and then click Next.
5. On the Customer Information page, type user name and organization, and then click
Next.
6. On the Chose Setup Type page, click Install Now.
7. On the User Account Control page, click Continue.
8. On the Completing the MSXML 4.0 SP2 Parser and SDK Setup Wizard page, click
Finish.

Task 5.2: Install Office Excel

In the following procedure you install Microsoft Office Excel 2007.
What is this for and why do I need this?
Microsoft Office Excel is used for the Business Activity Monitoring (BAM) feature in BizTalk
Server. Business analysts use the BAM Excel Add-in with Excel to define the business processes
you want to monitor, and the way in which business users see the data collected by BAM.
Note
Office Excel 2003 with SP2 is also supported.
Estimated time to complete: 20 minutes
To install Microsoft Office Excel 2007
1. Insert the Office 2007 installation disk into the CD-ROM drive.
2. From Choose the installation you want, click Customize.
3. Click the Installation options tab.
4. Click Microsoft Office Excel, select Run from My Computer, and set the rest Not
Available.
5. Click Install Now.
6. Click OK twice.

Task 5.3: Install BizTalk Server BAM Client

In the following procedure, you install the BizTalk Server BAM client component, which is the
Excel BAM Add-in.
What is this for and why do I need this?
The BAM client component provides the Excel Add-in for creating BAM activities and BAM views.
42

Estimated time to complete: 15 minutes

To install BAM client
1. Run Setup.exe.
2. On the User Account Control page, click Continue.
3. On the welcome screen, click Install Microsoft BizTalk Server 2006 R2 on this
computer.
4. On the Customer Information page, type your user name and organization, and then
click Next.
5. On the License Agreement page, click Yes, I accept the terms of the license
agreement, and the click Next.
6. On the Component Installation page, clear all the selections. Expand Additional
Software, select BAM Client, and then click Next.
7. On the Summary page, click Install.
8. On the Installation Completed page, click Finish.

Task 5.4: Enable BAM Add-in from Excel

In the following procedure you enable BAM Add-in from Excel.
What is this for and why do I need this?
You must enable the BAM Add-in from Excel before it can be used.
Estimated time to complete: 5 minutes
To enable BAM add-in from Excel
1. Click Start, expand All Programs, expand Microsoft Office, and then click Microsoft
Office Excel 2007.
2. From Excel, click the Microsoft Office button, and then click Excel Options.
3. From Excel Options, click Add-Ins on the left pane. In Manage, select Excel Add-ins,
and then click Go.
4. From Add-Ins, select Business activity Monitoring, and then click OK.
5. If you get a Repairs to Bam.xla prompt, click Close.

Step 6: Installing and Configuring BizTalk Server

Application Developers Workstation
The developer workstation includes all the components installed on the runtime servers as well as
the business analysts workstation. You can also refer to Installing and Configuring BizTalk
Server 2006 R2 on Windows Vista or Installing and Configuring BizTalk Server 2006 R2 on
Windows XP at http://go.microsoft.com/fwlink/?linkid=81041 depending your operating system to
configure the developers workstation.
43

44