Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)

Posted: January 3, 2012  |  Categories: Administration Advance Configurations BizTalk

There are many things to consider when planning this type of installation, often 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.

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 an infrastructure and needs of one of my customers, who asked me to write about this.

BizTalk infrastructure client scenario

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

BizTalk infrastructure my scenario

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 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

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *


Back to Top