BizTalk Application context
The existing BizTalk Management Pack does a good job in discovering all BizTalk components. It also includes a number of useful monitors and rules but still it isn’t super Helpdesk/non-BizTalk user firendly.
How can you overcome this problem? By creating your own custom BizTalk Addon Management Pack.
A typical BizTalk Application consists of “Receive port(s) & Receive location(s)” an “Orchestration” which processes the incomming messages and one or more “Send ports” to forward the processed messaged to another source.
Knowing this makes it possible to create a “Distributed Application” for each one of your BizTalk Applications.
Creating your “Distributed Application”
Once you have a good understanding of how your BizTalk Application is constructed, you can go into SCOM Authoring and create your DA. In my example I have added a TCP Port check to ensure availability of the Receive port that is used.
After Authoring your DA, you can view your Distributed Application under the Monitoring Pane. My BizTalk application is a bit faulty.
Exposing your work
Next step is to expose your work to the colleagues. You can do this by Creating a “BizTalk Addon Management Pack Folder”. In this folder you can create alert & diagram views.
In the BizTalk 1st line Alerts view, you should filter alerts. This way your 1st line helpdesk isn’t spammed with all the biztalk alerts. You can use a Group and the condition criteria to do this.
There’s a lot more you can do to improve and elevate your BizTalk monitoring. I.e. a scripted monitor that counts the number of suspended messaged, a Distributed Application for the Shared BizTalk components, etc… Common sense and someone that masters BizTalk will help you in doing this.
Hope you get the idea of elevated BizTalk Monitoring.