Configuring Tivoli Management Services

The OMEGAMON® products share a common technology, Tivoli® Management Services on z/OS®. They also share a set of common components.

Figure 1 shows the relationship between the components of Tivoli Management Services, monitoring agents, and the IBM Z® Software Asset Management products.
Figure 1. IBM Z Service Management Suite components
Relationship between the components of Tivoli Management Services, monitoring agents, and the IBM Z NetView and IBM Z Software Asset Management products

Installation and configuration process

To plan and configure components of Tivoli Management Services, follow these steps:
  1. Plan the locations of the hub and remote Tivoli Enterprise Monitoring Servers and the Tivoli Enterprise Portal Server (if applicable).
  2. For the z/OS-based components, use either of the following methods to configure the runtime environment (RTE):
    • Using Monitoring Configuration Manager (Configuration Manager), use a simple batch-only interface to configure a set of parameters and generate the necessary runtime members.

      For information on creating your first, minimal runtime environment, see Creating your first, minimal runtime environment.

    • Using Parameter Generator (PARMGEN), select the Quick Configuration option on the primary menu to get started.

      For information on using the PARMGEN program for quick configuration of z/OS-based components, see Quick configuration mode.

  3. For the distributed IBM® Tivoli Monitoring components - the hub Tivoli Enterprise Monitoring Server (if not on z/OS), Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal client (optional if you use the browser client), install and configure them using the installer program for IBM Tivoli Monitoring components.

    For information on the installer program, see IBM Tivoli Monitoring Installation and Setup Guide.

  4. The IBM Tivoli Monitoring product version files are used by the self-describing agent (SDA) installation process to determine whether new or updated product support is available.

    By default, SDA support is turned off on the hub Tivoli Enterprise Monitoring Server (monitoring server) and the remote Tivoli Enterprise Monitoring Server (monitoring server). In the z/OS environment, the monitoring server requires z/OS UNIX System Services and Java™ prerequisite configuration before SDA can be turned on. To use the SDA feature on the hub monitoring server or the remote monitoring server, add the KMS_SDA=Y parameter. For a z/OS hub monitoring server or a z/OS remote monitoring server, complete the Configuration Manager or PARMGEN steps to prepare and configure the hub monitoring server RTE for SDA processing.