Install BizTalk Server 2013 and 2013 R2
Lists the steps to install BizTalk Server.
Before you get started
Account names – Use the default account names whenever possible. The BizTalk Server setup automatically enters the default accounts. If there are multiple BizTalk Server groups within the Domain, change the account names to avoid conflicts. If you change the names, BizTalk Server supports only <NetBIOS domain name>\<user> for service accounts and Windows groups.
Account names with BAM Management Web Service – BizTalk Server does not support built-in accounts or accounts without passwords for the BAM Management Web Service User. The web service accesses the BizTalk Server database and these accounts may suggest a security threat.
Configuring BizTalk Server with these typs of accounts may succeed, but the BAM Management Web Service fails. Built-in accounts or accounts without passwords can be used for the BAM Application pool.
BizTalk Assembly Viewer – Not supported on a 64-bit platform.
Install and Uninstall – Uninstalling BizTalk Server requires manually deleting the BizTalk Server databases. If you are installing BizTalk Server as a developer or evaluator, use a virtual machine. If you need to reinstall, you can easily roll back the virtual machine without having to uninstall and delete the databases.
32-bit and 64-bit computers – There are few differences when installing BizTalk Server on 32-bit or 64-bit computer. The installation and configuration covers 32-bit and 64-bit computers. Any differences are noted.
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. See KB 832027.
BAM Portal - If the BAM portal is configured on a website used by applications that are running .NET Framework 2.0, then create a new website for the BAM portal:
After creating the new website:
Open BizTalk Server Configuration.
Configure the BAM portal and select the new website from the BAM Portal Web Site list.
Community Additions: Read:
Install BizTalk Server
Close any open programs. Run the BizTalk Server installer as Administrator.
In Start, select Install Microsoft BizTalk Server.
In Customer Information, enter your user name, organization, product key, and then select Next.
In License Agreement, accept the license agreement, and select Next.
In Customer Experience Improvement Program, choose your participation preference, and then select Next.
In Component Installation, review the available components, and select the ones you want to install:
Feature Description 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. Note: You can select this only if you selected the Server Runtime feature. Windows Communication Foundation (WCF) Adapter Runtime Adapters enabling BizTalk Server to communicate with WCF-based applications. Note: You can select this only if you selected the Server Runtime feature. Portal Components Portal components are a set of features used by the business analysts to communicate, collaborate, and reach decisions using business data. Business Activity Monitoring Also known as BAM, these are a set of features that gives business users a real-time view of their heterogeneous business processes, thereby enabling them to take important business decisions. Note: You can select this only if you selected the Portal Components feature. Administrative Tools and Monitoring Components necessary to administer and monitor BizTalk Server on both the local computer and a remote server. Windows Communication Foundation (WCF) Administration Tools Selecting this feature installs the administrative services for WCF components. Note: You can select this only if you selected the Administrative Tools and Monitoring feature. Developer Tools and SDK Samples and utilities that enable rapid creation of BizTalk Server solutions. This includes SDK samples and supporting documentation, schema and map designers, and Visual Studio project templates. Important: 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 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 Deprecated. Using an IIS web service installed on the SharePoint Services computer, the SharePoint Services adapter processes incoming and outgoing documents through Microsoft SharePoint.
Recommendation: Do not install. By default, BizTalk Server uses the SharePoint Client Side Object Model (CSOM) Redistributable automatically installed on the BizTalk Server; as described at Appendix B: Install the Microsoft SharePoint Adapter.
BAM Alert Provider Configures BAM Alerts.
When using BAM Alerts with SQL Server 2014 or SQL Server 2012 SP1, you must configure the Database Mail feature. SQL Server Notification Services cannot be used.
BAM Client Client-side software enabling business users to work with BAM. BAM Eventing Interceptors for Windows Workflow Foundation and Windows Communication Foundation. Also includes the BAM Event API, which sends events to the BAM database from custom applications. Project Build Component A tool that enables you to build BizTalk Server solutions without using Visual Studio.
Accept the default installation location, or select Browse to enter another location to install BizTalk Server. Select Next.
If your computer is missing a prerequisite component, such as ADOMD.NET, Setup can install the redistributable prerequisites. You can either:
Select Automatically install the redistributable prerequisites from the web
Select Automatically install the redistributable prerequisites from a CAB file if you have downloaded the CAB file. If you select this, you can then browse to the location of the CAB file.
In Summary, verify that the components are correct. To enable auto-logon after a system reboot, select Set, and enter your logon information. Auto-logon is enabled only for reboots during setup, and is disabled when setup is complete.
Select Install to start the installation process.
In Microsoft Update Setup, choose your preference, and select Next.
In Installation Completed, uncheck Launch BizTalk Server Configuration, and then select Finish.
When you installed SQL Server, SQL Server setup granted your logged-on account System Administrator rights. Since these rights are also required for installing BizTalk Server, you must do one of the following:
Use the same account you used when you installed SQL Server.
Give the logged on account System Administrator rights.
After you download the self-extracting EXE for BizTalk Server, the installation guide is opened. The Setup.exe for BizTalk Server is at the same location as the installation guide.
Instead of installing BizTalk Server on a physical computer, you can o configure a Microsoft Azure virtual machine with a BizTalk Server image. See Configuring BizTalk Server on an Azure VM.
For the steps to install BizTalk Server using a command prompt, see Appendix A: Silent Installation.