IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Introduction > Components of the monitoring architecture
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Enterprise Monitoring Server
The Tivoli Enterprise Monitoring Server is the key component on which all other architectural components directly depend. The monitoring server collects and controls all data and alerts received from monitoring agents.
The Tivoli Enterprise Monitoring Server (referred to as the monitoring server) is the first component to install to begin building the Tivoli Management Services foundation.
The monitoring server is the collection and control point for performance and availability data and alerts received from monitoring agents. It is also responsible for tracking the online or offline status of monitoring agents.
Because of the number of functions the monitoring server performs, large-scale environments usually include a number of monitoring servers to distribute the load. One of the monitoring servers is designated the hub monitoring server, and the remaining servers are termed remote monitoring servers. Each remote monitoring server must be located on its own computer and have a unique monitoring server name (node), but the architectures of various remote monitoring servers might differ from each other and from the hub monitoring server. In other words, a remote monitoring server running on UNIX can report to a hub monitoring server running on Windows.
The portal server communicates with the hub, which in turn controls the remote servers, as well as any monitoring agents that might be connected to it directly.
The monitoring server storage repository is a proprietary database format (referred to as the Enterprise Information Base, or EIB). The hub holds the master copy of the EIB, while the remote servers maintain a subset of the EIB relevant to them, which is synchronized with the hub.
Parent topic:
Components of the monitoring architecture