Tutorial 2: Performing BizTalk Server Administration Tasks

This is the second part of the BizTalk Server 2006 administration tutorials. In Tutorial 1: Configuring a Multi-Server Environment, you configured a multi-server BizTalk Server environment. In this tutorial, you will practice basic administration tasks based on that environment.

Note the following requirements before you begin:

You will go through the following steps to prepare for this tutorial:

  • Creating a domain user account for BizTalk Server administrator.

  • Making the domain BizTalk Server administrator account the local administrator of the BizTalk Servers.

  • Installing the tutorial files.

Creating a Domain User Account for BizTalk Server Administrator

In this step, you create the domain user account that you will use as a BizTalk Server administrator in this tutorial. This account must be a member of the BizTalk Server Administrators (Contoso\BizTalk Server Administrators) domain group. You also need to make this account a member of the SSO Administrators (Contoso\SSO Administrators) domain group to be able to add BizTalk Server host instances, and assign the SQL Server sysadmin role to create new BizTalk Server hosts. You will add host instances and create hosts in Lesson 2: Scaling Out Applications.

To create a BizTalk Server administrator account
  1. Log on to ContosoDC as the domain administrator. The user name is Contoso\Administrator and the password is pass@word1.

  2. Click Start, point to All Programs, point to Administrative Tools, and then click Active Directory Users and Computers.

  3. If it is not already expanded, click the plus sign (+) to expand the Contoso.com domain.

  4. Right-click Users, point to New, and then click User.

  5. From New Object - User, enter the following values, and then click Next.


    First name


    Last name


    User logon name


  6. From New Object - User, enter the following values, and then click Next.




    Confirm password


    User must change password at next logon


    User cannot change password


    Password never expires


    Account is disabled


  7. Click Finish.

To add Contoso\BTAdministator to the BizTalk Server Administrators group and the SSO Administrators group
  1. From Active Directory Users and Computers, in the left pane, expand contoso.com, and then expand Users.

  2. In the details pane, right-click BizTalk Administrator, and then click Add to a group.

  3. From Select Group, in Enter the object name to select, type BizTalk Server Administrators, and then click OK.

  4. In the details pane, right-click BizTalk Administrator, and then click Add to a group.

  5. From Select Group, in Enter the object name to select, type BizTalk Server Administrators, and then click OK.

  6. Click OK to confirm.

  7. Repeat steps 2 through 6 to add Contoso\BTAdministrator to the Contoso\SSO Administrators group.

To assign Contoso\BTAdministrator the SQL Server sysadmin role
  1. Log on to ContosoSQL1 or ContosoSQL2 as Contoso\BTInstaller. The password is pass@word1.

  2. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  3. From Connect to Server, verify the Server name is CONTOSOSQL1, and then click Connect.

  4. In the left pane, expand Security, and then expand Server Roles.

  5. In the left pane, double-click sysadmin.

  6. From Server Role Properties – sysadmin, click Add.

  7. In Enter the object names to select, type Contoso\BizTalk Server Administrators, and then click OK.

  8. Click OK.

Adding the BizTalk Server Administrator to the Local Administrators Group of the BizTalk Servers

Contoso\BTAdministrator must be a member of the BizTalk Server local administrators group to be able to deploy BizTalk Server applications.

To make Contoso\BTAdministrator a local administrator on the BizTalk Servers
  1. Log on to ContosoBTS1a as the local administrator.

  2. Click Start, right-click My Computer, and then click Manage.

  3. From Computer Management, expand System Tools, expand Local Users and Groups, and then click Groups.

  4. From the Groups list, right-click Administrators, and then click Add to Group.

  5. From Administrators Properties, click Add.

  6. From Select Users, Computers, or Groups, enter the following values, and then click OK.


    Select this object type

    Users or Groups

    From this location


    Enter the object name to select


  7. From Enter Network Password, enter the following values, and then click OK.


    User name




  8. From Administrator Properties, click OK.

  9. Log off ContosoBTS1a\administrator from ContosoBTS1a.

  10. Repeat the same steps to make Contoso\BTAdministrator as the local administrator on ContosoBTS1b.

Installing the Tutorial Files.

The tutorial files create the folder structure needed for this tutorial, the Microsoft® Windows® Installer (MSI) packages used for BizTalk Server application deployment, and the BizTalk Server application solution files as the references.

To install the tutorial files
  1. Download the tutorial files from http://go.microsoft.com/fwlink/?LinkID=118355.

  2. Run the installer to extract the files to the C:\ folder on ContosoBTS1a.

BizTalk Server makes it easy for integrating applications, and the virtual design tool makes it easy to create workflow applications. However, BizTalk Server administration is a specialized job role. It requires you to have in-depth knowledge of BizTalk Server, for example, how BizTalk Server processes messages, what is the message lifecycle, what is the database infrastructure. It also requires you to have a thorough understanding of the BizTalk Server solution you are managing.

Understanding the BizTalk Server Message Flow

BizTalk Server serves as a hub among other applications and integrates those applications. Adapters are used to connect other software to BizTalk Server. An adapter is an implementation of a communication mechanism, such as a particular protocol. BizTalk Server provides a series of adapters; it also provides the frameworks for developing custom adapters.

In addition to connecting different systems, you can also use BizTalk Server to define and execute business processes. The BizTalk Server engine uses orchestrations to define the logics of these business processes.

In between receiving/sending messages using adapters, and the orchestration process, messages are saved into the MessageBox database. One of the advantages is to be able to scale out a BizTalk solution into multiple BizTalk Servers.

Understanding the EAISolution BizTalk Server Application

This tutorial provides a BizTalk Server application that you can use to practice deployment and scaling-out applications. The BizTalk Server application is based on BizTalk Server 2006 Tutorial 1 at http://go.microsoft.com/fwlink/?LinkId=130151. It is an enterprise application integration (EAI) scenario which integrates a warehouse system and a ERP system for order request processing. As a BizTalk Server administrator, you must understand the basic ideas of the business process the application is trying to manage.

The basic document flow is an order request XML file is received from the warehouse system. Based on the Quantity field inside the file, the order is either forwarded to the ERP system or a new order decline file is generated and sent back to the warehouse system. The following is a screen capture of the orchestration which illustrates the workflow:


A Suspend shape is added after the Receive shape. It helps to explore more BizTalk Server features in this tutorial.

To simulate the ERP system and the warehouse system, the following folder structure is needed on ContosoBTS1a and ContosoBTS1b:




This is the folder where the warehouse system drops the order requests files, and that is the folder where BizTalk Server uses the file adapter to pick up the files.


This is the folder where BizTalk Server drop the order request decline documents.


This is the folder where BizTalk Server forwards the order request documents to.

There are two types of documents involved. One is the order request message and the other is the order decline message. The following is a screenshot of the map. The map shows the two schemas and the map itself:


The EAI solution includes two .NET assemblies. EAIOrchestration contains the orchestration; EAISchemas contains the schemas and the map.

Community Additions