Monitoring

Enterprise Monitoring

The key to a stable, reliable distributed system is to monitor the moving parts of the system. It is strongly recommended for CLM Deployments to deploy professional monitoring tools for production.

Application Managed Beans

As part of our serviceability strategy for the CLM product suite, we provide detailed instrumentation and best practices for collecting data on how your system is behaving.

Managed beans (MBeans) are "Java objects that represent a manageable resource, such as an application, a service, a component, or a device" (1). These objects are available through a MBean Server or Java Management Extensions (JMX) agent.

Over the last few releases, we have been working to instrument the CLM applications using managed beans. We have implemented MXBeans. MXBeans use a predefined set of data types which make consuming data from the beans easier (2). There is no need to introspect the bean before collecting the data.

• Overview
• CLM Monitoring Primer
• MBeans Reference List
• MBean Utilities
• Register Custom Resource Intensive Scenario for tracking in MBeans

CLM Server Monitoring (Feature) deprecated in v6.0.3

• CLM Server Monitoring is a CLM solution feature developed to directly monitor Jazz Foundation-based Application server activity in more detail, enabling CLM Administrators to be informed and proactively notified about issues related to scalability, performance, and availability. CLM Server Monitoring can be used with a provided CLM Server Monitoring Agent, or with a larger monitoring solution through JMX.

Jazz server monitoring

• JMonitoring and TroubleShooting Guide provides a general view into the monitoring capabilities available for checking system stability and troubleshooting problems across the CLM application and software stack.
• JTSMon will help you make more sense out of Jazz server traffic patterns by turning web service reports into time trend spreadsheets and graphs. To get a copy of JTSMon see the JTSMonFAQ.
• Jazz monitoring through JMX provides how to set up JMX to monitor a Jazz Server.

Web and Application Server monitoring

• WebSphere Performance Monitoring Infrastructure (PMI) is the core monitoring infrastructure for WebSphere Application Server.
• Websphere Liberty's Admin Center for monitoring shows how to access the Admin Center which provides basic out of the box monitoring.
• CLM monitor is a lightweight HTTP client that uses Perl to detect the health of the CLM server and measures the response time of each round-trip HTTP call.

Basic system responsiveness

• Health Check is a provided optional dashboard widget that can be used to periodically check on server responsiveness.
• Metronome is a feature in the RTC client that provides understanding as to what the web services are doing and how the services are used by the individual RTC client with each user action.

System monitoring

• NMON (AIX/Linux) gives you a wealth of system performance statistics and automatically creates graphs for CPU, memory, disk, and network usage.

Java Virtual Machine monitoring

• IBM Java Health Center IBM Java Health Center provides tooling for monitoring and problem diagnosis of running IBM JREs.
• The IBM Whole-system Analysis of Idle Time tool (WAIT) can help you pinpoint performance bottlenecks in workloads with a central Java component and produces an HTML report that describes the main bottlenecks.
• IBM Monitoring and Diagnostic Tools for Java - Garbage Collection and Memory Visualizer Version 2.7 The IBM Monitoring and Diagnostic Tools for Java - Garbage Collection and Memory Visualizer (GCMV) is a tool that you can use to visualize and analyze the memory usage and garbage collection activity of your Java application.
  • Use of IBM Monitoring and Diagnostic Tools - Health Center on Jazz Applications through WebSphere Application Server is outlined at http://www-01.ibm.com/support/docview.wss?uid=swg21693346