IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Monitor functions and architecture > Monitor architecture
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Optional components
A configuration optionally includes the following components:
- Tivoli Data Warehouse for storing historical data collected from agents in your environment. The data warehouse is located on an IBM DB2 for Linux, UNIX, and Windows, DB2 on z/OS, Oracle, or Microsoft SQL database. To store data in this database, 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, the Event Integration Facility, that sends updates to situation events that have been forwarded to a Tivoli Enterprise Console event server or a Netcool/OMNIbus ObjectServer back to the monitoring server.
- IBM Dashboard Application Services Hub is a Jazz for Service Management component that provides dashboard visualization and reporting services. Operators of the dashboard access it through a web browser interface. You can install the following types of applications into the Dashboard Application Services Hub:
- The IBM Infrastructure Management Dashboards for Servers application displays situation event information, managed system groups and key health metrics for Windows OS agents, Linux OS agents, and UNIX OS agents. Situation events and monitoring data are retrieved from the Tivoli Enterprise Portal Server using its dashboard data provider.
Notes:
- Other monitoring products, such as IBM Tivoli Monitoring for Virtual Environments and IBM Smart Cloud Monitoring, may provide their own management dashboard applications that use the dashboard data provider. You can also create custom dashboard views that display monitoring data using the Dashboard Application Services Hub user interface.
- To use monitoring dashboards, you must enable the dashboard data provider component of the Tivoli Enterprise Portal Server. IBM Dashboard Application Services Hub sends requests for monitoring data to the dashboard data provider which uses the portal server services to retrieve agent data through the monitoring servers.
- A shared user registry is an LDAP server such as Tivoli Directory Server or Microsoft Active Directory that can be used to authenticate portal server users, IBM Dashboard Application Services Hub users, and optionally, 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 users are not required to re-enter their credentials. A shared user registry is strongly recommended if you plan to use IBM Dashboard Application Services Hub with monitoring dashboards. The registry takes advantage of the authorization features supported by IBM Tivoli Monitoring and enables single signon when the portal client is launched from IBM Dashboard Application Services Hub.
- The Tivoli Authorization Policy Server application is used to create authorization policies that control which managed system groups and managed systems can be viewed by a dashboard operator. The authorization policies are created using the tivcmd CLI for Authorization Policy and stored at the Authorization Policy Server. The policies are enforced in the dashboard data provider component of the Tivoli Enterprise Portal Server. The dashboard data provider retrieves the policies from the Authorization Policy Server.
- Tivoli Common Reporting can be used to gather, analyze, and report important trends in your managed environment using historical data from the Tivoli Data Warehouse. The Tivoli Common Reporting user interface is installed with Dashboard Application Services Hub and can be used to display predefined reports provided by monitoring agents and to create custom reports. Tivoli Common Reporting accesses the Tivoli Data Warehouse directly (this interaction is not depicted in Typical configuration.
IBM Dashboard Application Services Hub Server supports load balancing for high availability. Refer to the Jazz for Service Management Configuration Guide for more details on setting up this support.
However, the Authorization Policy Server does not support load balancing in this release. Therefore, if you set up multiple Dashboard Application Services Hub Severs for load balancing, you can only install the Authorization Policy Server with one of the Dashboard Application Services Hub Servers. Also, when enabling authorization policies in the portal server in the IBM Tivoli Monitoring environment, you must configure the location of the single Dashboard Application Services Hub server where the authorization policy server package is installed and configured. In addition, users of the tivcmd CLI must specify the hostname and port number of the Dashboard Application Services Hub with the Authorization Policy Server instead of the hostname and port number of the load-balancing HTTP server.
- Tivoli Performance Analyzer for predictive capability with Tivoli Monitoring so you can monitor resource consumption trends, anticipate future performance issues, and avoid or resolve problems more quickly.
Parent topic:
Monitor architecture