Export (0) Print
Expand All

Routine Monitoring Tasks

Performing the following monitoring tasks on a regularly scheduled basis will assist you in keeping your BizTalk Server applications and infrastructure operationally ready.

  • Review all open alerts.

  • Verify that all BizTalk Server computers are communicating with the MOM server or Operations Manager server

  • Use the Group Hub page in the BizTalk Server Administration Console to investigate orchestration, port, and message failures. The Group Hub page provides access to the current real-time state of the system, accessing data in the MessageBox database. You can view all service instances such as orchestrations, ports, and messaging, along with their associated messages. Using the Group Hub page you can perform the following activities:

    • See currently running service instances, such as orchestrations and messaging, and their associated messages.

    • Look into the MessageBox database for a view of the current data and the real-time state of the system.

    • Suspend, terminate, and resume service instances.

    For more information about using the Group Hub page, see Monitoring Using the Group Hub Page.

  • Review warnings (optional).

  • If you are not using MOM 2005 or Operations Manager 2007, then review the event logs at least once per week. The reason for this task is to prevent issues, such as DBNetLib errors going undetected. Service interruption might go unnoticed unless you have a very low latency system. However, some of these errors can indicate a bigger issue (for example, too many hosts or BizTalk Server servers for the number of message boxes, performance issues on the SQL box, etc).

  • Modify the rules to customize the monitoring of your BizTalk Server applications and infrastructure.

  • Run the Performance Analysis of Logs tool (PAL). If your BizTalk Server deployment is fairly constant (for example, new trading partners aren't added routinely, new code is not deployed), you might run Perfmon and PAL once a quarter or even every six months. If your BizTalk Server deployment changes more frequently, you may want to run Perfmon and PAL every couple of months to compare against a baseline. For more information on PAL, see Using the Performance Analysis of Logs (PAL) Tool.

  • Run Perfmon every few months, to once a quarter or even every six months depending on the number of changes occur in your BizTalk Server deployment.

  • Run BizTalk Server 2006 Best Practices Analyzer when the BizTalk Server deployment changes (for example, the addition of new applications or creation of new hosts). You can download the BizTalk Server 2006 Best Practices Analyzer at http://go.microsoft.com/fwlink/?LinkID=86622.

  • Review the effectiveness of the monitoring of your BizTalk Server applications and infrastructure.

  • Create a plan to make any needed changes in monitoring.

Show:
© 2015 Microsoft