Installing and Configuring BizTalk Server 2006 R2 On Windows Server 2003

Installing and Configuring BizTalk Server
2006 R2 on Windows Server 2003

Microsoft Corporation
Published: June 2008
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, Excel,
SharePoint, Visio, Visual C#, and Visual Studio 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
Installing and Configuring BizTalk Server 2006 R2 on Windows Server 2003................................7
What's New and Changed in This Document..............................................................................7
Known Issues in the Installation of BizTalk Server 2006 R2 on Windows Server 2003...............8
BizTalk Server 2006 R2 Installation Guide Contains Incorrect Links to Redistributable CAB
Files................................................................................................................................... 8
BizTalk Server Installation Creates SQL Server Objects on the Primary Filegroup...............8
"Error when downloading BtsRedist.cab" when Downloading Simplified Chinese (CN)
CAB File............................................................................................................................ 9
Setup Fails When Attempting to Install SQLXML 3.0 SP3....................................................9
About the Installation Process..................................................................................................... 9
Overview.................................................................................................................................. 9
Hardware Requirements......................................................................................................... 11
Software Requirements.......................................................................................................... 13
BizTalk Server 2006 R2 Features and Components..............................................................17
BizTalk Server 2006 R2 Feature Dependency Matrix.........................................................20
Deploying BizTalk Server 2006 R2 on Windows Server 2003...................................................21
Considerations for 64-Bit Windows Server 2003 Editions...................................................21
Windows Groups and Accounts.......................................................................................... 22
Localized Versions and Cross-Language Support..............................................................22
Using SQL Server with BizTalk Server 2006 R2.....................................................................22
Supported SQL Server Topologies for Windows Server 2003 Editions............................23
Using SQL Server Named Instances...............................................................................23
Supported SQL Server Collations....................................................................................23
List of Databases Used in BizTalk Server 2006...............................................................23
Considerations for Installing Windows SharePoint Services...............................................24
Considerations for Installing Commerce Server 2007 on the Same Computer...................25
Considerations for Installing BizTalk Server on Domain Controllers...................................26
Performing an Administration Tools-Only Installation.............................................................26
Performing a Complete Installation............................................................................................27
Task 1: Install the Operating System......................................................................................27
Step 1: Install Windows Server 2003..................................................................................27
Step 2: Install Windows Server 2003 Service Pack 2.........................................................28
Step 3: Apply Windows Server 2003 Updates....................................................................28
Task 2: Install Software Prerequisites....................................................................................29
Step 1: Install Internet Information Services 6.0.................................................................29
Step 2: Install Office Excel and Office InfoPath...................................................................30
Step 3: Install Visual Studio 2005.......................................................................................31
Step 4: Install SQL Server 2005 or SQL Server 2000.........................................................32
Step 5: Install Windows SharePoint Services.....................................................................35
Configure ASP.NET 2.0 to Run In 64-Bit Mode On 64-Bit Windows Editions..................35

Install Windows SharePoint Services 3.0........................................................................35
Configure ASP.NET 2.0 to Run In 32-Bit Mode On 64-Bit Windows Editions..................37
Install Windows SharePoint Services 2.0 with Service Pack 2........................................37
Task 3: Configure the Platform...............................................................................................38
Step 1: Configure Default Web Site for ASP.NET 2.0.........................................................38
Step 2: Configure Windows SharePoint Services 2.0.........................................................38
Step 3: Extend Default Web Site as a Virtual Server..........................................................40
Step 4: Disable SQL Server Shared Memory Protocol.......................................................41
Task 4: Install BizTalk Server 2006.........................................................................................41
Step 1: Install BizTalk Server 2006.....................................................................................42
Task 5: Configure BizTalk Server 2006..................................................................................43
Step 1: Configure BizTalk Server 2006...............................................................................44
Step 2: (Optional) Install Orchestration Designer for Business Analysts (ODBA)...............45
Post-Installation Requirements.................................................................................................. 45
Performing a Silent Installation.................................................................................................. 46
Performing a Silent Installation of BizTalk Server 2006..........................................................46
Uninstalling BizTalk Server 2006...............................................................................................48
Task 1: Uninstalling BizTalk Server 2006 Runtime Components and Databases...................48
Step 1: Uninstall BizTalk Server 2006 R2 Runtime Components........................................49
Step 2: Remove BAM Alerts Notification Services Instance................................................50
Step 3: Remove BizTalk Server 2006 R2 SQL Server Agent Jobs......................................51
Step 4: Remove BizTalk Server 2006 R2 SSIS or DTS Packages......................................52
Step 5: Remove BizTalk Server 2006 R2 SQL Server Databases......................................53
Step 6: Remove BizTalk Server 2006 R2 SQL Server Analysis Services Databases.........54
Technical Appendices................................................................................................................ 54
Appendix I: Windows Groups and Service Accounts..............................................................54
Windows Groups Used In BizTalk Server...........................................................................55
User and Service Accounts Used In BizTalk Server............................................................60
Appendix II: Databases Used by BizTalk Server....................................................................63
List of SQL Server Analysis Services Databases............................................................66
List of Windows SharePoint Services Databases............................................................67
Appendix III: How to Install SQL Server 2000........................................................................67
Step 1: Install SQL Server 2000.......................................................................................... 67
Step 2: Install SQL Server 2000 Analysis Services.............................................................68
Step 3: Install SQL Server 2000 Service Pack 4.................................................................69
Step 4: Install SQL Server 2000 Analysis Services Service Pack 4....................................70
Step 5: Install SQL Server Notification Services 2.0 with Service Pack 1...........................71
Appendix IV: Localization Version and Cross-Language Support..........................................72
Localization Version............................................................................................................ 72
Cross-Language Support.................................................................................................... 72
Appendix V: Redistributable CAB Files..................................................................................73
CAB Files for Windows Server 2003 (32-Bit Editions)........................................................74
CAB Files for Windows Server 2003 (64-Bit Editions)........................................................74
Copyright................................................................................................................................... 75
Installing and Configuring BizTalk Server

2006 R2 on Windows Server 2003
This document provides detailed instructions for installing and configuring Microsoft BizTalk
Server 2006 R2 on a single computer running the Windows Server 2003 operating system,
including the 64-bit editions of Windows Server 2003.
A single server installation requires that Microsoft SQL Server be installed on the same
computer as BizTalk Server 2006 R2. Although this document assumes you are performing a
single-server installation, it contains many topics that are relevant to BizTalk Server installations
in a multicomputer configuration.
A multicomputer configuration is one in which BizTalk Server and SQL Server are installed on
different computers. Multicomputer configurations can provide significant performance and
reliability benefits over single server installations.
There are relatively few differences between installing BizTalk Server on 32-bit editions of
Windows compared to installation on 64-bit editions of Windows. This document covers both 32bit and 64-bit installations. Differences between them are noted in the instructions to follow.
This document and the other installation and upgrade guides are updated when new information
regarding BizTalk Server installation becomes available. The latest version of this document is
available for download at http://go.microsoft.com/fwlink/?LinkId=81041.
For more information about installing and configuring BizTalk Server in a multicomputer
configuration, see the multicomputer installation guide at http://go.microsoft.com/fwlink/?
linkid=83322.
What's New and Changed in This Document

This section contains a list of significant changes to this document.
1. This document was reorganized by moving certain reference material to the Appendices:
a. Appendix I: Windows Groups and Service Accounts
b. Appendix II: Databases Used by BizTalk Server
c.
Appendix III: How To Install SQL Server 2000
d. Appendix IV: Localization Version and Cross-Language Support

e. Appendix V: Redistributable CAB Files
2. Added a note to Hardware Requirements, to recommend that Hyper-Threading Technology
be disabled.
3. Added a procedure describing how to perform an Administration Tools-Only Installation.
4. Deleted references to a BizTalk Server readme.txt. There is no readme file included with
BizTalk Server 2006 R2.
5. Revised the Windows SharePoint Services 2.0 configuration procedure.

6. Changed the MQSeries Agent note for the BizTalk Server 2006 R2 Feature Dependency
Matrix, to indicate a dependency on the .NET Framework 2.0 that is not enforced during
BizTalk Server setup.
7. Revised and added new material to Considerations for Installing Windows SharePoint
Services.
Known Issues in the Installation of BizTalk

Server 2006 R2 on Windows Server 2003
This section lists known issues in the installation and configuration of BizTalk Server 2006 R2 on
Windows Server 2003, the symptoms of these issues, and their possible causes and resolutions.
BizTalk Server 2006 R2 Installation Guide Contains Incorrect Links to

Redistributable CAB Files
Problem
The Installation_Guide.htm and Setup Wizard Downloadable Prerequisites Help page list
incorrect links to download the redistributable CAB files. This problem affects only the
documentation on the product setup disc. Online documentation (such as this guide) is not
affected.
Cause
The links in the affected documentation actually refer to the redistributable CAB files for BizTalk
Server 2006. These CAB files are not suitable for use with BizTalk Server 2006 R2.
Resolution
For more information about the problem and a list of the correct download locations, see the
Knowledge Base article at http://support.microsoft.com/kb/942181, or the Redistributable CAB
Files topic in this document.
BizTalk Server Installation Creates SQL Server Objects on the Primary

Filegroup
Problem
Setup does not recognize SQL Server default filegroups. All database objects are created on the
primary filegroup.
Cause
The Transact-SQL statements used to create BizTalk Server database objects are scripted with
the ON PRIMARY keywords.
Resolution
If you want to move BizTalk Server objects from the primary filegroup to an alternate filegroup,
you must do so manually. There is no other workaround available at this time.
"Error when downloading BtsRedist.cab" when Downloading Simplified

Chinese (CN) CAB File
Problem
If a redistributable component is missing from the computer during setup of the Simplified
Chinese version of BizTalk Server 2006 R2 and you attempt to install the component by selecting
"Automatically Download CAB File from the Web," setup may fail with the following error
message:
"Error when downloading BtsRedist.cab. Cause: The user has not logged on the network, cannot
carry out the operation requested. Service does not exist." Setup will not continue past this error.
Cause
This error is caused by the Background Intelligent Transfer Service (BITS).
Resolution
1. Stop the BITS service.
2. Restart the BITS service.
3. Rerun BizTalk Server setup.
Setup Fails When Attempting to Install SQLXML 3.0 SP3

Problem
BizTalk Server 2006 R2 installation or upgrade may fail when setup attempts to install
SQLXML 3.0 SP3. SQLXML provides XML support for SQL Server databases.
Cause
SQLXML 3.0 SP2 is installed on the computer where you are trying to install BizTalk Server 2006
R2.
Resolution
You must manually uninstall SQLXML 3.0 SP3 before running setup for BizTalk Server 2006 R2.
About the Installation Process

This section provides an overview of the BizTalk Server 2006 R2 installation process and the
features and components that are available to install.
Overview
The basic installation process for BizTalk Server 2006 R2 is the same as for most Windowsbased applications. The BizTalk Server Setup program calls Windows Installer to install BizTalk
Server 2006 R2 and the related components. Setup coordinates the installation process from
beginning to end, terminating when the last component is installed. If you do not have a
component, Setup is able to install prerequisites from the Web or from a previously downloaded
CAB file.
The following table provides a brief overview of the steps needed to install BizTalk Server,
assuming that you are beginning with a new computer that does not have an operating system
installed.
Step/Task
Notes
Step 1: Install Windows Server 2003 with

Service Pack 1 or Service Pack 2.
After installing Windows, you must be

logged on as an administrator to complete
the full installation process for BizTalk
Server.
Step 2: Install critical updates for Windows.
Install any high priority updates listed at the

Windows Update Web site.
Step 3: Install Internet Information

Services (IIS) 6.0.
Enable ASP.NET 2.0.
Enable ASP.NET 32-bit mode on 64-bit

Windows editions.
Step 4: Install Microsoft Office Excel 2003
and Microsoft Office InfoPath 2003 with Office

Service Pack 2, or Microsoft Office Excel 2007
and Microsoft Office InfoPath 2007.
Install using default settings.

Office Excel should be installed before SQL
Server 2005.
Step 5: Install Visual Studio 2005.
Install Microsoft C# and the .NET

Framework SDK.
Step 6: Install SQL Server 2005 with Service

Pack 2.
Install using default settings.
Step 7: Install and configure Microsoft

Windows SharePoint Services 2.0 with
Service Pack 2 (SP2), Microsoft Windows
SharePoint Services 3.0, or Microsoft Office
SharePoint Server 2007.
Installation type must be Server Farm; this

allows you to specify the configuration
database.
Windows SharePoint Services must be

installed on the BizTalk Server to support
the Windows SharePoint Services adapter
Web service.
Windows SharePoint Services 3.0 and

SharePoint Server 2007 are not supported
for use with Business Activity Services
(BAS).
Side-by-side installation of both Windows

SharePoint Services 2.0 SP2 and Windows
SharePoint Services 3.0 is supported. In
this scenario, the Windows SharePoint
Services adapter supports the use of either
Windows SharePoint Services 2.0 SP2 or
Windows SharePoint Services 3.0 at a
10
Step/Task
Notes
given time.
For more information about the versions of

Windows SharePoint Services that are
supported for use with BizTalk Server 2006
R2 see the BizTalk Server online Help topic
"Windows SharePoint Services Support in
BizTalk Server 2006 R2" at
http://go.microsoft.com/fwlink/?
linkid=102615.
Step 8: Extend default Web site as a virtual

server.
Select NTLM for the security type. Kerberos

authentication is not supported with
Business Activity Services.
Step 9: Create a network share for Business

Activity Monitoring (BAM) alerts.
Create a share named Alerts.
Give Everyone Change permissions to this

share.
For information about installing BizTalk RFID, see Installing and Configuring BizTalk RFID at
http://go.microsoft.com/fwlink/?linkid=81041.
For the download locations of the CAB files, see Redistributable Cab Files.
Hardware Requirements
The following table shows the minimum hardware requirements for a BizTalk Server 2006 R2
installation. Achieving acceptable performance in a production environment will generally dictate
greater hardware requirements for your servers. The minimum computer configuration is suitable
for development and testing purposes.
Component
Minimum Requirement
Computer and processor
A computer with an Intel Pentium-compatible

CPU that is:
1 GHz or higher for single processors
900 MHz or higher for double processors
700 MHz or higher for quad processors
Hyper-Threading Technology (HT Technology)

and multiple-core processors are supported.
Note
BizTalk Server licensing is per socket.
Thus a dual-core processor that uses
11
Component
Minimum Requirement
only one socket is considered one

processor for licensing purposes.
Important
We recommend that you disable HT
Technology if it is present in hardware
by using the system BIOS configuration
utility. This is because a system with HT
Technology enabled appears to
applications as two logical processors,
as do dual-core processors. BizTalk
Server performs internal optimizations
to take advantage of multiple
processing cores. Unlike dual-core
processors, which have two distinct
processing cores, processors that
support HT Technology have only one
processing core. The BizTalk Server
performance enhancing strategies that
work well with multiple cores often
perform poorly when run on a CPU with
HT Technology enabled.
The 64-bit versions of BizTalk Server require a
64-bit operating system running on an x64based system. Computers based on CPUs that
are compatible with the AMD64 (x86-64) and
Extended Memory 64-bit Technology (EM64T)
processor architecture are considered x64based systems. For more information about 64bit support, see Considerations for 64-Bit
Windows Systems.
BizTalk Server is not supported on Itaniumbased systems.
Memory
1 GB of RAM; 2 GB or more recommended.
Hard disk
10 GB of available hard disk space for a

complete installation including the operating
system and all prerequisite software. Increase
this to 15 GB for localized versions of BizTalk
Server with language packs installed.
The maximum sustainable throughput of a
BizTalk Server system is often limited by hard
12
Component
Minimum Requirement
disk performance rather than CPU

performance. Improved storage system
performance usually, but not always, leads to
improved BizTalk Server application
performance. The degree to which performance
improves is determined by the kinds of activities
the application performs.
Drive
CD-ROM or DVD-ROM drive
Display
Windows Server 2003-compatible VGA or

higher-resolution monitor set to 1024 x 768
pixels or greater resolution
Other
Network adapter card, and Microsoft mouse or

compatible pointing device
Software Requirements
BizTalk Server relies on a broad base of prerequisite software to provide the services necessary
for a BizTalk Server application to function. The following table is a complete list of the
prerequisite software you may be required install on the server that will run BizTalk Server 2006
R2. Not all of these prerequisites will be required for every installation. Exactly what software
must be installed depends on which BizTalk Server features you decide to implement. For more
information, see the BizTalk Server 2006 R2 Feature Dependency Matrix.
Product
Description
Windows Server 2003 Datacenter Edition,

Enterprise Edition, or Standard Edition,
including 64-bit editions, with Service Pack 1 or
Service Pack 2
Operating system. BizTalk Server supports 64bit Windows on x64-based systems; Itaniumbased systems are not supported.
Windows Server 2003 R2 Datacenter Edition,

Enterprise Edition, or Standard Edition,
including 64-bit editions
Microsoft Small Business Server 2003 with
Service Pack 1, or Microsoft Small Business
Server 2003 R2
Note
Windows Server 2003 Web Edition is
not supported.
Internet Information Services (IIS) 6.0
BizTalk Server requires IIS for the following

13
Product
Description
features:
SQL Server 2005 with Service Pack 2, or SQL

Server 2000 with Service Pack 4
HTTP adapter
SOAP adapter
Windows SharePoint Services adapter
Secure Sockets Layer (SSL) encryption
Business Activity Services (BAS)
Human Workflow Services (HWS)
BizTalk Server supports all Microsoft SQL

Server editions except SQL Server Express
Edition. Support for failover clustering requires
SQL Server Standard Edition or Enterprise
Edition. For optimal performance, we
recommend that you use Enterprise Edition of
SQL Server 2005.
Using SQL Server Express Edition in a
production environment is not recommended.
The Express edition does not include the SQL
Agent Job Scheduling Service, which is
essential for the proper operation of BizTalk
Server.
Microsoft SQL Server 2000 Analysis Services

with Service Pack 4
SQL Server 2000 Analysis Services is the next

generation of the OLAP Services component
that was released in SQL Server 7.0. This is
used by the BAM Client.
SQLXML 3.0 with Service Pack 3
SQLXML enables XML support for your SQL

Server database.
Note
There is a known issue that sometimes
occurs during the installation of
SQLXML 3.0. For more information, see
Setup Fails When Attempting to Install
SQLXML 3.0 SP3.
SQL Server Notification Services 2.0 with

Service Pack 1
Microsoft SQL Server 2000 Notification Services

is required if you plan to configure BAM Alerts.
Windows SharePoint Services 2.0 with Service

Pack 2
Windows SharePoint Services is a collection of

services for Windows Server 2003 that you can
use to share information, collaborate with other
users on documents, and create lists and Web
14
Product
Description
part pages. This is required if you plan to

configure Business Activity Services (BAS).
Windows SharePoint Services 3.0 or Office
SharePoint Server 2007
Windows SharePoint Services 3.0 Service Pack

1 (SP1) is supported.
Installation of Microsoft Office SharePoint
Server 2007 (MOSS) is supported. For more
information see the topic "Windows SharePoint
Services Support in BizTalk Server 2006 R2" in
the BizTalk Server 2006 R2 online help at
Note
Business Activity Services (BAS) is not
supported for use with Windows
SharePoint Services 3.0 or Office
SharePoint Server 2007.
Microsoft Office Excel 2003 with Office 2003

Service Pack 2, or Microsoft Office Excel 2007
Business Activity Monitoring (BAM) uses an

Excel workbook to provide business users with
a way to see a real-time view of business
processes.
Microsoft Office InfoPath 2003 with Office 2003

Service Pack 2, or Microsoft Office
InfoPath 2007
Microsoft Office InfoPath is optional for a

BizTalk Server 2006 R2 installation. It is
required only if you plan to configure Business
Activity Services (BAS).
Microsoft .NET Framework 1.1
The .NET Framework version 1.1 is required for

the Business Activity Monitoring (BAM) Tools.
This is required when you plan to configure
BAM alerts with SQL Server 2000 with Service
Pack 4 and SQL Server Notification
Services 2.0 with Service Pack 1.
The .NET Framework version 2.0 is required for

the BizTalk Server 2006 R2 runtime.
The .NET Framework 3.0 (formerly WinFX) is

required for the WCF adapter, WCF interceptor,
and WCF Administration Tools.
Microsoft Visual Studio 2005
Microsoft Visual Studio 2005 is required for the

BizTalk Server Developer Tools and SDK
component. Visual Studio is not required on
production computers; however it is often
15
Product
Description
installed to permit debugging a BizTalk Server

application in a production setting. Visual
Studio 2005 Service Pack 1 (SP1) is supported.
Note
The Developer Tools and SDK
component cannot be installed on
Visual Studio 2005 Express Editions.
Microsoft Data Access Components
(MDAC) 2.8 Service Pack 1 (SP1)
Microsoft Data Access Components

(MDAC) 2.8 SP1 contains core Data Access
components such as the Microsoft SQL Server
OLE DB provider and ODBC driver.
By default, MDAC 2.8 is installed on Windows
Server 2003.
Microsoft XML Core Services (MSXML) 3.0

Service Pack 7 (SP7)
XML Core Services (formerly known as MSXML,

for Microsoft Extensible Markup Language or
XML) is required for your BizTalk Server
installation.
Microsoft XML Core Services (MSXML) 6.0
MSXML 6.0 has improved reliability, security,

conformance with the XML 1.0 and XML
Schema 1.0 W3C Recommendations, and
compatibility with System.Xml 2.0.
Microsoft Office 2003 Web Components
Office Web Components is required only if you

want to use Health and Activity Tracking (HAT),
Administration Tools, or BAM portal
components.
ADOMD.NET 8.0
ADOMD.NET 8.0 is a .NET object model, used

for building client applications that access and
XML for Analysis 1.1-compliant data provider,
such as that provided by the XML for
Analysis 1.1 SDK. ADOMD.NET is required by
the BizTalk Server runtime.
ADOMD.NET 9.0
ADOMD.NET 9.0 is able to support all of the

capabilities found in SQL Server 2005 Analysis
Services. For more information, see
http://go.microsoft.com/fwlink/?LinkID=93877,
"ADOMD.NET Release Differences" in SQL
Server 2005 Books Online.
16
BizTalk Server 2006 R2 Features and Components

The following table describes the available BizTalk Server 2006 R2 features and components that
can be installed. This list is given in approximately the same order that the features appear in the
feature selection tree in setup. During setup, some features may not be available for installation,
depending on the availability of certain prerequisites on your computer. In many cases the
needed prerequisite is available for download from the Web or extraction from a CAB file.
Component
Description
Documentation
Selecting the Documentation component installs the core

documentation, tutorials, UI reference (F1 Help),
programmers reference, and usage instructions for the
SDK samples and utilities.
Server Runtime
Selecting the Server Runtime component installs the

runtime services for BizTalk Server 2006 R2. These
runtime services are an essential part of the BizTalk
Server platform.
Base EDI Adapter
Selecting the Base EDI Adapter component installs the

necessary software that enables BizTalk Server 2006 R2
to process documents in the Electronic Data Interchange
(EDI) format.
This option is disabled during setup unless the setup
computer will be upgraded from a previous version of
BizTalk Server to BizTalk Server 2006 R2 and the Base
EDI adapter is already installed on the computer.
The Base EDI adapter is 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.
Important
If the Base EDI adapter is removed from the
computer (uninstalled), it cannot be reinstalled
using the BizTalk Server 2006 R2 setup
program.
BizTalk EDI/AS2 Runtime
Selecting the BizTalk EDI/AS2 Runtime component

installs the BizTalk EDI/AS2 Runtime. These runtime
services provide native support for Electronic Data
Interchange (EDI) data exchange and AS2 (Applicability
Statement 2) data transport messaging functionality.
Windows Communication
Framework (WCF) Adapter Runtime
The BizTalk Server Windows Communication Foundation

(WCF) adapters allow Microsoft BizTalk Server 2006 R2
17
Component
Description
to communicate with WCF-based applications.

Portal Components
The Portal Components are a set of services used by

business people to communicate, collaborate, and reach
decisions enabling them to interact, configure, and
monitor business processes and workflows. The
components consist of the following:
Business Activity Monitoring (BAM)
Human Workflow Web Service (HWS)
BAS and HWS are deprecated in BizTalk Server 2006

R2. These features will be removed from future versions
of BizTalk Server.
Administrative Tools
Selecting the Administration Tools component installs the

necessary software to administer BizTalk Server 2006
R2 on both the local computer and a remote server.
BizTalk Server supports an Administration Tools only
installation.
WCF Administration Tools
Provides administration services for WCF components.
Developer Tools and SDK
Selecting the Developer Tools and SDK component

installs samples and utilities that enable the rapid
creation of BizTalk Server 2006 R2 solutions. This
includes: SDK samples and supporting documentation,
BizTalk Explorer, schema and map designers, and Visual
Studio project templates. This component requires Visual
Studio 2005.
Note
The Developer Tools and SDK component
cannot be installed on Visual Studio 2005
Express Editions.
Additional Software
Additional Software is a set of components that enable

deployment flexibility in BizTalk Server 2006 R2. This
includes the following:
Enterprise Single Sign-On (SSO) Administration

Module
Note
This feature requires Microsoft Management
Console 3.0 available at
18
Component
Description
http://go.microsoft.com/fwlink/?LinkId=67694
(32-bit) or http://go.microsoft.com/fwlink/?
linkid=88352 (64-bit), "Microsoft
Management Console 3.0 for Windows
Server 2003."
Enterprise Single Sign-On Master Secret Server.

Enterprise Single Sign-On Master Secret Server is
required in a BizTalk Server environment, including
single server installations.
Business Rules Components
MQSeries Agent. This feature requires IBM

WebSphere MQ 5.3 with CSD 10 or later or IBM
WebSphere MQ 6.0 to be installed on the computer.
You must run the MQSAgent COM+ Configuration
Wizard on the computer where MQSAgent is
installed prior to using the MQSeries Adapter, or
Windows SharePoint Services Web service
Important
Before installing this feature you must
install .NET Framework 2.0, although this
prerequisite is not enforced by the BizTalk
Server 2006 R2 setup program.
Business Activity Monitoring (BAM) Alert Provider for

SQL Server Notification Services
BAM Client
BAM Event API
BizTalk Server 2006 R2 Feature Dependency Matrix

The following table indicates the dependencies that you must install or update before installing
BizTalk Server 2006 R2 based on the features you select.
19
Note
.NET Framework 1.1 is required when you install SQL Server Notification Services 2.0
with Service Pack 1 and for Windows SharePoint Services 2.0 with Service Pack 2.
Note
.NET Framework 3.0 is required only if you install the WCF adapter or WCF Admin Tools,
or if you install Windows SharePoint Services 3.0.
Note
You only need to install IBM WebSphere MQ 5.3 with CSD 10 or IBM WebSphere MQ 6.0
for MQSeries Agent. If you install the MQSeries Agent you must also install the .NET
20
Framework 2.0, however, this requirement is not enforced by the SQL Server setup
program.
Deploying BizTalk Server 2006 R2 on Windows

Server 2003
This section describes some of the possible single-server deployment scenarios and factors you
should be aware of before installing BizTalk Server 2006 R2 on Windows Server 2003. The
discussion that follows assumes the entire BizTalk Server system is installed on one server.
Single-server installations are useful when hardware or licensing limits prevent use of a multiple
server topology. A single-server installation is well suited to low transaction volume applications
and applications that can tolerate downtime in the event of a serious hardware failure.
Consider the following before implementing a single-server BizTalk Server installation:
High availability cannot be assured; fault tolerance is limited to data protection and disaster
recovery. For more information about disaster recovery and backup procedures for BizTalk
Server, see "Backing Up and Restoring BizTalk Server" at http://go.microsoft.com/fwlink/?
linkid=105772.
Security is complicated by the concentration of services and data on one computer. For more
information about security in BizTalk Server, see "Planning for Security" at
The system may be difficult to scale. For more information about scaling BizTalk Server
solutions, see "Scaling Your Solutions" at http://go.microsoft.com/fwlink/?linkid=110437.
Considerations for 64-Bit Windows Server 2003 Editions

The following considerations apply to installing BizTalk Server 2006 R2 on 64-bit editions of
Windows Server 2003.
Running host instances in native 64-bit mode is only supported on BizTalk Server 2006 R2
Enterprise Edition, Developer Edition, Branch Edition, and Evaluation Edition.
BizTalk Server cannot be run on Itanium-based Windows editions; however, BizTalk Server
can make use of SQL Server databases hosted on an Itanium-based system.
There is no unique installation application for the 64-bit platform. During installation the Setup
Wizard (setup.exe) will determine which platform (32-bit or 64-bit) it is running on, and then
install the appropriate version of the BizTalk Server executables. The Setup Wizard itself is a
32-bit application.
There are separate setup programs for 32-bit and 64-bit Enterprise Single Sign-On (SSO).
The Setup Wizard will automatically invoke the correct SSO installation package; however, if
it becomes necessary to install SSO directly from its installation package you must be sure to
choose the correct setup version. The SSO subfolder contains the 32-bit installation package.
The SSO64 folder contains the 64-bit installation package.
The Configuration Wizard (configuration.exe) is a 32-bit application only. There is no 64-bit

version of configuration.exe.
21
If you have installed BizTalk Server 2006 R2 on the 64-bit edition of SQL Server 2005, the
default server name will not be populated in the custom configuration manager unless the
SQL Server Browser service is started before running configuration. For more information,
see "SQL Server Browser Service" in SQL Server 2005 Books Online at
You can configure host instances to run in either 32-bit or 64-bit mode by using the 32-bitonly check box option in the Host Properties dialog box in the BizTalk Server Administration
console. By default, host instances are created to run in 32-bit mode.
Business Activity Services (BAS) requires the 32-bit editions of Microsoft Internet Explorer 6
or Windows Internet Explorer 7.
If you are installing the BAM portal, you must configure ASP.NET 2.0 to run in 32-bit mode.
For more information about running BizTalk Server on 64-bit Windows Server 2003 editions, see
"BizTalk Server 64-Bit Support" in the Performance and Capacity Planning section of BizTalk
Server 2006 R2 Help.
Windows Groups and Accounts

For a complete list of the Windows groups and accounts used by BizTalk Server, see Appendix I:
Windows Groups and Service Accounts. The Setup Wizard will create these groups and most
accounts for you during a single-server installation, and then the wizard will configure BizTalk
Server to use these accounts. We recommend that, if possible, you retain the group and account
names created by the Setup Wizard.
Important
During a multiserver installation you must manually create the Windows groups and
accounts for BizTalk Server. The multiple-server installation guide discusses this topic.
For more information about installing and configuring BizTalk Server in a multiple-server
configuration, see the multiple-server installation guide at http://go.microsoft.com/fwlink/?
linkid=83322.
Localized Versions and Cross-Language Support

For information about the localized versions of BizTalk Server and operating system compatibility,
see Appendix IV: Localization Versions and Cross-Language Support.
Using SQL Server with BizTalk Server 2006 R2

SQL Server is an essential part of a BizTalk Server installation. This section contains information
you need to consider before installing SQL Server for use with BizTalk Server.
BizTalk Server system performance is often directly proportional to SQL Server performance.
Realizing the maximum potential from the SQL Server requires planning to decide where BizTalk
Server databases are located. For best performance, we recommend placing the MessageBox
database onto a device separate from all other BizTalk Server databases. For more information,
see Guidelines for Avoiding Bottlenecks at http://go.microsoft.com/fwlink/?linkid=117739.
22
Supported SQL Server Topologies for Windows Server 2003 Editions

By definition, all single server installations of BizTalk Server include a local installation of SQL
Server. A local installation of SQL Server is one in which SQL Server and BizTalk Server
(including all of the BizTalk Server databases) are installed on the same computer. A remote
installation of SQL Server is one in which SQL Server runs on a server other than the server
hosting BizTalk Server. Remote installations of SQL Server are inherently multicomputer
configurations. For more information about multicomputer installations of BizTalk Server, see
http://go.microsoft.com/fwlink/?linkid=83322, "Installing and Configuring BizTalk Server 2006 R2
in a Multicomputer Environment."
BizTalk Server supports the following combinations:
32-bit Windows Server 2003 with 32-bit SQL Server 2005 or 32-bit SQL Server 2000
64-bit Windows Server x64 Editions with 32-bit SQL Server 2005 or 32-bit SQL Server 2000
64-bit Windows Server x64 Editions with 64-bit SQL Server 2005 or 64-bit SQL Server 2000
The following are not supported or not recommended:
Itanium-based systems are not supported for single-server installations. BizTalk Server will
not run on Itanium-based systems. (Itanium-based systems can be used in a multiple server
configuration, with SQL Server installed on the Itanium system.)
Local installations of SQL Server 2000 and SQL Server 2005 at the same time are not
supported.
The SQL Server Express editions are not recommended for production use because the SQL
Server Agent Service is not included with the Express editions.
Using SQL Server Named Instances

Installing and configuring BizTalk Server 2006 R2 against SQL Server 2000 and SQL Server 2005
default instances and named instances is supported.
Named instances of SQL Server 2000 Analysis Services are not supported. You must use the
default instance of SQL Server 2000 Analysis Services during the configuration.
Supported SQL Server Collations
BizTalk Server 2006 R2 supports most SQL Server collations; however, binary collations are not
supported.
List of Databases Used in BizTalk Server 2006
For a complete list of the databases used in BizTalk Server, see Appendix II: Databases Used in
BizTalk Server.
Considerations for Installing Windows SharePoint Services

BizTalk Server requires Windows SharePoint Services (WSS) to support the following features:
Business Analysis Services (BAS)
If you do not intend to install any of these features, you do not need to install WSS.
23
BizTalk Server 2006 R2 supports Windows SharePoint Services 2.0 SP2 and Windows
SharePoint Services 3.0, or Windows SharePoint Services 2.0 and Microsoft Office SharePoint
Server 2007 (MOSS). Not all BizTalk Server features are compatible with all versions of Windows
SharePoint Services.
Windows SharePoint Services support in BizTalk Server 2006 R2 is summarized in the following
table:
Windows SharePoint Services
WSS adapter
BAS
32-bit only
32-bit only
32-bit on Windows 32-bit x86

editions
Not supported
version
Windows SharePoint
Services 2.0 SP2
Support for 64-bit systems is
provided by WOW64. IIS and
ASP.NET must run in 32-bit
mode.
Windows SharePoint
Services 3.0 or Microsoft Office
SharePoint Server 2007
WSS 3.0 and MOSS require IIS
and ASP.NET to run in 64-bit
mode on 64-bit Windows
editions.
The WSS adapter is

supported in 32-bit (WOW64)
or native 64-bit modes on 64bit Windows editions.
Before you install Windows SharePoint Services, consider the following:
BizTalk Server 2006 R2 supports side-by-side installation of Windows SharePoint

Services 2.0 SP2 (WSS 2.0) and Windows SharePoint Services 3.0 (WSS 3.0).
If you plan a side-by-side installation of WSS 2.0 and WSS 3.0, we recommend (but dont
require) that you install WSS 3.0 before WSS 2.0. If WSS 3.0 is installed after WSS 2.0, the
WSS 3.0 Setup Wizard automatically attempts to upgrade the existing WSS 2.0 installation.
Installing WSS 3.0 first will avoid this problem, although you can manually choose not to
perform an upgrade when the WSS 3.0 Setup Wizard runs.
The Windows SharePoint Services (both WSS 2.0 and WSS 3.0) installation type must be
Server Farm. This is true even if you are performing a single-server installation of BizTalk
Server 2006 R2. The Server Farm type of installation allows you to configure WSS to use the
databases you specify.
WSS 3.0 requires Microsoft .NET Framework 3.0. The .NET Framework must be installed
prior to installing Windows SharePoint Services 3.0.
On 64-bit Windows, both IIS and ASP.NET must be configured to run in 64-bit mode before
installing WSS 3.0.
24
On 64-bit Windows, both IIS and ASP.NET must be configured to run in 32-bit mode before
installing WSS 2.0.
Although side-by-side installation of WSS 2.0 and WSS 3.0 is supported on 64-bit Windows,
side-by-side execution is not supported. WSS 2.0 requires IIS and ASP.NET to run in 32-bit
mode on 64-bit Windows, however, WSS 3.0 requires IIS and ASP.NET to run in 64-bit mode.
IIS can only run in one mode, 32-bit or 64-bit, at any given time on 64-bit Windows. This
prevents side-by-side execution of WSS 2.0 and WSS 3.0.
In general this is not a serious constraint, but there are exceptions. For example, if you want
to run BAM or BAS in conjunction with the Windows SharePoint Services adapter, you will
have to configure the adapter to use WSS 2.0.
Side-by-side installation and side-by-side execution of WSS 2.0 and WSS 3.0 is supported on
Windows 32-bit x86 editions. This means that it is possible to configure the WSS adapter
Web service to use WSS 3.0, and simultaneously host the BAS Web site using WSS 2.0. This
configuration is only possible on Windows 32-bit x86 editions.
The Windows SharePoint Services adapter supports Windows SharePoint Services 2.0 SP2
(32-bit only), Windows SharePoint Services 3.0 (32-bit on x86 systems; 64-bit on x64
systems with 64-bit Windows installed), or Microsoft Office SharePoint Server 2007. The
WSS adapter can be configured to use only one version of WSS or MOSS at a given time.
Installation of Microsoft Office SharePoint Server 2007 (MOSS) is supported.
BAS does not support WSS 3.0 or MOSS. BAS requires WSS 2.0 SP2.
For more information about the versions of Windows SharePoint Services that are supported for
use with BizTalk Server 2006 R2, see the BizTalk Server online Help topic Windows SharePoint
Services Support in BizTalk Server 2006 R2.
Considerations for Installing Commerce Server 2007 on the Same

Computer
You can install Microsoft Commerce Server 2007 and BizTalk Server 2006 R2 on the same
computer, but you must run the configuration wizard for each product before you install and
configure the next product. For example, install and configure Commerce Server 2007 before you
install and configure BizTalk Server 2006 R2. Alternatively, install and configure BizTalk Server
2006 R2 before you install and configure Commerce Server 2007.
Considerations for Installing BizTalk Server on Domain Controllers

You can install BizTalk Server 2006 R2 on the Active Directory domain controllers; however we do
not recommend you do so unless you are installing BizTalk Server 2006 R2 on Small Business
Server 2003 where typically it is a domain controller.
There is overhead associated with functions performed by the domain controller. This extra CPU
and network activity may have a detrimental effect on BizTalk Server performance.
25
Performing an Administration Tools-Only Installation

It is sometimes desirable to administer a BizTalk Server from a remote computer. To do this you
can install only the BizTalk Server Administration Tools, without installing the other BizTalk Server
components.
During an Administration Tools-only installation, the Administration console, BM.exe,
BTSDeploy.exe, HWS Server Administration console, and Health and Activity Tracking (HAT) tool
are installed.
Note
An administration tools only setup does not require a BizTalk Server license. You do still
need a license for products required to use Administrative Tools; for example, SQL Server
and Windows.
Note the following before you perform an Administration Tools-only installation:
SQL Server Agent must be running on all computers that are hosting BizTalk Server
MessageBox databases. This is required if you want to track message bodies in the BizTalk
Server Messaging engine. The SQL Server Agent also runs maintenance jobs that are critical
to the proper function of your BizTalk Server system.
To use HAT, you must have the read permissions to access the SQL Server, Analysis Server,
and the IIS virtual directory. For information about how to use the BizTalk Server
Administration console and HAT, see "Monitoring BizTalk Server" at
When you run the BizTalk Server Configuration Wizard, you must create an Analysis Server
database.
To create an Administration Tools-only installation
1. During the installation of BizTalk Server, select Administration Tools in the component
selection screen without selecting any other components and complete the Installation
Wizard.
2. After the installation is complete, launch the custom configuration manager and join an
existing SSO system and BizTalk Group.
Performing a Complete Installation

The following tasks guide you through installing and configuring a complete installation of BizTalk
Server 2006 R2 on Windows Server 2003 with Service Pack 2. Installation begins by installing the
operating system and ends when initial configuration of the BizTalk Server environment is
complete.
You can skip Task 1 if you are an experienced administrator or if you are beginning your BizTalk
Server installation on a computer that has Windows Server 2003 installed. Whether you decide to
skip Task 1 or not, you should consider the following during installation:
Troubleshooting installation and configuration problems is often complicated by other

software currently or previously installed on the computer. To be certain that your system is in
26
a known state, you should start with a fresh installation of Windows Server 2003. Additional
software, if any, should be kept to a minimum.
Ensure that your server has all necessary security and software updates installed by visiting
the Microsoft Update site before installing software prerequisites, and periodically check for
additional updates as installation progresses. In general, you should install all high-priority
updates, and optional updates, as appropriate.
Real-time antivirus scanning software should be disabled during BizTalk Server installation.
Antivirus software may block certain configuration changes that are necessary for the proper
operation of your BizTalk Server.
After installing Windows Server 2003, you must log on as an administrator in order to install
additional software.
Task 1: Install the Operating System

In this task, you install the operating system that will be used as the base platform for BizTalk
Server 2006 R2. The procedure for installing Windows Server 2003 is not described in detail
here, because it is well-documented and supported elsewhere.
For information about installing Windows Server 2003, see the Windows Server 2003
Deployment Guide at http://go.microsoft.com/fwlink/?linkid=111188.
For more information about installing Windows Server 2003 R2, see
Step 1: Install Windows Server 2003

Before you install Windows Server 2003, consider the following:
Installation of BizTalk Server 2006 R2 into a domain is only supported on an Active Directory
domain environment that is running in Windows 2000 native mode or later. You cannot install
into a mixed-mode domain (i.e., one that supports NT 4.0 clients).
After installing Windows, you must be logged on as an administrator, or add a Windows user
account to the Administrators group in order to install additional software.
Windows Firewall is on by default only during new installations of Windows Server 2003.
Windows Firewall provides network protection while users update their system with the latest
updates using the new Post-Setup Security Updates feature. As soon as the updates are
finished, the firewall is turned off unless it was explicitly enabled. If a server running Windows
Server 2003 is updated or upgraded to Service Pack 1 or Service Pack 2 the firewall is off by
default and the Post Setup Security Updates feature is not used. For more information about
using Windows Firewall with Windows Server 2003, see "Windows Server 2003 Windows
Firewall (WF)" at http://go.microsoft.com/fwlink/?linkid=67902.
Step 2: Install Windows Server 2003 Service Pack 2

As a minimum, Windows Server 2003 Service Pack 1 is required by BizTalk Server 2006 R2. You
do not need to perform this step if you have installed a copy of Windows Server 2003 that
27
includes Service Pack 1, or if you are using Windows Server 2003 R2. Even so, we recommend
that you install Service Pack 2 to obtain the latest software updates and security improvements.
To learn more about Windows Server 2003 Service Pack 2, see "Windows Server 2003 Service
Pack 2 Technical Library" http://go.microsoft.com/fwlink/?LinkId=86804.
The Windows Server 2003 Service Pack 2 and installation procedure is available for download at
the following locations:
32-bit Windows Server 2003 editions: http://go.microsoft.com/fwlink/?LinkId=86805
64-bit Windows Server 2003 editions: http://go.microsoft.com/fwlink/?linkid=88372
Windows Server 2003 Service Pack 2 can also be obtained from Microsoft Update.
Step 3: Apply Windows Server 2003 Updates

In the following procedure you apply the latest Windows Server 2003 updates to your server. This
procedure should be followed for all versions of Windows Server 2003. You will probably find that
there are a considerable number of high priority and optional updates available for your system.
You will need to monitor the installation process because some of the updates do require user
input to complete installation.
You will need to update Windows again as the BizTalk Server installation procedure progresses.
This is to ensure that all software prerequisites are updated.
To apply Windows Updates
1. Click Start, point to All Programs, and then click Windows Update.
2. On the Microsoft Windows Update home page, click Express. Windows Update looks
for available updates.
Tip
Choose Custom if you want to review the list of updates before they are applied.
This also allows you to review and select optional updates for installation.
3. Install any high-priority updates listed.
Note
You may be required to restart your computer several times.
Task 2: Install Software Prerequisites

In this task, you install all of the software prerequisites needed for your type of installation of
BizTalk Server 2006 R2. A complete BizTalk Server installation requires all of the software in the
following list, however, most of the prerequisites are required only for specific BizTalk Server
features. The actual list of prerequisites depends on which BizTalk Server features you install.
Consult the BizTalk Server 2006 R2 Feature Dependency Matrix to determine which prerequisites
you need to install.
Internet Information Services 6.0
28
Microsoft Office Excel 2007 and Office InfoPath 2007, or Office Excel 2003 and
InfoPath 2003 with Office 2003 Service Pack 2. Office Excel is required for BAM. Office
InfoPath is required for BAS.
Visual Studio 2005
SQL Server 2005 with Service Pack 2 or SQL Server 2000 with Service Pack 4 (SQL
Server 2005 is recommended)
If SQL Server 2000 is installed, then the following services are necessary
SQL Server 2000 Analysis Services with Service Pack 4
SQL Server Notification Services 2.0 with Service Pack 1
Windows SharePoint Services 2.0 with Service Pack 2
Step 1: Install Internet Information Services 6.0

In the following procedure you install Internet Information Services 6.0.
Microsoft Internet Information Services (IIS) provides a Web application infrastructure for many
BizTalk Server features. BizTalk Server requires IIS for the following features:
HTTP adapter
SOAP adapter
Secure Sockets Layer (SSL) encryption
Human Workflow Services (HWS)

To install Internet Information Services 6.0
1. Click Start, and then click Manage Your Server.
2. In the Manage Your Server window, click Add or remove a role.
3. In the Configure Your Server Wizard, click Next.
4. Under Server Role, select Application server (IIS), and then click Next.
5. Under Application Server Options, select Enable ASP.NET, and then click Next.
Note
The sequence of screens described here may appear differently if you run the
Configure Your Server wizard again after IIS is initially installed. For example,
the Application Server Options and Summary of Selections screens will not
be displayed.
Note
This step does not apply to 64-bit Windows editions.
6. On Summary of Selections, review the information and then click Next.
29
7. On the Configure Your Server Wizard completion page, click Finish.

Note
The Common Files component in IIS 6.0 is required for publishing BizTalk Web
services. Do not remove this component after installing IIS 6.0.
Step 2: Install Office Excel and Office InfoPath

BizTalk Server 2006 R2 supports the 2007 Microsoft Office system and the Microsoft Office 2003
System. In the procedures that follow you install Office Excel 2003 with Office InfoPath 2003, or
you install Office Excel 2007 and Office InfoPath 2007. If you install Microsoft Office 2003 you
must also install Microsoft Office 2003 Service Pack 2.
Office Excel is needed by the Business Activity Monitoring feature in BizTalk Server. You use the
BAM Office Excel Workbook to define the business processes you want to monitor. You also use
the BAM Excel Workbook to define the way in which business users see the data collected by
BAM.
Note
If Office Excel is not installed prior to installing BizTalk Server, BAM.xla and
KW_User_Guide.chm will be installed to their default location at %Drive%\Program
Files\Microsoft BizTalk Server 2006\Exceldir instead of %Drive%\Program Files\Microsoft
Office\OFFICE11\Library. If the 2007 Office system is installed, \OFFICE11\... will be
replaced with \OFFICE12\... in the preceding example.
Office InfoPath is optional for a BizTalk Server 2006 R2 installation. It is required only if you plan
to configure Business Activity Services (BAS) and use Office InfoPath as a BAS client.
The following procedures install only Office Excel and Office InfoPath. You can install additional
Microsoft Office system applications and tools if you want, but they are not necessary to complete
the installation of BizTalk Server.
To install Microsoft Office Excel 2003 and InfoPath 2003 with Office 2003 Service Pack 2
1. Begin the Microsoft Office 2003 setup.
2. When you reach the Type of Installation screen, select Custom Install, and then click
Next.
3. On the Custom Setup screen, select only Excel and InfoPath, and then click Next.
4. Click Install.
5. On the Setup Completed screen, click Finish.
6. Install Office 2003 Service Pack 2. To obtain the service pack, browse to
http://go.microsoft.com/fwlink/?LinkId=86806, "Office 2003 Service Pack 2 (SP2)."
To install Microsoft Office Excel 2007 and InfoPath 2007
1. Begin the Microsoft Office 2007 setup.
2. On the Choose the installation you want screen, click the Customize button.
30
3. On the next screen, click the Installation Options tab.

Only two programs are needed for a full installation of BizTalk Server 2006 R2: Office
Excel and Office InfoPath. Additionally, you must install Visual Basic for Applications
(VBA). You may install additional programs and features if you want.
4. To remove a program or feature from installation, click the name, and then choose Not
Available from the list.
5. Ensure that Run from My Computer is selected for Microsoft Office Excel and
Microsoft Office InfoPath.
6. Expand Office Shared Features, and then ensure Run from My Computer is selected
for Visual Basic for Applications.
7. Click the Install Now button.
Step 3: Install Visual Studio 2005

In the following procedure you install Visual Studio 2005.
Visual Studio 2005 is necessary to develop BizTalk Server applications. The BizTalk Server
development tools are integrated with Visual Studio 2005. BizTalk Server supports Visual
Studio 2005 SP1.
The BizTalk Server development tools are optional for a BizTalk Server installation. If you do not
intend to develop or debug BizTalk Server applications on your server, you do not need to install
Visual Studio 2005 or the BizTalk Server development tools.
If you plan to install the BizTalk Server Developer Tools and SDK component, then at a minimum,
you must install the Microsoft Visual C# .NET portion of Visual Studio 2005. The most common
configuration is a Typical or Complete installation of Visual Studio 2005. Do not install SQL
Server 2005 Express Edition.
The BizTalk Server runtime components require .NET Framework 2.0. In addition, the .NET
Framework 3.0 is required if the Windows Communication Foundation (WCF) adapter or WCF
Interceptor is installed.
To install Visual Studio 2005
1. Begin the Visual Studio 2005 setup.
2. Click Install Visual Studio 2005.
3. When you reach the Options Page, ensure that Custom is selected, and then click
Next.
4. Under Select features to install, clear all features except Visual C# and .NET
Framework SDK, and then click Install. You can install additional features if you want,
but only C# and the .NET Framework SDK are required.
Caution
Microsoft SQL Server 2005 Express Edition should not be installed on the same
31
computer as SQL Server 2000.

Caution
Microsoft SQL Server 2005 Mobile Edition should not be installed on the same
computer as SQL Server 2005. Doing so will cause SQL Server to use the Mobile
Edition runtime at startup.
5. On the Finish Page, click Finish.
You should restart your computer at the end of the installation.
Although you are not required to install Visual Studio service packs, we recommend that you
do. You can download the Visual Studio 2005 Service Pack 1 at
Step 4: Install SQL Server 2005 or SQL Server 2000

In the following procedure you install SQL Server 2000 or SQL Server 2005. For optimum
performance, we recommend SQL Server 2005 Enterprise Edition. If you plan to install SQL
Server 2000 instead of SQL Server 2005, see Appendix III: How To Install SQL Server 2000 in the
Technical Appendix at the end of this document.
The BizTalk Server 2006 R2 engine provides the capability to specify a business process and a
mechanism for communicating between applications that the business process uses. BizTalk
Server 2006 R2 uses SQL Server as the main repository for this communication mechanism. SQL
Server 2005 or SQL Server 2000 is a required piece of the overall architecture.
Note
SQL Server 2005 installation sets the profile to the Business Intelligence profile. When
you open Visual Studio for the first time, you will not have the option to select a default
profile setting. To work around this issue, reset the settings to the profile you want by
using Import and Export Settings in Visual Studio 2005.
Follow these steps if you plan to install SQL Server 2005.
To install SQL Server 2005 with SQL Server 2005 Service Pack 2
1. Begin the SQL Server 2005 installation.
2. Under Install, click Server components, tools, Books Online, and samples.
SQL Server 2005 Setup will install prerequisites.
3. On the Welcome to the Microsoft SQL Server Installation Wizard screen, click Next.
4. On the System Configuration Check screen, ensure that there are no errors before you
continue, and then click Next.
5. When you reach the Components to Install screen, select SQL Server Database
Services and Workstation components, Books Online and development tools. In
addition, you should select the following if you plan to leverage BAM features:
Analysis Services
Notification Services
32
Integration Services
Note
Using BizTalk Tracking database with SQL Server 2005 Analysis Services is not
supported.
Note
The Reporting Services component is optional.
Note
SQL Server Management Tools is required to configure BAM. Management Tools
are installed by default if the Workstation components, Books Online and
development tools option is selected, however, if you perform as advanced
setup you will need to ensure that Management Tools is installed. Management
Tools is located under the Client Components section in the SQL Server Setup
Wizard Feature Selection page.
6. After selecting all the necessary components, click Next.

7. On the Instance Name screen, select Default instance, and then click Next.
8. On the Service Account screen, leave the Customize for each service account check
box cleared and assign a logon account to the SQL Server services. If Use a domain
user account is selected, then enter a local account or domain account and password.
Make sure that the SQL Server Agent check box is selected for Start services at the
end of setup. Click Next.
If the computer on which you are installing SQL Server is a member of a domain, you
should use a domain local or domain global account. Local accounts (those that are
visible only on the computer where they were created) are not recommended except
when there is no alternative. Local accounts do not appear in Active Directory and they
must be managed on the computer where they were created.
9. On the Authentication Mode screen, select Windows Authentication Mode, and then
click Next.
10. On the Collation Settings screen, leave the default unless you have a specific
requirement for a different collation, and then click Next.
BizTalk Server does not support binary (case sensitive) collations.
11. On the Error and Usage Report Settings screen, you can leave the defaults or elect to
participate in the error reporting and feature usage programs, and then click Next.
12. On the Ready to Install screen, review the information, and then click Install.
13. On the Setup Progress screen, after setup has finished, click Next.
14. On the Completing Microsoft SQL Server 2005 Setup screen, click Finish.
Note
Restart your computer at the end of the installation.
33
SQL Server 2005 Service Pack 2 is required for BizTalk Server 2006 R2. In this procedure you
will update your SQL Server 2005 installation by applying SQL Server 2005 Service Pack 2.
Note
You do not need to perform this step if you installed a version of SQL Server 2005 that
includes Service Pack 2.
To install SQL Server 2005 Service Pack 2
1. Browse to http://go.microsoft.com/fwlink/?linkid=86436 to download the appropriate
service pack for your computer. For Windows x64 editions, download and save
SQLServer2005SP2-KB921896-x64-ENU.exe to your local hard drive. For 32-bit
Windows editions, download and save SQLServer2005SP2-KB921896-x86-ENU.exe to
your local hard drive.
2. Locate the file you just downloaded and double-click it to run Setup. The Microsoft SQL
Server 2005 Service Pack 2 Setup screen will appear. Click Next.
3. Review the license terms, select I accept the agreement, then click Next.
4. On the Feature Selection screen, click Next.
5. On the Authentication screen, verify that the authentication method is set to Windows
Authentication, and then click Next.
6. On the Error and Usage Reporting Settings screen, you can leave the defaults or
choose to send error and feature usage data, and then click Next.
7. The Running Processes screen will appear. Running processes that have locked files
that need to be updated will be displayed here. Listed processes, if any, should be shut
down using the Services management tool. When there are no running processes
remaining in the list, click Next.
8. The Ready to Install screen will appear. Click Install.
Step 5: Install Windows SharePoint Services

In the following procedures you install Windows SharePoint Services (WSS). Windows
SharePoint Services is a collection of services for Windows Server 2003 that you can use to
share information, collaborate with other users on documents, and create lists and Web part
pages.
Note
You do not need to install WSS if you do not also plan to install the WSS adapter or BAS.
BizTalk Server 2006 R2 supports side-by-side installation of both Windows SharePoint
Services 2.0 and Windows SharePoint Services 3.0. (Side-by-side installation is not the same as
side-by-side execution.) This step of the installation contains the procedures needed to install
both WSS 3.0 and WSS 2.0 SP2. See Considerations for Installing Windows SharePoint Services
for more information.
34
In the following procedures, you will install WSS 3.0 before installing WSS 2.0 SP2. If WSS 3.0 is
installed after WSS 2.0, the WSS 3.0 Setup Wizard will automatically attempt to upgrade the
existing WSS 2.0 installation. Installing WSS 3.0 first will avoid this problem.
Configure ASP.NET 2.0 to Run In 64-Bit Mode On 64-Bit Windows Editions
The following procedure only applies to the 64-bit Windows editions. You must configure IIS and
ASP.NET 2.0 to run in 64-bit mode before installing WSS 3.0. You do not have to perform this
step if you do not plan to install WSS 3.0.
To configure ASP.NET 2.0 for 64-bit mode
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 64-bit mode:
cscript %Systemdrive%\inetpub\adminscripts\adsutil.vbs SET
W3SVC/AppPools/Enable32bitAppOnWin64 0
3. Type the following command to install the version of ASP.NET 2.0 (64-bit) and to install
the script maps at the IIS root and under:
%Systemroot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i -enable
4. Type the following command to reset IIS

IISRESET
Note
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the
Web service extension list in Internet Information Services Manager.
Install Windows SharePoint Services 3.0
In the following procedure you install Windows SharePoint Services 3.0.
To install Windows SharePoint Services 3.0
1. Windows SharePoint Services 3.0 requires Microsoft .NET Framework 3.0, which must
be installed before beginning installation of Windows SharePoint Services 3.0. The .NET
Framework is available for download at http://go.microsoft.com/fwlink/?linkid=75053.
Note
The default .NET Framework 3.0 download requires that the installation computer
is connected to the Internet during the setup process. This requirement may be
avoided by downloading and installing the full redistributable package for .NET
Framework 3.0. The full redistributable package for 32-bit systems is available at
http://go.microsoft.com/fwlink/?linkid=70848. The full redistributable package for
64-bit (x64) systems is available at http://go.microsoft.com/fwlink/?linkid=70849.
2. Browse to http://go.microsoft.com/fwlink/?linkid=77800 (32-bit x86) or
http://go.microsoft.com/fwlink/?linkid=95019 (64-bit x64). Download the installation
package to a location on your hard disk.
35
3. Locate the package you just downloaded (SharePoint.exe), and then double-click the
package to start the setup.
4. On the End User License Agreement screen, select I accept the terms in the License
Agreement. On this screen and several others that follow, the setup wizard will
automatically move to the next screen when you have made your selection.
5. Under Type of installation, choose the Advanced button.
Note
If Windows SharePoint Services 2.0 is already installed, the Windows SharePoint
Services 3.0 setup will display an Upgrade earlier versions tab. If you would
like to perform a side-by-side installation of Windows SharePoint Services 3.0
with Windows SharePoint Services 2.0, chose the option for No, do not run
upgrade at this time, then continue with the setup procedure as documented
below.
Important
Do not upgrade a Windows SharePoint Services 2.0 installation until you have
reviewed Considerations for Installing Windows SharePoint Services. Some
BizTalk Server features are not compatible with Windows SharePoint Services
3.0 or Microsoft Office SharePoint Server 2007.
6. On the Server Type tab, select Web Front End, then click Install Now.
7. When installation is completed, clear the check box for Run the SharePoint products
and technologies Configuration Wizard, and then click Close. You will not configure
anything at this time.
Configure ASP.NET 2.0 to Run In 32-Bit Mode On 64-Bit Windows Editions
The following procedure only applies to the 64-bit Windows editions. You must configure IIS and
ASP.NET 2.0 to run in 32-bit mode before installing WSS 2.0 SP2.
To Configure ASP.NET 2.0 for 32-bit mode
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 32-bit mode:
cscript %Systemdrive%\inetpub\adminscripts\adsutil.vbs SET
W3SVC/AppPools/Enable32bitAppOnWin64 1
3. Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install
the script maps at the IIS root and under:
%Systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable
4. Type the following command to reset IIS

IISRESET
Note
Make sure that the status of ASP.NET version 2.0.50727 (32-bit) is set to
36
Allowed in the Web service extension list in Internet Information Services

Manager.
Install Windows SharePoint Services 2.0 with Service Pack 2
In this procedure you will install Windows SharePoint Services (WSS).
To install Windows SharePoint Services 2.0 with Service Pack 2
1. Browse to http://go.microsoft.com/fwlink/?LinkId=47398 (for 32-bit and 64-bit Windows
editions).
2. On the Download Windows SharePoint Services with Service Pack 2 page, under
Download, click Windows SharePoint Services with SP2.
3. On the Windows SharePoint Services with Service Pack 2 page, click Download.
4. Save the file to a location on your hard disk.
5. Locate the package you just downloaded, and then double-click stsv2.exe.
6. On the End User License Agreement screen, select I accept the terms in the License
Agreement, and then click Next.
7. Under Type of Installation, ensure that Server Farm is selected, and then click Next.
Note
The default setting for Type of Installation is Typical Installation. Make sure
that you select Server Farm before you click Next.
8. On the Summary screen, click Install.
Note
At the end of installation, the Configure Administrative Virtual Server screen
appears. You will not configure anything at this time.
9. Close the Configure Administrative Virtual Server Web browser.
Task 3: Configure the Platform

In this task, you finish configuring the platform. You must complete the configuration steps before
installing BizTalk Server 2006 R2.
Step 1: Configure Default Web Site for ASP.NET 2.0

In this procedure you configure the Default Web Site for ASP.NET 2.0. This must be done prior to
installing the Windows SharePoint Services adapter for BizTalk Server.
Note
The following procedure applies to 32-bit Windows only. There are no user-configurable
options for ASP.NET 2.0 on 64-bit systems. For more information, see
37
To configure the Default Web Site for ASP.NET 2.0

1. Click Start, point to Administrative Tools, and then click Internet Information Services
(IIS) Manager.
2. In Internet Information Services (IIS) Manager, expand your server, expand Web
Sites, right-click Default Web Site, and then click Properties.
3. In Default Web Site Properties, click the ASP.NET tab.
4. In the ASP.NET Version drop-down box, select 2.0.50727.0, and then click OK.
5. Close IIS Manager.
Step 2: Configure Windows SharePoint Services 2.0

In the following procedure you finish configuring Windows SharePoint Services 2.0 (WSS).
This procedure (and the configuration procedures that follow) suggests generic names for
objects, such as the application pool and Windows SharePoint Services database. You are free to
substitute names to suit your organizational requirements and preferences, however, be sure to
use the correct names in place of the generic names in the configuration procedures following
this one.
You will need to provide an application pool identity account during configuration. It is best to
create this account before beginning WSS configuration. The identity account is a user or domain
user account, and it is a member of the IIS_WPG and STS_WPG security groups. Ordinarily the
SharePoint Central Administration setup will perform this task for you, but if you are performing a
manual configuration or troubleshooting a new installation, you should verify correct group
membership.
The application pool identity account must have a corresponding login account on the SQL Server
that will host your WSS configuration database. The SQL Server login for the application pool
identity account must be granted the following Server Roles: dbcreator,securityadmin, and
public. The SharePoint Central Administration configuration program will map the login account
to the database you specify during configuration.
To configure Windows SharePoint Services 2.0
1. Click Start, point to Administrative Tools, and then click SharePoint Central
Administration.
Note
Because you did not finish configuration earlier, you are presented with the
configuration screens for Windows SharePoint Services.
2. Under Application Pool, ensure that Create a new application pool is selected.
3. In the Application pool name field, type WSSAppPool.
4. Under Select a security account for this application pool, ensure that Configurable
is selected.
5. In the User name field, type the name of the network account the application pool will run
38
under.
The account you specify must be in the format of DomainName\UserName
orServerName\UserName if you are using a local account. If when you attempt to save
the configuration settings you receive System Error 1057 while trying to query SPTimer
it is a cryptic indication that you did not correctly format the account as described above.
If you encounter Error 18456, see http://go.microsoft.com/fwlink/?LinkId=61924 for
instructions to resolve the error.
Note
When using binary collation with SQL Server, the domain or server name you
specify in the SharePoint Admin Application Pool account must be in uppercase
letters.
6. In the Password field, type the account password, and then confirm the password.
7. Under Security Configuration, select NTLM, and then click OK.
Note
Kerberos authentication is not supported with Business Activity Services.
8. The Application Pool Changed page loads and tells you that you must restart IIS.
9. Click Start, click Run, type IISRESET, and then click OK.
10. On the Application Pool Changed page, click OK. The Configuration Database page
loads.
11. Under Configuration Database, in the Database server field, type the name of your
SQL Server.
12. In the SQL Server database name field, type WSSDB.
13. Leave the rest of the default values, and then click OK. This creates the configuration
database and you are redirected to the Central Administration Homepage.
Step 3: Extend Default Web Site as a Virtual Server

Microsoft Windows SharePoint Services uses virtual servers to host Web sites on your server.
The process of applying Windows SharePoint Services to a virtual server is called extending. You
must extend a virtual server with Windows SharePoint Services before you can create a Web site
based on Windows SharePoint Services. In the following procedure you extend the Default Web
Site as a Windows SharePoint Services virtual server.
To extend Default Web Site as a virtual server
1. On the Central Administration Homepage, under Virtual Server Configuration, select
Extend or upgrade virtual server.
2. On the Virtual Server List page, under Virtual Server List, select Default Web Site.
3. On the Extend Virtual Server page, under Provisioning Options, select Extend and
create a content database.
4. On the Extend and Create Content Database page, under Create a new application
39
pool, in the Application pool name field, type MyAppPool.

5. Under Select a security account for this application pool, in the User name text box,
type an account that will be used for this application pool.
6. In the Password text box, type the account password, and then confirm that password.
7. Under Site Owner, in the E-mail text box, type your e-mail address.
8. Under Security Configuration, select NTLM.
Note
Kerberos authentication is not supported with Business Activity Services.
9. Leave the rest of the default values, and then click OK.
10. On the Virtual Server Successfully Extended page, select your new top-level Web site.
This will open a new browser.
Note
Depending on your security settings, you may be prompted to enter your
credentials.
11. On the Template Selection page, select the Team Site template, and then click OK.
12. Close the Team Web Site you just created.
13. Click the Windows SharePoint Services link to return to the SharePoint Central
Administration site.
14. On the SharePoint Central Administration site, click the Configure virtual server
settings link.
15. Click the Default Web Site that you extended.
16. Under Virtual Server Management, click Define managed paths.
17. Under Included Paths select the (root) check box and click the Remove selected paths
link.
18. Click the Windows SharePoint Services link to return to the SharePoint Central
Administration site.
19. Close the SharePoint Central Administration tool.
Step 4: Disable SQL Server Shared Memory Protocol

In the following procedure you disable the SQL Server shared memory protocol.
When using the SQL Server shared memory protocol with BizTalk Server 2006 R2 you might
experience degradation in performance under certain stress conditions, if clients are accessing
SQL Server from the same computer. To resolve the problem you need to disable the use of the
shared memory network protocol in the SQL Server Client Network Utility. After you disable the
shared memory protocol, you will need to restart SQL Server services.
To disable shared memory protocol for SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to
40
Configuration Tools, and then click SQL Server Configuration Manager.

2. In SQL Server Configuration Manager, expand SQL Server 2005 Network
Configuration, and then click Protocols for MSSQLSERVER.
3. Right-click Shared Memory, and then click Disable.
4. Close SQL Server Configuration Manager.
Note
Changes will not take effect until the SQL Server service is restarted.
To disabled shared memory protocol for SQL Server 2000
1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Client
Network Utility.
2. In the SQL Server Client Network Utility, clear Enable shared memory protocol, and
then click OK.
Task 4: Install BizTalk Server 2006

In this task, you install BizTalk Server 2006 R2 on the server you just prepared.
Note
After you install BizTalk Server 2006 R2, see the Post-Installation Requirements. We
strongly recommend that you perform each step in the Post-Installation Requirements
section to complete a successful BizTalk Server 2006 R2 installation.
When you install BizTalk Server 2006 R2, consider the following:
Ensure that you have installed all BizTalk Server software prerequisites necessary for the
type of installation you want to perform.
Your computer name should not exceed 15 characters for the BizTalk Server configuration to
work properly.
Avoid changing the computer name after configuration. If the computer name is changed, the
BizTalk Server configuration will not work. Recovery entails restoring the computer name or
removing and reinstalling BizTalk Server.
The account you are logged on as must be part of the local administrators group and have
DBA rights on SQL Server. After configuration is complete, you can lower the privileges to
DBO.
Close all other programs before installing BizTalk Server.
Both BizTalk Server 2006 R2 Setup and Windows Installer generate log files during the
installation process. By default, Setup creates log files in the %Temp% folder. The log files consist
of one .htm summary file that is generated each time Setup is executed, one detailed .log file
generated by MSI, and one .log file for configuration.
BizTalk Server 2006 R2 writes event messages to the Windows application log. The Windows
application log collects information about events that are generated by the applications running
41
on the local system. You can use the Event Viewer to view the log file and to filter the messages it
contains.
If the application event log runs out of space during BizTalk Server setup, the installation will fail.
To avoid this problem you should ensure that the application log has sufficient space available
before running setup. The amount of space required in the application log varies depending on
the BizTalk Server features installed during setup. You can clear the log events before running
setup, or change the event log properties to provide more space or to allow the event logging
system to overwrite old event log entries.
For more information about the Windows application log or Event Viewer, see the Windows
product documentation.
Step 1: Install BizTalk Server 2006

In the following procedure you install BizTalk Server 2006 R2.
To install BizTalk Server 2006 R2
1. Start the BizTalk Server setup program. On the Microsoft BizTalk Server 2006
Installation Wizard page, click Install Microsoft BizTalk Server 2006 on this
computer.
2. When you reach the Component Installation page, review the available components
and select the ones you want to install. For more information about the components, see
"BizTalk Server 2006 Features and Components" in BizTalk Server 2006 R2 Help. Accept
the default installation location or click Browse to move to the location where you want to
install BizTalk Server 2006 R2, and then click Next.
Note
If a feature option is grayed out, it means that the feature has a prerequisite that
is not included in the redistributable prerequisite package.
Note
MQSeries Agent option is disabled if IBM WebSphere MQ 5.3 with CSD10 or
IBM WebSphere MQ 6.0 is not found on the computer.
Note
Unicode characters are not supported in the installation path for BizTalk Server
2006 R2.
3. On the Redistributable Prerequisites page, if your computer is missing a prerequisite
component such as ADOMD .NET 8.0, ADOMD .NET 9.0, or SQLXML 3.0 SP3, Setup
can install the redistributable prerequisites. Select Automatically install the
redistributable prerequisites from the web, or if you have downloaded the CAB file,
select Automatically install the redistributable prerequisites from a CAB file and
browse to the location of the CAB file and select it. For a complete listing of the
redistributable CAB files, see . Click Next.
Note
42
If you plan to use a redistributable CAB file, we recommend that you download
the CAB file to a network share. During the installation, the BizTalk Server 2006
R2 installation disk needs to remain in the CD drive from which you are installing
BizTalk Server.
4. On the Summary page, verify that the components that you select to install are correct.
5. Click Install to start the installation process.
Note
During the installation of the BizTalk Server Web services, the Visual Studio 2005
Choose your default environment settings dialog box may appear. To close
this dialog box and continue the installation of BizTalk Server 2006 R2, click Exit
Visual Studio.
6. On the Installation Completed page, verify that the Launch BizTalk Server
Configuration check box is selected, and then click Finish. This starts the Configuration
Wizard.
Task 5: Configure BizTalk Server 2006

In this task, you configure BizTalk Server 2006 R2 using the Basic configuration option.
Alternatively, you can configure BizTalk Server using the Custom configuration option. The
basic configuration is for single-computer installation only. For multicomputer environments, see
http://go.microsoft.com/fwlink/?LinkId=83322. For more information about manually configuring
your BizTalk Server, see "Configuring BizTalk Server 2006 R2" in BizTalk Server Help.
Before you configure BizTalk Server 2006 R2, consider the following:
You should create the service account under which the BizTalk Server service in-process host
will run before starting configuration. You will be prompted to enter the account name and
password during configuration. For more information, see the section.
The account you are logged on as must be part of the local administrators group and have
System Administrator rights on SQL Server.
During Basic Configuration, the user who is running the configuration tool will be the BAS site
owner.
Configuration fails if the event log is full. You need to make sure that the event log is not full
during the configuration.
Antivirus software should be temporarily disabled before beginning configuration. Real-time

file scanning can interfere with the configuration program.
Step 1: Configure BizTalk Server 2006

In the following procedure you configure your server using the Basic Configuration option.
To configure BizTalk Server 2006 R2 using Basic Configuration
1. On the Microsoft BizTalk Server 2006 Configuration start page, ensure that Basic
43
Configuration is selected.
2. Under Database, ensure that you enter the name of the computer where SQL Server is
installed. SQL Server must be installed on the local computer for basic configuration.
3. Under Service Credential, in the User name text box, type the user name for the
account that the BizTalk services will run under.
Note
In a Basic Configuration, all BizTalk services will run under this account. The
configuration process grants this account the necessary security permissions on
the server and objects in SQL Server.
4. Under Service Credential, in the Password text box, type the password for the account
you specified, and then click Configure.
Note
You may receive a warning if you enter a user name with administrative
credentials on this computer. Click OK to continue.
5. On the Summary page, review the configuration about to be performed and make sure
all features are validated, and then click Configure.
6. On the Completion page, click Finish.
Note
If you have an anti-spyware software package installed, you may see a security level
warning during the configuration of the BAS site.
Step 2: (Optional) Install Orchestration Designer for Business Analysts

(ODBA)
In the following procedure you install Orchestration Designer for Business Analysts (ODBA).
Note
Microsoft .NET Framework 2.0 and Microsoft Office Visio 2003 SP2 (or Microsoft Office
Visio 2007) must be installed before installing ODBA.
To install Orchestration Designer for Business Analysts
1. Browse to http://go.microsoft.com/fwlink/?LinkId=63132.
2. Download and double-click ODBA.exe to extract the files to C:\ODBA, and then browse
to that directory.
3. Double-click Microsoft BizTalk Server 2006 Orchestration Designer for Business
Analysts.msi.
4. On the Welcome screen, click Next.
5. On the License Agreement screen, select I accept the License Agreement, and then
click Next.
6. On the Start Installation screen, click Install.
44
7. On the Completion page, click Finish.

For information about completing the BizTalk Server 2006 R2 installation, see Post-Installation
Requirements.
Post-Installation Requirements
After you install BizTalk Server 2006 R2, you must follow these post-installation steps in the order
listed:
If you installed the Windows SharePoint Services adapter, you must add the BizTalk Service
account to the SharePoint Enabled Hosts Windows group on that server.
If you installed Human Workflow Services, you will need to add the HWS Web Service user to
the IIS_WPG and STS_WPG Windows groups.
Ensure that TCP/IP and named pipes are enabled in the Microsoft SQL Server 2000 Client
Network Utility or the SQL Server 2005 Configuration Manager.
Download and install BizTalk Server 2006 Best Practices Analyzer from
http://go.microsoft.com/fwlink/?LinkId=83317. The BizTalk Server 2006 Best Practices
Analyzer examines a BizTalk Server 2006 R2 deployment and generates a list of best
practices issues it discovers. The Best Practices Analyzer performs configuration-level
verification, by reading and reporting only, and uses the gathered data to determine whether
best practices are being followed.
Performing a Silent Installation

BizTalk Server 2006 R2 provides a command-line setup which enables automated software
distribution, also known as silent installation. You use silent installation to install BizTalk Server
2006 R2 in an automated way on computers that have the same configurations. Silent installation
lets system administrators who want to install BizTalk Server 2006 R2 on remote computers do so
without user intervention. With a silent installation, a user does not have to monitor the installation
and provide input.
To perform a silent installation, use the command-line options provided to suppress all interaction
and to provide parameters for all options.
When you perform a silent installation, the installation program does not display messages.
Instead, a log file captures the installation information that includes whether the installation was
successful. You can then review the log file and determine the results of the installation.
Performing a Silent Installation of BizTalk Server 2006

Use the following steps to perform a silent installation of BizTalk Server 2006 R2.
To perform a BizTalk Server 2006 R2 silent installation
1. Click Start, point to All Programs, point to Accessories, and then click Command
Prompt.
45
2. To start the silent installation, at the command prompt, type setup.exe /<command
name> <options>, and then press ENTER.
The following table shows the Windows Server 2003 command-line options that you use to install
Command name
Option
Description
/HELP, or /?, or /H
Provides help and quick

reference.
/QUIET
Performs an installation
without a user interface. You
cannot cancel the installation.
Note
All messages are
entered into the setup
log file.
Note
The Quiet flag cannot
be specified for an
upgrade.
/CABPATH
<CAB file location>
Indicates the location of the

redistributable CAB file.
/S
<Configuration XML file>
Performs a silent installation of

features found in the specified
configuration file.
Note
To install all features,
specify ALL for the
<InstalledFeature>
parameter of the
configuration XML file.
/PASSIVE
Performs a passive
installation. The setup program
only displays the progress bar.
/NORESTART
Suppresses restart prompts

and automatic restarts at the
end of the installation.
/FORCERESTART
Always forces a restart after

46
Command name
Option
Description
the installation is complete.

/PROMPTRESTART
Prompts the user before

restarting.
/X or /UNINSTALL
Uninstalls BizTalk Server 2006

R2.
/L
<Logfile> [i][w][e][a][r][u][c][m]
[p][v][*]
Writes logging information to a

log file to the specified path.
Always uses verbose MSI
logging and it appends to an
existing file.
The following flags indicate
which information to log:
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Startup of actions
r - Action-specific records
u - User requests
c - Initial user interface
parameters
m - Out-of-memory
p - Terminal properties
v Verbose output
* - All
/IGNOREDEPENDENCIES
Bypasses the checks for

downloadable prerequisites.
/INSTALLDIR <Install Path>
<program files folder>
Specifies the full path to

product install location.
/COMPANYNAME
<Company name>
Sets the company or

organization name.
/USERNAME
<User name>
Sets the user name.
/PRODUCT
Specifies the product name.
/ADDLOCAL ALL
Installs all features.
/REMOVE ALL
Removes all features.
47
Command name
Option
/REPAIR ALL
Description
Repairs all features.
Uninstalling BizTalk Server 2006

To uninstall BizTalk Server 2006 R2 and all its components, follow these steps in the order
shown.
Note
If you have installed a prerelease version of BizTalk Server 2006 R2 you will have to
uninstall it before you can install the retail version of BizTalk Server 2006 R2.
Task 1: Uninstalling BizTalk Server 2006 Runtime Components

and Databases
In this task, you uninstall BizTalk Server 2006 R2 from your server. Before you uninstall BizTalk
Server 2006 R2, consider the following:
Do not remove BizTalk Server prerequisites before you remove BizTalk Server. They must be
present for the process to complete successfully.
If assemblies stored in the global assembly cache (GAC) are in use when you uninstall
BizTalk Server, you cannot remove them completely. To ensure that you remove all
assemblies, stop all host instances from running and stop Internet Information Services (IIS)
before you uninstall BizTalk Server.
The BizTalk Server uninstall process does not remove the maps and schemas that have been
created in Visual Studio 2005 or the BizTalk Server databases.
Uninstalling BizTalk Server does not uninstall Enterprise Single Sign-On (SSO). Use
Add/Remove Programs to uninstall SSO manually. You cannot uninstall SSO if you have a
dependent BizTalk Server feature installed on the same computer.
If you have other applications using SSO, you must reconfigure SSO. If SSO is configured on
the master secret server, you will need to back up the master secret before uninstalling
BizTalk Server 2006 R2 and then restore it after SSO has been reconfigured.
If you choose to delete the Windows groups created during an installation and configuration
of BizTalk Server, you must revoke the rights from the SQL Server database by deleting it
from SQL Server Security. If you do not do this, the next configuration of BizTalk Server 2006
R2 will fail.
Step 1: Uninstall BizTalk Server 2006 R2 Runtime Components

In the following procedure you uninstall the BizTalk Server 2006 R2 Runtime components.
To uninstall BizTalk Server 2006 R2 runtime components
1. Click Start, point to Control Panel, and then click Add/Remove Programs.
48
2. In the Add/Remove Programs dialog box, click Microsoft BizTalk Server 2006, and
then click Change/Remove.
3. On the Program Maintenance screen, select Remove, and then click Next.
4. On the Summary screen, review the components to be uninstalled, and then click
Uninstall.
5. On the Uninstall Completed screen, click Finish.
In the following procedure you uninstall the Microsoft Enterprise Single Sign-On Services.
To uninstall Enterprise SSO services
1. Click Start, point to Control Panel, and then click Add/Remove Programs.
2. In the Add/Remove Programs dialog box, click Microsoft Enterprise Single Sign-On,
and then click Change/Remove.
3. On the Program Maintenance screen, select Remove, and then click Next.
4. On the Summary screen, review the components to be uninstalled, and then click
Uninstall.
5. On the Uninstall Completed screen, click Finish.
Note
If you have BizTalk Server Runtime, Development, or Administration features
installed, you are not able to uninstall the SSO Runtime or Administration
components until all dependencies are removed.
Step 2: Remove BAM Alerts Notification Services Instance

In the following procedure you remove the Notification Services instance created for BAM Alerts
when you configure BizTalk Server 2006 R2 using this guide.
To remove BAM Alerts Notification Services instance from SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click
Configuration Tools. On the Configuration Tools menu, click Notification Services
Command Prompt.
2. Type the following command to disable the instance: nscontrol disable -name
BAMAlerts.
3. Type the following command to stop the instance: net stop NS$BAMAlerts.
4. Type the following command to unregister the instance: nscontrol unregister -name
BAMAlerts.
Note
The BAM Notification name is generated as NS$<Prefix for Alerts Database
Name> where <Prefix for Alerts Database Name> is what you specified on the
BAM Alerts configuration page. The default name is BAMAlerts.
49
To remove BAM Alerts Notification Services instance on SQL Server 2000 Notification
Services
1. Click Start, point to All Programs, point to Microsoft SQL Server Notification
Services 2.0 SP1, and then click Notification Services Command Prompt.
2. Type the following command to disable the instance: nscontrol disable -name
BAMAlerts.
3. Type the following command to stop the instance: net stop NS$BAMAlerts.
4. Type the following command to unregister the instance: nscontrol unregister -name
BAMAlerts.
Note
The BAM Notification name is generated as NS$<Prefix for Alerts Database
Name> where <Prefix for Alerts Database Name> is what you specified on the
BAM Alerts configuration page. The default name is BAMAlerts.
Step 3: Remove BizTalk Server 2006 R2 SQL Server Agent Jobs

In the following procedure you remove the SQL Server Agent Jobs that were created when you
installed the BizTalk Server 2006 R2.
To remove SQL Server agent jobs on SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to SQL
Server Management Studio, and then click SQL Server Management Studio.
2. Click Connect.
3. In Object Explorer, expand SQL Server Agent, and then expand Jobs.
4. Remove the following jobs:
Backup BizTalk Server (BizTalkMgmtDb)
CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
DTA Purge and Archive (BizTalkDTADb)
MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
MessageBox_UpdateStats_BizTalkMsgBoxDb
Operations_OperateOnInstances_OnMaster_BizTalkMsgBoxDb
PurgeSubscriptionsJob_BizTalkMsgBoxDb
Rules_Database_Cleanup_BizTalkRuleEngineDb
TrackedMessages_Copy_BizTalkMsgBoxDb
Note
50
If you deployed BAM, you may also need to remove the job named bam_<Cube
Name>_<View Name>.
To remove SQL Server agent jobs on SQL Server 2000
1. Click Start, point to All Programs, point to Microsoft SQL Server, point to Enterprise
Manager, and then click Enterprise Manager.
2. In Enterprise Manager, expand SQL Server Group, expand (local), expand
Management and expand SQL Server Agent. Click Jobs.
3. Remove the following jobs:
Backup BizTalk Server (BizTalkMgmtDb)
CleanupBTFExpiredEntriesJob_BizTalkMgmtDb
DTA Purge and Archive (BizTalkDTADb)
MessageBox_DeadProcesses_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_Cleanup_BizTalkMsgBoxDb
MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb
MessageBox_Parts_Cleanup_BizTalkMsgBoxDb
MessageBox_UpdateStats_BizTalkMsgBoxDb
Operations_OperateOnInstances_OnMaster_BizTalkMsgBoxDb
PurgeSubscriptionsJob_BizTalkMsgBoxDb
Rules_Database_Cleanup_BizTalkRuleEngineDb
TrackedMessages_Copy_BizTalkMsgBoxDb
Note
If you deployed BAM, you may also need to remove the job named bam_<Cube
Name>_<View Name>.
Step 4: Remove BizTalk Server 2006 R2 SSIS or DTS Packages

In the following procedure you remove the SQL Server Integration Services (SSIS) packages on
SQL Server 2005 or remove the DTS packages on SQL Server 2000 that were created when you
deployed BAM.
To remove SQL Server Integration Services Packages on SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, point to SQL
Server Management Studio, and then click SQL Server Management Studio.
2. Click Connect.
3. In Object Explorer, click Connect and select Integration Services, and then click
Integration Services.
4. Expand Stored Packages and expand MSDB.
5. Remove the packages with the following prefixes:
51
BAM_AN_<Cube Name>
BAM_DM_<View Name>
To remove SQL Server DTS Packages on SQL Server 2000

1. Click Start, point to All Programs, point to Microsoft SQL Server, point to Enterprise
Manager, and then click Enterprise Manager.
2. In Enterprise Manager, expand SQL Server Group, expand (local), expand Data
Transformation Service and expand Local Packages. Click Local Packages.
3. Remove the packages with the following prefixes:
BAM_AN_<Cube Name>
BAM_DM_<View Name>
Step 5: Remove BizTalk Server 2006 R2 SQL Server Databases

In the following procedure you remove the default SQL Server databases that were created when
you performed a complete installation of BizTalk Server 2006 R2 using this guide.
To remove BizTalk Server 2006 R2 databases on SQL Server 2005
1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click
SQL Server Management Studio.
2. In Object Explorer, expand Databases.
3. Remove the following databases:
BAMAlertsApplication
BAMAlertsNSMain
BAMArchive
BAMPrimaryImport
BAMStarSchema
BizTalkDTADb
BizTalkEDIDb
BizTalkHwsDb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
SSODB
Note
If you configured the server using Custom configuration and modified the
database names, you will need to remove those databases.
52
To remove BizTalk Server 2006 R2 databases on SQL Server 2000

1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click
Enterprise Manager.
2. In Enterprise Manager, expand Microsoft SQL Servers, expand SQL Server Group,
expand (local)(Windows NT), and then click Databases.
BAMAlertsNSMain
BAMArchive
BAMPrimaryImport
BAMStarSchema
BizTalkDTADb
BizTalkEDIDb
BizTalkHWSDb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
SSODB
Note
If you configured the server using Custom configuration and modified the
database names, you will need to remove those databases.
Step 6: Remove BizTalk Server 2006 R2 SQL Server Analysis Services

Databases
In the following procedure you remove the default SQL Server Analysis Services databases that
were created when you performed a complete installation of BizTalk Server 2006 R2 using this
guide.
Note
If you configured the server using Custom configuration and modified the database
names, you will need to remove those databases.
To remove BizTalk Server 2006 R2 Analysis Service databases on SQL Server 2000
1. Click Start, point to All Programs, point to Microsoft SQL Server, point to Analysis
Services, and then click Analysis Manager.
2. In Analysis Manager, expand Analysis Servers, and then expand your local server.
BizTalkAnalysisDB
53
BAMAnalysis
Technical Appendices
This section covers technical reference information for BizTalk Server 2006 R2.
Appendix I: Windows Groups and Service Accounts

If possible, you should 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 may 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, and you need to change the default accounts to
conform to the standard.
If you must change the account names, consider the following:
BizTalk Server 2006 R2 supports only <NetBIOS domain name>\<user> name formats for
service accounts and Windows groups.
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 must 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 "Group Scope" in the Windows Server 2003 product Help at
If Domain Local Groups are used, the logon account used to configure BizTalk Server must
also be a member of the domain where the Domain Local Groups exist.
The user running the BizTalk Server configuration must belong to the following user groups:
Administrators group on the local computer.
SQL System Administrators group on the SQL server. The user does not need to be a
member of the Administrators group for the computer on which SQL Server is installed.
The domain group used for the BizTalk Server Administrators group.
The domain group used for the SSO Administrators group.
Windows Groups Used In BizTalk Server

The 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.
Group
Group Description
Membership
SQL Server Roles or

Database Roles
SSO
Administrator of the Enterprise Single
Administrator Sign-On (SSO) service.
Contains
service
db_owner SQL Server

Database Role for the
54
Group
Group Description
Membership
SQL Server Roles or

Database Roles
For more information about SSO

accounts, see "How to Specify SSO
Administrator and Affiliate Administrators
Accounts" at
LinkID=89383.
accounts for
Enterprise
Single SignOn service.
Contains
users/groups
that need to
be able to
configure and
administer
BizTalk
Server and
SSO service.
SSO
securityadmin SQL
Server Role for the
SQL Server where
SSO is located
Contains
accounts
used to run
BizTalk
Configuration
Manager
when
configuring
SSO master
secret server.
SSO Affiliate Administrators of certain SSO affiliate
Administrator applications.
s
Can create/delete SSO affiliate
applications, administer user mappings,
and set credentials for affiliate application
users.
Contains no
service
accounts.
BizTalk
Server
Administrator
s
Can deploy solutions, manage

applications, and resolve message
processing issues.
Contains
BAS
Management
Web Service
Account.
BTS_ADMIN_USERS
SQL Server Database
Role in the following
databases:
To perform administrative tasks for

adapters, receive and send handlers, and
Contains
users/groups
BizTalkMsgBoxDb
Has the fewest privileges necessary to

perform administrative tasks.
Contains
account used
for BizTalk
Server
Administrator
s.
BizTalkMgmtDb
BizTalkRuleEngineDb
55
Group
Group Description
Membership
SQL Server Roles or

Database Roles
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
linkid=110476.
that need to
be able to
configure and
administer
BizTalk
Server.
BizTalkDTADb
BAMPrimaryImport
db_owner SQL Server
Database Role for the
following databases:
BAMStarSchema
BAMPrimaryImport
BAMArchive
BAMAlertsNSMain
NSAdmin SQL Server
Database Role in the
BAMAlertsNSMain
HWS_ADMIN_USER
SQL Server Database
databases:
BizTalkDTADb
BizTalkHwsDb
BizTalkMgmtDb
OLAP Administrators
on the computer
hosting the
BAMAnalysis OLAP
database.
BizTalk
Server
Operators
Has a low privilege role with access only

to monitoring and troubleshooting actions.
Contains
user/groups
that will
monitor
solutions.
BTS_OPERATORS
SQL Server Database
databases:
Contains no
service
accounts.
BizTalkEDIDb
BizTalkDTADb
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
56
Group
Group Description
Membership
SQL Server Roles or

Database Roles
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).
BizTalk
The default name of the first Isolated
Isolated Host BizTalk Host Group created by
Users
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
In-Process
host instance
in the host
that the
BizTalk Host
Group is
designated
for.
BTS_HOST_USERS
SQL Server Database
databases:
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
databases:
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
BizTalkDTADb
BAMPrimaryImport
BAM_EVENT_WRITE
R SQL Server
BAMPrimaryImport
BizTalkMgmtDb
BizTalkMsgBoxDb
BizTalkRuleEngineDb
BizTalkDTADb
BAMPrimaryImport
Contains
HWS
Runtime
Account.
EDI
Subsystem
Users
Has access to the EDI database.
Contains
service
accounts for
BizTalk Base
EDI service.
BAM Portal
Users
Has access to BAM Portal Web site.
Everyone
group is used
for this role
by default.
EDI_ADMIN_USERS
SQL Server Database
Role in the
BizTalkEDIDb
57
Group
Group Description
Membership
SQL Server Roles or

Database Roles
Contains no
service
accounts.
BizTalk BAS
Web
Services
Group
Includes all non-interactive user accounts

under which BAS Web services run.
Contains
BAS
Management
Web Service
Account,
BAS
Publishing
Web Service
Account,
and BAS
Application
Pool
Account.
BizTalk BAS
Users
Has the fewest privileges necessary to

perform basic BAS tasks not requiring the
capability to configure business
processes (for example, read access to
partner profiles and agreements).
Contains no
service
accounts.
BizTalk BAS
Managers
Has higher privileges than BizTalk BAS

Users, including tasks to configure
business processes such as deploy and
activate partners and agreements.
Contains no
service
accounts.
BizTalk BAS Has complete privileges to perform all

Administrator BAS tasks and operations, including
s
administrative tasks such as Business
Activity Site repair and synchronization.
Contains
BAS Site
Owner.
BizTalk
SharePoint
Adapter
Enabled
Hosts
Contains
service
accounts for
the BizTalk
host instance
to be able to
call
SharePoint
Adapter.
Has access to Windows SharePoint

Services Adapter Web Service.
58
Group
Group Description
Membership
SQL Server Roles or

Database Roles
BAS
Enabled
Hosts
Has privileges to handle BAS parameters

through BAS Web services.
The default
BizTalk
Application
Users group
is used for
this role by
default.
User and Service Accounts Used In BizTalk Server

The 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
Enterpris
e 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 Users
Rule
Engine
Update
Service
Service account
used to run Rule
Engine Update
Service, which
receives
notifications to
deployment/undep
IIS_WPG
RE_HOST_USERS
SQL Server
BizTalkRuleEngineD
b
59
User
User Description
Group Affiliation
SQL Server Roles or

Database Roles
loyment policies
from the Rule
engine database.
BizTalk
Base
EDI
service
Service account
used to run
BizTalk Base EDI
service, which
processes EDI
documentations.
EDI Subsystem Users
HWS
Runtime
Account
Service account
used to run HWS
Messaging
components.
BizTalk Isolated Host Users
HWS
Web
Service
Account
Application pool
account used to
run HWS Web
Service.
IIS_WPG
In-Process BizTalk Host Groups hosting

the Base EDI adapter.
IIS_WPG
STS_WPG
STS_WPG
HWS_WS_USER
SQL Server
BizTalkMgmtDb
BizTalkDTADb
BizTalkHwsDb
BAM
Notificati
on
Services
User
Service account
SQLServer2005NotificationServicesUser$
used to run BAM
<ComputerName>
Notification
No group affiliation for SQL Server 2000.
Services, which
accesses the BAM
databases.
NSRunService SQL
Server Database
databases:
BAMAlertsApplicatio
n
BAMAlertsNSMain
BAM_ManagementN
SReader SQL
Server role for the
BAMPrimaryImport
BAM
Manage
ment
Web
Service
User
User account for

IIS_WPG
BAM Management
Web service
(BAMManagement
Service) to access
various BAM
resources. BAM
NSSubscriberAdmin
SQL Server
BAMAlertsApplicatio
n
60
User
User Description
Group Affiliation
SQL Server Roles or

Database Roles
Portal calls
BAMManagement
Service with the
user credentials
logged on the
BAM Portal to
manage alerts, get
BAM definition
XML and BAM
views.
BAMAlertsNSMain
BAM_Management
WS SQL Server role
for the
BAMPrimaryImport
BAM
Applicati
on Pool
Account
Application pool
account for
BAMAppPool,
which hosts BAM
Portal Web site.
IIS_WPG
BAS
Manage
ment
Web
Service
Account
User account for

BizTalk BAS Web Services Group
BAM Management BizTalk Server Administrators
Web service
STS_WPG
(BAMManagement
Service) to access
various BAM
resources. BAM
Portal calls
BAMManagement
Service to retrieve
information about
user credentials,
activities, views,
alerts, and
configuration
information. BAM
metadata is thus
secured by
restricting backend access to the
account used by
the BAM
Management Web
service logon.
BAS
User account used BizTalk BAS Web Services Group

61
User
User Description
Group Affiliation
SQL Server Roles or

Database Roles
Publishin
g Web
Service
Account
by the TPM
Publishing Web
Service
(TPPubWS) to
access the BizTalk
Management
database
TPPubWS
performs the tasks
for BizTalk BAS
Users, BizTalk
BAS Managers,
and BizTalk BAS
Administrators.
STS_WPG
BAS
Applicati
on Pool
Account
Application pool
account for BAS
web services
(TpmWSSAppPoo
l) which hosts
TPMgmtWs and
TPPubWs.
BizTalk BAS Web Services Group
BAS Site The site owner

Owner
and Administrator
of the SharePoint
Services Web site
used by BAS.
IIS_WPG
STS_WPG
BizTalk BAS Administrators
This account is set

during WSS
installation and
configuration prior
to BizTalk Server
being installed.
For more information about Windows groups and service accounts used in BizTalk Server 2006
R2, see "Windows Groups and User Accounts in BizTalk Server" in BizTalk Server 2006 R2 Help.
Appendix II: Databases Used by BizTalk Server

The following is the list of SQL Server databases used in BizTalk Server 2006 R2.
62
Data store name
Default database name
Volume
Growth
Description
SSO Database
SSODB
Low
Low
This Enterprise Single SignOn 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
This database is used by

the BizTalk Server engine
for routing, queuing,
instance management, and
a variety of other tasks.
Note
The Auto update
statistics option, the
Auto create
statistics option,
and the Parallelism
setting are
purposely turned off
in the SQL
Server 2000 or SQL
Server 2005
database instance
that hosts the
BizTalk Server 2006
R2
BizTalkMsgBoxDB
database. Do not
enable these
settings.
BizTalk Tracking BizTalkDTADb

Database
High
High
This database stores

business and health
monitoring data tracked by
the BizTalk Server tracking
engine.
Rule Engine
Database
Low
Low
This database is a
repository for policies, which
are sets of related rules and
BizTalkRuleEngineDb
63
Data store name
Volume
Growth
Description
vocabularies. Vocabularies
are collections of userfriendly, 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 is
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.
HWS
Administration
Database
BizTalkHWSDb
Low
Low
This database contains all

administration information
related to Human Workflow
Services (HWS).
BAM Primary
Import
Database
BAMPrimaryImport
Medium
Medium
This is the database where

BAM collects raw tracking
data.
BAM Archive
Database
BAMArchive
Medium
Medium
This database archives old

business activity data.
Create a BAM Archive
database to minimize 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
Services
Application
database
Medium
Medium
This database contains alert

information for BAM
notifications. For example,
when you create an alert
using the BAM portal,
64
Data store name
Volume
Growth
Description
entries are inserted in this

database specifying the
conditions and events to
which the alert pertains, as
well as other supporting
data items for the alert.
BAM
Notification
Services
Instance
database
BAMAlertsNSMain
Medium
Medium
This database contains

instance information
specifying how the
notification services connect
to the system that BAM is
monitoring.
Trading Partner
Management
Database
BizTalkMgmtDb
Low
Low
This database stores trading

partner data for Business
Activity Services (BAS).
List of SQL Server Analysis Services Databases

The following is the list of SQL Server Analysis Services databases used in BizTalk Server 2006
R2.
Data store name
Volume
Growth
Description
BizTalk Tracking
Analysis
Database
BizTalkAnalysisDB
Medium
Medium
This database
stores both
business and
health monitoring
online analytical
processing
(OLAP) cubes.
BAM Analysis
Database
BAMAnalysis
Medium
Medium
This database
contains Business
Activity
Monitoring (BAM)
OLAP cubes for
both online and
offline analysis.
Note
Using the BizTalk Tracking Analysis database with SQL Server 2005 Analysis Services is
not supported.
65
List of Windows SharePoint Services Databases

The following is the list of SQL Server databases used by Windows SharePoint Services.
Data store name
Default database
Volume
Growth
Description
name
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.
Appendix III: How to Install SQL Server 2000

Follow these steps if you plan to install SQL Server 2000 instead of SQL Server 2005 during Task
2:Install SQL Server 2005 or SQL Server 2000 of the installation process.
Step 1: Install SQL Server 2000

To install SQL Server 2000
1. Insert the SQL Server 2000 installation disk into the CD-ROM drive. If the SQL Server
2000 Setup page does not appear, double-click autorun.exe located in the root of the
installation CD.
2. Select SQL Server 2000 Components.
3. Select Install Database Server.
Note
You may see a warning stating that SQL Server 2000 SP2 and earlier versions
are not supported. Click Continue.
5. On the Computer Name screen, leave the defaults, and then click Next.
6. On the Installation Selection screen, ensure that Create a new instance of SQL
Server, or install Client Tools is selected, and then click Next.
7. On the User Information screen, click Next.
8. On the Software License Agreement screen, click Yes.
9. On the CD-Key screen, enter your CD key, and then click Next.
66
10. On the Installation Definition screen, ensure that Server and Client Tools are
selected, and then click Next.
On the Instance Name screen, ensure that Default is selected, and then click Next.
11. On the Setup Type screen, ensure that Typical is selected, and then click Next.
12. On the Services Accounts screen, ensure that Use the same account for each
service. Auto start SQL Server Service is selected, enter a local account or domain
account and password, and then click Next.
13. On the Authentication Mode screen, select Windows Authentication, and then click
Next.
14. On the Start Copying Files screen, click Next.
15. On the Choose Licensing Mode screen, under Licensing Mode, select the type of
licensing you have, and then click Continue.
16. On the Setup Complete screen, click Finish.
Step 2: Install SQL Server 2000 Analysis Services

Note
You do not need to complete this step if you installed SQL Server 2005.
In the following procedure you install SQL Server 2000 Analysis Services. SQL Server 2000
Analysis Services is the OLAP services component that enables you to build multidimensional
cubes and provide application programs with access to the cubes.
SQL Server Analysis Services is optional for a BizTalk Server 2006 R2 installation. It is required
only if you want to use Health and Activity Tracking (HAT) or Business Activity Monitoring (BAM).
To install SQL Server 2000 Analysis Services
1. Insert the SQL Server 2000 installation disk into the CD-ROM drive. If the SQL Server
2000 Setup page does not appear, double-click autorun.exe located in the root of the
installation CD.
2. Select SQL Server 2000 Components.
3. Select Install Analysis Services.
Note
You may see a warning stating that SQL Server 2000 Analysis Services SP2 and
earlier is not supported. Click Continue.
6. On the Select Components screen, leave the defaults selected, and then click Next.
7. On the Data Folder Location screen, click Next.
8. On the Select Program Folder screen, click Next.
67
Step 3: Install SQL Server 2000 Service Pack 4

Note
In the following procedure you install SQL Server 2000 Service Pack 4. SQL Server 2000 Service
Pack 4 (SP4) addresses specific issues discovered in SQL Server 2000 since it was released.
SP4 is required for an installation of BizTalk Server 2006 R2.
To install SQL Server 2000 Service Pack 4
2. On the Microsoft SQL Server 2000 Service Pack 4 download page, select your
download language, and then click Go.
3. On the download page, scroll to the bottom, click SQL2000-KB884525-SP4-x86.EXE,
and then save the file to a location on your hard disk.
4. Locate the package you just downloaded and double-click it.
5. Extract the files to C:\sql2ksp4.
6. Browse to C:\sql2ksp4 and double-click setup.bat.
8. On the Software License Agreement screen, read the license agreement, and then click
Yes.
9. On the Instance Name screen, click Next.
10. On the Connect to Server screen, ensure that you select The Windows account
information I use to log on to my computer with (Windows authentication), and then
click Next.
Note
You may see the SA Password Warning dialog box if it detects a blank
password for the sa logon. Although you can continue your installation with a
blank password for the sa logon by explicitly choosing to ignore the
recommendation and continue Setup, a blank password poses a security risk and
is not recommended. This dialog box is displayed regardless of the
authentication mode you use.
11. On the Backward Compatibility Checklist screen, select Upgrade Microsoft Search
and apply SQL Server 2000 SP4 (required), and then click Continue.
Note
Depending on your configuration, this screen may not appear.
12. On the Error reporting screen, click OK.
13. On the Start Copying Files screen, click Next.
Note
At the end of the file copy process, a message appears stating that you should
68
back up your master and msdb databases. Click OK.

Step 4: Install SQL Server 2000 Analysis Services Service Pack 4

Note
In the following procedure you install SQL Server 2000 Analysis Services Service Pack 4. SQL
Server 2000 Analysis Services Service Pack 4 (SP4) addresses specific issues discovered in
SQL Server 2000 Analysis Services since its release date. SP4 is required for an installation of
To install SQL Server 2000 Analysis Services Service Pack 4
Note
This page contains instructions and service packs for x86 32-bit, x64 64-bit and
Itanium-based (IA-64) systems. The following steps reference the 32-bit versions
but you should follow the instructions on the download page to select the
download that is appropriate for your system.
2. On the Microsoft SQL Server 2000 Service Pack 4 download page, select your
download language, and then click Change.
3. On the download page, scroll to the bottom, click SQL2000.AS-KB884525-SP4x86.EXE, and then save the file to a location on your hard disk.
4. Locate the package you just downloaded and double-click SQL2000.AS-KB884525-SP4x86.EXE.
5. Extract the files to C:\sql2ksp4.
6. Browse to C:\sql2ksp4\msolap\install and double-click setup.exe.
9. On the Error reporting screen, click OK.
Note
Restart your computer at the end of the installation.
Step 5: Install SQL Server Notification Services 2.0 with Service Pack 1
Note
This is required only if you want to use Business Activity Monitoring (BAM) Alerts.
69
Note
You are required to install SQLXML 3.0 with Service Pack 3 before you install SQL Server
Notification Services 2.0 with Service Pack 1.
Note
In the following procedure you start the SQL Server services. The SQL Server services must be
running before you install SQL Server Notification Services 2.0 with Service Pack 1.
To start SQL Server Services
1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click
Service Manager.
2. Under Services, select SQL Server, and then click Start/Continue.
3. Under Services, select SQL Server Agent, and then click Start/Continue.
4. Close SQL Server Service Manager.
In the following procedure you install SQL Server Notification Services 2.0 with Service Pack 1.
Microsoft SQL Server Notification Services 2.0 with Service Pack 1 provides organizations with a
platform to build scalable notification applications that generate messages customized to meet
their users' specific information requirements. SQL Server Notification Services is optional for a
BizTalk Server 2006 R2 installation. It is required only if you want to use Business Activity
Monitoring (BAM) Alerts.
To install SQL Server Notification Services 2.0 with Service Pack 1
2. On the Notification Services 2.0 Service Pack 1 download page, under Enterprise
Edition, select your download language, and then click Go.
Note
Optionally, you can install Standard Edition.
3. Download and save MSSQLNS20SP1.Ent.exe to a location on your hard disk.
4. Double-click MSSQLNS20SP1.Ent.exe.
6. On the License Agreement screen, select I accept the terms in the license
agreement, and then click Next.
7. On the Customer information screen, type your user name and organization, select
Anyone who uses this computer (all users), and then click Next.
8. On the Custom Setup screen, ensure that all features are selected to be installed, and
then click Next.
Note
At a minimum you must install Engine Components, Client Components, and
70
Database Components on the computer where BAM alerts are configured.

9. On the Database Components Setup screen, select your SQL server, and then click
Next.
10. On the SQL Server Login information screen, select Windows Authentication, and
then click Next.
11. On the Ready to Install the Program screen, click Install.
12. On the Installation Wizard Completed screen, click Finish.
13. Browse to http://go.microsoft.com/fwlink/?LinkId=59065. The KB article provides links to
download a "hotfix" update to SQL Server 2000 Notification Services.
14. Download and save the hotfix for Notification Services 2.0 to your local hard disk.
15. Double-click the package you just downloaded.
16. Click Run.
17. On the License Agreement screen, select I accept the terms in the license
agreement, and then click Update.
18. Click Finish.
Appendix IV: Localization Version and Cross-Language Support

Localization Version
BizTalk Server 2006 R2 is available in the following languages:
English
Japanese
German
French
Spanish
Italian
Korean
Simplified Chinese
Traditional Chinese
Cross-Language Support
BizTalk Server 2006 R2 provides the following cross-language support:
The English-language version of BizTalk Server 2006 R2 is supported on all localized

versions of supported operating systems.
Localized versions of BizTalk Server 2006 R2 are supported on localized operating systems
that are the same language as the localized BizTalk Server version.
71
Installing the English-language version of Visual Studio 2005 is supported on all localized
versions of BizTalk Server. You can install a localized version of Visual Studio 2005 if it is the
same language as the localized BizTalk Server version.
Localized versions of BizTalk Server 2006 R2 are also supported on English-language versions of
supported operating systems through the use of Windows Multilingual User Interface Pack (MUI)
settings. You must verify certain operating system settings before installing a localized version of
BizTalk Server 2006 R2 on a server that is running an English-language operating system with a
non-English MUI setting. You must verify that the following operating system settings match the
language of the localized BizTalk Server to be installed:
The operating system user interface setting
The operating system user locale setting
The system locale setting
The 64-bit editions of Windows Server 2003 are only available in English or Japanese language
versions. Support for localized versions of BizTalk Server on the English language version of 64Bit Windows is provided using MUI, as described above.
Appendix V: Redistributable CAB Files

BizTalk Server relies on diverse products and technologies to provide essential services and
features. This software will be installed on your computer during the installation of BizTalk Server
if it is not already present. Setup gives you the option of downloading software prerequisites from
the Web or extracting them from CAB files that you download before running setup.
Important
You cannot use CAB files from previous versions of BizTalk Server to install BizTalk
Server 2006 R2, including CAB files intended for BizTalk Server 2006 and those intended
for beta versions of BizTalk Server 2006 R2. To ensure that you have the correct CAB file,
please download the latest version from the links given below.
Note
You cannot download the CAB files through a Telnet session.
Each CAB file contains localized versions of the following software:
Microsoft Office 2003 Web Components Version 4
Microsoft Data Access Components 2.8 Service Pack 1
Microsoft XML Core Services 3.0 SP7
Microsoft XML Core Services 6.0
SQLXML 3.0 SP3
ADOMD.NET 8.0
ADOMD.Net-KB893091-v8.00.0991-x86.EXE
ADOMD.NET 9.0
72
CAB Files for Windows Server 2003 (32-Bit Editions)

The following table provides the locations of the localized CAB files for BizTalk Server 2006 R2
running on 32-bit Windows Server 2003.
Language
Link
CN
DE
EN
ES
FR
IT
JA
KO
TW
CAB Files for Windows Server 2003 (64-Bit Editions)

The following table provides the locations of the localized CAB files for BizTalk Server 2006 R2
running on 64-bit editions of Windows Server 2003.
Language
Link
CN
DE
EN
ES
FR
IT
JA
KO
TW
73
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, Excel,
InfoPath, Internet Explorer, SharePoint, Visio, Visual C#, and Visual Studio 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.
74

Installing and Configuring BizTalk Server 2006 R2 On Windows Server 2003

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Installing and Configuring BizTalk Server 2006 R2 On Windows Server 2003

Загружено:

Авторское право:

Доступные форматы

Installing and Configuring BizTalk Server

2006 R2 on Windows Server 2003

Configure ASP.NET 2.0 to Run In 64-Bit Mode On 64-Bit Windows Editions..................35

Installing and Configuring BizTalk Server

What's New and Changed in This Document

Appendix III: How To Install SQL Server 2000

d. Appendix IV: Localization Version and Cross-Language Support

5. Revised the Windows SharePoint Services 2.0 configuration procedure.

Known Issues in the Installation of BizTalk

BizTalk Server 2006 R2 Installation Guide Contains Incorrect Links to

BizTalk Server Installation Creates SQL Server Objects on the Primary

"Error when downloading BtsRedist.cab" when Downloading Simplified

Setup Fails When Attempting to Install SQLXML 3.0 SP3

About the Installation Process

Step 1: Install Windows Server 2003 with

After installing Windows, you must be

Step 2: Install critical updates for Windows.

Install any high priority updates listed at the

Step 3: Install Internet Information

Enable ASP.NET 2.0.

Enable ASP.NET 32-bit mode on 64-bit

Step 4: Install Microsoft Office Excel 2003

and Microsoft Office InfoPath 2003 with Office

Install using default settings.

Step 5: Install Visual Studio 2005.

Install Microsoft C# and the .NET

Step 6: Install SQL Server 2005 with Service

Install using default settings.

Step 7: Install and configure Microsoft

Installation type must be Server Farm; this

Windows SharePoint Services must be

Windows SharePoint Services 3.0 and

Side-by-side installation of both Windows

For more information about the versions of

Step 8: Extend default Web site as a virtual

Select NTLM for the security type. Kerberos

Step 9: Create a network share for Business

Create a share named Alerts.

Give Everyone Change permissions to this

Computer and processor

A computer with an Intel Pentium-compatible

1 GHz or higher for single processors

900 MHz or higher for double processors

700 MHz or higher for quad processors

Hyper-Threading Technology (HT Technology)

only one socket is considered one

1 GB of RAM; 2 GB or more recommended.

10 GB of available hard disk space for a

disk performance rather than CPU

CD-ROM or DVD-ROM drive

Windows Server 2003-compatible VGA or

Network adapter card, and Microsoft mouse or

Windows Server 2003 Datacenter Edition,

Windows Server 2003 R2 Datacenter Edition,

BizTalk Server requires IIS for the following

SQL Server 2005 with Service Pack 2, or SQL

Windows SharePoint Services adapter

Secure Sockets Layer (SSL) encryption

Business Activity Services (BAS)

Human Workflow Services (HWS)

BizTalk Server supports all Microsoft SQL

Microsoft SQL Server 2000 Analysis Services