• Print
  • Share

Auto-Correct

  • Updated on 23 Jan 2019
  • 5 minutes to read
  • Contributors

What is Auto-Correct

If you are a BizTalk administrator, there may be many times when you have been notified by your colleagues/monitoring system for a potential issue in the BizTalk environment. Upon further analysis into the root cause of the problem, it would be a real simple fix - say, the receive location was accidentally disabled, NT services failing to restart automatically, and so on. These are quite common problems in the day-to-day life of the BizTalk administrator. To solve this specific problem and make the life of BizTalk administrators easy, BizTalk360 offers the "Auto Correct" or "Auto Healing" functionality.

With the Auto Correct functionality, administrators can set up monitoring on any "State-based" artifact and let the monitoring service 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 receive location(s) of an application and additionally set up the auto correct functionality for the Expected State of the artifact (which should be "Started"). Whenever the receive location goes down/gets disabled, 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).

Which are the state-based artifacts for which I can set up Auto Correct functionality?

Auto Correct can be enabled for the following state-based artifacts:

  1. Receive Locations
  2. Send Ports
  3. Send Port Groups
  4. Orchestrations
  5. NT Services
  6. SQL Jobs
  7. Host Instances
  8. Azure Logic Apps

If an artifact is eligible for auto correct, you will notice the "Auto Correct" column in the grid with an Auto Correct drop down option.

BizTalk360-Auto-Correct-Receive-Locations.png

We have also provided the functionality of "how many times the monitoring service can attempt an auto correct" on a particular state-based artifact. For instance, there may be a FTP receive location that is expecting messages from a FTP server and there might be some network issues in the FTP server that has caused the receive location to be disabled. Once the network issue is fixed, its perfectly safe to bring back the receive location, however the administrator must manually log in to the BizTalk Administration Console to get this working. To avoid this manual intervention, administrators can set up the "Max Retry" count in the Auto Correct functionality. This would allow the auto correct (BizTalk360 monitoring service) to continuously try and bring back the receive location to "Enabled State". If the operation was successful within the Max Retry count, the artifact would be automatically healed to ensure business continuity. If the operation was not successful within the Max Retry count, the artifact would move into a Critical state. The monitoring dashboard would display the artifact in Red color. Once the attempt count reaches the Max Retry count, then the auto correct will get reset after the configured x minutes in “Reset Interval”.

An In Depth Look

In this section, we will take a look at the auto correct functionality in detail. As mentioned earlier, auto correct functionality is available for all state-based artifacts such as Receive locations, Send Ports, Orchestrations, NT Services, SQL Jobs, and Host instances. We will take one artifact (say, Receive Location) and explain the different auto correct options available. The functionality works the same for all state-based artifacts.

The first and foremost step to get auto correct functionality to work is to Create a Threshold Alarm, map the artifacts to the alarm, and set up monitoring for the artifacts. Only then you will be able to enable auto correct for the artifact. Click here to read the steps to set up a threshold alarm.

BizTalk360-Auto-Correct-In-Depth.png
BizTalk360-Auto-Correct-Reset.png

  1. Alarm Selection - Select the alarm from the drop down
  2. Artifacts - Select the artifacts for which you want to set up monitoring and auto correct functionality
  • Applications - Receive Locations, Send Ports, Send Port Groups, Orchestrations
  • BizTalk Servers/SQL Servers - NT Services
  • SQL Server Instances - SQL Jobs
  • BizTalk Environment - Host Instances
  1. State-based monitoring - Select the check box against the artifact for which you want to set up monitoring and set the "Expected state" of the artifact
You need to set up monitoring for the artifacts in order to set up auto correct functionality. The Auto Correct option will not be activated unless you set up monitoring for the artifact.
  1. Auto Correct Drop down - The auto correct drop down will not get activated unless you perform activity in Step 3
  2. Enabling Auto Correct - Select the checkbox against the artifact and Enable Auto Correct from the drop down. You will notice Auto Correct gets enabled with a Max Retry count of 5 (default), Attempt count of 0 and Reset Interval count of 0.
  • Max Retries - Click the numeric value and adjust the slider to set the number of retries the monitoring service should attempt
  • Attempt - Shows the number of times the monitoring service has performed the retry operation
  • Reset Interval - Click the numeric value and adjust the slider to set the minutes to reset the auto correct. The reset interval holds a value of minimum 1 to maximum 1440 mins (i.e., 24 hours). By default, the reset interval is 0 which means that reset will not happen.
Auto Correct will execute during every monitoring service run (every 60 seconds)
Once the value of attempt count matches with the maximum retry count (say, Max Retry: 10, Attempt Count: 10,), the auto correct will not execute any further and no alerts will be triggered. If you have configured the alarm to trigger DOWN alert emails, you will receive the DOWN Alert email from BizTalk360 System in this situation. You will also notice the message "NOTE: Maximum auto-correct attempts exhausted" in the monitoring dashboard. However, by configuring the reset interval, to for example 10 minutes, the auto correct will get reset automatically after the configured interval and it will try to recover the artifact to its expected state.
Was this article helpful?