Its midnight, and suddenly your phone rings – “Mike, our purchase department guys say they have not received the latest invoices from our FTP location.” Frustration takes a heavy toll and with a grumpy mood, you turn on your BizTalk Administration Console to realize – “Oh no! The receive location is (again) disabled – that’s the reason the purchase department haven’t received the invoices!!” As a BizTalk administrator, how many times have you been in such a situation when all it required was to simply re-enable the receive location. A few other scenarios could be when you deploy a new version of a BizTalk MSI, and forget to start all the applications (and, its artifacts too!!), failure of an NT Services to automatically get back to running state after a server patch, etc.
We understand the frustration in these situations and that’s the reason we’ve tailor-made a feature that will help you to proactively handle these situations in a relaxed way.
Auto Correct works with artifacts that support State-Based monitoring in BizTalk360; such as:
It’s simple – you want your artifact to be “Started” (the expected state!) at all times. By any chance, the artifact goes down for some specific reason, BizTalk360 Auto Correct feature will get it back to the expected state automatically. Comforting, isn’t it?
You can define how many times the monitoring service must try and attempt to bring the artifact back to the expected state. You can set a minimum retry count of 3 to maximum of 10. We also give you an update on the number of attempts. The attempt count resets to 0 when things are back to normal.
We’ve included BizTalk360’s most useful feature – Notifications – with Auto Healing functionality. Get notified with the detailed status information of auto correction operation that has happened on a particular artifact.
Of course – the basics of Monitoring will apply! You must create an alarm, map the alarm to the (state-based) artifact, and then set up auto healing for the artifact.
Once again, BizTalk360 is known in the market for its intelligent auditing capabilities that will help administrators to find out “Who did what in the environment”. Track your artifact level operations under “Application Activities” and “Host Instance Activities”.
We have rolled out auto healing to several parts of our BizTalk environment and it has added tremendous value. If we configure a receive location to a long period of retries we end up without any notification until the receive location shuts down, and if we configure it for a shorter period, it goes down during routine patches and reboots which requires manual intervention to bring back up. With auto healing, I can have the best of both worlds, I get the quick notification and BizTalk 360 handles the extra retries that I need to survive a service interruption and avoid an after hours phone call.