IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Introduction

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Tivoli Management Services components

For a complete list of components, see the IBM Tivoli Monitoring Installation and Setup Guide.

Tier Component Description
Client Tivoli Enterprise Portal Java-based client used for viewing and monitoring the enterprise network. Depending on how it was installed, you can start Tivoli Enterprise Portal as a desktop application or through your browser as a web application.
Presentation server Tivoli Enterprise Portal Server The Tivoli Enterprise Portal client connects to the Tivoli Enterprise Portal Server, a collection of software services for the client that enables retrieval, manipulation and analysis of data from the monitoring agents on the enterprise. The Tivoli Enterprise Portal Server also includes the optional dashboard data provider which is used to retrieve read-only monitoring data for display in monitoring dashboards.
Management server hub Tivoli Enterprise Monitoring Server The Tivoli Enterprise Portal Server connects to the main, or hub, Tivoli Enterprise Monitoring Server. The monitoring server acts as a collection and control point for alerts received from the enterprise monitoring agents, and collects performance and availability data from them. The hub monitoring server correlates the monitoring data collected by monitoring agents and any remote monitoring servers and passes it to the portal server for presentation in the portal console.
Management automation server Tivoli Enterprise Monitoring Automation Server Optional. Installed on the same system as the hub monitoring server. Extends the functionality of the hub monitoring server. Includes the Open Services Lifecycle Collaboration Performance Monitoring (OSLC-PM) service provider.
Dashboard server IBM Dashboard Application Services Hub Jazz for Service Management component that provides dashboard visualization and reporting services. Operators of the dashboard access it through a web browser interface. IBM Dashboard Application Services Hub uses the dashboard data provider component of the portal server to retrieve monitoring data.

You can install the IBM Infrastructure Management Dashboards for Servers application into Dashboard Application Services Hub to display situation event information, managed system groups and key health metrics for Windows OS agents, Linux OS agents, and UNIX OS agents. You can also create custom dashboard pages that display monitoring data.

You can install the Authorization Policy Server and tivcmd Command-Line Interface for Authorization Policy to use role-based authorization policies to control what monitored resources are displayed in dashboards. See Use role-based authorization policies.

Help server IBM User Interface Help System Built on Eclipse. Installed with the portal server. Provides presentation and search features for the integrated help system.
Command-line tacmd Command-Line Interface Manage monitoring environment. Automate Tivoli Enterprise Portal administrative functions. The CLI commands either send requests to the hub monitoring server or to the portal server.
Agents Tivoli Enterprise Monitoring Agents Installed on the systems or subsystems whose applications and resources you want to monitor. An agent collects monitoring data from the managed system and passes it to the monitoring server to which it is connected. The portal client and dashboard server gathers the current values of the attributes and produces reports formatted into tables, charts, and relational table-based topology views. The agents and monitoring servers can also test the values of the current attributes against a threshold. When a threshold is exceeded or a value is matched, an alert icon can be displayed in the portal client or monitoring dashboard and the hub monitoring server can forward an event to an event server such as IBM Tivoli Netcool/OMNIbus. The attribute value conditions to test are called situations.

OS agents can be installed outside the enterprise as Tivoli System Monitor Agents. They do not connect to nor have any reliance on the Tivoli Enterprise Monitoring Server. They can run private situations, which are independent of the monitoring server, save data samples for attribute groups as private history, and can send SNMP alerts or EIF events to IBM Tivoli Netcool/OMNIbus.

Data warehouse Tivoli Data Warehouse Optional component for storing historical data collected from agents in your environment. The data warehouse is located on a supported database (such as DB2, Oracle, or Microsoft SQL).
Shared user registry Tivoli Directory Server
Microsoft Active Directory
Used to authenticate portal server users, IBM Dashboard Application Services Hub users, and other application users such as Netcool/OMNIbus Web GUI users. When a shared user registry is used, users are authenticated by the first server that they access and authentication tokens are passed to the other servers so that the user is not required to re-enter their credentials.

Event synchronization Optional. Send situation event updates that were forwarded to a IBM Tivoli Enterprise Console Event Server or a Netcool/OMNIbus ObjectServer back to the monitoring server.


Parent topic:

Introduction

+

Search Tips   |   Advanced Search