View the latest version.Version 8.0

Installing BizTalk360 on one of the existing BizTalk servers is a straight forward task. Most of the prerequisites will be present and you can simply run the MSI file from a Administrator command prompt. But some customers prefer to install BizTalk360 on a standalone server and point to various remote environments. This gives them bit of confidence since nothing gets installed on the production BizTalk servers. BizTalk360 doesn't use any agents, so there won’t be any footprint on the real BizTalk servers. The only requirement is for the service account to have adequate permission to query the remote servers. In this article we will cover in detail the steps required to install BizTalk360 on a stand-alone (non BizTalk) server.


To understand the setup process, let us start from a clean setup of Windows Server 2008 R2. You can download the latest version of BizTalk360 MSI file from the website http://www.biztalk360.com/free-trial/ and execute it as administrator (either right click “Run as Administrator” or via Administrator Command prompt).


Step 1 – Run the BizTalk360 MSI

Run the BizTalk360 MSI. After the welcome screen, the installer will verify the prerequisites in your server environment. Since this is a fresh setup, much of the prerequisites will not be validated. You will notice a 'Red error icon' against the items that are not validated.



Step 2 – Install .NET 3.5 SP1

To install .NET 3.5 SP1 on your server, follow the steps as shown below:

  1. Open the Server Manager interface. Select Features from the left menu, and click Add Features. This displays the list of features.
  2. In the Select Features interface, expand .NET Framework 3.5.1 Features
  3. Once you expand .NET Framework 3.5.1 Features, you will see two check boxes. One for .NET Framework 3.5.1 and other for WCF Activation. Select the check box next to .NET Framework 3.5.1 and click Next.
  4. Click Install in the Confirmation page. You will see the installation progress
  5. Click Close to close the wizard once the framework has been installed


Step 3 - Add IIS Roles

Once you have set up the .NET 3.5.1 Framework, the next step is to install IIS (Web Server) and the required modules to support running BizTalk360. To install IIS, follow the steps as shown below:

  1. Open the Server Manager interface. Select Roles from the left menu, and click Add Roles. Click Next in the Before You Begin screen.
  2. Select Web Server from the list and click Next
  3. On the Role Services screen, select ASP.NET. This will bring a new popup window to resolve the dependencies as shown below. Click on Add Required Role Services
  4. Select the following Role Services in addition to the default ones already selected — Security > Basic Authentication, Windows Authentication, Complete IIS 6 Management Compatibility (select all the items in the list)
  5. Click Install in the Confirmation screen
  6. Click Close to close the wizard once the roles have been set up
  7. Once you have done Step 2 and Step 3, try to run the BizTalk360 Installer MSI once again. In the prerequisite checks section, you will notice that now most of the items will be verified and have the green tick mark against them. The only one item that will have the Red Error mark is Supported BizTalk servers (2006 R2, 2009, 2010, 2010 R2). To resolve this issue, you need to install the BizTalk server in your server.


Step 4 – Installing BizTalk Administration Components

To resolve the issue mentioned above, run the original BizTalk Server installation Setup.exe file. On the component selection screen, just select Administration Tools and Monitoring section. As you can witness, you don’t need to install any other components of BizTalk server. Make sure you install the correct version of BizTalk administration components. Ex: If you are going to monitor a remote BizTalk 2009 environment, then you need to install BizTalk Server 2009 administration components.



Step 5 - Service Account Requirement

Once all the prerequisite validations are over, run the MSI again. On the IIS virtual directory screen, you’ll be able to provide the IIS application pool name and the identity. You need to provide a domain account, since you are going to access a remote environment. The service account should have adequate rights to access the remote environment. Click here to know how to set up the following prerequisites on your server environment.



Once you have made the prerequisite settings, in addition, make sure the service account is having “Log on as Service” rights in the server where you are installing BizTalk360. Use the same domain account when configuring the monitoring services screen.


If you encounter the following error during installation, click on “Ignore” button, we can start the service later via the services snap in.



Launching BizTalk360 For The First Time

After successful installation, when you launch BizTalk360 for the first time, you may see an error message as follows:

BizTalk Management Database information is missing for the environment: <environment name>. If you have installed BizTalk360 on a standalone server, where BizTalk server is not configured you will receive this error. You can correct this by manually entering the details in the table b360_admin_BizTalkEnvironment (columns BizTalkMgmtSqlInstance and BizTalkMgmtDb).


When you install BizTalk360 on an existing BizTalk environment, the installer will read the management database details from the registry and stores it in the BizTalk360 database and everything will work seamlessly. But in our case we are installing BizTalk360 on a complete standalone server and there is no trace of the remote BizTalk environment we are going to configure. In order to fix this issue, open the BizTalk360 database, edit the table b360_admin_BizTalkEnvironment table, which will look as shown below (without management database details).


Simply enter the corresponding values for BizTalkMgmtSqlInstanceName and BizTalkMgmtDb columns as shown below:


You can only add the same version of BizTalk environments. 


Example: If you installed BizTalk 2010 administration components, then you can only add any BizTalk 2010 environments. If you try to add a mismatched BizTalk versions (example you installed BizTalk 2010 Administration components but trying to configure a BizTalk 2006 R2 environment), you will see the following error message:


The database or the database version is incompatible with the installed version of this product.