View the latest version.Version 8.0

In BizTalk360, the BizTalk360 monitoring service plays the key role as it is responsible to fetch the status of artifacts from the BizTalk server. When the monitoring service accidentally stops running, you will not receive any notifications about threshold violations in the environment. The alternative to this problem would be to cluster the monitoring service using the Windows Failover clustering mechanism. There may be situations when the BizTalk environment does not have a failover clustering mechanism. To solve this problem and to make the BizTalk360 monitoring service more robust, BizTalk360 offers High Availability as an out of the box functionality. (from v6.0 onwards). 


Achieving High Availability in BizTalk360

To achieve HA, you need to install the BizTalk360 monitoring service on multiple servers and point them to the same BizTalk360 configuration database. The services will do regular self-health checks to make sure at least one of them is active. Depending on the status of the active server, BizTalk360 will trigger alerts and notifications for the health of the artifacts at periodic intervals. BizTalk360 considers one of the servers to be the primary server while it treats the other to be secondary.


High Availability  Status


UI Improvements to Activate the monitoring service

You can manually change a passive server to the active state by selecting it and clicking on the Active button. Instantly, the passive server becomes active and switches to be the primary server.


HA Status


Similarly when one of the BizTalk server fails, the BizTalk360 monitoring service will realize that one of the instance has failed and immediately the second node (server) takes over the role of primary. You can have preconfigured alerts for this scenario so that you will get a notification when either of the servers have an unexpected failure. When the stopped server/service comes back online after a period of time, they will automatically be set to the passive state as the other server is currently the active one.


HA Status - Only 1 Active


Setting up High Availability monitoring

  1. Log in to the BizTalk360 application
  2. Click 'Settings' (gear icon) located at the top of the page
  3. Click 'BizTalk360 Health' in the Menu panel on the left side of the screen
  4. Click High Availability Status
  5. If your environment has multiple registered servers, you will notice one server is active (primary) and the other ones are secondary
  6. Active - Selecting and clicking the Active button will make the selected server as active (primary) and switch the remaining ones to secondary
  7. Last Live Time - Indicates the last recent time till when the servers were active and running. When a server accidentally stops running, the last live time will help you with the time to look into the event logs to ascertain the cause of failure.