Installing and Configuring Microsoft BizTalk Serveron Windows Server 2003

Installing and Configuring Microsoft BizTalk Server 2006 on Windows Server 20034ContentsInstalling and Configuring Microsoft BizTalk Server 2006 on Windows Server 20035Known Issues5About the Installation Process5Overview5BizTalk Server2006 Features and Components6Considerations When Installing BizTalk Server 2006 on Windows Server 200310General Considerations10Considerations for Windows Group and Service Account10Considerations for Using SQL Server15SQL Server Remote Installed15Supported SQL Server Topologies15Supported Instances of SQL Server16Supported SQL Server Collations16List of Databases Used in BizTalk Server200618Considerations for Installing Commerce Server 2007 on the Same Computer21Considerations for Installing BizTalk Server on Domain Controllers21Localization Version and Cross-Language Support22Localization Version22Cross-Language Support22Hardware Requirements22Software Requirements23BizTalk Server2006 Software Requirements23Installation and Configuration Tasks27Task 1: Install Operating System27Step 1: Install Windows Server200327Step 2: Install Windows Server2003 Service Pack128Step 3: Apply Windows Updates28Task 2: Install Software Pre-requisites29Step 1: Install Internet Information Services6.029Step 2: Install Office Excel 2003 and InfoPath 2003 with Service Pack230Step 3: Install Visual Studio200531Step 4: Install SQL Server2000 or SQL Server200532Step 5: Install SQL Server2000 Analysis Services34Step 6: Install SQL Server2000 Service Pack435Step 7: Install SQL Server2000 Analysis Services Service Pack436Step 8: Install SQL Server Notification Services2.0 with Service Pack137Step 9: Install Windows SharePoint Services 2.0 with Service Pack239Task 3: Configure the Platform40Step 1: Configure Default Web Site for ASP.NET2.040Step 2: Configure Windows SharePoint Services40Step 3: Extend Default Web Site as a Virtual Server42Step 4: Disable SQL Server Shared Memory Protocol43Task 4: Install BizTalk Server200644Step 1: Install BizTalk Server200644Task 5: Configure BizTalk Server200646Step 1: Configure BizTalk Server200646Step 2 (Optional): Install Orchestration Designer for Business Analysts (ODBA)47Post-Installation Requirements48Silent Installation48Installing a Silent Installation of BizTalk Server 200648Uninstalling BizTalk Server200651Task 1: Uninstalling BizTalk Server2006 Runtime Components and Databases51Step 1: Uninstall BizTalk Server2006 Runtime Components52Step 2: Remove BAM Alerts Notification Services Instance52Step 3: Remove BizTalk Server2006 SQL Server Agent Jobs53Step 4: Remove BizTalk Server2006 SSIS or DTS Packages55Step 5: Remove BizTalk Server2006 SQL Server Databases55Step 6: Remove BizTalk Server2006 SQL Server Analysis Services Databases57Technical Appendix57Redistributable CAB Files57Installing and Configuring Microsoft BizTalk Server 2006 on Windows Server 2003Last updated: October 16, 2007This document provides hardware and software requirements and detailed instructions for installing and configuring Microsoft BizTalk Server2006 on computers running the 32-bit version of Microsoft Windows Server2003. For installing BizTalk Server2006 on Windows Server2003 x64 Editions, see Installing and Configuring Microsoft BizTalk Server2006 on 64-Bit Windows at Only the BizTalk Server2006 Enterprise and Developer editions support native 64-bit execution on 64-bit systems.Note To ensure that you are reading the most up-to-date information, download the latest version of the BizTalk Server2006 installation guide, at Note Before installing BizTalk Server2006, you must uninstall pre-release versions of Microsoft Visual Studio2005 and .NET Framework2.0. For information about uninstalling previous versions of Visual Studio2005, see Known IssuesBefore installing BizTalk Server2006, you should review this document, as well as the Microsoft BizTalk Server2006 Readme, which contains important, late breaking information about this release of BizTalk Server2006. For more information, see the readme file located at About the Installation ProcessThis section provides an overview of the BizTalk Server2006 installation process and the available features and components to install.OverviewThe basic installation process for BizTalk Server2006 is the same as for most Windows-based applications. The BizTalk Server Setup program calls Windows Installer to install BizTalk Server2006 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 a pre-downloaded CAB file. The CAB file contains the following software:Office2003 Web Components Microsoft Data Access Components(MDAC)2.8SP1 Microsoft XML Core Services(MSXML)3.0SP7Microsoft XML Core Services(MSXML)6.0SQLXML3.0SP3 Microsoft .NET Framework2.0ADOMD.NET8.0ADOMD.Net-KB893091-v8.00.0991-x86.EXEADOMD.NET9.0For the download locations of the CAB files, see Redistributable CAB Files.Note You cannot download the CAB files through a Telnet session.BizTalk Server2006 Features and ComponentsThe following table describes the available BizTalk Server2006 features and components that can be installed.ComponentDescriptionDocumentationSelecting the Documentation component installs the core documentation, tutorials, UI reference (F1 help), programmers reference, and usage instructions for the SDK samples and utilities.Server RuntimeSelecting the Server Runtime component installs the runtime services for BizTalk Server2006. These runtime services are an essential part of the BizTalk Server platform.Base EDI AdapterSelecting the Base EDI Adapter component installs the necessary software that enables BizTalk Server2006 to process documents in the Electronic Data Interchange (EDI) format.Portal ComponentsThe 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 ServicesBusiness Activity MonitoringHuman Workflow Web ServiceAdministrative ToolsSelecting the Administration Tools component installs the necessary software to administer BizTalk Server2006 on both the local machine and a remote server.Developer Tools and SDKSelecting the Developer Tools and SDK component installs samples and utilities that enable the rapid creation of BizTalk Server2006 solutions. This includes: SDK samples and supporting documentation, BizTalk Explorer, schema and map designers, and Microsoft Visual Studio2005 project templates. This component requires Visual Studio2005.Note The Developer Tools and SDK component cannot be installed on Visual Studio2005 Express Editions.Additional SoftwareAdditional Software is a set of components that enable deployment flexibility in BizTalk Server2006. This includes the following:Enterprise Single Sign-On Administration ModuleNote This feature requires Microsoft Management Console3.0 available at Enterprise Single Sign-On Master Secret ServerNote Enterprise Single Sign-On Master Secret Server is required in a BizTalk Server environment.Business Rules ComponentsMQSeries Agent Note IBM WebSphere MQ 5.3 with CSD 10 or higher or IBM WebSphere MQ 6.0 is required 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.Windows SharePoint Services Adapter Web ServiceNote .NET Framework2.0 must be installed prior to install this feature. This prerequisite is not enforced by BizTalk Server2006 setup program.Business Activity Monitoring (BAM) Alert Provider for SQL Notification ServicesBAM ClientBAM Event APIThe following table indicates the dependencies that you must install or update before installing BizTalk Server2006 based on the features you select.Note .NET Framework1.1 is only required when you install SQL Server Notification Services2.0 with Service Pack1 for BAM Alerts.Note Business Activity Services and Windows SharePoint Services Adapter Web Service are not available because Windows SharePoint Services2.0 is not supported on Windows 2000 and Windows XP.Note You only need to install the components listed in SQL 2000 group or SQL 2005 group for BizTalk Server2006 components.Note You only need to install IBM WebSphere MQ 5.3 with CSD 10 or IBM WebSphere MQ 6.0 for MQSeries Agent.Considerations When Installing BizTalk Server 2006 on Windows Server 2003When installing BizTalk Server2006 on Windows Server2003 consider the following:General ConsiderationsBizTalk Server is supported on x64-based 64-bit Windows Editions. Installation on 64-bit Windows is described in Installing and Configuring Microsoft BizTalk Server 2006 on 64-Bit Windows. The following general considerations apply to BizTalk Server2006 on 64-bit Windows operating systems:Only the BizTalk Server2006 Enterprise Edition, Developer Edition, and Evaluation Edition support native 64-bit execution (host instances) on 64-bit versions of Windows.The Setup Wizard (setup.exe) and Configuration Wizard (configuration.exe) are 32-bit processes on all platforms. The Setup Wizard will determine if it is being run on a 32-bit or 64-bit platform, then install the BizTalk Server components from the appropriate installation package for the platform.If you are using Microsoft Operations Manager (MOM) for monitoring the BizTalk Server2006 in your network environment, the TCP port 1270 must be open for the agent to connect to the MOM server.Installing and configuring BizTalk Server2006 in the workgroup environment on a single computer is supported. When performing such type of installation, SQL Server must be present at local and BizTalk Server2006 features and components are installed and configured at local machine.Installing BizTalk Server2006 using Terminal Server running in application mode is not supported. Refer to support article for more details.Considerations for Windows Group and Service AccountBizTalk Server2006 supports only name formats for service accounts and Windows groups.BizTalk Server supports only Active Directory domain groups and user accounts when you use multiple-computer configurations, including SQL Server. Domain groups include Domain Local Groups, Global Groups, and Universal Groups, which are supported in single-server and in multiple-computer environments. You must manually create all of the domain groups and accounts before you configure BizTalk Server.Note Domain Local Groups are supported only if BizTalk Server and SQL Server are both joined to the same domain and the log on user who configures BizTalk Server is also a member of the domain where the Domain Local Groups exist.The user running the BizTalk Server configuration must have the following rights:Administrator on the local machineSQL System Administrator rights on the SQL serverMember of the domain group used for the BizTalk Server Administrators group.Member of the domain group used for the SSO Administrators group.The following is a list of Windows Groups used in BizTalk Server2006:Role nameDefault Windows Group nameDescriptionSSO Administrator(s)SSO AdministratorsAdministrator of the Enterprise Single Sign-On (SSO) Service.SSO Affiliate Administrator(s)SSO Affiliate AdministratorsMust be able to create affiliate applications. The BizTalk Administrator must be a member of this group.BizTalk Administrators GroupBizTalk Server AdministratorsHave the least privileges necessary to perform administrative tasks in the Configuration Wizard and to administer the BizTalk Server environment after installation.BizTalk Operators GroupBizTalk Server OperatorsHave the least privileges necessary to perform tasks required for operating the BizTalk Server environment after installation.BizTalk Host Users GroupBizTalk Application UsersWindows group for accounts with access to the In-Process BizTalk Hosts (host processes in BizTalk Server).BizTalk Isolated Host Users GroupBizTalk Isolated Host UsersWindows group for accounts with access to the Isolated BizTalk Hosts (host processes not running on BizTalk Server, such as HTTP and SOAP).BizTalk Base EDI Users GroupEDI Subsystem UsersWindows group that has access to the EDI database.Note The BizTalk Base EDI Users Group must be a member of the BizTalk Host Users Group used to run the Base EDI adapter.BizTalk BAM Portal UsersEveryoneWindows group that has access to the BAM Portal.BizTalk SharePoint Adapter Enabled HostsSharePoint Enabled HostsWindows group that has permissions to call the Windows SharePoint Services Adapter Web services.BizTalk BAS Web Services GroupBizTalk BAS Web Services GroupFor non-interactive user accounts under which BAS Web services run.BizTalk BAS UsersBizTalk BAS UsersHas the least privileges necessary to perform basic tasks in BAS not requiring the capability to configure business processes (for example, read access to partner profiles and agreements).BizTalk BAS ManagersBizTalk BAS ManagersHas higher privileges than the BAS Users Group, including tasks to configure business processes such as deploy and activate partners and agreements.BizTalk BAS AdministratorsBizTalk BAS AdministratorsHas privileges to perform all tasks and operations in BAS including administrative tasks, such as Business Activity Site repair and synchronization.BAS Enabled HostsBizTalk Application UsersWindows group for accounts with access to the In-Process BizTalk Hosts for BAS.The following is a list of Services Accounts used in BizTalk Server2006:NameDescriptionEnterprise Single Sign-On ServiceService account name under which the Single Sign-On NT service should run.BizTalk Host Instance AccountService account with access to a specific In-Process BizTalk Host instance, an NT service.BizTalk Isolated Host Instance AccountService account with access to a specific Isolated BizTalk Host instance, an IIS Application Pool Identity.Rule Engine Update ServiceService account with access to Rule Engine Update Service, an NT service, to receive notification to deploy or undeploy rules and policies from the Rule Engine database.BizTalk Base EDI ServiceService account with access to BizTalk Base EDI Service, an NT service.HWS Runtime AccountService account that the Human Workflow Services runtime services run under, an IIS Application Pool Identity.HWS Web Service AccountService account that the Human Workflow Services Web services run under, an IIS Application Pool Identity.BAM Notification Services UserService account with access to SQL Server Notification Services Instance, an NT service.BAM Management Web Service UserService account that BAM Management Web service runs under.BAM Application Pool AccountService account that the BAM Management Service and the BAM Query Service run under, an IIS Application Pool Identity for BAM Portal.BAS Site OwnerService account that runs as the owner of a BAS site.BAS Management Web Service AccountService account that the BAS Management Web service runs under.BAS Publishing Web Service AccountService account that the Business Activity Publishing Web service runs under.BAS Application Pool AccountService account that the BAS SharePoint Services and Trading Partner Management Web services run under, an IIS Application Pool Identity.For more information about Windows Group and Service Accounts used in BizTalk Server2006, see Windows Group and User Accounts in BizTalk Server in BizTalk Server2006 Help.Considerations for Using SQL ServerSQL Server Remote InstalledBy default, network Distributed Transaction Coordinator (DTC) access and network COM+ access are disabled on Microsoft Windows Server2003. You can only use them locally. Before configuring BizTalk Server2006 in a multiple-computer environment, you must enable network DTC access and network COM+ access on all separate computers. To enable network DTC and network COM+ access, do the following:1.Click Start, point to Control Panel, and then click Add or Remove Programs.2.Click Add/Remove Windows Components.3.Select Application Server, and then click Details.4.Select Enable network DTC access and Enable network COM+ access, and then click OK.5.Click Next.6.Click Finish.7.Stop and then restart the Distributed Transaction Coordinator service.8.Stop and then restart Microsoft SQL Server and the other resource manager services that participate in the distributed transaction, such as Microsoft Message Queuing.The SQL client tool must be installed at the local computer when using remote SQL Server. The version of the SQL Client Tools on the local computer must match the version installed on the remote SQL Server.If you plan on using Analysis Services remotely, you must have the SQL Server OLAP client installed locally.The remote SQL server must be started during the configuration, and the TCP and UDP port numbers you specify during the SQL Server setup process must be open.Supported SQL Server TopologiesThe following are the supported configurations for using Microsoft SQL Server2000 and Microsoft SQL Server2005 with BizTalk Server2006:Location of SQL Server in relation to BizTalk Server2006SupportedLocal SQL Server2000 OnlyYesLocal SQL Server2005 OnlyYesRemote SQL Server2000 OnlyYesRemote SQL Server2005 OnlyYesRemote SQL Server2000 and Remote SQL Server2005 on the same machineYesNote This is only supported if all BizTalk Server databases are installed on the same version of SQL Server.Local SQL Server2000 and Local SQL Server2005 on the same machineNoLocal SQL Server2000 with BizTalk Server databases on a remote SQL Server2005 machineNoLocal SQL Server2005 with BizTalk Server databases on a remote SQL Server2000 machineNoSupported Instances of SQL ServerInstalling and configuring BizTalk Server2006 against SQL Server2000 and SQL Server2005 default instances and named instances are supported. Note Named instances of SQL Server2000 Analysis Services are not supported. You must use the default instance of SQL Server2000 Analysis Services during the configuration.Supported SQL Server CollationsThe following are the supported collations for using SQL Server2000 and SQL Server2005 with BizTalk Server2006.SQL Server2000 supports the following collations: Albanian_CI_ASArabic_CI_ASChinese_PRC_CI_ASChinese_Taiwan_Stroke_CI_ASCroatian_CI_ASCyrillic_General_CI_ASCzech_CI_ASDanish_Norwegian_CI_ASEstonian_CI_ASFinnish_Swedish_CI_ASFrench_CI_ASGreek_CI_ASHebrew_CI_ASHindi_CI_ASHungarian_CI_ASIcelandic_CI_ASJapanese_CI_ASKorean_Wansung_CI_ASLatin1_General_CI_ASLatvian_CI_ASLithuanian_CI_ASMacedonian_CI_ASMexican_Trad_Spanish_CI_ASModern_Spanish_CI_ASPolish_CI_ASRomanian_CI_ASSlovak_CI_ASSlovenian_CI_