SL's BW Monitor® takes the time and guesswork out of monitoring and troubleshooting TIBCO® ActiveMatrix® BusinessWorks™ implementations. This out-of-the-box solution provides a centralized view of both real-time and historical performance metrics across numerous BusinessWorks engines and related services, processes and activities.
Companies rely on BusinessWorks (BW) to expose existing systems as services, build new services, and orchestrate and assemble services into applications. In doing so, typically each business service created is associated with its own BW engine, or set of load-balanced BW engines. Larger implementations may have hundreds of BW engines associated with numerous services and critical processes for the company.
RTView for APM | BW Monitor enables BW users to:
- Dramatically speed the correlation of crucial troubleshooting data for BW
- Compare real-time performance information across multiple BW engines, servers, processes and activities within a single view
- Leverage historical information to provide a centralized view of BW metrics over specific time intervals
- Navigate through the data to assess the history behind the metrics associated with the problem
- Create custom monitoring displays (optional through the RTView Builder, not included)
The challenge is, if a BW engine goes down, the associated service and processes often go down with it. Such a problem may manifest itself as a process timing out (elapsed time for completion takes too long) or excess process memory usage, for example.
Until now, the only way to monitor and troubleshoot BW engines was off of Hawk® alerts. Typically, when an alert is triggered, the first step would be to log into each affected server to determine whether the BW engines on that server were up and running. However, the administration interface only gives the current state of each BW engine with no way to look back at the time interval when the alert was triggered.
If all of the engines appear to be up and running, the next step would be to pore through log files for each BW engine and look at the data around the time of the alert. But this history is only regarding the alert, not the data that created the alert condition. The person responsible for troubleshooting would have to manually correlate data from all of the BW engines affected - assuming it is known which ones were affected - in order to infer what went wrong and resolve the problem. By this time, significant time has passed since the BW engine, service and business-critical processes went down.
BW Monitor provides out-of-the-box displays that show both real-time and historical performance metrics across all identified BW engines, as well as related services, processes and activities. The metrics available are numerous and include, for example, server memory and CPU usage, BW engine memory usage and thread count, and process execution time. Users are also able to access summary views across multiple BW engines and their process loads, dramatically speeding the correlation of crucial troubleshooting data.
CALL TODAY TO SCHEDULE A PROJECT REVIEW AND PRODUCT EVALUATION.
US and Canada: 1.800.548.6881