Host Instances
  • 03 Sep 2019
  • 4 Minutes To Read
  • Contributors
  • Print
  • Share
  • Dark
    Light

Host Instances

  • Print
  • Share
  • Dark
    Light

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

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. This 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. Setting up monitoring for 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.

image.png

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 is active at any point in 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.

Monitoring Non-Clustered Host Instances

From the version 9.0 phase 2, you are able monitor non-clustered host as same as clustered host instances. To make use of clustered host instance monitoring with non-clustered hosts, the host name should be the same.

Set Up Monitoring for cluster and non-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.

When the monitored clustered host Instance are all down or in the stopped state, then BizTalk360 triggers an alert and also sends the notification through the Email and custom notification channels.

image.png

Setting Auto Correct for Clustered and Non-Clustered Host Instance

With the Auto Correct functionality, administrators can set up monitoring on any "State-based" artefact, 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 cluster and non-cluster 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.

Let’s see the behaviour of cluster and non-cluster host instance auto-correct.

When both of host instances are in stopped state when AtleastOne option is enabled. First it will attempt to start the first host-instance and add a count to the number of attempts. If it doesn’t get started, it will try to start the second host-instance and add a count to the number of attempts. If the operation is successful, the artifact will come back to the Expected State within the next monitoring service cycle (60 seconds). If not, for every 60 seconds it will try to match with the expected state up to the max retry count.

Was This Article Helpful?