IBM Tivoli OMEGAMON XE V3.1 Deep Dive on z/OS

20 IBM Tivoli OMEGAMON XE V3.1 – Deep Dive on z/OS

2.1 Architecture and components

This section explains the overall architecture of IBM Tivoli OMEGAMON XE. The

architecture is based on IBM Tivoli OMEGAMON XE V3.1. In this section we

explain the structure and mechanism of IBM Tivoli OMEGAMON XE monitoring

as well as the interrelationship and dependencies of its main components. The

discussion in this section consists of:

򐂰 2.1.1, “Architecture of IBM Tivoli OMEGAMON XE” on page 20

򐂰 2.1.2, “IBM Tivoli Monitoring Services components” on page 24

򐂰 2.1.3, “OMEGAMON components on z/OS” on page 26

2.1.1 Architecture of IBM Tivoli OMEGAMON XE

IBM Tivoli OMEGAMON XE products on z/OS consist of several independent

components that make up the overall monitoring environment as shown in

Figure 2-1.

Figure 2-1 IBM Tivoli OMEGAMON XE platform architecture

As shown in Figure 2-1, the components of IBM Tivoli OMEGAMON XE are:

򐂰 Tivoli Enterprise Portal, a Java-based user interface that communicates with

Tivoli Enterprise Portal Server to request and retrieve monitoring data.

Depending on how it is installed, it enables you to view the data using a

desktop application (desktop mode) or Web browser (browser mode).

Hub

Tivoli Enterprise

Monitoring Server

`

Tivoli Enterprise Portal

- Desktop mode

- Browser mode

Tivoli Enterprise

Portal Server

Candle Management

Workstation

Remote

Tivoli Enterprise

Monitoring Server

monitoring

agent

monitoring

agent

monitoring

agent

Remote

Tivoli Enterprise

Monitoring Server

monitoring

agent

monitoring

agent

monitoring

agent

Chapter 2. IBM Tivoli OMEGAMON XE components and architecture 21

򐂰 Tivoli Enterprise Portal Server, a Java application server that enables

retrieval, manipulation, and analysis of data collected from the monitoring

agents. It functions as a repository for all user data, such as user IDs,

workspaces, views, and queries, which are used to retrieve data from different

data sources such as agents. It connects to the hub Tivoli Enterprise™

Monitoring Server and can be accessed by the Tivoli Enterprise Portal client.

򐂰 Tivoli Enterprise Monitoring Server has these functions:

– Consolidates the data collected by the agent and distributes the data

either to the Tivoli Enterprise Portal Server or to the Hub Tivoli Enterprise

Monitoring Server if it is a remote Tivoli Enterprise Monitoring Server.

– Evaluates column function for situations that cannot be resolved at the

Tivoli Enterprise Monitoring Agent.

– Sends an alert to the Tivoli Enterprise Portal Server when specified

conditions are met and receives commands from the interface and

distribute them to the appropriate monitoring agents.

– Stores historical data and prototypes for configuration in the form of

seed

data, which consists of product-specific situations, templates, and other

sample data added to the Tivoli Enterprise Monitoring Server Enterprise

Information Base (EIB) tables when a monitoring agent is installed.

– Specify security settings such as logon password requirement.

We discuss the mechanism of Tivoli Enterprise Monitoring Server in 2.1.2,

“IBM Tivoli Monitoring Services components” on page 24.

򐂰 Candle Management Workstation (CMW) is the client component of a

CandleNet Command Center environment. It has been mostly replaced by the

Tivoli Enterprise Portal user interface, but is required for some advanced

functions such as importing and exporting situations and policies, and

support for Tivoli Enterprise Monitoring Server hot standby (hub switching).

򐂰 Tivoli Enterprise Monitoring Agent is responsible for monitoring and collecting

performance data from your systems. These agents run on the managed

systems, evaluating situations and returning only rows that match the criteria

to Tivoli Enterprise Monitoring Server. Actions can be performed locally on

Tivoli Enterprise Monitoring Agent. These agents also respond to and

process queries from Tivoli Enterprise Portal Server. These agents can issue

commands to the monitored system or application. This book discusses the

monitoring agent specifically for z/OS environment.

Specific to z/OS implementation, which is the basis of IBM Tivoli OMEGAMON

XE architecture, there are additional components that come from the history of

the product, as shown in Figure 2-2 on page 22.