There are many things to consider when planning this type of installation. The network infrastructure already exists, and BizTalk Server must coexist with other network applications. This guide describes some of the considerations that apply to the various parts of a BizTalk Server installation in a basic multi-computer environment. This information will help you plan the installation and configuration of BizTalk Server 2010, applications, and components on which it depends.
📝 One-Minute Brief
This is the first part of a comprehensive guide on installing Microsoft BizTalk Server 2010 in a multi-computer environment (remote SQL Server). It outlines a real-world scenario involving a Domain Controller, a SQL Server machine, and a BizTalk Server machine, focusing on infrastructure planning, network restrictions, and the components included in a full production-like installation.
This article explains how to install Microsoft BizTalk Server 2010 on a basic multi-computer (or basic multi-server), i.e., installation of BizTalk Server with a remote SQL Server (1 SQL Server and 1 BizTalk Server), and will be based on the infrastructure and needs of one of my customers, who asked me to write about this.
Some considerations on the scenario:
- The servers are in the same domain.
- They are in different networks with limited access to machines (network restriction)
- So we have to request access to different ports for the communication between the two machines.
Because this scenario is hard to emulate, I will use firewalls in both machines to emulate network access
There will be 3 virtual servers:
- 1 Domain controller
- 1 Virtual Machine to host SQL Server
- Windows Server 2008 R2
- SQL Server 2008 R2 Standard Edition
- 1 Virtual Machine to host BizTalk Server.
- Windows Server 2008 R2
- BizTalk Server 2010 Development Edition
In this scenario, I will perform a full installation, with the exception of the SharePoint Adapter, of Microsoft BizTalk Server 2010, emulating a production environment. The following components will be installed:
- Enterprise Single Sign-On (SSO).
- BizTalk Group.
- BizTalk Runtime.
- Business Rule Engine.
- BAM Tools and Alerts.
- BAM Portal.
- BizTalk EDI/AS2 Runtime
- Microsoft BizTalk Adapters
And we assume that all machines are already installed with the operating system and the latest critical Windows updates from Microsoft. Another presumption is that the domain controller is already installed and configured (this article will not explain this step)
Related Links
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: The need for a Domain Controller – Windows Groups and Service Accounts (Part 2)
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing Computers for Installation – Important considerations before set up the servers (Part 3)
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing and Install SQL Server 2008 R2 machine (Part 4)
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing and install prerequisites on BizTalk Server 2010 machine (Part 5)
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Testing environment connectivity’s (Part 6)
- Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Install and configure BizTalk Server 2010 machine (Part 7)
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
