IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
The Agents
There is a Monitoring Agent and a data collector running on each server you are monitoring.
Monitoring Agent Route information to the Tivoli Enterprise Monitoring Server where the information is processed and presented in the Tivoli Enterprise Portal. data collector Collect and route data to the monitoring agent. It is not intended to analyze or interpret data.
If you are monitoring a Tomcat server, a J2EE Agent is installed on this server. If you are monitoring a WebSphere Portal server, a WebSphere Agent is installed.
The WebSphere Agent
Consists of a Monitoring Agent and a data collector. The WebSphere data collector collects monitoring data from WebSphere servers and communicates the data to the monitoring agent.
The WebSphere Agent collect data from four primary sources:
- Response time data for application service requests from the data collector
- Resource data from the WebSphere PMI
- WAS log messages
- Garbage-collector activity recorded in the JVM verbose GC trace
- Process data from the operating system
The J2EE Agent
Composed of a Monitoring Agent and a data collector. The J2EE Agent works with the J2EE data collector to collect performance data from J2EE application servers. The J2EE data collector collects monitoring data from J2EE servers and communicates the data to the monitoring agent. The J2EE Agent collects data from three primary sources:
- Response time data for application service requests from the data collector
- J2EE application server log messages
- Garbage collection activity that is recorded in the JVM verbose GC trace
The HTTP Agent
Composed of a Monitoring Agent only. The Monitoring Agent can monitor the following HTTP servers:
- IIS Web Servers
- Apache Web Servers
- IBM HTTP Web Servers
- Sun Web Servers
The HTTP Monitoring Agent has three components that are used to collect monitoring data from Web servers. There is an Apache, an IIS, and a Sun Web servers component.
The HTTP Agent collects performance data about the Web servers and Web sites in the following ways:
Apache Server and HTTP Server:
The agent modifies the Apache server and IBM HTTP server configuration files to include the monitoring module. The monitoring module is loaded dynamically during Web server start up. The module receives all HTTP requests and report data to the HTTP Agent. In addition, the HTTP Agent parses static information from the configuration file.
IIS Web Server:
The HTTP Agent collects monitoring data from IIS Servers in the following two ways:
- For static information about server configuration, the agent issues queries to the Admin Base Object (ABO) interface which provides access to the IIS metabase.
- For dynamic information about server availability and performance metrics, the agent issues queries to the Microsoft Windows Management Instrumentation (WMI) interface.
Sun Web Server:
The HTTP Agent collects monitoring data from Sun Web Servers by polling the SNMP service for Web server-related statistics. It also parses Web server configuration files to get information that is not provided by the SNMP service.
Parent topic:
Components used by the Tivoli Enterprise Portal user interface