This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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.
Microsoft, Active Directory, ActiveX, BizTalk, Excel, InfoPath, JScript, IntelliSense, Internet Explorer, MSDN, Outlook, PivotChart, PivotTable, PowerPoint, SharePoint, Tahoma, Visio, Visual Basic, Visual C++, Visual C#, Visual SourceSafe, Visual Studio, Win32, Windows, Windows NT, Windows PowerShell, Windows Server, Windows Server System, and Windows Server are trademarks of the Microsoft group of companies.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
All other trademarks are property of their respective owners.
Installing BizTalk Server 2010 on Windows 7 and Windows Vista 4
How to Use this Document 4
Checklist: Planning Your Installation 5
Choosing your BizTalk Server Features and Components 5
Feature Dependency Matrix 7
Hardware Requirements 8
Software Requirements 9
Considerations When Installing BizTalk Server 2010 11
Preparing Your Computer for Installation 12
Install Critical Windows Updates 12
Enable Internet Information Services 12
Install Microsoft Office Excel 2010 or 2007 13
Install Visual Studio 2010 14
Install SQL Server 2008 R2/ SP1 14
Install Prerequisites for MQSeries Agent 16
Install SQL Server 2005 Notification Services 16
Disable the Shared Memory Protocol 17
Join the Local Administrators Group 17
Configure the Application Event Log 18
Installing and Configuring BizTalk Server 18
Verify Your Installation 19
Configure BizTalk Server 20
Enable TCP/IP and Named Pipes 20
Enable DTC on the Local Host Server 21
Uninstalling BizTalk Server 22
Uninstall BizTalk Runtime Components 22
Uninstall Enterprise Single Sign-On 22
Remove All Remaining Components 23
Uninstallation Complete 25
Appendix A: Silent Installation 25
Appendix B: Redistributable CAB Files 28
Appendix C: Customer Experience Improvement Program in BizTalk Server 2010 30
Customer Experience Improvement Program 30
Installing BizTalk Server 2010 on Windows 7 and Windows Vista
Documentation Feedback and Updates
Microsoft values your feedback. To send feedback and comments about this topic to the documentation team, click here.
This document describes the process for installing and configuring Microsoft® BizTalk® Server on a single computer running Windows 7 or Windows® Vista.
We recommend that you read this entire document before beginning your installation. This is because BizTalk Server connects many disparate components both internal and external to your enterprise so information can flow smoothly and securely in many directions. While even the most basic single-server deployment relies on many variables, most real-world deployment scenarios extend much farther to include multiple servers and eventually clusters of both physical and virtual computers.
No two deployments of BizTalk Server are the same. Before you begin the installation process, gather information on the needs of your enterprise, and discuss the scope of your deployment with the IT Professionals, System Administrators, and Developers who will use BizTalk Server. By studying this Installation Guide and carefully analyzing the specific needs of your enterprise, you will eventually create your own deployment roadmap.
For information about installing BizTalk Server 2010 on multiple computers, see Installing BizTalk Server 2010 and BAM in a Multi-Computer Environment (http://go.microsoft.com/fwlink/?LinkID=191321).
You can also download and install the BizTalk Server Best Practices Analyzer (http://go.microsoft.com/fwlink/?LinkID=196491). The Best Practices Analyzer (BPA) examines a BizTalk Server deployment and generates a list of best practices issues it discovers. BPA performs configuration-level verification, by reading and reporting only, and uses the gathered data to determine whether best practices are being followed.
How to Use this Document
This guide is divided into the following four sections:
Introduction gives an overview of the installation process and tells what information you’ll need during the installation process. The section also lists important considerations regarding Windows® and SQL Server®.
Preparing your computer for installation walks you through installing and configuring all prerequisite software, and setting necessary permissions.
Installing and Configuring BizTalk Server walks you through installing and configuring BizTalk Server. The section includes procedures for determining whether your installation was successful.
A. Silent Installation lists commands and options for an unattended installation.
B. CAB Files links to the redistributable CAB files containing BizTalk Server prerequisites.
C. Customer Experience Improvement Program in BizTalk Server 2010 provides information about providing feedback to Microsoft about BizTalk Server 2010.
Below is a high-level glimpse of the installation process. Installation on a single computer usually takes 4-6 hours. Note that each of these steps must be carried out in the order shown, and that each step contains many variables relevant to your enterprise. All of these issues will be addressed in later sections of this guide.
Preparing your computer for installation
Install any critical updates for Windows
Enable Internet Information Services (IIS)
Install Microsoft Office Excel 2010/2007
Install Visual Studio® 2010
Install SQL Server 2008 R2/2008 SP1
Install SQL Server 2005 Notification Services (required only for BAM Alerts)
Install prerequisites for MQSeries Agent (required only for MQSeries Agent)
Install .Net Framework 4 and 3.5 SP1
Disable shared Memory Protocol
Join the local Administrators group
Configure the Application Event Log
*Only necessary if you are using the Windows SharePoint Services Adapter Web Service.
Enable TCP/IP and named pipes in the SQL Server Configuration Manager
Enable Microsoft Distributed Transaction Coordinator (MS DTC) on the Local Host Server (LHS)
Choosing your BizTalk Server Features and Components
Review this list of features and components before beginning your installation, and decide which ones you want to install. Items are listed here in the same order that they appear in the Setup program feature tree.
Documentation Core documentation, tutorials, UI reference (F1 Help), programmer’s reference, and usage instructions for the SDK samples and utilities.
Server Runtime The essential runtime services for BizTalk Server.
BizTalk EDI/AS2 Runtime Runtime services providing native support for Electronic Data Interchange (EDI) data exchange and Applicability Statement 2 (AS2) data transport messaging functionality.
Windows Communication Foundation (WCF) Adapter Runtime Adapters enabling BizTalk Server to communicate with WCF-based applications.
Portal Components Also known as Business Activity Monitoring (BAM), these are a set of services enabling users to communicate and collaborate, and also to configure and monitor business processes and workflows.
Administrative Tools Software necessary to administer BizTalk Server on both the local computer and a remote server.
Windows Communication Foundation (WCF) Administration Tools Administration services for WCF components.
Developer Tools and SDK Samples and utilities that enable the rapid creation of BizTalk Server 2010 solutions. This includes SDK samples and supporting documentation, BizTalk Explorer, schema and map designers, and Visual Studio project templates.
You must install this component if you plan to do any development work. The Visual Studio extensions used by BizTalk Server will not work without the Developer Tools and SDK component installed.
Additional Software The following components enable a more flexible BizTalk deployment:
Enterprise Single Sign-On (SSO) Administration Module: The interface for managing SSO Affiliate Applications and their mappings.
Enterprise Single Sign-On Master Secret Server: The SSO server that stores the master secret. All other SSO servers in the system get the master secret from this server. The Master Secret Server is required in a BizTalk Server environment.
Business Rules Components: Used for composing policies to be consumed by the Business Rules Engine.
MQSeries Agent: Provides communication between the BizTalk Adapter for MQSeries and MQSeries Server for Windows.
Windows SharePoint Services Adapter Web Service: Allows the Windows SharePoint Services Adapter to process incoming and outgoing documents through Windows SharePoint Services.
The following table shows the minimum hardware requirements for your BizTalk Server computer. In a production environment, the volume of traffic may dictate greater hardware requirements for your servers.
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 and dual-core processors are supported.
The 64-bit versions of BizTalk Server require a 64-bit operating system running on an x64-based system. Computers based on CPUs that are compatible with the AMD64 (x86-64) and Extended Memory 64-bit Technology (EM64T) processor architecture are considered x64-based systems.
BizTalk Server is not supported on Itanium-based systems.
10 GB of available hard disk space for a complete installation including the operating system and all prerequisite software. The hard disk must be NTFS formatted.
CD-ROM or DVD-ROM drive
Windows Server® 2003-compatible VGA or higher-resolution monitor set to 1024 x 768 pixels or greater resolution
Network adapter card, and Microsoft mouse or compatible pointing device
This page lists the software required for running BizTalk Server. You’ll be guided through installation steps for all of these prerequisites in a later section.
Microsoft Windows Can be either Windows 7, Windows Server 2008 R2, Windows Server 2008 SP2, Windows Vista® with Service Pack 2 (SP2).
Internet Information Services (IIS) Version 7.5 and 7.0 is supported. Provides a scalable Web application infrastructure.
Required for: EDI, BAM, WSS Adapter, and UDDI.
Microsoft Office Excel 2010 or 2007 Business Activity Monitoring (BAM) uses an Excel workbook to display a real-time view of business processes.
If you are using Microsoft Office Excel 2010, you must install Excel 2010 hotfix package – Knowledge Base article 2345338 (Description of the Excel 2010 hotfix package (excelc-x-none.msp, excel-x-none.msp): August 31, 2010).
BizTalk Server 2010 supports only 32-bit version of Microsoft Office 2010.
Required for: BAM.
Microsoft .NET Framework 4 and .NET Framework 3.5 with Service Pack 1 (SP1) The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default.
The Microsoft .NET Framework 3.5 SP1 (formerly WinFX), is the new managed code programming model for Windows. It combines .NET Framework 2.0 with four new technologies: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Windows CardSpace (WCS, formerly “InfoCard”).
Required for: All BizTalk Server managed components.
Microsoft Visual Studio 2010 Provides a development environment for building applications that target any device and integrate with any platform. Professional Edition is recommended, but Standard and Team System are also supported.
Required for: BizTalk Server Developer Tools and SDK component.
SQL Server 2008 R2/2008 SP1 A relational database server for processing high volumes of data. For optimal performance, we recommend SQL Server 2008 R2/2008 SP1 Enterprise Edition. In order to fully use the BizTalk Server 2010 SDK, or deploy BizTalk Server applications from a Visual Studio development environment, you must also install the SQL Server Development Tools.
BAM real-time aggregation (RTA) is not supported in SQL Server 2008 R2/2008 SP1 Standard Edition. In order to use BAM RTA, you must install SQL Server 2008 R2/2008 SP1 Enterprise Edition.
Using SQL Server Express Edition in a production environment is not recommended. The Express edition does not include certain features needed by BizTalk Server.
BizTalk Server supports all case-sensitive and case-insensitive SQL Server collations except for binary collations. Binary collations are not supported.
Required for: BizTalk Server Runtime, EDI, and BAM.
SQL Server 2005 Notification Services Enables the use of BAM Alerts. Note that this SQL Server 2005 feature is not included in SQL Server 2008 R2/2008 SP1, and must be downloaded separately.
Required for: BAM Alerts.
SQLXML 4.0 with Service Pack 1 Enables XML support for your SQL Server database and allows developers to bridge the gap between XML and relational data. You can create an XML view of your existing relational data and work with it as if it were an XML file. To install SQLXML 4.0 SP1, see Microsoft SQL Server 2008 Feature Pack (http://go.microsoft.com/fwlink/?LinkID=189325).
Considerations When Installing BizTalk Server 2010
You should understand the following before beginning your installation:
Account names You should use the default account names whenever possible. The BizTalk Server setup program automatically configures installed components to use the default accounts. While using the default names simplifies setup and configuration, 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. If you must change the names, note that BizTalk Server supports only <NetBIOS domain name>\<user> name formats for service accounts and Windows groups.
Account names with BAM Management Web Service BizTalk Server does not support use of either built-in accounts or accounts without passwords for the BAM Management Web Service User. This is because the web service accesses the BizTalk database, and such accounts may represent a security threat.
Configuring BizTalk Server with such accounts may appear to succeed, but the BAM Management Web Service will fail.
Note that use of such accounts for the BAM Application pool is supported.
BizTalk Assembly Viewer Use of the BizTalk Assembly viewer is not supported on a 64-bit platform.
Install and Uninstall Uninstalling BizTalk Server is fully supported. However it requires manually deleting a number of databases which can be complicated and time consuming. If you are installing BizTalk Server as a developer or evaluator, consider installing on a virtual computer. This way, if you need to reinstall, you can easily roll back to a preset checkpoint without having to go through the uninstall process.
32-bit and 64-bit computers 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 32-bit and 64-bit installations. Differences between them are noted in the instructions to follow.
Workgroups Installing and configuring BizTalk Server in the workgroup environment on a single computer is supported. SQL Server and BizTalk Server features and components are installed and configured on the same computer.
Terminal Server Installing BizTalk Server using Terminal Server running in application mode is not supported. For more information, see the support article at http://go.microsoft.com/fwlink/?LinkId=88092.
Bam Portal If the BAM portal is configured on a website used by applications that are running .Net Framework 2.0 then you must host the BAM portal on a new website. To add a new website see Create a Web Site (IIS 7) (http://go.microsoft.com/fwlink/?LinkID=196470). After creating the new website, do these steps:
1. Open BizTalk Server 2010 Configuration.
2. Configure the BAM portal by selecting the new website from the BAM Portal Web Site list.