When you install and configure your BizTalk Server environment a bunch of SQL jobs get installed and scheduled automatically. SQL Jobs are crucial to keep the health of your environment. SQL jobs are responsible for variety of things in a BizTalk environments. Some of them include
You navigate to the “Manage Mapping” section and select “SQL Server instances” tab This lists all the SQL jobs that are related to your BizTalk environment. Select the Alarm name (see Manage Alarms) from the drop-down for which you would like to associate the alerts. Select the instance for which you need to set up monitoring/alerting.
Set the value of ‘Expected Job State’ by selecting the appropriate value from the drop-down box
Set the value of ‘Expected Last Run State’ after selecting Expected Job State from the drop-down box
Depending on your business requirements, you can setup the expected state. If all the jobs are in expected state, the overall health will be good (Green).If all the jobs are in expected state, the overall health will be good (Green). For demo purpose, we just set the second job expected state to be disabled, whereas the current state is enabled. As soon as you save the configuration, the icons will turn red as shown below highlighting the SQL jobs are not in expected state.
In addition to the status displayed in UI, BizTalk360 will also constantly monitor your SQL jobs configurations, and whenever it violated the condition, based on your alarm threshold settings it will send you email/SMSalerts. You can see the alert emails coming up every 2 mins (the value we configured while defining the alarm), and the subject will clearly show the type of alarm (“Down”). The subject line will show the environment and the alarm name (ex: “SQL Jobs Health Check”)An example email notification will look as shown below. The summary will be displayed at the top followed by detailed description of each configured job and the threshold.
SQL Server agent is actually a Windows NT service and users can monitor such services with BizTalk360. Let us see how it works!
As a BizTalk administrator to make sure that your NT services are up and running in your BizTalk Server, you always log in to services.msc console to take necessary action against the services.
With BizTalk360, you can perform all the possible operations such as Start, Stop, Pause, and restart as similar as done in services.msc console in Windows. Users don’t need to context switch to the services window on your server for performing the operations. Likewise, users can monitor the NT Services with BizTalk360 itself. Please take a lookout at this blog and this gives a great insight how BizTalk360 monitors your NT services.