Tivoli Monitoring products, and other products that share Tivoli Management
Services, participate in a server-client-agent architecture.
Monitoring agents for various operating systems, subsystems, databases, and
applications (known collectively as Tivoli Enterprise™ Monitoring Agents) collect
data and send it to a Tivoli Enterprise Monitoring Server. Data is accessed from the monitoring server
by Tivoli Enterprise Portal clients. A Tivoli Enterprise Portal server provides presentation and communication services
for the clients. Several optional components such as an historical data warehouse
extend the functionality of the framework. Figure 1 shows
the configuration of an IBM Tivoli Monitoring environment.
Before deciding where to deploy the components of the Tivoli Monitoring
product in your environment, you should understand the components of the product,
the roles that they play, and what affects the load on these components.
Every installation requires the following components:
One or more Tivoli Enterprise Monitoring Servers, which act as a collection and control
point for alerts received from the agents, and collect their performance and
availability data. The monitoring server also manages the connection status
of the agents. One server in each environment must be designated as the hub.
A Tivoli Enterprise Portal Server, which provides the core presentation
layer for retrieval, manipulation, analysis, and pre-formatting of data. The
portal server retrieves data from the hub monitoring server in response to
user actions at the portal client, and sends the data back to the portal client
for presentation. The portal server also provides presentation information
to the portal client so that it can render the user interface views suitably.
One or more Tivoli Enterprise Portal clients, with a Java-based user interface for viewing
and monitoring your enterprise. Tivoli Enterprise Portal offers two modes of operation: desktop
and browser.
Tivoli Enterprise Monitoring Agents, installed on the systems
or subsystems you want to monitor. These agents collect data from monitored,
or managed, systems and distribute it to a monitoring server.
z/OS only: Tivoli Management Services:Engine (TMS:Engine) provides common
functions, such as communications, multithreaded runtime services, diagnosis
(dumps), and logging (RKLVLOG), for the Tivoli Enterprise Monitoring Server,
monitoring agents, and OMEGAMON components of OMEGAMON XE products on z/OS.
IBM Eclipse Help Server for presenting help for the portal and all monitoring
agents for which support has been installed.
An installation optionally includes the following components:
Tivoli Data Warehouse for storing historical data collected from agents
in your environment. The data warehouse is located on a DB2, Oracle, or Microsoft
SQL database. To store data in this database, you must install the Warehouse
Proxy agent. To perform aggregation and pruning functions on the data, you
must also install the Summarization and Pruning agent.
Event synchronization component that sends updates to situation events
that are forwarded to a Tivoli Enterprise Console event server or a Netcool®/OMNIbus Netcool/Objectserver® back to the monitoring server.
The following sections describe each of these components in more detail.
Monitoring, Version 6.2