When messages flow into the BizTalk server, they pass through BizTalk server's Publish-Subscribe messaging engine architecture. The messages get persisted in BizTalk server's MessageBox database along with the message properties, subscriptions, orchestration states, tracking data and many more information. Within the publish-subscribe architecture, the service instances such as the receive ports, orchestrations, and send ports process the message and there may be situations when the service instances move into a certain state such as Suspended (Resumable), Suspended (Non-Resumable), Active, Ready to Run, Dehydrated, Completed, and so on. Once the service instance moves into a particular state that demands user intervention, this forces the BizTalk server administrator to manually log in to the BizTalk Server Administration Console and fix the problem w.r.t. the service instance. BizTalk360 solves this problem through the Message Box (Queries) offering that allows administrators to query the message box database for such messages and take action without having to log in to BizTalk Server Administration Console. For more information about BizTalk360 Message Box (Queries) concept, click here.
Despite offering this capability to BizTalk administrators, BizTalk360 goes one step further to reduce the manual intervention that is required from the administrators. Through the Message Box Data Monitoring concept, administrators can choose what they need to do when a service instance becomes suspended by setting an alarm. For e.g., the administrator can set up an alarm like "If there are >20 Suspended Service Instances between 09:00 AM and 05:00 PM, suspend all the instances". He can simply log in to the BizTalk360 Data Monitoring Dashboard to see the status of the message box data for the day. He can also set up email notifications for the alarm. By doing so, it eliminates the administrator to often log in to the BizTalk360 application and check for the status of the service instances.