Sapa Shared Services

BizTalk 2010
Installation and
Configuration
Guide
BizTalk 2010, SQL Server 2008 R2, Windows 7, Windows Server
2008 R2

Gyan Chand Kabra

Contents
1

Document Information......................................................................................... 3
1.1

Revision History............................................................................................. 3

1.2

Reviewers and Sign-of..................................................................................3

1.3

References..................................................................................................... 3

BizTalk 2010 64-bit Installation & Configuration Guide........................................3

2.1

Pre requisites............................................................................................... 3

2.2
Add and Configure the Web Server (IIS) and Application Server Roles In
Windows Server 2008 R2......................................................................................... 5
2.3

Configure IIS and HTTP features in Windows 7.............................................27

2.4

Install Microsoft Office 2010.........................................................................28

2.5

Install Visual Studio 2010 Ultimate Edition..................................................31

2.6

Install SQL Server 2008 R2 64-bit................................................................43

2.7

Install SQL Notifications Services.................................................................69

2.8

SharePoint Foundation 2010........................................................................80

2.9

Join the Local Administrators Group...........................................................105

2.10 Configure the Application Event Log..........................................................105

2.11 BizTalk Server 2010 64-bit Installation.......................................................106
2.12 Verify Your BizTalk Server 2010 Installation...............................................115
2.13 Optional Step - Setup Domain Accounts For BizTalk Server 2010..............116
2.14 Configure BizTalk Server 2010...................................................................118
2.15 Enable TCP/IP, Named Pipes protocols and DTC on the Local Host Server. 119
2.15.1 Enable TCP/IP and Named Pipes..........................................................119
2.15.2 Enable DTC on the Local Host Server...................................................121
3

Installing BizTalk Adapter Pack 2010................................................................124

Optional Step - Configure BizTalk Server SQL Jobs...........................................129

Optional Step - Backing Up Custom BizTalk Databases....................................137

1 Document Information
1.1 Revision History
Revision

Description

Revised By

v1.0

Original Version

Gyan
Chand
Kabra

Revised
on
07-Oct2014

1.2 Reviewers and Sign-of

Name

Role

Sign-of comments

1.3 References
Name of Document

Link/Location

2 BizTalk 2010 64-bit Installation & Configuration Guide

2.1 Pre requisites
Install the hot fixes and patches via Windows Update.

Turn of UAC

Set IE ESC to Of for both settings

2.2 Add and Configure the Web Server

(IIS) and Application Server Roles In
Windows Server 2008 R2

Click Next

Check the Web Server (IIS) role and click Next

Click Next

Click Next

Review the informational messages and click Install

You should not see any errors, click Close

Next, add the Application Server Role

Click Next

On the popup window click Add Required Features

Check the Application Server role and then click Next

Click Next

Check all the boxes and click Next

On the popup window click Add Required Role Services

Select the Choose a certificate for SSL encryption later option and click Next
Next, do to the options selected in the Application Server role the Web Server
(IIS) role needs to be updated

Click Next

Click Next

Click Install

Review any messages, above the information message is To configure WS-Atomic

Transactions, run the wsatconfig.exe utility in
C:\Windows\Microsoft.Net\Framework64\v3.0\Windows Communication Foundation
when a certificate is available. This adds a tab on the MS-DTC to allow you to
configure WS-AT. Click Close.

2.3 Configure IIS and HTTP features in

Windows 7
Check all the tick mark as per below screenshot and then press OK

2.4 Install Microsoft Office 2010

Note - If Microsoft Office is not installed in your workstation then do this otherwise
skip this point.
Install Microsoft Office 2010 and select Excel and InfoPath. If you doing BizTalk
work you probably want to leverage InfoPath to enable 3 rd Party form submission
and SharePoint integration

Click Continue, I had already installed Microsoft Word to allow me to document the
installation process

Click Close

2.5 Install Visual Studio 2010 Ultimate

Edition
Note If Visual Studio 2010 is not install then do this point otherwise skip.

Click Install Microsoft Visual Studio 2010.

Click Next

Accept the license terms and click Next

Select Custom and click Next

Uncheck Visual F#, Microsoft SQL Server 2008 Express Service, and then click
Install

Go get a cofee, this will take a while.....

Click Finish

Click Check for Service Releases

Click Install

Close the browser

Install any important updates

Close the Windows Update window

2.6 Install SQL Server 2008 R2 64-bit

Note If it is not installed in your workstation then do it otherwise skip this point
Install SQL Server 2008 R2 64-bit

Click the Installation link

Click on New SQL Server stand-alone installation or add features to an existing

installation link

You want all green check boxes, click OK

Next you will see the Product Key screen, enter your product key, in my case I
installed SQL Server 2008 R2 Developer Edition which is pre-pidded, click Next

Accept the terms and click Next

Click Install

I had two warnings which are listed below, click Next

To fix Windows Firewall warning I opened up TCP port 1433

Select SQL Server Feature Installation and click Next

Select the options above and click Next

You should not see any errors, click Next

Select Default instance and then click Next

Click Next

Click the Use the same account for all SQL Server services button, fill in the
Account Name and Password fields, and set SQL Server Agent to Automatic.
Next, click the Collation tab

Leave the defaults and click Next

Select Mixed Mode, enter a password for sa, and then add your domain account
to the Specify SQL Server administrators list by click the Add Current User button.
Then click on the Data Directories tab

Review and click on the next tab, I only have 1 .vhd so all my stuf is on the C:\ drive

I enabled FILESTREAM to demo the capability, click Next

Click the Add Current User button and then click the next tab

Click Next

Select Install the native mode default configuration option and then click Next

Uncheck the check box and then click Next

Click Next

Click Install

You should see a green checkmark, click Close

2.7 Install SQL Notifications Services

Note If you want to use BAM alerts in BizTalk services then have to install it
otherwise skip this point.
This feature is required for BAM alerts. SQL Notification Services is not included in
SQL Server 2008 R2, you must download the install packages from the Microsoft
Download Center listed under the Feature Pack for Microsoft SQL Server 2005
December 2008 which you can find here;
http://www.microsoft.com/downloads/details.aspx?FamilyID=536fd7d5-013f-49bc9fc7-77dede4bb075&displaylang=en
Scroll down to the bottom of the page to the Files In Download section and
download these packages;
Microsoft SQL Server Native Client X64 Package (sqlncli_x64.msi)

Microsoft SQL Server 2005 Management Objects Collection X64 Package

(SQLServer2005_XMO_x64.msi)
Microsoft SQL Server 2005 Notification Services Client Components X64 Package
(SQLServer2005_NS_x64.msi)
Once you have downloaded and saved of the 3 MSI packages, install the SQL
Server Native Client

Click Next

Accept the terms and click Next

Fill out the form and click Next

Install only the Client Components and click Next

Click Install

You should see a message that it installed successfully, click Finish

Next install the Microsoft SQL Server 2005 Management Objects Collection by
kicking of the
SQLServer2005_XMO_x64.msi

Click Next

Accept the terms and click Next

Fill out the form and click Next

Click Install

You should see a message stating the install was successful, click Finish
Next install the Microsoft SQL Server 2005 Notification Services Client Components
by kicking of the SQLServer2005_NS_x64.msi package

Click Next

Accept the terms and click Next

Fill out the form and click Next

Click Install

You should see a message stating the install was successful, click Finish

2.8 SharePoint Foundation 2010

Note If you want to use SharePoint adapter in the BizTalk then install it otherwise
skip this point.

Click Install software prerequisites

Click Next

Accept the terms and click Next

Click Finish

Click Install SharePoint Foundation

Accept the terms and click Continue

Click Server Farm

Select Complete

Click Install Now

Click Close

Click Next, you will see the popup listed below;

Click Yes

Select Create a new server farm, then click Next

Add the server name of your BizTalk SQL Server, in this case it is the local server,
specify your database access account, then click Next

Enter your Passphrase and then click Next

Accept the default port and click NTLM, then click Next

Review and then click Next

Click Finish

Add SharePoint Central Admin to your list of Trusted sites

Select No, I dont wish to participate and then click OK

Click Start the Wizard

Fill out the form and click Next

Give a Title to your new top-level Web site and then click OK

Click Finish

SharePoint 2010 Central Admin home page

You should have 2 Web Applications (SharePoint 80 and SharePoint Central

Administration v4)

2.9 Join the Local Administrators Group

BizTalk requires you to be a Local Administrator to install and configure BizTalk.
Click Start, Control Panel, Administrator Tools, Computer Management, Local
Users and Groups, Groups, ..Add you user account to the Administrators group

2.10

Configure the Application Event Log

BizTalk logs its events to the Windows Application Event Log. Depending on the
features you plan to install for BizTalk and the current size of the Application Event
Log your installation might fail if the log exceeds its size limit. Also in production
you always want a rolling list of the latest events and do not want your Application
Event Log to become massive in size
Click Start, Control Panel, Administrative Tools, Event Viewer, expand Windows
Logs, and right-click Application, then click Properties, set the Maximum log size
to a reasonable number and select Overwrite events as needed.
Click OK and close the Event Viewer

2.11 BizTalk Server 2010 64-bit

Installation
Download the BizTalk 2010 Developer edition from the microsoft.com site here;
http://www.microsoft.com/en-us/download/details.aspx?id=24433

Click the Install Microsoft BizTalk Server 2010 link

Fill out the form and click Next

Accept the terms and click Next

Click Next

Note - All Additional Software are optional.

Select all the options except Portal Components, Business Activity Monitoring,
and MQ Series Agent. The BAM Portal can only run in 32-bit mode, installing the
other BAM components gives you the BAM API and BAM databases to store events,
then you can create your own portal in SharePoint, ASP.NET, etc. to display BAM
information to your business. Click, Next

Select, Automatically install the redistributable prerequisites from the web and
click Next

Review and click Install

You should see a message that BizTalk was installed successfully, click on the
Logfile link to review the log if any errors were encountered. Clear the check box
and click Finish, BizTalk is now installed but not configured.

2.12 Verify Your BizTalk Server 2010

Installation
Microsoft lists this step in their Installation guide.
Click Start, Run, type regedit, press Enter, then browse to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0 key

If the key exists then your setup succeeded. Also nice to know where this key is so
you can view what version of BizTalk you installed by looking at the ProductEdition
node, now you are now ready to configure BizTalk Server 2010 via the BizTalk
Server Configuration Wizard.

2.13 Optional Step - Setup Domain

Accounts For BizTalk Server 2010
You need to setup some domain accounts for the various pieces of BizTalk Server
2010. Ideally you should have separate accounts for your production environment
then your development/test environments. If you share these accounts between
development and production then you could make a mistake with your password in
the bindings and lock up this account in production causing a host to fail.
Production BizTalk Environment
Domain User Accounts
<DOMAIN>\BTS_Service
<DOMAIN>\SSO_Service

<DOMAIN>\BTS_Host_Ins
<DOMAIN>\BTS_Iso_Host_Ins

Domain Group Accounts

<DOMAIN>\SSO_Admins
<DOMAIN>\BTS_Server_Admins
<DOMAIN>\BTS_Server_Oper
<DOMAIN>\BTS_App_Users
<DOMAIN>\BTS_Iso_Host_Users
<DOMAIN>\SPS_Enabled_Hosts

Dev/Test BizTalk Environment

Domain User Accounts
<DOMAIN>\BTS_Service_T
<DOMAIN>\SSO_Service_T
<DOMAIN>\BTS_Host_Ins_T
<DOMAIN>\BTS_Iso_Host_Ins_T

Domain Group Accounts

<DOMAIN>\SSO_Admins_T
<DOMAIN>\BTS_Server_Admins_T
<DOMAIN>\BTS_Server_Oper_T
<DOMAIN>\BTS_App_Users_T
<DOMAIN>\BTS_Iso_Host_Users_T
<DOMAIN>\SPS_Enabled_Hosts_T

TODO: Need to list permissions needed for the Domain Users and Domain
Groups listed above

2.14

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
Normally you would select Custom configuration and provide diferent User and
Group Accounts on all the screens but since Im just evaluating the BizTalk 2010
Beta I choose Basic configuration in the interests of saving time.

Click Configure

BizTalk is now configured, your screen should have all green checkmarks, close the
BizTalk Configuration Tool, the BizTalk Server is now installed and configured

2.15 Enable TCP/IP, Named Pipes

protocols and DTC on the Local Host
Server
This are two key steps to facilitate transactions and improve performance between
SQL Server and BizTalk Server.

2.15.1
Enable TCP/IP and Named Pipes
To facilitate transactions between SQL Server and BizTalk Server, you must enable
TCP/IP and Named Pipes in SQL Server.
To enable TCP/IP and named Pipes

Click Start, click All Programs, click Microsoft SQL Server 2008 R2, click
Configuration Tools, and then click SQL Server Configuration Manager.
In the left-hand pane, expand SQL Server Network Configuration.
Click Protocols for MSSQLSERVER.
Verify that both TCP/IP and Named Pipes are enabled.
o

If either is not, follow these steps:

Right-click the protocol, and then click Enable.

Note: the Shared Memory protocol should be disabled

In the left-hand pane, click SQL Server Services.

In the right-hand pane, right-click SQL Server (MSSQLSERVER), and click
Restart.

You must restart also the NS$BAMAlerts service.

Close the Configuration Manager.

2.15.2
Enable DTC on the Local Host Server
To facilitate transactions between SQL Server and BizTalk Server, you must enable
Microsoft Distributed Transaction Coordinator (MS DTC) on the Local Host Server
(LHS).
To enable Distributed Transaction Coordinator (DTC) on the LHS:

Click Start, click Run, type dcomcnfg and then click OK to open Component
Services.

In the console tree, expand Component Services, expand Computers, expand

My Computer, expand Distributed Transaction Coordinator, and then click
Local DTC.
Right-click Local DTC and click Properties to display the Local DTC Properties
dialog box.

Click the Security tab.

Ensure that each of the following four options is selected, and all others are
cleared:
o

Network DTC Access

Allow Inbound

Allow Outbound

No Authentication Required

Click OK to close the Local DTC Properties dialog box. If prompted to restart
the MSDTC service, click Yes.
Close Component Services.
Click Start, point to Administrative Tools, and then click Windows Firewall with
Advanced Security.

In Windows Firewall with Advanced Security, click Inbound Rules.

In the Inbound Rules pane, right-click in all Distributed Transaction
Coordinator rules and then click Enable Rule.

In Windows Firewall with Advanced Security, click Outbound Rules.

In the Outbound Rules pane, right-click Distributed Transaction Coordinator
and then click Enable Rule.

Close Windows Firewall.

Click Start, point to Administrative Tools, and then click Services

And restart the following services:
o Right-click COM+ System Application clicks Restart, and wait for the
service to restart.
o Right-click and restart the Distributed Transaction Coordinator service.
o Right-click and restart the SQL Server (MSSQLSERVER) service.
Close Services window.

3 Installing 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.
The BizTalk Adapter Pack 2010 includes support for new versions of the following
line-of-business applications and databases: SAP 7, Oracle EBS 12.1 and SQL Server
2008 R2. The Adapter Pack also provides support for Visual Studio 2010 and .NET
Framework 4.
It is included in both the Enterprise and Standard Editions of BizTalk. When you
install the adapter pack on x64 environment you have to perform a few steps.
These steps were described in earlier versions through installation guides. There
is documentation to install adapters pack, but now during installation one is guided
through the necessary steps.

This is a definite improvement towards installing Adapter Pack on for instance x64
environment as shown on the screenshot above. So first step is installing WCF LOB
Adapter SDK and by clicking on the first step an installer of SDK is launched.

By clicking next and selecting one of installation options the SDK is installed. After
installation you will see that first step is completed in the overall process. Second
step is installation of the Adapter Pack (x86). By clicking Microsoft BizTalk Adapter
Pack needs to be installed an installer is launched again.

After installation of this pack the screen is updated again stating second step is
completed successfully.

You will sometime see windows update screen or screen with question if you want to
join the improvement program. Next step is installing the Microsoft BizTalk Adapter
Pack(x64). Before installing this pack you have to install x86 first, which is
overlooked a lot of times in past by people.

Having installed the x64 Adapter Pack the final step can be performed.

By clicking on Install Microsoft BizTalk Adapters for Enterprise Applications an

installer is launched.

As this installation has been successfully completed the process of installing the
LOB Adapters is complete.

I recommend to always choosing complete installation of SDK, Adapter Packs and

Microsoft BizTalk Adapters for Enterprise Applications. Next step is adding the
appropriate adapters in BizTalk Administration Console.
Note: When installing the adapter pack you do not see a new adapter show up
under the Adapters folder or in the drop down for Add new Adapter.

4 Optional Step - Configure BizTalk Server SQL Jobs

All of the BizTalk jobs are not configured and enabled upon installation. You must
configure and enabled these.
All the BizTalk jobs will have an owner of the user that installed BizTalk. Ideally you
would want to change the owner to sa from your user account on all BizTalk jobs.

View of the BizTalk job status. As you can see 3 jobs are disabled out of the box.
Two BizTalk jobs need to be configured and enabled.

DTA Purge and Archive Job

The original script after installing BizTalk looks like this:
exec dtasp_BackupAndPurgeTrackingDatabase
0, --@nLiveHours tinyint, --Any completed instance older than the live hours +live
days
1, --@nLiveDays tinyint = 0, --will be deleted along with all associated data
30, --@nHardDeleteDays tinyint = 0, --all data older than this will be deleted.

null, --@nvcFolder nvarchar(1024) = null, --folder for backup files

null, --@nvcValidatingServer sysname = null,
0 --@fForceBackup int = 0 -Review the parameters and change them:
declare @dtLastBackup datetime set @dtLastBackup = GetUTCDate()
exec dtasp_PurgeTrackingDatabase 0, 60, 90, @dtLastBackup
NOTE: You have two options, run the dtasp_PurgeTrackingDatabase or
dtasp_BackupAndPurgeTrackingDatabase stored proc. We dont archive to a remote
SQL Server so we implemented dtasp_PurgeTrackingDatabase. If you want keep
your tracking data for a period of a year, it would be best to archive this of to a
remote SQL Server using the dtasp_BackupAndPurgeTrackingDatabase stored proc.
Enable the job and check the job to make sure it ran successfully after the defined
interval

Backup BizTalk Server

This is a critical job that must be setup and configured. It consists of 4 steps.

Step 1: Set Compression Option

exec [dbo].[sp_SetBackupCompression] @bCompression = 0 /*0 - Do not use
Compression, 1 - Use Compression */
Leave the default settings
Step 2: BackupFull
Original script:
exec [dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */,
'<destination path>' /* location of backup files */
Change the location of the backup files to match your environment:

exec [dbo].[sp_BackupAllFull_Schedule] 'd' /* Frequency */, 'BTS' /* Name */,

'C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup' /* location of backup files */
Step 3: MarkAndBackupLog
Original script:
exec [dbo].[sp_MarkAll] 'BTS' /* Log mark name */, '<destination path>' /* location
of backup files */
Change the location of the backup files to match your environment:
exec [dbo].[sp_MarkAll] 'BTS' /* Log mark name */, 'C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup' /* location of backup files */
Step 4: Purge Backup History
NOTE: This is a custom step that has been added to remove backups older than 3
days old so the hard drive does not fill up.
Script:
pathstring = "C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\"
daysBack = 2
Set fso = CreateObject("Scripting.FileSystemObject")
For Each file In fso.GetFolder(pathstring).files
If DateValue(file.datelastModified) < DateValue(Now - daysBack) Then
fso.DeleteFile file.Path
End If
Next
Set fso = nothing

NOTE: You must grant the account NETWORK_SERVICE Modify permissions to the
C:\Program Files\Microsoft SQL
Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup \ directory so it can delete files
if needed, this is the account SQL Server Agent is running as.

Step 5: Clear Backup History

Original script:
exec [dbo].[sp_DeleteBackupHistory] @DaysToKeep=14
Leave the default settings, enable the job, and run the job and make sure it is
successful

The Backup BizTalk Server job can be manually kicked of, you should see no errors.
Next review the Job Activity Monitor

You should see only 1 job not enabled, do not enable this job, it is called by another
BizTalk job. The BizTalk jobs are now configured. You must have one of the host
instances running otherwise the Monitor BizTalk Server job will fail.

NOTE: If you have custom BizTalk databases then you need to perform the steps in
the next section to enable BizTalk to mark these databases for point in time
recovery using the same process as the BizTalk Server databases

5 Optional Step - Backing Up Custom BizTalk Databases

To back up custom BizTalk databases you need a add entries into two BizTalk tables,
see link below;
http://msdn.microsoft.com/en-us/library/aa561198(BTS.10,printer).aspx