IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


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.

The portal server database stores information related to the presentation of monitored data at the portal client, including definitions related to users, workspaces and views. After IBM Tivoli Monitoring V6.1 Fix Pack 3, the portal server also stores information related to events and event attachments in the portal server database. Before IBM Tivoli Monitoring V6.1 Fix Pack 3, the portal server database required little or no tuning. In environments with a moderate to high rate of events, the portal server database might require some tuning to optimize performance. In particular, the KFWTSIT table, which is used to store events, can grow large.

If you are using DB2 for the portal server database, consider the following tuning recommendations:


Parent topic:

Performance tuning

+

Search Tips   |   Advanced Search