ContentsInstalling BizTalk Server 2013 and BAM in a Multi-Computer Environment....................................2

Installation for High Availability....................................................................................................2Installation for Separate Runtime and Administration..................................................................2Installing and configuring Distributed Transaction Coordinator....................................................3Considerations for using DTC in a BizTalk Server environment..................................................3Considerations for Using SQL Server..........................................................................................4

Considerations when SQL Server Is Installed on a Remote Computer....................................4Supported SQL Server Topologies...........................................................................................4How to maintain and troubleshoot BizTalk Server databases..................................................5

Business Activity Monitoring (BAM).............................................................................................5Installing BAM.......................................................................................................................... 6Configuring BAM...................................................................................................................... 8Installing and Configuring SQL Server for BAM.......................................................................8

Configuring BAM Primary Import, BAM Archive, BAM Star Schema, BAM Analysis, and BAM Notification Services Application databases.............................................................9

Notification Services Roles - SQL Server 2008 R2 Only.....................................................10BAM Scale-Out Alerts Topology.......................................................................................10

BAM Portal............................................................................................................................. 11Configuring Multiple BizTalk Groups to Reference a Single BAM Database..........................12BAM Client............................................................................................................................. 12

Enabling BAM Add-in from Excel...............................................................................................13Windows Groups and Service Accounts....................................................................................13

Windows Groups Used In BizTalk Server...............................................................................14User and Service Accounts Used In BizTalk Server...............................................................17

Databases Used by BizTalk Server...........................................................................................20Installing BizTalk Server in a Multiple Server environment........................................................23Considerations for clustering BizTalk Server in a Multiple Server environment.........................23Using SCOM to Monitor BizTalk Server.....................................................................................24See Also.................................................................................................................................... 25

Installing BizTalk Server 2013 and BAM in a Multi-Computer EnvironmentThere are many things to consider when planning a multicomputer installation of Microsoft® BizTalk® Server. Often the network infrastructure exists and BizTalk Server must coexist with other network applications. This guide describes some of the considerations that apply to the BizTalk Server and Business Activity Monitoring (BAM) installation in a multicomputer, distributed deployment. This information helps you plan the installation and configuration of BizTalk Server and Business Activity Monitoring (BAM) and the applications and components it depends on.

To ensure that you are reading the most up-to-date information, you can download the latest version of this document from Installation Guides Related to BizTalk Server 2013 (http://go.microsoft.com/fwlink/p/?LinkID=269582). The single server installation guide is available at http://go.microsoft.com/fwlink/p/?LinkID=320162. The single server installation guide contains important procedures and more background information that is not duplicated in this document. For example, the following information is discussed in detail in the single server installation guide:

Detailed installation procedures Descriptions of BizTalk Server features and dependencies Details of BizTalk Server basic configuration settings Software and hardware requirements CAB file redistributable component list

Installation for High AvailabilityBizTalk Server provides a high availability solution that uses network load balancing (NLB) clustering and failover clustering. A high availability solution helps minimize the downtime if there is a hardware or software failure. NLB and failover clusters complement each other in complex architectures. NLB clustering is used for to load balance requests between front-end web servers. Failover clustering provides high availability for the BizTalk Server in-process hosts, the Enterprise Single Sign-On Master Secret Server and BizTalk Server databases.

For more information about BizTalk Server with Windows Server clusters, see Improving Fault Tolerance in BizTalk Server by Using a Windows Server 2008 failover cluster or Windows Server 2003 server cluster.

Installation for Separate Runtime and AdministrationBizTalk Server supports various installation scenarios in the production environment. For example, you can install, configure, and deploy a runtime-only installation on one computer and an administration tools-only installation on a second computer.

2

During an Administration tools-only installation, the following components are installed: BizTalk Administration console, BM.exe, and BTSDeploy.exe. The following considerations apply to an Administration Tools-only installation of BizTalk Server:

SQL Server Agent must be running on all computers that are hosting BizTalk Server MessageBox databases. SQL Server Agent is required to track message bodies in the BizTalk Server Messaging engine.

When you run the BizTalk Server Configuration Wizard, you create an Analysis Services database.

Using the BizTalk Tracking database with SQL Server 2008 R2 Analysis Services is not supported.

Using named instances of SQL Server 2008 R2 Analysis Services is not supported.

To install only Administration tools for BizTalk Server, select only Administration Tools during Setup. After the installation is complete, open the custom configuration manager and join an existing Enterprise Single Sign-On (SSO) system and BizTalk group.

Installing and configuring Distributed Transaction CoordinatorBefore installing and configuring BizTalk Server in a multicomputer environment, enable network DTC access and network COM+ access on all BizTalk servers and any remote SQL Server instances used by BizTalk Server. To install and configure network DTC access and network COM+ access, see Post-installation Steps for BizTalk Server 2013 (http://technet.microsoft.com/library/jj248704(v=bts.80).aspx).

Considerations for using DTC in a BizTalk Server environment All BizTalk servers and SQL Servers in a group must have the same remote procedure call

(RPC) authentication level applied. The DTC proxy may not correctly authenticate DTC when the computers use different operating systems, are joined to workgroups, or are in different domains that do not trust each other. For more information, see MSDTC Fails to Mutually Authenticate (http://go.microsoft.com/fwlink/p/?LinkId=220974) in the DTC Administrator's Guide.

If using a firewall, open the required DTC and RPC ports. For more information, see Service overview and network port requirements for Windows (http://support.microsoft.com/kb/832017).

To ensure that the DTC settings are correct, use the DTC Tester and DTC Ping tools. These tools and more DTC troubleshooting are described at BizTalk Server - Troubleshooting Problems with MSDTC (http://go.microsoft.com/fwlink/p/?LinkID=313651).

3

Considerations for Using SQL ServerThis section describes considerations for using SQL Server in a multicomputer installation of BizTalk Server.

Considerations when SQL Server Is Installed on a Remote ComputerThe following conditions apply regarding remote computers.

SQL Server Client Tools Connectivity must be installed on the local BizTalk Server computer when SQL Server is remote. The SQL Server Client Tools Connectivity installs the client libraries required to communicate with the remote instance of SQL Server. The version of the SQL Server Client Connectivity tools on the local BizTalk Server computer must be the same version that is installed on the remote SQL Server.

SQL Server OLAP client must be installed on the local computer if you plan to use Analysis Services remotely.

The remote SQL Server must be running during BizTalk Server configuration. The TCP and UDP ports you specified during the SQL Server setup process must be open

during BizTalk Server configuration. To configure BAM tools, install SQL Server Management Tools - Basic and Complete on the

BizTalk BAM Server. For more information about setting up and configuring BAM in a multi-computer environment, see Install and Configure BAM (Business Activity Monitoring) in a Multi-Computer Environment (http://go.microsoft.com/fwlink/p/?LinkID=208597).

Named instances of SQL Server 2008 R2 Analysis Services are not supported.

Supported SQL Server TopologiesThe following are the supported configurations for using SQL Server with BizTalk Server 2013:

Location of SQL Server in relation to BizTalk Server

Supported

SQL Server 2012: Installed locally on the BizTalk Server

Yes

SQL Server 2012: Installed on a remote computer

Yes

SQL Server 2008 R2 SP1: Installed locally on the BizTalk Server

Yes

SQL Server 2008 R2 SP1: Installed on a remote computer

Yes

Important

4

SQL Server 2012 and SQL Server 2008 R2 SP1 are the minimum requirements. Any additional service packs and Windows Updates are supported and should be installed.

How to maintain and troubleshoot BizTalk Server databasesFor information maintaining and troubleshooting BizTalk Server databases, see How to maintain and troubleshoot BizTalk Server databases (http://support.microsoft.com/kb/952555).

Business Activity Monitoring (BAM)BizTalk Server provides several tools for information workers, among them BAM. A basic understanding of the component architecture helps you plan the BizTalk Server installation to utilize the server resources available to you.

Business Activity Monitoring (BAM) is a collection of tools used to manage aggregations, alerts, and profiles to monitor relevant business metrics, known as key performance indicators or KPIs.BAM is a module that gives you end-to-end visibility into your business processes to provides information about the status and results of various operational processes and transactions. You can use the BAM output to address problem areas and resolve issues within your business. For more information about BAM life cycle, see Business Activity Monitoring (BAM) poster at http://go.microsoft.com/fwlink/p/?LinkId=120003.

BAM consists of three layers:

Presentation and tools Web services or processing Database or platform services

Each of these layers and its relation to the installation process is described in the following table.

Layer What it does Examples Where installed

Presentation and Tools

Provides front-end services to business users and developers. Displays data, allows business users and developers define and manage templates and profiles; among other functions.

Office Excel, BAM Portal.

Excel, management tools, and custom user interfaces are installed on the business user's or developer's workstation. The BAM portal and custom web applications built on the BAM infrastructure are installed on a server.

Web Services and Processing

Link the presentation and database layers;

Windows SharePoint Services (WSS),

On a server with IIS, SQL Notification

5

Layer What it does Examples Where installed

implementation of business rules and processes; data aggregation and analysis.

Trading Partner Management Web Service, BAM Management Web Service, and the BizTalk Server engine.

service, and possibly custom web services, depending on the application. The BizTalk host services can also be installed on this server, or on a separate server in multiple computer configuration that has three or more computers.

Database and Platform Services

Data storage and retrieval; security and authentication; networking; operating system functions

SQL Server, Windows Server, Enterprise Single Sign-On (SSO), and fail-over and NLB clustering

On a server with Windows Server, SQL Server. For performance reasons, this server typically does not run the BizTalk host services.

Installing BAMTo set up BAM (Business Activity Monitoring) in a multi-computer environment on a Windows Server 2008 R2 and SQL Server 2008 R2 platform, see Install and Configure BAM (Business Activity Monitoring) in a Multi-Computer Environment (http://go.microsoft.com/fwlink/p/?LinkID=208597).

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

Runtime Environment Design-time Environment Usage-time Environment

A basic BizTalk Server runtime environment can include the following servers:

BizTalk Server 2013 SQL Server 2008 R2 or

SQL Server 2012 BizTalk BAM Server Web Server

There are three roles involved during the BAM development and deployment process. Roles include:

Business analyst Business administrator Application developer

After a BAM solution is implemented and deployed, business end users can view the reports generated by various reporting tools. These tools include

BAM Portal SQL Server Reporting

Services

6

Runtime Environment Design-time Environment Usage-time Environment

Microsoft PerformancePoint Monitoring Server

Custom BAM reporting applications

The following table describes the BAM components to install:

Category BAM Component Purpose

Portal Components Business Activity Monitoring Selecting the Business Activity Monitoring component installs the software that gives business users a real-time view of their heterogeneous business processes, enabling them to make important business decisions.

Additional Software BAM Alerts Installs the necessary software that enables BizTalk Server to provide Business Activity Monitoring (BAM) alerts.

BAM Alerts with SQL Server 2012 uses the Database Mail feature. SQL Notification Services is not used or supported.

BAM Alerts with SQL Server 2008 R2 uses SQL Notification Services.

BAM Client Selecting the BAM Client component installs the necessary client-side software that allows business users to work with the Business Activity Monitoring feature of BizTalk Server.

BAM-Eventing Select the BAM-Eventing Support component installs the software for the BAM-Eventing Interceptors for Windows

7

Category BAM Component Purpose

Workflow Foundation and Windows Communication Foundation. Selecting this component also installs the BAM Event API that is used to send events to the BAM database from custom applications. BAM-Eventing Support is part of the Business Activity Monitoring feature in BizTalk Server.

Configuring BAMTo configure BAM components, open BizTalk Server Configuration and choose Custom Configuration. Custom configuration allows you to configure the server with advanced configuration options. With custom configuration, you can selectively configure or unconfigure each feature. For information on customizing your configuration, see Custom Configuration (http://technet.microsoft.com/library/aa547917(v=bts.80).aspx).

Installing and Configuring SQL Server for BAMFor BizTalk Server 2013 and BAM, install SQL Server 2008 R2 SP1 or SQL Server 2012. To install SQL Server, see BizTalk Server 2013: Preparing Your Computer for Installation (http://technet.microsoft.com/library/jj248684(v=bts.80).aspx).

In addition to Database Services that required by the BizTalk Server core functions, 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)

Configure SQL Server Integration Services (SSIS): If your SQL Server is installed on a computer other than the BizTalk Server, then configure SSIS. In this task, you configure the SSIS to use the msdb database on a remote SQL Server.

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, modify the configuration file. For example, you can create more root folders of the type, SqlServerFolder, to manage packages in the msdb database of multiple instances of the Database Engine.If the service stops, you can also modify the configuration file to allow packages to continue running. This option displays more root folders in Object Explorer,

8

or specifies a different folder or more folders in the file system 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\100\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.

1. Open a Command Prompt.2. Change directory to %ProgramFiles%\Microsoft SQL Server\100\DTS\Binn3. Run the following command: notepad MsDtsSrvr.ini.xml4. 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 MsDtsServer7. From the Command Prompt, execute the following command: net start MsDtsServer

Configuring BAM Primary Import, BAM Archive, BAM Star Schema, BAM Analysis, and BAM Notification Services Application databasesYou can configure BAM Primary Import, BAM Archive, BAM Star Schema, BAM Analysis, and BAM Notification Services Application databases on different computers. The following are the software requirements when SQL Server is installed on a computer other than the BizTalk Server:

BAM feature Feature configuration BizTalk Server SQL Server

BAM Tools BAM Primary Import Tables and BAM Archive database

ADOMD.NET SQL Server Integration Services

SQL Server 2008 R2 or SQL Server 2012

BAM Tools Enable Analysis Services for BAM aggregations

SQL Server Integration Services

SQL Server 2008 R2 Analysis Services or SQL Server 2012 Analysis Services

BAM Notification Services Application Database

Enable Notification Services for BAM alerts

If using SQL Server 2008 R2, install SQL Server 2005 Notification Services Engine Components.

The BAM Alerts requirements are

If using SQL Server 2012, configure SQL Server Database Mail.

The BAM Alerts requirements are documented at

To configure the Integration Services

9

BAM feature Feature configuration BizTalk Server SQL Server

documented at Preparing Your Computer for Installation.

Preparing Your Computer for Installation.

The service account used for the OLAP service should have db_datareader permissions on the BAM Star Schema database.

Notification Services Roles - SQL Server 2008 R2 Only

This section only applies if SQL Server 2008 R2 is used.

You can install SQL Server Notification Services in a multicomputer environment where the Provider, Generator, and Distributor roles of Notification Services are on different computers. The following describes the dependencies in that scenario:

The AggregationEventProvider.dll should be installed on the computer that hosts the Provider role. This .dll file is installed when you install the BAM Alerts Aggregate Event Provider during the installation of BizTalk Server. The BAM Alerts Aggregate Event Provider is present if the BizTalk Runtime, Administration Tools, or Developer Tools and SDK are installed.

EmailNotification.xslt and FileNotification.xslt are required on the computer that hosts the Distributor role. You can copy the files in the following path from an existing BizTalk Server: <System Drive>:\Program Files\Microsoft BizTalk Server 2013\Tracking

Update the Notification Services Application definition file (.adf file) with the exact location of the .xslt files on the computer that hosts the Distributor role.

1. On the computer where BizTalk Server is installed, open the Notification Services command prompt.

2. Browse to <System Drive>:\Program Files\Microsoft BizTalk Server 2013\Tracking.3. Execute ProcessBamNsFiles.vbs to create the initial .adf file.4. Modify the .adf file with the path to the .xslt file.5. Execute ProcessBamNsFiles.vbs again to update the .adf file.6. Restart the BAMAlerts NT service.

BAM Scale-Out Alerts TopologyIf you are upgrading your existing BAM scale-out alerts topology to BizTalk Server 2013, then do the following steps on each server:

Note

Important

To update the Application definition file (.adf file)

10

1. Stop the Notification Service and then unregister an instance of Notification Service:a. In Programs, click Microsoft SQL Server 2005, click Configuration Tools, and

then click Notification Services Command Prompt.b. At the command prompt, type: net stop NS$<instance_name>. For example, type:

net stop NS$BamAlerts.c. To unregister the instance, type the following command: nscontrol unregister -

name BamAlerts. Unregistering an instance removes the registry entries, removes the NS$instance_name service (if present), and deletes the performance counters for the service.

2. Upgrade your servers that have Notification Services instances to a higher edition of SQL Server 2005 Notification Services.

Click or navigate to the Feature Pack for Microsoft SQL Server 2005 - December 2008 (http://go.microsoft.com/fwlink/?LinkId=154501).

3. To migrate your BAM databases based on the SQL Server version you are upgrading from, run the migration database command bm.exe program located in the BizTalk Server Tracking folder. For example, if SQL Server 2005 is upgraded to SQL Server 2008 R2, run the following in the command prompt with administrative credentials: bm.exe migrate-sql –From:sql2005 –To:sql2008 –NSUser:<username>.

4. Reregister the Notification Service on all the servers except the server where the migration program (bm.exe) is being used.a. Click Start, click Programs, click Microsoft SQL Server 2005, click Configuration

Tools, and then click Notification Services Command Prompt.b. At the command prompt, type: nscontrol register -name BamAlerts -server <NS

DB Server> -service -serviceusername "<NSServiceUserName>" -servicepassword "<NSServicePassword>" This enables Notification Services to log on to the correct database (this information is maintained in the registry of the service computer by nscontrol).

ImportantRemember to use the new Notification Services database server in the -server option when re-registering the service. In addition, use the same user name for the new Notification Services service as the old one.

5. Validate the BAM alerts: Open the Notification Services Command Prompt and type: nscontrol.exe status –name BAMAlerts –server <NS DB Server>.

BAM PortalThe Portal Components are a set of services used by business people to communicate, collaborate, and make decisions that enabliethem to interact, configure, and monitor business processes and workflows. To use this feature, install Internet Information Services (IIS) 8.0/7.5. Preparing Your Computer for Installation lists the IIS requirements.

11

Configuring Multiple BizTalk Groups to Reference a Single BAM Database

1. Configure the first BizTalk group with the BAM features. These features include BAM tools, the BAM Analysis database, BAM alerts, and the BAM portal.

2. 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 so it's 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.

NoteThe same Primary Import Tables (PIT) can be used but with different BAM Archive, BAM Analysis, and Star Schema databases. However, this option impacts all groups that use the same PIT.

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

NoteAll 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 BAM portal when configured against the same BAM databases.

4. Click Apply Configuration.

BAM ClientThe following are the software requirements when using the BAM client:

For the web client, you need Internet Explorer 8.0 or later and Office Web Components 11 version 4.0 or later.

If you are running the web client and using SQL Server 2008 R2 Analysis Services, install Microsoft SQL Server 2008 R2 Analysis Services 10.0 OLE DB Provider.

For the Excel client, you need Microsoft Excel® and the BAM Excel Add-in provided with BizTalk Server.

To share the BAM databases across multiple BizTalk groups

12

Enabling BAM Add-in from ExcelTo enable BAM add-in from excel, see Add the BAM Add-In to Microsoft Office Excel (http://go.microsoft.com/fwlink/p/?LinkId=201992).

Windows Groups and Service AccountsManually create all of the domain groups and accounts before you configure BizTalk Server in a multicomputer installation. The following information is useful in creating these groups and accounts.

In a multicomputer environment, BizTalk Server supports only domain groups and domain service accounts.

BizTalk Server supports only <NetBIOSDomainName>\<User> name formats for Windows groups and service accounts.

BizTalk Server supports only Active Directory domain groups and user accounts in multicomputer configurations. Domain groups include Domain Local groups, Global groups, and Universal groups, which are supported in both single computer and multicomputer environments.

In general, Domain Local Groups are not recommended because their use requires that all of the servers, including SQL Servers, in the BizTalk Server infrastructure belong to the same domain. This consideration does not apply to small networks where all of the servers and user accounts reside in a single domain. For more information about Active Directory groups, see http://technet.microsoft.com/library/cc733001.aspx.

Built-in accounts such as NT AUTHORITY\LOCAL SERVICE, NT AUTHORITY\NETWORK SERVICE, NT AUTHORITY\SERVICE, NT AUTHORITY\SYSTEM, and Everyone are not supported when you install and configure BizTalk Server in a multicomputer environment.

The user that runs the BizTalk Server configuration must belong to the following user groups: the Administrators group on the local computer, the System Administrators group on the SQL Server computer, the domain group used for the BizTalk Server Administrators group, and the domain group used for the SSO Administrators group.

Whenever possible, use the default account names created during setup. The BizTalk Server setup program automatically configures installed components to use the default accounts. Using the default names simplifies setup and configuration, but it is not always possible. For example, there can be multiple BizTalk Server groups within an Active Domain forest. In this situation, the account names must be modified to avoid conflicts. Or, your organization might use naming standards for service and user accounts so you change the default accounts to conform to the standard.

Windows Groups Used In BizTalk ServerThe following table lists the Windows groups and their membership used by BizTalk Server. It also identifies the SQL Server Roles or Database Roles for the group.

13

Group Group Description Membership SQL Server Roles or Database Roles

SSO Administrators

Administrator of the Enterprise Single Sign-On (SSO) service.For more information about SSO accounts, see "How to Specify SSO Administrator and Affiliate Administrators Accounts" at http://go.microsoft.com/fwlink/?LinkID=89383.

Contains service accounts for Enterprise Single Sign-On service. Contains users/groups that need to be able to configure and administer BizTalk Server and SSO service.Contains accounts used to run BizTalk Configuration Manager when configuring SSO master secret server.

db_owner SQL Server Database Role for the SSO.

securityadmin SQL Server Role for the SQL Server where SSO is located.

SSO Affiliate Administrators

Administrators of certain SSO affiliate applications. Can create/delete SSO affiliate applications, administer user mappings, and set credentials for affiliate application users.

Contains no service accounts. Contains account used for BizTalk Server Administrators.

BizTalk Server Administrators

Has the fewest 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

Contains users/groups that need to be able to configure and administer

BTS_ADMIN_USERS SQL Server Database Role in the following databases:BizTalkMgmtDb, BizTalkMsgBoxDb, BizTalkRuleEngineDb,

14

Group Group Description Membership SQL Server Roles or Database Roles

handlers, and receive locations, the BizTalk Server Administrators must be added to the Single Sign-On Affiliate Administrators. For more information, see "Managing BizTalk Server Security" in at http://go.microsoft.com/fwlink/?linkid=110476.

BizTalk Server.

BizTalkDTADb, BAMPrimaryImport. db_owner SQL Server Database Role for the following databases:BAMStarSchema, BAMPrimaryImport, BAMArchive, BAMAlertsApplication, BAMAlertsNSMain. NSAdmin SQL Server Database Role in the following databases: BAMAlertsApplication, BAMAlertsNSMain. SQL Server Database Role in the following databases: BizTalkDTADb, BizTalkMgmtDb. OLAP Administrators on the computer that hosts the BAMAnalysis OLAP database.

BizTalk Server Operators

Has a low privilege role with access only to monitoring and troubleshooting actions.

Contains user/groups that monitor solutions. Contains no service accounts.

BTS_OPERATORS SQL Server Database Role in the following databases: BizTalkDTADb, BizTalkEDIDb, BizTalkMgmtDb, BizTalkMsgBoxDb, BizTalkRuleEngineDb.

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 In-Process host in your environment. Includes accounts with access to In-Process BizTalk Hosts (hosts processes in

Contains service accounts for the BizTalk In-Process host instance in the host that

BTS_HOST_USERS SQL Server Database Role in the following databases:BizTalkMgmtDb, BizTalkMsgBoxDb, BizTalkRuleEngineDb, BizTalkDTADb,

15

Group Group Description Membership SQL Server Roles or Database Roles

BizTalk Server, BTSNTSvc.exe). the BizTalk Host Group is designated for.

BAMPrimaryImport. BAM_EVENT_WRITER SQL Server Database Role in the BAMPrimaryImport.

BizTalk Isolated Host Users

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.

Contains service accounts for the BizTalk Isolated host instance in the host that the Isolated BizTalk Host Group is designated for.

BTS_HOST_USERS SQL Server Database Role in the following databases: BizTalkMgmtDb, BizTalkMsgBoxDb, BizTalkRuleEngineDb, BizTalkDTADb, BAMPrimaryImport.

EDI Subsystem Users

Has access to the EDI database. Contains service accounts for BizTalk Base EDI service.

EDI_ADMIN_USERS SQL Server Database Role in the BizTalkEDIDb.

BAM Portal Users

Has access to BAM Portal website. Everyone group is used for this role by default.Contains no service accounts.

BizTalk SharePoint Adapter Enabled Hosts

Has access to Windows SharePoint Services Adapter Web Service.

Contains service accounts for the BizTalk host instance to use the SharePoint Adapter.

BizTalk B2B Operators

A new BizTalk role that reduces the onus on the Administrators to perform

Contains users/groups

BTS_OPERATORS SQL Server Database Role in

16

Group Group Description Membership SQL Server Roles or Database Roles

Group all Party management operation. This role allows windows users associated with the role to perform all party management operations.

that must be able to configure and administer BizTalk Server TPM data and monitor solutions.

the following databases: BizTalkDTADb, BizTalkMgmtDb, BizTalkMsgBoxDb, BizTalkRuleEngineDb, and BAMPrimaryImport

User and Service Accounts Used In BizTalk ServerThe following table lists the Windows user or service accounts and group affiliations used by BizTalk Server. It also identifies the SQL Server Roles or Database Roles for the accounts.

User User Description Group Affiliation SQL Server Roles or Database Roles

Enterprise Single Sign-On Service

Service account used to run Enterprise Single Sign-On Service, which accesses the SSO database.

SSO Administrators

BizTalk Host Instance Account

Service account used to run BizTalk In-Process host instance (BTNTSVC).

BizTalk Application Users

BizTalk Isolated Host Instance Account

Service account used to run BizTalk Isolated host instance (HTTP/SOAP).

BizTalk Isolated Host UsersIIS_WPG

Rule Engine Update Service

Service account used to run Rule Engine Update Service, which

RE_HOST_USERS SQL Server Database Role in the

17

User User Description Group Affiliation SQL Server Roles or Database Roles

receives notifications to deployment/undeployment policies from the Rule engine database.

BizTalkRuleEngineDb.

BizTalk Base EDI service

Service account used to run BizTalk Base EDI service, which processes EDI documentations.

ImportantThe Base EDI adapter was deprecated in BizTalk Server 2006 R2. The Base EDI adapter can be used in upgrade scenarios, but for new installations of BizTalk Server, use the native EDI and AS2

EDI Subsystem UsersIn-Process BizTalk Host Groups hosting the Base EDI adapter.

18

User User Description Group Affiliation SQL Server Roles or Database Roles

functionality.

BAM Notification Services User

Service account used to run BAM Notification Services, which accesses the BAM databases.

SQLServer2005NotificationServicesUser$<ComputerName>

NSRunService SQL Server Database Role in the following databases:BAMAlertsApplication, BAMAlertsNSMain. BAM_ManagementNSReader SQL Server role for the BAMPrimaryImport.

BAM Management Web Service User

User account for BAM Management Web service (BAMManagementService) to access various BAM resources. BAM Portal calls BAMManagementService with the user credentials logged on the BAM Portal to manage alerts, get BAM definition XML and BAM views.

IIS_WPG NSSubscriberAdmin SQL Server Database Role in the following databases:BAMAlertsApplication, BAMAlertsNSMain. BAM_ManagementWS SQL Server role for the BAMPrimaryImport.

BAM Application Pool Account

Application pool account for BAMAppPool, which hosts the BAM Portal website.

IIS_WPG

Important

19

For more information about Windows groups and service accounts used in BizTalk Server, see Windows Groups and User Accounts in BizTalk Server.

Databases Used by BizTalk ServerThe following is the list of SQL Server databases used in BizTalk Server:

Data store name

Default database name Volume Growth Description

SSO Database SSODB Low Low This Enterprise Single Sign-On credential database securely stores the user name and password.

BizTalk Management Database

BizTalkMgmtDb Low Low This database is the central meta-information store for all instances of BizTalk Server.

BizTalk MessageBox Database

BizTalkMsgBoxDb High Medium The BizTalk Server engine uses this database for routing, queuing, instance management, and various other tasks.

NoteAuto Update Statistics, Auto Create Statistics, and the Parallelism setting are purposely turned off in the SQL Server database instance that hosts the BizTalk Server BizTalkMsgBoxDB database. Do not enable these settings.

BizTalk Tracking Database

BizTalkDTADb High High This database stores business and health monitoring data tracked by

20

Data store name

Default database name Volume Growth Description

the BizTalk Server tracking engine.

Rule Engine Database

BizTalkRuleEngineDb Low Low This database is a repository for policies, which are sets of related rules and vocabularies. Vocabularies are collections of user-friendly, domain-specific names for data references in rules.

BizTalk Base EDI Database

BizTalkEDIDb Low Low This database stores state for the electronic data interchange (EDI) adapter. The Base EDI adapter was deprecated in BizTalk Server 2006 R2. The Base EDI adapter can be used in upgrade scenarios, but for new installations of BizTalk Server, use the native EDI and AS2 functionality.

BAM Primary Import Database

BAMPrimaryImport Medium Medium This database collects raw BAM tracking data.

BAM Archive Database

BAMArchive Medium Medium This database archives old business activity data. Create a BAM Archive database to minimizes the accumulation of business activity data in the BAM Primary Import database.

BAM Star Schema Database

BAMStarSchema Medium Medium This database contains the staging table, and the measure and dimension tables.

BAM Notification

BAMAlertsApplication Medium Medium This database contains alert information for BAM

21

Data store name

Default database name Volume Growth Description

Services Application database

notifications. For example, when you create an alert using the BAM portal, entries are inserted in this database that specify the conditions and events to which the alert pertains, as well as other supporting data for the alert.

BAM Notification Services Instance database

BAMAlertsNSMain Medium Medium This database contains instance information that specifies how the notification services connect to the system that BAM is monitoring.

List of Windows SharePoint Services DatabasesThe following is the list of SQL Server databases used by Windows SharePoint Services:

Data store name Default database name

Volume Growth Description

Windows SharePoint Services configuration database

User-defined Low Low This database contains all of the global settings for the server.

Windows SharePoint Services content database

User-defined Medium Medium This database contains all of the site content, such as list items and documents.

Installing BizTalk Server in a Multiple Server environment1. Install Active Directory Domain Services - The first step required to install BizTalk Server

into a multiple server environment is to install Active Directory domain services for the various

22

BizTalk Server groups and accounts. To create the Active Directory domain, refer to the following:

Windows Server 2008 R2: AD DS Installation and Removal Step-by-Step Guide (http://go.microsoft.com/fwlink/?LinkID=160742)

Windows Server 2012: Install Active Directory Domain Services (http://technet.microsoft.com/library/hh472162.aspx)

The BizTalk Server groups described in the User and Service Accounts Used In BizTalk Server table must be created manually before installing BizTalk Server into a multiple server environment.

2. Install Multiple Instances of SQL Server as needed – If your load requirements dictate that you need multiple MessageBox databases or that you need to spread the BizTalk Server I/O load over multiple SQL Server instances, then install more SQL Server instances as required. For more information about performance testing your BizTalk Server environment, see BizTalk Server Performance Optimizations Guide (http://go.microsoft.com/fwlink/p/?LinkID=150492). For more information about optimizing BizTalk Server database performance, see BizTalk Server Database Optimization whitepaper (http://go.microsoft.com/fwlink/p/?LinkID=153594).

3. Install Multiple BizTalk Server computers into your BizTalk Server Group as needed – If your load requirements dictate that you need multiple BizTalk Server computers into your BizTalk Server group, then use the BizTalk Server Enterprise Edition to scale out your processing requirements across multiple BizTalk Servers. For a table that lists each of the BizTalk Server Editions and their capabilities, see BizTalk Server Editions page (http://go.microsoft.com/fwlink/p/?LinkID=185239).

Many of the Enterprise level features of BizTalk Server such as clustering, adding multiple servers to a group, and native 64-bit processing are only available with the Enterprise edition of BizTalk Server.

Considerations for clustering BizTalk Server in a Multiple Server environment Clustering MSDTC – The Microsoft Distributed Transaction Coordinator (MSDTC) is a

central component of any BizTalk Server environment. If other components of the BizTalk Server environment are clustered, it is recommended to also cluster MSDTC. For more information about clustering MSDTC, see How to Cluster MSDTC (http://go.microsoft.com/fwlink/p/?LinkId=189514).

Install SQL Server Failover Clustering – To provide high availability/fault tolerance for the BizTalk Server databases, it is recommended that the BizTalk Server databases are installed on a SQL Server failover cluster. For information on installing SQL Server failover cluster, refer to the following:

SQL Server 2008 R2: Getting Started with SQL Server 2008 R2 Failover Clustering (http://msdn.microsoft.com/library/ms189134(v=sql.105).aspx).

Important Important

23

SQL Server 2012: Windows Server Failover Clustering (WSFC) with SQL Server (http://msdn.microsoft.com/library/hh270278.aspx)

Once SQL Server is configured for high availability/fault tolerance, then the SQL Server clustered instance can be referenced just as any other SQL Server instance by the BizTalk Server configuration.

Configure the Enterprise Single Sign-On Master Secret Server as a cluster resource – A failure of the Enterprise Single Sign-On Master Secret Server can cause a system-wide failure of the BizTalk Server environment. It is recommended to configure the Enterprise Single Sign-On Master Secret Server for high availability/fault tolerance by configuring the Master Secret Server as a cluster resource. Because the Master Secret Server is not a resource-intensive component of a BizTalk Server environment, it is recommended that the Master Secret Server be clustered on the same cluster nodes as the SQL Server instances. For more information about configuring the Enterprise Single Sign-On Master Secret Server as a cluster resource, see How to Cluster the Master Secret Server (http://go.microsoft.com/fwlink/p/?LinkId=189511).

Configuring a BizTalk host as a cluster resource – Running multiple instances of a BizTalk Server host provides high availability/fault tolerance. As a result, configuring a BizTalk host as a cluster resource is not recommended except in particular circumstances. For example, you can confgure a BizTalk host as a cluster resource when accommodating high availability/fault tolerance or for providing ordered delivery for certain BizTalk Server adapters. For more information about when it is appropriate to configure a BizTalk host as a cluster resource, see Considerations for Running Adapter Handlers within a Clustered Host (http://msdn.microsoft.com/library/aa561801(v=bts.80).aspx). For more information about how to configure a BizTalk host as a cluster resource see How to Configure a BizTalk Host as a Cluster Resource (http://go.microsoft.com/fwlink/p/?LinkId=189512).

Clustering Message Queuing – For information about how to cluster Message Queuing, see How to Cluster Message Queuing (http://go.microsoft.com/fwlink/p/?LinkId=189516).

Clustering the File System – For information about how to cluster the File System, see How to Cluster the File System (http://go.microsoft.com/fwlink/p/?LinkId=189517).

Using SCOM to Monitor BizTalk ServerThe BizTalk Server Management Pack for Operations Manager provides comprehensive discovery and monitoring of BizTalk Server components and applications that are running in multiple machines. For more information about the BizTalk Server Management Pack, see http://www.microsoft.com/download/details.aspx?id=39617.

See AlsoTroubleshooting Problems with MSDTC

Improving Fault Tolerance in BizTalk Server by Using a Windows Server Cluster

24