WebSphere MQ (WMQ) has long been recognized as one of the most dependable middleware solutions in the marketplace. When it comes to managing WMQ, there are some important questions that IT managers need answers to. Let’s look at some of the WMQ questions that need answers.
Why is event-based WMQ monitoring inadequate?
The reason event-based Websphere MQ monitoring is inadequate for monitoring the health of your middleware is that WMQ is only one component in your IT infrastructure. You may also have Oracle databases, an ERP system like SAP, an ESM like IBM’s Tivoli, HP OpenView or CA Unicenter, a network communications platform such as TIBCO, operating systems including UNIX, Windows, Linux and various mainframe operating systems, assorted web servers, etc.
In any given day, each of these components generate thousands of static events and alerts. Add the sheer volume of information generated by the interaction of WMQ with these other components, and the task of identifying a WMQ problem becomes time consuming and almost overwhelming.
The major problem with event-based monitoring is the fact that it can miss problems entirely when they are caused by the convergence of disruptive conditions, bottlenecks, disconnects or failures in the interactions between WMQ and the other infrastructure components.
Why do event-based WMQ monitoring tools fail to detect problems?
Event-based WMQ monitoring tools are designed so monitor the internal functioning of WMQ. Many problems caused by the interaction between external applications are not visible to component-centric monitoring tools.
Is there a solution that overcomes WMQ’s limitations?
Yes, there is a solution that resolves the limitations of WMQ’s self-monitoring tools. Business transaction performance (BTP) software addresses the limitations of event-based WMQ monitoring. BTP is possible because the development of complex event processing (CEP) has reached the stage where it is able to analyze the information generated by WMQ and all the other applications within the IT infrastructure.
What is complex event processing and why is it important to a WMQ monitoring solution?
Complex event processing began as a way to help users define financial event patterns. It has expanded to monitor far more than the stock market. Definitions can be generated automatically by the data flowing into the processor itself. Once a business “normal” has been established, CEP can alert IT to impending business “abnormal” situations.
This is an important development, because it automates much of the detection process. CEP makes real-time visibility from end-to-end through the WMQ middleware layer an automated process, not something that has to be coordinated between a dozen different application dashboards. This saves IT staff considerable time.
Not all problems occur in WebSphere MQ’s middleware layer. Having a tool that identifies where the real problem resides cuts down the mean time to know (MMTK), which in turn cuts down mean time to repair (MMTR) times. This all reduces business operation costs.