Integrating with BMC Middleware Management

Infrastructure Management integrates with BMC Middleware Management to identify middleware and transaction problems that affect service delivery. It monitors middleware software and hardware, including IBM WebSphere DataPower Integration Appliance, and provides insight into the overall end-user experience for non-web applications.

BMC Middleware Management including both the TrueSight Middleware Monitor and TrueSight Middleware Transaction Monitor integrates with BMC ProactiveNet at both the data and event levels.

TrueSight Middleware Monitor (BMM) tracks all key properties of middleware infrastructure including IBM WebSphere MQ, IBM Integration Bus (also known as Message Broker), IBM DataPower, IBM WebSphere Application Server, TIBCO EMS, TIBCO Rendezvous and more. Examples of BMM data include the rates of messages through queues, the elapsed time in IIB Message Flows or DataPower Multi-Protocol Gateways, the CPU usage of DataPower Devices, and so on.

TrueSight Middleware Transaction Monitor (BMTM) tracks transactions as they move through middleware components listed above as well as web servers such as Apache, Microsoft IIS, and more. BMTM monitors the time taken by individual transactions between any arbitrary set of "touchpoints".  These metrics are then also rolled up into Min/Max/Avg for all transactions over each interval.  Additionally, BMTM views the payload of individual transactions and can group transactions according to the value of any payload field for tracking and statistical purposes. Finally, BMTM calculates summary metrics on business value payload such as order amount or loan value.

All numeric field monitored by BMM and BMTM are made visible as metrics in BMC ProactiveNet through the MTM KM (Monitor to Monitor KM that is supplied as a part of BMM/BMTM).  Thus, all such metrics are eligible for standard BMC ProactiveNet baselining, alerting, and incorporation into service models.

Additionally, BMM/BMTM provides internal event generation. BMM/BMTM allows the definition of event triggers based on any boolean combination of monitored properties. For example, the rate at which messages are being read from an MQ queue is zero while the current depth of that queue is greater than zero and the status of the DataPower MultiProtocol Gateway that must read the queue is zero ("Not Running"). All such events can be directed to BMC ProactiveNet out-of-the-box using the msend command.  BMM/BMTM provides a BMTM.baroc file for this purpose and populates all standard event slots such as mc_category, subcategory, severity, msg, object_uri (with an in context link back to BMM/BMTM), and so on.

For details on the configuration, consult the BMC TrueSight Middleware and Transaction Monitor documentation.