• Print
  • Share

Host Instances

  • Updated on 18 Jun 2018
  • 4 minutes to read
  • Contributors

The first step in monitoring BizTalk Environments is to set up monitoring of Host Instances. One of the advantages of using BizTalk360 to monitor host instances is that you can set up monitoring not only on 'Started' state but also on other different states such as Stopped, Disabled, At Least One Active (used for clustered host instances). For instance, you may have left the state of a particular host instance in the Disabled state and forgot to turn it back to the Enabled state. Therefore, by setting an alarm on the actual status (Enabled), the system sends a warning alert email indicating that the host instance is in the Disabled state.

Assigning the expected state of a host instance to At Least One Active can only be done for clustered host instances. When this is assigned the monitoring service will verify that across all the instances for the clustered host, one host instance is active, guaranteeing that the service is running and no downtime happened for that host.

Setting up monitoring for Host Instances

  • Log in to the BizTalk360 application
  • Click 'Monitoring' in the navigation panel
  • Click the expand button against 'Manage Mapping' tab and select 'BizTalk Environment' link
  • Select the Alarm name (See Creating an alarm) from the drop down for which you would like to associate the alerts
  • At the tab pages with system resources at the top, select Host Instances
  • Select the check boxes against the host instances that you wish to monitor
  • Set the value of Expected State by selecting from the values from drop down. For instance, if the current state of the host instances is Stopped, you need to set the value in the drop down to Started. This will trigger a notification email/SMS to the administrator about the status change

Host-Instances-monitoring.gif From the Health Monitor alarm, the BizTalkServerApplication Host Instance needs to be monitored, to be in the Started state. In case the Host Instance is stopped, BizTalk360 should automatically try to start the Host Instance, so Auto Correct needs to be Enabled

Auto Correct Functionality

With the Auto Correct functionality, administrators can set up monitoring on any "State-based" artifact and let the monitoring service try to automatically heal the artifact any time when there is a mismatch between the "Expected State" and "Current State". For instance, administrators can set up monitoring on the Host Instances and additionally set up the auto correct functionality for the Expected State of the artifact (which should be "Started"). Whenever the host instance gets stopped, there will be a mismatch in the state and the auto correct will try to bring the artifact back to the expected state. If the operation is successful, the artifact will come back to the Expected State within the next monitoring service cycle (60 seconds). Assuming you are still on the Host Instances screen, follow below steps to setup Auto Correct for Host Instances:

  • Select the check box of the Host Instances for which you want to setup Auto Correct, click Auto Correct drop down, and select Started
  • Auto Correct will be enabled for the Host Instances with the default values for Max Retry as 5 and Retry Count as 0

Monitoring Clustered Host Instances

To achieve high availability for adapters that cannot have multiple host instances running at one point in time, BizTalk allows you to cluster hosts using Windows Failover Clustering which will make only one host instance running for the clustered host and in case of any failure it will failover by running the host instance in a different server.

BizTalk360 has the capability of monitoring clustered host instances. Monitoring clustered instances is the same as monitoring all other artifacts in a BizTalk server environment. You need to Create an alarm and associate the alarm with the artifacts in order to be able to monitor the host instances. In this case, configuring monitoring for clustered host instances happens in the same place as normal host instances under BizTalk Environments.

For a non-clustered host instance, you can monitor them on one of the following states — Started, Stopped, or Disabled. However, for a clustered host instance (since only one needs to be active at any point of time), you need to monitor by choosing the state — At Least One Active. Monitoring on this expected state will keep a watch on the clustered host instance to see if one of the two host instances are active at any point of time. If no host instance for the clustered host is active BizTalk360 will trigger an alert and a notification will be sent to your notification channels.

BizTalk360-Monitoring-BizTalk-Clustered-Host-Instances-Select-Host-Instances.png

Set Up Monitoring For Clustered Host Instances

  • Log in to the BizTalk360 application
  • Click 'Monitoring' in the Navigation panel
  • Click the expand button against 'Manage Mapping' tab and select 'BizTalk Environment' link
  • Select the Alarm name (see Creating an alarm) from the drop down for which you would like to associate the alerts
  • At tab pages with system resources at the top, select Host Instances
  • Select the check boxes against the clustered host instances (BizTalkServerApplication) that you wish to monitor
  • Set the value of Expected State as AtleastOneActive by selecting from the values from drop down. Setting the value as AtleastOneActive sets the value to both the clustered Host Instances
  • When there is a violation in the threshold, BizTalk360 triggers an alert and sends the notification through the notification channels