IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
This chapter contains information about optimizing the performance of several components within an IBM Tivoli Monitoring environment.
This chapter includes some sections from the redbook IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments.
Agent configuration and environment variables provides an extensive list of environment variables that can be customized for different components in the Tivoli Monitoring environment. The following sections highlight specific environment variables to consider in performance tuning of the Tivoli Monitoring environment.
When changing environment variables in configuration files, note that whenever maintenance or reconfiguration takes place in your environment, these changes might be lost and need to be reapplied.
- Disable TCP-delayed acknowledgments on AIX systems
On AIX systems, the default behavior for TCP connections results in delayed acknowledgments (Ack packets). When tcp_nodelayack is set to 0 (the default setting), TCP delays sending Ack packets by up to 200ms, the Ack attaches to a response, and system overhead is minimized.
- Tivoli Enterprise Monitoring Server
This section provides information about parameters you might consider editing to improve either hub or remote monitoring server performance.
- Tivoli Enterprise Monitoring agents
This section describes agent environment variables to consider when tuning the Tivoli Monitoring environment.
- Agentless Monitoring
This section provides tuning recommendations you might consider to improve Agentless Monitoring performance in large-scale environments.
- Tivoli Enterprise Portal Server
The Tivoli Enterprise Portal Server (portal server) acts as a conduit for Tivoli Enterprise Portal clients requesting data for analysis from monitoring agents and other components within the enterprise. The portal server connects directly to the hub monitoring server, which it queries for enterprise information and receiving updates as they occur. As it is responsible for handling large amounts of data, it can be a potential bottleneck within the IBM Tivoli Monitoring environment. This section outlines considerations to optimize the portal server performance.
- Tivoli Enterprise Portal client
The Tivoli Enterprise Portal client issues requests to the Tivoli Enterprise Portal Server and renders the data that is returned. Depending on the choice of installation, the portal client can be started as a desktop application or as an applet embedded in a Web browser.
- Tivoli Data Warehouse
The Tivoli Data Warehouse is the most intensely used component of the Tivoli Monitoring infrastructure. The warehouse must support a large volume of data transactions during every warehousing period, daily summarization and pruning of the warehoused data and multiple queries that often return result sets that are thousands of rows long. The processing power required to support the warehouse database and the Summarization and Pruning Agent can be significant.
- Optimizing queries
This section contains information about tuning the queries that are processed to display the tables, charts, and graphs that make up workspace views within the Tivoli Enterprise Portal.
- Optimizing situations
Situations are conditions that you want to monitor on managed systems. Each situation contains a name, a predicate formula, special attributes for specific situation processing, information about whether the situation is automatically started or not, and the sampling interval. It can also contain a command to execute when the situation is true, and advice to give the client when an alert for the situation is surfaced, and so on.