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.

Some considerations on the scenario:

• The servers are in same domain.
• There 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 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)

Tags: BizTalk 2010 | Installation | Configuration

A very important difference between a single server and a multi-server installation is that the multi-server configuration requires you to use domain users and groups to run the various BizTalk services making having a domain controller a necessity. These domain accounts and groups are used for the security configuration of the BizTalk Server databases.

Because BizTalk and SQL are installed on a separate machine, the use of a domain user account is therefore a necessity so that the account can have access rights on both the BizTalk machine and the SQL Server machine.

Create Domain Groups and Users

The BizTalk setup procedure is not able to create the Windows Groups and Users on a Domain Controller, so on a multi-computer installation, BizTalk Windows Groups and Users must be created manually on the Domain Controller.

The following information will be useful in creating these groups and accounts.

• In a multicomputer environment, BizTalk Server supports only domain groups and domain service accounts.
• BizTalk Server 2010 supports only <NetBIOSDomainName>\<User> name formats for Windows groups and service accounts.
• BizTalk Server supports only Active Directory domain groups and user accounts in multi-computer configurations. Domain groups include Domain Local groups, Global groups, and Universal groups, which are supported in both single computer and multi-computer environments.
• Built-in accounts such as NT AUTHORITY\LOCAL SERVICE, NT AUTHORITY\NETWORK SERVICE, NT AUTHORITY\SERVICE, NT AUTHORITY\SYSTEM, and Everyone are not supported when you install and configure BizTalk Server 2010 in a multi-computer environment.
• For more information see Installing BizTalk Server 2010 and BAM in a Multi-Computer Environment manual.

Planning the use of a new Organizational Unit

To keep things tidy, we can place the BizTalk Users and Groups in an Organizational Unit (OU), it is a good practice to utilize a new Organizational Unit (OU) to create all groups, user accounts and service accounts that we will use in the configuration of BizTalk Server 2010.

OU are Active Directory containers into which you can place users, groups, computers, and other organizational units. By using them you can create containers within a domain that represent the hierarchical or logical structures within your organization.

To create a new OU follow these steps:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
• Right-click on the domain name and select NewàOrganizational Unit.

• Enter “BizTalk” as the name of the new ‘Organizational Unit Object”, Ensure to check “Protect container from accidental deletion” and press “OK”

Windows Groups Used In BizTalk Server

The following table lists the Windows groups and their membership used by BizTalk Server.

Note: must be created within the OU created earlier

To create a new Group follow these steps:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
• Select the OU create earlier: “BizTalk”. Right-click on the OU name and select NewàGroup.

• Enter the Group name of the new Group and ensure to select “Group scope” as “Domain local” or “Global” and “Group Type” as “Security”, press “OK”.
• Repeat all the steps for the remaining groups.

IIS_IUSRS Group

IIS_IUSRS is another group used by BizTalk Server 2010, however, unlike the previous groups we do not need to create this because it is a built-in group with access to all the necessary file and system resources so that an account, when added to this group, can seamlessly act as an application pool identity.

User and Service Accounts Used In BizTalk Server

The following table lists the Windows user or service accounts and group affiliations used by BizTalk Server.

Note: must be created within the OU created earlier

To create a new user follow these steps:

• Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
• Select the OU create earlier: “BizTalk”. Right-click on the OU name and select NewàUser.

• Enter the First and Last name and the User logon name of the new User. Press Next.
• Enter the password and password confirmation and ensure to select “Password never expires”, press “Next”.

• Repeat all the steps for the remaining groups.

Summary of users and Groups Affiliation

SQL Server Service Accounts

The following table lists the Windows service accounts used by SQL Server.

Note: must be created within the OU created earlier

Alternatively, you can create a single Domain Account to run this services (like sql-bts-service or srvc-sql-bts)

Depending on the selection that you made while installing SQL Server, you will have the services installed in your server.

SQL Server Database Services:

• SQL Server Agent
• Analysis Services
• Reporting Services
• Integration Services
• SQL Server Browser
• Full-text search
• SQL Server Active Directory Helper
• SQL Writer

You can configure you SQL Server related services either during the setup or after the installation using the SQL Server configuration Manager.

Types of startup accounts:

• Local User Account: This user account is created in your server where SQL Server is installed, this account does not have access to network resources.
• Local Service Account: This is a builtin windows account that is available for configuring services in windows. This account has permissions as same as accounts that are in the users group, thus it has limited access to the resources in the server. This account is not supported for SQL SERVER and AGENT services.
• Local System Account: This is a builtin windows account that is available for configuring services in windows. This is a highly privileged account that has access to all resources in the server with administrator rights.
• Network Service Account: This is a builtin windows account that is available for configuring services in windows. This has permissions to access resources in the network under the computer account.
• Domain Account: This account is a part of your domain that has access to network resources for which it is intended to have permission for. It is always advised to run SQL Server and related services under a domain account with minimum privilege need to run SQL Server and its related services.

Changing Service Accounts:

SQL Server service accounts can be configured either during installation or using SQL Server configuration Manager. The first one is part of the installation and can be configured during the step Instance Configuration. I would walk you through changing a service account using SQL Server Configuration Manager.

• Start -> Programs Microsoft SQL Server 2008 -> Configuration Tools -> SQL Configuration Manager
• Highlight a service in the right pane, right click for properties.

You can change the built-in account here, else if you would like to change it to a Local User account or a domain user account, choose option This Account to Ungray it and enter the credentials of a local or a domain user account.

Remember that you will need to restart the SQL Server and related services for the new Service account to take effect.

References

• Windows Groups and User Accounts in BizTalk Server
• Part 3: BizTalk High Availability Server Environment – SQL & BizTalk Active Directory Accounts
• Installing BizTalk Server 2010 and BAM in a Multi-Computer Environment manual
• SQL Server Service accounts

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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)

Tags: BizTalk 2010 | Installation | Configuration

There are some important considerations or suggestions, since these operations are not mandatory, that we can set before starting the installation and configuration of both servers.

Machine name

If your computer name is longer than 15 characters, BizTalk Server Configuration will not work.

Join the Local Administrators Group

To be able to install and configure BizTalk Server 2010, you have to log on the server using a Domain User who has Administrator rights on both the SQL Server and the BizTalk Server.

So the next step is to add BizTalk Server Administrators group to the Local Administrators Group in both machines.

To join to Local Administrators Group:

• Click ‘Start’, ‘Control Panel’, ‘Administrator Tools’, ‘Computer Management’, ‘Local Users and Groups, ‘Groups’
• Add you user account and BizTalk Server Administrators group to the ‘Administrators’ group

By default the Windows Builtin\Administrators group has the sysadmin SQL role on the SQL Server.

The user running the BizTalk Server configuration must belong…

The user running the BizTalk Server configuration must belong to the following user groups:

• To the Administrators group on the local computer
• To the System Administrators group on the SQL Server computer
• To the domain group used for the BizTalk Server Administrators group
• And to the domain group used for the SSO Administrators group

To simplify things put this user on the BizTalk Server Administrators group. After BizTalk Server is configured and installed, the user does not have to be part of the BizTalk Server Administrators group anymore.

By default the Windows Builtin\Administrators group has the sysadmin SQL role on the SQL Server.

Once SQL Server is installed, you will be able to check that by opening the SQL Server Management Console, go to “Security\Server Roles” and double click on the “sysadmin” role. The pop up window will show all the windows and SQL logins having the sysadmin role.

Install Critical Windows Updates

Before installing BizTalk Server or its prerequisites, make sure you have installed the latest critical Windows updates from Microsoft.

To install Windows updates:

• Click Start, point to All Programs, and then click Windows Update.
• Follow the directions on the Windows Update site.
• If prompted, restart your computer

Disable IPv6

IPv6 is the latest address protocol that will eventually replace IPv4. Windows Server 2008 R2 kept this protocol enabled by default, but it is also a fact that IPv6 is not yet common and many software, routers, modems, and other network equipment do not support it yet. So it may be a wise approach to disable it for now. Also by turning off it will facilitate the process of detecting which port certain application are listening.

IPv6 can be disabled either through the DisabledComponents registry value or through the check box for the Internet Protocol Version 6 (TCP/IPv6) component in the list of items on the Networking tab for the properties of connections in the Network Connections folder. The following figure shows an exemple:

Turn off Internet Explorer Enhanced Security Configuration

Internet Explorer Enhanced Security Configuration established a configuration for your server and for Microsoft Internet Explorer that decreases the exposure of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites may not display or perform as expected.

By default, Internet Explorer Enhanced Security Configuration is enabled on Windows Server 2008 R2 and can be configured through Server Manager.

To Turn off Internet Explorer Enhanced Security Configuration in Windows Server 2008 R2:

• Open the Server Manager by going to Start > Server Manager
• In the Server Manager browse to the Security Information section and click Configure IE ESC. In the figure below, IE ESC is located in the very lower right-hand corner of the window.

• A dialog box appears, letting Internet Explorer Enhanced Security Configuration be enabled/disable separately for normal users and administrators, turn off both.

Disable User Account Control

User Account Control (UAC) is a security component that allows an administrator to enter credentials during a non-administrator’s user session to perform occasional administrative tasks.

Whenever you need to configure a Windows Server 2008 R2 setting, even if you are logged on as the administrator – you need elevated privileges.  This is by design, and part of the fierce security initiative in Windows Server 2008.   Before you can complete any administrative task, the User Account Control manager pops-up with a ‘Continue’ message.

To Disable User Account Control (UAC):

• Click Start, and type “Change User Account Control Settings”

.NET Framework 3.5 SP1 requirement

The .NET Framework 3.5 SP1 (also referred to as .NET Framework 3.5.1) is a prerequisite for SQL Server 2008 R2, however you should install .NET Framework 3.5 SP1 on both machines (BizTalk Server and SQL Server).

In Windows Server 2008 R2, the .NET Framework is a feature and installing it is different when compared to older versions of Windows Operating System. In previous versions, one could either download the .NET Framework 3.5.1 install binaries from Microsoft download site or use the install binaries from of the SQL Server 2008 installation media. Starting with Windows Server 2008, the method of installing .NET Framework 3.5.1 has changed.

To install/enable .Net 3.5 SP1 on Windows Server 2008:

• Using PowerShell
  • Click the Start button in the lower left hand corner of the display.
  • Highlight All Programs and select Accessories
  • Expand Windows PowerShell and right click Windows PowerShell and select Run as administrator. Click Yes on the User Account Control box.
  • At the PowerShell command prompt, type the following commands, and then press ENTER after each command:
    • Import-Module ServerManager
    • Add-WindowsFeature as-net-framework

Turn Windows Firewall

In you scenarios I advise you to turn Windows Firewall off on both machines However as I explained earlier, I will use firewalls in both machines to emulate network access

To turn Windows Firewall off:

• Click Start, and type “Windows Firewall”

• Select “Turn Windows Firewall on or off” option
• And select the option “Turn off Windows Firewall (not recommended)” in all the three settings

Configure Microsoft Distributed Transaction Coordinator (MS DTC)

In Windows server 2008 R2 MSDTC is installed by default.

In order for BizTalk to run against its databases located on a remote SQL server, you will need to turn on MS DTC options (both on the SQL Server and BizTalk Server).

Configure MSDTC on BizTalk and SQL Servers:

• Click ‘Start’, ‘Run’, type ‘dcomcnfg’, and hit the ‘Enter’ key
• Under ‘Component Services’, ‘My Computer’, ‘Distributed Transaction Coordinator’, right-click ‘Local DTC’ and select ‘Properties’, click the ‘Security’ tab.
• Ensure that the ‘Network DTC Access’, ‘Allow Inbound’, ‘Allow Outbound’, and ‘No Authentication Required’ options are selected and all others are cleared.

• Click ‘OK’

• Click ‘Yes’

NOTE1: It is suggested that a minimum of 100 ports are set, between ports 1024 to 10000.

NOTE2: If you receive COM+ related events or errors because of this setting you can revert it later or increase the ports range accordingly.

References:

• Troubleshooting MSDTC issues with the DTCPing tool
• How to configure DCOM to listen to a specific ports range

Network COM+ access considerations

Network COM+ access must also be enabled for all BizTalk and SQL servers. It is turned off by default on Windows Server 2008 R2.

The Application Server role installation process provides an option for enabling COM+ Network Access. When COM+ Network Access is enabled, a firewall exception rule is created that opens port 135.

In order to make DCOM applications work in Windows Server 2008 R2 you need to do install the Application role Application and then select the COM+ network access role service.

A quick test of DCOM access is the DCOM test client/server app, however to do this test is still necessary to give permissions at firewall level.

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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 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)

Tags: BizTalk 2010 | Installation | Configuration

This part of the article will focus on installing the SQL Server machine and all necessary requirements and components

Important considerations before set up the servers

Check if all the considerations described above are implemented:

• Join the BizTalk Administrator Group to Local Administrators Group
• Install Critical Windows Updates
• Disable IPv6
• Turn off Internet Explorer Enhanced Security Configuration
• Disable User Account Control
• Install .NET Framework 3.5 SP1
• Configure Microsoft Distributed Transaction Coordinator (MS DTC)
• Enable Network COM+ access

Install SQL Server 2008 R2

In this step, we will install SQL Server 2008 R2 on the machine that will host the BizTalk databases

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Install SQL Server 2008 R2 (Part 4)

The only recommendation that I made is to change the user running the SQL services to a domain account in the step 11, Microsoft recommends that you use a separate account for each SQL Server service (see SQL Server Service Accounts topic described earlier).

Note: Using SQL Server Express Edition in a production environment is not recommended. The Express edition does not include certain features needed by BizTalk Server.

Install Service Pack 1 for Microsoft SQL Server 2008 R2

Service Pack 1 for Microsoft SQL Server 2008 R2 can be found here.

SQL Server 2008 R2 service packs are cumulative updates and upgrade all service levels of SQL Server 2008 R2 to SP1. This service pack contains the cumulative updates of SQL Server 2008 R2 cumulative update packages 1 thru 6. You can use these packages to upgrade any of the following SQL Server 2008 R2 editions:

• SQL Server 2008 R2 Datacenter Edition
• SQL Server 2008 R2 Enterprise Edition and Developer Edition
• SQL Server 2008 R2 Standard Edition
• SQL Server 2008 R2 Web Edition
• SQL Server 2008 R2 Workgroup Edition
• SQL Server 2008 R2 Express Edition

You should install this Service Pack.

SQL Reporting Services Note

One of the changes in the SQL Server Reporting 2008 Reporting Services is the removal of the Internet Information Services (IIS) dependency.

The first reason Microsoft moved away from IIS is for better configuration. IIS was built several years ago to do lots of things, including serving up web pages from the file system, host ISAPIs, Internet printing, etc. SSRS 2005 uses very little of IIS, mainly as a port 80 listener, client authentication, and process hosting. But when you install IIS, you got a bunch of stuff that RS really doesn’t need at all. It turns out that all of the parts of IIS that we didn’t use got configured in very strange ways and made RS not work.

This is especially true in the case where there were other IIS applications on the same server as RS. Not only did other application settings conflict with RS, any application running under the same Application Pool identity is granted full access to the RS catalog. By moving out of IIS, so Microsoft have actually significantly reduced the surface area that you to configure and secure.

The second reason for the change is a need for better resource management. IIS has a pretty simple model for thread, memory, and state management. This works well for most applications that are serving up static or dynamic HTML pages. However, it wasn’t really built to host an enterprise server responsible for serving up reports with gigabytes of data in multiple formats to thousands of users simultaneously. By hosting the service engine ourselves, Microsoft gain much more control over resource management. For example, RS 2008 has a new on-demand processing model to ensure that no report executions will run out of memory. It does this by paging and releasing allocated memory to the disk when it gets memory pressure notifications. This would have been very difficult to implement using the IIS hosting model.

Reference:

• Everybody (Why Leave IIS?)
• SQL Server 2008: Reporting Services no longer needs IIS?

Configure SQL Server for Remote Connections

In order for the BizTalk servers to connect to SQL Server, remote connections need to be enabled.

To do so you need to:

• Run Microsoft SQL Server Management Studio and connect to the right instance.
• Once the tool opens, right click over instance name and select Properties
• Go to Connections page and select the option “Allow remote connections to this server”

Configured SQL Server protocols – Disable the Shared Memory Protocol, Enable TCP/IP and Named Pipes

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Disable the Shared Memory Protocol (Part 7)

Click ‘Start’, ‘All Programs’, click ‘Microsoft SQL Server 2008 R2’, click ‘Configuration Tools’, then click ‘SQL Server Configuration Manager’

In the SQL Server Configuration Manager, click on the ‘SQL Server Network Configuration’ node and expand it, under ‘Protocols for MSSQLSERVER’ right-click the ‘Shared Memory’ protocol and disable it. Right-click the TCP/IP protocol and enable it and repeat the process for Named Pipes.

Configure a Server to Listen on a Specific TCP Port

This is one request of my client.

If enabled, the default instance of the SQL Server Database Engine listens on TCP port 1433. Named instances of the Database Engine and SQL Server Compact 3.5 SP2 are configured for dynamic ports. This means they select an available port when the SQL Server service is started. When you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port can be opened in the firewall.

To assign a TCP/IP port number to the SQL Server Database Engine

• In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for <instance name>, and then double-click TCP/IP.
• In the TCP/IP Properties dialog box, on the Protocol tab, change the property “Listen All” to “No”(This is one request of my client – just want to listen in one IP set in the machine)

• In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure.
• If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.
• In the IPn Properties area box, in the TCP Port box, type the port number you want this IP address to listen on, and then click OK.

• In the console pane, click SQL Server Services.
• In the details pane, right-click SQL Server (<instance name>) and then click Restart, to stop and restart SQL Server.

After you have configured SQL Server to listen on a specific port, there are three ways to connect to a specific port with a client application:

• Run the SQL Server Browser service on the server to connect to the Database Engine instance by name.
• Create an alias on the client, specifying the port number.
• Program the client to connect using a custom connection string.

Reference: How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)

Configure SQL Analysis Server to Listen on a Specific TCP Port

This is one request of my client.

You will be able to configure the port that SQL Analysis Server is listening by:

• Opening the SQL Server Management Console
• Connect to Analysis Server

• Right Click on SQL instance and select “Properties” option
• On “General” tab, go to “Port” and set the port that you want to configure, in my case “2382”.

• Click “Ok” and restart the service.

Configuring Microsoft Distributed Transaction Coordinator (DTC) to work through a firewall or network address translation firewalls

DTC uses Remote Procedure Call (RPC) dynamic port allocation. By default, RPC dynamic port allocation randomly selects port numbers above 1024.

You can configure DTC to communicate through firewalls, including network address translation firewalls, just follow these steps:

• Go to Component Services
• On Component Services console, expand “Component Services
• Right click over “My Computer” and select Properties option
• Go to “Default Protocols” tab select “Connection-oriented TCP/IP” option in DCOM protocols

• Click “Properties” button
• On “Properties for COM Internet Services” windows, click “Add” button to set a port range
• Specify the range of ports you want to use, I set the following range: “5000-8976”

• Click “Ok”

• Ensure that “Internet range” is check in both options: “Port range assignment” and “Default dynamic port allocation”

List of ports between BizTalk Server and SQL Server

The following table lists the ports that we need to configured in firewall or request ACLs to network IT.

Direction:

• Source Host: BizTalk Server
• Destination Host: SQL Server

Reference:

• Required Ports for BizTalk Server

Configure Firewall on SQL Server machine

Inbound Rules

In order to make DCOM applications work in Windows Server 2008 R2 you need to add the COM+ network access as show below:

• Open “Server manager” console and expand “Configuration” option in the left tree.
• Expand “Windows Firewall with Advanced Security” and select “Inbound Rules” option.
• Enable the following inbound rules by select them and right click and select the option “Enable Rule” option
  • COM+ Network Access (DCOM-in)
  • COM+ Remote Administrator (DCOM-In)

Also we enable Microsoft Distributed Transaction Coordinator (MS DTC) to communicate through a firewall with another MS DTC.

Repeat the previous steps and Enable the followings rules:

• Distributed Transaction Coordinator (RPC)
• Distributed Transaction Coordinator (RPC-EPMAP)
• Distributed Transaction Coordinator (TCP-In)

Now we need to create new rules for each of port described in topic “List of ports between BizTalk Server and SQL Server” to allow BizTalk Server to communicate with SQL Server machine. To create a new Inbound Rule, follow these steps:

• Right click on “Inbound Rules” on the left tree and select the option “New Rule”

• On “New Inbounded Rule Wizard” windows in step “Rule Type” select "Port" option
• In step "Protocol and Ports" select the protocol requested and specify the port or list of ports
• In step "Action" select "Allow the connection" option
• In step "Profile" leave the default options
• In step "name" set the name and description of the rule

Outbound Rules

First thing is to enable the following outbound rules:

• Distributed Transaction Coordinator (TCP-Out) – this will allow Outbound traffic for the Distributed Transaction Coordinator.

To do this follow the steps described in Inbound Rules, the steps are the same the only difference is that we are dealing with Outbound Rules

The second is to create a new outbound rule for RPC ports:

• Right click on “Outbound Rules” on the left tree and select the option “New Rule”
• On “New Outbounded Rule Wizard” windows in step “Rule Type” select "Port" option
• In step "Protocol and Ports"
  • Select the protocol: TCP
  • Specify the range of ports: 5000-8976
• In step "Action" select "Allow the connection" option
• In step "Profile" leave the default options
• In step "name" set the name and description of the rule

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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 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)

Tags: BizTalk 2010 | Installation | Configuration

This part of the article will focus on installing the BizTalk prerequisites and operate the necessary configuration on BizTalk Server machine.

Before installing BizTalk Server or its prerequisites, make sure you have installed the latest critical Windows updates from Microsoft.

Important considerations before set up the servers

Check if all the considerations described above are implemented:

• Join the BizTalk Administrator Group to Local Administrators Group
• Install Critical Windows Updates
• Disable IPv6
• Turn off Internet Explorer Enhanced Security Configuration
• Disable User Account Control
• Install .NET Framework 3.5 SP1
• Configure Microsoft Distributed Transaction Coordinator (MS DTC)
• Enable Network COM+ access

Enable Internet Information Services

Microsoft Internet Information Services (IIS) provides a Web application infrastructure for many BizTalk Server features. BizTalk Server requires IIS for the following features:

• HTTP adapter
• SOAP adapter
• Windows SharePoint Services adapter
• Secure Sockets Layer (SSL) encryption
• BAM Portal

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Enable Internet Information Services (Part 1)

In alternative you can install these features by using PowerShell:

• Open PowerShell as administrator and run this script
  • Set-ExecutionPolicy unrestricted press ‘y’
  • Import-Module ServerManager
    @("Web-Server",
    "Web-Http-Errors",
    "Web-App-Dev",
    "Web-Asp-Net",
    "Web-Net-Ext",
    "Web-ASP",
    "Web-CGI",
    "Web-ISAPI-Ext",
    "Web-ISAPI-Filter",
    "Web-Includes",
    "Web-Basic-Auth",
    "Web-Windows-Auth",
    "Web-Mgmt-Compat",
    "Web-Metabase",
    "Web-WMI",
    "Web-Lgcy-Scripting",
    "Web-Lgcy-Mgmt-Console"
    )| Add-WindowsFeature

Install Microsoft Office Excel 2010 or Excel 2007

Microsoft Office Excel is required for using the Business Activity Monitoring (BAM) feature in BizTalk Server. You use the BAM Office Excel Workbook to define the business processes you want to monitor. You also use the BAM Excel Workbook to define the way in which business users see the data collected by BAM.

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Install Microsoft Office Excel 2007 (Part 2)

Install Visual Studio 2010

The BizTalk Server development tools are based on Visual Studio 2010. Because this is an emulation of production environment I will skip this part. However, the steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Install Visual Studio 2010 (Part 3)

SQL Server Considerations

The following software requirements are need when SQL Server is installed on a computer other than the one where BizTalk Server is installed:

The following conditions apply regarding remote computers.

• SQL Server Client Tools must be installed on the local computer when SQL Server is remote. The SQL Server Client Tools install the client libraries required to communicate with the remote instance of SQL Server.
• The version of the SQL Server Client tools on the local computer must be the same version that is installed on the remote SQL Server.
• SQL Server OLAP client must be installed on the local computer if you plan to use Analysis Services remotely.
• The remote SQL Server must be running during BizTalk Server configuration.
• The TCP and UDP ports you specified during the SQL Server setup process must be open during BizTalk Server configuration.
• Named instances of SQL Server 2008 Analysis Services are not supported.

Install SQL Server 2008 R2 Client Tools

SQL Server Client Tools must be installed on the local computer when SQL Server is remote.

The SQL Server Client Tools (must be the same version that is installed on the remote SQL Server) install the client libraries required to communicate with the remote instance of SQL Server.

To Install SQL Server 2008 R2 Client Tools:

• Insert the SQL Server 2008 R2 installation disk into the DVD-ROM drive. The setup program will begin automatically. If prompted for automatic installation of prerequisite software, click OK.
• On the SQL Server Installation Center, click Installation.
• Click New Installation or Add Features to an Existing Installation.
• Review the information on the Setup Support Rules screen, and then click OK.
• On the Product Key screen, enter your product key and click Next.
• On the License Terms screen, select I accept the license terms, and then click Next.
• On the Setup Support Files screen, click Install.
• On the Feature Selection screen, select the following features, and then click Next.
  • Shared Features
    • Management Tools – Basic
    • Management Tools – Complete

The similar steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Install SQL Server 2008 R2 (Part 4)

Install SQL Server 2005 Notification Services

If you plan to use BAM Alerts in your BizTalk Server project, you must install SQL Notification Services and its prerequisites.

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Install SQL Server 2005 Notification Services on top of SQL Server 2008 R2 (Part 5)

Microsoft SQL Server Native Client

Microsoft SQL Server Native Client (SQL Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 7.0, 2000 or 2005. SQL Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2005 features. This redistributable installer for SQL Native Client installs the client components needed during run time to take advantage of new SQL Server 2005 features, and optionally installs the header files needed to develop an application that uses the SQL Native Client API.

Microsoft SQL Server 2005 Management Objects Collection

The Management Objects Collection package includes several key elements of the SQL Server 2005 management API, including Analysis Management Objects (AMO), Replication Management Objects (RMO), and SQL Server Management Objects (SMO). Developers and DBAs can use these components to programmatically manage SQL Server 2005.
Note: Microsoft SQL Server 2005 Management Objects Collection requires Microsoft Core XML Services (MSXML) 6.0 and Microsoft SQL Server Native Client, also available on this page.

Microsoft SQL Server 2005 Notification Services Client Components

The SQL Server 2005 Notification Services Client Components package provides client APIs that enable subscription management and event submission within custom applications that include SQL Server 2005 Notification Services functionality. The subscription management APIs allows developers to create subscriptions and subscribers, and manage subscriber devices. The event submission APIs allow users to specify events using the event APIs or stored procedures.

Create SQL Alias to communicate with remote SQL Server using Non-Standard Port

When we want to install BizTalk Server with a remote SQL Server using non default port we cannot use “servername\instance, port number” for BizTalk installation, it will give you the following error:

Error Configuration Framework]Feature: [Group] Failed to configure with error message [Exception of type 'System.EnterpriseServices.TransactionProxyException' was thrown.]

Instead you should create a SQL Server Alias on the client machine to connect to SQL Server machine.

An alias can be created on the client machine by running the SQL Server Configuration Manager tool.

• Under the SQL Server Native Client folder, right click on the “Aliases” item and select the “New Aliases” item.
• When doing this the “Alias – New” dialog box will be displayed. In the new alias dialog box, you can create an alias where you can specify the instance name and the port number it is using.
  • In the “Alias Name “set the name of alias: “BizTalkSQL”
  • In “Port No” specify the port where Database Engine running is listening: 1433
  • In “Protocol” leave the default value “TCP/IP”
  • In “Server” specify “servername\instance”

List of ports between SQL Server and BizTalk Server

The following table lists the ports that we need to configured in firewall or request ACLs to network IT.

Direction:

• Source Host: SQL Server
• Destination Host: BizTalk Server

Reference:

• Required Ports for BizTalk Server

Configuring Microsoft Distributed Transaction Coordinator (DTC) to work through a firewall or network address translation firewalls

DTC uses Remote Procedure Call (RPC) dynamic port allocation. By default, RPC dynamic port allocation randomly selects port numbers above 1024.

You can configure DTC to communicate through firewalls, including network address translation firewalls, just follow these steps:

• Go to Component Services
• On Component Services console, expand “Component Services
• Right click over “My Computer” and select Properties option
• Go to “Default Protocols” tab select “Connection-oriented TCP/IP” option in DCOM protocols

• Click “Properties” button
• On “Properties for COM Internet Services” windows, click “Add” button to set a port range
• Specify the range of ports you want to use, I set the following range: “5000-8976”

• Click “Ok”

• Ensure that “Internet range” is check in both options: “Port range assignment” and “Default dynamic port allocation”

Configure Firewall on BizTalk Server machine

Inbound Rules

In order to make DCOM applications work in Windows Server 2008 R2 you need to add the COM+ network access as show below:

• As described previously on “Configure Firewall on SQL Server machine”. Enable the following inbound rules by select them and right click and select the option “Enable Rule” option
  • COM+ Network Access (DCOM-In)
  • COM+ Remote Administrator (DCOM-In)
• Also enable Microsoft Distributed Transaction Coordinator (MS DTC) to communicate through a firewall with another MS DTC.
  • Distributed Transaction Coordinator (RPC)
  • Distributed Transaction Coordinator (RPC-EPMAP)
  • Distributed Transaction Coordinator (TCP-In)

Now we need to create new rules for each of port described in topic “List of ports between SQL Server and BizTalk Server” to allow SQL Server to communicate with BizTalk Server machine. As described previously on “Configure Firewall on SQL Server machine”

Outbound Rules

First thing is to enable the following outbound rules:

• Distributed Transaction Coordinator (TCP-Out) – this will allow Outbound traffic for the Distributed Transaction Coordinator.

The second is to create a new outbound rule for RPC ports:

• Right click on “Outbound Rules” on the left tree and select the option “New Rule”
• On “New Outbounded dRule Wizard” windows in step “Rule Type” select "Port" option
• In step "Protocol and Ports"
  • Select the protocol: TCP
  • Specify the range of ports: 5000-8976
• In step "Action" select "Allow the connection" option
• In step "Profile" leave the default options
• In step "name" set the name and description of the rule

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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: 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)

Tags: BizTalk 2010 | Installation | Configuration

Before you install and configure BizTalk Server is always a good practice to test or validate the connectivity’s between BizTalk Server and SQL Server machines.

To accomplish that we can use 4 Tools:

• TCPView – This is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system and can be obtained from Microsoft: TCPView
• DTCPing – This tool is designed to assist with troubleshooting Microsoft DTC Firewall Issues and can be obtained from Microsoft: DTCPing.exe
• DTCTester – This tool tests a distributed transaction against a specified Microsoft SQL Server. This tool helps to test distributed transactions across firewalls or against networks. The tool performs distributed transactions by using ODBC API against a SQL Server database and can be obtained from Microsoft: How To Use DTCTester Tool
• SQL Server 2008 R2 Client Tools – Tools to communicate with the remote instance of SQL Server

TCPView

TCPView is a Windows program that will show you detailed listings of all TCP and UDP endpoints on your system, including the local and remote addresses and state of TCP connections.

To execute this tool, just download it, extract all files and execute Tcpview.exe file.

DTCPing

Before running this tool and since this tool runs on dynamic port, we have to check which port this tool is listening on both machines and add an inbound rule in each firewall. To accomplish that, we can use the tool TCPView (see picture above)..

To test DTCPing tool you must run this tool on both the machines, then you can test whether the normal RPC communication is working or not.

On SQL Server machine put the following configuration:

On BizTalk Server machine put the following configuration:

Test ping on both machines, you receive a similar message:

Please refer to following log file for details:
C:\Users\…\Desktop\dtcping\BTSSQL1704.log
Invoking RPC method on BTSSQL
WARNING:the CID values for both test machines are the same
Please send following LOG to Microsoft for analysis:
Partner LOG: BTSSQL 1704.log
My LOG: BTSSQL 1704.log
RPC test is successful
++++++++++++RPC test completed+++++++++++++++

DTCTester

To test DTCTester you must:

• Create an ODBC Data Source in BizTalk machine
  • Go to Startà Data sources (ODBC)

• Select “Add” button and select “SQL Server” option

• Configure the New Data Source

• Leave Default options

• Leave Default options

• Leave Default options

• Press Finish
• Test Data Source

• Press Ok and Ok
• Access to command line (runàcmd) from BizTalk Server machine a run the following command:
  • Go to DTCTester directory
  • Type dtctester <odbc name> <user name> <password>
  • Example: dtctester SQLTest myuser mypass

SQL Server 2008 R2 Client Tools

This is the easy part, just open SQL Server Management Studio from BizTalk Server machine and try to connect to Database Engine and Analysis Services by using servername\instance or the Alias that we create earlier.

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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: Install and configure BizTalk Server 2010 machine (Part 7)

Tags: BizTalk 2010 | Installation | Configuration

This part of the article will focus on installing and configuring BizTalk Server 2010, installing additional components and confirm that the installation succeeded.

Install BizTalk Server 2010

The steps to install BizTalk Server are described in my blog:

• BizTalk 2010 Installation and Configuration – Installing and Configuring BizTalk Server (Part 8)

Configure BizTalk Server

To configure BizTalk Server 2010, click Start, click All Programs, click Microsoft BizTalk Server 2010, right-click BizTalk Server Configuration, and then click Run as Administrator.

• Because this is a multi-Computer BizTalk Server installation we cannot use a “Basic Configuration” option. You must select “Custom configuration” option

• Click Configure
• On Enterprise SSO tab, Create a new SSO System and place the following configurations

• On Enterprise SSO Secret Backup tab, set a secret backup password, password reminder and the location of the SSO backup file

• On Group tab, Create a new BizTalk Group and place the following configurations

• On BizTalk Runtime tab, Create a new In-Process and Isolate Host and Instance with the following configurations

• On Business Rule Engine tab place the following configurations

• On BAM Tools tab, Enable Analysis Services for BAM aggregations and place the following configurations

• On BAM Alerts tab, enable SQL Notification Services for BAM Alerts and place the following configurations

• On BAM Portal tab, place the following configurations

• On BizTalk EDI/AS2 Runtime tab, enable all features

• Click “Apply Configurations”
• On the Summary screen, review the configuration about to be performed, and then click Next.
• On the Completion screen, click Finish.

Install BizTalk Adapter Pack 2010

The BizTalk Adapter Pack 2010 provides connectivity to SAP, Oracle E-Business Suite, Siebel and SQL and Oracle Databases. The BizTalk Adapter Pack can be installed in conjunction with, or separately from, BizTalk Server .

BizTalk Adapter Pack 2010 it is included in both the Enterprise and Standard Editions of BizTalk and can be install from BizTalk Server 2010 installation disk into the DVD-ROM drive

The steps are described in Steef-Jan Wiggers blog:

• Installing BizTalk Adapter Pack 2010 on x64

Install Microsoft AppFabric Connect

BizTalk Server 2010 introduces a new feature “AppFabric Connect”, which combines rich proven features of BizTalk Server with the flexible development experience of .NET to allow users to easily develop simple integration applications. This enables users to:

• Develop custom .NET applications that require connectivity to backend Line of Business (LOB) systems like SAP, Oracle database, Oracle E-Business Suite, Seibel, and SQL Server without writing custom code for LOB connectivity
• Utilize the XML-based data transformation capabilities of the easy to use and rich interface of the BizTalk Server Mapper directly from within a .NET project.

References:

• Introducing BizTalk Server 2010 AppFabric Connect

Installation process is similar to the previous point.

Install BizTalk Server 2010 Cumulative Updates

You should install the last cumulative updates available for BizTalk Server 2010.

List of CU available are referenced in my blog:

• BizTalk Server: List of Service Packs and Cumulative Updates available

Configure BizTalk Services to start Automatic (Delayed Start)

The steps are described in my blog and prevents that the services don’t start up automatically after a server restart:

• BizTalk 2010: BizTalk Server Application Service (BTSNTSvc.exe) fails to start automatically after a system restart

Verify BizTalk Configuration

You can check if the configuration went well by having a look at the Windows Event Log, there should be a lot of Information entries and no errors or warning related to BizTalk.

You should also start the BizTalk Server administration console and verify the BizTalk Server host instance is started (found under BizTalk Group\Platform Settings\ Host Instances). Try stopping and starting the host instance.

Configure BizTalk Server SQL Jobs

By default, the following BizTalk jobs aren’t configured and enabled upon installation.

• Backup BizTalk Server (BizTalkMgmtDb)
• DTA Purge and Archive (BizTalkDTADb)
• MessageBox_Message_Cleanup_BizTalkMsgBoxDb

If you want these functionalities you must configure and enabled them.

The steps are described in my blog:

• BizTalk 2010 Installation and Configuration – Configure BizTalk Server SQL Jobs (Part 11)

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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)

Tags: BizTalk 2010 | Installation | Configuration

This part of the article will focus on configuring TCP setting on BizTalk server and the SQL server machines that can impact BizTalk Server and that can prevent from occurring general network errors.

When I was analyzing my BizTalk environment with BizTalk Server Best Practice Analyser tool, has appeared a warning that caught my attention:

Privilege Attribute Certificate (PAC) Signature Validation is Enabled on Server BTS2010LAB01.
On server BTS2010LAB01, Privilege Attribute Certificate (PAC) signature is enabled, which may cause some user-authentication delay

And led me to go deeper in trying to see what was causing this strange issue and I found a number of TCP settings that needs to be done (or is recommended) which can also prevent from occurring general network errors on BizTalk Server Environments.

In the scenario described in this series of articles we should apply the following TCP/IP settings:

• Disable the Scalable Networking Pack (SNP) features
• This needs to be done on the BizTalk Server and the SQL Server
• Disable Privilege Attribute Certificate (PAC)
• This needs to be done on the BizTalk Server and the SQL Server
• Check and if necessary increase the ephemeral ports and reduce the TCP re-use timeout setting
• This needs to be done only on the BizTalk Server

How to Disable the Scalable Networking Pack (SNP) features

Scalable Networking Pack (SNP) be used, under specific circumstances, to improve network performance, however, most environments do not have SNP capable network adapters/drivers. This can result in unexpected network problem which is why it is recommended to disable SNP unless a server can benefit from it.

To disable SNP features we need to:

• Disable TCP Chimney Offload in the operating system
• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp set global chimney=disabled
• Disable RSS in the operating system
• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp set global rss=disabled
• Disable NetDMA in the operating system
• Click Start, click Run, type regedit, and then click OK.
• Locate the following registry subkey, and then click it:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
• Double-click the EnableTCPA registry entry.
• Note: If this registry entry does not exist, right-click Parameters, point to New, click DWORD Value, type EnableTCPA, and then press ENTER.
• To disable NetDMA, type 0 in the Value data box, and then click OK.

To determine the current status of SNP features, follow these steps:

• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp show global

Note: you need to restart the computer first.

How to Disable Privilege Attribute Certificate (PAC)

The Privilege Attribute Certificate (PAC) is a function invoked within the Windows security system when you log on to a system utilizing Kerberos. It is a network authentication protocol.

The Kerberos Privilege Attribute Certificate (PAC) contains all of the group memberships for the security principal requesting access to a resource. PAC validation means a more secure environment so why should be disabled?

When you run a high-volume server program on a domain member that uses Kerberos to authenticate users, you experience a delay in the user-authentication process. Additionally, you notice an increase in the remote procedure call (RPC) traffic between the domain controller that uses the Net Logon RPC interface and the server. This problem occurs because the Kerberos client verifies the Privilege Attribute Certificate (PAC) signature in the Kerberos ticket by using the domain controller. The Kerberos client performs this verification to prevent PAC spoofing. The increased network traffic is generated by the RPC requests that are part of this verification process.

To disable PAC we need to:

• Click Start, click Run, type regedit, and then click OK.
• Locate the following registry subkey, and then click it:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
• Add the following registry entry
• Right-click Parameters, point to New, click DWORD Value, type ValidateKdcPacSignature, and then press ENTER.
• To disable PAC, double-click the ValidateKdcPacSignature registry entry and type 0 in the Value data box, and then click OK

How to Check and if necessary increase the ephemeral ports and reduce the TCP re-use timeout setting

When a client initiates a TCP/IP socket connection to a server, the client typically connects to a specific port on the server and requests that the server responds to the client over an ephemeral, or short lived, TCP or UDP port.

Under certain conditions it is possible that the available ports in the default range will be exhausted. If this occurs the following symptoms may be observed:

• Client applications may fail to connect to the BizTalk Server.
• The BizTalk Application service may fail to connect to a remote SQL Server.
• BizTalk Server adapters may fail to connect to a remote server.

To verify that one or more client applications are not generating excessive TCP/IP socket connections perform the following on the BizTalk servers in the group:

• From a command prompt window execute “netstat -ano -p tcp”.
• Count the number of unique Local Address TCP ports open above 1024 for each IP address.

If less than 3000 ephemeral ports are currently in use then it’s fine. (Original source: Recommended Platform Configuration for BizTalk Server by Abdul Rafay)

You can check or modify these settings at the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters registry key. The recommended values are:

• Registry name: MaxUserPort
• Value: 0xFFFE (65534)
• Comment: Prevents port exhaustion
• Registry name: TcpTimedWaitDelay
• Value: 0x1E (30)
• Comment: Release unused ports as quickly as possible

Or you can view the dynamic port range by using the following netsh commands:

• netsh int ipv4 show dynamicport tcp
• netsh int ipv4 show dynamicport udp

On all BizTalk servers running on Windows Server 2008, Microsoft recommend not modifying the dynamic port range. However, if you determine that additional dynamic ports are needed you can also use netsh command to modify these settings, as follows:

• netsh int <ipv4|ipv6> set dynamic <tcp|udp> start=number num=range

This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. Example:

• netsh int ipv4 set dynamicport tcp start=10000 num=1000

These sample commands set the dynamic port range to start at port 10000 and to end at port 11000 (1000 ports).

Important notes:

• The minimum range of ports that can be set is 255.
• The minimum starting port that can be set is 1025.
• The maximum end port (based on the range being configured) cannot exceed 65535.

See Microsoft Help and Support

At the end you should restart BizTalk and SQL Servers.

Other sources TCP settings that can impact BizTalk Server

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• 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)

Tags: BizTalk 2010 | Installation | Configuration

Normally we tend to inherit BizTalk environments already installed and preconfigured, is not every day that we create an environment from scratch, this is one of these situations. It was given BizTalk Administrator permission to my user, i.e., my user was added to BizTalk Server Administrators group.

My first operations was to create some BizTalk Hosts, which went smoothly (for more information about this topic see Managing BizTalk Hosts and Host Instances)

However when I was creating the Host Instances associated with BizTalk Hosts created previous, I obtained the following error:

TITLE: BizTalk Server Administration
——————————
Installation of instance of host BizTalkSoapApplication on server … failed.
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2010&ProdVer=3.9.469.0&EvtSrc= Microsoft.BizTalk.Administration.SnapIn.Properties.Errors&EvtID=HostInstance_CreateFailed&EvtChain= BTSAdminMsg+%2c10294
——————————
ADDITIONAL INFORMATION:
Permission is denied. The current user does not have sufficient permissions to perform this operation. (WinMgmt)
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2010&ProdVer=3.9.469.0&EvtSrc=BTSAdminMsg&EvtID=10294

CAUSE

The additional information is explicit, this problem occurs because the user account that you’re using to configure BizTalk doesn’t have sufficient permissions.

SOLUTION

• When you install a host instance, you must have the privileges to create a Windows service, and to grant SQL Server logon and access rights for the BizTalk databases to the Host Windows user group.

I usually say: “To be able to install and configure BizTalk Server 2010 without problems, you have to log on the server using a Domain User who is member of BizTalk Server Administrators group and this group have Administrator rights on both the SQL Server and the BizTalk Server.”

In my case, my user was member of BizTalk Server Administrators group, but this group didn’t have Administrator rights in BizTalk Server machine.

To add BizTalk Server Administrators group to the Local Administrators Group in both machines:

• Click ‘Start’, ‘Control Panel’, ‘Administrator Tools’, ‘Computer Management’, ‘Local Users and Groups, ‘Groups’
• Add you user account and BizTalk Server Administrators group to the ‘Administrators’ group

Note: as I had no administrator rights in machine, I had to request to the system administrators to carry out this operation.

By default the Windows Builtin\Administrators group has the sysadmin SQL role on the SQL Server, however, we need to ensure that this group have access to the BizTalk databases. In my case the group is db_ower of all BizTalk databases, have permission to connect to database engine and the login is enable.

References

• About Host Instances
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment

Tags: BizTalk | Configuration | Hosts | Errors and Warnings, Causes and Solutions

Today I want to talk to you about two small optimizations often forgotten but with performance implications. Some of these implications may be noticed more in the early days of our BizTalk environment when the databases are small or almost empty and often need to increase, others can have impact later when databases are large and the percentage increase is also too large.

By default BizTalk Server databases are defined with small files size and with the parameter “Autogrowth” set to:

• Increase by 1 MB for database file
• And by 10% for log file

There’s a great post from Jeroen Hendriks: Checking database autogrowth settings where it is explained how we can check all BizTalk Server database settings using an SQL query and also Database file size – data collection so that we can recommend the right values.

So what’s the problem with these settings?

Auto growth setting plays an important role in BizTalk configuration for performance reasons, why?

SQL Server database auto-growth is a blocking operation which hinders BizTalk Server database performance. When SQL Server increases the size of a file, it must first initialize the new space before it can be used. This is a blocking operation that involves filling the new space with empty pages.

Therefore it’s recommended to:

1. Set this value (databases auto-growth) to a fixed value of megabytes instead of to a percentage, so SQL server doesn’t waste is resources expanding the data and log files during heavy processing. This is especially true for the MessageBox and Tracking (DTA) databases:
   1. In a high throughput BizTalk Server environment, the MessageBox and Tracking databases can significantly increase. If auto-growth is set to a percentage, then auto-growth will be substantial as well.
   2. As a guideline for auto-growth, for large files increment should be no larger than 100 MB, for medium-sized files 10 MB, or for small files 1 MB.
   3. This should be done so that, if auto-growth occurs, it does so in a measured fashion. This reduces the likelihood of excessive database growth.
2. Also allocate sufficient space for the BizTalk Server databases in advance to minimize the occurrence of database auto-growth.

How can I implement these optimizations?

You can do these optimizations by two ways:

• Manually, by opening “Microsoft SQL Server Management Studio”
  • Maximize you SQL Server and then Databases
  • Right-click in the database, for example “BizTalkMsgBoxDb” and select “Properties” option
  • On Database Properties window, select Files page option and then you can check and change Autogrowth property associated to database and log file.

However checking and changing all BizTalk databases manually is too much work and can be a little boring …

• Or you can do this by running the following SQL Script:

ALTER DATABASE BizTalkDTADb MODIFY FILE (NAME = BizTalkDTADb , SIZE = 2GB , FILEGROWTH = 100MB)
GO
ALTER DATABASE BizTalkDTADb MODIFY FILE (NAME = BizTalkDTADb_log , SIZE =  1GB , FILEGROWTH = 100MB)
GO

ALTER DATABASE BizTalkMgmtdb MODIFY FILE (NAME = BizTalkMgmtDb , SIZE = 512MB , FILEGROWTH = 100MB)
GO
ALTER DATABASE BizTalkMgmtdb MODIFY FILE (NAME = BizTalkMgmtDb_log , SIZE =  512MB , FILEGROWTH = 100MB)
GO

ALTER DATABASE BizTalkMsgBoxDb MODIFY FILE (NAME = BizTalkMsgBoxDb , SIZE = 2GB , FILEGROWTH = 100MB)
GO
ALTER DATABASE BizTalkMsgBoxDb MODIFY FILE (NAME = BizTalkMsgBoxDb_log , SIZE =  2GB , FILEGROWTH = 100MB)
GO

ALTER DATABASE SSODB MODIFY FILE (NAME = SSODB , SIZE = 512MB , FILEGROWTH = 100MB)
GO
ALTER DATABASE SSODB MODIFY FILE (NAME = SSODB_log , SIZE =  512MB , FILEGROWTH = 100MB)
GO

ALTER DATABASE BAMPrimaryImport MODIFY FILE (NAME = BAMPrimaryImport , SIZE = 150MB , FILEGROWTH = 10MB)
GO
ALTER DATABASE BAMPrimaryImport MODIFY FILE (NAME = BAMPrimaryImport_log , SIZE =  150MB , FILEGROWTH = 10MB)
GO

ALTER DATABASE BAMArchive MODIFY FILE (NAME = BAMArchive , SIZE = 70MB , FILEGROWTH = 10MB)
GO
ALTER DATABASE BAMArchive MODIFY FILE (NAME = BAMArchive_log , SIZE =  200MB , FILEGROWTH = 10MB)
GO

ALTER DATABASE BizTalkRuleEngineDb MODIFY FILE ( NAME = BizTalkRuleEngineDb , FILEGROWTH = 1024KB )
GO
ALTER DATABASE BizTalkRuleEngineDb MODIFY FILE ( NAME = BizTalkRuleEngineDb_log , FILEGROWTH = 1024KB )
GO

The execution of this SQL script will set automatically the values for all BizTalk Server databases according to what is recommended. Not only the auto-growth property but also the database and log file size:

• BizTalkDTADb (BizTalk Tracking database): Data file having a file size of 2 GB with 100 MB growth and a log file of 1 GB with 100 MB growth.
• BizTalkMgmtdb (BizTalk Management database): Data file having a file size of 512 MB with 100 MB growth and a log file of 512 MB with 100 MB growth.
• SSODB (SSO database): Data file having a file size of 512 MB with 100 MB growth and a log file of 512 MB with 100 MB growth.
• BizTalkMsgBoxDb (BizTalk MessageBox database): Data file having a file size of 2 GB with 100 MB growth and a log file of 2 GB with 100 MB growth.
• BAMPrimaryImport (BAM Primary Import database): Data file having a file size of 150 MB with 10 MB growth and a log file of 150 MB with 100 MB growth.
• BAMArchive (BAM Archive): Data file having a file size of 70 MB with 10 MB growth and a log file of 200 MB with 10 MB growth.
• BizTalkRuleEngineDb (Rule Engine database): Data file with 1 MB growth and a log file with 1 MB growth.

Note: These values were used for a standalone environment. In a high throughput BizTalk Server environment you should consider devide the BizTalkMsgBoxDb in 8 data files, each having a file size of 2 GB with 100 MB growth and a log file of 20 GB with 100 MB growth. Because the BizTalk MessageBox databases are the most active, we recommend you place the data files and transaction log files on dedicated drives to reduce the likelihood of problems with disk I/O contention, as is explained here: http://msdn.microsoft.com/en-us/library/ee377048.aspx

EXEC dbo.sp_helpdb BizTalkMsgBoxDb
ALTER DATABASE BizTalkMsgBoxDb MODIFY FILE (NAME = BizTalkMsgBoxDb , FILENAME = 'J:\BizTalkMsgBoxDb.mdf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_2 , FILENAME = 'J:\BizTalkMsgBoxDb_2.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_3 , FILENAME = 'J:\BizTalkMsgBoxDb_3.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_4 , FILENAME = 'J:\BizTalkMsgBoxDb_4.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_5 , FILENAME = 'J:\BizTalkMsgBoxDb_5.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_6 , FILENAME = 'J:\BizTalkMsgBoxDb_6.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_7 , FILENAME = 'J:\BizTalkMsgBoxDb_7.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
ALTER DATABASE BizTalkMsgBoxDb ADD FILE    (NAME = BizTalkMsgBoxDb_8 , FILENAME = 'J:\BizTalkMsgBoxDb_8.ndf' , SIZE = 2GB , FILEGROWTH = 100MB)
GO
ALTER DATABASE BizTalkMsgBoxDb MODIFY FILE (NAME = BizTalkMsgBoxDb_log , FILENAME = 'K:\BizTalkMsgBoxDb_log.LDF', SIZE =  20GB , FILEGROWTH = 100MB)
GO

The script can be found and download on Microsoft TechNet Gallery:
Pre-allocate space and define auto-growth settings for BizTalk Server databases (1.5 KB)
Microsoft TechNet Gallery

Today is a special day for me, it’s my birthday, and I will continue the tradition of giving something to the community on this day (I started this tradition last year)… In the past I wrote a series of posts describing step by step how to install and configure BizTalk Server 2010.

One of this step is to configure SQL Server Network Protocols, in special ensure that TCP/IP is enable and Shared Memory is disable. You can see how to accomplish this using SQL Server Configuration Manager tool here.

However a community member (anonymous) left me a comment asking me whether it was possible to accomplish this (disable shared memory) from command line or registry and the answer is: YES, of course, you can for example configure all the SQL Server Network Protocols with PowerShell.

All network protocols are installed by SQL Server Setup, but may or may not be enabled. And you need to be aware that this protocols can have impact in your BizTalk Environment, for example:

• Under certain stress conditions (such as clients accessing SQL Server from the same computer), the SQL Server Shared Memory protocol may lower BizTalk Server performance.
• BizTalk Server loses connectivity with a remote SQL Server computer that houses the BizTalk Server databases and this may happen if the necessary protocols for SQL Server are not enabled.

So normally we need to perform the following configuration:

• Disable the “Shared Memory” and “VIA” protocols
• And Enable the “TCP/IP” and “Named Pipes” protocols

How can I configure SQL Server Network Protocols with PowerShell?

This is a simple script to configure SQL Server Network Protocols for SQL Server that houses BizTalk Server databases:

[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo")
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.SqlWmiManagement")

##################################################################
# Function to Enable or Disable a SQL Server Network Protocol
##################################################################
function ChangeSQLProtocolStatus($server,$instance,$protocol,$enable){

	$smo = 'Microsoft.SqlServer.Management.Smo.'

	$wmi = new-object ($smo + 'Wmi.ManagedComputer')

	$singleWmi = $wmi | where {$_.Name -eq $server}

	$uri = "ManagedComputer[@Name='$server']/ServerInstance[@Name='$instance']/ServerProtocol[@Name='$protocol']"

	$protocol = $singleWmi.GetSmoObject($uri)

	$protocol.IsEnabled = $enable

	$protocol.Alter()

	$protocol
}

##################################################################
# Enable TCP/IP SQL Server Network Protocol
##################################################################
ChangeSQLProtocolStatus -server "BTS2010LAB01" -instance "MSSQLSERVER" -protocol "TCP" -enable $true

##################################################################
# Enable Named Pipes SQL Server Network Protocol
##################################################################
ChangeSQLProtocolStatus -server "BTS2010LAB01" -instance "MSSQLSERVER" -protocol "NP" -enable $true

##################################################################
# Disable Shared Memory SQL Server Network Protocol
##################################################################
ChangeSQLProtocolStatus -server "BTS2010LAB01" -instance "MSSQLSERVER" -protocol "SM" -enable $false

##################################################################
# Disable VIA SQL Server Network Protocol
##################################################################
ChangeSQLProtocolStatus -server "BTS2010LAB01" -instance "MSSQLSERVER" -protocol "VIA" -enable $false

Because after we correctly set up the protocols, we need to restart the SQL services for the changes to take effect, this script additional also restart all the services and also BizTalk Services if they exist! However this last part is optional.

$service = get-service "MSSQLSERVER"
restart-service $service.name -force #Restart SQL Services

$service = get-service "ENTSSO" #Start Enterprise Single Sign-On Service
if( $service -ne $null )
{
	start-service $service.name
}
get-service BTS* | foreach-object -process {start-service $_.Name} # Start BizTalk Services

Once again I also like to thank my friend Rui Machado for always want and help in all my small challenges, In this particular sample Rui was the creator of the function ChangeSQLProtocolStatus

The script can be found and download on Microsoft TechNet Gallery:
How to set SQL Server Network Protocols in the SQL Server for BTS Databases (7.4 KB)
Microsoft TechNet Gallery

BizTalk Server Installation Scenario

This article explains how to install and configure Microsoft BizTalk Server 2013 on a single computer (development standalone machine) running Windows Server 2012. This information will help you plan the installation and configuration of BizTalk Server 2013, applications and components on which it depends.

We will assume that the machine already have installed the operating system: Windows Server 2012 and latest critical Windows updates from Microsoft.

In this scenario I will perform a full installation of Microsoft BizTalk Server, with the exception of the deprecated SharePoint Adapter (SharePoint Services Service Side Object Model (SSOM)). 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

Important considerations before set up the server

There are some important considerations or suggestions, since some of these operations are not mandatory, that we can set before starting the installation and configuration of the server.

One of the downsides of dealing with a new version of Windows Server is figuring out where things have moved in the new release.

Join the Local Administrators Group

To be able to install and configure BizTalk Server 2013, you have to log on the server using an administrator account on the local computer.

To add a member to a local group using the Windows interface

• Press the “Windows key” to switch to Metro UI.
• Type “Computer Management” and click in “Computer Management” option on Apps menu.

• Right-click the group to which you want to add a member, click “Add to Group”, and then click “Add”.

• In the “Select Users, Computers, or Groups” dialog box, do the following:
  • To add a user account or group account to this group, under “Enter the object names to select” , type the name of the user account or group account that you want to add to the group, and then click “OK”.
  • To add a computer account to this group, click Object Types, select the Computers check box, and then click “OK”. Under “Enter the object names to select”, type the name of the computer account that you want to add to the group, and then click “OK”.

Change the Machine Name

An important consideration that you take into consideration is: if your computer name is longer than 15 characters, BizTalk Server Configuration will not work.

• Start by running the Server Manager from either the Start Screen or the Desktop.
• In the Server Manager Dashboard, click on “Local Server” on the left side.

• In the Server Properties for the Local Server, click in the “Computer name” property to be able to change it

• Click on the “Change” button to edit computer name and domain information, which will pop up this dialog:

Now you can finally change the name of the computer. You’ll have to reboot after you make this change.

Disable IPv6

IPv6 is the latest address protocol that will eventually replace IPv4. Windows Server 2012 kept this protocol enabled by default, but it is also a fact that IPv6 is not yet common and many software, routers, modems, and other network equipment do not support it yet. So it may be a wise approach to disable it for now. Also by turning off it will facilitate the process of detecting which port certain application are listening.

IPv6 can be disabled either through the DisabledComponents registry value or through the check box for the Internet Protocol Version 6 (TCP/IPv6) component in the list of items on the Networking tab for the properties of connections in the Network Connections folder. The following figure shows an example:

Turn off Internet Explorer Enhanced Security Configuration

Internet Explorer Enhanced Security Configuration established a configuration for your server and for Microsoft Internet Explorer that decreases the exposure of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites may not display or perform as expected.

By default, Internet Explorer Enhanced Security Configuration is enabled on Windows Server 2012 and can be configured through Server Manager.

To disable Internet Explorer Enhanced Security Configuration (IE ESC) in Windows Server 2012

• Start by running the Server Manager from either the Start Screen or the Desktop.

• In the Server Manager Dashboard, click on Local Server on the left side.

• In the Server Properties for the Local Server, you’ll see the option for IE Enhanced Security Configuration. Click “On” to change the option.

• A dialog box appears, letting Internet Explorer Enhanced Security Configuration be enabled/disable separately for normal users and administrators, turn off both. After disable both options, click “OK”.
• Click the Refresh button at the top of the Server Manager and the IE Enhanced Security Configuration should now show as “Off”

Disable User Account Control (UAC)

User Account Control (UAC) is a security component that allows an administrator to enter credentials during a non-administrator’s user session to perform occasional administrative tasks.

Whenever you need to configure a Windows Server 2012 setting, even if you are logged on as the administrator – you need elevated privileges.  This is by design, and part of the fierce security initiative in Windows Server 2012. Before you can complete any administrative task, the User Account Control manager pops-up with a ‘Continue’ message.

To Disable User Account Control (UAC):

• Press the “Windows key” to switch to Metro UI.
• Type “Change User Account Control Settings” or “UAC” and click in “Change User Account Control Settings” option on Settings menu.

• Select “Never notify me when…” to disable UAC.

Turn Windows Firewall Off

I always advise you to turn Windows Firewall on BizTalk Server.

To turn Windows Firewall off:

• Press the “Windows key” to switch to Metro UI.
• Type “Windows Firewall” and click in “Windows Firewall” option on Settings menu.

• Select “Turn Windows Firewall on or off” option

• And select the option “Turn off Windows Firewall (not recommended)” in both settings

Configure the Application Event Log

BizTalk Server setup keeps a record of events in the Application Event Log. Depending on the BizTalk Server features installed, the amount of space required in the log may exceed its limit. If the application event log runs out of space during BizTalk Server setup, the installation will fail. To prevent this from happening, you can change the settings in the Application Event Log.

To change settings in the Application Event Log:

• Press the “Windows key” to switch to Metro UI.
• Type “Event Viewer” and click in “Event Viewer” option on Apps menu.

• In the Event Viewer, expand Windows Logs.
• Right-click Application, and then click Properties. This opens the Log Properties dialog box.

• To see how much available space your log has, compare the Log Size field with the Maximum log size field.
• To provide more space in the event log, enter a higher number in the Maximum log size field.
• To enable overwriting of old events when the log becomes full, select Overwrite events as needed.
• To clear the log events, click Clear log.

• Click OK, to close the Event Viewer.

Install Critical Windows Updates

Before installing BizTalk Server or its prerequisites, make sure you have installed the latest critical Windows updates from Microsoft.

To install Windows updates:

• Press the “Windows key” to switch to Metro UI.
• Type “Windows Update” and click in “Install optional updates” option on Settings menu.

• Click “Check for updates” and if exist new updates available, install them

• If prompted, restart your computer

Related links

• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration (Part 4) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 5)
• BizTalk 2013 Installation and Configuration (Part 6)
• BizTalk 2013 Installation and Configuration (Part 7)
• BizTalk 2013 Installation and Configuration (Part 8)

Microsoft Internet Information Services (IIS) provides a Web application infrastructure for many BizTalk Server features. BizTalk Server requires IIS for the following features:

• HTTP adapter
• SOAP adapter
• Windows SharePoint Services adapter
• Secure Sockets Layer (SSL) encryption
• BAM Portal

To install IIS 8, use the following steps:

• Open “Server Manager”.
• Under “Manage” menu, select “Add Roles and Features” (or press “Add roles and features” under the Dashboard panel)

• On the Before You Begin screen, click “Next”

• On the Installation Type screen, select “Role-based or feature-based installation” and click “Next”

• On the Server Selection screen, select the appropriate server, leave the default options and click “Next”
  • Select a server from the server pool
  • local is selected by default

• On the Server Roles screen, select “Web Server (IIS)” option
  • If prompted, click “Add Features”, and then click “Next”

• On the Features screen, no additional features are needed for IIS, however, in addition to the default values, we will need or should select the following options:
  • .Net Framework 3.5 Features
  • SMTP Server (If prompted, click “Add Features”) – optional
  • Windows Identity Foundation 3.5 – optional: Windows Identity Foundation (WIF) is required for the SharePoint Services adapter or SharePoint Online when used with SharePoint Services Client Side Object Model (CSOM).

• Then click “Next”
• On the Web Server Role (IIS) screen, click “Next”
• On the Role Services screen under Web Server Role (IIS), we will customize our installation of IIS with the following options:
  • Common HTTP Features
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • Static Content
  • Health and Diagnostics
    • Http Logging
    • Logging Tools
    • ODBC Logging
    • Request Monitor
    • Tracking
  • Performance
    • Static Content Compression
    • Dynamic Content Compression
  • Security
    • Request Filtering
    • Basic Authentication
    • Digest Authentication
    • Windows Authentication
  • Application Development
    • Select all options
  • Management Tools
    • IIS Management Console
    • IIS 6 Management Compatibility
      • IIS 6 Metabase Compatibility
      • IIS 6 Management Console
      • IIS 6 Scripting Tools
      • IIS 6 WMI Compatibility

• Then click “Next”
• On the Confirmation screen, click “Install”

• When the IIS installation completes, the wizard reflects the installation status on the Results screen
• Click Close to exit the wizard.

Running the BAM Portal in a 64-bit Environment

BAM Portal runs only runs on a 32-bit mode. If you are using Internet Information Services (IIS) in a 64-bit environment, you must set IIS to 32-bit mode to run the BAM portal. To do this, follow these steps:

• Open a command prompt and run the adsutil command. To do this, Press the “Windows key” to switch to Metro UI and type “cmd” and click in “Command Prompt” option on Apps menu.
• Type the following at the command prompt:
  • cscript c:\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
• Close the command prompt.

Or:

· Press the “Windows key” to switch to Metro UI.

• Type “Internet Information Services (IIS) Manager” or “IIS” and click in “Internet Information Services (IIS) Manager” option on Apps menu.
• Expand the server and click on “Application Pools” to display available application pools in center panel.
• Right-click on ‘DefaultAppPool’ and select “Advanced Settings”.

• Change the value of ‘Enable 32-bit Applications’ from False to True. Click OK.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration (Part 4) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 5)
• BizTalk 2013 Installation and Configuration (Part 6)
• BizTalk 2013 Installation and Configuration (Part 7)
• BizTalk 2013 Installation and Configuration (Part 8)

In the previous step “Enable Internet Information Services” I mentioned that we should install the Windows Identity Foundation 3.5 feature, why?

If we plan to use/configure SharePoint Services adapter or SharePoint Online when used with SharePoint Services Client Side Object Model (CSOM), then Windows Identity Foundation (WIF) feature is required.

WIF is required if you are planning to use:

• SharePoint Services Adapter with CSOM
• SharePoint Online with CSOM

WIF is not required if you are planning to use:

• SharePoint Services Adapter Web Service (deprecated)
• No plan to use SharePoint

Windows Identity Foundation is included with the operating system (Windows 8 and Windows Server 2012) as a Feature in Turn Windows features on or off. (if you plan to use Windows 7 and Windows Server 2008 R2 the download is available here Windows Identity Foundation):

If you didn’t previous install WIF then you should following this steps:

· Open “Server Manager”.

· Under “Manage” menu, select “Add Roles and Features” (or press “Add roles and features” under the Dashboard panel)

• On the Before You Begin screen, click “Next”
• On the Installation Type screen, select “Role-based or Feature-based Installation” and click “Next”
• On the Server Selection screen, select the appropriate server, leave the default options and click “Next”
• On the Server Roles screen, click “Next”
• On the Features screen, select "Windows Identity Foundation 3.5" and click “Next”

• On the Confirmation screen, select “Restart the destination server automatically if required” and click “Install”

• When the installation completes, the wizard reflects the installation status on the Results screen
• Click “Close” to exit the wizard.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration (Part 4)  – Coming soon
• BizTalk 2013 Installation and Configuration (Part 5)
• BizTalk 2013 Installation and Configuration (Part 6)
• BizTalk 2013 Installation and Configuration (Part 7)
• BizTalk 2013 Installation and Configuration (Part 8)

Again in the previous step “Enable Internet Information Services” I mentioned that we should install the SMTP Server feature, why?

If you wish to configure BAM Alerts, you must have configured SQL Server Database Mail feature (we will see how to accomplish that afterwards) and I will intend to configure this features using your local SMTP Server.

Note: This type of configuration is optional and you don’t need to install the local SMTP Server, you can configured SQL Server Database Mail feature using an external SMTP.

If you didn’t previous install SMTP Server then you should following this steps:

• Open “Server Manager”.
• Under “Manage” menu, select “Add Roles and Features” (or press “Add roles and features” under the Dashboard panel)
• On the Before You Begin screen, click “Next”
• On the Installation Type screen, select “Role-based or Feature-based Installation” and click “Next”
• On the Server Selection screen, select the appropriate server, leave the default options and click “Next”
• On the Server Roles screen, click “Next”
• On the Features screen, select “SMTP Server” and click “Next”
  • If prompted, click “Add Features”, and then click “Next”
• On the Confirmation screen, select “Restart the destination server automatically if required” and click “Install”:
• When the installation completes, the wizard reflects the installation status on the Results screen
• Click “Close” to exit the wizard.

To configure the SMTP Server you should following this steps:

• Press the “Windows key” to switch to Metro UI and type “IIS 6.0 Manager” and click in “Internet information Services (IIS) 6.0 Manager” option on Apps menu.

• Right click on the SMTP Server ([SMTP Virtual Server #1]) and select “Properties” to open the properties window

Note: For the purpose of this installation, we will assume that email only can be generated from this machine. If the application that generates the email runs on a separate server, you need to grant relaying access for that server in IIS SMTP.

• On the Properties windows, click on the “Access” tab and click “Relay…” under “Relay restrictions”

• On Rely Restrictions windows, click” Add…”

• On Computer window, enter 127.0.0.1 for the address and then click “OK”
  • The Connection setting controls which computers can connect to the SMTP server and send mail. By granting only localhost (127.0.0.1) access limits only the server itself the ability to connect to the SMTP server. This is a requirement for security, it prevents the SMTP server from being an open relay and being used to send unsolicited spam email by other computers on the internet, which could lead to the SMTP server being blacklisted.

• On the Properties windows, click on the “Delivery” tab and click “Outbound Security…”

• On the Outbound Security windows, select “Basic authentication” and enter the login credentials you use for your Exchange or personal account (Gmail, Live and so on). Click “OK” to continue.
  • If required, enable “TLS encryption”
  • This will be the account that will transmitted the emails.

• On the Outbound Security windows, click “Advanced…”. Enter the SMTP server URL you got in the previous step in the Smart host edit box and then click “OK” to continue.

• On the Outbound Security windows, click on “Outgoing connections…” and set the port of your server
  • Limit number of connections to: When the check box is selected, this option specifies the total number of simultaneous outbound connections to all remote domains that can exist at one time. The default is 1,000 connections. The minimum is 1.
  • Time-out (minutes): Specifies the time allowed before an inactive connection is closed. The default is 10 minutes.
  • Limit number of connections per domain to: When the check box is selected, this option limits connections to any single remote domain. The default is 100 connections. This number should be less than or equal to the value for the Limit number of connections to option.
  • TCP port: Designates the TCP port used for outgoing transmissions. The default is port 25. The outgoing port setting can be the same as that for incoming transmissions or it can be different.

• Click “Ok” twice to apply the settings on the SMTP local server
• Right-click “SMTP Virtual Server #1” again, and then restart the service to pick up the new configuration.

Verify Your Installation

The next step is to verify if the SMTP is successful configured by using the simple Telnet Client, however Telnet Client is not installed by default on Windows Server 2012.

To install Telnet Client by using a command line

• Open a command prompt window. , Press the “Windows key” to switch to Metro UI and type “cmd” and click in “Command Prompt” option on Apps menu.
• Type the following command:

pkgmgr /iu:"TelnetClient"

• If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

To send a test email:

• Open a command prompt window. , Press the “Windows key” to switch to Metro UI and type “cmd” and click in “Command Prompt” option on Apps menu.
• Type the following sequence of command:

telnet localhost 25
Helo serevr
mail from:email
rcpt to:email
data
put the body of the email message

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration (Part 5) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 6)
• BizTalk 2013 Installation and Configuration (Part 7)
• BizTalk 2013 Installation and Configuration (Part 8)

Microsoft Office Excel is required for using the Business Activity Monitoring (BAM) feature in BizTalk Server. You use the BAM Office Excel Workbook to define the business processes you want to monitor. You also use the BAM Excel Workbook to define the way in which business users see the data collected by BAM.

Note: BizTalk Server 2013 supports only 32-bit version of Microsoft Office.

The following procedure installs only Microsoft Office Excel. You can install additional Microsoft Office system applications and tools if you wish, but they are not necessary to complete the installation of BizTalk Server.

Note: To successfully load BAM.xla into Excel, install the “Visual Basic for Applications” option under “Office Shared Features”. Otherwise, you may get the error “This workbook has lost its VBA project, ActiveX controls and any other programmability-related features.”

To install Microsoft Office Excel:

• Insert the Microsoft Office installation disk into the DVD-ROM drive.
• On Read the Microsoft Software License Terms screen, select “I accept the terms of this agreement” and click “Continue”

• On the Type of Installation screen, select Custom Install, and then click “Next”.

• On the Custom Setup screen, ensure that:
• Microsoft Excel option is selected.
• And “Visual Basic for Applications” option under Office Shared Features is select.

• And then click “Install Now”.
• On the Setup Completed screen, click “Finish”.

After installing the office Excel and tools I like to do a Windows update, this step is not necessary.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
• BizTalk 2013 Installation and Configuration (Part 6) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 7)
• BizTalk 2013 Installation and Configuration (Part 8)

The BizTalk Server development tools are based on Visual Studio. And like previous versions, at a minimum, you must have the Microsoft Visual C#® .NET component of Visual Studio installed on your computer if you wish to install the BizTalk Server Developer Tools and SDK component.

Note: Visual Studio 2012 is not required if you are installing BizTalk Server on a production computer (runtime only), on which no application development or debugging is required to be done.

The BizTalk Server runtime components require .NET Framework 4.5. In addition, the .NET Framework 3.0 is required if the Windows Communication Foundation (WCF) adapter or WCF Interceptor is installed.

However, unlike previous versions of Visual Studio and the official documentation, with Visual Studio 2012 you cannot customize the features to install to the point of only install Visual C#, at least that I know of.

To install Visual Studio 2012:

• Insert the Visual Studio 2012 installation disk into the DVD-ROM drive.
• On the Start page, accept the license agreement by selecting “I agree to the License terms and conditions” and then click “Next”.

• On the Optional features to install page, you can clear all features, however I think that is important at least to install “Microsoft Web Developer Tools“. Add the following features to your installation:
• Microsoft Web Developer Tools
• Microsoft Office Developer Tools (not required)

• And then click “Install”
• On the Finish page, close the window or click “Launch”.

Important Note: Your version of Visual Studio will include Microsoft SQL Server Express or compact as an optional feature. This feature it may cause BizTalk Server setup to fail and should not be installed but as we cannot customize the Visual Studio 2012 installation, we should remove this features afterwards.

Remove Microsoft SQL Server Express

As I say previous your version of Visual Studio will include Microsoft SQL Server Express or compact as an optional feature. This feature it may cause BizTalk Server setup to fail and should not be installed but as we cannot customize the Visual Studio 2012 installation, it’s very important that we remove this features.

To avoid futures complications I choose to uninstall this two features:

• Microsoft SQL Server 2012 Express LocalBd
• Microsoft SQL Server Compact 4.0 SP1 x4 ENU: Microsoft SQL Server Compact 4.0 is a free, embedded database that software developers can use for building ASP.NET websites and Windows desktop applications. SQL Server Compact 4.0 has a small footprint and supports private deployment of its binaries within the application folder, easy application development in Visual Studio and WebMatrix, and seamless migration of schema and data to SQL Server

To uninstall this features:

• Press the “Windows key” to switch to Metro UI.
• Type “Programs and Features” and click in “Programs and Features” option on Settings menu.

• Select “Microsoft SQL Server 2012 Express LocalBd” and click “Uninstall”.

• Repeat the process, select “Microsoft SQL Server Compact 4.0 SP1 x4 ENU” and click “Uninstall”.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
• BizTalk 2013 Installation and Configuration – Install Microsoft Office Excel 2013 (Part 5)
• BizTalk 2013 Installation and Configuration (Part 7) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 8)

BizTalk Server provides the capability to specify a business process and also a mechanism by which the applications used in that business process can communicate with each other. SQL Server is the main repository for this communication mechanism. For optimal performance, Microsoft recommends using the Enterprise Edition of SQL Server.

Note: Using SQL Server Express Edition is not recommended or supported. The Express edition does not include certain features needed by BizTalk Server.

To install SQL Server 2012:

• Insert the SQL Server installation disk into the DVD-ROM drive. The setup program will begin automatically. If prompted for automatic installation of prerequisite software, click “OK”
• On the SQL Server Installation Center, click “Installation” and then click “New SQL Server stand-alone or add features to an existing installation”

• On the Setup Support Rules screen, review the information and then click “OK”

• On the Product Key screen, enter your product key and click “Next”

• On the License Terms screen, select “I accept the license terms”, and then click “Next”

• On the Product Updates page, the latest available SQL Server product updates are displayed. Select “Include SQL Server product updates”, and then click “Next”

• On the Install Setup files page, Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for SQL Server Setup is found, and is specified to be included, that update will also be installed, Click “Install”
• The System Configuration Checker verifies the system state of your computer before Setup continues.
• If prompted to restart the computer, click "OK”

• On the Setup Role page, select “SQL Server Feature Installation”, and then click “Next” to continue to the Feature Selection page.

• On the Feature Selection screen, select the following features, and then click “Next”
• Database Engine Services
• SQL Server Replication
• Full-Text and Semantic Extractions for Search
• Analysis Services
• Reporting Services – Native
• Shared Features
• SQL Server Data Tools
• Client Tools Connectivity
• Integration Services
• Management Tools – Basic
• Management Tools – Complete

• On the Installation Rules page, Setup verifies the system state of your computer before Setup continues, and then click “Next”

• On the Instance Configuration screen, select “Default instance”, leave the rest of the default values, and then click “Next” to continue.

• Review the information on the Disk Space Requirements screen, this page calculates the required disk space for the features that you specify and compares with available disk space. Click “Next” to continue.

• On the Server Configuration screen, you can specify login accounts for each SQL Server services. You can assign the same login account to all SQL Server services, or you can configure each service account individually. You can also specify whether services start automatically, are started manually, or are disabled (Microsoft recommends that you configure service accounts individually to provide least privileges for each service).
• Leave the default login account to all SQL Server services
• Configure all of them with the startup type: “Automatic”
• And then click “Next”

• On the Database Engine Configuration screen, select “Windows authentication mode”, click “Add Current User”, and then click “Next”
• Authentication Mode: Select “Windows authentication mode”. If you select Mixed Mode Authentication, you must provide a strong password for the built-in SQL Server system administrator account.
• Specify SQL Server administrators: You must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, click “Add Current User”

• On the Analysis Services Configuration screen, select “Multidimensional and Data mining Mode”, click “Add Current User”, and then click “Next”
• Server Mode: Select “Multidimensional and Data mining Mode”. Server mode determines which memory and storage subsystems are used on the server. If you plan to run multidimensional cube databases on the server, choose the default option, Multidimensional and Data Mining server mode.
• Specify which users have administrative permissions for Analysis Services: you must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, click Add Current User.

• On the Reporting Services Configuration screen, select “Install and configure”, and then click “Next” to continue.

• On the Error and Usage Reporting screen, leave the default values, and then click “Next”

• On the Installation Configuration Rules screen, review the information and resolve any issues, and then click “Next”

• On the Ready to Install screen, review the information, and then click “Install”

• On the Complete screen, click “Close”

Note: Once again, after this installation, I like to do a Windows update, this step is not necessary.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
• BizTalk 2013 Installation and Configuration – Install Microsoft Office Excel 2013 (Part 5)
• BizTalk 2013 Installation and Configuration – Install Visual Studio 2012 (Part 6)
• BizTalk 2013 Installation and Configuration (Part 8) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 9) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 10) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 11) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 12) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 13) – Coming soon 

If your BizTalk Server environment uses SQL Server 2012 and you wish to configure BAM Alerts, you must have already configured SQL Server Database Mail feature before you try to configure BAM Alerts, otherwise the BizTalk Basic configuration will ignore this feature (BAM Alerts).

Database Mail is an enterprise solution for sending e-mail messages from the SQL Server Database Engine. Using Database Mail, your database applications can send e-mail messages to users. The messages can contain query results, and can also include files from any resource on your network. You can read more here: http://msdn.microsoft.com/en-us/library/ms189635.aspx

Note: You still can have BAM Portal with activities and aggregations without alerts, this is mandatory if you want alerts.

Before we begin, we need to determine the server name and port number for the Simple Mail Transfer Protocol (SMTP) server that we will use to send e-mail (If the SMTP server requires authentication, determine the user name and password for the SMTP server). In our case will be the local SMTP Server that we previous install and configure.

To Configure SQL Server Database Mail Account:

• Press the “Windows key” to switch to Metro UI and type “SQL Management” or “SQL” and click in “SQL Server Management Studio” option on Apps menu.

• In Object Explorer panel, connect to the SQL Server instance you want to configure Database Mail on, and expand the server tree.
• Expand the “Management” node

• Double click “Database Mail” to open the Database Mail Configuration Wizard.
• Or right click under “Database Mail” and select the option “Configure Database Mail”

• On the Welcome to Database Mail Configuration Wizard page, click “Next” to continue

• On the Select Configuration Task page, select “Set up Database Mail by performing the following tasks:” and click “Next” to continue.
• Set up Database Mail by performing the following tasks: Perform all of the tasks required to set up Database Mail for the first time. This option includes all of the other three options.
• Manage Database Mail accounts and profiles: Create new Database Mail accounts and profiles or to view, change, or delete existing Database Mail accounts and profiles.
• Manage profile security: Configure which users have access to Database Mail profiles.
• View or change system parameters: Configure Database Mail system parameters such as the maximum file size for attachments.

• If Database Mail has not been enabled, you will receive the message: “The Database Mail feature is not available. Would you like to enable this feature?” Click “Yes” to continue.

• On the New Profile page, specify the “Profile name” and “Description” to be included in the profile, and click “Add…” to specify an account

• On the New Database Mail Account page, specify the account name, description, mail server information, and authentication type. Click “OK”
• A Database Mail account contains the information that SQL Server uses to send e-mail messages to an SMTP server. Each account contains information for one e-mail server and doesn’t correspond to a SQL Server account or a Microsoft Windows account. Database Mail can be sent using the credentials of the SQL Server Database Engine, using other credentials that you supply, or anonymously. When using basic authentication, the user name and password in a Database Mail account are only used for authentication with the e-mail server. An account need not correspond to a SQL Server user or a user on the computer running SQL Server.
• Account name: Type the name of the new account.
• Description: Type a description of the account. The description is optional.
• E-mail address: Type the name of the e-mail address for the account. This is the e-mail address that e-mail is sent from. For example, an account for SQL Server Agent may send e-mail from the address SqlAgent@Adventure-Works.com.
• Display name: Type the name to show on e-mail messages sent from this account. The display name is optional. This is the name displayed on messages sent from this account. For example, an account for SQL Server Agent may display the name "SQL Server Agent Automated Mailer" on e-mail messages.
• Reply e-mail: Type the e-mail address that will be used for replies to e-mail messages sent from this account. The reply e-mail is optional. For example, replies to an account for SQL Server Agent may go to the database administrator, danw@Adventure-Works.com.
• Server name: Type the name or IP address of the SMTP server the account uses to send e-mail. Typically this is in a format similar to smtp.<your_company>.com. For help with this, consult your mail administrator. As I say early we will use our local SMTP Server, so the server name will be “localhost”
• Port number: Type the port number of the SMTP server for this account. Most SMTP servers use port 25.
• This server requires a secure connection (SSL): Encrypts communication using Secure Sockets Layer.
• Windows Authentication using Database Engine service credentials: Connection is made to the SMTP server using the credentials configured for the SQL Server Database Engine service.
• Basic Authentication: Specify the user name and password required by the SMTP server.
• Anonymous authentication: Mail is sent to the SMTP server without login credentials. Use this option when the SMTP server does not require authentication.

• Back on the New Profile page, click “Next” to continue

• On the Manage Profile Security page, you will be able to set the Public, Private and Default Profiles, select our profile as public and default and click “Next”.

• On the Configure System Parameters page, leave the default values and click “Next”

• On the Complete the Wizard page, review the actions to be performed and click “Finish” to complete creating the new account.

• On the “Configuring…” page, ensure that all actions succeed and then click “Close”

The Database Mail should now be configured successfully and all should be correctly setup to send emails, but we must make sure by testing it. So we will send a test email and confirm the reception. To do that:

• Right-click on Database Mail and select “Send Test E-Mail…”

• On the Send Test E-mail from windows, specify a “To:” email and click “Send Test E-Mail”

If all goes well you should receive the email in a few seconds. If you have received the email, you have been able to configure Database Mail successfully.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
• BizTalk 2013 Installation and Configuration – Install Microsoft Office Excel 2013 (Part 5)
• BizTalk 2013 Installation and Configuration – Install Visual Studio 2012 (Part 6)
• BizTalk 2013 Installation and Configuration – Install SQL Server 2012 (Part 7)
• BizTalk 2013 Installation and Configuration (Part 9) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 10) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 11) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 12) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 13) – Coming soon 

In this section you’ll install BizTalk Server, confirm that the installation succeeded, and then configure BizTalk Server.

When you installed SQL Server, setup granted your account Database 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.
• Or make sure the account you’re using now also has Database Administrator rights and is also local administrator.

To install BizTalk Server 2013

• Close any programs you have open. Run the BizTalk Server 2013 installer as Administrator.
• On the Start screen, click “Install Microsoft BizTalk Server 2013”

• On the Customer Information screen, type your user name and organization, enter your product key, and then click “Next”

• On the License Agreement screen, accept the license agreement, and then click “Next”

• On the Customer Experience Improvement Program screen, specify whether you want to participate in the program, and then click “Next”
• BizTalk Server 2013 participates in the Customer Experience Improvement Program. As part of this support, you can choose to provide useful feedback to Microsoft regarding feature usage reporting functionality of BizTalk Server. The data collected from you is anonymous and cannot be used to identify you. Microsoft collects feature usage statistics as part of this program. By participating in this program, you can help improve the reliability and performance of various features of BizTalk Server. For more information about this program and its privacy policy, see Microsoft BizTalk Server CEIP Privacy Policy (http://go.microsoft.com/fwlink/?LinkId=188553).

• On the Component Installation screen, review the available components and select the ones you want to install.
• Choose all possible components
• Accept the default installation location or click Browse to move to the location where you want to install BizTalk Server 2013.
• And then click “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”
• Or if you prefer you can select “Automatically install the redistributable prerequisites from a CAB file” if you have already downloaded the CAB file. If you select this, you can then browse to the location of the CAB file and select it.
• And then click “Next” to continue.

• On the Summary screen, verify that the components that you select to install are correct.
• To enable auto-logon after a system reboot, click “Set” and provide your logon information. Auto-logon is enabled only for reboots during setup, and is disabled when setup is complete.
• Click “Install” to start the installation process.

• On the Microsoft Update Setup screen, specify whether you want to use Microsoft Update for checking for regular updates from Microsoft:
• Select “Use Microsoft Update when I check for updates (recommended)”
• And then click “Next” to continue.

• On the Installation Completed screen, clear the “Launch BizTalk Server Configuration” check box, and then click “Finish”

Verify Your Installation

You can check to see whether your installation was successful by using either Programs and Features or the Registry.

To verify installation using Programs and Features

• Press the “Windows key” to switch to Metro UI.
• Type “Programs and Features” and click in “Programs and Features” option on Settings menu.
• When the list is fully populated, look for BizTalk Server 2013. If it appears in the list, setup succeeded.

To verify installation using the Registry:

• Press the “Windows key” to switch to Metro UI and type “regedit” and click in “regedit” option on Apps menu.

• When the Registry opens, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0
• If files exist in the 3.0 folder, setup succeeded.

• Close the Registry, and then close the command prompt.

Configre BizTalk Server 2013

Use the following procedure to complete a basic configuration of BizTalk Server. For information on customizing your configuration, see Custom Configuration.

Note: If your BizTalk Server environment uses SQL Server 2012 and you wish to configure BAM Alerts, you must have already configured SQL Server Database Mail feature.

To configure BizTalk Server 2013 using Basic Configuration:

• Press the “Windows key” to switch to Metro UI and type “BizTalk Server Configuration” or “BizTalk”, right-click “BizTalk Server Configuration” option on Apps menu, and then click Run as Administrator.

• On the Microsoft BizTalk Server 2013 Configuration screen, apply the following configurations and then click “Configure” to continue:
• Select “Basic configuration” option
• In the “Database server name” field under “Database” properties, enter the name of the local computer.
• In the “Service credential” properties, type the User name and Password for the account that the BizTalk services will run under.

• Note: You may receive a warning if you enter a user name with administrative credentials on this computer. Click “Yes” to continue.

• On the Summary screen, review the configuration about to be performed, and then click “Next”

• On the Completion screen, click “Finish”

We now have BizTalk Server 2013 Installed and Configured!!!

Pin BizTalk Server Administration to taskbar

Everybody knows that BizTalk Server Administration Console is the most important tool, it’s a Microsoft Management Console (MMC) that you can use to manage and monitor BizTalk Server, and that you can use to deploy and manage your BizTalk Server applications.

With the new UI in Windows Server 2013, almost all programs are “hidden” and can be easily be accessed through context search from the metro UI. However be constantly doing this type of operation eventually becomes annoying.

So to be able to quickly and easily access BizTalk Server Administration Console you can pin the console to the taskbar, to accomplish that you need:

• Press the “Windows key” to switch to Metro UI and type “BizTalk Server Administration” or “BizTalk” and right click in “BizTalk Server Administration” option on Apps menu to open the option bar at the bottom of the window.
• In the option bar, select “Pin to taskbar” option to add “BizTalk Server Administration” to your desktop taskbar.

Related links

• BizTalk 2013 Installation and Configuration – Important considerations before set up the server (Part 1)
• BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
• BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
• BizTalk 2013 Installation and Configuration – Install and configure SMTP Server Feature (Part 4)
• BizTalk 2013 Installation and Configuration – Install Microsoft Office Excel 2013 (Part 5)
• BizTalk 2013 Installation and Configuration – Install Visual Studio 2012 (Part 6)
• BizTalk 2013 Installation and Configuration – Install SQL Server 2012 (Part 7)
• BizTalk 2013 Installation and Configuration – Configure SQL Server Database Mail feature (Part 8)
• BizTalk 2013 Installation and Configuration (Part 10) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 11) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 12) – Coming soon
• BizTalk 2013 Installation and Configuration (Part 13) – Coming soon