Adding application support to a monitoring server on z/OS

IMPORTANT: If your site has activated the self-describing agents capability at the hub monitoring server, it is not necessary to take any additional steps to add support for any agent that has the self-describing capability. You can skip this section. However, if your site has agents reporting to the hub that do not have self-describing capability, or if you have not enabled the capability at the hub, you must install application support.

About this task

Before you can view data collected by a monitoring agent, support for the agents must be added to the Tivoli Enterprise Portal Server, to the hub monitoring server, and in some cases, to a remote monitoring server.

Application support for a monitoring agent includes two types of files:

  • Catalog and attribute (CAT and ATR) files are required for presenting workspaces, online help, and expert advice for the agent in Tivoli Enterprise Portal.
  • SQL files are required for adding product-provided situations, templates, and policies to the Enterprise Information Base (EIB) tables maintained by the hub monitoring server. These SQL files are also called seed data, and installing them on a monitoring server is also called seeding the monitoring server.
Important: The catalog and attribute files for a monitoring agent must be added to a monitoring server on z/OS® before the SQL files can be added to that monitoring server.

The way you implement the application support requirements depends on your setup.

  • If a monitoring agent and a monitoring server are installed in the same CSI, the catalog and attribute files are added automatically to the monitoring server when its runtime libraries are loaded.
    Tip: A monitoring agent on z/OS have additional requirements. See the configuration documentation for each monitoring agent product.
  • If a monitoring agent and a monitoring server are installed in different CSIs, and if data collected by the monitoring agent will flow through the monitoring server, you must copy or transfer the catalog and attribute files (KppATR and KppCAT) from the thilev.TKANDATV library in the CSI where the monitoring agent is installed to the rhilev.rte.RKANDATV library for the runtime environment in which the monitoring server is configured.
  • You add the catalog and attribute files for the Warehouse Proxy agent and for the Summarization and Pruning agent to the hub monitoring server on z/OS from the Manage Tivoli Monitoring Services utility on a Windows, Linux®, or UNIX computer where a portal server is installed and where either the portal server or a monitoring server is configured to communicate with the hub on z/OS.
  • You add the SQL files for one monitoring agent or more, for the Warehouse Proxy agent, and for the Summarization and Pruning agent to the hub monitoring server on z/OS from the Manage Tivoli Monitoring Services utility.
  • If a distributed monitoring agent (a monitoring agent installed on a Windows, Linux, or UNIX system) or a monitoring agent on a z/VM® system reports directly to a hub monitoring server on a z/OS system, you must add both the catalog and attribute files and the SQL files to the hub on z/OS from Manage Tivoli Monitoring Services.

This topics in this section provide instructions for adding application support to a monitoring server on z/OS. For instructions on adding application support to a monitoring server on Windows, Linux, or UNIX, see the IBM Tivoli Monitoring: Installation and Setup Guide.