IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Monitor functions and architecture
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Monitor architecture
Tivoli Monitoring products use a set of service components (known collectively as Tivoli Management Services) that are shared by a number of other product suites, including IBM Tivoli XE monitoring products, IBM Tivoli Composite Application Manager products, System Automation for z/OS, Web Access for Information Management, and others. The information in this section is also relevant to these products.
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 and by dashboard users of the Dashboard Application Services Hub. A Tivoli Enterprise Portal Server provides presentation and communication services for these clients. Several optional components such as an historical data warehouse extend the functionality of the framework.
IBM Tivoli Monitoring also includes Jazz for Service Management which brings together the Open Services for Lifecycle Collaboration (OSLC) community's open specifications for linking data and other shared integration services, including administrative, dashboard, reporting, and security services. You can use IBM Tivoli Monitoring components to extend the Jazz for Service Management functionality for your 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.
Parent topic:
Monitor functions and architecture