Originally posted on: http://geekswithblogs.net/StuartBrierley/archive/2014/03/06/biztalk-360-v7.1-ndash-standalone-installation-and-configuration.aspx
I recently installed BizTalk 360 v7.1 on a standalone server, detailed below are the prerequisites, installation process and some initial configuration that is required when installing as a standalone server instance.
BizTalk 360 Prerequisites
The prerequisites for the installation and configuration of BizTalk 360 are:
Windows Server with a SQL Server Installation – in this case I used a SQL Server Express Installation.
To take advantage of the HTML 5 interface you need to use IE v9 or above or the Google Chrome web browser. With earlier versions of IE the interface reverted to the Silverlight interface.
A BizTalk 360 service account with the following permissions:
Local Administrators Group (in all servers to be monitored)
BizTalk Server Administrators Group
BizTalk Application Users Group
BizTalk Isolated Host Users Group
SSO Administrators Group
IIS_IUSRS group
In addition there are certain SQL select permissions that need to be granted to the BTS_ADMIN SQL role on the BizTalk Server databases:
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
Configure the IIS role:
Open the Server Manager interface, Roles, and select Add Roles to display a list of possible roles.
From the list select Web Server:
On the Role Services screen, select ASP.NET. This will bring up a new popup window to resolve the dependencies as shown below. Click on Add Required Role Services:
Select the following Role Services in addition to the default ones already selected
Security > Select Basic Authentication and Windows Authentication
IIS 6 Management Compatibility > Select all features
Go through the wizard and complete the IIS configuration.
BizTalk360 is dependant on the BizTalk Server Administration component. For a standalone server installation you need to install the administration component from the BizTalk Server installation media. On the component selection screen, just select the Administration Tools and Monitoring section as shown below:
Installing BizTalk 360
Download the latest version of BizTalk360 MSI file from the BizTalk 360 website and execute it as Administrator (either right click “Run as Administrator” or via an Administrator Command prompt).
I was not given the right click "Run as Administrator" option, so I started an Administration command prompt and navigated to the location of the BizTalk 360 msi and began the installation that way:
Select Run:
Select Next:
Accept the license conditions and select next:
The BizTalk 360 Installer will carry out a prerequisite check, if any of these are not green you will need to fix the issue(s) and try again:
Accept the default Virtual Directory name and Application pool name. Enter the User name and Password for the BizTalk 360 service account for this environment:
Enter the BizTalk 360 database details, in this case I was using a local instance of SQL Server 2012 express:
Test the connection to ensure a successful connection can be made:
Close the connection status window and select next.
On the service settings screen change the radio button to use the BizTalk 360 service account.
On the Custom Setup screen select Next:
On the Ready to Install screen select Install:
You will now see the Installing BizTalk 360 screen:
When this completes, you should see the Completed screen:
Select Finish and BizTalk 360 should be started for you:
At this stage I received the following error:
BizTalk Management Database information is missing for the Environment:xxxxx. 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).
To fix this you need to Open SQL Server Management Studio and navigate to the required table:
Looking at the table, there are gaps in the data where the BizTalk Management Database details would otherwise be stored:
You need to update this to point at the database server and BizTalk Management database for the BizTalk Environment to be monitored.
I updated this using the following script:
UPDATE [BizTalk360].[dbo] .[b360_admin_BizTalkEnvironment]
SET BizTalkMgmtSqlInstance = 'MySQLServer', BizTalkMgmtDb = 'BizTalkMgmtDb'
Now when navigating to the BizTalk 360 URL you should get the full BizTalk 360 HTML 5 interface:
Initial Configuration of BizTalk 360
Following the installation of BizTalk 360 you will then need to complete a small amount of initial configuration for the environment(s) to be monitored.
To update the BizTalk Environment settings we first need to navigate to the Settings page. To do this select the “cog” icon at the top of the navigation pane on the left:
Select Environment/Licences to view the existing setup. This will initially reflect the entry we updated in the database earlier:
The name entry reflected the BizTalk 360 server instance rather than the remote BizTalk Server being monitored.
I updated this initial entry for my environment to reflect the actual environment being monitored by updating the Name to a user friendly descriptive name, I also updated the License Key:
If you are going to be monitoring multiple BizTalk Server Groups you can also add these additional environments using the Environment/Licences page and the “Add New” button.
BizTalk 360 should now be fully installed, configured and ready to be set up to monitor your BizTalk Server environments.