How to install and configure

BizTalk360 on BizTalk Server 2013

standalone machine running on

Windows Serve 2012

A Publication of

http://www.biztalk360.com This article explains how to install and con

About the author In the last few years, he has been working implementing integration scenarios and Cloud

Provisioning at a major telecommunications service provider in Portugal. His main focus is on

Integration Technologies using .NET, BizTalk and SOAP/XML/XSLT since 2002.

He is an active member and moderator on the MSDN BizTalk Server Forums, TechNet Wiki

author, code Gallery contributor and was awarded Most Valuable Professional (MVP) for

BizTalk Server by Microsoft since 2010 and MCTS: BizTalk Server BizTalk Server 2006 and

BizTalk Server 2010 certified.

He is also an author of the Blog: http://sandroaspbiztalkblog.wordpress.com , member of

the BizTalk Brazil community: http://www.biztalkbrasil.com.br/, NetPonto community

(http://netponto.org ), member of BizTalk Administrators community:

http://www.biztalkadminsblogging.com , editor of the magazine Programar, public speaker

and technical reviewer of "BizTalk 2010 Cookbook", Packt Publishing book and several

BizTalk white papers.

You can contact Sandro at sandro-pereira@live.com.pt (Twitter: @sandro_asp)

Document Version Author Reviewed By Release Date

V1.0 Sandro Pereira Dhana Krishnaswamy Saravana Kumar

June 2013

Contents

About the author .................................................................................................................................................. 1

1.BizTalk360 Installation scenario ...................................................................................................................... 3

2. Important considerations before set up the server .......................................................................................... 3

2.1 Hardware Requirements .......................................................................................................................... 3

2.2 Software Requirements ........................................................................................................................... 4

2.3 Create a Service Account for BizTalk360 .................................................................................................... 5

2.4 Grant access to following table in BizTalk Management database ............................................................... 6

2.5 Microsoft SQL Server Authentication Modes ............................................................................................. 7

3. Install and configure BizTalk360 ..................................................................................................................... 9

3.1 Install BizTalk360 ..................................................................................................................................... 9

3.2 Verify Your Installation ........................................................................................................................... 16

3.3 Update BizTalk360 License Key ............................................................................................................... 17

3.4 Configure BizTalk360 Window Service ..................................................................................................... 19

3.5 Fixing BizTalk360 shortcuts ..................................................................................................................... 21

4. Troubleshooting BizTalk360 Installation ........................................................................................................ 25

1. BizTalk360 Installation scenario This article explains how to install and configure BizTalk360 in an existing Microsoft BizTalk Server standalone

machine (single computer) running under Windows Server 2012. This information will help you plan the BizTalk360

installation and configuration process and components on which it depends.

We will assume that the machine already have installed all basic BizTalk Server 2013 components like:

Enterprise Single Sign-On (SSO).

BizTalk Group.

BizTalk Runtime.

In this scenario we will perform a full installation of BizTalk360. The following components will be installed:

BizTalk360 – Website

BizTalk360 – Windows Service

BizTalk360 – Database

You can download the BizTalk360 installation package here: http://www.biztalk360.com/content/download. A basic

user registration is required before downloading the BizTalk360 MSI package and you will have a 14 days free trial

key that will be emailed to the registered email address. The trial key is valid for both standard and enterprise

edition and can be tested in as many environment as required.

2. Important considerations before setting up the server Some of the steps outlined here are not mandatory, but it will improve the installation experience and allows

seamless working of BizTalk360 after installation.

This topic lists down all the hardware and software requirements for installing BizTalk360.

2.1 Hardware Requirements The following table shows the minimum hardware requirements for your BizTalk360 computer.

Resource Id Minimum Requirement

Computer and

processor

A computer with an Intel Pentium-compatible CPU that is:

1 GHz or higher for single processors

900 MHz or higher for double processors

700 MHz or higher for quad processors

Hyper-Threading and Dual-Core processors are supported.

The 64-bit versions of BizTalk Server require a 64-bit operating system running on an x64-

based system. Computers based on CPUs that are compatible with the AMD64 (x86-64)

and Extended Memory 64-bit Technology (EM64T) processor architecture are considered

x64-based systems.

Memory 4GB or more

Hard disk 10 GB of available hard disk space for a complete installation including the operating

system and all prerequisite software. The hard disk must be NTFS formatted.

2.2 Software Requirements Installing BizTalk360 on one of the existing BizTalk servers is a straight forward task. Most or all of the pre-requisites

will be present and you can simply run the MSI file from an Administrator command prompt.

This table lists the software required for running BizTal360. You’ll be guided through installation steps for all of these

prerequisites in a later section.

Software Required Description Required for

Microsoft Windows Supported versions: Windows Server 2012,

Windows Server 2008 R2, Windows Server

2008, Windows Server 2003 R2, Windows

Server 2003, Windows 7 and Windows 8.

Internet Information

Services (IIS)

IIS version 8.0 and 7.5 are supported.

To run BizTalk360, despise the standard

features you will need the following IIS roles:

Under Security BASIC AUTHENTICATION and WINDOWS AUTHENTICATION

Under Management Tools IIS

MANAGEMENT CONSOLE and the complete IIS 6 MANAGEMENT COMPATIBILITY roles

Provides a scalable Web application

infrastructure for BizTalk360 Website

and services

Microsoft .NET

Framework

Minimum .NET Framework 3.5 SP1 This is required for all BizTalk360

managed components

Microsoft SQL Server Microsoft SQL Server 2005 or higher (including

Express Edition is supported)

For running the default installation of

BizTalk360 the SQL Server Authentication

Mode must be set to:

MIXED MODE AUTHENTICATION AND USE SQL

SERVER AUTHENTICATION (this will enables both Windows Authentication and SQL Server Authentication)

NOTE: Setting SQL server in MIXED MODE is

not mandatory, it will just make the default

installation work seamlessly. If you wanted to

support only Windows Authentication, you’ll

manually need to correct the connection string

in WEB.CONFIG and

BIZTALK360.MONITOR.EXE.CONFIG file after

installation. In the future versions this step will

not be required.

This is required to accommodate

BizTalk360 Databases

Microsoft BizTalk

Servers

Supported Versions:

Microsoft BizTalk Server 2006

Microsoft BizTalk Server 2006 R2

Microsoft BizTalk Server 2009

Microsoft BizTalk Server 2010

Microsoft BizTalk Server 2013

Microsoft Silverlight Microsoft Silverlight 5.0

Verify your installation by visiting the

Silverlight installation page.

BizTalk 360 is a web based (RIA)

application using Microsoft Silverlight.

BizTalk360 also needs Silverlight on the

machines from which BizTalk360 will be

accessed

The BizTalk360 MSI installer is automated as much as possible to detect all the prerequisite conditions; it won’t allow

proceeding further if it detects any missing components. If any errors are highlighted, the user need to cancel the

setup, correct the highlighted error and rerun the MSI again.

2.3 Create a Service Account for BizTalk360 BizTalk360 requires a service account to run the IIS Application pool and the monitoring service. It’s the best practice

to create a brand new Windows Account (ex: SvcBizTalk360), it’s recommended to create a domain level account for

this purpose. Once the service account is created, then you can add the Service account to following NT Groups

Local Administrators Group

BizTalk Server Administrators Group

BizTalk Application Users Group

BizTalk Isolated Host Users Group

SSO Administrators Group

IIS_IUSRS group

NOTE: If you are adding multiple environments to the same BizTalk360 installation make sure the BizTalk360 service

account is part of all the corresponding BizTalk Server groups (as listed above) in each environment.

To add, view or manage users and groups:

Press the “Windows key” to switch to Metro UI and type “Computer Management” or “Computer” and click in

“Computer Management” option on Apps menu.

On the tree panel (charm bar) in the left side, expand the “System Tools” and then “Local Users and Groups”

option.

2.4 Grant access to following table in BizTalk Management database You can either grant access directly to the service account created above or you can grant access to

“BTS_ADMIN_USERS” SQL role. Since the service account is already added to the BizTalk Administrators group.

To grant access to “BTS_ADMIN_USERS” SQL role:

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 grant the access, and expand the server

tree.

o Expand the SQL Server and “Databases” and click on “BizTalkMgmDb” database

o Right click on “BizTalkMgmDb” database and select “New Query” option

o On the query window type the following and click execute:

GRANT SELECT ON dbo.adm_OtherDatabases TO BTS_ADMIN_USERS

GRANT SELECT ON dbo.adm_Server2HostMapping TO BTS_ADMIN_USERS

GRANT SELECT ON dbo.adm_ServiceClass TO BTS_ADMIN_USERS

GRANT SELECT ON dbo.BizTalkDbVersion TO BTS_ADMIN_USERS

GRANT SELECT ON dbo.adm_BackupHistory TO BTS_ADMIN_USERS

2.5 Microsoft SQL Server Authentication Modes There are two possible authentication modes for the SQL Server Database Engine: Windows Authentication mode

and SQL Server and Windows Authentication mode (mixed mode).

Windows Authentication mode only enables Windows Authentication, whereas mixed mode authentication

enables both SQL Server and Windows Authentication.

In both options Windows Authentication is always available and cannot be disabled.

BizTalk360 support both SQL authentication modes for connecting to the SQL Server that will host BizTalk360

databases, however by default the SQL Server and Windows Authentication mode (Mixed) will be used by BizTalk360.

The installer will create a SQL server user (biztalk360) and configure both the configuration files:

WEB.CONFIG: on the BizTalk360 “Web” installation folder

BIZTALK360.MONITOR.CONFIG: on the BizTalk360 “Service” installation folder

with SQL server authentication to access the back-end database.

If you have already configured the SQL server with SQL Server and Windows Authentication mode (Mixed), everything

should work out of the box. If in case your SQL server is configured for Windows Authentication mode, you’ll see the

following screen when the application launches first time:

If you want to use only Windows Authentication mode, after the installation you will need to change the

BizTalk360ConnectionString in the WEB.CONFIG on the BizTalk360 Web Installation Folder:

You will find the Web.config file in BizTalk360 Web Installation folder that by default is:

o C:\Program Files (x86)\Kavai Ltd\BizTalk360\Web

There you will find two BizTalk360ConnectionString:

o For Windows Authentication mode:

<!--<add name="BizTalk360ConnectionString" connectionString="Data Source=(local);Initial

Catalog= biztalk360;Integrated Security=True" providerName="System.Data.SqlClient"/>-->

Note: This line will be comment

o And for SQL Server and Windows Authentication mode (Mixed mode):

<add name="BizTalk360ConnectionString" providerName="System.Data.SqlClient"

connectionString="Data Source=(local);Initial Catalog=BizTalk360;User

Id=biztalk360;Password=*********;Persist Security Info=True"/>

Change the connection string by uncommenting the first line and commenting the second.

You also need to follow the above steps to change the BizTalk360ConnectionString in the

BIZTALK360.MONITOR.EXE.CONFIG on the BizTalk360 Service Installation Folder:

You will find the BizTalk360.monitor.exe.config file in BizTalk360 Service Installation folder that by default is:

o C:\Program Files (x86)\Kavai Ltd\BizTalk360\Service

To change security SQL Server authentication mode

In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.

On the Security page, under Server authentication, select the new server authentication mode, and then click OK.

In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.

In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be

restarted.

3. Install and configure BizTalk360 This part of the article will focus on installing and configuring BizTalk360.

3.1 Install BizTalk360 In this section you’ll install BizTalk360 and confirm that the installation succeeded. Before you begin the installation

process, make sure the account you logged in is

Local Administrator on the server you are installing BizTalk360, and

The account is also a sys_admin in the SQL server where you’ll configure BizTalk360 database.

To install BizTalk360

Press the “Windows key” to switch to Metro UI and type “cmd” and right click in “Command Prompt” option on

Apps menu to open the option bar at the bottom of the window and select “Run as administrator”.

o Note: If you have previously disable the UAC you don’t need this first step of “Run as an Administrator”,

you can simple execute the MSI.

On the command prompt, navigate to the location where the MSI file is stored and execute the file to launch the

BizTalk360 Installation Wizard.

On the Welcome to the BizTalk36o Setup Wizard screen, click “Next” to continue

On the End-User License Agreement screen, select “I accept the terms of the License Agreement” to accept the

license agreement and click “Next”

On the Prerequisite checks screen, check if all pre-requisite conditions are met and then click “Next”

o If one or more of the prerequisites fail, cancel the installation and make sure that all the pre-requisite

conditions are met before the installation process. If you could not resolve the failure issue please contact

us at support@biztalk360.com

On the IIS Virtual Directory and Application Pool Settings screen, you will be able to select the IIS web site where

you want to create the virtual directory and setup the IIS application pool details that will run BizTalk360,

configure the following settings:

o Under “Select Web Site”, select the IIS web site where you want to create the virtual directory for

BizTalk360

o Under “Virtual Directory Name”, set the name for virtual directory that will host BizTalk360 website.

By default the virtual directory is named as “BizTalk360”

o Under “Application Pool Setting”, you must specify the IIS application pool details which will be

configured for the virtual directory.

Under “Name”, specify the name of the application pool that you want to create.

Under “User Name”, provide a user in which the application pool will run.

Make sure user is part of the following local groups.

o Local Administrators Group

o BizTalk Server Administrators Group

o BizTalk Application Users Group

o BizTalk Isolated Host Users Group

o SSO Administrators Group

o IIS_IUSRS group

Under “Password”, specify the password for the previous user.

Under “Confirm Password”, confirm the password to see if match to the previous one.

o When finish, click “Next”

On the Access for creating BizTalk360 Database screen, you will be able to specify the SQL Server name that will

store the BizTalk360 databases and the database name. We will leave the default values.

o Under “SQL Server Name”, select the SQL Server name and instance that will store the BizTalk360

databases

BizTalk360 will use this server to create a database which will persist some runtime data like

event log entries, throttling counter data and so on.

The default value is “(local)”.

o Under “Database Name”, set the name for the BizTalk360 database.

The default value is “BizTalk360”.

o You can validate the configuration by click “Test Connection”

o If you can connect successfully, click “OK” to close the Connection Status screen and the click “Next” to

continue.

On the Windows Service Settings screen, leave the default value and click “Next” to continue.

o BizTalk360 uses a background Windows service for certain tasks like creating event log data and

persisting in the backend SQL server database, taking care of data purging and so on.

o If you need this to run under different user, the instructions are given below for configuring different

user, do not do it at this step.

On the Custom Setup screen, review the available components and Install.

o Make sure all possible components are selected (by default everything is selected)

o Accept the default installation location or click Browse to move to the location where you want to install

BizTalk360. Please make sure if you change the installation directory, you change for both Website and

Windows service component as changing one will not automatically change the other

o And then click “Next”

On the Ready to install BizTalk360 screen, review if all the information are correct and then click “Install” to start

the installation process.

o The installation process will take a minute or 2 to install all the features.

On the Completed the BizTalk360 Setup Wizard screen, click “Finish” to complete the installation of BizTalk360.

3.2 Verify Your Installation The installation wizard at the end will open the BizTalk360 application in the browser and if all goes as planned you

will be able to access to BizTalk360 as shown in the picture below:

o If you do not see this page but see an error page, please refer the first time Troubleshooting first launch

article at http://support.biztalk360.com/customer/portal/topics/38286-troubleshooting---first-

launch/articles

o BizTalk360 also has a troubleshooter tool which can help you identify the issues and resolve them. Refer

Troubleshooting BizTalk360 Installation for more information.

3.3 Update BizTalk360 License Key From time to time or after you finish the BizTalk360 installation you may need to update the license key in your

environment.

To update BizTalk360 License Key:

Open Internet Explorer and type http://localhost/BizTalk360, and then hit Enter

On the BizTalk360 home page, in the right upper corner click “Settings”

On the Setting option screen, under “Licensing”, click “manage Licenses”.

On the Environments manage Environments page, click “Edit” to show the environment settings.

o On the “License Key” text box replace the existing license for the correct one and click “Update”

You need to refresh the whole browser (Ctrl+F5) for the changes to take effect.

3.4 Configure BizTalk360 Window Service By default, the “Startup type” propriety of BizTalk360 Window Service – “BizTalk360 Monitor”, similar to some of the

BizTalk Services like “Microsoft UDDI Notification Service” and “BAMAlerts” services, its set as “Automatic”, however

this Window Service may not start automatically after a system restart because it depends on other services that

must be fully running, to avoid this behavior you must configure the “Startup type” to “Automatic (Delayed Start)”

option in this service. If you want the BizTalk Windows Service to run on a dedicated user than the local user, the

below steps will guide you to do so. To proper configure the “BizTalk360 Monitor” service:

Press the “Windows key” to switch to Metro UI and type “Services” and click in “View local services” option on

Settings menu.

In the Services window, on the Services (Local) panel select the “BizTalk360 Monitor” service, right click and

select “Properties” option.

On the BizTalk360 Monitor Properties (Local Computer) window:

o On the General tab apply the following configuration.

Startup type: “Automatic (Delayed Start)”

o On the Recovery tab, apply the following configuration:

First failure: “Restart the Service”

Second failure: “Restart the Service”

Subsequent failures: “Restart the Service”

Reset fail count after … day: 1

Restart service after … minutes: 1

o If you want the service to run under different service user, click on Log On tab and Choose “This account”

option and enter the user details.

o Click “OK” to apply the changes and close the window

3.5 Fixing BizTalk360 shortcuts The only problem with the installation process in Windows Server 2012 is the shortcuts created by the MSI. If you try

to open the shortcuts create by default you will get an error saying that this app can’t open.

This is because Windows Server 2012 interprets and processes traditional web links shortcut URL slightly differently.

This traditional shortcuts are from the type Shortcut, this is the type of shortcuts created by the BizTalk360 MSI

installer. To avoid this you must create an Internet Shortcut, to accomplish that:

Press the “Windows key” to switch to Metro UI and type “BizTalk360” and right click in “Open BizTalk360” option

on Apps menu to open the option bar at the bottom of the window and select “Open file location”.

On the shortcut folder,

o Delete the two BizTalk360 shortcuts

o And right click on the folder and select “New Shortcut”

On the What item would you like to create a shortcut for screen:

o On the “Type the location of the item”: place the URL or BizTalk360 application

Default value is : http://localhost/BizTalk360/

o And then click “Next” to continue

On the What would you like to name the shortcut screen:

o On the “Type a name for this shortcut”: insert the name that you want to give for the shortcut

Type “Open BizTalk360”

o Click “Finish”.

Do the same process to the Documentation shortcut.

o On the “Type the location of the item”: “http://support.biztalk360.com/”

o On the “Type a name for this shortcut”: “Documentation”

4. Troubleshooting BizTalk360 Installation If you face any issues post BizTalk360 installation BizTalk360 trouble shooter tool will help you figure out if there is

any steps you may have missed or not covered in that document adequately.

Download load the BizTalk360 Troubleshooter from http://blogs.biztalk360.com/introducing-biztalk360-

troubleshooter/ . In order for the troubleshooter to do the necessary checks it needs to be run as Administrator.

This tool does not make any changes to your environment.

o Right click on the Troubleshooter exe and select Run as administrator

o On the password boxes, enter the IIS App Pool user’s password and BizTalk360 Monitoring service user’s

password and click “Troubleshoot BizTalk360”.

The troubleshooter will show red boxes where there is a misconfiguration or errors. o Fix all the errors reported and re run the troubleshooter to make sure there are no more errors. Now

biztalk360 should launch and work.