System Center Operation Manager (SCOM) is an enterprise class monitoring tool that is a part of the System Center Enterprise Suite family of products from Microsoft. SCOM offers monitoring for Windows systems, some UNIX/Linux systems, and various other devices. SCOM has the capability to monitor the entire data center infrastructure such as SQL, Windows, IIS, SAN, and so on, and can also be used to monitor BizTalk servers. SCOM has a dedicated Management Pack to monitor the BizTalk servers. The management pack defines the set of rules that determines what SCOM has to monitor in the infrastructure.
Tools like SCOM offer a wide array of functionalities to monitor the server infrastructure. But when it comes to monitoring BizTalk servers, things are different. The SCOM team in an organization needs to have the understanding about BizTalk servers in order to set up the integration, and the same is the case with the BizTalk server management team. Also, configuring SCOM for BizTalk server management is a time consuming process. Another challenge is that BizTalk production support people prefer to use BizTalk Admin Console to view the alerts rather than the SCOM console as they are accustomed to using the tool. Therefore, the lack of understanding between the two teams and the preference to stay away from complex solutions leads to having a heavily invested solution in your organization that is not fully utilized to its potential.
To overcome these problems with monitoring BizTalk servers, you can deploy BizTalk360 in the server infrastructure. BizTalk360 is focused towards offering monitoring capabilities for BizTalk servers and has more powerful functionalities than a general purpose monitoring tool. In addition, you can take full advantage of BizTalk360's unique monitoring and notifications capabilities that are specific to BizTalk servers.
How does BizTalk360 integrate with SCOM?
Every monitoring tool (such as HP OpenView, SCOM, and so on) has the capability to listen to any event viewer. BizTalk360 has the capability to write the events into the event viewer as a part of the notification channel. We have made the event viewer as the bridge between SCOM and BizTalk360 to achieve the integration. To allow BizTalk360 log the events to event viewer, some basic settings need to be done while creating an alarm. You need to enable the option of allowing events getting logged into the event viewer with a specific id. Once the events are generated, they will be written into the standard Windows Event Viewer. SCOM can be configured to pick up these events and display them in its own console.
Setting up event logging in BizTalk360
In BizTalk360, users can set up event logging against a specific event id while creating an alarm. You need to set up the advanced settings (under create alarms) to be able to log the events to an event viewer. Follow the steps 1–9 as mentioned in Creating an alarm section. In the Advanced Setting page;
Log Events to Event Viewer — Select the check box to log events to Event Viewer. Enter the specific event id in the text box provided. This is the id against which the events will be generated in the event viewer
Save the alarm information
Click the sliders to view the process of setting up event logging in BizTalk360.
Check out this whitepaper that compares the capabilities of the two monitoring solutions and provides an independent view of the strengths and weaknesses of both the products for BizTalk Server Monitoring.