Configuring theTivoli Enterprise Monitoring Server on z/OS · OMEGAMON XE and IBM Tivoli Management...

IBM Tivoli Management Services on z/OSVersion 6.2.3 Fix Pack 1

Configuring the Tivoli EnterpriseMonitoring Server on z/OS

SC27-2313-03

��

IBM Tivoli Management Services on z/OSVersion 6.2.3 Fix Pack 1

Configuring the Tivoli EnterpriseMonitoring Server on z/OS

SC27-2313-03

��

NoteBefore using this information and the product it supports, read the information in Appendix C, “Notices,” on page 167.

This edition applies to version 6, release 2, modification 3, Fix Pack 1 of IBM Tivoli Management Services on z/OS(product number 5698-A79) and to all subsequent releases and modifications until otherwise indicated in neweditions.

This edition replaces SC27-2313-02.

© Copyright IBM Corporation 2005, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Part 1. Preparing to configure the Tivoli Enterprise Monitoring Server on z/OS . . 1

Chapter 1. Overview of Tivoli Management Services and the Tivoli Enterprise Monitoring Server 3Tivoli Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tivoli Enterprise Monitoring Server . . . . . . . . . . . . . . . . . . . . . . . . . 4Tivoli Enterprise Portal Server and clients . . . . . . . . . . . . . . . . . . . . . . . 4Tivoli Data Warehouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5TMS:Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Event synchronization component . . . . . . . . . . . . . . . . . . . . . . . . . . 5Tivoli Enterprise Portal Server extended services . . . . . . . . . . . . . . . . . . . . 5Monitoring agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

New in this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2. Planning your deployment . . . . . . . . . . . . . . . . . . . . . . . . 13Decision 1: What kinds of monitoring servers to configure . . . . . . . . . . . . . . . . . 13

Whether to configure a high-availability hub on z/OS . . . . . . . . . . . . . . . . . . 13How many remote monitoring servers to configure . . . . . . . . . . . . . . . . . . . 14Whether to enable the self-describing agents capability . . . . . . . . . . . . . . . . . 15Whether to enable the auditing function . . . . . . . . . . . . . . . . . . . . . . . 17

Decision 2: Whether and how to enable event forwarding. . . . . . . . . . . . . . . . . . 22

Part 2. Configuring hub and remote monitoring servers on z/OS . . . . . . . . 25

Chapter 3. Configuring a high-availability hub and the remote monitoring servers that report toit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

PARMGEN method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Step 1. Create and configure a runtime environment for the high-availability hub . . . . . . . . 27Step 2. Configure a remote monitoring server to report to the high-availability hub . . . . . . . 30Step 3. Configure monitoring agents to report to the remote monitoring server . . . . . . . . . 31Step 4. (Optional) Replicate the remote runtime environment . . . . . . . . . . . . . . . 32

Configuration Tool (ICAT) method . . . . . . . . . . . . . . . . . . . . . . . . . . 32Step 1. Add a runtime environment . . . . . . . . . . . . . . . . . . . . . . . . . 32Step 2. Build the runtime libraries . . . . . . . . . . . . . . . . . . . . . . . . . 39Step 3. Configure the high-availability hub monitoring server . . . . . . . . . . . . . . . 39Step 4. Configure a remote monitoring server to report to the high-availability hub . . . . . . . 64Step 5. Configure monitoring agents to report to the remote monitoring server . . . . . . . . . 76Step 6. Load the runtime libraries . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 4. Configuring the hub monitoring server and monitoring agents in the same runtimeenvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

PARMGEN method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Step 1. Create the runtime environment and set the configuration parameters for the hub . . . . . 79Step 2. Set configuration parameters for the monitoring agents in the same runtime environment 81Step 3. (Optional) Replicate the runtime environment to a remote system . . . . . . . . . . . 81

Configuration Tool (ICAT) method . . . . . . . . . . . . . . . . . . . . . . . . . . 82Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Step 1. Configure the hub monitoring server . . . . . . . . . . . . . . . . . . . . . 83Step 2. Configure monitoring agents in the runtime environment . . . . . . . . . . . . . . 97

© Copyright IBM Corp. 2005, 2012 iii

Step 3. Load the runtime libraries . . . . . . . . . . . . . . . . . . . . . . . . . 98

Chapter 5. Configuring a remote monitoring server on z/OS to report to a distributed hub . . . 99PARMGEN method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Step 1. Create the runtime environment and set the configuration parameters for the remotemonitoring server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Step 2. Set configuration parameters for the monitoring agents in the same runtime environment 101Step 3. (Optional) Replicate the remote runtime environment . . . . . . . . . . . . . . . 101

Configuration Tool (ICAT) method . . . . . . . . . . . . . . . . . . . . . . . . . . 102Configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Step 1. Configure the remote monitoring server . . . . . . . . . . . . . . . . . . . . 102Step 2. Configure monitoring agents in the runtime environment . . . . . . . . . . . . . . 115

Step 3. Load the runtime libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Part 3. Post-configuration procedures . . . . . . . . . . . . . . . . . . . . 117

Chapter 6. Completing the configuration . . . . . . . . . . . . . . . . . . . . . . 119Typical tasks of completing the configuration of a monitoring server . . . . . . . . . . . . . 119

(If applicable) Add support for the SYSTCPD DDNAME in the monitoring server started task . . . 119(If applicable) Add the NetView CNMLINK data set to the monitoring server started task . . . . . 120Copy the started task procedures to your procedure library. . . . . . . . . . . . . . . . 120Copy the VTAM definitions to your system VTAMLST . . . . . . . . . . . . . . . . . . 121Vary the VTAM major node active . . . . . . . . . . . . . . . . . . . . . . . . . 121APF-authorize the runtime load libraries. . . . . . . . . . . . . . . . . . . . . . . 121(If applicable) Refresh the KSHXHUBS member in other runtime environments . . . . . . . . 121Verify that you can start and stop the monitoring server . . . . . . . . . . . . . . . . . 121(If applicable) Enable NetView to authorize Take Action commands. . . . . . . . . . . . . 122(If applicable) Edit the portal server environment file . . . . . . . . . . . . . . . . . . 123Enable historical data store maintenance (optional) . . . . . . . . . . . . . . . . . . 123Enable historical data collection (optional) . . . . . . . . . . . . . . . . . . . . . . 124Enable event forwarding (optional) . . . . . . . . . . . . . . . . . . . . . . . . . 124Run the ITMSUPER Tools (optional) . . . . . . . . . . . . . . . . . . . . . . . . 128

Chapter 7. Adding application support to a monitoring server on z/OS. . . . . . . . . . . 129Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Selecting the correct procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Install the application support files on a distributed system where a portal server is installed . . . . 133

Installing application support files on Windows . . . . . . . . . . . . . . . . . . . . 133Installing application support files on Linux or UNIX . . . . . . . . . . . . . . . . . . 135

Copy or transfer catalog and attribute files to the monitoring server on z/OS . . . . . . . . . . 137Transferring the catalog and attribute files from Windows . . . . . . . . . . . . . . . . 137Transferring the catalog and attribute files from Linux or UNIX . . . . . . . . . . . . . . 138

Use Manage Tivoli Monitoring Services to add application support SQL files to the hub monitoringserver on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Adding application support SQL files from Manage Tivoli Monitoring Services on Windows . . . . 139Adding application support SQL files from Manage Tivoli Monitoring Services on Linux or UNIX 140

Chapter 8. Configuring security on a monitoring server on z/OS . . . . . . . . . . . . . 143Enabling security validation on a z/OS hub . . . . . . . . . . . . . . . . . . . . . . 143

Implementing security with RACF . . . . . . . . . . . . . . . . . . . . . . . . . 145Implementing CA-ACF2 security . . . . . . . . . . . . . . . . . . . . . . . . . 145Implementing security with CA-TOP SECRET . . . . . . . . . . . . . . . . . . . . 146Implementing security with Network Access Method (NAM). . . . . . . . . . . . . . . . 146Changing the security system specification . . . . . . . . . . . . . . . . . . . . . 147

Resetting the password encryption key . . . . . . . . . . . . . . . . . . . . . . . . 147PARMGEN method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

iv IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS

Configuring NetView authorization of z/OS commands . . . . . . . . . . . . . . . . . . 149Configure the monitoring server to forward Take Action commands . . . . . . . . . . . . . 150Add the NetView CNMLINK data set to the Tivoli Enterprise Monitoring Server started task . . . . 151Enable NetView to authorize Take Action commands . . . . . . . . . . . . . . . . . . 152Verifying the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Enable RACF authorization of Take Action commands . . . . . . . . . . . . . . . . . . 154Setting up the userid mapping capability . . . . . . . . . . . . . . . . . . . . . . 155

Part 4. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Appendix A. Documentation library . . . . . . . . . . . . . . . . . . . . . . . . 159IBM Tivoli Monitoring library . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Documentation for the base agents . . . . . . . . . . . . . . . . . . . . . . . . 160Shared OMEGAMON XE publications . . . . . . . . . . . . . . . . . . . . . . . . 161Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Other sources of documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Appendix B. Support information . . . . . . . . . . . . . . . . . . . . . . . . . 165

Appendix C. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Contents v

vi IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS

Figures

1. Agent/server/client architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 32. High-availability hub monitoring server and its connections . . . . . . . . . . . . . . . 273. Configuration Tool Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 334. Configure Products panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . 335. Product Selection Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336. Runtime Environments (RTEs) panel . . . . . . . . . . . . . . . . . . . . . . . 347. Add Runtime Environment (1 of 3) panel . . . . . . . . . . . . . . . . . . . . . . 358. Add Runtime Environment (2 of 3) panel . . . . . . . . . . . . . . . . . . . . . . 379. Add Runtime Environment (3 of 3) panel . . . . . . . . . . . . . . . . . . . . . . 39

10. Configure the TEMS panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 4011. Specify Configuration Values panel . . . . . . . . . . . . . . . . . . . . . . . . 4112. Eligible Products for HA Hub TEMS panel . . . . . . . . . . . . . . . . . . . . . 4413. Exclusion Verification for HA Hub TEMS panel . . . . . . . . . . . . . . . . . . . . 4514. Specify Advanced Configuration Values panel . . . . . . . . . . . . . . . . . . . . 4515. Specify Persistent Datastore Configuration Values panel . . . . . . . . . . . . . . . . 4816. Specify Values for Event Destination panel . . . . . . . . . . . . . . . . . . . . . 5017. Specify Communication Protocols panel . . . . . . . . . . . . . . . . . . . . . . 5118. Specify IP.PIPE Communication Protocol panel. . . . . . . . . . . . . . . . . . . . 5219. Specify IP.PIPE Partition References panel . . . . . . . . . . . . . . . . . . . . . 5420. Specify TEMS KSHXHUBS Values panel . . . . . . . . . . . . . . . . . . . . . . 5521. SOAP server KSHXHUBS List panel . . . . . . . . . . . . . . . . . . . . . . . 5622. SOAP server KSHXHUBS Security Access List panel . . . . . . . . . . . . . . . . . 5723. Specify TEMS KSHXHUBS User Access List panel . . . . . . . . . . . . . . . . . . 5724. Configure TEMS Self-Describing Agent Parameters panel . . . . . . . . . . . . . . . . 5825. Specify TEMS Self-Describing Agent Values panel . . . . . . . . . . . . . . . . . . 5926. Configure Persistent Datastore panel . . . . . . . . . . . . . . . . . . . . . . . 6127. Modify and Review Datastore Specifications panel . . . . . . . . . . . . . . . . . . 6228. Product Component Selection Menu. . . . . . . . . . . . . . . . . . . . . . . . 6429. Create LU6.2 Logmode panel . . . . . . . . . . . . . . . . . . . . . . . . . . 6530. Communication Selection panel . . . . . . . . . . . . . . . . . . . . . . . . . 7131. Specify Communication Protocols panel . . . . . . . . . . . . . . . . . . . . . . 7132. Specify IP.PIPE Communication Protocol panel. . . . . . . . . . . . . . . . . . . . 7233. Specify SNA Communication Protocol panel . . . . . . . . . . . . . . . . . . . . . 7434. Hub monitoring server and monitoring agents in the same runtime environment. . . . . . . . 7935. Remote monitoring server on z/OS reporting to a hub on a distributed system . . . . . . . . 9936. Communication Selection panel . . . . . . . . . . . . . . . . . . . . . . . . . 11037. Specify Configuration - Hub Values for Remote TEMS panel . . . . . . . . . . . . . . 11038. Specify Communication Protocols panel for a remote monitoring server . . . . . . . . . . 11139. Specify IP.PIPE Communication Protocol panel for a remote monitoring server . . . . . . . 11340. CNMSTYLE member after editing . . . . . . . . . . . . . . . . . . . . . . . . 12241. CNMLINK DD statement in the Tivoli Enterprise Monitoring Server started task . . . . . . . 15142. CNMSTYLE member after editing . . . . . . . . . . . . . . . . . . . . . . . . 152

© Copyright IBM Corp. 2005, 2012 vii

viii IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS

Tables

1. New monitoring server runtime libraries and started task DDNAMEs . . . . . . . . . . . . 102. SMF type-112 record subtypes. . . . . . . . . . . . . . . . . . . . . . . . . . 193. SMF record 112 format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194. Procedures for adding application support to a monitoring server on z/OS . . . . . . . . . 131

© Copyright IBM Corp. 2005, 2012 ix

x IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS

Part 1. Preparing to configure the Tivoli Enterprise MonitoringServer on z/OS

This publication is intended to be used together with IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide, which contains vital planninginformation. Read the chapters in Parts 1 and 2 of the Common Planning and Configuration Guide first,and then continue with the chapters in this part of Configuring the Tivoli Enterprise Monitoring Server onz/OS.

See Appendix A, “Documentation library,” on page 159 for information on finding the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide and other related publications.

The chapters in this part of Configuring the Tivoli Enterprise Monitoring Server on z/OS provide informationrequired for beginning to configure your monitoring servers on z/OS®.

v Chapter 1, “Overview of Tivoli Management Services and the Tivoli Enterprise Monitoring Server,” onpage 3 explains the architecture and the commonly shared components of IBM® Tivoli® ManagementServices. Chapter 1 also contains a New in this release section, which describes changes andenhancements that affect the configuration of the Tivoli Enterprise Monitoring Server.

v Chapter 2, “Planning your deployment,” on page 13 helps you plan a first-time deployment of the TivoliEnterprise Monitoring Server on z/OS. Chapter 2 covers basic planning decisions that are not coveredin Part 1 of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide:

__ “Decision 1: What kinds of monitoring servers to configure” on page 13

__ “Decision 2: Whether and how to enable event forwarding” on page 22

Navigation tips

v If you are installing and configuring the Tivoli Management Services components for the first time,be sure to read all the chapters in Part 1 of the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide and in Part 1 of thispublication before you begin.

v If you are upgrading existing components, you can skip ahead.

1. Examine “New in this release” on page 7 to learn about changes that affect the TivoliEnterprise Monitoring Server.

2. Follow the upgrade instructions in IBM Tivoli OMEGAMON XE and IBM Tivoli ManagementServices on z/OS: Upgrade Guide.

See Appendix A, “Documentation library,” on page 159 for information on finding the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Upgrade Guide and otherrelated publications.

© Copyright IBM Corp. 2005, 2012 1

2 IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS

Chapter 1. Overview of Tivoli Management Services and theTivoli Enterprise Monitoring Server

The Tivoli Enterprise Monitoring Server (also called the monitoring server) is the central component of thecommonly shared technology called Tivoli Management Services. The monitoring server consolidates anddistributes data; receives and distributes commands; and sends alerts when specified availability andperformance problems are detected in the monitored applications, systems, or networks.

The monitoring server can run on distributed or z/OS systems. This guide describes how to configure andcustomize a monitoring server on a z/OS system.

Tivoli Management ServicesThe commonly shared components of Tivoli Management Services provide security, data transfer andstorage, notification, user interface presentation, and communication for a number of Tivoli monitoringproducts. The Tivoli Management Services components and the monitoring agents work together in anagent/server/client implementation (Figure 1).

Some components of Tivoli Management Services, such as Tivoli Enterprise Portal and the WarehouseProxy and Summarization and Pruning agents, run only on distributed systems. The Tivoli EnterpriseMonitoring Server and the Tivoli Data Warehouse can run on either distributed or mainframe systems.Tivoli Management Services:Engine (TMS:Engine) runs only on mainframe systems.

The Tivoli Management Services shared components are included with the IBM Tivoli Monitoring product,with the OMEGAMON® XE monitoring agent products, with the IBM Tivoli Management Services on z/OSproduct, and with many other Tivoli applications.

Tivoli Management Services comprises the following commonly shared components:

Figure 1. Agent/server/client architecture


v “Tivoli Enterprise Monitoring Server”

v “Tivoli Enterprise Portal Server and clients”

v “Tivoli Data Warehouse” on page 5

v “TMS:Engine” on page 5

v “Event synchronization component” on page 5

v “Tivoli Enterprise Portal Server extended services” on page 5

Tivoli Enterprise Monitoring ServerTivoli Enterprise Monitoring Server is the nerve center of Tivoli Management Services. The monitoringserver performs the following tasks:

v Consolidates the data collected by monitoring agents and distributes the data to the Tivoli EnterprisePortal Server.

v Manages the connection status of the monitoring agents.

v Receives commands from Tivoli Enterprise Portal and distributes them to the appropriate monitoringagents.

v Sends alerts to the Tivoli Enterprise Portal Server when specified availability and performance problemsare detected

v Stores historical data and configuration prototypes.

The master monitoring server is called the hub monitoring server. The hub monitoring server acts as thefocal point for data collection and distribution. It communicates with monitoring agents, with remotemonitoring servers, with the Tivoli Enterprise Portal Server, and with the Warehouse Proxy andSummarization and Pruning agents (see “Tivoli Data Warehouse” on page 5).

A remote monitoring server is remote only with respect to the hub monitoring server, not with respect tothe monitoring agents. Remote monitoring servers communicate only with the monitoring agents that reportto them and with the hub monitoring server to which they report.

Monitoring servers can run on z/OS, Windows, AIX®, HP-UX, Solaris, or Linux systems.

Tivoli Enterprise Portal Server and clientsTivoli Enterprise Portal (also called the portal or the portal client) is the user interface for products usingTivoli Management Services. The Tivoli Enterprise Portal is a thin Java client application. It has its ownserver, the Tivoli Enterprise Portal Server, that communicates with the hub monitoring server to sendrequests to and retrieve data from monitoring agents on managed systems. Tivoli Enterprise Portal Server(the portal server) builds and formats the portal workspaces that display real-time and historical datacollected by the monitoring agents. The portal server can run on Windows, AIX, or Linux systems.

You can access the portal client in any of the following ways:

v Browser client (Internet Explorer or Mozilla Firefox on Windows, Mozilla Firefox on Linux) connected toa web server embedded in the portal server. The desktop client is downloaded or updated every time itstarts up.

Your site can now run the Tivoli Enterprise Portal browser client using newer levels (v3.6.x, V5.0, orV6.0.x) of the Firefox Web browser on Windows and Linux when used in conjunction with a Java V6runtime environment. Note: If your site is running a Java V5 runtime environment instead, you mustcontinue to run the V3.5 or earlier level of Firefox.

v Desktop client installed on a Windows or Linux system.

v Desktop client downloaded and run by IBM Web Start for Java, and updated at every startup.

For setup information about the portal server and client, see the IBM Tivoli Monitoring: Installation andSetup Guide.


Tivoli Data WarehouseTivoli Data Warehouse, an optional component of Tivoli Management Services, is a long-term data storefor the performance and analysis data collected by the monitoring agents. The Warehouse Proxy agentperiodically receives data indirectly from the hub monitoring server or directly from the monitoring agentsand inserts that data into the Tivoli Data Warehouse. On z/OS systems, short-term history data formonitoring agents is maintained in data sets allocated and initialized during product configuration. TheWarehouse Proxy agent receives the short-term history data and delivers it to the warehouse.

Two specialized agents interact with the Tivoli Data Warehouse:

v The Warehouse Proxy agent receives the short-term history data and delivers it to the Tivoli DataWarehouse.

v You can use the Summarization and Pruning agent to customize how long to save (pruning) and howoften to aggregate (summarization) the data in the Tivoli Data Warehouse database.

The Warehouse Proxy agent and the Summarization and Pruning agent can run on Windows, AIX, HP-UX,Solaris, or Linux systems. For more information, see the following publications:

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide

v IBM Tivoli Monitoring: Installation and Setup Guide

v IBM Tivoli Monitoring: Administrator's Guide

TMS:EngineTMS:Engine provides common functions such as communications, multithreaded runtime services, tracing,and logging for the monitoring server and monitoring agents on z/OS. This shared component enablescommon portable code to make platform-independent system calls. This allows Tivoli Enterprise MonitoringServer code to be compiled for and executed on z/OS, Windows, Linux, and UNIX platforms.

Event synchronization componentThe event synchronization component sends updates to situation events that have been forwarded to aTivoli Enterprise Console® event server or a Netcool®/OMNIbus ObjectServer back to the hub monitoringserver. In the Tivoli Enterprise Portal, the Situation Event Console, the Common Event Console and theTivoli Enterprise Console event views are synchronized with the updated status of the events.

For information about the configurations of event servers that you can have in your environment, see theIBM Tivoli Monitoring: Installation and Setup Guide. For information about forwarding events from a hubmonitoring server on z/OS, see “Decision 2: Whether and how to enable event forwarding” on page 22.

With Tivoli Management Services V6.2.2 and later, stand-alone monitoring agents (those that areconfigured in their own address spaces) can run in autonomous mode (without communicating directly witha monitoring server). An autonomous agent can emit Simple Network Management Protocol (SNMP) trapsand Event Integration Facility (EIF) events directly to an OMNIbus ObjectServer for agent-specificsituations (but not for enterprise situations).

The IBM Tivoli Monitoring: Installation and Setup Guide provides instructions for configuring OMNIbusObjectServers to receive the events. For information on specifying which situation events to forward, seethe Tivoli Enterprise Portal online help and the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide.For detailed information about managing autonomous agents, see the "Agent autonomy" chapter of theIBM Tivoli Monitoring: Administrator's Guide.

Tivoli Enterprise Portal Server extended servicesTivoli Enterprise Portal Server extended services (TEPS/e) is an embedded, co-located extension of theTivoli Enterprise Portal Server that provides J2EE-based Application Server integration facilities. TEPS/eprovides support for a federated user repository.

Chapter 1. Overview of Tivoli Management Services and the Tivoli Enterprise Monitoring Server 5

Monitoring agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of operating system monitoringagents (also called OS agents or base agents) as part of the product. If you purchased a monitoring agentproduct (for example, an OMEGAMON XE product) that includes the commonly shared components ofTivoli Management Services, you did not receive the base agents.

Monitoring agent products are available for systems, database products, and applications. You can see thecomplete list of monitoring agents at the following website:http://www.ibm.com/software/tivoli/solutions/availability/products.html

A monitoring agent on any platform can be part of an enterprise that includes monitoring servers on z/OSsystems.


http://www-306.ibm.com/software/tivoli/solutions/availability/

New in this releaseThis section describes enhancements that affect the configuration of Tivoli Enterprise Monitoring Serverand that have been added since the last release of this publication.

v Userid-level security now available for Take Action commands. As of fix pack 1 for IBM TivoliMonitoring Version 6.2.3, all z/OS Take Action commands issued by the OMEGAMON XE agents, plusany other agents based on the Tivoli Management Services framework that run on z/OS, can now beassociated with the Tivoli Enterprise Portal userid instead of the userid of the started task running theagent. This allows you to authorize the use of Take Action commands by selected portal server userswhile restricting it from others. You can secure these userids (or the RACF® groups they are in) viastandard security objects provided by your site's security product; for RACF, these are the OPERCMDSfacility class and its profiles. See “Enable RACF authorization of Take Action commands” on page 154.

v Later versions of the Firefox browser now supported. Your site can now run the Tivoli EnterprisePortal browser client using v3.6.x, V5.0, or V6.0.x of the Firefox Web browser on Windows and Linux.This update requires that your site also use a Java V6 runtime environment.

In addition, AIX has been removed as a Tivoli Enterprise Portal client platform from this configurationguide. Only the Windows and Linux platforms are supported for the Tivoli Enterprise Portal browserclient. AIX is still fully supported as a Tivoli Enterprise Portal server platform.

v PARMGEN configuration method. The PARMGEN configuration method is now the preferred methodof product configuration. The PARMGEN method is particularly suitable for the following types ofcustomers:

– New OMEGAMON XE customers.

– Existing OMEGAMON XE customers in environments in which one person is responsible forconfiguring all OMEGAMON XE products and components.

With the PARMGEN configuration method, you edit a comprehensive list of parameters for configuringall installed products and components. You then submit a series of jobs to create a complete runtimeenvironment with the parameter values you specified. The chapters in Part 2, “Configuring hub andremote monitoring servers on z/OS,” on page 25 and Part 3, “Post-configuration procedures,” on page117 now include procedural instructions for both PARMGEN and the Configuration Tool (ICAT)configuration methods.

For more information about the PARMGEN configuration method, see IBM Tivoli OMEGAMON XE andIBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide, IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference, andthe PARMGEN Technote at http://www.ibm.com/support/docview.wss?uid=swg21417935.

Tip: Both the PARMGEN method and the Configuration Tool (ICAT) method are currently supported,but future product enhancements and updates will be available by the PARMGEN method only.Therefore, it is a good idea to begin using the PARMGEN method for configuring your products andcomponents.

v Self-describing agents. Prior to version 6.2.3, before an agent could connect to a Tivoli EnterpriseMonitoring Server, you were required to update the monitoring server (as well as other TivoliManagement Services components such as the Tivoli Enterprise Portal Server and the Tivoli DataWarehouse) with information necessary for it to recognize and process data sent by that agent, andthen restart all affected components. As of V6.2.3, this "seeding" step (as it was once known) becomesunnecessary for the distributed (that is, non-z/OS) agents: they have been enhanced with aself-description capability that automatically distributes each agent's operating configuration directly tothe local monitoring server, which then replicates those agent configuration files first to the hubmonitoring server (if necessary) and then to the various IBM Tivoli Monitoring components that requireit.

“Whether to enable the self-describing agents capability” on page 15 has more information about theself-describing distributed agents.


http://www.ibm.com/support/docview.wss?uid=swg21417935

Note: Once your site activates self-describing agents on a hub Tivoli Enterprise Monitoring Server, themonitoring server must have access to a Java Runtime Environment running under IBM's 31-bit or64-bit Java SDK Version 5 (or higher) and an HFS or zFS file system configured for UNIX SystemServices (USS).

– As part of monitoring server configuration, the RKCPDEFW VSAM file is now allocated for you.Historically, this file is allocated only by the PARMGEN process if the OMEGAMON XE for CICS(that is, the C5) agent is configured in the current runtime environment. In support of self-describingagents, this file is now processed as part of monitoring server configuration; in this way, themonitoring server started task is already set up to accommodate the C5 agent's hub monitoringserver requirements when the C5 Agent is later added to the RTE.

v New auditing function. The new auditing function allows you to capture significant events occurring inyour site's IBM Tivoli Monitoring environment and record them in permanent storage for later retrievaland analysis. Each audit record fully describes some event that has changed the state of your TivoliMonitoring system. Platforms covered include Windows, UNIX/Linux, i5/OS®, and z/OS. On z/OS, theauditing facility optionally creates and stores Systems Management Facility–format (SMF) records.

These new auditing and logging records can be stored in the Tivoli Data Warehouse. Standard reportsare provided via the Tivoli Common Reporting feature. In addition, a new Tivoli Enterprise Portalworkspace enables you to view auditing and logging records online; see the IBM Tivoli Monitoring: TivoliEnterprise Portal User's Guide for information.

“Whether to enable the auditing function” on page 17 has more information about the new auditingfeature.

Supporting the auditing function required the creation of a new ICAT panel , KDSPPDS (SpecifyPersistent Datastore Configuration Values) panel, where you supply the PDS definition parameters; seeFigure 15 on page 48.

v Web Services (SOAP server) support extended to remote monitoring servers. IBM TivoliMonitoring's Web Services solution provides you with an industry-standard, open interface into TivoliMonitoring's performance and availability data. With it, your site can integrate Tivoli Monitoring data withexternal automation and integration applications.

Tivoli Monitoring Web Services implements a client/server architecture in which the client sends SimpleObject Access Protocol (SOAP) requests to the SOAP server running within the Tivoli EnterpriseMonitoring Server. The SOAP server receives, processes, then responds to the client's SOAP requests.

Previously, the SOAP server ran only within a hub monitoring server. The SOAP server now can run ina remote monitoring server as well. This means that a policy running on a remote monitoring server cannow send a SOAP request to an agent that is connected to that same monitoring server, which isimportant because version 6.2.3 adds new SOAP-based, on-demand and email activities, which sendSOAP requests to the monitoring server on which the policy is running.

In addition, this architecture is more efficient than having all remote monitoring servers send their SOAPrequests to the hub. It also means that a policy that is running on a remote monitoring server cancontinue to process SOAP requests even when the hub or the connection to the hub becomesunavailable.

To activate the SOAP server for a remote monitoring server, ensure you set the Enable Web ServicesSOAP Server parameter to Y when completing step “Specify configuration values” on page 103.

v Automatic registration of products with the local monitoring server. The runtime environment loadprocessing option now automatically copies the KppATR and KppCAT members from the&thilev.TKANDATV target data set that was installed by SMP/E to the runtime environment&rhilev.&rte.RKANDATV library. You do not have to regenerate and rerun the "Register with local TEMS"(pp#4ssss) job for each product in the runtime environment if you apply maintenance that updates theKppATR and KppCAT members only. Instead, you can just reload the runtime environment to refreshthe members.

The "Register with local TEMS" step is still required the first time you configure a monitoring agent orwhenever you apply maintenance that updates parameters.

v High-availability hub monitoring server. You can now configure a high-availability hub monitoringserver in any sysplex environment with dynamic virtual IP addressing (DVIPA) and shared DASD. A


high-availability hub is configured in its own runtime environment, without any monitoring agents, andcan be configured on the same LPAR with a remote monitoring server. This configuration allows the hubmonitoring server to be relocated to any suitable LPAR in the sysplex with no changes, and withminimal disruption to the components connecting to the hub.

v Agent failover. During configuration of stand-alone distributed monitoring agents, you can specify aprimary and secondary monitoring server for agent connections. If an agent's primary monitoring servergoes offline, the agent connects to the secondary monitoring server. When the primary monitoringserver goes back online, the agent is automatically reconnected with it.

Note: This feature does not apply to the OMEGAMON Monitoring Agents, as it requires the ProxyAgent Services feature of Tivoli Monitoring, which is not available on z/OS.

v Increased default value for minimum extended storage. For a new runtime environment containing amonitoring server, the default value for minimum extended storage is now 768000. This value indicatesthe minimum amount of virtual storage to be made available to the monitoring agents and othercomponents communicating with the monitoring server. You can override the default by specifying avalue in the PARMGEN configuration profile or (in the Configuration Tool) on the Specify AdvancedConfiguration Values panel during monitoring server configuration.

v Event forwarding to the Tivoli Enterprise Console and Netcool/OMNIbus event managementservers. You can now forward situation events reported to a hub monitoring server on z/OS to the TivoliEnterprise Console or to OMNIbus for correlation and management. To forward situation events, theTivoli Event Integration Facility (EIF) on the hub monitoring server must be enabled, and the host nameand listening port of the event receiver must be specified in the Configuration Tool.

In addition, several tasks must be completed outside the configuration software:

– The destination event server or servers must be configured to receive the events.

– A situation update forwarding process (the event synchronization component) must be installed onthe event server or servers.

– If situation events are forwarded to OMNIbus, an EIF probe must be installed.

– For situation events forwarded to the Tivoli Enterprise Console, .baroc files for the monitoring agentsreporting to the hub must be installed and imported on the Tivoli Enterprise Console server, and therule base must be updated.

The "Event integration scenarios" section of IBM Tivoli Monitoring: Installation and Setup Guidedescribes the deployment possibilities for hubs and event servers; and the section on "Integrating eventmanagement systems" provides detailed instructions for configuring the Tivoli Enterprise Console andOMNIbus event servers to receive the events, including installing the event synchronization componentand the .baroc files.

“Decision 2: Whether and how to enable event forwarding” on page 22 in this guide explains briefly howevent forwarding works, discusses issues to consider before you enable event forwarding on a z/OShub, and points you to more complete documentation on event forwarding.

The information for Figure 14 on page 45 and Figure 16 on page 50 gives instructions for enabling EIFand specifying the destination event servers during configuration of the hub.

“Enable event forwarding (optional)” on page 124 outlines further steps you must take to enable eventforwarding and points you to instructions for configuring the Tivoli Enterprise Console and OMNIbusevent servers to receive forwarded events.

v Simplified persistent data store maintenance processing. The maintenance processing of thepersistent datastore has been simplified. KPDPROC1 now does all the work formerly done by themaintenance job (KPDJOBC), and KPDPROC2 has been eliminated. It is no longer necessary toauthorize and submit the maintenance job; however, because the KPDPROCC REXX procedure runs ina TSO environment, the KPDDSCO program has to be enabled to execute as an authorized programunder TSO, by adding the KPDDSCO persistent datastore module name to theSYS1.PARMLIB(IKJTSO00) under the AUTHPGM section.

If you are upgrading from a previous version of the monitoring server, you can remove the KPDPROC2member from the library. After the environment has been completely upgraded, you can remove any


special RACF or ACF2 rules set up for KPDPROC2. See the IBM Tivoli OMEGAMON XE and IBMTivoli Management Services on z/OS: Common Planning and Configuration Guide for furtherinformation.

v Sample VSAM refresh jobs. The Tivoli Enterprise Monitoring Server configuration now generates twosample VSAM jobs: KDSDVSRN and KDSVSRF. The KDSDVSRF job deletes all the&rvhilev.&rte.RKDS* and &rvhilev.&rte.RKMS* monitoring server VSAM libraries, and allocates andinitializes a new set. This job is useful if you must reinitialize a remote monitoring server or convert ahub monitoring server to a remote.

Important: Use the KDSDVSRF job with caution. It deletes all monitoring server VSAM libraries.The KDSDVSRN job renames the original VSAM libraries. If you prefer to rename the original VSAMlibraries instead of deleting them, use the KDSDVSRN job to rename the original libraries before yousubmit the KDSDVSRF job. The monitoring server must be stopped before you run either job.

v New libraries and started task DDNAMEs. A number of new runtime libraries support new features ofthe monitoring server on z/OS, and corresponding DDNAMEs are added to the monitoring serverstarted task. Table 1 lists the new libraries and DDNAMEs.

Table 1. New monitoring server runtime libraries and started task DDNAMEs

DDNAME Library suffix Description VSAM or non-VSAMHub, remote, orboth

DSEVT RKDSEVT EIF event PDSE Non-VSAM Hub

QA1CSPRD RKDSSPRD Role security VSAM Both

QA1CSPRR RKDSSPRR Role security VSAM Both

QA1DCALE RKDSCALE Dynamic threshold VSAM Both

QA1DCONP RKDSCONP Configuration properties VSAM Both

QA1DCPRM RKDSCPRM Deploy asynchronous commandconfiguration parameter

VSAM Both

QA1DDYST RKDSDYST Deploy asynchronous commandstatus

VSAM Both

QA1DEPRM RKDSEPRM Deploy asynchronous commandexecution parameter

VSAM Both

QA1DGRPA RKDSGRPA TGROUP group VSAM Both

QA1DGRPI RKDSGRPI TGROUPI individual group VSAM Both

QA1DNAME RKDSNAME Long name alias VSAM Both

QA1DOVRD RKDSOVRD Dynamic threshold VSAM Both

QA1DOVRI RKDSOVRI Dynamic threshold VSAM Both

QA1DBUNG RKDSBUNG Bundle group member VSAM Hub

QA1DEVMP RKDSEVMP EIF event mapping VSAM Hub

QA1DEVSR RKDSEVSR EIF event VSAM Hub

QA1DGRPB RKDSGRPB TGROUP group VSAM Hub

QA1DGRPC RKDSGRPC TGROUPI individual group VSAM Hub

QA1DPYMR RKDSPYMR Deploy group member VSAM Hub

QA1DAPPL &&rvhilev.&&rte.RKDSAPPL

VSAM library for the self-describingagents' application properties

VSAM Both

The new libraries are allocated as part of the runtime environment build job in a new environment or aspart of the Tivoli Enterprise Monitoring Server upgrade job.

v Reconnect after TCP/IP recycle. This setting allows the monitoring server address space to reconnectto its TCP/IP stack without being recycled after the stack is recycled.


v Default TCP/IP started task name. Sets the default TCP/IP started task name to a wildcard * (asterisk)for new runtime environments. This default, which uses the first TCP/IP stack that was started, issuitable if the LPAR contains a single TCP/IP stack. If the LPAR contains more than one TCP/IP stack,you can specify the started task name of the TCP/IP stack you want to use, or you can specify thenumber sign (#), which is translated to a blank and allows the TCP/IP environment to choose the stackto use, either through TCP/IP definitions or through the use of the SYSTCPD DD statement. If the IPdomain name resolution is not fully configured on the z/OS system, you must specify the SYSTCPDDDNAME in the started task for each monitoring server and monitoring agent. For further information,see "Decision 5: how to set up communications between components" in the "Planning yourdeployment" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide.

v Network interface support. If your site runs more than one TCP/IP interface or network adapter on thesame z/OS image, you can indicate the specific local network interfaces to be used by monitoringservers and monitoring agents on z/OS. For further information, see "Decision 5: how to set upcommunications between components" in the "Planning your deployment" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.



Chapter 2. Planning your deployment

The information in this chapter is intended to help you plan a first-time deployment. If you are upgradingyour monitoring servers on z/OS from a previous version, follow the instructions in the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Upgrade Guide.

For a first-time deployment, review the prerequisites and make the planning decisions described in Part 1of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide. Then make the planning decisions described in this chapter:

__ “Decision 1: What kinds of monitoring servers to configure”

__ “Decision 2: Whether and how to enable event forwarding” on page 22

Decision 1: What kinds of monitoring servers to configureThe hub monitoring server is the focal point for the entire monitoring environment. This server is under asignificant load. Work on the hub includes communicating with remote monitoring servers, with the TivoliEnterprise Portal Server, and with local monitoring agents; authenticating users; consolidating anddistributing data; storing and tracking situations and policies; and initiating and tracking all generated TakeAction commands.

Place the hub monitoring server inside the data center on a high-performance network. Connectivitybetween the hub monitoring server and the portal server and between the hub and remote monitoringservers must be fast and reliable.

Remote monitoring servers communicate only with the monitoring agents that report to them and with thehub monitoring server to which they report. Note that a remote monitoring server is remote with respect tothe hub monitoring server, not necessarily with respect to the monitoring agents. If monitoring agents areinstalled on the same system as a remote monitoring server, that monitoring server is local to themonitoring agents but remote to the hub.

The load on remote monitoring servers is typically low. Load is driven higher if historical data collection isperformed on the monitoring servers instead of on the monitoring agents.

You can install monitoring servers on z/OS, Windows, and some UNIX and Linux systems. See IBM TivoliMonitoring: Installation and Setup Guide for a complete list of supported platforms.

See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planningand Configuration Guide for considerations in deciding where to place hub and remote monitoring servers,for information about monitoring server names, and for planning information for the SOAP server.

Whether to configure a high-availability hub on z/OSAn operational hub monitoring server is essential to a monitoring environment. If the hub monitoring serveraddress space fails, or if the system on which the hub is installed has a planned or unplanned outage, theflow of monitoring data comes to a halt. Therefore, it is important to restart the hub or move it to anothersystem as quickly as possible.

You can configure a high-availability hub monitoring server in any sysplex environment with dynamic virtualIP addressing (DVIPA) and shared DASD. A high-availability hub is configured in its own runtimeenvironment, without any monitoring agents, and can be configured on the same LPAR with a remotemonitoring server. This configuration allows the hub monitoring server to be relocated to any suitableLPAR in the sysplex with no changes, and with minimal disruption to the components connecting to thehub.


If you have purchased the Tivoli System Automation for z/OS product, you can automate the relocation ofthe hub. To find instructions, search for automating a high availability hub on the Integrated ServiceManagement Library website.

The high-availability hub on z/OS has the following requirements:

v It must be configured in a sysplex.

v It must have a dynamic virtual IP address (DVIPA), so it can respond to the same IP address on anyLPAR in the sysplex.

v It must be configured stand-alone (in its own runtime environment without monitoring agents).

v Its runtime libraries must be stored on shared DASD, so that the hub can start on any LPAR in thesysplex without requiring replication of the libraries.

v Its runtime environment cannot use system variables. The hub is not defined to run on any specificsystem, and it retains the same parameter values on any system in the sysplex.

Tip: If your environment fulfills the requirements for a high-availability hub, it is a good idea to configureone. Before you begin configuring the high-availability hub, create an application-instance-specific (private)dynamic virtual IP address, and define it to DNS as a new name (for example, OMEGAHUB).

For instructions on configuring a high-availability hub on z/OS if you are configuring components andproducts for the first time, see Chapter 3, “Configuring a high-availability hub and the remote monitoringservers that report to it,” on page 27. For instructions on modifying an existing configuration toaccommodate a high-availability hub, search for high-availability hub on the Integrated ServiceManagement Library website.

For instructions on configuring a high-availability hub on a distributed system, see the IBM TivoliMonitoring: High-Availability Guide for Distributed Systems.

How many remote monitoring servers to configureIf possible, place a remote monitoring server on every z/OS system where you are installing monitoringagents. In fact, two monitoring agents (OMEGAMON XE on z/OS and OMEGAMON XE for Storage onz/OS) require that you configure them in the same address space as a hub or remote monitoring server.

For advice about placing remote monitoring servers on distributed systems, see IBM Tivoli Monitoring:Installation and Setup Guide.


http://www.ibm.com/software/brandcatalog/ismlibrary/




Tips

v A remote monitoring server can report to a high-availability hub on the same LPAR.

v If the hub is not a high-availability hub, it cannot be on the same LPAR as any of the remotemonitoring servers that report to it and that are configured to use any TCP/IP protocol.

v If more than one remote monitoring server is configured in a z/OS image and if a TCP/IP protocolis being used for communication, the hub to which each remote monitoring server reports musthave a unique port number. Otherwise, connectivity problems are likely.

v If more than one hub is configured in a z/OS image, each hub must have a unique port number forany nonsecure TCP/IP protocols being used and a unique port number for any secure TCP/IPprotocols being used.

For information about port number allocation, see the "Port number assignments" section of theIBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planningand Configuration Guide.

v If a remote monitoring server is to communicate with any monitoring agents that require SNA, theremote monitoring server must be configured for SNA communications. Examples of suchmonitoring agents include OMEGAMON XE on z/OS (for the EPILOG facility of the OMEGAMONII® component) and OMEGAMON XE for Messaging on z/OS (for the 3270 interface component).See the product-specific configuration guides for further information about SNA requirements.

Whether to enable the self-describing agents capabilityThe self-describing agents enhancement is intended to reduce the time you spend getting the commoncomponents of Tivoli Management Services and the monitoring agents that use them up and running, aswell as the time and cost of maintaining Tivoli Monitoring products and components once you have themrunning. In addition, self-describing agents make it unnecessary for you to bring Tivoli Monitoringcomponents down and then back up so these newly installed or upgraded agents can be recognized; thiscan save your site significant wasted monitoring productivity.

As of Version 6.2.3, the application data necessary for the Tivoli Enterprise Monitoring Server to recognizeand process data from a distributed agent need no longer be "seeded" at installation into the agent's localmonitoring server and then replicated out to the hub monitoring server and all other Tivoli ManagementServices components that require it (such as the Tivoli Enterprise Portal Server and the Tivoli DataWarehouse). Instead, this application support data can now be automatically replicated from the agent toits local monitoring server whenever the agent starts up. Thus, it is also no longer necessary that youfollow each seeding step by restarting all affected Tivoli Management Services components so they canrecognize and process data generated by these newly installed or upgraded agents.

After you activate the self-describing agents capability, application support is automatically refreshedwhenever a newer version of a self-describing agent is detected. Also, components need not be recycledevery time an update is applied (similarly, its situations, policies, and activities are automaticallyredistributed and restarted), nor is it necessary each time a newly updated agent connects to itsmonitoring server—each update is seeded once and only once. This means you need not interrupt yourenterprise monitoring whenever you add a new self-describing agent or update an existing agent. Thisenhancement also means that no mainframe agents' application data need be stored on distributedsystems.

All updates are logged for auditing purposes. If the hub monitoring server is ever brought down,self-describing capabilities are terminated until it is brought back online.

The self-describing agents capability can be selectively disabled on the Tivoli Enterprise Monitoring Serverrunning on z/OS, and is initially disabled when installing a hub Tivoli Enterprise Monitoring Server. It isinitially enabled for remote monitoring servers; this effectively disables support for all self-describing agents

Chapter 2. Planning your deployment 15

connected to either the hub or one of its remotes. Thus, enabling the self-description capability requiresonly that you enable it at the hub monitoring server, as shown in this example.

Example of activating self-describing agents at the hub and its three remotesYour site has defined one hub monitoring server named HUBTEMS and three remote monitoringservers, RTEMS1, RTEMS2, and RTEMS3, that report to it. You have not yet touched theself-describing capabilities at any of these monitoring servers; thus, their initial environment is asfollows:

v Self-describing agents are initially turned on at all three remote monitoring servers but turned off atthe hub monitoring server.

v Since self-describing agents are turned off at the hub, their self-describing capabilities areeffectively turned off everywhere, regardless of which monitoring server they actually connect to.

v Turning on the agents' self-describing capabilities requires only that you turn it on at the hub,HUBTEMS.


Note about Java usage and USSOnce your site activates self-describing agents on a hub Tivoli Enterprise Monitoring Server, themonitoring server must have access to a Java Runtime Environment running under IBM's 31-bit or64-bit Java SDK Version 5 (or higher) and an HFS or zFS file system accessed through UNIXSystem Services (USS). The self-describing agent function stores the application support packages inthe USS file system and then invokes the Java jar command to extract the files from the applicationsupport packages stored there. Since IBM's Java runs on z/OS under UNIX System Services (USS),this also means USS must be available with ~50MB of working space. If your environment has morethan 10-15 agent types, see the hardware and software requirements section of the IBM TivoliMonitoring: Installation and Setup Guide for more details on the storage requirements.

When using the self-describing agents feature on a Tivoli Enterprise Monitoring Server running onz/OS, ICAT requests that you supply the UNIX System Services (USS) directory where Java isinstalled. The value you supply gets set as the TEMS_JAVA_BINPATH statement in the KDSDPROFfile, which is created in the monitoring server's USS support directory.

When a version 6.2.3 monitoring server running on z/OS installs a self-describing agent, it prependsthe TEMS_JAVA_BINPATH value to the default USS PATH setting so it can locate the Java /bindirectory where the jar utility resides. The jar utility is required to extract the files from the applicationsupport packages that were uploaded from the agent.

You must ensure that there isn't an older or inconsistent version of Java still left over in the defaultUSS PATH or LIBPATH libraries, because the older Java binaries may conflict with the Java binariesin the directory you supplied to ICAT. For example, the default LIBPATH on most USS systems isLIBPATH=/lib:/usr/lib:. Because this specification contains no Java binary directories, it won't conflictwith the TEMS_JAVA_BINPATH setting, and so the TEMS-invoked jar utility should run successfully.

But if there is a LIBPATH setting that includes a Java directory with a different version of Java thanyou specified to ICAT, it could cause the self-describing function to fail when it calls the jar utility.This occurs because the TEMS_JAVA_BINPATH value specifying one Java version has beenprepended to the PATH setting, with a different Java version specified in LIBPATH. If these areincompatible Java versions, the jar utility cannot work correctly.

To resolve this problem, update the default USS LIBPATH setting so that it either omits the Javadirectory or specifies a directory at the same Java level as that provided to ICAT. IBM recommendsthat, if the jar utility invoked by the monitoring server fails to complete successfully, you verify thatthere isn't an inconsistent level of Java specified in the default USS PATH or LIBPATH setting thatmay be causing a binary incompatibility.

Whether to enable the auditing functionThe auditing function allows you to capture significant events occurring in your site's IBM Tivoli Monitoringenvironment and record them in permanent storage for later retrieval and analysis. Each audit record fullydescribes some event that has changed the state of your Tivoli Monitoring system: authorization andauthentication failures (such as those that allow or disallow the execution of Take Action commands), andmajor and minor state changes (though they do not reflect the minor service messages stored in the RASlogs). Platforms covered include Windows, UNIX/Linux, i5/OS, and z/OS. The records stored arecompatible with those created by Tivoli Business Service Manager.

These new auditing and logging records can be stored in the Tivoli Data Warehouse. Standard reports areprovided via the Tivoli Common Reporting feature. In addition, the Tivoli Enterprise Portal ManagedSystem Lists workspace (within the Enterprise icon) enables you to view auditing and logging recordsonline; see the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide for information.


Initially the auditing function is turned off by default on all Tivoli Management Services nodes.

On z/OS, the auditing facility optionally creates and stores Systems Management Facility–format (SMF)type-112 records, coded in UTF8 and included in a common repository (the SYS1.MANn data sets) with allother z/OS event data. Note that SMF type-112 records are disabled by default in theSYS1.PARMLIB(SMFPRMxx) member. To display the current SMFPRMxx settings, invoke the z/OSconsole command D SMF. For complete information on the syntax of this console command, includinghow you check which records are enabled for recording and how you dynamically change these settings,consult the z/OS System Management Facilities document and the MVS System Commands reference.

At this release, the auditing data written covers the new self-describing agents (including their auto-refreshfeature), actions of the Warehouse Proxy Agent, successful and failed automation-command actions (forexample, the invocation of Take Action commands), and IBM Tivoli Monitoring's integration with TivoliApplication Dependency Discovery Manager.

Environment variables that control the auditing functionThere are two environment variables that affect the auditing function when running on a z/OS-based TivoliEnterprise Monitoring Server:

AUDIT_TRACEThe auditing facility supports three levels of tracing:

setting result

Minimum Records major changes to the product state such as authorization failure, newconnections to the monitoring server or the portal server, or failed user loginattempts.

Basic Records any actions that modify objects or cause an access failure, such asattempts to modify monitoring server entities like situations and Take Actioncommands.

This is the default tracing level.

Detail Records all authorization requests, whether successful or failed, such as allsuccessful logins and all modifications to entities such as Take Action commands.

Disabled Disables the auditing function.

AUDIT_SMFz/OS only.

Controls the writing of auditing records to the System Management Facility.

setting result

Disabled Prevents the creation of SMF records while still allowing IBM Tivoli Monitoringaudit data to be recorded in the Tivoli Data Warehouse and for reporting purposes.

Enabled Both SMF and warehouse audit records get written.

This is the default for SMF recording.

Note: The AUDIT_SMF parameter is not exposed in either the PARMGEN or the ICATconfiguration methods. To access this parameter and reset its value, use the Specify NonstandardParameters screen; see IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services onz/OS: Common Planning and Configuration Guide for details.

Setting the trace level to Basic or Detail might require you to enlarge your SYS1.MANn data sets or toincrease the frequency with which you offload Tivoli Monitoring audit data to your SMF archives. If you donot want to record Tivoli Monitoring events, you can disable SMF audit records (AUDIT_SMF=Disabled)and thereby eliminate the storage requirements and I/O overhead necessary when writing SMF records.


SMF recording of audit recordsYou can configure the Tivoli Enterprise Monitoring Server running on z/OS to write audit records to thez/OS System Management Facility (SMF). This enables you to use SMF to integrate Tivoli Monitoringevents with the event data recorded by other products and components that run on your z/OS system: youcan extract Tivoli Monitoring audit record data from SMF data sets (or from the archives of such data sets)for analysis of performance or resource utilization, and for validation of security events (authorization andauthentication).

SMF provides facilities that let you suppress recording of SMF records by record types, event types (listedin Table 2 as record subtypes), and product codes (known as subsystem IDs, or SSIs).

Table 2. SMF type-112 record subtypes

SMF 112 subtype Event type category

32 (0x20) permission checking

33 (0x21) object maintenance

34 (0x22) security maintenance

35 (0x23) system administration

36 (0x24) authorization validation

37 (0x25) contextual event

38–47 (0x26 through 0x2f) reserved

SMF record 112 subtypes 32–37 (0x20 through 0x25) share a common, fixed header format followed by avariable-length field of up to 8,912 bytes that contains XML-encoded event data, as shown in Table 3.

Table 3. SMF record 112 format

Name Assembler name Type Length Offset Description

smf112len SMF112LEN Binary(unsigned short)

2 0 Record length (RDW1).Maximum size 32756. This fieldand the next (total of four bytes)form the record descriptor word(RDW). The first two bytes (thisfield) must contain the logicalrecord length including theRDW1 field. The second twobytes (the following field) areused for variable-block, spannedrecords. If the record is notspanned, set these two bytes tohexadecimal zeros.

smf112seg SMF112SEG Binary(unsigned short)

2 2 (0x02) Segment descriptor (RDW2); seesmf112len field above.


Table 3. SMF record 112 format (continued)


smf112flg#definedconstants:

FLGSTYFLGSP4FLGSP3FLGSP2FLGVS2

SMF112FLGpredefined EQUconstants:

FLGSTYFLGSP4FLGSP3FLGSP2FLGVS2

Binary(unsigned char)predefined values:

0x400x100x080x040x02

1 4 (0x04) Header flag byte. Contains thesystem indicator bits.

Bit Meaning when set0 Reserved.1 Subtypes are valid.2 Reserved.3 MVS/SP Version 4 and

above. Bits 3, 4, 5, and6 are on.Note: IBMrecommends you userecord type 30 to obtainthe MVS™ product level.

4 MVS/SP Version 3. Bits4, 5, and 6 are on.

5 MVS/SP Version 2. Bits5 and 6 are on.

6 VS2. Bit 6 is on.7 Reserved.

System indicator bits areautomatically set when therecord is written.

smf112rty#definedconstants:

RTY112

SMF112RTYpredefined EQUconstants:

RTY112

Binary(unsigned char)predefined values:

112 (0x40)

1 5 (0x05) Record type (hexadecimal valuesare 0-FF). Record type 112(0x70) for this record type.

smf112tme SMF112TME Binary(unsigned int)

4 6 (0x06) Time since midnight, inhundredths of a second, that therecord was moved into the SMFbuffer.

smf112dte SMF112DTE Packed Decimal(char [4])

4 10 (0x0A) Date when the record wasmoved into the SMF buffer, inthe form 00yydddF or 0cyydddF(where c is 0 for 19xx and 1 for20xx, yy is the current year(0-99), ddd is the current day(1-366), and F is the sign).

smf112sid SMF112SID Char(char [4])

4 14 (0x0E) System identification (also knownas the SMFID).

smf112ssi SMF112SSI Char(char [4])

4 18 (0x12) Subsystem ID(OMEGAMON product code).This field is a four-byte charactervalue set by theSUBSYS=option keywordspecified to SMF. Refer tomember RKANSAM(KOLSSI) fora partial list of product codes.


Table 3. SMF record 112 format (continued)


smf112sty#definedconstants:

STY_EVENT_CHECKINGSTY_EVENT_OBJMAINTSTY_EVENT_SECMAINTSTY_EVENT_SYSADMINSTY_EVENT_ACTION

STY_EVENT_VALIDATE

SMF112STYpredefined EQUconstants:

STY_EVENT_CHECKINGSTY_EVENT_OBJMAINTSTY_EVENT_SECMAINTSTY_EVENT_SYSADMINSTY_EVENT_ACTION

STY_EVENT_VALIDATE

Halfword(unsigned short)predefined values:

32 (0x20)33 (0x21)34 (0x22)35 (0x23)36 (0x24)

37 (0x25)

2 22 (0x16) Record subtype 32-37(0x20-0x25):

Permission Checking eventObject Maintenance eventSecurity Maintenance eventSystem Administration eventAuthorization Validation

eventContextual event

ai_ver#definedconstants:

AICVER

AIVERpredefined EQUconstants:

AICVER

Fullword(unsigned long)predefined values:

1

4 24 (0x18) Audit information version. Thisrelease is 1.

ai_jname AIJNAME Char(char [8])

8 28 (0x1c) Name of the address spaceissuing this SMF record.

ai_asid AIASID Halfword(unsigned short)

2 36 (0x24) ID of the address space issuingthis SMF record.

ai_event_len AIEVENTLEN Halfword(unsigned short)

2 38 (0x26) Length of the null-terminatedstring in ai_event_info, includingthe null terminator. Smallestlength is 1 for a null string.

ai_event_info AIEVENTINFO Char(char [8192])

1-8192 40 (0x28) A null-terminated stringcontaining the audit event dataencoded in XML. The maximumlength of this field is 8192 bytes,but the actual length is specifiedby ai_event_len. The contents ofthe field depend on the recordsubtype, which is directlyassociated with the Event TypeCategory for this record. Refer toTable 2 on page 19 for furtherinformation.

In addition, your site can write its own exits that programmatically decide which records are suppressed;see the z/OS System Management Facilities reference for details.


The following sample Tivoli Monitoring RKANSAM library members are provided to assist you in extractingdata from various subtypes of type-112 records:

Member Contents

KOLSMFA Record format as an assembler language DSECT.

KOLSMFC Record format as a C typedef.

KOLSMFCX Sample program to extract and print the contents of IBM Tivoli Monitoring SMF records.

KOLSMFCC Sample JCL to compile RKANSAM(KOLSMFCX).

KOLSMFS Record format as a SAS DATA statement.

KOLSMFSX Sample SAS program to extract and print the contents of Tivoli Monitoring SMF records.

KOLSMFSC Sample JCL to run RKANSAM(KOLSMFSX).

KOLSSI Partial list of product codes (SSIs) mapped to Tivoli product names.

Additional reference material is provided on the Tools DVD in the XML directory: see either kolddtd.samplibor the copy in the runtime environment's RKANSAM library, member KOLDDT. This DTD (document typedefinition) contains XML metadata that describes each XML record's constituent fields and their contents.

Decision 2: Whether and how to enable event forwardingIf you use either the Tivoli Enterprise Console or Netcool/OMNIbus product, in addition to the TivoliEnterprise Portal, to manage events in your enterprise, you can configure a z/OS hub monitoring server toforward situation events to these event servers for correlation and management.

The hub monitoring server uses a Situation Event Forwarder component. The Event Forwarder mapssituation events to Tivoli Event Integration Facility (EIF) events and uses the EIF interface to send theevents to a Tivoli Enterprise Console event server or to an OMNIbus EIF probe (the EIF receivers). Theevent receivers receive the forwarded events, and expand and format the events for the event servers. Onthe Tivoli Enterprise Console or OMNIbus console, users can view, acknowledge, or reset situation events.The updated situation status is returned to the originating hub monitoring server and reflected in the TivoliEnterprise Console or OMNIbus console.

The EIF is an application programming interface (API) that external applications can use to create, send,or receive events. These events are in the same format as Tivoli Enterprise Console events and arereferred to as either EIF events or TEC/EIF events. For complete information about EIF, see the IBM TivoliEnterprise Console Event Integration Facility Reference. In the IBM Tivoli Monitoring: Administrator'sGuide, the section "Customizing event integration with Tivoli Enterprise Console" discusses the mapping ofsituation events to Tivoli Enterprise Console events; and the section "Customizing event integration withTivoli Netcool/OMNIbus" discusses the mapping of situation events to OMNIbus events.

In addition to using the Configuration Tool to enable EIF forwarding and to specify the default destinationserver, the following tasks must be completed outside the Configuration Tool to implement situation eventforwarding:

v The destination event server or servers must be configured to receive the events.

v A situation update forwarding process (the event synchronization component) must be installed on theevent receivers.

v For situation events forwarded to the Tivoli Enterprise Console:

– The .baroc files for the monitoring agents reporting to the hub must be installed and imported on theTivoli Enterprise Console server, and the rule base must be updated.

– If any distributed agents report either directly or indirectly (through a distributed remote monitoringserver) to a z/OS hub, map and resource files for each monitoring agent must be transferred from a


hub monitoring server on a Windows, Linux, or UNIX system to the RKANDATV library of the runtimeenvironment that contains the hub monitoring server on z/OS. See “Map, .baroc, and resource files”on page 125 for details.

– If z/OS agents report to a z/OS hub monitoring server in another CSI, their map files must be copiedto the RKANDATV library of the runtime environment that contains the hub.

The section on "Integrating event management systems" in the IBM Tivoli Monitoring: Installation andSetup Guide provides detailed instructions for configuring the Tivoli Enterprise Console and OMNIbus toreceive forwarded events, including installing the event synchronization component and the .baroc files.

Tip: If you already have workflow policies containing emitter activities that send events to the TivoliEnterprise Console, turning on EIF event forwarding results in duplicate events. You can deactivate theemitter activities within policies by selecting Disable Workflow Policy/Tivoli Emitter Agent EventForwarding when you configure the monitoring server. However, it is likely that the policies invoking theTivoli Enterprise Console emitter are doing little else. If you deactivate these activities, there is no point inrunning the policies. You might want to delete policies that are no longer required, instead of disablingthem.

If situation event forwarding is enabled, by default all situation events are forwarded to the EIF destinationsdefined when you configured the monitoring server. However, you can configure additional EIF receiversand selectively forward situation events to different destinations by using the EIF tab of the TivoliEnterprise Portal Situation editor. You can also use the EIF tab to assign a Tivoli Enterprise Console orOMNIbus severity to a situation.

The severity of EIF events is derived from the situation name. The severity is determined as follows:

v If the suffix of the situation name is either _Warn or _Warning, the EIF event severity is set to WARNING.

v If the suffix is either _Crit or _Critical, the severity is set to CRITICAL.

v If the severity cannot be determined from the suffix, a severity of UNKNOWN is assumed.

You might have to use the EIF tab to set the severity for situations that display in the Tivoli EnterpriseConsole or OMNIbus console with a severity of UNKNOWN. See the IBM Tivoli Monitoring: TivoliEnterprise Portal User's Guide for instructions on using the Situation editor to assign a situation severity.



Part 2. Configuring hub and remote monitoring servers onz/OS

The chapters in this part of Configuring the Tivoli Enterprise Monitoring Server on z/OS give instructionsfor configuring the monitoring server.

Navigation tips

v If you are upgrading a monitoring server on z/OS from a previous version, follow the instructions inthe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Upgrade Guide.

v For a first-time configuration, follow this path:

1. Follow the instructions in Part 2 of the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

2. For a hub monitoring server on z/OS, follow the instructions in one of the following chapters:

– To configure a high-availability hub on z/OS and the remote monitoring servers on z/OS thatreport to it, follow the instructions in Chapter 3, “Configuring a high-availability hub and theremote monitoring servers that report to it,” on page 27.

– To configure a hub monitoring server in a z/OS environment that does not support thehigh-availability hub, follow the instructions in Chapter 4, “Configuring the hub monitoringserver and monitoring agents in the same runtime environment,” on page 79.

3. To configure any additional remote monitoring servers, follow the instructions in one of thefollowing locations:

– To configure a remote monitoring server on z/OS to report to a hub on a Linux, UNIX, orWindows system, follow the instructions in Chapter 5, “Configuring a remote monitoringserver on z/OS to report to a distributed hub,” on page 99.

– To configure a remote monitoring server on a distributed system to report to a z/OS hub,follow the instructions in the IBM Tivoli Monitoring: Installation and Setup Guide.

4. Go on to Part 3, “Post-configuration procedures,” on page 117.

Note to PARMGEN users: If after having built a static hub monitoring server on z/OS you decide toconvert it to a remote monitoring server, a scenario that describes this process, “Scenario PGN04: clonean existing environment but convert its hub monitoring server to a remote", is provided in the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: PARMGEN Reference.



Chapter 3. Configuring a high-availability hub and the remotemonitoring servers that report to it

The first monitoring server you configure must be a hub. If your environment supports the requirements fora high-availability hub, there are important advantages to configuring one. (See “Whether to configure ahigh-availability hub on z/OS” on page 13.) This chapter explains how to configure a high-availability hubmonitoring server on z/OS and then how to configure remote monitoring servers on z/OS to report to it.

The configuration shown in Figure 2 depicts the high-availability hub monitoring server connected to aremote monitoring server on the same LPAR, to remote monitoring servers on other LPARs, to remotemonitoring servers on distributed systems, and to the portal server. This configuration is resilient andefficient: resilient because the high-availability hub can be relocated to any LPAR in the sysplex withminimal disruption to the other components, and efficient because the remote monitoring server on thesame LPAR as the hub handles all communications with the monitoring agents and thus reduces the loadon the hub.

Tip: The high-availability hub is the only type of hub that can be on the same LPAR with a remotemonitoring server that reports to it. See “Decision 1: What kinds of monitoring servers to configure” onpage 13

PARMGEN methodComplete these steps to configure a runtime environment for the high-availability hub and another runtimeenvironment on the same LPAR for a remote monitoring server.

Step 1. Create and configure a runtime environment for thehigh-availability hubFollow the steps in "Scenario PGN03: perform a pristine install of a high-availability hub monitoring server"of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: PARMGEN Referenceto create a runtime environment for the high-availability hub. Also refer to the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Parameter Reference for information about theparameters in the configuration profile. The configuration profile is the &rhilev.&rte.WCONFIG(&rte)member.

Figure 2. High-availability hub monitoring server and its connections


Tips

v The parameters shown in this section are specific to the high-availability hub but are not the onlyparameters for which you must either accept or override the default values in the configurationprofile for the runtime environment. After you set the parameters shown here, be sure to gothrough the entire configuration profile to make sure the parameter values are correct for theconfiguration you want.

v The parameters with names beginning KDS_HUB are not parameters for the hub monitoringserver; they are parameters for remote monitoring servers.

v Be sure to uncomment any parameters that are needed for your configuration but are commentedout by default. For example, if you intend to configure OMEGAMON XE for CICS® on z/OS andOMEGAMON XE on z/OS to report to the high-availability hub, uncomment this line of theconfiguration profile by removing the two asterisks (**) from the beginning of the line:

Before:**KDS_TEMS_HA_INCLUDE_KM5 "Y" * OMXE on z/OS Agent

After:KDS_TEMS_HA_INCLUDE_KM5 "Y" * OMXE on z/OS Agent

Be sure to set the following parameter values for the high-availability hub in the configuration profile:* Tivoli Enterprise Monitoring Server: KDS flagCONFIGURE_TEMS_KDS "Y"

** (Optional) z/OS System Variable setting:** Specify "Y" if you are using symbolics as parameter values.RTE_SYSV_SYSVAR_FLAG N

** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:RTE_TEMS_CONFIGURED_FLAG YRTE_TEMS_NAME_NODEID "rte_name:CMS"

** TEMS configuration values:KDS_TEMS_TYPE HUB

** Begin - High Availability (HA) Hub TEMS section:** High Availability (HA) Hub TEMS values:** Note: Specify "HA" if you want to enable this Hub TEMS for High** Availability support:KDS_TEMS_HA_TYPE "HA"

The following additional requirements also apply to the high-availability hub configuration:

KDS_TEMS_COMM_PROTOCOLn parameterAt least one of the values must be IPPIPE, IP6PIPE, IPSPIPE, or IP6SPIPE. For more informationabout the communication protocols, see "Decision 5: How to set up communications betweencomponents" in the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide.

KDS_TEMS_TCP_HOST parameterThe value must be the application-instance-specific (private) dynamic virtual IP address you havedefined to the Domain Name Server (DNS).

KDS_TEMS_TCP_KDEB_INTERFACELIST parameterThe value must be !dvipa_hostname, where dvipa_hostname is the private DVIPA name set for theKDS_TEMS_TCP_HOST parameter. This setting ensures that the high-availability hub is restrictedto its private DVIPA address and cannot interfere with the remote monitoring server configured onthe same LPAR.


KDS_TEMS_VIRTUAL_IP_ADDRESS parameterThe value must be D (for DVIPA).

Many other KDS_* parameters are needed for the hub monitoring server configuration. See the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference forinformation about them.

After you finish customizing the configuration profile, go on to "Step 3. Submit batch jobs to complete thePARMGEN setup" in the "Configuring products with the PARMGEN method" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

Configuring the monitoring server to support encryption/decryptionTo activate ICSF encryption/decryption within your newly configured high-availability hub monitoring serverusing the PARMGEN configuration method, locate these lines in the configuration profile for the runtimeenvironment of the monitoring server::** GBL_DSN_CSF_* ICSF system libraries:GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"** TMS KAES256 password encryption key:**KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"

Set GBL_DSN_CSF_SCSFMOD0 to the name of your site's Integrated Cryptographic Service Facility(ICSF) library. Uncomment KDS_TEMS_SECURITY_KAES256_ENCKEY, and set it to your site's ICSFencryption key for IBM Tivoli Monitoring.

Once you have set these parameters, if you enabled ICSF password encryption for your monitoring serverafter creating the runtime environment, rerun the following jobs:

WCONFIG($PARSE*)File-tailoring job to recreate:

WKANSAMU(KDSDKAES)Stand-alone Tivoli Management Services on z/OS password encryption job, if you want asample job that you can edit manually.

WKANSAMU(KCIJPSEC)Composite security job's KAES256 step, if you want a file-tailored job.

WKANSAMU(CANSDSST)Monitoring server started task to concatenate the ICSF load library in the STEPLIBDDNAME.

CANSDSST is the IBM-supplied default; set the value to whatever you specified for theKDS_TEMS_STC parameter.

WKANSAMU(KDSDKAES) or WKANSAMU(KCIJPSEC)Creates the encryption key member.

WKANPARU(KAES256) or WKANSAMU(KCISYPJB)Run either WKANPARU(KAES256), the stand-alone started task procedure copy job, orWKANSAMU(KCIJPSYS), the composite system copy job that copies the modified monitoringserver started task to the system procedure library.

(Optional) Configuring the monitoring server to support self-describing agentsTo enable support for self-describing agents with the PARMGEN configuration method, uncomment thisline in the configuration profile for the runtime environment of the monitoring server:**KDS_KMS_SDA "Y" * Y, N

To disable support, uncomment the line and set the KDS_KMS_SDA parameter value to "N".

Chapter 3. Configuring a high-availability hub and the remote monitoring servers that report to it 29

For more information on self-describing agents, see “Whether to enable the self-describing agentscapability” on page 15.

(Optional) Configuring the monitoring server to support the auditing featureTo enable the auditing feature (see “Whether to enable the auditing function” on page 17) with thePARMGEN configuration method, locate these lines in the configuration profile for the runtime environmentof the monitoring server, and uncomment them:** Audit parameters:** Note:** Specify M=Minimum, B=Basic, D=Detail or X=Disabled to enable or** disable z/OS SMF output (z/Secure).**KDS_AUDIT_TRACE "B" * M, B, D, or X** Specify the maximum entries in the in-memory cache reported by** queries.**KDS_AUDIT_MAX_HIST "100" * 10-1000** Specify an identifier that may be used to associate audit** records.**KDS_AUDIT_ITM_DOMAIN ""

Set the KDS_AUDIT_TRACE parameter to M, B, D, or X, as explained in “Environment variables thatcontrol the auditing function” on page 18. Set KDS_AUDIT_MAX_HIST to any value from 10 to 1000,depending on the number of audit records you want kept in the in-memory cache before writing them out.To group audit records by related agents and monitoring servers, set KDS_AUDIT_ITM_DOMAIN to thename you assigned to that group.

To disable auditing, set KDS_AUDIT_TRACE to "X".

Step 2. Configure a remote monitoring server to report to thehigh-availability hubAfter you finish configuring a runtime environment for the high-availability hub, create a second runtimeenvironment on the same LPAR, and configure a remote monitoring server to report to the high-availabilityhub.

Tips

v The parameters shown in this section are specific to a remote monitoring server reporting to thehigh-availability hub, but they are not the only parameters for which you must either accept oroverride the default values in the configuration profile for the runtime environment. After you setthe parameters shown here, be sure to go through the entire configuration profile to make sure theparameter values are correct for the configuration you want.

v Be sure to uncomment any parameters that are needed for your configuration but are commentedout by default. For example, the configuration profile for a runtime environment containing aremote monitoring server that reports to the high-availability hub requires theKDS_HUB_TEMS_HA_TYPE parameter, which is commented out by default. For such aconfiguration, you must uncomment this parameter and insert HA between the quotation marks forthe parameter value.

Before:**KDS_HUB_TEMS_HA_TYPE ""

After:KDS_HUB_TEMS_HA_TYPE "HA"

In the configuration profile of the second runtime environment, set the following parameter values for theremote monitoring server:


** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:RTE_TEMS_CONFIGURED_FLAG YRTE_TEMS_NAME_NODEID "remote_rte_name:CMS"

** TEMS configuration values:KDS_TEMS_TYPE REMOTE

** If the TEMS is a Remote, uncomment the KDS_HUB_* parameters** and specify the Hub values accordingly:KDS_HUB_TEMS_NAME_NODEID "ha_hub_rte_name:CMS"

** If the TEMS is a Remote and its Hub TEMS is enabled for** High Availability (HA) support (specify "HA"):KDS_HUB_TEMS_HA_TYPE "HA"

The following additional requirements also apply to the remote monitoring server configuration:

KDS_TEMS_COMM_PROTOCOLn parameterAt least one of the communication protocols must be the same as a protocol selected for thehigh-availability hub. Even though the high-availability hub does not use the SNA protocol, you canset SNA as one of the communication protocols for the remote monitoring server reporting to thehigh-availability hub, if you need this protocol for any monitoring agents that will report to theremote monitoring server. For more information about the communication protocols, see "Decision5: How to set up communications between components" in the IBM Tivoli OMEGAMON XE andIBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.

KDS_TEMS_TCP_HOST parameterThis is the TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where theremote monitoring server is installed.

KDS_HUB_TCP_HOST parameterThe value must be the application-instance-specific (private) dynamic virtual IP address of thehigh-availability hub.

KDS_HUB_TCP_pipe_type_PORT_NUMThe value must be the port number of the hub for each protocol selected.

KDS_TEMS_TCP_KDEB_INTERFACELIST parameterTo avoid network interface conflicts, you must specify one of the following values for a remotemonitoring server reporting to the high-availability hub in the same sysplex:

v !* to force the remote monitoring server to use only the interface associated with the defaulthost name for the z/OS image.

v -dvipa_hostname to use any interface except the one associated with dvipa_hostname.

KDS_TEMS_VIRTUAL_IP_ADDRESS parameterThe value must be D (for DVIPA).


Step 3. Configure monitoring agents to report to the remotemonitoring serverIn the same configuration profile, set parameter values for each of the products you want to include in theruntime environment of the remote monitoring server. Follow the instructions in each product's Planningand Configuration Guide, and use the information in each product's Parameter Reference.



Step 4. (Optional) Replicate the remote runtime environmentNow you can replicate to other z/OS systems the configured runtime environment that contains the remotemonitoring server and its monitoring agents. Replicating the configured runtime environment is an easyway to ensure that all your remote monitoring servers are configured to report to the high-availability hub.Follow the instructions in the "Using the PARMGEN method to replicate a configured environment" chapterof the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide.

Configuration Tool (ICAT) methodBe sure to complete Steps 1, 2, and 3 in the "Configuring products with the Configuration Tool" chapter ofthe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide before you begin the configuration steps in this section.

Complete the following steps in order:

__ “Step 1. Add a runtime environment”

__ “Step 2. Build the runtime libraries” on page 39

__ “Step 3. Configure the high-availability hub monitoring server” on page 39

__ “Step 4. Configure a remote monitoring server to report to the high-availability hub” on page 64

__ “Step 5. Configure monitoring agents to report to the remote monitoring server” on page 76

__ “Step 6. Load the runtime libraries” on page 77

Step 1. Add a runtime environmentComplete these steps to define a runtime environment for the high-availability hub.

1. If the Configuration Tool is not already running, start it:EX 'shilev.INSTLIB'

The Configuration Tool Main Menu is displayed, as shown in Figure 3 on page 33.


2. From the Configuration Tool Main Menu, enter 3 (Configure products).

The Configure Products panel is displayed, as shown in Figure 4.

3. On the Configure Products panel, enter 1 (Select product to configure).

The Product Selection Menu (Figure 5) lists the products available for configuration.

4. Enter S (Select) to the left of IBM Tivoli Management Services on z/OS V6.2.3.

KCIPRIM -------------------------- MAIN MENU ----------------------------------

Enter the number to select an option:

1 Set up work environment

2 Install products (Optional: for file-tailored SMP/E jobs)

3 Configure products

I Installation information <=== RevisedS Services and utilities

Installation and Configuration Assistance Tool Version 310.22© Copyright IBM Corp. 1992-2012

Licensed Material - Program Property of IBM

F1=Help F3=Back

Figure 3. Configuration Tool Main Menu

KCIPRCM ---------------------- CONFIGURE PRODUCTS ------------------------------OPTION ===>

Enter the number to select an option:

1 Select product to configure

I Configuration informationS Services and utilities

F1=Help F3=Back

Figure 4. Configure Products panel

KCIPPLST ------------------- PRODUCT SELECTION MENU ---------------------------COMMAND ===>

Actions: S Select product

__ monitoring_agent_1_Vn.n.n__ monitoring_agent_2_Vn.n.n__ monitoring_agent_3_Vn.n.n__ IBM Tivoli Management Services on z/OS V6.2.3__ monitoring_agent_4_Vn.n.n__ monitoring_agent_5_Vn.n.n

Figure 5. Product Selection Menu


ImportantThe high-availability hub must be configured in its own runtime environment, without anymonitoring agents. Therefore, be sure to select IBM Tivoli Management Services on z/OSV6.2.3 rather than selecting one of the monitoring agents.

The Runtime Environments (RTEs) panel (Figure 6) is displayed.

5. On the Runtime Environments (RTEs) panel, type A (Add RTE) in the Action field beside the firstempty row, and type a name for the runtime environment in the Name field.

The runtime environment name is a unique identifier of up to 8 characters. It is the default mid-levelqualifier of the runtime libraries.

6. Specify the type of runtime environment being created. In this example, a Full runtime environment iscreated for the high-availability hub.

For more detailed information about the available types of runtime environments, see "What types ofruntime environments to set up" in the "Planning your deployment" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide.

7. Type a description for this runtime environment. The description can be any information that is usefulfor you and others at your site.

8. When you have specified all required values on the Runtime Environments (RTEs) panel, pressEnter.

The Add Runtime Environment (1 of 3) panel is displayed, as shown in Figure 7 on page 35.

KCIPRTE ----------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------COMMAND ===>

*** Current product entry selected: ***product_name Vn.n.n

Actions: A Add RTE, B Build libraries, C Configure,L Load all product libraries after SMP/E,D Delete, U Update, V View values, Z UtilitiesR README Table of Contents

Action Name Type Sharing Description

A HAHUB FULL Runtime environment for high-availability hub-------------------------------------------------------------------------------

Enter=Next F1=Help F3=Back F7=Up F8=Down

Figure 6. Runtime Environments (RTEs) panel


The values on the Add Runtime Environment panels are used to allocate runtime libraries and provideconfiguration defaults.

9. Use the following information to complete the first Add Runtime Environment panel.

High-level qualifierSpecify the high-level qualifiers to be used for allocating the runtime libraries. These entriesare required.

SMS considerationsIf you plan to allocate SMS-managed data sets for the runtime environment, ensure thatthe following are all true:

v SMS is active on the z/OS image.

v The high-level qualifier that you specify is eligible for SMS-managed volumes.

v You specify a combination of VOLSER, UNIT, STORCLAS, and MGMTCLASparameters that is valid at your site. Because SMS can be implemented in severaldifferent ways, the Configuration Tool does not attempt to validate these parameters.The data set allocation jobs use the values you enter.

Volser Specify the volume serial numbers to be used for allocating the runtime data sets. This valueis required if the runtime data sets are not managed by SMS.

Unit Specify the unit name to be used for allocating the non-VSAM runtime data sets. This valueis required if the runtime data sets are not managed by SMS.

StorclasIf the runtime data sets are to be managed by SMS, specify the SMS storage class to beused for the allocation. If your site does not require the SMS STORCLAS parameter, you canleave this field blank.

MgmtclasIf the runtime data sets are to be managed by SMS, specify the SMS management class tobe used for the allocation. If your site does not require the SMS MGMTCLAS parameter, youcan leave this field blank.

PDSE If the non-VSAM data sets are to be managed by SMS, you can specify Y to allocate PDSE

KCIPRTEA -------------- ADD RUNTIME ENVIRONMENT (1 of 3) ----------------------COMMAND ===>

RTE: HAHUB Type: FULL Desc: Runtime environment for high-availability hub

Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSENon-VSAM rhilev volser unit NVSAM rvhilev volserMid-level qualifier ==> HAHUB

JCL suffix ==> ssss Remote RTE for transport ==> N (Y, N)STC prefix ==> HAHB Runtime members analysis ==> Y (Y, N)SYSOUT class ==> X Diagnostic SYSOUT class ==> XLoad optimization ==> N (Y, N)

Will this RTE have a Tivoli Enterprise Monitoring Server ==> Y (Y, N)If Y, TEMS name ==> HAHUB:CMS (Case sensitive)

Copy configuration values from RTE ==> (Optional)

Enter=Next F1=Help F3=Back

Figure 7. Add Runtime Environment (1 of 3) panel


data sets instead of PDS data sets. PDSE data sets do not require compression and are notlimited by a predefined number of directory entries.

The default is N. Even if you specify Y, most load module libraries are not allocated as PDSEdata sets. The main exception is a load library used for the SMP/E CALLLIBS facility.

Mid-level qualifierSpecify a mid-level qualifier for runtime libraries, or accept the default (the runtimeenvironment name).

JCL suffixSpecify a unique JCL suffix, no more than 4 characters long, to identify the batch jobmembers created in &shilev.INSTJOBS by the Configuration Tool for this runtimeenvironment. Check the INSTJOBS data set to ensure that the suffix is not already in use.

STC prefixSpecify a unique prefix to be used when generating started task procedures for this runtimeenvironment. For the high-availability hub, do not accept the default value of CANS. Specifyyour own unique prefix.

SYSOUT classSpecify the value of the SYSOUT class for non-diagnostic output DDNAMEs, such asRKPDLOG, in generated JCL. This replaces the previously hardcoded SYSOUT class value.

Load optimizationSpecify whether you want to optimize the loading of this runtime environment, when theruntime environment load action (L) is selected after maintenance is applied or products arereconfigured.

If you specify Y, the load job has the following characteristics:v Copies only modified modules from target to runtime libraries.v Requires access to IBM's SuperC (ISRSUPC) utility.v Uses less DASD space.v Performs additional analysis, which uses more CPU processing and file I/O.

If you specify N (the default), the load job has the following characteristics:v Copies all members from target to runtime libraries, whether or not they were modified.v Requires more DASD space.v Uses less CPU time.

Tip: Even if you enable load optimization, the first load operation copies all members to theruntime data sets. Load optimization takes effect on the second and subsequent loadoperations.

Remote RTE for transportAccept the default value of N in this field.

Runtime members analysisThe Configuration Tool generates configuration batch jobs for the runtime environment andcan identify user-modified data set members that each batch job will affect. If runtimemembers analysis is enabled, a report of user-modified members is displayed. You can alsogenerate these reports from the RTE Utility Menu (action Z, option "Analyze user modifiedelements").

The default is Y.

Diagnostic SYSOUT classSpecify the value of the SYSOUT class for diagnostic output DDNAMEs, such asSYSUDUMP and SYSABEND, in generated JCL. This replaces the previously hardcodedSYSOUT class value. The default is X.


Will this RTE have a Tivoli Enterprise Monitoring Server?Specify Y (the default) to allocate libraries for the monitoring server.

Be sure to make a note of the TEMS name value displayed here. You will have to specify itlater, when you configure the other components. The TEMS name parameter iscase-sensitive on all platforms.

Copy configuration values from RTELeave this field blank. Configuration values for the high-availability hub cannot be copied fromanother runtime environment.

10. After you have specified all required values on the first Add Runtime Environment panel, press Enter.

The second Add Runtime Environment panel is displayed, as shown in Figure 8.

The "Global SAF class name" in this panel provides security for the OMEGAMON enhanced 3270user interface.

11. Use the following information to complete the second Add Runtime Environment panel.

Use z/OS system variables?Leave the default of N in this field. A runtime environment for a high-availability hub cannotuse system variables, because the hub is not defined to run on any specific system, and itretains the same parameter values on any system in the sysplex.

Security systemSpecify what, if any, security system is to be used for this runtime environment. The default isNONE. If you specify a security system, verify that it is installed and configured correctly foryour site. If you specify ACF2, you must also provide the name of the ACF2 macro library.

Tip: Specifying a security system here indicates which system will be used for securityvalidation of users signing on to the Tivoli Enterprise Portal, but it does not enable thevalidation. Security validation of users is enabled in a Tivoli Enterprise Monitoring Serverconfiguration panel. For more information about configuring security, see Chapter 8,“Configuring security on a monitoring server on z/OS,” on page 143.

Global SAF class nameSpecify a common System Authorization Facility (SAF) security class name for OMEGAMONenhanced 3270 user interface security controls. The value is used in theRTE_SECURITY_CLASS parameter in the KppENV member of the RKANPARU library. If this

KCIPRTA1 ----------- ADD RUNTIME ENVIRONMENT (2 of 3) -------------------------COMMAND ===>

Use z/OS system variables? ==> N (Y, N) Use VTAM model applids? ==> N (Y, N)RTE name specification ==> &SYSNAMERTE base alias specification ==> n/aApplid prefix specification ==> K&SYSCLONE.

Security system ==> NONE (RACF, ACF2, TSS, NAM, None)ACF2 macro library ==>Fold password to upper case ==> Y (Y, N)Global SAF class name ==> (ACF2 max is 3 chars.)

VTAM values are required under certain conditions. Press F1=Help:Applid prefix ==> CTD Network ID ==>Logmode table ==> KDSMTAB1 LU6.2 logmode ==> CANCTDCS

If you require TCP/IP communications for this RTE, complete these values:Hostname ==>

Started task ==> (Recommended default = *)Port number ==>




field is not specified, the RTE_SECURITY_CLASS parameter is generated as a placeholdercomment in the RKANPARU(KppENV) member of components exploiting the parameter.Specify a valid SAF class name if you want to specify a value. If you are using ACF2 as yourexternal security resource manager, specify a maximum of three characters.

Fold password to upper caseBy default, TMS:Engine folds logon passwords to uppercase. However, RACF V1.7 andhigher supports mixed-case passwords. If you want to implement mixed-case passwords andif all your monitoring agents support them (this requires application of maintenance for eachmonitoring agent), set this field to N.

If any of your monitoring agents do not support mixed-case passwords, do not activate theSETROPTS PASSWORD(MIXEDCASE) option in RACF and do not enable mixed-casepasswords in your runtime environments. Leave this field with the default value Y.

For more information about the MIXEDCASE option in RACF, refer to the z/OS SecurityServer RACF Security Administrator's Guide. For more information about the wayTMS:Engine handles security, enter README SEC at the command line of any ConfigurationTool panel.

VTAM® communication valuesThe high-availability hub does not use VTAM for communication. Clear all the input fields inthis section.

Applid prefixClear this field.

Network IDClear this field.

Logmode tableClear this field.

LU6.2 logmodeClear this field.

TCP/IP communication valuesThe values you specify here become the default TCP/IP values for the monitoring server.

HostnameFor the runtime environment of the high-availability hub, specify as the host name theapplication-instance-specific (private) DVIPA name you have defined to DNS. In theexample shown, the host name is the private DVIPA name OMEGAHUB.

The host name for the runtime environment of the high-availability hub is a virtualsystem name, because the hub can run on any LPAR in the sysplex.

Started taskIdentifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack,accept the default value of an asterisk (*), which uses the first TCP/IP stack that wasstarted.

If the LPAR contains more than one TCP/IP stack, specify the started task name ofthe TCP/IP stack you want to use. Alternatively, you can specify the number sign (#),which is translated to a blank and allows the TCP/IP environment to choose the stackto use, either through TCP/IP definitions or through the use of the SYSTCPD DDstatement.

Tip: Whichever method is used to select a TCP/IP stack in a multi-stackenvironment, the Tivoli Management Services components continue to use that stack,even if a different stack becomes the primary stack. Therefore, in a multi-stack


environment, it is best to specify the started task name of the TCP/IP stack to beused, rather than specifying a wildcard or a blank.

If IP domain name resolution is not fully configured on the z/OS system, theSYSTCPD DD statement is required (see “(If applicable) Add support for theSYSTCPD DDNAME in the monitoring server started task” on page 119).

Port numberThe number of the well-known port to be used for communications with thehigh-availability hub. The default is 1918. (For detailed information about port numberassignments, see the IBM Tivoli OMEGAMON XE and IBM Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide.)

12. After you have specified all required values on the second Add Runtime Environment panel, pressEnter.

A third Add Runtime Environment panel is displayed, as shown in Figure 9.

13. Leave the third Add Runtime Environment panel blank. This panel does not apply to the runtimeenvironment of the high-availability hub.

14. Press Enter to return to the Runtime Environments (RTEs) panel (Figure 6 on page 34).

Tip: Enter V (View values) to verify the runtime environment information and U (Update) to make anynecessary changes.

This completes the addition of the runtime environment. You must build the runtime libraries beforecontinuing to configure the high-availability hub. Go on to “Step 2. Build the runtime libraries.”

Step 2. Build the runtime librariesThis step generates a batch job to allocate the required runtime libraries.

1. On the Runtime Environments (RTEs) panel, type B to the left of the name of the runtime environment,and press Enter.

The JCL to allocate the runtime libraries is displayed.

2. Review the JCL, edit if necessary, and submit the DS#1ssss job.

3. Verify that the job completes successfully.

Expect to receive a return code of zero. If you do not, check the log to diagnose errors, and then rerunthe job.

4. Press F3 (Back) to return to the Runtime Environments (RTEs) panel.

Step 3. Configure the high-availability hub monitoring serverTo configure the high-availability hub, perform the following tasks in order:

1. “Begin the configuration” on page 40.

2. “Specify configuration values” on page 40.

KCIPRTA2 -------------- ADD RUNTIME ENVIRONMENT (3 of 3) ----------------------

If you require TN3270E Telnet session link support override, complete thesevalues:

Hostname ==>Port number ==>LUGROUP ==>




3. “Specify communication protocols” on page 51.

4. “(Optional) Enable the self-describing agent capability” on page 58

5. “Create the runtime members” on page 61.

6. “Configure the persistent datastore” on page 61.

7. “Prepare to complete the configuration of the persistent datastore and monitoring server” on page 63

8. “Load the runtime libraries” on page 63.

Begin the configurationPerform the following steps to begin the configuration:

1. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), enter C (Configure) next to thename of the runtime environment you created for the high-availability hub.

The Configure the TEMS panel (Figure 10) is displayed.

Tips

v The high-availability hub does not use the SNA communication protocol, so you can skip option 1(Create LU6.2 logmode) on the Configure the TEMS panel.

v Select option I (Configuration information: What's New) to read about updates to monitoring serverconfiguration options since the previous versions.

Specify configuration valuesIn this step you indicate that the monitoring server you are configuring is a high-availability hub. You alsospecify the name of the started task for this monitoring server and whether security validation is in forcefor the server. You also use this option to activate and set control parameters for the auditing function.

Do not enable security validation at this point. Security can be set up more effectively after you completeand verify the configuration.

KDS62MCU ----------- CONFIGURE THE TEMS / RTE: rte -----------------------

Each RTE can contain only one TEMS. To configureLast selected the TEMS for this RTE, perform these

steps in order: Date TimeI Configuration

information (What’s New)

1 Create LU6.2 logmode11/03/10 05:06 2 Specify configuration values

11/08/03 17:36 3 Specify communication protocols11/08/04 22:31 4 Configure TEMS Self-Describing

Agent parameters 11/08/04 05:33 5 Create runtime members11/07/04 08:37 6 Configure

persistent datastore 11/03/10 05:067 Complete the configuration 11/05/2416:52

Optional:

8 View TEMSlist and registration status9 Generate sample migration JCL 11/03/1005:06

F1=Help F3=Back

OPTION ===>

Figure 10. Configure the TEMS panel


1. From the Configure the TEMS panel (Figure 10 on page 40), enter 2 to display the SpecifyConfiguration Values panel (Figure 11).

2. For the high-availability hub, the following values are required:Started task ==> unique_nameType (Hub or Remote) ==> HUBHub TEMS type ==> HA (HA=High Availability)

For the other fields, accept the default values or provide the values appropriate for your site.

Started taskThe name of the high-availability hub started task JCL procedure. Make a note of the name,because later you will have to copy this started task procedure to your system procedurelibrary. The default started task name for a monitoring server is ccccDSST, where cccc is the4-character STC prefix specified when you defined the runtime environment. You can edit thestarted task name displayed on this panel, but make sure the name you specify is unique.

Type (Hub or Remote)Specify HUB as the monitoring server type.

Hub TEMS typeSpecify HA to configure a high-availability hub.

Security settings

Validate security?This setting determines whether the hub monitoring server validates the user IDs andpasswords of users signing on to the Tivoli Enterprise Portal. Leave the value N fornow. If you set security validation to Y at this point, you will have difficulty completingthe configuration steps and verifying the configuration. You can return to this panel andset security validation to Y later, after you set up security for the monitoring server (seeChapter 8, “Configuring security on a monitoring server on z/OS,” on page 143). When

KDS62PP1 ---------------- SPECIFY CONFIGURATION VALUES ------------------------

Started task ==> HAHBDSSTType (Hub or Remote)

==> HUB Hub TEMStype ==> HA (HA=High Availability)

Security settings:Validate

security? ==> N (Y, N)

TMS password encryption information:Integrated Cryptographic Service

Facility (ICSF) installed? ==> N (Y, N) ICSF load library==>

CSF.SCSFMOD0TMS encryption key

==> IBMTivoliMonitoringEncryptionKey

Program to Program Interface (PPI) information:Forward Take Action commands to NetView for z/OS?

==> N (Y, N) NetView PPI receiver ==> CNMPCMDRTEMS PPI sender

==> Enter=NextF1=Help F3=Back F5=Advanced

COMMAND ===>

Figure 11. Specify Configuration Values panel


security validation is enabled on this panel, validation of users is handled by thesecurity system specified for the runtime environment.

Integrated Cryptographic Service Facility (ICSF) installed?If the IBM Integrated Cryptographic Service Facility (ICSF) is installed and configuredon the z/OS system, set the value to Y. If you specify that ICSF is not installed on thisz/OS system (N), then the monitoring server uses an alternative, less secure encryptionscheme.

Note: The encryption method specified for the monitoring server and the TivoliEnterprise Portal Server must match. If you specify that ICSF is not installed on thisz/OS system (N), you must add the line USE_EGG1_FLAG=1 (or USE_EGG1_FLAG=Y) to theKFWENV environment file of the Tivoli Enterprise Portal Server (see “(If applicable)Edit the portal server environment file” on page 123).

ICSF load libraryIf ICSF is installed and configured on the z/OS system, specify the ICSF load librarythat contains the CSNB* modules used for password encryption. CSF.SCSFMOD0 is thedefault.

If ICSF is not installed on the system, clear the field.

TMS encryption keySpecify a unique, 32-byte password encryption key. The value is case-sensitive. Besure to record the value you use for the key. You must use the same key during theinstallation of any components that communicate with this monitoring server, such asthe Tivoli Enterprise Portal Server or a remote monitoring server.



Encryption key tips

v The ampersand (&) character cannot be part of the encryption key.

v The DS#3ssss job (where ssss is the JCL suffix for the runtime environment)creates the runtime members after you complete the monitoring serverconfiguration panels. This job uses the value you specify for the encryption keyto create the key file. The key file is member KAES256 in the&rhilev.&rte.RKANPARU library (see “Create the runtime members” on page61).

v For security reasons, the encryption key value is not displayed if you return tothe Specify Configuration Values panel after you finish configuring themonitoring server. If you reconfigure the monitoring server by changing otherparameter values on the configuration panels, the resulting DS#3ssss job doesnot create a new key file.

If you must change the encryption key value after initial configuration, type thePWD command on the command line of the Specify Configuration Values panel,and then answer Y to the prompt "Do you want to disable ICSF encryption orreset the key?". You can then re-enable encryption and specify a different key.After doing so, you must recreate the runtime members (“Create the runtimemembers” on page 61) and reload the runtime libraries (“Step 3. Load theruntime libraries” on page 98).

v In batch mode, the encryption key value is stored in parameterKDS_CMS_SEC_ENC_KEY. For batch mode processing, the encryption key isdisplayed in plain text so that it can be used as input for the KAES256 file inthe &rhilev.&rte.RKANPARU library of other runtime environments. Therefore,ensure that the &shilev.INSTJOBS library for this runtime environment issecured before you create a batch parameter member containing its values.

The value of the encryption key batch parameter (KDS_CMS_SEC_ENC_KEY)is enclosed in double quotation marks in the batch parameter member. If youmust use a single quotation mark or apostrophe (') as part of the key value,edit the batch parameter member to enclose the 32-byte encryption key stringin two sets of double quotation marks (for example, ""key’s_value""). If youmust use both single and double quotation marks as part of the key value, usethe interactive mode of the Configuration Tool instead of the batch mode.

Program to Program Interface (PPI) information(Optional) Specify the PPI values that enable forwarding of Take Action commands toNetView® for z/OS for authorization and execution. If you enable forwarding, you must alsoenable NetView to receive and authorize the commands (see “Enable NetView to authorizeTake Action commands” on page 152).

Forward Take Action commands to NetView for z/OSSpecify Y if you want the Tivoli Enterprise Monitoring Server to forward z/OS consolecommands issued as Take Action commands to NetView for authorization andexecution. The default value is N.

NetView PPI receiverSpecify the name of the PPI receiver on NetView that will receive Take Actioncommands. This name must match the receiver name specified on the NetViewAPSERV command. The default name is CNMPCMDR. The Configuration Tool generatesthe KGLHC_PPI_RECEIVER environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library.

The value must be a 1- through 8-character unique identifier for the receiver program.It can contain alphabetic characters A-Z and a-z, numeric characters 0-9, and the


following special characters: dollar sign ($), percent sign (%), ampersand (&), at sign(@), and number sign (#). This value must match the value specified in the NetViewDSIPARM initialization member, CNMSTYLE (see “Enable NetView to authorize TakeAction commands” on page 152).

If a value is specified for this parameter and either the specified name is incorrect orthe receiver is not active on NetView for z/OS, the command fails. If no value isspecified, default command routing to the z/OS console is performed.

This parameter is required if you answered Y in the Forward Take Action commandsto NetView for z/OS field.

TEMS PPI senderOptionally, specify the name of the PPI sender. The value must be a 1- through8-character, unique identifier for the receiver program. It can contain alphabeticcharacters A-Z and a-z, numeric characters 0-9, and the following special characters:dollar sign ($), percent sign (%), ampersand (&), at sign (@), and number sign (#).This name must not conflict with any NetView for z/OS domain name, as it is used inlogging the command and command response in the NetView log. If a value isspecified on this field, the Configuration Tool generates the KGLHC_PPI_SENDERenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library.

If you do not specify a value in this field, the default is the job name of the monitoringserver that is the source of the command.

3. When you have completed the Specify Configuration Values panel, press Enter

The Eligible Products for HA Hub TEMS panel is displayed (Figure 12).

This panel lists the products that can be configured to report to a high-availability hub, either indirectly(through a remote monitoring server) or directly. The products are listed in alphabetical order ofproduct name; the 2-character product codes (pp) are also shown for your convenience.

Tip: Not all monitoring agents are eligible for configuration with a high-availability hub. The list islimited to those that are eligible.

4. On the Eligible Products for HA Hub TEMS panel, type an X beside the names of all products you wantto exclude from reporting to the high-availability hub. (In the example shown in Figure 12, products 1and 4 are excluded from reporting to the high-availability hub.) Use the F7 (Up) and F8 (Down) keys toscroll through the list.

5. When you finish excluding products, press Enter.

The Exclusion Verification for HA Hub TEMS panel is displayed (Figure 13 on page 45).

KDSPHUBH ------------ Eligible Products for HA Hub TEMS -------- Row 1 from 25

Exclude products that will not participate in the High Availability (HA)Hub TEMS configuration.

Action: X Exclude product

PP Component name-- -------------------------------------------------------------------

X pp product_1_ pp product_2_ pp product_3X pp product_4

Figure 12. Eligible Products for HA Hub TEMS panel


This panel lists all the products you selected for exclusion. If you did not select any products forexclusion, the list is blank. Review the list, and press Enter to accept it, or F3 (Back) to go back to theEligible Products for HA Hub TEMS panel and change your selections.

When you press Enter to accept the list, you return to the Configure the TEMS panel (Figure 10 onpage 40).

6. From the Configure the TEMS panel, select 2 (Specify configuration values) to display the SpecifyConfiguration Values panel, and then press F5 (Advanced) to display the Specify AdvancedConfiguration Values panel (Figure 14).

Accept the default values or provide the values appropriate for your site.

Enable Web Services SOAP ServerAccept the default value of Y. The SOAP server must be enabled for a hub monitoring server.See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide for more information.

Enable Tivoli Event Integration Facility (EIF)Specify Y if you want to enable event forwarding on this hub. The default value is N. If youspecify Y, the KMS_OMTEC_INTEGRATION=YES environment variable is generated in theKDSENV member of &rhilev.&rte.RKANPARU.

KDSPHUBV --------- Exclusion Verification for HA Hub TEMS ------ Row 1 from 25

Exclude verification list.

Press Enter to accept, End or Cancel to redo the exclude list.

PP Component name-- -------------------------------------------------------------------pp product_1pp product_4

Figure 13. Exclusion Verification for HA Hub TEMS panel

KDS62PP3 ----------- SPECIFY ADVANCED CONFIGURATION VALUES --------------------

Enable Web Services SOAP Server==> Y (Y, N) Enable Tivoli Event IntegrationFacility (EIF) ==> N (Y, N) Enable startup consolemessages ==> Y (Y, N) Enable communicationstrace ==> N (Y, N, D, M, A) Reconnectafter TCP/IP recycle ==> N (Y, N)

Enable storage detail logging ==> Y (Y, N)Storage detail logging: Hours ==> 0 (0-24)

Minutes ==> 60 (0-60) Flush VSAM buffers: Hours==> 0 (0-24) Minutes ==> 30 (0-60) Virtual IP Address(VIPA) type ==> N (S=Static, D=Dynamic, N=None) Minimumextended storage ==> 768000 K

Maximum storage request size ==> 16 (Primary) ==> 30 (Extended)Language locale ==> 1 (Press F1=Help

for a list of codes)z/OS Audit collection values:

Enable/Disablez/OS audit collection ==> (M, B, D, X)Maximum in-memory cache entries ==> (10-1000)

Domain ==>

Enter=NextF1=Help F3=Back F5=Advanced F6=PDS F10=CMS List

COMMAND ===>

Figure 14. Specify Advanced Configuration Values panel


See “Decision 2: Whether and how to enable event forwarding” on page 22 for moreinformation about event forwarding.

Enable startup console messagesAccept the default value of Y if you want a SYSLOG message on the console to indicate whenthe monitoring server finishes initializing. You can use this message as an UP status messagein your automation package (for example, Tivoli System Automation for z/OS). See thedocumentation for your automation package for instructions on capturing the monitoring serverautomation message IDs (KO4SRV032 and KDSMA001).

If the value of this field is Y, the KGL_WTO=YES parameter is added to the KDSENV memberof the &rhilev.&rte.RKANPARU data set.

Enable communications traceSet this parameter to Y if you want KDC_DEBUG=Y as the override setting in the&rhilev.&rte.RKANPARU(KDSENV) member. Otherwise, the default setting of KDC_DEBUG=Ninstructs the data communications layer to summarize communications problems. The defaultsetting is intended for stable applications in production.

Tip: The setting KDC_DEBUG=Y causes a great many records to be written to the log files. Usethis setting only for testing or problem diagnosis.

The default setting (KDC_DEBUG=N) generates standard RAS1 trace data in the monitoring serverRKLVLOG, in addition to the summary information diagnosing possible timeout conditions. Thefollowing settings report on data communications problems:

KDC_DEBUG=NMinimal tracing (the default).

KDC_DEBUG=YFull-packet tracing.

KDC_DEBUG=DKDC_DEBUG=Y, plus state and flow tracing.

KDC_DEBUG=MKDC_DEBUG=D, plus input and output help tracing.

KDC_DEBUG=AKDC_DEBUG=M, plus all-format tracing.

Do not set KDC_DEBUG=A unless directed by IBM Software Support personnel.

Reconnect after TCP/IP recycleIf you specify Y, the monitoring server address space reconnects to its TCP/IP stack withoutbeing recycled after the stack is recycled. When this parameter is set to Y, theTOLERATERECYCLE keyword is added in the KLXINTCP member of the &rhilev.&rte.RKANPARUlibrary.

If this parameter is set to N (the default), then if the TCP/IP stack used by the monitoringserver is recycled, the monitoring server address space must also be recycled to re-establishTCP/IP connectivity.

Enable storage detail loggingAccept the default value of Y if you want to enable storage allocation detail logging. You canuse the storage detail command output to analyze storage allocated by the monitoring serveraddress space. Specifying Y generates the second EVERY command in &rhilev.&rte.RKANCMDU(KDSSTART).

To disable storage detail logging, set this parameter to N. The second EVERY command isthen written as a comment in &rhilev.&rte.RKANCMDU(KDSSTART).


Tip: If you disable storage logging on this panel and then want to activate it after themonitoring server is configured and running, you can issue the following modify command tothe monitoring server started task:/F started_task,EVERY hh:mm:ss STORAGE D

Issuing this modify command activates storage detail logging without a requirement to recyclethe monitoring server.

If you are enabling storage detail logging on the Specify Advanced Configuration Values panel,accept the default values or set your own values for two time intervals:

Storage detail loggingSpecify how often you want storage allocation detail to be logged. This interval value iswritten as part of the second EVERY command in &rhilev.&rte.RKANCMDU(KDSSTART). The default is 60 minutes.

Flush VSAM buffersSpecify how often you want to force all deferred VSAM writes to DASD. This intervalvalue is written as part of the third EVERY command in &rhilev.&rte.RKANCMDU(KDSSTART). The default is 30 minutes.

Virtual IP Address (VIPA) typeSpecify D (Dynamic VIPA, or DVIPA). The VIPA name (the application instance specificdynamic virtual IP address) of the monitoring server must be resolvable through DNS. DVIPArequires one of the following communication protocols: IP.PIPE, IP.SPIPE, IP6.PIPE, orIP6.SPIPE. For more information about specifying communication protocols, see “Specifycommunication protocols” on page 51.

Minimum extended storageSpecify the minimum amount of virtual storage to be made available to the monitoring agentsand other components that are communicating with this monitoring server. The default value is768000. If you do not have many IBM components reporting to the server and you want toconserve storage, you can lower the value.

This value is used for the MINIMUM parameter in the KDSSYSIN member of&rhilev.&rte.RKANPARU. This example shows the default value:MINIMUM(768000,X)

Maximum storage request sizeSpecify the maximum TMS:Engine storage request size, as a power of 2, for primary storageand for extended storage. The maximum value you specify for each type of storage request(primary and extended) can be no higher than 25 (32768 KB).

The default maximum for extended storage is 30 (8192 KB). The default maximum for primarystorage is 16 (64 KB). However, some monitoring agents configured to run in the monitoringserver address space require a maximum primary storage request size of 20 (1 MB).

If a program requests a block of storage larger than the maximum value set, an abend occurs.The maximum value is used in building storage access tables to speed memory allocation. Toosmall a value causes TMS:Engine components to fail. Too large a value wastes storage andincreases processing overhead. You might have to specify a larger value if any of yourmonitoring agents builds large VTAM request/response units (RUs) and data streams.

This value is used for the LIMIT parameter in the KDSSYSIN member of &rhilev.&rte.RKANPARU. This example shows the default values:LIMIT(23,X)LIMIT(16,P)

Language localeThis parameter is required. The default value is 1 (English - United States).


Press F1 (Help) and select Language locale for a list of the possible values. Specify thenumeric value that represents the language and region for the z/OS system.

The Configuration Tool uses this value to set the country and character set for the LANGenvironment variable in &rhilev.&rte.RKANPARU(KDSENV). For example, if you accept thedefault value of 1 (English - United States), the Configuration Tool generates this environmentvariable in KDSENV:LANG=en_US.ibm-037

If the z/OS UNIX System Services (USS) codepage (en_US.ibm-1047) is required, you canspecify either en_US.ibm-1047 or 1A in the Language locale field. In batch mode, you canspecify either of these values:Kpp_CMS_ICU_LANG en_US.ibm-1047Kpp_CMS_ICU_LANG 1A

Tip: The USS codepage (en_US.ibm-1047) is required for agent autonomy and for privatesituation XML files.

z/OS Audit collection valuesThese parameters allow you to activate and set parameters that control the auditing facility(see “Whether to enable the auditing function” on page 17 for more information).

Enable/Disable z/OS audit collectionThis parameter specifies the audit detail level; set it to M, B, D, or X, as explained in“Environment variables that control the auditing function” on page 18. The value youspecify generates an AUDIT_TRACE parameter in member KDSENV of theRKANPARU library. If you do not specified a value for this parameter,AUDIT_TRACE=BASIC is set as the default.

Maximum in-memory cache entriesThis parameter defines the maximum number of auditing records kept in short-termmemory, from 10 to 1000; it generates an AUDIT_MAX_HIST parameter in memberKDSENV of the RKANPARU library. If you do not specify a value here,AUDIT_MAX_HIST=100 is set as the default.

DomainThis field specifies an identifier that your site can use to associate audit records. It issuitable for grouping agents that are associated with each other. One example mightbe for collecting records regarding a particular customer. This field is also used tocreate unique namespaces for role-based access control (RBAC). The value youspecify generates an ITM_DOMAIN parameter in KDSENV.

To specify advanced parameters for the Persistent Datastore, press F6 (PDS) to display the KDSPPDS(Specify Persistent Datastore Configuration Values) panel (see Figure 15). These fields define defaultparameters for the persistent datastore, the repository for short-term historical data. For detailedinformation, see IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide.

KDSPPDS ------ SPECIFY PERSISTENT DATASTORE CONFIGURATION VALUES --------------COMMAND ===>

Persistent datastore parameters:Maintenance procedure prefix

==> KPDPROC Datastore file high-levelprefix ==> rhilev.rte

Volume ==> Storclas ==>Unit ==> Mgmtclas

==> Enter=NextF1=Help F3=Back

Figure 15. Specify Persistent Datastore Configuration Values panel


Maintenance procedure prefixThis prefix is applied to the procedures that perform maintenance when the persistentdatastore is full. Specify the same prefix for all products in all runtime environments. Thedefault is KPDPROC.

This parameter is required even if you intend to configure historical data collection at thelocation of the monitoring agents rather than at the location of the monitoring server.

Datastore file high-level prefixSpecify the high-level qualifier to use when allocating persistent datastore files in this runtimeenvironment. The default is &rhilev.&rte.


VolumeSpecify the default DASD volume to use when allocating persistent datastore files in thisruntime environment. The default is the volume specified for the runtime environment.

Unit Specify the default DASD unit to use when allocating persistent datastore files in this runtimeenvironment. Valid unit types are 3380 and 3390. The default is the unit type specified for theruntime environment.

StorclasSpecify the default SMS storage class to use when allocating persistent datastore files in thisruntime environment. If your site does not require the SMS STORCLAS parameter, you canleave this field blank.

MgmtclasSpecify the default SMS management class to use when allocating persistent datastore files inthis runtime environment. If your site does not require the SMS MGMTCLAS parameter, youcan leave this field blank.

When you have defined all necessary Persistent Datastore parameters, press Enter.

Tip: Under the guidance of IBM Software Support, you can specify values for parameters other thanthose shown on the Specify Configuration Values and Specify Advanced Configuration Values panels.To do so, press F5 from the Specify Advanced Configuration Values panel to display the SpecifyNonstandard Parameters panel. On this panel you can add, replace, or delete parameter values in anymember of any runtime library. For details, press F1 on the Specify Nonstandard Parameters panel orsee IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planningand Configuration Guide.

7. If you specified Y for Enable Tivoli Event Integration Facility (EIF), the Specify Values for EventDestination panel (Figure 16 on page 50) is displayed when you press Enter on the Specify AdvancedConfiguration Values panel.


To configure event forwarding, provide values for the fields on the Specify Values for Event Destinationpanel:

Event server typeSpecify the type of event server: T (the default) for Tivoli Enterprise Console, or M forOMNIbus. This field corresponds to the EventListenerType parameter in the EIF configurationmember &rhilev.&rte.RKANPARU(KMSOMTEC).

Event server locationSpecify the fully qualified host name (the IPV4 dotted-decimal IP address) of the primary eventserver and of up to seven backup event servers. This field corresponds to the ServerLocationparameter in the KMSOMTEC member.

If you specify more than one event server, use commas to separate the host names or IPaddresses.Event server location ==> primary_server,backup_server1,backup_server2

If the EIF cannot send an event to the first server on the list, it tries the next one, and so on.

Event server portSpecify the port number on which the Tivoli Enterprise Console event server or OMNIbus EIFprobe listens for events. This field corresponds to the ServerPort parameter in theKMSOMTEC member. The default port number is 5529.

If you specify more than one event server, use commas to separate the port numbers. List theport numbers in an order corresponding to the list of event server locations.Event server port ==> primary_port,backup_port1,backup_port2

Buffer events maximum sizeSpecify the maximum size, in KB, of the adapter cache file. The cache file stores events ondisk when they cannot be sent to the event server. This field corresponds to theBufEvtMaxSize parameter in the KMSOMTEC member. The default value is 4096.

Disable Workflow Policy/Emitter Agent event forwardingIf you already have workflow policies containing emitter activities that send events to the TivoliEnterprise Console, turning on EIF event-forwarding causes duplicate events. If you specify Yin this field, you deactivate the emitter activities in your policies. The default value is N.

Policies give you more control over which events are sent, and you might want to keep somepolicies active. Moreover, policies that contain the Tivoli Enterprise Console emitter activitiesgenerally do little else. If you deactivate these activities, there is no point in running thepolicies. Therefore, you might want to delete the policies that are no longer required, instead ofdisabling them.

If this field is set to Y, the KMS_DISABLE_TEC_EMITTER=YES parameter is generated in theKDSENV member of &rhilev.&rte.RKANPARU.

KDSPEIF ------------- SPECIFY VALUES FOR EVENT DESTINATION ------------------

Specify the hostname and port number for the TEC event server orOMNIbus EIF probe to which you want to forward situation events:

Event server type ==> T (T=TEC, M=OMNIbus)Event server location ==>Event server port ==> 5529Buffer events maximum size ==> 4096 Kilobytes

For TEC event listener:Disable Workflow Policy/Emitter Agent event forwarding ==> N (Y, N)


Figure 16. Specify Values for Event Destination panel


8. Press Enter until you return to the Configure the TEMS panel (Figure 10 on page 40).

Specify communication protocolsTo specify protocols for communications between the high-availability hub and other components, completethe following procedure:

1. From the Configure the TEMS panel (Figure 10 on page 40), enter 3 to display the SpecifyCommunication Protocols panel (Figure 17).

This panel lists the communication protocols to be used by the monitoring server. The number besideeach protocol indicates its priority. When communication with another component is initiated, themonitoring server tries Protocol 1 first and goes to Protocol 2 and then to Protocol 3, and so on, incase of failure.

Tips

v The high-availability hub does not use the SNA protocol. Do not assign a number toSNA.PIPE.

v The high-availability hub requires at least one of the following communication protocols:IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE.

For more information about the communication protocols, see "Decision 5: How to set upcommunications between components" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

2. Supply the priority number for each protocol you want to select.IP.PIPE

Uses the TCP/IP protocol for underlying communications.IP.UDP

Also a TCP/IP protocol. Uses the packet-based, connectionless User Datagram Protocol (UDP).IP6.PIPE

IP.PIPE protocol that supports IPV6. This protocol is available for a monitoring server on a z/OSsystem at release level V1R7 or higher, with IPV6 installed and operational.

IP6.UDPIP.UDP protocol that supports IPV6. This protocol is available for a monitoring server on a z/OSsystem at release level V1R7 or higher, with IPV6 installed and operational.

IP.SPIPESecure IP.PIPE protocol. This protocol is available for a monitoring server on a z/OS system atrelease level V1R7 or higher.

KDS62PP3 -------------- SPECIFY COMMUNICATION PROTOCOLS -----------------------

Specify the communication protocols in priority sequence forTEMS HAHUB:CMS.

IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> 2 (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)SNA.PIPE ==> (Non-secure NCS RPC)

Note: SNA.PIPE is required under certain conditions. Press F1=Help.* Web Services SOAP Server is enabled: TCP protocol is required.* Event Integration Facility (EIF) is enabled: TCP protocol is required.


Figure 17. Specify Communication Protocols panel


IP6.SPIPESecure IP.PIPE for IPV6. This protocol is available for a monitoring server on a z/OS system atrelease level V1R7 or higher with IPV6 installed and operational.

SNA.PIPEThe high-availability hub does not use the SNA protocol. Do not assign a number to SNA.PIPE.

3. When you have selected protocols and assigned their priorities, press Enter.

The panel displayed next depends on the protocols and priorities you have specified.

v IP.PIPE, IP6.PIPE, IP.SPIPE, and IP6.SPIPE

Figure 18 shows the Specify IP.PIPE Communication Protocol panel, where you specify values forthe IP.PIPE, IP6.PIPE, IP.SPIPE, and IP6.SPIPE protocols.

Network address (Hostname)For the high-availability hub, the host name is the application-instance-specific (private)dynamic virtual IP address you have defined to DNS. In the example shown, the host nameis the private DVIPA name OMEGAHUB.

Started taskIdentifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack, acceptthe default value of an asterisk (*), which uses the first TCP/IP stack that was started.

If the LPAR contains more than one TCP/IP stack, specify the started task name of theTCP/IP stack you want to use. Alternatively, you can specify the number sign (#), which istranslated to a blank and allows the TCP/IP environment to choose the stack to use, eitherthrough TCP/IP definitions or through the use of the SYSTCPD DD statement.

Tip: Whichever method is used to select a TCP/IP stack in a multi-stack environment, theTivoli Management Services components continue to use that stack, even if a different stackbecomes the primary stack. Therefore, in a multi-stack environment, it is best to specify thestarted task name of the TCP/IP stack to be used, rather than specifying a wildcard or ablank.

If IP domain name resolution is not fully configured on the z/OS system, the SYSTCPD DDstatement is required (see “(If applicable) Add support for the SYSTCPD DDNAME in themonitoring server started task” on page 119).

Network interface listTo ensure that the high-availability hub is restricted to its private DVIPA address and cannot

KDS62PPD ----------- SPECIFY IP.PIPE COMMUNICATION PROTOCOL -------------------

Specify IP.PIPE and Web Services SOAP Server configuration.

* Network address (Hostname):==> OMEGAHUB

Started task ==> * (Recommended default = *)Network interface list: (If applicable)

==> !OMEGAHUB

Port number ==> 1918 (IP.PIPE)Port number ==> 1918 (IP.PIPE for IPV6)Port number ==> 3660 (Secure IP.PIPE)Port number ==> 3660 (Secure IP.PIPE for IPV6)HTTP server port number ==> 1920Access TEMS list via SOAP Server? ==> Y (Y, N)Address translation ==> N (Y, N)

Partition name ==>

* Note: See F1=Help for TSO HOMETEST command instructions.


Figure 18. Specify IP.PIPE Communication Protocol panel


interfere with the remote monitoring server configured on the same LPAR, thehigh-availability hub requires the use of a specific local TCP/IP interface. In this field, specify!dvipa_hostname, where dvipa_hostname is the private DVIPA name you specified in theNetwork address (Hostname) field. In the example shown, the value for Networkinterface list is !OMEGAHUB.

When you supply a value in the Network interface list field, the Configuration Toolgenerates the KDEB_INTERFACELIST environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library.

Important

– After you set the value of Network interface list to !dvipa_hostname for thehigh-availability hub, you must specify one of the following values for all otherproducts and components configured in all runtime environments on the sameLPAR, and for all remote monitoring servers configured to report to thehigh-availability hub in the same sysplex:

- !* to force the products and components to use only the interface associatedwith the default host name for the z/OS image.

- -dvipa_hostname to use any interface except the one associated withdvipa_hostname.

See "Network interfaces" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide formore information about interface lists.

– In the default character set (language locale en_US.ibm-037), the code for anexclamation point is x’5A’. If you are using a character set other than the default, adifferent character might map to that code. Use the character that maps to x’5A’ inyour character set. Set HEX ON in TSO Edit to confirm the correct character isentered.

Port numberSpecify the well-known port for the hub monitoring server, for each of the selected IP*.*PIPEprotocols. The port numbers specified here are stored in the KDE_TRANSPORTenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library. Thedefault port numbers are 1918 for nonsecure IP protocols and 3660 for secure IP protocols.If you specified a different TCP/IP port number for the runtime environment, the number youspecified is shown as the default for nonsecure IP protocols.

Make sure that the hub monitoring server well-known port is not already on the TCP/IPreserved port list. Also, the hub well-known port is the basis for an algorithm that assignsport numbers to the components configured to report to the hub. Make sure that thealgorithm will not result in attempts to reserve already-reserved ports for those components.See "Port number assignments" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

HTTP server port numberThe HTTP server port is used for communications with the SOAP server. Accept the defaultvalue of 1920. If Port 1920 is in use when the monitoring server is started, another port isassigned.

Access TEMS list via SOAP Server?Specify Y to create the initial KSHXHUBS member required for SOAP server operation. TheKSHXHUBS member is stored in the &rhilev.&rte.RKANPARU library.


The KSHXHUBS member contains the list of hub monitoring servers with which the SOAPserver communicates, and the corresponding user access list if access has been secured.The TEMS list in the KSHXHUBS member is an aliasing mechanism, equivalent to thekshxhubs.xml file on distributed platforms.

If the initial KSHXHUBS member has already been created and no changes are required tothe SOAP server values, set this field to N.

Address translationBy default, Ephemeral Pipe Support (EPS) is enabled to allow IP.PIPE connections to crossa network address-translating firewall. This feature obviates the requirement for a brokerpartition file (KDC_PARTITIONFILE=KDCPART). If you specifically want to disable EPS, specify Yfor Address translation. For more information, see "Implementation of firewall support" inthe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide.

Partition nameIf you specified Y for Address translation, you must supply the partition name (label) thatidentifies the location of the monitoring server relative to the firewall(s) used for addresstranslation.

The partition name that you supply is added to the partition table, which contains labels andassociated socket addresses provided by the firewall administrator. The label is usedoutside the firewall to establish monitoring server connections.

The well-known port for the hub monitoring server must be authorized by the firewalladministrator. For the IP*.*PIPE protocols, no additional ports require authorization.

When you press Enter after providing the IP*.*PIPE configuration values, you are presented withone of the following panels:

– If you specified Y for Address translation, the Specify IP.PIPE Partition References panel(Figure 19) is displayed.

The name of the monitoring server, its partition name (that is, its location or namespace relativeto the firewall), and its partition address (the IP address assigned to the monitoring server in thespecified partition) are displayed at the top of the Specify IP.PIPE Partition References panel.Use the fields of this panel to specify partition references (the values required to supportcommunication across a firewall using address translation rather than EPS). If more than onefirewall is used, specify a partition reference for each firewall.

PartitionSupply the partition name assigned to the monitoring server from a location on the otherside of the firewall.

KDS62PPE ------------ SPECIFY IP.PIPE PARTITION REFERENCES ------------------

TEMS name ==> rte:CMSPartition name ==> partition_namePartition address ==> partition_address

Specify IP.PIPE partition references to this TEMS.

To add a new entry, type the partition name in the first field and setthe address accordingly. To modify an entry, type over its values.Use D to delete a partition reference.

Action Partition Address__ ________________________________ ___________________

Enter=Next F1=Help F3=Back F7=Up F8=Down

Figure 19. Specify IP.PIPE Partition References panel


AddressSupply the IP address assigned to the monitoring server from a location on the otherside of the firewall.

To add a partition reference, specify the partition name and the address used in that partition tocommunicate with the monitoring server, and press Enter. To modify an existing partitionreference, type over an entry and press Enter. To delete a reference, type D in the Action fieldand press Enter. Modifications resulting in duplicate entries are ignored.

The values provided on this panel are saved as the KDC_PARTITIONFILE environment variablein the KDSENV member of the &rhilev.&rte.RKANPARU library. KDC_PARTITIONFILE points to amember, KDCPART, created in the &rhilev.&rte.RKANPARU library.

– If you specified N for Address translation, the Specify TEMS KSHXHUBS Values panel isdisplayed (Figure 20).

Use this panel to begin a list of hub monitoring servers to connect with the SOAP server. Thevalues you specified in earlier configuration panels are displayed as default values.

Hub TEMS SOAP Server values for RTEnameAccept the default value, which is the name of the runtime environment where themonitoring server is being configured.

TEMS nameAccept the default value, which is the TEMS name (CMS_NODEID) you specified whenyou defined the runtime environment.

TCP hostnameAccept the default, which is the host name specified on the Specify IP.PIPECommunication Protocol panel (Figure 18 on page 52).

TCP port numberAccept the default, which is the port number specified on the Specify IP.PIPECommunication Protocol panel (Figure 18 on page 52).

SNA network IDLeave this field blank. It is required only if SNA is Protocol 1.

SNA global location broker applidLeave this field blank. It is required only if SNA is Protocol 1.

SNA LU6.2 logmodeLeave this field blank. It is required only if SNA is Protocol 1.

KDS62PPG ------ SPECIFY TEMS KSHXHUBS VALUES / RTE: RTEname ------------------

Action: AddHub TEMS SOAP Server values for RTEname :TEMS name ==> RTEname:CMS (case sensitive)Protocol 1 ==> IPPIPE (IPPIPE,IP,IP6PIPE,IP6,IPSPIPE,IP6SPIPE,SNA)

TCP hostname ==> hostnameTCP port number ==> port_number

SNA network ID ==>SNA global location broker applid ==>SNA LU6.2 logmode ==>

Alias name ==> HAHUB:CMSNote: IBM recommends that the Alias name is the same as the TEMS name.


Figure 20. Specify TEMS KSHXHUBS Values panel


Alias nameAccept the default, which is the TEMS name (CMS_NODEID value). The alias nameidentifies the hub monitoring server to the SOAP server. The value is case-sensitive.

When you press Enter, the SOAP server KSHXHUBS List panel (Figure 21) is displayed, with thehub monitoring server shown on the list.

This panel lists the hub monitoring servers that are eligible for SOAP server access. The list ismaintained in the KSHXHUBS member of the &rhilev.&rte.RKANPARU library.

Tips

- You can specify non-local hubs if desired. To do so, enter A (Add TEMS) in the Actionfield to the left of any hub in the list. Then, on the Specify TEMS KSHXHUBS Valuespanel, provide the TEMS name, TCP hostname (network address), and Alias name forthe non-local hub.

- Do not edit the KSHXHUBS member directly. Its XML tags and values require a specificformat and are case-sensitive. If you want to change the contents of the KSHXHUBSmember, do so in the Configuration Tool.

If you exit the SOAP server KSHXHUBS List panel without securing user access, the SOAPserver honors requests from any user ID that passes logon validation. The value shown in theTEMS secured field indicates whether user access to the SOAP server is secured (Y) orunsecured (N). For an explanation of SOAP server security, see the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.

If you want to limit user access to the SOAP server, follow this procedure:

a. On the SOAP server KSHXHUBS List panel, enter S (Secure TEMS) in the Action field to theleft of the item for the hub you just added to the list.

The Specify TEMS KSHXHUBS Values panel (Figure 20 on page 55) is displayed, withAction: Secure at the top and with two fields at the bottom for specifying the first user ID towhich access is to be granted.

Specify initial user ID with Query and/or Update access:Query access ==> ________ Update access ==> ________Note: To add more users, press Enter.


b. On the Specify TEMS KSHXHUBS Values panel (Figure 20 on page 55), specify the first userID to have Query (read) access and Update (write) access. You can specify a user ID for

KDS62PPF --------- SOAP SERVER KSHXHUBS LIST / RTE: RTEname

The following Hub TEMS list is eligible for SOAP Server access.

RTE: RTEname Local SOAP Server: RTEname:CMS

Actions: A Add TEMS, U Update TEMS, D Delete TEMS,V View TEMS, S Secure TEMS,G Grant global security access, C Copy TEMS

RTE name TEMS name Preferred TEMSprotocol secured

_ RTEname RTEname:CMS IPPIPE N

F1=Help F3=Back F7=Up F8=Down

Figure 21. SOAP server KSHXHUBS List panel


Query access without specifying one for Update access, but if you specify a user ID forUpdate access, you must also specify a user ID for Query access.

c. If you want only one user ID to have access, press F3 to return to the SOAP serverKSHXHUBS List panel.

If you want to specify more user IDs, press Enter. The SOAP server KSHXHUBS SecurityAccess List panel is displayed (Figure 22).

d. Enter A (Add user) in the Action field to the left of the first user ID. The Specify TEMSKSHXHUBS User Access List panel is displayed (Figure 23).

e. Specify a user ID and indicate whether to grant it Query access and Update access.

f. Press Enter to return to the SOAP server KSHXHUBS Security Access List panel.

g. Continue adding user IDs until you have added all the user IDs to which you want to grantSOAP server access.

h. If you want to grant a user ID the same level of access to all hubs on the SOAP serverKSHXHUBS List, enter I (Install user into all monitored TEMS) to the left of the user ID onthe SOAP server KSHXHUBS Security Access List panel.

Caution: This action (I) has the immediate effect of securing every hub on the list and ofgranting access only to the user ID selected. Be sure you want this result before specifyingthe I action.

i. Press F3 (Back) until you return to the SOAP server KSHXHUBS List panel (Figure 21 onpage 56).

KDS62PPH --------- SOAP SERVER KSHXHUBS SECURITY ACCESS LIST ---- TEMS SECURED

The following users have access to the monitored Hub TEMS:

Local SOAP Server: RTEname:CMSMonitored Hub TEMS: RTEname:CMSMonitored RTE: RTEname

Actions: A Add user, U Update user access, D Delete userI Install user into all monitored TEMS

User ID Query Update_ user_id Y Y

F1=Help F3=Back F7=Up F8=Down

Figure 22. SOAP server KSHXHUBS Security Access List panel

KDS62PPI - SPECIFY TEMS KSHXHUBS USER ACCESS LIST / RTE: RTEname -------------

Add the TEMS SOAP Server KSHXHUBS values forRTEname:CMS

User ID ==>

Grant query access? ==> Y (Y, N)

Grant update access? ==> N (Y, N)


Figure 23. Specify TEMS KSHXHUBS User Access List panel


If you want to disable SOAP server security for a hub, specify G (Grant global security access) inthe Action field for that hub on the SOAP server KSHXHUBS List panel. This action removes alluser IDs from the user access list and thus enables access for all user IDs that pass logonvalidation.

Press F3 (Back) to return to the communication protocol configuration panels.

v IP.UDP and IP6.UDP

The field definitions and instructions for the IP.UDP and IP6.UDP protocols are the same as thosefor the IP*.*PIPE protocols, except that address translation does not apply to IP.UDP and IP6.UDP.

4. Press Enter to return to the Configure the TEMS panel (Figure 10 on page 40).

(Optional) Enable the self-describing agent capabilityFor the Tivoli Enterprise Monitoring Server you are configuring to correctly "seed" agents built with theself-describing capability (for version 6.2.3, these are only the distributed agents; in other words, no z/OSagent is self-describing), you must first enable the hub monitoring server with which these agents willcommunicate to receive and process self-description data. (For additional information about this capability,see “Whether to enable the self-describing agents capability” on page 15.) To enable the self-describingagent capability, complete the following procedure:

1. From the Configure the TEMS panel, enter 4 (Configure TEMS Self-Describing Agent Parameters) todisplay the Configure TEMS Self-Describing Agent Parameters (panel ID KDS62MC4), shown inFigure 24.

This panel lays out the remaining steps required for you to authorize the processing of self-describingagent data; they are:

a. Specify TEMS Self-Describing Agent values

Here you specify the parameters the monitoring server requires to process self-describing agentdata.

b. Create configuration members

Here you generate a batch job that will configure the runtime members that create the HFS or zFSdirectories and copy files to z/OS UNIX system services (USS).

c. Create USS directories and copy files on USS

KDS62MC4 ----- CONFIGURE TEMS SELF-DESCRIBING AGENT PARAMETERS ----------------

Perform the following steps in the order presented:Last selected

Date Time 1 Specify TEMS Self-DescribingAgent values 11/08/05 22:34 2 Create configurationmembers 11/08/05 23:14 3 CreateUSS directories and copy files on USS 11/08/05 23:14

F1=HelpF3=Back

Option ===>

Figure 24. Configure TEMS Self-Describing Agent Parameters panel


Here you generate a batch job that will create those HFS or zFS directories and copy the files toUSS.

The remaining subsections describe each of these steps in turn.

Specify TEMS Self-Describing Agent values:

1. From the Configure TEMS Self-Describing Agent Parameters panel (see Figure 24 on page 58), selectthe Specify TEMS Self-Describing Agent values step: tab to line 1, and enter S.

The TEMS Self-Describing Agent Values panel (panel ID KDS62PP4), shown in Figure 25, isdisplayed.

2. Turn on the processing of self-describing agent data: set Enable TEMS Self-Description processingto Y.

3. If the address space of the monitoring server you're configuring will also contain z/OS monitoringagents (such as the OMEGAMON XE on z/OS agent or the OMEGAMON XE for Storage agent), turnon support for self-describing agents within this monitoring server: set Agent Self-DescriptionProcessing in TEMS to Y.

Note: For Version 6.2.3 of the IBM Tivoli Monitoring, there are no self-describing z/OS agents;therefore, for now, leave this parameter set to N.

4. Supply the name of your site's Java root directory (initially /usr/lpp/java/IBM/J6.0) within UNIX SystemServices (USS).

The self-describing agent capability uses this directory to locate and load the jar utility.

5. Supply the name of your site's UNIX System Services procedure (CLIST) library (initiallySYS1.SBPXEXEC).

6. Press Enter to save these parameter values.

Create configuration members: From the Configure TEMS Self-Describing Agent Parameters panel(see Figure 24 on page 58), select the Create configuration members step: tab to line 2, and enter S.

KDS62PP4 -------- SPECIFY TEMS SELF-DESCRIBING AGENT VALUES -------------------

Enable TEMS Self-Description processing (KMS_SDA)==> N (Y, N) Agent Self-Description processing in TEMS(TEMA_SDA) ==> Y (Y, N)

JavaRoot directory for TEMS_JAVA_BINPATH (case sensitive):/usr/lpp/java/IBM/J6.0________________

________________________________________________________________________________________________________________________________________________________

USS CLIST library (Required) ==> SYS1.SBPXEXEC

Press F1=Help for informationabout the TEMS_MANIFEST_PATH USS SDA Home Directory.


OPTION ===>

Figure 25. Specify TEMS Self-Describing Agent Values panel


The DS#6T623 batch job is created and submitted.

Create USS directories and copy files on USS: From the Configure TEMS Self-Describing AgentParameters panel (see Figure 24 on page 58), select the Create USS directories and copy files on USSstep: tab to line 3, and enter S.

The DS#UT623 batch job is created and submitted.

Note: This job must be submitted on a machine that can access the USS directories. In addition, the jobmust be submitted by a TSO userid that has write access to the HFS/zFS directories.

Note about security definitions for the new USS filesTo create the runtime environment's new UNIX System Services directories, the DS#UT623 jobinvokes mkdir commands similar to the following:mkdir ’RTE_USS_RTEDIR/COMPUSS/kds/support/TEMS/META-INF’ MODE(7,7,7)

Note that these directories are created with MODE(7,7,7), which grants write permission to thesedirectories to all users. This MODE value is specified because the TSO userid of the person runningICAT or PARMGEN is not necessarily the same userid as that associated with the monitoring serverstarted task. However, both userids require write access to the runtime USS directories for thefollowing reasons:

v To support the self-describing agents feature, the monitoring server running on z/OS must be ableto add and remove files from these USS directories. A more restrictive MODE setting wouldprevent the monitoring server from doing so.

v If a subsequent uninstall is performed from ICAT, the TSO userid of the person running ICAT musthave write access to these same directories.

If your site requires a more secure access scheme for these runtime USS directories, you canaccomplish this using group-based security. Here's how:

1. The configurator's userid is dayce as in the above example, and it is connected to three securitygroups: GROUP1, GROUP2, and GROUP3.

Since GROUP1 is dayce's default group, all of the newly created RTE USS directories are ownedby GROUP1 by default.

2. The userid of the monitoring server started task is stcuser, and it is connected to two securitygroups: GROUP2 and GROUP4.

Since both userids have GROUP2 in common, the dayce userid could log on to USS and issue achgrp command to set GROUP2 as the owner of the runtime environment's USS directories, asin this example:> chgrp -R GROUP2 COMPUSS

3. Next, the dayce userid can issue a chmod command to change the original MODE(7,7,7) valueto something more restrictive, such as:> chmod -R 775 COMPUSS

After issuing this chmod command, only users who are connected to GROUP2 have writeaccess to the runtime USS directories.

If the configurator's userid and the userid associated with the monitoring server started task do nothave any security groups in common, you must either connect both userids to a common securitygroup or define a new security group and connect both userids to that group. Whichever option youchoose, you must still perform the chgrp and chmod actions described above.

This information applies to users of either the Configuration Tool (ICAT) or PARMGEN.


Create the runtime membersTo create the runtime members required by Tivoli Enterprise Monitoring Server, complete the followingprocedure:

1. From the Configure the TEMS panel, enter 5 to display the JCL for the DS#3ssss job that creates theruntime members required by the monitoring server. These members are created in the runtimelibraries for this runtime environment.

2. Review the JCL, edit if necessary, and submit. Verify that the job completes successfully and that allreturn codes are zero.

The following error messages indicate that ICSF is not configured correctly on your system:Cannot encrypt text: call to CSNBSYE failedCannot encrypt contents of keyfileFunction failed with error code 26

If you receive those messages, work with your security specialist to resolve the ICSF problem, andthen rerun only the KAES256 step of the DS#3ssss job. (If you rerun the entire job, the KAES256 stepis omitted for security reasons.)

3. When the job finishes, return to the Configure the TEMS panel (Figure 10 on page 40).

Configure the persistent datastoreIf you want to collect historical data, you must perform this step, which provides a job that configures apersistent datastore. The persistent datastore is the repository for short-term historical data that can beretrieved for table and chart views in the Tivoli Enterprise Portal.

For detailed planning information about the persistent datastore, see the IBM Tivoli OMEGAMON XE andIBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide. You can also findadditional information about the persistent datastore by entering README PDS from the command line of anypanel in the Configuration Tool.

To configure the persistent datastore, follow these steps.

1. On the Configure the TEMS panel (Figure 10 on page 40), enter 6 to display the Configure PersistentDatastore panel (Figure 26).

2. Enter 1 to display the Modify and Review Datastore Specifications panel (Figure 27 on page 62).

KPD62PP0 --------------- CONFIGURE PERSISTENT DATASTORE -----------------------Last selected

Perform these configuration steps in order: Date Time

1 Modify and review datastore specifications2* Create or edit PDS maintenance jobcard3 Create runtime members4 Allocate and initialize datastore files5 Complete persistent datastore configuration

* Note: The initial PDS maintenance jobcard defaults to the jobcardset on the Set up work environment option. This jobcard isshared by all products that configured historical collectionwithin this RTE=rte. Change to a generic jobcard, asnecessary.

F1=Help F3=Back

Figure 26. Configure Persistent Datastore panel


On this panel you can specify the placement of the data store files, how much space to allocate, andmaintenance options for the data store. The values you specified when configuring the monitoringserver (see Figure 14 on page 45) are displayed as default values. You can accept the defaults orchange them.

Group nameThe name of the group containing the historical data sets. You cannot edit this name.

Datasets in Group

LowlevThe low-level qualifier of the data set name. You cannot edit the low-level qualifier.

A 1-character value (1-9, A-Z) is suffixed to the low-level qualifier to indicate the data setnumber in the group. For example, if the low-level value is RGENHIS and there are three datasets in the group, these are the names of the data sets:

&rhilev.&rte.RGENHIS1



Count Indicates the number of data sets in the group. The minimum supported value is 3.

Volser/UnitAccept the default or modify it.

Storclas/MgmtclasAccept the default or modify it.

Est Cyl SpaceThis field is used to allocate space for the data sets and for overhead information such as theproduct dictionary, table records, index records, and buffers to hold overflow data when thedata sets are full. Allocate enough storage so that maintenance procedures can run only oncea day. See your monitoring agent publications for guidelines to estimating the space required.

If you collect short-term history for over 24 hours, but you still cannot create views at the TivoliEnterprise Portal for a full 24 hours of data, then you require more data sets (Count) or largerdata sets (Est Cyl Space).

MaintenanceThese fields are used for data store maintenance functions. Specify Y to turn on one or moreof these maintenance functions for a group.

BackupMakes an exact copy of the data set being maintained.

ExportWrites the data to a flat file in an internal format that can be used by external

KPD62PP3 ----- MODIFY AND REVIEW DATASTORE SPECIFICATIONS ---- Row 1 to 1 of 1

Modify persistent datastore allocation and maintenance information as requiredPress Enter to accept values and then F3 to return.

Datastore high-level qualifier: &rhilev.&rte

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extrac------------------------------------------------------------------------------GENHIST RGENHIS 3 ________ ________ 36__ N N N

________ ________F1=Help F3=Back

Figure 27. Modify and Review Datastore Specifications panel


programs to process the data. The exported data can also be used for recovery whenthe persistent datastore detects problems with the data.

ExtractWrites the data to a flat file in human-readable form that is suitable for loading intoother database management systems.

3. Press Enter to accept the values, and then press F3 to return to the Configure Persistent Datastorepanel (Figure 26 on page 61).

Tip: Option 2 (Create or edit PDS maintenance jobcard) on the Configure Persistent Datastore panel isno longer required. You can skip it.

Create runtime members for the persistent datastore:

1. On the Configure Persistent Datastore panel, enter 3 (Create runtime members) to display thePD#Pssss job that creates the persistent datastore runtime members.

2. Edit this job and submit it. Expect to see a return code of zero.

3. You are returned to the Configure Persistent Datastore panel (Figure 26 on page 61).

Allocate and initialize the persistent datastore files:

1. On the Configure Persistent Datastore panel, enter 4 (Allocate and initialize datastore files) to displaythe job that allocates and initializes all data sets required for the persistent datastore.

Note: This job applies to a new persistent datastore configuration. If the persistent datastore data setsalready exist, delete or rename the existing persistent data store files if you want the ConfigurationTool to reallocate and re-initialize the data sets for the persistent datastore.

2. Edit this job and submit it. Expect to see a return code of zero.

3. You are returned to the Configure Persistent Datastore panel (Figure 26 on page 61).

Prepare to complete the configuration of the persistent datastore and monitoringserver1. On the Configure Persistent Datastore panel, enter 5 (Complete persistent datastore configuration) to

display a list of the steps you must take outside the Configuration Tool to complete the configuration ofthe persistent datastore. Print this list for later reference, but wait to complete the steps.

2. Press F3 until you return to the Configure the TEMS panel (Figure 10 on page 40).

3. On the Configure the TEMS panel, select Option 7 (Complete the configuration) to display a list of thesteps you must take outside the Configuration Tool to complete the configuration of the monitoringserver. Print this list for later reference, but wait to complete the steps until you finish loading theruntime libraries.

4. Press F3 (Back) until you return to the Runtime Environments (RTEs) panel Figure 6 on page 34.

Load the runtime librariesBefore you complete the configuration of the monitoring server outside the Configuration Tool, you mustload the runtime libraries from the target libraries that were installed by SMP/E. The load job requiresexclusive access to the runtime libraries.

1. On the Runtime Environments (RTEs) panel Figure 6 on page 34, enter L (Load) in the Action field tothe left of the name of the runtime environment.

2. Review the JCL and submit the job. Verify that the job completes successfully and that the return codeis 04 or lower.

3. When you finish loading the libraries, press F3 (Back) until you return to the Product Selection Menu(Figure 5 on page 33).

Complete the configuration of the high-availability hubSee Part 3, “Post-configuration procedures,” on page 117 for information about completing theconfiguration of the hub monitoring server outside the Configuration Tool. Because the high-availability hub


is the only component configured in its runtime environment, you can complete its configuration now,without waiting to configure other components and products.

Step 4. Configure a remote monitoring server to report to thehigh-availability hubAfter you finish configuring the high-availability hub, create a second runtime environment on the sameLPAR, and configure a remote monitoring server to report to the high-availability hub.

To configure the remote monitoring server, perform the following tasks in order:

1. Follow the instructions in Chapter 5 of the IBM Tivoli OMEGAMON XE and IBM Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide to add a runtime environment and buildthe runtime libraries.

ImportantOn the Product Selection Menu (Figure 5 on page 33), select a monitoring agent product ratherthan selecting IBM Tivoli Management Services on z/OS. When you select a monitoring agent,you can configure a monitoring server and one or more monitoring agents in the same runtimeenvironment. If you select Tivoli Management Services on z/OS, you can only configure astand-alone monitoring server in its own runtime environment, without any monitoring agents.

2. “Begin the configuration.”

3. “Create a logmode” on page 65.



6. “(Optional) Enable the self-describing agent capability” on page 74.




1. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), enter C (Configure) next to theruntime environment you added for the remote monitoring server and monitoring agents.

The Product Component Selection Menu is displayed (Figure 28).

2. From the Product Component Selection Menu, enter 1 to select Tivoli Enterprise Monitoring Server.

KCIPMCU --------------- PRODUCT COMPONENT SELECTION MENU ----------------------

The following list of components requires configuration to make the productoperational. Refer to the appropriate configuration documentation if yourequire additional information to complete the configuration.To configure the desired component, enter the selection number on the commandline. You should configure the components in the order they are listed.

Note: It may not be necessary to configure Tivoli Enterprise Monitoring Server(TEMS) component, if listed below. Press F1 for more information.

COMPONENT TITLE

1 Tivoli Enterprise Monitoring Server2 monitoring_agent_component_13 monitoring_agent_component_2

Figure 28. Product Component Selection Menu


The Configure the TEMS panel is displayed (Figure 10 on page 40).

Create a logmodeIf the monitoring server is to communicate with any monitoring agents that require SNA, you must create alogmode or provide information about an existing logmode. Examples of monitoring agents that requireSNA communications include OMEGAMON XE on z/OS (for the EPILOG facility of the OMEGAMON IIcomponent) and OMEGAMON XE for Messaging on z/OS (for the 3270 interface component). See theproduct-specific configuration guides for further information about SNA requirements.

If this monitoring server will not communicate with any monitoring agents that require SNA, you can skip to“Specify configuration values” on page 66.

Otherwise, complete the following procedure:

1. From the Configure the TEMS panel (Figure 10 on page 40), enter 1 (Create LU 6.2 logmode).

The Create LU6.2 Logmode panel is displayed (Figure 29). Use this panel to specify the name of theLU6.2 logmode and logmode table to be used for SNA communications.

Tip: If you plan to use an existing LU6.2 logmode, you do not have to submit the job created from thispanel. However, you must ensure that the existing logmode has the same VTAM attributes as thelogmode contained in the job. Be sure to provide the logmode information, even if you do not intend tosubmit the job.

2. Review the values on the panel and specify site-specific values.

LU6.2 logmodeThe name of the LU6.2 logmode. A name is required even if you do not submit the job.

Logmode table nameThe name of the logmode table that contains the LU6.2 logmode. A name is required even ifyou do not submit the job.

VTAMLIB load libraryThe name of the system library that contains VTAM logmode tables. This is typicallySYS1.VTAMLIB (the default value), but you can specify a different load library if you cannot ordo not want to update VTAMLIB directly.

VTAM macro libraryThe name of the system library that contains the VTAM macros. This library is typicallySYS1.SISTMAC (the default).

3. To accept the values, press Enter.

The JCL to create the logmode is displayed.

v If you want to use the LU6.2 logmode created by this job, review the JCL and submit the job. Verifythat the job completes successfully and that all return codes are zero.

v If you want to use an existing LU6.2 logmode whose attributes match those in the logmode createdby the job, press F3 (End) without submitting the job.

KDS62PLU -------------------- CREATE LU6.2 LOGMODE ----------------------------

The TEMS requires an LU6.2 logmode. Complete the items on this panel andpress Enter to create a job that will assemble and link the required logmode.

LU6.2 logmode ==> CANCTDCSLogmode table name ==> KDSMTAB1

VTAMLIB load library ==> SYS1.VTAMLIBVTAM macro library ==> SYS1.SISTMAC1

Figure 29. Create LU6.2 Logmode panel


You are returned to the Configure the TEMS panel (Figure 10 on page 40).

Specify configuration valuesIn this step you indicate that the monitoring server you are configuring is a remote monitoring server andthat it reports to the high-availability hub. You also specify the name of the started task for the remotemonitoring server and its security settings. Security validation of users is handled by hub monitoringservers only. Do not attempt to enable security validation on a remote monitoring server.

1. From the Configure the TEMS menu (Figure 10 on page 40), enter 2 to display the SpecifyConfiguration Values panel (Figure 11 on page 41).

2. Provide values in the following fields:

Started taskThe name of the remote monitoring server started task JCL procedure. Make a note of thename, because later you will have to copy this started task procedure to your systemprocedure library. The default is CANSDSST.

Type (Hub or Remote)Specify REMOTE as the monitoring server type.

Hub TEMS typeLeave this field blank.

Tip: If you come back to this panel later, this field will not be displayed, because it appliesonly to a hub monitoring server.

Security settings

Validate security?This setting determines whether the hub monitoring server validates the user IDs andpasswords of users signing on to the Tivoli Enterprise Portal. Leave the value N forremote monitoring servers.


Note: The encryption method specified for the remote and hub monitoring serversmust match that of the Tivoli Enterprise Portal Server. If you specify that ICSF is notinstalled on this z/OS system (N), you must add the line USE_EGG1_FLAG=1 (orUSE_EGG1_FLAG=Y) to the KFWENV environment file of the Tivoli Enterprise PortalServer (see “(If applicable) Edit the portal server environment file” on page 123).



TMS encryption keySpecify a unique, 32-byte password encryption key. The value is case-sensitive. Besure to record the value you use for the key. You must use the same key during theinstallation of any monitoring agents that communicate with this monitoring server.


Program to Program Interface (PPI) information(Optional) Specify the PPI values that enable forwarding of Take Action commands to NetView


for z/OS for authorization and execution. If you enable forwarding, you must also enableNetView to receive and authorize the commands (see “Enable NetView to authorize TakeAction commands” on page 152).


NetView PPI receiverSpecify the name of the PPI receiver on NetView that will receive Take Actioncommands. This name must match the receiver name specified on the NetViewAPSERV command. The default name is CNMPCMDR. If the specified name is incorrect orthe receiver is not active on NetView for z/OS, default command routing to the z/OSconsole is performed. The Configuration Tool generates the KGLHC_PPI_RECEIVERenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library.

The value must be a 1- through 8-character, unique identifier for the receiver program.It can contain alphabetic characters A-Z and a-z, numeric characters 0-9, and thefollowing special characters: dollar sign ($), percent sign (%), ampersand (&), at sign(@), and number sign (#). This value must match the value specified in the NetViewDSIPARM initialization member, CNMSTYLE (see “Enable NetView to authorize TakeAction commands” on page 152).



TEMS PPI senderOptionally, specify the name of the PPI sender. The value must be a 1- through8-character unique identifier for the receiver program. It can contain alphabeticcharacters A-Z and a-z, numeric characters 0-9, and the following special characters:dollar sign ($), percent sign (%), ampersand (&), at sign (@), and number sign (#).This name must not conflict with any NetView for z/OS domain name, as it is used inlogging the command and command response in the NetView log. If a value isspecified on this field, the Configuration Tool generates the KGLHC_PPI_SENDERenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library.


3. When you have completed the Specify Configuration Values panel, press F5 (Advanced) to display theSpecify Advanced Configuration Values panel (Figure 14 on page 45). Accept the defaults or providethe values appropriate for your site in the following fields:

Enable Web Services SOAP ServerAccept the default value of Y. The SOAP server must be enabled for a hub monitoring server.See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide for more information.






The default setting (KDC_DEBUG=N) generates standard RAS1 trace data in the monitoring serverRKLVLOG, in addition to the summary information diagnosing possible timeout conditions.










Virtual IP Address (VIPA) typeSpecify D (Dynamic VIPA, or DVIPA). DVIPA requires one of the following communicationprotocols: IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE. For more information about specifyingcommunication protocols, see “Specify communication protocols” on page 51.

Minimum extended storageSpecify the minimum amount of virtual storage to be made available to the monitoring agents


and other components that are communicating with this monitoring server. The default value is768000. If you do not have many IBM components reporting to the server and you want toconserve storage, you can lower the value.













Maximum in-memory cache entriesThis parameter defines the maximum number of auditing records kept in short-term


memory, from 10 to 1000; it generates an AUDIT_MAX_HIST parameter in memberKDSENV of the RKANPARU library. If you do not specify a value here,AUDIT_MAX_HIST=100 is set as the default.


To specify advanced parameters for the Persistent Datastore, press F6 (PDS) to display the KDSPPDS(Specify Persistent Datastore Configuration Values) panel (see Figure 15 on page 48). These fieldsdefine default parameters for the persistent datastore, the repository for short-term historical data. Fordetailed information, see IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide.










Tip: Under the guidance of IBM Software Support, you can specify values for parameters other thanthose shown on the Specify Configuration Values and Specify Advanced Configuration Values panels.To do so, press F5 from the Specify Advanced Configuration Values panel to display the SpecifyNonstandard Parameters panel. On this panel you can add, replace, or delete parameter values in anymember of any runtime library. For details, press F1 on the Specify Nonstandard Parameters panel orsee the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planningand Configuration Guide.

4. Press Enter to accept the values.


The Communication Selection panel is displayed, as shown in Figure 30. This panel lists hubmonitoring servers configured in other runtime environments accessible to the Configuration Tool.

5. Enter S beside the high-availability hub. In the example, this is the hub in the runtime environmentnamed HAHUB.


Specify communication protocolsTo specify protocols for communications with this remote monitoring server, complete the followingprocedure:

1. From the Configure the TEMS panel (Figure 10 on page 40), enter 3 to display the SpecifyCommunication Protocols panel (Figure 31).

This panel lists the communication protocols to be used by the remote monitoring server. The numberbeside each protocol indicates its priority. When communication with another component is initiated,the monitoring server tries Protocol 1 first and goes to Protocol 2 and then to Protocol 3, and so on, incase of failure.

KCIPCMSS -------- COMMUNICATION SELECTION PANEL FOR SHARING2 Row 1 to 1 of 1

Select the hub (primary TEMS) to connect to this remote TEMS.

The following lists eligible Tivoli Enterprise Monitoring Servers(TEMS) that you have configured. Enter S next to the TEMS to connectto this remote. To manually enter the TEMS information, press F5.

TEMS RTE name RTEType (mid-level) Description

-----------------------------------------------------------------------------_ HUB HAHUB Runtime environment for high-availability hub

F1=Help F3=Back F5=Advanced F7=Up F8=Down

Figure 30. Communication Selection panel

KDS62PPA -------------- SPECIFY COMMUNICATION PROTOCOLS ----------------------

Specify the communication protocols in priority sequence forTEMS rte:CMS.

IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> 2 (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)SNA.PIPE ==> 3 (Non-secure NCS RPC)

Note: SNA.PIPE is required under certain conditions. Press F1=Help.* This Remote TEMS reports to a Hub that uses IP.PIPE to connect.

Ensure that this Remote TEMS also specifies the IP.PIPE protocol.* The protocol(s) in use by the Hub TEMS are:

-Unsecured IP.PIPE -Unsecured IP.UDP* Ensure that this Remote TEMS also specifies a Network interface list

that is compatible with the Hub TEMS.


Figure 31. Specify Communication Protocols panel


Tips

v Because the high-availability hub uses a piped protocol (IP.PIPE, IP6.PIPE, IP.SPIPE, orIP6.SPIPE), you must select that protocol for the remote monitoring server.

v If the remote monitoring server will communicate with any monitoring agents that require SNA,SNA.PIPE must be one of the protocols chosen, but it does not have to be Protocol 1.Examples of such monitoring agents include OMEGAMON XE on z/OS (for the EPILOG facilityof the OMEGAMON II component) and OMEGAMON XE for Messaging on z/OS (for the 3270interface component). See the product-specific configuration guides for further informationabout SNA requirements.


2. Supply the priority number for each protocol you want to select.




Figure 32 shows the Specify IP.PIPE Communication Protocol panel, where you specify values forthe IP.PIPE, IP6.PIPE, IP.SPIPE, and IP6.SPIPE protocols.

Network address (Hostname)The TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where theremote monitoring server is installed. To obtain the host name and IP address, enter TSOHOMETEST at the command line.

If the z/OS domain name resolver configuration specifies a search path that includes thetarget domain suffix, specify only the first qualifier of the host name. (Example: sys is thefirst qualifier of the fully qualified host name sys.ibm.com.) Otherwise, specify the fullyqualified host name.

KDS62PPD ----------- SPECIFY IP.PIPE COMMUNICATION PROTOCOL -----------------

Specify IP.PIPE communication values.

* Network address (Hostname):==> system_hostname

Started task ==> * (Recommended default = *)Network interface list: (Required**)

==> !*** Non-local Hub TEMS interface list: "!OMEGAHUB"** Use "!*": Required for any Remote TEMS connecting to an HA Hub

Port number of Hub ==> 1918 (IP.PIPE)Port number of Hub ==> (IP.PIPE for IPV6)Port number of Hub ==> (Secure IP.PIPE)Port number of Hub ==> (Secure IP.PIPE for IPV6)

Address translation ==> N (Y, N)Partition name ==>



Figure 32. Specify IP.PIPE Communication Protocol panel






Network interface listYou must specify one of the following values for a remote monitoring server reporting to thehigh-availability hub in the same sysplex:

– !* to force the remote monitoring server to use only the interface associated with thedefault host name for the z/OS image.

– -dvipa_hostname to use any interface except the one associated with dvipa_hostname.

When you supply a value in the Network interface list field, the Configuration Toolgenerates the KDEB_INTERFACELIST environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library. See "Network interfaces" in the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guidefor more information about interface lists.

Hub port numbersFor each of the selected IP*.*PIPE protocols, these fields specify the well-known port for thehub. These fields are read-only.





When you press Enter after providing the IP*.*PIPE configuration values, if you specified Y forAddress translation, the Specify IP.PIPE Partition References panel (Figure 19 on page 54) isdisplayed. The name of the monitoring server, its partition name (that is, its location or namespacerelative to the firewall), and its partition address (the IP address assigned to the monitoring server inthe specified partition) are displayed at the top of the Specify IP.PIPE Partition References panel.


Use the fields of this panel to specify partition references (the values required to supportcommunication across a firewall using address translation rather than EPS). If more than onefirewall is used, specify a partition reference for each firewall.


AddressSupply the IP address assigned to the monitoring server from a location on the other side ofthe firewall.

To add a partition reference, specify the partition name and the address used in that partition tocommunicate with the monitoring server, and press Enter. To modify an existing partition reference,type over an entry and press Enter. To delete a reference, type D in the Action field and pressEnter. Modifications resulting in duplicate entries are ignored.

The values provided on this panel are saved as the KDC_PARTITIONFILE environment variable inthe KDSENV member of the &rhilev.&rte.RKANPARU library. KDC_PARTITIONFILE points to amember, KDCPART, created in the &rhilev.&rte.RKANPARU library.



v SNA.PIPE

Figure 33 shows the Specify SNA Communication Protocol panel.

Supply values for these fields.

Applid prefixThis value is used to create the VTAM applids required by the monitoring server. Theseapplids begin with the prefix, and end with a specific value that makes each applid unique.The applids are contained in the VTAM major node. You specified this value when youdefined the runtime environment.

Network IDThe identifier of your VTAM network. You specified this value when you defined the runtimeenvironment. You can also obtain this value from the NETID parameter in the VTAMLSTstartup member ATCSTRnn.


(Optional) Enable the self-describing agent capabilityFor the Tivoli Enterprise Monitoring Server you are configuring to correctly "seed" agents built with theself-describing capability (for version 6.2.3, these are only the distributed agents; in other words, no z/OSagent is self-describing), you must first enable the hub monitoring server with which these agents willcommunicate to receive and process self-description data. (For additional information about this capability,see “Whether to enable the self-describing agents capability” on page 15.) To enable the self-describingagent capability, complete the following procedure:

KDS62PPB ------------- SPECIFY SNA COMMUNICATION PROTOCOL ---------------------

Specify the SNA communication values for this TEMS.

Applid prefix ==> DSNetwork ID ==> (NETID value from SYS1.VTAMLST(ATCSTRnn))

Enter=Next F1=Help F3=Back F6=Applids

Figure 33. Specify SNA Communication Protocol panel


1. From the Configure the TEMS panel, enter 4 (Configure TEMS Self-Describing Agent Parameters) todisplay the Configure TEMS Self-Describing Agent Parameters (panel ID KDS62MC4), shown inFigure 24 on page 58.

This panel lays out the remaining steps required for you to authorize the processing of self-describingagent data; they are:

a. Specify TEMS Self-Describing Agent values

Here you specify the parameters the monitoring server requires to process self-describing agentdata.

b. Create configuration members

Here you generate a batch job that will configure the runtime members that create the HFS or zFSdirectories and copy files to z/OS UNIX system services (USS).

c. Create HFS directories and copy files on USS

Here you generate a batch job that will create those HFS or zFS directories and copy the files toUSS.

The remaining subsections describe each of these steps in turn.

Specify TEMS Self-Describing Agent values:

1. From the Configure TEMS Self-Describing Agent Parameters panel (see Figure 24 on page 58), selectthe Specify TEMS Self-Describing Agent values step: tab to line 1, and enter S.

The TEMS Self-Describing Agent Values panel (panel ID KDS62PP4), shown in Figure 25 on page 59,is displayed.

2. Turn on the processing of self-describing agent data: set Enable TEMS Self-Description processingto Y.

3. If the address space of the monitoring server you're configuring will also contain z/OS monitoringagents (such as the OMEGAMON XE on z/OS agent or the OMEGAMON XE for Storage agent), turnon support for self-describing agents within this monitoring server: set Agent Self-DescriptionProcessing in TEMS to Y.

Note: For Version 6.2.3 of the IBM Tivoli Monitoring, there are no self-describing z/OS agents;therefore, for now, leave this parameter set to N.

4. Supply the name of your site's Java root directory (initially /usr/lpp/java/IBM/J6.0) within UNIX SystemServices (USS).

The self-describing agent capability uses this directory to locate and load the jar utility.

5. Supply the name of your site's UNIX System Services procedure (CLIST) library (initiallySYS1.SBPXEXEC).

6. Press Enter to save these parameter values.

Create configuration members: From the Configure TEMS Self-Describing Agent Parameters panel(see Figure 24 on page 58), select the Create configuration members step: tab to line 2, and enter S.

The DS#6T623 batch job is created and submitted.

Create HFS directories and copy files on USS: From the Configure TEMS Self-Describing AgentParameters panel (see Figure 24 on page 58), select the Create HFS directories and copy files on USSstep: tab to line 3, and enter S.

The DS#UT623 batch job is created and submitted.

Note: This job must be submitted on a machine that can access the USS directories. In addition, the jobmust be submitted by a TSO userid that has write access to the HFS/zFS directories.


Note about security definitions for the new USS filesTo create the runtime environment's new UNIX System Services directories, the DS#UT623 jobinvokes mkdir commands similar to the following:mkdir ’RTE_USS_RTEDIR/COMPUSS/kds/support/TEMS/META-INF’ MODE(7,7,7)

Note that these directories are created with MODE(7,7,7), which grants write permission to thesedirectories to all users. This MODE value is specified because the TSO userid of the person runningICAT is not necessarily the same userid as that associated with the monitoring server started task.However, both userids require write access to the runtime USS directories for the following reasons:

v To support the self-describing agents feature, the monitoring server running on z/OS must be ableto add and remove files from these USS directories. A more restrictive MODE setting wouldprevent the monitoring server from doing so.

v If a subsequent uninstall is performed from ICAT, the TSO userid of the person running ICAT musthave write access to these same directories.

If your site requires a more secure access scheme for these runtime USS directories, you canaccomplish this using group-based security. Here's how:

1. The ICAT userid is dayce as in the above example, and it is connected to three security groups:GROUP1, GROUP2, and GROUP3.

Since GROUP1 is dayce's default group, all of the newly created RTE USS directories are ownedby GROUP1 by default.

2. The userid of the monitoring server started task is stcuser, and it is connected to two securitygroups: GROUP2 and GROUP4.

Since both userids have GROUP2 in common, the dayce userid could log on to USS and issue achgrp command to set GROUP2 as the owner of the runtime environment's USS directories, asin this example:> chgrp -R GROUP2 COMPUSS

3. Next, the dayce userid can issue a chmod command to change the original MODE(7,7,7) valueto something more restrictive, such as:> chmod -R 775 COMPUSS

After issuing this chmod command, only users who are connected to GROUP2 have writeaccess to the runtime USS directories.

If the ICAT userid and the userid associated with the monitoring server started task do not have anysecurity groups in common, you must either connect both userids to a common security group ordefine a new security group and connect both userids to that group. Whichever option you choose,you must still perform the chgrp and chmod actions described above.

Create runtime members and configure the persistent datastoreFollow the instructions in “Create the runtime members” on page 61 to create the runtime members for theremote monitoring server, and then follow the instructions in “Configure the persistent datastore” on page61 to configure the persistent datastore and create its runtime members.

Then press F3 (Back) until you return to the Product Component Selection panel (Figure 28 on page 64).

Step 5. Configure monitoring agents to report to the remotemonitoring serverIn this step, you configure monitoring agents in the same runtime environment with the remote monitoringserver.


1. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. If twomonitoring agent components are listed, select the OMEGAMON II component first.

COMPONENT TITLE

1 Tivoli Enterprise Monitoring Server2 OMEGAMON II ...3 IBM Tivoli OMEGAMON XE ...

2. To configure the monitoring agent, follow the configuration instructions in the product publications in theTivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=.

Be sure to select the option Register with local TEMS. This option produces a job that enables themonitoring agent to transmit data to the remote monitoring server.

If you are configuring the monitoring agent in its own address space, be sure to leave the default valueof Y at this prompt:

Connect to TEMS in this RTE ==> Y (Y, N)

Follow the steps up to Complete the configuration.

3. Press F3 until you return to the Product Selection Menu (Figure 5 on page 33).

4. On the Product Selection Menu, enter S (Select) to the left of the name of another monitoring agent.

5. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), type C (Configure) in the Actionfield to the left of the name of the runtime environment where you configured the remote monitoringserver and the first monitoring agent.

6. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. Youdo not have to reconfigure the remote monitoring server to add a monitoring agent to the runtimeenvironment.

7. Repeat steps 2 to 6 until you have configured all desired monitoring agents in the runtimeenvironment.

Step 6. Load the runtime librariesBefore you complete the configuration of the monitoring server and monitoring agents outside theConfiguration Tool, you must load the runtime libraries from the target libraries that were installed bySMP/E. The load job requires exclusive access to the runtime libraries.



3. When you finish loading the libraries, press F3 (Back) to return to the Runtime Environments (RTEs)panel.

4. Go to Chapter 6, “Completing the configuration,” on page 119, Chapter 7, “Adding application supportto a monitoring server on z/OS,” on page 129, and Part 3 of the IBM Tivoli OMEGAMON XE and IBMTivoli Management Services on z/OS: Common Planning and Configuration Guide for instructions oncompleting the configuration, adding application support to the monitoring servers, and validating theconfiguration.

5. After you validate the configuration, perform the tasks in Chapter 8, “Configuring security on amonitoring server on z/OS,” on page 143.

6. Go to Parts 4 and 5 of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide for instructions on using batch mode to replicate theconfigured environment to other LPARs.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?toc=



Chapter 4. Configuring the hub monitoring server andmonitoring agents in the same runtime environment

If your environment does not have DVIPA or does not meet some other requirement of the high-availabilityhub, you have other configuration options. The configuration shown in Figure 34 depicts the hubmonitoring server and several monitoring agents installed in the same runtime environment on a singlez/OS image, with the monitoring agents reporting directly to the hub. This configuration is a basic one thatyou can expand to accommodate more systems.

PARMGEN methodComplete these steps to configure a hub monitoring server and monitoring agents in the same runtimeenvironment.

Tip: To configure a stand-alone hub monitoring server that is not a high-availability hub, perform themonitoring server configuration as described in this section, but omit “Step 2. Set configuration parametersfor the monitoring agents in the same runtime environment” on page 81.

Step 1. Create the runtime environment and set the configurationparameters for the hubFollow the steps in the "Configuring products with the PARMGEN method" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide to create a runtime environment. In "Step 2. Set up your PARMGEN configuration profile," refer tothe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common ParameterReference for information about the parameters in the configuration profile. The configuration profile is the&rhilev.&rte.WCONFIG(&rte) member.

Figure 34. Hub monitoring server and monitoring agents in the same runtime environment


Tips

v The parameters shown in this section are specific to the hub monitoring server but are not the onlyparameters for which you must either accept or override the default values in the configurationprofile for the runtime environment. After you set the parameters shown here, be sure to gothrough the entire configuration profile to make sure the parameter values are correct for theconfiguration you want.

v The parameters with names beginning KDS_HUB are not parameters for the hub monitoringserver; they are parameters for remote monitoring servers.

v Be sure to uncomment any parameters that are needed for your configuration but are commentedout by default. For example, if you want to enable event forwarding, uncomment theKDS_TEMS_EIF_FLAG parameter and make sure its value is Y. To uncomment a parameter in theconfiguration profile, delete the two asterisks (**) from the beginning of the line.

Before:**KDS_TEMS_EIF_FLAG Y

After:KDS_TEMS_EIF_FLAG Y

Be sure to set the following parameter values for the hub in the configuration profile:* Tivoli Enterprise Monitoring Server: KDS flagCONFIGURE_TEMS_KDS "Y"

** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:RTE_TEMS_CONFIGURED_FLAG YRTE_TEMS_NAME_NODEID "rte_name:CMS"

** TEMS configuration values:KDS_TEMS_TYPE HUB

The following additional requirements also apply to the hub configuration:

KDS_TEMS_COMM_PROTOCOLn parameterAt least one of the values must be IPPIPE, IP, IP6PIPE, IP6, IPSPIPE, or IP6SPIPE. If thismonitoring server will communicate with any monitoring agents that require SNA, SNA must be oneof the protocols chosen, but it does not have to be Protocol 1. Examples of such monitoringagents include OMEGAMON XE on z/OS (for the EPILOG facility of the OMEGAMON IIcomponent) and OMEGAMON XE for Messaging on z/OS (for the 3270 interface component). Seethe product-specific configuration guides for further information about SNA requirements.

KDS_TEMS_TCP_PIPEc_PORT_NUMThe port number that you set for each protocol used by the hub must be respecified for everycomponent that will communicate with the hub.


Configuring the monitoring server to support encryption/decryptionTo activate ICSF encryption/decryption within your newly configured hub monitoring server using thePARMGEN configuration method, locate these lines in the configuration profile for the runtime environmentof the monitoring server::** GBL_DSN_CSF_* ICSF system libraries:GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"** TMS KAES256 password encryption key:**KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"











Step 2. Set configuration parameters for the monitoring agents in thesame runtime environmentIn the same configuration profile, set parameter values for each of the products you want to include in theruntime environment of the hub monitoring server. Follow the instructions in each product's Planning andConfiguration Guide, and use the information in each product's Parameter Reference.


Step 3. (Optional) Replicate the runtime environment to a remotesystemIf desired, you can replicate the configured runtime environment to another LPAR where the TivoliEnterprise Monitoring Server and monitoring agents are installed, and set the monitoring serverparameters for a remote rather than a hub monitoring server configuration. Follow the instructions in the"Using the PARMGEN method to replicate a configured environment" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

In the configuration profile of the second runtime environment, set the following parameter values for theremote monitoring server:

Chapter 4. Configuring the hub monitoring server and monitoring agents in the same runtime environment 81

** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:RTE_TEMS_CONFIGURED_FLAG YRTE_TEMS_NAME_NODEID "remote_rte_name:CMS"



KDS_TEMS_COMM_PROTOCOLn parameterAt least one of the communication protocols must be the same as a protocol selected for the hub.For information about the communication protocols, see "Decision 5: How to set upcommunications between components" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.


KDS_HUB_TCP_HOST parameterThis is the TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where the hubmonitoring server is installed. This parameter applies only to a remote monitoring server that usesTCP/IP for communications. The value specified for this parameter must match the value set forthe KDS_TEMS_TCP_HOST parameter in the runtime environment where the hub is configured.


Many other KDS_* parameters are needed for the remote monitoring server configuration. See the IBMTivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference forinformation about them.

Modify as needed the monitoring agent parameter values for communication with the remote monitoringserver in the same runtime environment. Follow the instructions in each product's Planning andConfiguration Guide, and use the information in each product's Parameter Reference.


Now you can replicate to other z/OS systems the configured runtime environment that contains the remotemonitoring server and its monitoring agents. Follow the instructions in the "Using the PARMGEN method toreplicate a configured environment" chapter of the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

Configuration Tool (ICAT) methodBe sure to complete Steps 1, 2, and 3 in the "Configuring products with the Configuration Tool" chapter ofthe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide before you begin the configuration steps in this section.


Important

v When you select a product on the Product Selection Menu (Figure 5 on page 33), select one ofthe monitoring agents, not IBM Tivoli Management Services on z/OS, if you want to configure botha monitoring server and monitoring agents in the runtime environment. If you select IBM TivoliManagement Services on z/OS, you can only configure a stand-alone monitoring server in its ownruntime environment, without any monitoring agents.

v To configure a stand-alone hub monitoring server that is not a high-availability hub, you select IBMTivoli Management Services on z/OS and perform the monitoring server configuration as describedin this section, but omit “Step 2. Configure monitoring agents in the runtime environment” on page97.

Configuration stepsComplete the following steps in order:

__ “Step 1. Configure the hub monitoring server”

__ “Step 2. Configure monitoring agents in the runtime environment” on page 97


Step 1. Configure the hub monitoring serverIf you intend to use a z/OS hub and you have not already configured one, the first monitoring server youconfigure must be a hub.

To configure the hub monitoring server, perform the tasks in the following sections:


2. “Create a logmode.”






1. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), enter C (Configure) next to theruntime environment you added for the hub monitoring server and monitoring agents.

The Product Component Selection Menu is displayed (Figure 28 on page 64).



Tip: Select option I (Configuration information: What's New) to read about updates to monitoringserver configuration options since the previous versions.



If this monitoring server will not communicate with any monitoring agents that require SNA, you can skip to“Specify configuration values.”



The Create LU6.2 Logmode panel is displayed (Figure 29 on page 65). Use this panel to specify thename of the LU6.2 logmode and logmode table required by the monitoring server.












Specify configuration valuesIn this step you indicate that the monitoring server you are configuring is a hub. You also specify the nameof the started task for this monitoring server and whether security validation is in force for the server. Donot enable security validation at this point. Security can be set up more effectively after you complete andverify the configuration.

1. From the Configure the TEMS panel (Figure 10 on page 40), enter 2 to display the SpecifyConfiguration Values panel (Figure 11 on page 41).

2. Provide values for the following fields.

Started taskThe name of the monitoring server started task JCL procedure. Make a note of the name,because later you will have to copy this started task procedure to your system procedurelibrary. The default is CANSDSST.

Tip: If you have two or more runtime environments on the same z/OS image, make sure thatthe name of each started task is unique.

Type (Hub or Remote)Specify HUB as the monitoring server type.


Hub TEMS typeLeave this field blank. If you specify HA to configure a high-availability hub, you cannotconfigure monitoring agents in the same runtime environment as the hub. To configure ahigh-availability hub, follow the instructions in Chapter 3, “Configuring a high-availability huband the remote monitoring servers that report to it,” on page 27.

For more information about the high-availability hub, see “Whether to configure ahigh-availability hub on z/OS” on page 13.

Security settings

Validate security?This setting determines whether the hub monitoring server validates the user IDs andpasswords of users signing on to the Tivoli Enterprise Portal. Leave the value N fornow. If you set security validation to Y at this point, you will have difficulty completingthe configuration steps and verifying the configuration. You can return to this panel andset security validation to Y later, after you set up security for the monitoring server (seeChapter 8, “Configuring security on a monitoring server on z/OS,” on page 143). Whensecurity validation is enabled on this panel, validation of users is handled by thesecurity system specified for the runtime environment.


Note: The encryption method specified for the monitoring server and the TivoliEnterprise Portal Server must match. If you specify that ICSF is not installed on thisz/OS system (N), you must add the line USE_EGG1_FLAG=1 (or USE_EGG1_FLAG=Y) to theKFWENV environment file of the Tivoli Enterprise Portal Server (see “(If applicable)Edit the portal server environment file” on page 123).



TMS encryption keySpecify a unique, 32-byte password encryption key. The value is case-sensitive. Besure to record the value you use for the key. You must use the same key during theinstallation of any components that communicate with this monitoring server, such asthe Tivoli Enterprise Portal Server or a remote monitoring server.



Encryption key tips



v For security reasons, the encryption key value is not displayed if you return tothe Specify Configuration Values panel after you finish configuring themonitoring server. If you reconfigure the monitoring server by changing otherparameter values on the configuration panels, the resulting DS#3ssss job doesnot create a new key file.




Program to Program Interface (PPI) information(Optional) Specify the PPI values that enable forwarding of Take Action commands to NetViewfor z/OS for authorization and execution. If you enable forwarding, you must also enableNetView to receive and authorize the commands (see “Enable NetView to authorize TakeAction commands” on page 152).




The value must be a 1- through 8-character unique identifier for the receiver program.It can contain alphabetic characters A-Z and a-z, numeric characters 0-9, and thefollowing special characters: dollar sign ($), percent sign (%), ampersand (&), at sign(@), and number sign (#). This value must match the value specified in the NetViewDSIPARM initialization member, CNMSTYLE (see “Enable NetView to authorize TakeAction commands” on page 152).



TEMS PPI senderOptionally, specify the name of the PPI sender. The value must be a 1- through8-character, unique identifier for the receiver program. It can contain alphabeticcharacters A-Z and a-z, numeric characters 0-9, and the following special characters:dollar sign ($), percent sign (%), ampersand (&), at sign (@), and number sign (#).This name must not conflict with any NetView for z/OS domain name, as it is used inlogging the command and command response in the NetView log. If a value isspecified on this field, the Configuration Tool generates the KGLHC_PPI_SENDERenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library.



Enable Web Services SOAP ServerAccept the default value of Y. The SOAP server is required to be enabled for a hub monitoringserver. See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide for more information.

Enable Tivoli Event Integration Facility (EIF)Specify Y if you want to enable event forwarding on this hub. The default value is N. If youspecify Y, the KMS_OMTEC_INTEGRATION=YES environment variable is generated in theKDSENV member of &rhilev.&rte.RKANPARU.

See “Decision 2: Whether and how to enable event forwarding” on page 22 for moreinformation about event forwarding.






















Virtual IP Address (VIPA) typeSpecify the type of VIPA defined for the z/OS system. The default is N (None). If VIPA is in use,


specify either S (Static) or D (Dynamic). The VIPA name of the monitoring server must beresolvable through the Domain Name Server (DNS). Dynamic VIPA requires one of thefollowing communication protocols: IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE. For moreinformation about communication protocols, see “Specify communication protocols” on page51.















Maximum in-memory cache entriesThis parameter defines the maximum number of auditing records kept in short-termmemory, from 10 to 1000; it generates an AUDIT_MAX_HIST parameter in memberKDSENV of the RKANPARU library. If you do not specify a value here,AUDIT_MAX_HIST=100 is set as the default.


To specify advanced parameters for the Persistent Datastore, press F6 (PDS) to display the KDSPPDS(Specify Persistent Datastore Configuration Values) panel (see Figure 15 on page 48). These fieldsdefine default parameters for the persistent datastore, the repository for short-term historical data. Fordetailed information, see IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide.












4. If you specified Y for Enable Tivoli Event Integration Facility (EIF), the Specify Values for EventDestination panel (Figure 16 on page 50) is displayed when you press Enter on the Specify AdvancedConfiguration Values panel. To configure event forwarding, provide values for the fields on the SpecifyValues for Event Destination panel:

Event server typeSpecify the type of event server: T (the default) for Tivoli Enterprise Console, or M forOMNIbus. This field corresponds to the EventListenerType parameter in the EIF configurationmember &rhilev.&rte.RKANPARU(KMSOMTEC).

Event server locationSpecify the fully qualified host name (in IPV4 dotted-decimal format) of the primary eventserver and of up to seven backup event servers. This field corresponds to the ServerLocationparameter the KMSOMTEC member.

If you specify more than one event server, use commas to separate the host names or IPaddresses.Event server location ==> primary_server,backup_server1,backup_server2

If the EIF cannot send an event to the first server on the list, it tries the next one, and so on.

Event server portSpecify the port number on which the Tivoli Enterprise Console event server or OMNIbus EIFprobe listens for events. This field corresponds to the ServerPort parameter in theKMSOMTEC member. The default port number is 5529.

If you specify more than one event server, use commas to separate the port numbers. List theport numbers in an order corresponding to the list of event server locations.Event server port ==> primary_port,backup_port1,backup_port2

Buffer events maximum sizeSpecify the maximum size, in KB, of the adapter cache file. The cache file stores events ondisk when they cannot be sent to the event server. This field corresponds to theBufEvtMaxSize parameter in the KMSOMTEC member. The default value is 4096.

Disable Workflow Policy/Emitter Agent event forwardingIf you already have workflow policies containing emitter activities that send events to the TivoliEnterprise Console, turning on EIF event-forwarding causes duplicate events. If you specify Yin this field, you deactivate the emitter activities in your policies. The default value is N.

Policies give you more control over which events are sent, and you might want to keep somepolicies active. Moreover, policies that contain the Tivoli Enterprise Console emitter activitiesgenerally do little else. If you deactivate these activities, there is no point in running thepolicies. Therefore, you might want to delete the policies that are no longer required, instead ofdisabling them.

If this field is set to Y, the KMS_DISABLE_TEC_EMITTER=YES parameter is generated in theKDSENV member of &rhilev.&rte.RKANPARU.


Specify communication protocolsTo specify protocols for communications between the hub monitoring server and other components,complete the following procedure:


1. From the Configure the TEMS panel (Figure 10 on page 40), enter 3 to display the SpecifyCommunication Protocols panel (Figure 17 on page 51). This panel lists the communication protocolsto be used by the monitoring server. The number beside each protocol indicates its priority. Whencommunication with another component is initiated, the monitoring server tries Protocol 1 first and goesto Protocol 2 and then to Protocol 3, and so on, in case of failure.

Tips

v For the hub monitoring server, at least one of the protocols chosen must be a TCP protocol tosupport the SOAP server.

v If you have enabled EIF event forwarding, at least one of the protocols chosen must be a TCPprotocol.

v If you plan to implement long-term historical data collection, communication with the Tivoli DataWarehouse also requires a TCP protocol.

v If this monitoring server will communicate with any monitoring agents that require SNA,SNA.PIPE must be one of the protocols chosen, but it does not have to be Protocol 1.Examples of such monitoring agents include OMEGAMON XE on z/OS (for the EPILOG facilityof the OMEGAMON II component) and OMEGAMON XE for Messaging on z/OS (for the 3270interface component). See the product-specific configuration guides for further informationabout SNA requirements.









SNA.PIPEUses the SNA Advanced Program-To-Program Communications (APPC). This protocol is required ifthe monitoring server will communicate with any monitoring agents that require SNA, but it doesnot have to be Protocol 1.




Figure 18 on page 52 shows the Specify IP.PIPE Communication Protocol panel, where you specifyvalues for the IP.PIPE, IP6.PIPE, IP.SPIPE, and IP6.SPIPE protocols.


Network address (Hostname)The TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where the hubmonitoring server is installed. To obtain the host name and IP address, enter TSO HOMETESTat the command line.






Network interface listOne or more network interfaces for the monitoring server to use. If the z/OS image hasmore than one TCP/IP interface or network adapter, you can use this parameter to direct themonitoring server to connect to a specific TCP/IP local interface.

If you provide a value for this parameter, the Configuration Tool generates theKDEB_INTERFACELIST environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library.

To set a network interface list for the monitoring server, supply one of the following values:

– The host name or IP address of the preferred interface.

– A list of host names or IP addresses, in descending order of preference. Use a blankspace to separate the entries.

– An asterisk (*) to prefer the interface associated with the default host name for the z/OSimage. To display this value, enter TSO HOMETEST at the command line.

– An exclamation point followed by an asterisk (!*) to use only the interface associatedwith the default host name for the z/OS image.

– An exclamation point followed by a host name or IP address (!hostname) to use only theinterface associated with hostname.

– A minus sign followed by a host name or IP address (-hostname) to use any interfaceexcept the one associated with hostname.


Important

– If you set the value of Network interface list to !* or !hostname, you must specifythe same value for every component and product configured in all runtimeenvironments on the same z/OS image.


Port numberSpecify the well-known port for the hub monitoring server, for each of the selected IP*.*PIPEprotocols. The port numbers specified here are stored in the KDE_TRANSPORTenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library. Thedefault port numbers are 1918 for nonsecure IP protocols and 3660 for secure IP protocols.If you specified a different TCP/IP port number for the runtime environment, the number youspecified is shown as the default for nonsecure IP protocols.

Make sure that the hub monitoring server well-known port is not already on the TCP/IPreserved port list. Also, the hub well-known port is the basis for an algorithm that assignsport numbers to the components configured to report to the hub. Make sure that thealgorithm will not result in attempts to reserve already-reserved ports for those components.See "Port number assignments" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

HTTP server port numberThe HTTP server port is used for communications with the SOAP server. Accept the defaultvalue of 1920. If Port 1920 is in use when the monitoring server is started, another port isassigned.

Access TEMS list via SOAP Server?Specify Y to create the initial KSHXHUBS member required for SOAP server operation. TheKSHXHUBS member is stored in the &rhilev.&rte.RKANPARU library.

The KSHXHUBS member contains the list of hub monitoring servers with which the SOAPserver communicates, and the corresponding user access list if access has been secured.The TEMS list in the KSHXHUBS member is an aliasing mechanism, equivalent to thekshxhubs.xml file on distributed platforms.

If the initial KSHXHUBS member has already been created and no changes are required tothe SOAP server values, set this field to N.






When you press Enter after providing the IP*.*PIPE configuration values, you are presented withone of the following panels:

– If you specified Y for Address translation, the Specify IP.PIPE Partition References panel(Figure 19 on page 54) is displayed.

The name of the monitoring server, its partition name (that is, its location or namespace relativeto the firewall), and its partition address (the IP address assigned to the monitoring server in thespecified partition) are displayed at the top of the Specify IP.PIPE Partition References panel.Use the fields of this panel to specify partition references (the values required to supportcommunication across a firewall using address translation rather than EPS). If more than onefirewall is used, specify a partition reference for each firewall.


AddressSupply the IP address assigned to the monitoring server from a location on the otherside of the firewall.

To add a partition reference, specify the partition name and the address used in that partition tocommunicate with the monitoring server, and press Enter. To modify an existing partitionreference, type over an entry and press Enter. To delete a reference, type D in the Action fieldand press Enter. Modifications resulting in duplicate entries are ignored.

The values provided on this panel are saved as the KDC_PARTITIONFILE environment variablein the KDSENV member of the &rhilev.&rte.RKANPARU library. KDC_PARTITIONFILE points to amember, KDCPART, created in the &rhilev.&rte.RKANPARU library.

– If you specified N for Address translation, the Specify TEMS KSHXHUBS Values panel isdisplayed (Figure 20 on page 55). Use this panel to begin a list of hub monitoring servers toconnect with the SOAP server. The values you specified in earlier configuration panels aredisplayed as default values.

Hub TEMS SOAP Server values for RTEnameAccept the default value, which is the name of the runtime environment where themonitoring server is being configured.

TEMS nameAccept the default value, which is the TEMS name (CMS_NODEID) you specified whenyou defined the runtime environment.

TCP hostnameAccept the default, which is the host name specified on the Specify IP.PIPECommunication Protocol panel (Figure 18 on page 52).

TCP port numberAccept the default, which is the port number specified on the Specify IP.PIPECommunication Protocol panel (Figure 18 on page 52).

SNA network IDIf you selected SNA as Protocol 1 (the highest-priority protocol), supply the identifier ofyour VTAM network. You specified this value while defining the runtime environment. Youcan also obtain this value from the NETID parameter in the VTAMLST startup memberATCSTRnn. This field is required only if SNA is Protocol 1.


SNA global location broker applidIf you selected SNA as Protocol 1, supply the VTAM applid for the global location broker.This field is required only if SNA is Protocol 1.

SNA LU6.2 logmodeIf you selected SNA as Protocol 1, supply the name of the default LU6.2 logmode entryrequired by the hub monitoring server. You specified this value while defining the runtimeenvironment. This field is required only if SNA is Protocol 1.

Alias nameAccept the default, which is the TEMS name (CMS_NODEID value). The alias nameidentifies the hub monitoring server to the SOAP server. The value is case-sensitive.

When you press Enter, the SOAP server KSHXHUBS List panel (Figure 21 on page 56) isdisplayed, with the hub monitoring server shown on the list.

This panel lists the hub monitoring servers that are eligible for SOAP server access. The list ismaintained in the KSHXHUBS member of the &rhilev.&rte.RKANPARU library.

Tips

- You can specify non-local hubs if desired. To do so, enter A (Add TEMS) in the Actionfield to the left of any hub in the list. Then, on the Specify TEMS KSHXHUBS Valuespanel, provide the TEMS name, TCP hostname (network address), and Alias name forthe non-local hub.

- Do not edit the KSHXHUBS member directly. Its XML tags and values require a specificformat and are case-sensitive. If you want to change the contents of the KSHXHUBSmember, do so in the Configuration Tool.

If you exit the SOAP server KSHXHUBS List panel without securing user access, the SOAPserver honors requests from any user ID that passes logon validation. The value shown in theTEMS secured field indicates whether user access to the SOAP server is secured (Y) orunsecured (N). For an explanation of SOAP server security, see the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.

If you want to limit user access to the SOAP server, follow this procedure:

a. On the SOAP server KSHXHUBS List panel, enter S (Secure TEMS) in the Action field to theleft of the item for the hub you just added to the list.

The Specify TEMS KSHXHUBS Values panel (Figure 20 on page 55) is displayed, withAction: Secure at the top and with two fields at the bottom for specifying the first user ID towhich access is to be granted.

b. On the Specify TEMS KSHXHUBS Values panel (Figure 20 on page 55), specify the first userID to have Query (read) access and Update (write) access. You can specify a user ID forQuery access without specifying one for Update access, but if you specify a user ID forUpdate access, you must also specify a user ID for Query access.

c. If you want only one user ID to have access, press F3 to return to the SOAP serverKSHXHUBS List panel.

If you want to specify more user IDs, press Enter. The SOAP server KSHXHUBS SecurityAccess List panel is displayed (Figure 22 on page 57).

d. Enter A (Add user) in the Action field to the left of the first user ID. The Specify TEMSKSHXHUBS User Access List panel is displayed (Figure 23 on page 57).

e. Specify a user ID and indicate whether to grant it Query access and Update access.

f. Press Enter to return to the SOAP server KSHXHUBS Security Access List panel.

g. Continue adding user IDs until you have added all the user IDs to which you want to grantSOAP server access.


h. If you want to grant a user ID the same level of access to all hubs on the SOAP serverKSHXHUBS List, enter I (Install user into all monitored TEMS) to the left of the user ID onthe SOAP server KSHXHUBS Security Access List panel.

Caution: This action (I) has the immediate effect of securing every hub on the list and ofgranting access only to the user ID selected. Be sure you want this result before specifyingthe I action.

i. Press F3 (Back) until you return to the SOAP server KSHXHUBS List panel (Figure 21 onpage 56).

If you want to disable SOAP server security for a hub, specify G (Grant global security access) inthe Action field for that hub on the SOAP server KSHXHUBS List panel. This action removes alluser IDs from the user access list and thus enables access for all user IDs that pass logonvalidation.

Press F3 (Back) to return to the communication protocol configuration panels.



v SNA.PIPE

Figure 33 on page 74 shows the Specify SNA Communication Protocol panel. Supply values forthese fields.


Tip: Enter README APP on the command line for more information on how the ConfigurationTool processes VTAM applids. If system variable support is enabled, enter README SYS onthe command line for more information on how the Configuration Tool processes VTAMapplids using z/OS system symbols. Press F6 (Applids) for a list of the VTAM major nodeand applid values.



Create runtime members and configure the persistent datastoreFollow the instructions in “Create the runtime members” on page 61 to create the runtime members for thehub monitoring server, and then follow the instructions in “Configure the persistent datastore” on page 61to configure the persistent datastore and create its runtime members.


Step 2. Configure monitoring agents in the runtime environmentIn this step, you configure monitoring agents in the same runtime environment with the hub monitoringserver.



COMPONENT TITLE



Be sure to select the option Register with local TEMS. This option produces a job that enables themonitoring agent to transmit data to the monitoring server.






5. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), type C (Configure) in the Actionfield to the left of the name of the runtime environment where you configured the hub monitoring serverand the first monitoring agent.

6. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. Youdo not have to reconfigure the hub monitoring server to add a monitoring agent to the runtimeenvironment.












Chapter 5. Configuring a remote monitoring server on z/OS toreport to a distributed hub

This chapter explains how to configure a remote monitoring server on a z/OS image to report to a hubmonitoring server on a distributed system.

The configuration shown in Figure 35 depicts a hub monitoring server on Windows, Linux, or UNIX, with aremote monitoring server on z/OS configured to report to the hub. Several monitoring agents areconfigured in the same runtime environment with the remote monitoring server. The data collected bythose monitoring agents flows through their local monitoring server to the hub.

This configuration makes it possible to locate the hub monitoring server and the portal server on the samedistributed system, and can be advantageous in an environment where most monitoring agents are ondistributed systems.

PARMGEN methodThe procedure in this section assumes that you have already configured a hub monitoring server on adistributed system (see IBM Tivoli Monitoring: Installation and Setup Guide for instructions).

Complete these steps to configure a remote monitoring server on z/OS to report to a hub on a distributedsystem.

Step 1. Create the runtime environment and set the configurationparameters for the remote monitoring serverFollow the steps in the "Configuring products with the PARMGEN method" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide to create a runtime environment. In "Step 2. Set up your PARMGEN configuration profile," refer tothe IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common ParameterReference for information about the parameters in the configuration profile. The configuration profile is the&rhilev.&rte.WCONFIG(&rte) member.

Figure 35. Remote monitoring server on z/OS reporting to a hub on a distributed system


Tips

v The parameters shown in this section are specific to the remote monitoring server but are not theonly parameters for which you must either accept or override the default values in theconfiguration profile for the runtime environment. After you set the parameters shown here, besure to go through the entire configuration profile to make sure the parameter values are correctfor the configuration you want.

v Be sure to uncomment any parameters that are needed for your configuration but are commentedout by default. For example, the configuration profile for a runtime environment containing aremote monitoring server that will use the IP.PIPE protocol to communicate with the hub requiresthe KDS_HUB_TCP_PIPE_PORT_NUM parameter, which is commented out by default. For sucha configuration, you must uncomment this parameter and insert the port number between thequotation marks for the parameter value.

Before:**KDS_HUB_TCP_PIPE_PORT_NUM ""

After:KDS_HUB_TCP_PIPE_PORT_NUM "1918"

In the configuration profile for the runtime environment, set the following parameter values for the remotemonitoring server:** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:RTE_TEMS_CONFIGURED_FLAG YRTE_TEMS_NAME_NODEID "remote_rte_name:CMS"



KDS_TEMS_COMM_PROTOCOLn parameterAt least one of the communication protocols must be the same as a protocol selected for the hub.For information about the communication protocols, see "Decision 5: How to set upcommunications between components" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.


KDS_HUB_TCP_HOST parameterThis is the TCP/IP host name (in IPV4 dotted-decimal format) of the distributed system where thehub monitoring server is installed.


Many other KDS_* parameters are needed for the remote monitoring server configuration. See the IBMTivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference forinformation about them.

Configuring the monitoring server to support encryption/decryptionTo activate ICSF encryption/decryption within your newly configured remote monitoring server using thePARMGEN configuration method, locate these lines in the configuration profile for the runtime environmentof the monitoring server::


** GBL_DSN_CSF_* ICSF system libraries:GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"** TMS KAES256 password encryption key:**KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"










Step 2. Set configuration parameters for the monitoring agents in thesame runtime environmentIn the same configuration profile, set parameter values for each of the products you want to include in theruntime environment of the remote monitoring server. Follow the instructions in each product's Planningand Configuration Guide, and use the information in each product's Parameter Reference.


Step 3. (Optional) Replicate the remote runtime environmentNow you can replicate to other z/OS systems the configured runtime environment that contains the remotemonitoring server and its monitoring agents. Replicating the configured runtime environment is an easyway to ensure that all your remote monitoring servers are configured to report to the high-availability hub.Follow the instructions in the "Using the PARMGEN method to replicate a configured environment" chapterof the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide.

Chapter 5. Configuring a remote monitoring server on z/OS to report to a distributed hub 101

Configuration Tool (ICAT) methodThe procedure in this section assumes that you have already configured a hub monitoring server on adistributed system (see IBM Tivoli Monitoring: Installation and Setup Guide) and that you have completedSteps 1, 2, and 3 in the "Configuring products with the Configuration Tool" chapter of the IBM TivoliOMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

Tips

v When you select a product on the Product Selection Menu (Figure 5 on page 33), select one ofthe monitoring agents, not IBM Tivoli Management Services on z/OS, if you want to configure botha monitoring server and monitoring agents in the runtime environment. If you select IBM TivoliManagement Services on z/OS, you can only configure a stand-alone monitoring server in its ownruntime environment, without any monitoring agents.

v To configure a remote monitoring server on z/OS to report to a hub monitoring server in a differentCSI, you can follow the same basic procedure described in this chapter.

Configuration stepsComplete the following steps in order:

__ “Step 1. Configure the remote monitoring server”

__ “Step 2. Configure monitoring agents in the runtime environment” on page 115


Step 1. Configure the remote monitoring serverTo configure a remote monitoring server, perform the following tasks in the order listed:


2. “Create a logmode.”






1. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), enter C (Configure) next to theruntime environment in which you want to configure the monitoring server.

The Product Component Selection Menu is displayed (Figure 28 on page 64).




If this monitoring server will not communicate with any monitoring agents that require SNA, you can skip to“Specify configuration values” on page 103.




The Create LU6.2 Logmode panel is displayed (Figure 29 on page 65). Use this panel to specify thename of the LU6.2 logmode and logmode table required by the monitoring server.












Specify configuration valuesIn this step you indicate that the monitoring server you are configuring is a remote monitoring server. Youalso specify the name of the started task for this monitoring server and its security settings. Securityvalidation of users is handled by hub monitoring servers only. Do not attempt to enable security validationon a remote monitoring server.

1. From the Configure the TEMS menu (Figure 10 on page 40), enter 2 to display the SpecifyConfiguration Values panel (Figure 11 on page 41).

2. Provide values in the following fields:

Started taskThe name of the monitoring server started task JCL procedure. Make a note of the name,because later you will have to copy this started task procedure to your system procedurelibrary. The default is CANSDSST.

Tip: If you have two or more runtime environments on the same z/OS image, make sure thatthe name of each started task is unique.

Type (Hub or Remote)Specify REMOTE as the monitoring server type.

Hub TEMS typeLeave this field blank.


Tip: If you come back to this panel later, this field will not be displayed, because it appliesonly to a hub monitoring server.

Security settings

Validate security?This setting determines whether the hub monitoring server validates the user IDs andpasswords of users signing on to the Tivoli Enterprise Portal. If your site plans toactivate Web Services (that is, the SOAP server) for the remote monitoring server youare defining, ensure you set this parameter to Y; see the description of the EnableWeb Services SOAP Server parameter later in this step. Otherwise, leave this valueset to N.


Note: The encryption method specified for the remote and hub monitoring serversmust match that of the Tivoli Enterprise Portal Server. If you specify that ICSF is notinstalled on this z/OS system (N), you must add the line USE_EGG1_FLAG=1 (orUSE_EGG1_FLAG=Y) to the KFWENV environment file of the Tivoli Enterprise PortalServer (see “(If applicable) Edit the portal server environment file” on page 123).



TMS encryption keySpecify a unique, 32-byte password encryption key. The value is case-sensitive. Besure to record the value you use for the key. You must use the same key during theinstallation of any monitoring agents that communicate with this monitoring server.


Important: You must ensure your site enabled Tivoli Management Services on z/OSpassword encryption via the Integrated Cryptographic Service Facility (ICSF) when youcomplete these security settings. This is because whenever the current remotemonitoring server runs policies that invoke either TADDM_Init or TADDM_Eventactivities, the password (which is stored within the activity definition in encrypted form)must be deciphered before the request is sent to Tivoli Application DependencyDiscovery Manager.

The encryption methodology must be uniform across the Tivoli Enterprise Portal Serverand all monitoring servers, including the hub monitoring server.


Encryption key tips



v For security reasons, the encryption key value is not displayed if you return tothe Specify Configuration Values panel after you finish configuring themonitoring server. If you reconfigure the monitoring server by changing otherparameter values on the configuration panels, the resulting DS#3ssss job doesnot create a key file.




Program to Program Interface (PPI) information(Optional) Specify the PPI values that enable forwarding of Take Action commands to NetViewfor z/OS for authorization and execution. If you enable forwarding, you must also enableNetView to receive and authorize the commands (see “Enable NetView to authorize TakeAction commands” on page 152).




The value must be a 1- through 8-character, unique identifier for the receiver program.It can contain alphabetic characters A-Z and a-z, numeric characters 0-9, and thefollowing special characters: dollar sign ($), percent sign (%), ampersand (&), at sign(@), and number sign (#). This value must match the value specified in the NetViewDSIPARM initialization member, CNMSTYLE (see “Enable NetView to authorize TakeAction commands” on page 152).



TEMS PPI senderOptionally, specify the name of the PPI sender. The value must be a 1- through8-character unique identifier for the receiver program. It can contain alphabeticcharacters A-Z and a-z, numeric characters 0-9, and the following special characters:dollar sign ($), percent sign (%), ampersand (&), at sign (@), and number sign (#).This name must not conflict with any NetView for z/OS domain name, as it is used inlogging the command and command response in the NetView log. If a value isspecified on this field, the Configuration Tool generates the KGLHC_PPI_SENDERenvironment variable in the KDSENV member of the &rhilev.&rte.RKANPARU library.



Enable Web Services SOAP ServerTo enable Web Services (that is, the SOAP server) for this remote monitoring server, ensurethis parameter is set to Y.

Enabling the SOAP server means that a policy running on this remote monitoring server cannow send new SOAP-based on-demand and email activities (supported as of version 6.2.3) toan agent connected to this remote monitoring server. The monitoring server's SOAP servermust be started if you include either on-demand or email activities within the workflow of oneor more policies that will run on that monitoring server.

In addition, this architecture is more efficient than having all remote monitoring servers sendtheir SOAP requests to the hub. It also means that a policy that is running on this remotemonitoring server can continue to process SOAP requests even when the hub or theconnection to the hub becomes unavailable. See the IBM Tivoli OMEGAMON XE and IBMTivoli Management Services on z/OS: Common Planning and Configuration Guide for moreinformation.

Turning on this parameter causes the HTTP server port number field to appear on panelKDS62PPA (Specify Communication Protocols; see Figure 38 on page 111). The HTTP serverport number defaults to the HTTP port of the hub monitoring server that this remote monitoringserver connects to. You can choose to override the HTTP port number on the IP.PIPE andIP.UDP panels.























Virtual IP Address (VIPA) typeSpecify the type of VIPA defined for the z/OS system. The default is N (None). If VIPA is in use,specify either S (Static) or D (Dynamic). The VIPA name of the monitoring server must beresolvable through the Domain Name Server (DNS). Dynamic VIPA requires one of thefollowing communication protocols: IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE. For moreinformation about communication protocols, see “Specify communication protocols” on page111.













Persistent datastore parametersThese fields define default parameters for the persistent datastore, the repository for short-termhistorical data. For detailed information, see the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

Maintenance procedure prefixThis prefix is applied to the procedures that perform maintenance when the persistentdatastore is full. Specify the same prefix for all products in all runtime environments.The default is KPDPROC.

This parameter is required even if you intend to configure historical data collection atthe location of the monitoring agents rather than at the location of the monitoringserver.

Datastore file high-level prefixSpecify the high-level qualifier to use when allocating persistent datastore files in thisruntime environment. The default is &rhilev.&rte.

This parameter is required even if you intend to configure historical data collection atthe location of the monitoring agents rather than at the location of the monitoringserver.

VolumeSpecify the default DASD volume to use when allocating persistent datastore files inthis runtime environment. The default is the volume specified for the runtimeenvironment.

Unit Specify the default DASD unit to use when allocating persistent datastore files in thisruntime environment. Valid unit types are 3380 and 3390. The default is the unit typespecified for the runtime environment.

StorclasSpecify the default SMS storage class to use when allocating persistent datastore filesin this runtime environment. If your site does not require the SMS STORCLASparameter, you can leave this field blank.

MgmtclasSpecify the default SMS management class to use when allocating persistentdatastore files in this runtime environment. If your site does not require the SMSMGMTCLAS parameter, you can leave this field blank.


4. Press Enter to accept the values.

The Communication Selection panel is displayed. This panel lists hub monitoring servers configured inother runtime environments accessible to the Configuration Tool. If any hubs are listed, they are z/OS


hubs. For the configuration described in this chapter, the hub is on a distributed system and is notfound on the list.

5. On the Communication Selection panel, press F5 (Advanced) to navigate to the Specify Configuration -Hub Values for Remote TEMS panel.

6. On the Specify Configuration - Hub Values for Remote TEMS panel, enter the values for the hubmonitoring server with which you want the remote monitoring server to connect. If you made a note ofthese values during configuration of the hub monitoring server, find it now. Otherwise, you can find thevalues in one of the following locations:

v On Windows systems, launch the Manage Tivoli Monitoring Services application by selecting Start >IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. Right-click Tivoli EnterpriseMonitoring Server and select Browse Settings.

v On Linux and UNIX systems, look in the KBBENV file located in the itm_installdir/tables/tems_name subdirectory.

Hub TEMS nameThe TEMS name (node ID) of the hub monitoring server. The TEMS name is case-sensitive onall platforms.

The TEMS name is generally not the same as the host name. The default TEMS name for thehub on distributed systems is HUB_hostname. For example, for host ITMSERV61, the defaultTEMS name is HUB_ITMSERV61.

KCIPCMSS -------- COMMUNICATION SELECTION PANEL FOR SHARING2 Row 1 to 1 of 1

Select the hub (primary TEMS) to connect to this remote TEMS.

The following lists eligible Tivoli Enterprise Monitoring Servers(TEMS) that you have configured. Enter S next to the TEMS to connectto this remote. To manually enter the TEMS information, press F5.

_ HUB SHARING1 Sharing runtime environment for hub and agents

F1=Help F3=Back F5=Advanced F7=Up F8=Down

Figure 36. Communication Selection panel

KDS62PP2 --- SPECIFY CONFIGURATION - HUB VALUES FOR REMOTE TEMS ---------------

Hub TEMS name (Case sensitive) ==>

Complete this section if the Remote TEMS is connecting to its Hub TEMSusing SNA. Enter the applicable VTAM values of its Hub TEMS:

Global location broker applid of Hub ==>Network ID of Hub ==>

Complete this section if the Remote TEMS is connecting to its Hub TEMSusing IP. Enter the applicable network address and respective port number(s):

Network address (Hostname of Hub):==>

IP.PIPE port number ==> (Non-secure NCS RPC)IP6.PIPE port number ==> (IP.PIPE for IPV6)IP.SPIPE port number ==> (Secure IP.PIPE)IP6.SPIPE port number ==> (Secure IP.PIPE for IPV6)IP.UDP port number ==> (Non-secure NCS RPC)IP6.UDP port number ==> (IP.UDP for IPV6)


Figure 37. Specify Configuration - Hub Values for Remote TEMS panel


The TEMS name is stored as the value of the CMS_NODEID parameter in the settings for thehub monitoring server. You can find this value on distributed systems by browsing themonitoring server settings in Manage Tivoli Monitoring Services on Windows systems, or byexamining the KBBENV file for the monitoring server on Linux or UNIX systems.

Global location broker applid of hubThis field does not apply to a hub on a distributed system. Leave it blank.

Network ID of hubThis field does not apply to a hub on a distributed system. Leave it blank.

Network address (Hostname of Hub)The fully qualified TCP/IP host name (in IPV4 dotted-decimal format) of the system on whichthe hub monitoring server is installed.

Port numbersSupply the hub listening port number for each protocol selected during configuration of thehub.

Important: If you are configuring more than one remote monitoring server in this z/OS image,the hub to which each remote monitoring server reports must have a unique port number.Otherwise, connectivity problems might occur. For more information about port numberallocation, see "Port number assignments" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide.

7. Press Enter until you return to the Specify Configuration Values panel.

The TEMS name of the hub you specified for connection with the remote monitoring server isdisplayed in the Hub TEMS name field.


Specify communication protocolsTo specify protocols for communications between the remote monitoring server and other components,complete the following procedure:

1. From the Configure the TEMS panel (Figure 10 on page 40), enter 3 to display the SpecifyCommunication Protocols panel.

This panel lists the communication protocols to be used by the monitoring server. The number besideeach protocol indicates its priority. When communication with another component is initiated, themonitoring server tries Protocol 1 first and goes to Protocol 2 and then to Protocol 3, and so on, incase of failure.

KDS62PPA -------------- SPECIFY COMMUNICATION PROTOCOLS -----------------------

Specify the communication protocols in priority sequence forTEMS rte:CMS.

IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> 2 (Non-secure NCS RPC)IP6.PIPE ==> (IP.PIPE for IPV6)IP6.UDP ==> (IP.UDP for IPV6)IP.SPIPE ==> (Secure IP.PIPE)IP6.SPIPE ==> (Secure IP.PIPE for IPV6)SNA.PIPE ==> 3 (Non-secure NCS RPC)

Note: SNA.PIPE is required under certain conditions. Press F1=Help.* This Remote TEMS reports to a Hub that uses IP.PIPE to connect.

Ensure that this Remote TEMS also specifies the IP.PIPE protocol.* The protocol(s) in use by the Hub TEMS are:

-SNA -Unsecured IP.PIPE -Unsecured IP.UDP


Figure 38. Specify Communication Protocols panel for a remote monitoring server


Tips

v If the hub with which the remote monitoring server will connect uses a piped protocol (IP.PIPE,IP6.PIPE, IP.SPIPE, or IP6.SPIPE), you must also select that protocol for the remotemonitoring server.

v If you plan to implement long-term historical data collection, communication with the Tivoli DataWarehouse requires a TCP protocol.

v If this monitoring server will communicate with any monitoring agents that require SNA,SNA.PIPE must be one of the protocols chosen, but it does not have to be Protocol 1.Examples of such monitoring agents include OMEGAMON XE on z/OS (for the EPILOG facilityof the OMEGAMON II component) and OMEGAMON XE for Messaging on z/OS (for the 3270interface component). See the product-specific configuration guides for further informationabout SNA requirements.









SNA.PIPEUses the SNA Advanced Program-To-Program Communications (APPC). This protocol is required ifthe monitoring server will communicate with any monitoring agents that require SNA, but it doesnot have to be Protocol 1.




Figure 39 on page 113 shows the Specify IP.PIPE Communication Protocol panel, where you specifyvalues for the IP.PIPE, IP6.PIPE, IP.SPIPE, and IP6.SPIPE protocols.


The values you specified for the runtime environment are displayed as default values for themonitoring server. You can accept the defaults or change them.

Network address (Hostname)The TCP/IP host name (the IPV4 dotted-decimal IP address) of the z/OS system where theremote monitoring server is installed. To obtain the host name and IP address, enter TSOHOMETEST at the command line.






Network interface listOne or more network interfaces for the monitoring server to use. If the z/OS image hasmore than one TCP/IP interface or network adapter, you can use this parameter to direct themonitoring server to connect to a specific TCP/IP local interface.

If you provide a value for this parameter, the Configuration Tool generates theKDEB_INTERFACELIST environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library.

KDS62PPD ----------- SPECIFY IP.PIPE COMMUNICATION PROTOCOL -------

Specify IP.PIPE communication values.

* Network address (Hostname):==> hostname

Started task ==> * (Recommended default = *)Network interface list: (If applicable)

==>

Port number of Hub ==> (IP.PIPE)Port number of Hub ==> (IP.PIPE for IPV6)Port number of Hub ==> (Secure IP.PIPE)Port number of Hub ==> (Secure IP.PIPE for IPV6)

Address translation ==> N (Y, N)Partition name ==>



Figure 39. Specify IP.PIPE Communication Protocol panel for a remote monitoring server


To set a network interface list for the monitoring server, supply one of the following values:

– The host name or IP address of the preferred interface.

– A list of host names or IP addresses, in descending order of preference. Use a blankspace to separate the entries.

– An asterisk (*) to prefer the interface associated with the default host name for the z/OSimage. To display this value, enter TSO HOMETEST at the command line.

– An exclamation point followed by an asterisk (!*) to use only the interface associatedwith the default host name for the z/OS image.

– An exclamation point followed by a host name or IP address (!hostname) to use only theinterface associated with hostname.

– A minus sign followed by a host name or IP address (-hostname) to use any interfaceexcept the one associated with hostname.

Important

– If you set the value of Network interface list to !* or !hostname, you must specifythe same value for every component and product configured in all runtimeenvironments on the same z/OS image.


Hub port numbersFor each of the selected IP*.*PIPE protocols, these fields specify the well-known port for thehub to which the remote monitoring server will connect. These fields are read-only. If youwant to change the hub port number specified in the remote monitoring server configuration,return to the Specify Configuration - Hub Values for Remote TEMS panel (Figure 37 onpage 110).

Address translationBy default, Ephemeral Pipe Support (EPS) is enabled to allow IP.PIPE connections to crossa network address-translating firewall. This feature obviates the requirement for a brokerpartition file (KDC_PARTITIONFILE=KDCPART). If you specifically want to disable EPS, specify Yfor Address translation.

Partition nameIf you specified Y for Address translation, supply the partition name (label) that identifiesthe location of the monitoring server relative to the firewall(s) used for address translation.



When you press Enter after providing the IP*.*PIPE configuration values, if you specified Y forAddress translation, the Specify IP.PIPE Partition References panel (Figure 19 on page 54) isdisplayed. The name of the monitoring server, its partition name (that is, its location or namespacerelative to the firewall), and its partition address (the IP address assigned to the monitoring server inthe specified partition) are displayed at the top of the Specify IP.PIPE Partition References panel.Use the fields of this panel to specify partition references (the values required to supportcommunication across a firewall using address translation rather than EPS). If more than onefirewall is used, specify a partition reference for each firewall.



AddressSupply the IP address assigned to the monitoring server from a location on the other side ofthe firewall.

To add a partition reference, specify the partition name and the address used in that partition tocommunicate with the monitoring server, and press Enter. To modify an existing partition reference,type over an entry and press Enter. To delete a reference, type D in the Action field and pressEnter. Modifications resulting in duplicate entries are ignored.

The values provided on this panel are saved as the KDC_PARTITIONFILE environment variable inthe KDSENV member of the &rhilev.&rte.RKANPARU library. KDC_PARTITIONFILE points to amember, KDCPART, created in the &rhilev.&rte.RKANPARU library.



v SNA.PIPE

Figure 33 on page 74 shows the Specify SNA Communication Protocol panel. Supply values forthese fields.


Tip: Enter README APP on the command line for more information on how the ConfigurationTool processes VTAM applids. If system variable support is enabled, enter README SYS onthe command line for more information on how the Configuration Tool processes VTAMapplids using z/OS system symbols. Press F6 (Applids) for a list of the VTAM major nodeand applid values.



Create runtime members and configure the persistent datastoreFollow the instructions in “Create the runtime members” on page 61 to create the runtime members for theremote monitoring server, and then follow the instructions in “Configure the persistent datastore” on page61 to configure the persistent datastore and create its runtime members.


Step 2. Configure monitoring agents in the runtime environmentIn this step, you configure monitoring agents in the same runtime environment with the remote monitoringserver.



COMPONENT TITLE



Be sure to select the option Register with local TEMS. This option produces a job that enables themonitoring agent to transmit data to the remote monitoring server.






5. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), type C (Configure) in the Actionfield to the left of the name of the runtime environment where you configured the remote monitoringserver and the first monitoring agent.

6. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. Youdo not have to reconfigure the hub monitoring server to add a monitoring agent to the runtimeenvironment.











Part 3. Post-configuration procedures

Some important post-configuration procedures are necessary before the configured monitoring server isready to function in a monitoring enterprise. The chapters in this part of Configuring the Tivoli EnterpriseMonitoring Server on z/OS give instructions for those procedures:

v Chapter 6, “Completing the configuration,” on page 119 outside the configuration software.

v Chapter 7, “Adding application support to a monitoring server on z/OS,” on page 129 for the monitoringagents that send it data.

v Chapter 8, “Configuring security on a monitoring server on z/OS,” on page 143.

Navigation tipsAll the chapters in Part 3 contain necessary information. Follow this path:

1. Complete the post-configuration tasks in Chapter 6, “Completing the configuration,” on page 119,in Chapter 7, “Adding application support to a monitoring server on z/OS,” on page 129, and inyour monitoring agent configuration guides.

2. Go to the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide for instructions on validating your configuration.


4. Go to Part 4 of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide for instructions on replicating the configuredenvironment to other LPARs.



Chapter 6. Completing the configuration

You must take a number of steps outside the configuration software to complete the configuration ofmonitoring servers and monitoring agents. The steps you have left to complete depend on the steps youhave already taken, the configuration options you have chosen, and what you intend to monitor.

Typical tasks of completing the configuration of a monitoring serverThe following tasks are typically required for completing the configuration of a monitoring server.

1. (If IP domain name resolution is not fully configured): “(If applicable) Add support for the SYSTCPDDDNAME in the monitoring server started task.”

2. (If you want to enable NetView authorization of Take Action commands): “(If applicable) Add theNetView CNMLINK data set to the monitoring server started task” on page 120.

3. “Copy the started task procedures to your procedure library” on page 120.

4. “Copy the VTAM definitions to your system VTAMLST” on page 121.

5. “Vary the VTAM major node active” on page 121.

6. “APF-authorize the runtime load libraries” on page 121.

7. (If you have configured more than one hub monitoring server on z/OS) “(If applicable) Refresh theKSHXHUBS member in other runtime environments” on page 121.

8. “Verify that you can start and stop the monitoring server” on page 121.

9. (If you want to enable NetView authorization of Take Action commands): “(If applicable) EnableNetView to authorize Take Action commands” on page 122.

10. If ICSF is not installed on the system: “(If applicable) Edit the portal server environment file” on page123.

11. If you intend to collect historical data:

v “Enable historical data store maintenance (optional)” on page 123

v “Enable historical data collection (optional)” on page 124

12. If you want to enable event forwarding to Tivoli Enterprise Console or OMNIbus: “Enable eventforwarding (optional)” on page 124

If you are using the Configuration Tool (ICAT), you can generate a list of required post-configuration tasksfor a specific configured runtime environment. For more information, see the "Completing theconfiguration" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide and see the configuration documentation for your monitoringagents.

(If applicable) Add support for the SYSTCPD DDNAME in themonitoring server started taskIf your monitoring servers are configured to use any of the TCP/IP communication protocols forconnection, but IP domain name resolution is not fully configured, you must specify the SYSTCPDDDNAME in the CANSDSST started task for each monitoring server.

The configuration software generates the CANSDSST started task in the &rhilev.&rte.RKANSAMU data setwith some lines commented out. To add support for the SYSTCPD DDNAME, uncomment the two lines atthe end of the section of CANSDSST shown here, and customize the TCPDATA library name for yourenvironment.//*SYSTCPD explicitly identifies which dataset to use to obtain//*the parameters defined by TCPIP.DATA when no GLOBALTCPIPDATA//*statement is configured. Refer to the IP Configuration Guide//*for information on the TCPIP.DATA search order. The dataset//*can be any sequential dataset or a member of a partitioned


//*dataset. TCPIP.SEZAINST(TCPDATA) is the default sample file.//*TCPIVP.TCPPARMS(TCPDATA) is another sample and is created as//*part of the Installation Verification Program for TCP/IP.//*Note: Uncomment out this DDNAME and point to appropriate//* TCPDATA library name supported at your site if domain//* name resolution is not fully configured.//*SYSTCPD DD DISP=SHR,//*DSN=TCPIP.SEZAINST(TCPDATA)

(If applicable) Add the NetView CNMLINK data set to the monitoringserver started taskTo connect to NetView, the monitoring server must reference the NetView CNMLINK data set. If you wantto enable NetView authorization of Take Action commands, concatenate the CNMLINK data set to theRKANMODL statement in the CANSDSST started task for each monitoring server. You can find theCANSDSST started task procedure in the &rhilev.&rte.RKANSAMU data set.

To provide the location, uncomment the CNMLINK DD card in CANSDSST and specify the NetViewCNMLINK data set. For example:

000350 //RKANMODL DD DISP=SHR,000351 // DSN= &RHILEV.&SYS.RKANMODU000352 // DD DISP=SHR,000353 // DSN= &RHILEV.&SYS.RKANMODUL000354 // DD DISP=SHR,000355 // DSN= &RHILEV.&SYS.RKANMOD000356 //******************************************************************000357 //* RKANMODL DD: CNMLINK000358 //******************************************************************000359 //* Uncomment this DD card and specify the location of the CNMLINK000360 //* load module for NetView for z/OS. This library is required for the000361 //* "Forward Take Action commands to NetView for z/OS" support which000362 //* is enabled for this Agent. The CNMLINK library must also be000363 //* APF-authorized.000364 // DD DISP=SHR,000365 // DSN=NETVIEW.V5R3M0.CNMLINK

Contact your NetView for z/OS system programmer for the data set name, if necessary. The defaultNetView 5.3 CNMLINK data set is NETVIEW.V5R3M0.CNMLINK.

The CNMLINK library must be APF-authorized.

Copy the started task procedures to your procedure libraryThe configuration software creates a number of started task procedures in the data set&rhilev.&rte.RKANSAMU. Under a user ID with write authority to the PROCLIB data set, copy the followingprocedures to your procedure library:

v CANSDSST (the monitoring server started task)

v KPDPROC1 (maintenance procedure for the persistent data store)

v started task procedures for any monitoring agents configured in their own address space in the runtimeenvironment

The KPDPROC1 procedure is present only if you configured a persistent data store in the runtimeenvironment.

Be careful not to overwrite any PROCLIB members that have already been modified.


Copy the VTAM definitions to your system VTAMLSTThe configuration software also creates VTAM definitions in the data set &rhilev.&rte.RKANSAMU. Under auser ID with write authority to the VTAMLST data set, copy the VTAM major node (default node ID for themonitoring server: CTDDSN) to your system VTAMLST. Be careful not to overwrite any VTAMLSTmembers that have already been modified.

Vary the VTAM major node activeIssue the following command to vary the VTAM major node active:V NET,ACT,ID=CTDDSN

If you changed the node ID for the monitoring server, replace CTDDSN with the new node ID.

APF-authorize the runtime load librariesAdd the following runtime load libraries to your list of APF-authorized libraries.

v &rhilev.&rte.RKANMOD

v &rhilev.&rte.RKANMODU

v &rhilev.&rte.RKANMODL

Any other runtime libraries concatenated in the STEPLIB DDNAME or in the RKANMODL DDNAME ofstarted tasks must also be APF-authorized. If you enabled password encryption, you must APF-authorizethe ICSF load library (default name CSF.SCSFMOD0), which is concatenated in the RKANMODL DDstatements.

If the runtime environment shares target libraries that were installed by SMP/E, you must alsoAPF-authorize the following libraries:

v &thilev.TKANMOD

v &thilev.TKANMODL

Some monitoring agents require additional target libraries. Check the monitoring agent configurationdocumentation.

(If applicable) Refresh the KSHXHUBS member in other runtimeenvironmentsThe hub monitoring server list monitored in the KSHXHUBS member of &rhilev.&rte.RKANPARU ismaintained in a global table (KDSTHUBS), which is used by all SOAP servers enabled in this installationlibrary. Subsequent changes to the entries in this table affect KSHXHUBS members in other runtimeenvironments.

Verify that you can start and stop the monitoring serverAt this point you can verify that the monitoring server can be started and stopped.

1. Start the hub monitoring server. If your hub is on a z/OS system, start the monitoring server startedtask:S CANSDSST

If your hub is on a distributed system, see IBM Tivoli Monitoring: Installation and Setup Guide.

2. If you have configured a remote monitoring server on z/OS, start its started task:S CANSDSST

3. In the RKLVLOG for the monitoring server address space, look for the following messages to indicatesuccessful startup:KDSMA001 Tivoli Enterprise Monitoring Server (TEMS) data collection server started.KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.

Chapter 6. Completing the configuration 121

Look also for the following messages to indicate successful establishment of a communications pathby the local location broker:KDSNC007 Local Location Broker is activeKDSNC004 Bind of local location broker complete= protocol_name:address

If the monitoring server is a hub, additional messages indicate successful establishment of acommunications path by the global location broker:KDSNC004 Bind of global location broker complete= protocol_name:addressKDSNC005 Bind of global location broker complete at address protocol_name:address on port numberKDSNC008 Global Location Broker is active

For a remote monitoring server, look for a message similar to this one to indicate a successfulconnection with the hub:KDS9141I The TEMS RTEname:CMS is connected to the hub TEMS protocol_name:address

The number of messages depends on the number of protocols defined.

4. Stop the monitoring server started task:P CANSDSST

If you encounter problems starting or stopping the monitoring server, refer to IBM Tivoli Monitoring:Troubleshooting Guide.

(If applicable) Enable NetView to authorize Take Action commandsIf you have configured monitoring servers to forward z/OS Take Action commands to NetView, you mustalso enable NetView to receive, authorize, and execute the commands.

To enable execution of forwarded commands, complete the following steps:

1. Define Tivoli Enterprise Portal user IDs to NetView.

For information on defining user IDs, see the section "Defining Tivoli Enterprise Portal User IDs" in theTivoli NetView for z/OS Security Reference. You can find the NetView for z/OS publications athttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itnetviewforzos.doc/toc.xml.

Tip: If an existing NetView operator ID matches a Tivoli Enterprise Portal user ID, Take Actioncommands are executed on the existing NetView operator ID. If the NetView operator ID is used to logon to a 3270 terminal, Take Action commands might run on an active NetView operator, with unwantedresults. Mapping Tivoli Enterprise Portal user IDs to NetView autotasks is preferable.

2. Perform one of the following actions:

v Define the NetView PPI receiver in the NetView DSIPARM member CNMSTYLE (see Figure 40).

Follow the instructions in the member. The PPI receiver for APSERV will be started during NetViewinitialization.

************************************************************************* Tivoli Management Services infrastructure server ** ** Uncomment the following (and, optionally, supply preferred OPID) to ** initialize support for commands and messages from Tivoli Management ** Services infrastructure and/or other APF authorized clients. See ** command help for APSERV for information about the function and ** clients depending on it. ** *************************************************************************function.autotask.APSERV = AUTOTMSI*AUTOTASK.?APSERV.Console = *NONE* //AUTOTASK.?APSERV.InitCmd = APSERV CNMPCMDR

Figure 40. CNMSTYLE member after editing


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itnetviewforzos.doc/toc.xml

v If you do not customize CNMSTYLE to define the receiver, start the NetView PPI receiver manuallyby issuing the APSERV command.

The APSERV command is a command server that runs on a NetView autotask or on a virtual OST(VOST). APSERV accepts commands or messages from APF authorized programs only. TheAPSERV command must be running, whether started during NetView initialization or manually, toreceive the system commands from the TEMS and agent. Refer to the NetView online help or to theTivoli NetView for z/OS Application Programmers Guide for more information on the APSERVcommand.

3. Verify that the NetView for z/OS Subsystem Address Space is active with the PPI enabled. The PPI isenabled by specifying the PPIOPT keyword in sample procedure CNMSJ010 (CNMPSSI), located inthe NetView CNMSAMP data set.

(If applicable) Edit the portal server environment fileCommunication between a hub monitoring server and the Tivoli Enterprise Portal Server requires ICSFencryption unless you edit the portal server environment file.

If ICSF is not installed on the z/OS system where the hub monitoring server is configured, edit the portalserver environment file (kfwenv) as follows:

1. On the Windows or Linux system where you have installed the portal server, launch the Manage TivoliMonitoring Services application.

2. In the application window, right-click Tivoli Enterprise Portal Server, and select Advanced > EditENV File.

The environment file kfwenv is opened in a text editor.

3. Add the following line to the end of the file, and then save the file and close the editor.USE_EGG1_FLAG=1

(or USE_EGG1_FLAG=Y)

4. Restart the Tivoli Enterprise Portal Server.

Enable historical data store maintenance (optional)If you intend to enable historical data collection and have allocated and configured maintenance of thehistorical data set, you must perform three additional tasks to enable the maintenance:

v “Provide access to the persistent datastore files.”

v “Authorize the KPDDSCO module” on page 124.

v “Verify persistent datastore configuration” on page 124.

If you are upgrading an existing monitoring server, you must also refresh the KPDPROC1 maintenanceprocedure in your system procedure library. See the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Upgrade Guide.

Provide access to the persistent datastore filesEnsure that KPDPROC1 procedure has the necessary authority to read, write, and update the persistentdatastore files.

The KPDPROC1 procedure is used to maintain the physical files that constitute the persistent datastore.Data store files are archived, exported or recycled according to the maintenance strategy that youspecified for persistent datastore file groups for the product. The persistent datastore subsystemautomatically submits maintenance jobs whenever a data store file becomes full. The maintenanceprocedure must be available in a system procedure library for the procedure to operate. The procedure isgeneric so it can be used by all runtime environment using this version of the persistent datastore.


Authorize the KPDDSCO moduleThe KPDPROCC REXX procedure runs in a TSO environment and must be enabled to run as anauthorized program under TSO. Authorize the KPDDSCO module by adding KPDDSCO to the systemPARMGEN(IKJTSOnn) under the AUTHPGM section and refresh the IKJTSOnn member by issuing the setcommand (T IKJTSO=nn). You might also request that authorized system programmers perform this stepso it can be scheduled with the LPAR change control processes.

Verify persistent datastore configurationTo verify that the configuration and authorization of the procedures have been successful, perform thefollowing steps:

1. Bring up the started task (for monitoring server or monitoring agent) that will collect historical data intothe product's persistent datastore libraries. In the RKPDLOG DDNAME started task, find any persistentdatastore libraries in a non-Offline status (for example, Partial or Full status).

2. From a z/OS operator console, issue the following z/OS MODIFY command:/F &stcname,KPDCMD RECOVER FILE=DSN:&pds_dataset

(where &stcname is the name of the started task performing the persistent datastore collection, and&pds_dataset is the persistent datastore data set).

For example, issue the following MODIFY command for the monitoring server:/F CIDSST,KPDCMD RECOVER FILE=+DSN:&rhilev.&rte.RGENHIS1

3. Wait 5 minutes.

4. In the RKPDLOG DDNAME started task, find the following Command: and KPDDSTR: references asshown in the following monitoring server RKPDLOG DDNAME example below:Command: RESUME FILE=DSN:&rhilev.&rte.RGENHIS1KPDDSTR: CONNECT processing started for DataStore fileDSN:rhilev.&rte.RGENHIS1KPDDSTR: CONNECT processing ended for DataStore fileDSN:&

5. If these references are not found, view the KPDPROC1 started task in SDSF and look for any obviouserrors.

Enable historical data collection (optional)Two levels of historical data are available:

v Short-term history data, which is stored in the persistent data store on z/OS systems.

v Long-term history data, which is stored in the Tivoli Data Warehouse on distributed systems.

Both short-term and long-term history are optional features that can be enabled from the Tivoli EnterprisePortal.

The Tivoli Enterprise Portal History Collection dialog box lists the attribute tables that are enabled forhistorical collection and reporting. To enable historical data collection, you must select and configure eachgroup (attribute table) for which you want to collect data, and then start collection for those groups. If youwant to warehouse the data for long-term historical reporting, you must set the Warehouse Interval to theinterval at which data is warehoused.

For detailed instructions on configuring history data collection in the Tivoli Enterprise Portal, refer to IBMTivoli Monitoring: Administrator's Guide and the Tivoli Enterprise Portal online help.

Enable event forwarding (optional)If you have configured a hub monitoring server on z/OS to forward situation events to Tivoli EnterpriseConsole or OMNIbus, you must complete the following tasks for event forwarding to succeed:

1. Configure the destination event server or servers to receive the events.


2. Install a situation update forwarding process (the event synchronization component) on the eventserver or servers.

3. If situation events are forwarded to the Tivoli Enterprise Console, complete the following steps:

a. Copy the .baroc files for the monitoring agents to the Tivoli Enterprise Console and install themthere.

b. If distributed agents report to a z/OS hub, use FTP to transfer the map and resource files for eachmonitoring agent to the RKANDATV library of the runtime environment that contains the hub.

c. If z/OS monitoring agents report to a hub in another CSI and their FMIDs have not been installed inthat CSI, copy their map files to the RKANDATV library of the runtime environment that containsthe hub.

d. Restart the Tivoli Enterprise Portal Server.

4. Use the taccmd createEventDest command to specify additional destination servers, if desired.

5. Use the Tivoli Enterprise Portal Situation editor to:

v Specify specific event servers to receive events (EIF receivers)

v Specify the event severity.

v Specify which events are sent to which event servers.

The IBM Tivoli Monitoring: Installation and Setup Guide provides detailed instructions for configuring TivoliEnterprise Console and OMNIbus servers to receive the situation events from the hub and for installing theevent synchronization component that allows the servers to return updated status to the hub. Theinstallation guide also contains instructions for installing the monitoring agent .baroc files on the TivoliEnterprise Console server. The IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide explains how touse the Situation editor to specify event destinations and set situation severities.

The following sections describe the .baroc, map, and resource files; tell where they are located; and givesinstructions for transferring them to the appropriate destinations:

v “Map, .baroc, and resource files”

v “Transferring KppBAR files to a Tivoli Enterprise Console server” on page 127

v “Transferring map and resource files to the z/OS hub” on page 127

Map, .baroc, and resource filesMonitoring agents provide three types of files for forwarding situations events to a Tivoli EnterpriseConsole:

v Map files are used by the Event Forwarder component to map attribute groups and attributes to TivoliEnterprise Console classes and slots before sending these events to a designated Tivoli EnterpriseConsole server through the Tivoli Event Integration Facility. Map files must be installed at the hub.

v .baroc files are used by the Tivoli Enterprise Console server to expand and format the forwardedsituation event data. The .baroc files are delivered with application support for the monitoring agents,but must be installed on the Tivoli Enterprise Console server.

If situation events are being forwarded to the Tivoli Enterprise Console event server, the kpp.baroc filesmust be copied from the TECLIB to the host of the Tivoli Enterprise Console server and installed in theserver. See IBM Tivoli Monitoring: Installation and Setup Guide for detailed instructions for installingkpp.baroc files on the Tivoli Enterprise Console server.

v Resource files contain the Tivoli Enterprise Console message slot translation resource files. These filesare used by the hub monitoring server.

If monitoring agents that run on distributed computers report to a z/OS hub monitoring server, or ifmonitoring agents that run on z/OS report to a hub in a different CSI, the map and resource files for thoseagents must be transferred to the hub. For instructions, see “Transferring map and resource files to thez/OS hub” on page 127.


The map, .baroc, and resource files are delivered with the application support for each monitoring agent.Monitoring agents that run on z/OS deliver map and .baroc files both in their FMIDs and with applicationsupport.

ImportantIf any distributed monitoring agents report either directly or indirectly (through a distributed remotemonitoring server) to a z/OS hub, you must complete the following steps to obtain the files requiredfor EIF event forwarding:

1. Install a monitoring server on a Windows, Linux, or UNIX computer.

2. Configure that monitoring server as a hub, but do not start it.

3. Install application support on that hub monitoring server for all monitoring agents from which youwant to forward situation events.

The IBM Tivoli Monitoring: Installation and Setup Guide provides instructions for installing andconfiguring a hub monitoring server on a distributed computer and for installing application supporton the hub. Follow the instructions for installing and configuring the hub, but not for starting it.

Tip: If only z/OS agents report to the z/OS hub, you do not have to configure a distributed hub andinstall application support for the agents. You can use the KppBAR files. See “Transferring KppBARfiles to a Tivoli Enterprise Console server” on page 127 for instructions on transferring KppBAR filesto a Tivoli Enterprise Console event server.

When application support is installed on a distributed hub, kpp.baroc and kpp.map files are placed in theTECLIB directory:<ITM_HOME>/tables/<TEMS_NAME>/TECLIB/(Unix and Linux)<ITM_HOME>/CMS/TECLIB (Windows)

Resource files are placed in the following directories:

v UNIX and Linux:<ITM_HOME>/tables/<TEMS_NAME>/rb/ascii-big/kpp_<LANG>.res

("big-endian" hardware <LANG> messages)<ITM_HOME>/tables/<TEMS_NAME>/rb/ascii-big/kpp_root.res

("big-endian" hardware default language messages)<ITM_HOME>/tables/<TEMS_NAME>/rb/ascii-little/kpp_<LANG>.res

("little-endian" hardware <LANG> messages)<ITM_HOME>/tables/<TEMS_NAME>/rb/ascii-little/kpp_root.res

( "little-endian" hardware default language messages)<ITM_HOME>/tables/<TEMS_NAME>/rb/ebcdic/KPPRSI

(z/OS English messages)

v Windows:<ITM_HOME>/CMS/TECLIB/rb/ascii-little/kpp_<LANG>.res

("little-endian" hardware <LANG> messages)<ITM_HOME>/CMS/TECLIB/rb/ascii-little/kpp_root.res

("little-endian" hardware default language messages)<ITM_HOME>/CMS/TECLIB/rb/ascii-big/kpp_<LANG>.res

("big-endian" hardware <LANG> messages)<ITM_HOME>/CMS/TECLIB/rb/ascii-big/kpp_root.res

("big-endian" hardware default language messages)<ITM_HOME>/CMS/TECLIB/rb/ebcdic

(z/OS English messages)

Monitoring agents that run on z/OS also provide KppBAR files and KppMAP files, which are installed inthe &rhilev.&rte.RKANDATV library in the z/OS hub runtime environment when the agent registers with thehub. OMEGAMON XE agents that run on z/OS do not deliver resource files, because their messages arenot translated.


Transferring KppBAR files to a Tivoli Enterprise Console serverIf you have only z/OS agents reporting to a z/OS hub and do not want to install a distributed monitoringserver, you can copy or transfer (FTP) the KppBAR files from the RKANDATV library of the runtimeenvironment that contains the hub to the host of the Tivoli Enterprise Console server. The files must berenamed to kpp.baroc on the Tivoli Enterprise Console host.

For example:

C:\temp>ftp bigblue.ibm.comConnected to bigblue.ibm.com.220-$FTPA1 IBM FTP CS V1R8 at bigblue.ibm.com, 23:03:19 on 2008-08-01.220 Connection will close if idle for more than 5 minutes.User (bigblue.ibm.com:(none)): myuserid331 Send password please.Password:230 myuserid is logged on. Working directory is "MYUSERID.".ftp> get ’test.tst420.sharing1.rkandatv(km5bar)’ km5.baroc200 Port request OK.250 Transfer completed successfully.ftp: 122724 bytes sent in 1.22Seconds 100.43Kbytes/sec.

Transferring map and resource files to the z/OS hubIf distributed agents report to a z/OS hub, their kpp.map and kpp.res files must be copied to theRKANDATV library of the hub's runtime environment and renamed in accordance with z/OS naming rules.

Important: If you use FTP to transfer the files, map files must be transferred in ASCII mode andresource files must be transferred in binary mode.

If you have monitoring agents on z/OS that report to a z/OS hub in a different CSI and the agent FMIDsare not installed in the hub CSI, you must also copy or transfer their map files to the hub.

Complete the following steps to transfer the files:

1. In a command window on the host of the distributed hub monitoring server where application supporthas been installed, change to the TECLIB directory. For example:cd IBM\ITM\CMS\TECLIB

2. At the command prompt, enter the following command:ftp <hostname>

where <hostname> is the name or IP address of the host of the z/OS hub monitoring server.

3. Enter an authorized user ID for the z/OS host and press Enter.

4. Enter the password for the user ID and press Enter.

5. Enter the following command:put kpp.map ’&rhilev.&rte.RKANDATV(KppMAP)’

where pp is the two-letter product code for the agent whose map file you are transferring, &rhilev is thehigh-level qualifier for the runtime environment, and &rte is the name of the runtime environment. Waitfor the message telling you that the transfer has completed successfully.

Repeat this step for every agent whose map file you want to transfer to the hub.

6. Change to the /rb/ebcdic directory. For example:cd rb/ebcdic

7. Change to binary mode:bin

8. Put the KppRSI files in the same library:put KppRSI ’&rhilev.&rte.RKANDATV(KppRSI)’


Repeat this step for every agent.

9. Exit the FTP session:bye

Run the ITMSUPER Tools (optional)Use the ITMSUPER Tools to learn about the health of your managed systems, situations, and environmentconfiguration. You can find the tools by searching for ITMSUPER on the Integrated Service ManagementLibrary website.

If you have configured products in more than one runtime environment, you must complete theconfiguration of the products in every runtime environment. Then go on to Chapter 7, “Adding applicationsupport to a monitoring server on z/OS,” on page 129.

Note: The ITMSUPER tools require that Web Services (that is, the SOAP server) be active at the hubmonitoring server.




Chapter 7. Adding application support to a monitoring serveron z/OS

When to follow the steps in this chapterIf your site has activated the self-describing agents capability at the hub monitoring server, it is notnecessary that you complete these steps for any agent that has the self-describing capability (that is,all distributed agents for version 6.2.3 and subsequent). These steps, however, are necessary for allOMEGAMON agents and for all distributed agents at a level prior to V6.2.3, regardless of the remotemonitoring server or hub monitoring server they report to, as these agents do not have theself-describing capability.

Before you can view data collected by monitoring agents, you must add support for the agents to the TivoliEnterprise Portal Server, to the hub monitoring server, and in some cases, to remote monitoring servers.Application support for a monitoring agent includes two types of files:

v Catalog and attribute (CAT and ATR) files are required for presenting workspaces, online help, andexpert advice for the agent in Tivoli Enterprise Portal.

v SQL files are required for adding product-provided situations, templates, and policies to the EnterpriseInformation Base (EIB) tables maintained by the hub monitoring server. These SQL files are also calledseed 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 serveron 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.

v If a monitoring agent and a monitoring server are installed in the same CSI, the catalog and attributefiles are added automatically to the monitoring server when its runtime libraries are loaded.

Tip: Some monitoring agents on z/OS have additional requirements. See the configurationdocumentation for each monitoring agent product.

v If a monitoring agent and a monitoring server are installed in different CSIs, and if data collected by themonitoring agent will flow through the monitoring server, you must copy or transfer the catalog andattribute files (KppATR and KppCAT) from the &thilev.TKANDATV library in the CSI where themonitoring agent is installed to the &rhilev.&rte.RKANDATV library for the runtime environment in whichthe monitoring server is configured.

v You add the catalog and attribute files for the Warehouse Proxy agent and for the Summarization andPruning agent to the hub monitoring server on z/OS from the Manage Tivoli Monitoring Services utilityon a Windows, Linux, or UNIX computer where a portal server is installed and where either the portalserver or a monitoring server is configured to communicate with the hub on z/OS.

v You add the SQL files for your monitoring agents, for the Warehouse Proxy agent, and for theSummarization and Pruning agent to the hub monitoring server on z/OS from the Manage TivoliMonitoring Services utility.

v If a distributed monitoring agent (a monitoring agent installed on a Windows, Linux, or UNIX system) ora 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 ManageTivoli Monitoring Services.

This chapter gives instructions for adding application support to a monitoring server on z/OS. Forinstructions on adding application support to a monitoring server on Windows, Linux, or UNIX, see the IBMTivoli Monitoring: Installation and Setup Guide.


PrerequisitesBefore you add application support to a monitoring server, you must complete these prerequisite tasks:

v Verify that every monitoring agent for which you plan to add application support is compatible with theversion 6.2.3 components of Tivoli Management Services. If you have any question about whether thecomponents are compatible, see the planning publications in the monitoring agent library.

v Install the distributed components of Tivoli Management Services or IBM Tivoli Monitoring. Theprocedures described in this chapter require that a portal server be installed on a Windows, Linux, orUNIX system and that either the portal server or a monitoring server be configured to communicate withthe hub on z/OS. For instructions, see the IBM Tivoli Monitoring: Installation and Setup Guide.

v Install any distributed non-base monitoring agents that you have purchased. For instructions, see thedocumentation for each monitoring agent.

v Make sure you have access to the application support data files for every monitoring agent for whichyou plan to add application support.

– Some monitoring agents that run on z/OS or z/VM are packaged with their own CD or DVD thatcontains the data files for adding application support to the monitoring server.

– Other monitoring agents that run on z/OS are packaged with a CD or DVD that contains applicationsupport data files for a number of agents.

– Distributed agents (including the Warehouse Proxy agent and the Summarization and Pruning agent)already have the necessary application support files available on the appropriate system, if theagents are installed on a computer with a portal server installed and with either the portal server or amonitoring server configured to communicate with the hub on z/OS.

Tip: During installation of the components of Tivoli Management Services or IBM Tivoli Monitoringon a distributed system, you are prompted to add application support to the monitoring server. Selectthe option On this computer to add application support to the local monitoring server. Do not selectthe option On a different computer to add application support to the hub on z/OS at this point.

– For a distributed agent installed on a computer on which no portal server is installed or on whichneither the portal server nor a remote monitoring server is configured to communicate with the hubmonitoring server on z/OS, use the product CD or DVD to install the application support files on adifferent computer where a portal server is installed and where either the portal server or a remotemonitoring server is configured to communicate with the hub monitoring server on z/OS. Forinstructions, see the installation instructions in the monitoring agent library, or see IBM TivoliMonitoring: Installation and Setup Guide.

To determine where application support files can be found for z/OS monitoring agents and to ensurethat you install application support for your monitoring agents in the correct order, see the Locating ITMWorkspace Application Support Files for z/OS Agents Technote. You can find this Technote by selectingone of your OMEGAMON XE products on the Software Support website at http://www.ibm.com/software/support and searching for locating application support.


http://www.ibm.com/software/support


Selecting the correct procedureThe procedure for adding application support to a monitoring server depends on your configuration. Someconfigurations, while supported, do not represent best practices and might not yield the best possibleresults in performance and reporting. The best-practice configurations are identified in Table 4. For moredetailed information about best practices for configuring your monitoring environment, see Chapter 2,“Planning your deployment,” on page 13.

Table 4. Procedures for adding application support to a monitoring server on z/OS

Monitoring agent location Best practice? Follow these instructions

Same CSI as the hub orremote monitoring server onz/OS

Yes 1. Install the application support files on a distributed system wherea portal server is installed and where either the portal server or aremote monitoring server is configured to communicate with thehub monitoring server on z/OS.

See “Install the application support files on a distributed systemwhere a portal server is installed” on page 133.

2. Copy or transfer catalog and attribute files to the monitoringserver on z/OS for the Warehouse Proxy agent and theSummarization and Pruning agent, if you want to store long-termhistory data.

See “Copy or transfer catalog and attribute files to the monitoringserver on z/OS” on page 137.

3. Use Manage Tivoli Monitoring Services to add applicationsupport SQL files to the hub monitoring server on z/OS.

See “Use Manage Tivoli Monitoring Services to add applicationsupport SQL files to the hub monitoring server on z/OS” on page139.

Different CSI from the hubor remote monitoring serveron z/OS

No 1. Copy or transfer the monitoring agent's catalog and attribute files(KppCAT and KppATR) from the &thilev.TKANDATV library in theCSI where the monitoring agent is installed to the&rhilev.&rte.RKANDATV library for the runtime environment inwhich the monitoring server is configured. You can use IEBCOPYor FTP file transfer.

2. Install the application support files on a distributed system wherea portal server is installed and where either the portal server or aremote monitoring server is configured to communicate with thehub monitoring server on z/OS.


3. Copy or transfer catalog and attribute files to the monitoringserver on z/OS for the Warehouse Proxy agent and theSummarization and Pruning agent, if you want to store long-termhistory data.




Chapter 7. Adding application support to a monitoring server on z/OS 131

Table 4. Procedures for adding application support to a monitoring server on z/OS (continued)

Monitoring agent location Best practice? Follow these instructions

z/VM system Yes 1. Install the application support files on a distributed system wherea portal server is installed and where either the portal server or aremote monitoring server is configured to communicate with thehub monitoring server on z/OS.


2. Copy or transfer catalog and attribute files to the monitoringserver on z/OS.




Distributed system where aportal server is installed andwhere either the portalserver or a remotemonitoring server isconfigured to communicatewith the hub monitoringserver on z/OS

Yes 1. Copy or transfer catalog and attribute files to the monitoringserver on z/OS.




Distributed system(Windows, Linux, or UNIX)on which no portal server isinstalled or on which neitherthe portal server nor aremote monitoring server isconfigured to communicatewith the hub monitoringserver on z/OS

No 1. Install the application support files on a distributed system wherea portal server is installed and where either the portal server or aremote monitoring server is configured to communicate with thehub monitoring server on z/OS.


2. Copy or transfer catalog and attribute files to the monitoringserver on z/OS.




The rest of this chapter provides instructions for these procedures.

Tip: Complete only the procedures that apply to your configuration. Use Table 4 on page 131 to determinewhich procedures you must complete, and complete them in the order indicated in the table.


Install the application support files on a distributed system where aportal server is installedThis step involves installing the application support files on a Windows, Linux, or UNIX system where aportal server is installed and where either the portal server or a remote monitoring server is configured tocommunicate with the hub monitoring server on z/OS. For base agents (distributed agents included in thepurchase of IBM Tivoli Monitoring) and for other distributed agents installed on a system that meets theserequirements, you can skip to “Copy or transfer catalog and attribute files to the monitoring server onz/OS” on page 137.

Follow the instructions for installing the application support files on the appropriate system:

v “Installing application support files on Windows”

v “Installing application support files on Linux or UNIX” on page 135

Installing application support files on Windows

ImportantFollowing the correct order for installing application support files on Windows is essential. Todetermine where application support files can be found and to ensure that you install applicationsupport for your monitoring agents in the correct order, see the Locating ITM Workspace ApplicationSupport Files for z/OS Agents Technote. You can find this Technote by selecting one of yourOMEGAMON XE products on the Software Support website at http://www.ibm.com/software/supportand searching for locating application support.

To install the application support files on Windows, follow this procedure:

1. Insert a CD or DVD containing the application support files into the CD-ROM drive of a Windowsworkstation where a portal server is installed and where either the portal server or a remotemonitoring server is configured to communicate with the hub monitoring server on z/OS. (See“Prerequisites” on page 130.)

v Some monitoring agents that run on z/OS or z/VM are packaged with their own CD or DVD thatcontains the data files for adding application support to the monitoring server.

Other monitoring agents that run on z/OS are packaged with a CD or DVD that contains data filesfor a number of agents.If in doubt, refer to the configuration guide for each of your monitoringagents to find the exact name of the CD or DVD to use.

v For a distributed agent installed on a computer without a portal server or monitoring serverconfigured to communicate with the hub on z/OS, use the product CD or DVD to install theapplication support files on a different workstation where a portal server is installed and whereeither the portal server or a remote monitoring server is configured to communicate with the hubmonitoring server on z/OS. For instructions, see the installation instructions in the monitoring agentlibrary, or see IBM Tivoli Monitoring: Installation and Setup Guide.

Installation begins automatically. If the installer does not start, go to the Windows directory on yourCD-ROM drive and run setup.exe. If setup.exe initialization fails, you might not have enough freedisk space to extract the setup files.

2. Read the text that welcomes you to the installation, and click Next to continue.

3. On the Install Prerequisites window, check boxes are cleared if the required software is alreadyinstalled. Otherwise, a message instructs you to install the required software.

4. Click Next to continue.

5. Read the software license agreement and click Accept.



6. On the Select Features window, expand Tivoli Enterprise Portal Server and Tivoli EnterprisePortal Desktop Client (and Tivoli Enterprise Monitoring Server, if it is installed on the Windowsworkstation). For each component, select support for the monitoring agents you have installed onz/OS.

Tip: The IBM Eclipse Help Server component might be included in the list on the Select Featureswindow. However, this component is not selectable because it does not require application support.

The rest of the instructions assume that you are installing application support on the portal server anddesktop client.


8. In the Current® Settings pane of the Start Copying Files window, read the list of actions to beperformed , and click Next.

9. A window notifies you that you will be unable to cancel the installation after this point, and askswhether you want to continue. Click Yes to continue.

Application support for the selected monitoring agents is installed on the portal server and desktopclient. This installation step can take several minutes.

10. On the Setup Type window, select the following items:

v Configure Tivoli Enterprise Portal

v Launch Manage Tivoli Monitoring Services for additional configuration options and to start TivoliMonitoring Services.


12. On the TEPS Hostname window, make sure that the host name of the Tivoli Enterprise Portal Serveris correct and does not include the domain name. Click Next.

Presentation files for the Tivoli Enterprise Portal are built. This process can take up to 20 minutes.

13. On the InstallShield Wizard Complete window, click Finish.

14. Use Manage Tivoli Monitoring Services to copy catalog and attribute files and to add SQL files to themonitoring server on z/OS. Follow the instructions in “Transferring the catalog and attribute files fromWindows” on page 137 and “Adding application support SQL files from Manage Tivoli MonitoringServices on Windows” on page 139.


Installing application support files on Linux or UNIXInstalling application support on a Linux or UNIX system is a procedure with three iterations:v Installing application support on the browser client component of the portal server.v Installing application support on the portal server.v Installing application support on the monitoring server (if a monitoring server is installed on the local

Linux or UNIX system).

Application support can be installed on only one component at a time.

This procedure uses the command-line interface. For instructions on using the GUI interface or silentmode, see IBM Tivoli Monitoring: Installation and Setup Guide.

To install the application support files on Linux or UNIX, follow this procedure.

1. On a system where either a portal server or a remote monitoring server is configured to communicatewith the hub monitoring server on z/OS, run the following command from the application supportinstallation media:./install.sh

The installation media can be either the agent product CD or DVD for distributed monitoring agents,or a data files CD or DVD for monitoring agents that run on z/OS or z/VM. See “Prerequisites” onpage 130.

2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default(/opt/IBM/ITM) or type the full path to the installation directory you used.

The installer presents a list of installation options:Select one of the following:1) Install products to the local host.2) Install products to depot for remote deployment (requires TEMS).3) Install TEMS support for remote seeding4) Exit install.Please enter a valid number:

3. Enter 1 to start the installation.

The software license agreement is displayed.

4. Review the license agreement, and then enter 1 to accept it.

5. Select the components on which you want to install application support.Product packages are available for this operating system and component support categories:

1) IBM Tivoli Monitoring components for this operating system2) Tivoli Enterprise Portal Browser Client support3) Tivoli Enterprise Portal Server support4) Tivoli Enterprise Monitoring Server support5) Other operating systems

If you have not already installed the Tivoli Management Services components on the currentoperating system, enter 1. Otherwise, select one of the components for installation of applicationsupport. Only one item can be selected at a time.

Tip: Tivoli Enterprise Portal Browser Client support is the component of Tivoli Enterprise PortalServer that supports presentation of the Tivoli Enterprise Portal for browser clients. You must installthe browser client support on the computer where you installed the portal server.

6. At the prompt for products to install, select and confirm either an individual monitoring agent or all ofthe above. (Although the prompts seem to indicate that the monitoring agents themselves are beinginstalled, only the application support files for the monitoring agents are actually being installed.)The following products are available for installation:1) monitoring_agent_1 Vnn.nn.nn.nn2) monitoring_agent_2 Vnn.nn.nn.nn3) all of the above


Type your selections here: 3The following products will be installed:

monitoring_agent_1 Vnn.nn.nn.nnmonitoring_agent_2 Vnn.nn.nn.nn

Are your selections correct [ y or n; "y" is default ]?... installing "monitoring_agent_1 Vnn.nn.nn.nn for Linux S390 R2.6 (32 bit)";

please wait.... installing "monitoring_agent_2 Vnn.nn.nn.nn for Linux S390 R2.6 (32 bit)";please wait.

7. Enter y at the next prompt:Do you want to install additional products or product support packages [ y or n; "n" is default ]?

8. Repeat the procedure to install browser client, portal server, and monitoring server (if a monitoringserver is installed on the local system) support.

Only one item can be installed at a time. For each item, select the same monitoring agents (products)to install.

9. When you have selected and installed application support for all installed components, enter n at thisprompt:Do you want to install additional products or product support packages [ y or n; "n" is default ]?

10. You are prompted to add application support to all locally installed components. For example, if thereis a local monitoring server, you see a prompt similar to this one:Following Tivoli Enterprise Monitoring Server product support were installed:

monitoring_agent_1monitoring_agent_2

Note: This operation causes the monitoring server to restart.Do you want to seed product support on the Tivoli Enterprise Monitoring Server?[ 1=Yes, 2=No ; default is "1" ]

11. Enter 1 to add application support to the local monitoring server. The installer starts the monitoringserver, adds application support, and stops the monitoring server; and repeats the procedure for eachof the other components installed on the local system. This message indicates successful completion:All supports successfully seeded.

12. Exit the installation program.

13. Stop the portal server and the portal client:./itmcmd agent stop cq./itmcmd agent stop cj

14. Reconfigure the portal server with the new agent information:./itmcmd config -A cq

Tip: If you already configured the portal server after installing it, you can press Enter at each promptto accept the previously entered parameters.

15. Reconfigure the portal client with the new agent information:./itmcmd config -A cj

16. Restart the portal server and the portal client:./itmcmd agent start cq./itmcmd agent start cj

17. Use Manage Tivoli Monitoring Services to copy catalog and attribute files and to add SQL files to themonitoring server on z/OS. Follow the instructions in “Transferring the catalog and attribute files fromLinux or UNIX” on page 138 and “Adding application support SQL files from Manage Tivoli MonitoringServices on Linux or UNIX” on page 140.


Copy or transfer catalog and attribute files to the monitoring server onz/OSThe requirements for catalog and attribute files depend on your setup.

v For monitoring agents in the same CSI with a monitoring server on z/OS, catalog and attribute files areadded automatically to the monitoring server when its runtime libraries are loaded. However, if you wantto store long-term history data, you must still transfer catalog and attribute files to the monitoring serveron z/OS for the Warehouse Proxy agent and the Summarization and Pruning agent.

v For a monitoring agent that is not installed in the same CSI as a z/OS monitoring server through whichthe agent's data flows, you must copy or transfer the agent's catalog and attribute files (KppATR andKppCAT) 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 can use IEBCOPY or FTP file transfer to put the files into the &rhilev.&rte.RKANDATV data set.

v For distributed monitoring agents reporting to a monitoring server on z/OS, you transfer catalog andattribute files to the monitoring server on z/OS from Manage Tivoli Monitoring Services on a systemwhere a portal server is installed and where either the portal server or a monitoring server is configuredto communicate with the monitoring server on z/OS.

v If you want to store long-term history data, you transfer catalog and attribute files for the WarehouseProxy agent and the Summarization and Pruning agent to the hub monitoring server on z/OS fromManage Tivoli Monitoring Services on a system where a portal server is installed and where either theportal server or a monitoring server is configured to communicate with the monitoring server on z/OS.

The required catalog and attribute files were installed on a Windows, Linux, or UNIX computer when youinstalled application support from the appropriate media. Follow the instructions for transferring the catalogand attribute files to a monitoring server on z/OS from a system where the portal server is installed:

v “Transferring the catalog and attribute files from Windows”

v “Transferring the catalog and attribute files from Linux or UNIX” on page 138

Transferring the catalog and attribute files from WindowsComplete this procedure to transfer the catalog and attribute files from Manage Tivoli Monitoring Serviceson Windows.

1. On the Windows workstation where you installed the application support data files and where the TivoliEnterprise Portal Server is installed, select Start > Programs (or All Programs) > IBM TivoliMonitoring > Manage Tivoli Monitoring Services.

2. On the Manage Tivoli Monitoring Services window, select Actions > Advanced > Utilities > FTPCatalog and Attribute files.

3. On the FTP Catalog and Attribute Files window, select the files you want to transfer, and click OK.

4. On the FTP TEMS Data to z/OS window, provide the following information:

v The fully qualified host name or the IP address of the monitoring server on z/OS.

v A valid FTP user ID and password.

v The fully qualified name of the &rhilev.&rte.RKANDATV data set (DSN).

Important: When you type the data set name, make sure that it does not end with a trailing blank,or the FTP will fail.

5. After you have completed these fields, click OK to transfer the files. Click OK again to confirm.

6. Stop and restart the monitoring server on z/OS.

7. Go on to add SQL files to the hub on z/OS. Follow the instructions in “Adding application support SQLfiles from Manage Tivoli Monitoring Services on Windows” on page 139.


Transferring the catalog and attribute files from Linux or UNIXComplete this procedure to transfer the catalog and attribute files from Manage Tivoli Monitoring Serviceson a Linux or UNIX system where you have already installed the Tivoli Enterprise Portal Server and theapplication support files.

1. To start Manage Tivoli Monitoring Services, go to the $CANDLEHOME bin directory (example:/opt/IBM/ITM/bin ) on the system where you installed the application support data files, and run thiscommand:./itmcmd manage &

A GUI window opens for Manage Tivoli Monitoring Services.

2. Select Actions > FTP Catalog and Attribute files.

3. On the Select Attribute and Catalog Data for Transfer window, select the files you want to transfer, andclick OK.

4. On the FTP TEMS Data to z/OS window, provide the following information:

v The fully qualified host name or the IP address of the monitoring server on z/OS.

v A valid FTP user ID and password.

v The fully qualified name of the &rhilev.&rte.RKANDATV data set (DSN).

Important: When you type the data set name, make sure that it does not end with a trailing blank,or the FTP will fail.

5. After you have completed these fields, click OK to transfer the files.

6. Look for this message in the log window of Manage Tivoli Monitoring Services:Done sending files

7. Stop and restart the monitoring server on z/OS.

8. Go on to add SQL files to the hub on z/OS. Follow the instructions in “Adding application support SQLfiles from Manage Tivoli Monitoring Services on Linux or UNIX” on page 140.


Use Manage Tivoli Monitoring Services to add application support SQLfiles to the hub monitoring server on z/OSYou can use Manage Tivoli Monitoring Services to add application support SQL files to the hub monitoringserver on z/OS from any Windows, Linux, or UNIX system where a portal server or monitoring server hasbeen installed and configured to communicate with the hub. For monitoring agents on z/OS or z/VM, theapplication support files must also have been installed from the appropriate data files CD or DVD.

For most monitoring agents on z/OS, the application support SQL files are required on the hub monitoringserver but not on the remote monitoring servers. Plex agents are the exception: they require SQL files onboth hub and remote monitoring servers. However, SQL files for the plex agents are added automaticallyto each remote monitoring server on z/OS when the agent is registered with the monitoring server, so youdo not have to concern yourself with them.

To add application support SQL files to a hub monitoring server on z/OS from Manage Tivoli MonitoringServices, follow the instructions for the operating system where you have installed the files:

v “Adding application support SQL files from Manage Tivoli Monitoring Services on Windows”

v “Adding application support SQL files from Manage Tivoli Monitoring Services on Linux or UNIX” onpage 140

Adding application support SQL files from Manage Tivoli MonitoringServices on WindowsTo add application support SQL files to the hub monitoring server on z/OS, complete this procedure.

1. Ensure that the hub monitoring server is running.

2. On a Windows workstation where the application support files are installed, select Start > Programs(or All Programs) > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services.

3. On the Manage Tivoli Monitoring Services window, select Actions > Advanced > Add TEMSapplication support.

4. On the Add Application Support to the TEMS window, select On a different computer and click OK.

5. When you are prompted to ensure that the hub monitoring server is configured and running, click OK.

6. On the Non-Resident TEMS Connection window, provide the hub monitoring server TEMS name (nodeID), specify that it is a hub, select the communication protocol to use in sending the application supportSQL files to the hub, and provide any values required by the selected communication protocol. Thenclick OK to continue.

If you made a note of the TEMS name you specified when you defined the runtime environment, find itnow. Otherwise, you can find the TEMS name as the case-sensitive value of the CMS_NODEIDenvironment variable in this location:&rhilev.&rte.RKANPARU(KDSENV)

7. On the next panel, select the products for which you want to add application support. (If you want tocollect historical data, be sure to select the Warehouse Proxy and Summarization and Pruning agents,in addition to any monitoring agents you have purchased.) Then specify whether you want to add thedefault managed system groups to situations when you process the application support files:

All Add the default managed system groups to all applicable situations.

Tip: Make this selection if you have never customized situations from previous releases.

None Do not add the default managed system groups to any situation.

Tip: Make this selection if you do not want any predefined managed system groups to beapplied to your environment.

New Add the default managed system groups to all situations from the application support packages


being installed for the first time. Modifications are not made to managed system groups inpreviously upgraded application support packages.

Tip: Make this selection if you have customized situations from previous releases and youwant to protect your customized settings, but you want to apply the predefined managedsystem groups to new situations.

Make a selection and click OK. The SQL application support files are added to the hub monitoringserver. This process might take several minutes, depending on the number of products.

Tip: Not all situations support the default managed group setting. You might have to define thedistribution of some situations later from the Tivoli Enterprise Portal. For more information aboutmanaged system groups, see the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide.

8. The Application Support Addition Complete window gives you information about the status and locationof the SQL application support files. A return code of 0 (rc=0) indicates that the process succeeded.Click Save As if you want to save the information in a text file. Click Close to close the window.

If the Application Support Addition Complete window is not displayed after 20 minutes, look in theIBM\ITM\CNPS\Logs\NonResSeedkpp.log files (where pp is the 2-character code for each monitoringagent) for diagnostic messages that help you determine the cause of the problem. See the IBM TivoliMonitoring: Messages and IBM Tivoli Monitoring: Troubleshooting Guide for information aboutmessages and abnormal return codes.

9. Stop and restart the hub monitoring server.

Adding application support SQL files from Manage Tivoli MonitoringServices on Linux or UNIXTo add application support SQL files to the hub monitoring server on z/OS, complete this procedure.

1. Enable the GUI interface.

Your Linux or UNIX environment might already have a GUI interface enabled. Otherwise, perform thefollowing tasks to enable it:

a. Enable X11.

b. Make sure you have access to a native X-term monitor or an X Window System emulator.

c. If using an X Window System emulator, enable X11 access to the X Window System server(command example: xhost +).

d. If using an X Window System emulator, set the display environment variable to point to the XWindow System server:export DISPLAY=pc_ip_address:0

2. Ensure that the hub monitoring server on z/OS is running.

3. To start Manage Tivoli Monitoring Services, go to the $CANDLEHOME bin directory (example:/opt/IBM/ITM/bin ) on the system where you installed the application support data files, and run thiscommand:./itmcmd manage &

A GUI window opens for Manage Tivoli Monitoring Services.

4. Select Actions > Install product support.

5. On the Add Application Support to the TEMS window, select On a different computer and click OK.

6. When you are prompted to ensure that the hub monitoring server is configured and running, click OK.

7. On the Non-Resident TEMS Connection window, provide the hub monitoring server TEMS name(node ID), specify that it is a hub, select the communication protocol to use in sending the applicationsupport SQL files to the hub, and provide any values required by the selected communicationprotocol. Then click OK to continue.


If you made a note of the TEMS name you specified when you defined the runtime environment, findit now. Otherwise, you can find the TEMS name as the case-sensitive value of the CMS_NODEIDenvironment variable in this location:&rhilev.&rte.RKANPARU(KDSENV)

8. On the next panel, select the products for which you want to add application support. (If you want tocollect historical data, be sure to select the Warehouse Proxy and Summarization and Pruningagents, in addition to any monitoring agents you have purchased.) Then specify whether you want toadd the default managed system groups to situations when you process the application support files:

All Add the default managed system groups to all applicable situations.

Tip: Make this selection if you have never customized situations from previous releases.

None Do not add the default managed system groups to any situation.

Tip: Make this selection if you do not want any predefined managed system groups to beapplied to your environment.

New Add the default managed system groups to all situations from the application supportpackages being installed for the first time. Modifications are not made to managed systemgroups in previously upgraded application support packages.

Tip: Make this selection if you have customized situations from previous releases and youwant to protect your customized settings, but you want to apply the predefined managedsystem groups to new situations.

Make a selection and click OK. The SQL application support files are added to the hub monitoringserver. This process might take several minutes, depending on the number of products.

Tip: Not all situations support the default managed group setting. You might have to define thedistribution of some situations later from the Tivoli Enterprise Portal. For more information aboutmanaged system groups, see the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide.

9. In Manage Tivoli Monitoring Services, look for this message:Remote seeding complete!

10. Stop and restart the hub monitoring server.



Chapter 8. Configuring security on a monitoring server onz/OS

Access to the Tivoli Enterprise Portal is controlled by user IDs defined to the Tivoli Enterprise PortalServer. If security verification is enabled on the hub Tivoli Enterprise Monitoring Server, passwords arealso required.

How security verification is controlled depends upon the operating system on which the hub is installed. Ahub monitoring server running on z/OS validates user IDs and passwords using either theproduct-provided security feature, Network Access Method (NAM), or one of several system authorizationfacility (SAF) products. Lightweight Directory Access Protocol (LDAP) authentication is not supported forhub monitoring servers on z/OS systems.

The monitoring server supports secure password encryption through the Integrated Cryptographic ServiceFacility (ICSF). The ICSF provides a robust encryption and decryption scheme for stored passwords and isthe preferred method of password encryption. (If you do not use ICSF, the monitoring server uses a lesssecure encryption method.) ICSF uses symmetric secret keys for encrypting and decrypting data. Forinstructions on setting the password encryption key on a z/OS monitor server with the PARMGEN method,see the comments in the KCIJVSEC (if system variables are enabled) or KCIJPSEC (if system variablesare not enabled) member of the &rhilev.&rte.WKANSAMU library; for Configuration Tool (ICAT)instructions, see “Specify configuration values” on page 40.

In addition to validating user IDs and passwords, a z/OS monitoring server can be configured to redirectTake Action commands to IBM Tivoli NetView for z/OS for authorization and execution. NetView uses theTivoli Enterprise Portal user ID to check command authorization. If the user ID is authorized, the commandis issued and the response is logged in the NetView log.

This chapter provides instructions for the following security configuration tasks:

v “Enabling security validation on a z/OS hub”

v “Resetting the password encryption key” on page 147

v “Configuring NetView authorization of z/OS commands” on page 149

For information on setting up security on a hub on a distributed system, see IBM Tivoli Monitoring:Installation and Setup Guide. Some monitoring agents might require additional security configuration; seethe configuration documentation for the monitoring agent.

Enabling security validation on a z/OS hubIf security validation is enabled on a z/OS hub monitoring server, Tivoli Enterprise Portal user IDs and validpasswords must be defined to the security system used by the Tivoli Enterprise Monitoring Server. A hubTivoli Enterprise Monitoring Server running on z/OS validates user IDs and passwords using either theproduct-provided security feature, Network Access Method (NAM), or one of the following systemauthorization facility products:

v RACF

v CA-ACF2

v CA-TOP SECRET

v (PARMGEN method only) SAF, which provides a generic API to interface to z/OS security software

Before you enable security, your security administrator must define to the selected security system eachlogon ID that will be allowed to access the Tivoli Enterprise Portal Server, and the Tivoli Enterprise Portal


administrator must create user accounts for those IDs. You do not have to define and authorize additionaluser IDs before you enable security, but you must define and authorize one administrative ID such as thesysadmin user ID.

TipTo create additional user IDs after security validation is enabled, use one of the following methods:

v Create a new Tivoli Enterprise Portal user whose user ID matches a new or existing user definedto the security program. This is the preferred method.

v Define a Tivoli Enterprise Portal user ID to the security program.

Follow these steps to enable security on the hub Tivoli Enterprise Monitoring Server:

1. If you have not already done so, define the security system to be used. For more information about thesecurity-related parameters, see IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services onz/OS: Common Parameter Reference.

v PARMGEN method:

a. In the configuration profile of the runtime environment that contains the hub monitoring server,set the value of the RTE_SECURITY_USER_LOGON parameter to specify the security systemto be used for the runtime environment: RACF, ACF2, TSS, SAF, NAM, or None.

b. If you specified ACF2, provide the name of the ACF2 macro library as the value of theGBL_DSN_ACF2_MACLIB parameter.

v Configuration Tool (ICAT) method:

a. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), enter U (Update) in theAction field beside the name of the runtime environment where the hub monitoring server isconfigured.

b. On the Update Runtime Environment panel, specify the security system you want to use, andpress Enter. This example specifies RACF:Security system ==> RACF (RACF, ACF2, TSS, NAM, None)

If you select ACF2, you must also specify the ACF2 macro library in the next field.

2. Enable security validation on the hub.

v PARMGEN method:

a. In the configuration profile, set the value of the KDS_TEMS_SECURITY_KDS_VALIDATEparameter to Y.

b. Uncomment the KDS_TEMS_SECURITY_KAES256_ENCKEY parameter, and either accept theIBM-supplied default value "IBMTivoliMonitoringEncryptionKey" or specify a unique 32-bytepassword encryption key. The value is case-sensitive, and the same key must be used for allcomponents that communicate with the hub.

Tip:: The encryption key is shown in plain text in the configuration profile, so that the value canused as input to create the KAES256 encryption key file. For this reason, ensure that the&rhilev.&rte.WCONFIG library is secured.

c. Run either the KCIJVSEC (if system variables are enabled) or KCIJPSEC (if system variablesare not enabled) job in the &rhilev.&rte.WKANSAMU library to create the security-relatedmembers of the runtime libraries. Alternatively, you can run the either the KCIJVSUB orKCIJPSUB composite job, which creates all the runtime members.

d. When enabling ICSF password encryption, you must set the GBL_DSN_CSF_SCSFMOD0parameter. This can be found in either the WCONFIG($GBL$USR) if this is not anICAT-to-PARMGEN conversion, or in the WCONFIG(%RTE_NAME%) LPAR profile if this is anICAT-to-PARMGEN conversion:


ISREDDE2 TSTEST.CCAPI.TESTSYSB.WCONFIG($GBL$USR) - 01.00 Columns 00001 00072Command ===> Scroll ===> CSR000123 ** GBL_DSN_CSF_* ICSF system libraries:000124 ** Note: This is required if you are enabling the ITM Password000125 ** Encryption (KAES256) across the ITM enterprise:000126 ** This library is concatenated in the TEMS STC’s STEPLIB DD:000127 ** Related PARMGEN CONFIG profile parameters:000128 ** - KDS_TEMS_SECURITY_KAES256_ENCKEY000129 GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"

v Configuration Tool (ICAT) method:

a. On the Product Component Selection menu (Figure 28 on page 64), enter 1 to select TivoliEnterprise Monitoring Server.

b. On the Configure the TEMS panel (Figure 10 on page 40), select option 2 (Specify configurationvalues).

c. On the Specify Configuration Values panel (Figure 11 on page 41), specify Y in the Securityvalidation? field:Security validation? ==> Y (Y, N)

d. Press Enter to return to the Configure the TEMS panel.

Important: Do not enable security validation until your security is set up.

e. On the Configure the TEMS panel, select option 5 (Create runtime members) to open JCL thatyou can review, edit, and submit. Check to make sure the return code is zero.

f. After the job completes, press F3 (Back) repeatedly to exit the Configuration Tool.

3. Implement security, following the instructions in the appropriate section:v “Implementing security with RACF”v “Implementing CA-ACF2 security”v “Implementing security with CA-TOP SECRET” on page 146

4. Verify that the user account you created can log on to the Tivoli Enterprise Portal.

Implementing security with RACFTo implement RACF security after enabling security validation, recycle the monitoring server:

1. If your Tivoli Enterprise Monitoring Server is running, stop it by entering:P cccccccc

where cccccccc is the name of your monitoring server started task.

2. If your site has a large numbers of users, you might have to increase the value assigned to theRESERVE parameter of member KDSSYSIN in the &rhilev.&rte.RKANPARU library.

3. Restart your Tivoli Enterprise Monitoring Server by entering:S cccccccc

where cccccccc is the name of your Tivoli Enterprise Monitoring Server started task.

Implementing CA-ACF2 securityFollow these steps to install an exit for CA-AF2 security validation.



2. Follow the instructions in KLVA2NEV to assemble and link KLVA2NEV. Change the -RHILEV- and-THILEV- variables as directed.

Member KLVA2NEV in &thilev.TKANSAM is the product-supplied interface to CA-ACF2. Theproduct-supplied member KLV@ASM, in &rhilev.&rte.RKANSAMU, contains sample assembly JCL.This gets assembled into the runtime environment-specific &rhilev.&rte.RKANMODU data set.

Chapter 8. Configuring security on a monitoring server on z/OS 145

3. Define the Tivoli Enterprise Monitoring Server started task as a MUSASS to CA-ACF2:

a. Log on to TSO. At the READY prompt, type ACF and press Enter.

b. At the ACF prompt, type SET LID and press Enter.

c. At the LID prompt, typeCH cccccccc MUSASS

where cccccccc is the name of the Tivoli Enterprise Monitoring Server started task. Press Enter.

d. At the LID prompt, type END and press Enter.

If your site has large numbers of users, you might have to increase the value assigned to theRESERVE parameter of member KDSSYSIN in the &rhilev.&rte.RKANPARU library.



Implementing security with CA-TOP SECRETFollow these steps to implement CA-TOP SECRET security.


where cccccccc is the name of the monitoring server started task.

2. Define the monitoring server as a started task in the STC record and relate it to a master facilityaccessor identifier. For example:TSS ADD(STC) PROC(cccccccc) ACID(master_facility_acid)

where cccccccc is the name of your monitoring server started task. The value for master_facility_acidcan be the same as cccccccc.

3. Define the name of your Tivoli Enterprise Monitoring Server started task as a FACILITY in the CA-TOPSECRET Facility Matrix Table. Set the SIGN parameter as SIGN(M) and set MODE to MODE=FAIL.Make sure the name of your Tivoli Enterprise Monitoring Server started task and the FACILITY namematch.

Example: This example shows FACILITY statements for a site that uses CA-TOP SECRET. Somestatements might not be relevant to your site or might require modification to fit the standards andconfiguration of your site.FACILITY(USER3=NAME=task)FACILITY(task=MODE=FAIL,ACTIVE,SHRPRF)FACILITY(task=PGM=KLV,NOASUBM,NOABEND,NOXDEF)FACILITY(task=ID=3,MULTIUSER,RES,WARNPW,SIGN(M))FACILITY(task=NOINSTDATA,NORNDPW,AUTHINIT,NOPROMPT,NOAUDIT,NOMRO)FACILITY(task=NOTSOC,LOG(INIT,SMF,MSG,SEC9))



Implementing security with Network Access Method (NAM)As an alternative to third-party security packages, you can use the product-provided security feature NAM(Network Access Method) to secure your Tivoli Enterprise Monitoring Server. However, be aware that thisis a less secure method than using one of the three security packages.

NAM user IDs are 1 to 8 characters in length and are not case-sensitive.

You can enable NAM from the system console, using the MVS MODIFY command. Instructions are givenin the following sections.


Adding users to NAMFollow these steps to add users to NAM from the z/OS system console.

1. Access the z/OS system console.

2. Define a password for each user who will access the Tivoli Enterprise Portal:F cccccccc,NAM SET userid PASSWORD=password

where cccccccc is the name of your Tivoli Enterprise Monitoring Server started task, userid is the userID, and password is the NAM password you want to define for that user

Adding a userid password file to NAMIf you are defining passwords for a large number of users, you might want to use the following procedureto set up a file containing all your NAM SET statements and execute the file once to define all passwords.

1. Access &rhilev.&rte.RKANCMDU and create member userids.

2. Edit userids, and populate it with a NAM SET command for each user who will access your TivoliEnterprise Monitoring Server.

Example:NAM SET userid1 PASSWORD=password1NAM SET userid2 PASSWORD=password2NAM SET userid3 PASSWORD=password3

Note: Make sure there is sufficient security on the &rhilev.&rte.RKANCMDU library, as it now containssensitive information.

3. To execute member userids, enter this command from the z/OS system console:F cccccccc,userids


Changing the security system specificationWhen you create the runtime members for the hub Tivoli Enterprise Monitoring Server, appropriateparameters are generated for the security system that you selected.

If you must convert to another security system, change the security system specification in the PARMGENconfiguration profile or on the Configuration Tool Update Runtime Environment panel. For the change totake effect, you must recreate the runtime members for the monitoring server before you recycle themonitoring server started task.

Resetting the password encryption keyThe Integrated Cryptographic Services Facility (ICSF) uses a symmetric key to encrypt and decrypt data.The key is known as symmetric because the same key is used to transform plain text to cipher text(encryption) as is used to transform cipher text back to plain text (decryption). When you run theDS#3ssss job (generated by the Create Runtime Members option on the Configure the TEMS panel), theConfiguration Tool takes the value you entered for the key, creates a key file named KAES256 in&rhilev.&rte.RKANPARU and loads the encrypted key into it.


TipEnsure that the KAES256 step of the DS#3ssss job ends successfully. Errors of the following typestypically indicate that ICSF is not configured correctly in your system:

Cannot encrypt text: call to CSNBSYE failed

Cannot encrypt contents of keyfile

Function failed with error code 26

If you receive those messages, work with your security specialist to resolve the ICSF problem, andthen rerun only the KAES256 step of the DS#3ssss job. (If you rerun the entire job, the KAES256step is omitted for security reasons.)

The same key must be used on all Tivoli Management Services components in your enterprise. Forexample, the encryption key you set for the Tivoli Enterprise Portal must be the same value you specify forthe encryption key for the hub monitoring server, and the key you set for each of the remote monitoringservers that connect to the hub must also have the same value. If you reset the key for one component,you must reset it for all of them.

In the Configuration Tool, the encryption key value is not displayed if you return to the SpecifyConfiguration Values panel after you finish configuring the monitoring server. If you reconfigure themonitoring server by changing other parameter values on the configuration panels, the resulting DS#3ssssjob does not create a key file.

If you must change the encryption key value after initial configuration with the Configuration Tool, type thePWD command on the command line of the Specify Configuration Values panel, and then answer Y to theprompt "Do you want to disable ICSF encryption or reset the key?". You can then re-enable encryption andspecify a different key. After doing so, you must recreate the runtime members (“Create the runtimemembers” on page 61) and reload the runtime libraries (“Step 3. Load the runtime libraries” on page 98).

For batch mode processing, the encryption key value is stored in a batch parameter calledKDS_CMS_SEC_ENC_KEY. The encryption key must be displayed in plain text in the batch parametermember, so that the value can used as input to create the KAES256 encryption key file. For this reason,ensure that the &shilev.INSTJOBS or whatever library the parameter member is stored in is secured.

In the batch parameter member, the value for the encryption key parameter (KDS_CMS_SEC_ENC_KEY)must be enclosed in quotation marks. If you must use a single quotation mark (') as part of the key value,enclose the 32-byte encryption key string in double quotation marks ("") and vice-versa: if you must use adouble quotation mark (") as part of the key value, enclose the string in single quotation marks ('). If youmust use both the single quotation mark and the double quotation mark as part of the key value, use theinteractive mode of the Configuration Tool instead.

The encryption key has the following characteristics:

v The key must be 32 bytes in length.

v The key is case-sensitive.

v The key cannot contain an ampersand (&) value.

If you change the encryption key on any component, you must change the key to the same value on allcomponents that connect to the same hub.


PARMGEN method1. Set the KDS_TEMS_SECURITY_KAES256_ENCKEY parameter to the new value of choice:

ISREDDE2 TSTEST.CCAPI.TESTSYSB.WCONFIG(TESTSYSB)Command ===> Scroll ===> CSR000821000822 ** TEMS’ security settings: KAES256 encryption key000823 ** Note: This is required if you are enabling the ITM Password000824 ** Encryption (KAES256) across the ITM enterprise:000825 ** The "KDS_TEMS_SECURITY_KAES256_ENCKEY" value is encrypted000826 ** and xKANPARU(KAES256) member is created as part of the000827 ** xKANSAMU(KCIJPSEC) composite security job.000828 ** Related PARMGEN CONFIG profile parameter:000829 ** - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the000830 ** TEMS STC’s STEPLIB DD)000831 KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"

2. Edit WCONFIG($PARSEPR) from the PARMGEN Workflow Menu option "7. $PARSE" > option "3.$PARSEPR IKANPARU/WKANPARU $PARSE job". Specify "SELECT MEMBER=(KAES256,K??ENV)"only instead of recreating all the runtime members from IKANPARU to WKANPARU.

3. Edit WCONFIG($PARSESM) from the PARMGEN Workflow Menu option "7. $PARSE" > option "4.$PARSESM IKANSAMU/WKANSAMU $PARSE job". Specify "SELECTMEMBER=(KDSDKAES,KCIJPSEC)" only instead of recreating all the runtime members fromIKANSAMU to WKANSAMU.

Note: Instead of steps 2 and 3 above, you also have the option of rerunning the $PARSE compositejob or (if the runtime environment is enabled for system variables) the $PARSESV composite job. Ineither case, the file-tailoring job recreates the following members:



WKANSAMU(CANSDSST)Monitoring server started task to concatenate the ICSF load library in the STEPLIB DDNAME.




4. Resubmit the WKANSAMU(KDSDKAES) job to refresh the RKANPARU(KAES256) member.

5. Adjust the Tivoli Enterprise Portal Server to also use the same password encryption key (the same keymust be used across your enterprise).

6. Recycle the Tivoli Enterprise Monitoring Server started task.

Configuring NetView authorization of z/OS commandsSystem commands issued from the Tivoli Enterprise Portal using Take Action commands, whether issuedby a user or triggered by situations or policies, run without any authorization or audit trail. However, youcan configure a monitoring server or monitoring agent address space to redirect z/OS Take Actioncommands to NetView through the Program to Program Interface (PPI). Take Action commands issued in


NetView make full System Authorization Facility (SAF) calls for authorization. NetView uses the TivoliEnterprise Portal user ID to determine the NetView operator on which the command authorization isperformed. If command authorization passes, the command is executed on the NetView operator.Messages are written to the NetView log to provide an audit trail of the commands and the users thatissued them. If you enable NetView command authorization on the monitoring server, you must alsoenable NetView to execute the commands.

Command authorization for the system commands uses the Tivoli Enterprise Portal user ID, which ispassed to the NetView program with the command. The user ID passed on a Take Action commanddetermines the user ID that issues the command. The user ID passed when a command is driven from asituation is the user ID that last edited the situation. Only the user ID is used for command authorization.Password validation is not performed.

Take Action forwarding requires NetView on z/OS, V5.3 (or V5.2 with APAR OA18449 applied).

To set up NetView of Take Action commands, complete the following steps:

1. “Configure the monitoring server to forward Take Action commands.”

2. “Add the NetView CNMLINK data set to the Tivoli Enterprise Monitoring Server started task” on page151.

3. “Enable NetView to authorize Take Action commands” on page 152

Note: Some agents provide their own Take Action commands, known as agent commands. Agentcommands have a 2-character prefix, such as pp: (where pp is the product code). These commands arenot sent to the NetView program for command authorization and execution. An example of an agent thatprovides agent commands is IBM Tivoli OMEGAMON XE for Messaging on z/OS.

Configure the monitoring server to forward Take Action commandsTo configure Take Action command forwarding, set the parameters as shown.

v PARMGEN method: In the configuration file for the runtime environment, uncomment theKDS_PPI_RECEIVER and KDS_PPI_SENDER parameters, and either accept the default values orspecify your own values.

v Configuration Tool (ICAT) method: On the Specify Configuration Values panel (Figure 11 on page 41),complete the Program to Program Interface (PPI) information section as follows:

Forward Take Action commands to NetView for z/OSSpecify Y if you want the Tivoli Enterprise Monitoring Server to forward z/OS console commandsissued as Take Action commands to NetView for authorization and execution. The default valueis N.

NetView PPI receiverSpecify the name of the PPI receiver on NetView that will receive Take Action commands. Thisname must match the receiver name that is specified on the NetView APSERV command. (Thedefault name is CNMPCMDR.) If the specified name is incorrect or the receiver is not active onNetView for z/OS, default command routing to the z/OS console is performed. TheConfiguration Tool generates the KGLHC_PPI_RECEIVER environment variable in the KDSENVmember of the &rhilev.&rte.RKANPARU library.

The value must be a 1- through 8-character unique identifier for the receiver program. It cancontain alphabetic characters A-Z or a-z, numeric characters 0-9, and the following specialcharacters: dollar sign ('$'), percent sign ('%'), ampersand ('&'), at sign ('@'), and number sign('#'). This value must match the value specified in the NetView DSIPARM initialization member,CNMSTYLE (see “Enable NetView to authorize Take Action commands” on page 152).

If a value is specified for this parameter and either the specified name is incorrect or thereceiver is not active on NetView for z/OS, the command fails. If no value is specified, defaultcommand routing to the z/OS console is performed.


TEMS PPI senderOptionally, specify the optional name of the PPI sender. The value must be a 1- through8-character unique identifier for the receiver program. It can contain alphabetic characters A-Zor a-z, numeric characters 0-9, and the following special characters: dollar sign ('$'), percentsign ('%'), ampersand ('&'), at sign ('@'), and number sign ('#'). This name must not conflict withany NetView for z/OS domain name, as it is used in logging the command and commandresponse in the NetView log. If a value is specified on this field, the Configuration Toolgenerates the KGLHC_PPI_SENDER environment variable in the KDSENV member of the&rhilev.&rte.RKANPARU library.

If you do not specify a value in this field, the default is the job name of the Tivoli EnterpriseMonitoring Server that is the source of the command.

Add the NetView CNMLINK data set to the Tivoli Enterprise MonitoringServer started taskTo connect to NetView, the Tivoli Enterprise Monitoring Server must reference the NetView CNMLINK dataset. Concatenate the NetView CNMLINK data set to the RKANMODL statement in the monitoring serverstarted task.

Note to PARMGEN users: In ICAT, this process is a manual step; however, with PARMGEN, this is not apost-configuration step. Shown below is the parameter in WCONFIG($GBL$USR) profile that PARMGENusers must customize. This will automatically generate the monitoring server and agent started tasks withthe CNMLINK library concatenated to the RKANMODL DD, provided the PPI parameters are alsospecified.

ISREDDE2 TSTEST.CCAPI.TESTSYSB.WCONFIG($GBL$USR) - 01.00 Columns 00001 00072Command ===> Scroll ===> CSR000113 ** GBL_DSN_NETVIEW_* NetView system libraries:000114 ** Note: This is required if you are enabling the ITM Forward000115 ** Take Action commands to NetView for z/OS.000116 ** Related PARMGEN CONFIG profile parameters:000117 ** - *_PPI_RECEIVER and *_PPI_SENDER000118 ** This library is concatenated in the TEMS and Agent STCs’000119 ** RKANMODL DD:000120 GBL_DSN_NETVIEW_CNMLINK "NETVIEW.VNRNMN.CNMLINK"

To provide the location, uncomment the CNMLINK DD card in the started task and specify the NetViewCNMLINK data set. For example:

Contact your NetView for z/OS system programmer for the data set name, if necessary. The defaultNetView 5.3 CNMLINK data set is NETVIEW.V5R3M0.CNMLINK.

000350 //RKANMODL DD DISP=SHR,000351 // DSN= &RHILEV.&SYS.RKANMODU000352 // DD DISP=SHR,000353 // DSN= &RHILEV.&SYS.RKANMODUL000354 // DD DISP=SHR,000355 // DSN= &RHILEV.&SYS.RKANMOD000356 //******************************************************************000357 //* RKANMODL DD: CNMLINK000358 //******************************************************************000359 //* Uncomment this DD card and specify the location of the CNMLINK000360 //* load module for NetView for z/OS. This library is required for the000361 //* "Forward Take Action commands to NetView for z/OS" support which000362 //* is enabled for this Agent. The CNMLINK library must also be000363 //* APF-authorized.000364 // DD DISP=SHR,000365 // DSN=NETVIEW.V5R3M0.CNMLINK

Figure 41. CNMLINK DD statement in the Tivoli Enterprise Monitoring Server started task


The CNMLINK library must be APF-authorized.

Enable NetView to authorize Take Action commandsIn addition to configuring Tivoli Enterprise Monitoring Server address spaces to forward z/OS Take Actioncommands to NetView, you must also enable NetView to receive and execute the commands. NetViewdoes command authorization as part of the execution.

To enable execution of forwarded commands, complete the following steps:

1. Define Tivoli Enterprise Portal user IDs to NetView.

To define a user ID to NetView, perform one or more of the following actions:

v Create a new Tivoli Enterprise Portal user ID that matches a new or existing NetView operator ID.

v Define an existing Tivoli Enterprise Portal user ID as a NetView operator ID.

v Map the TEP user ID to a valid NetView operator ID by using the NACMD.OPID.TEPLogonidCNMSTYLE statement.

See Chapter 2, "CNMSTYLE Initialization Statements" in Tivoli NetView for z/OS AdministrationReference for more information on the NACMD.OPID statement. For information on defining user IDs,see the section "Defining Tivoli Enterprise Portal User IDs" in the Tivoli NetView for z/OS SecurityReference. You can find the NetView for z/OS publications at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itnetviewforzos.doc/toc.xml.

2. Perform one of the following actions:

v Define the NetView PPI receiver in the NetView DSIPARM member CNMSTYLE (see Figure 40 onpage 122).

Follow the instructions in the member. The PPI receiver for APSERV will be started during NetViewinitialization.

v If you do not customize CNMSTYLE to define the receiver, start the NetView PPI receiver manuallyby issuing the APSERV command.

The APSERV command is a command server that runs on a NetView autotask or on a virtual OST(VOST). APSERV accepts commands or messages from APF authorized programs only. TheAPSERV command must be running, whether started during NetView initialization or manually, toreceive the system commands from the TEMS and agent. Refer to the NetView online help or to theTivoli NetView for z/OS Application Programmers Guide for more information on the APSERVcommand.

3. Verify that the NetView for z/OS Subsystem Address Space is active with the PPI enabled. The PPI isenabled by specifying the PPIOPT keyword in sample procedure CNMSJ010 (CNMPSSI), located inthe NetView CNMSAMP data set.

************************************************************************* Tivoli Management Services infrastructure server ** ** Uncomment the following (and, optionally, supply preferred OPID) to ** initialize support for commands and messages from Tivoli Management ** Services infrastructure and/or other APF authorized clients. See ** command help for APSERV for information about the function and ** clients depending on it. ** *************************************************************************function.autotask.APSERV = AUTOTMSI*AUTOTASK.?APSERV.Console = *NONE* //AUTOTASK.?APSERV.InitCmd = APSERV CNMPCMDR

Figure 42. CNMSTYLE member after editing




Notes:

1. If a NetView operator ID exists that matches a Tivoli Enterprise Portal user ID, the command will beexecuted on the existing NetView operator ID, if appropriate command authorization exists.

2. Be careful about mapping a Tivoli Enterprise Portal user ID to a NetView operator ID that is used tolog on to a 3270 terminal. The Take Action command might be run on an active NetView operator withunwanted results. Mapping Tivoli Enterprise Portal user IDs to NetView autotasks is preferable.

Verifying the configurationComplete the following steps to verify the configuration.

1. If you defined new NetView operator IDs, refresh NetView operator ID definitions.

2. If you did not complete Step 2 under “Enable NetView to authorize Take Action commands” on page152, issue the APSERV command on a NetView autotask or VOST.

This step must be completed before monitoring server and agent system commands can successfullybe sent to the NetView program.

If you completed Step 2 under “Enable NetView to authorize Take Action commands” on page 152,recycle NetView to start APSERV during NetView initialization.

3. Restart the monitoring server and agents.

4. Using a Tivoli Enterprise Portal client, complete one of the following steps:

v Issue an existing Take Action command.

v Create a new Take Action command and issue it.

If the command executes successfully, you will see messages in the NetView log. For example: If yourTake Action command is D T, you will see messages similar to the following:AUTOTMSI IBMUSER 13:34:21 | BNH806I TAKE ACTION COMMAND ’MVS D T (00000003)’RECEIVED FOR TASK SYSADMIN

SYSADMIN CANSN3 13:34:21 * MVS D T

SYSADMIN NTVAF 13:34:21 E IEE136I LOCAL: TIME=13.34.21 DATE=2008.233 GMT:TIME=18.34.21 DATE=2008.233

Troubleshooting tipsIf you encounter problems using the security solution, use the following information to troubleshoot:

v Review your monitoring server or agent RKLVLOG and NetView log for error messages.

v If you see either of the following symptoms, the NetView CNMLINK data set has not been concatenatedas part of the monitoring server or monitoring agent RKANMODL DD statement in the startupprocedure:

– A return code of 17 in the Action Status pop-up window after a Take Action command is issued

– A message in the RKLVLOG stating “NetView interface module unavailable: CNMCNETV”

v If you see any of the following symptoms, the NetView APSERV command is not running:

– A message in RKLVLOG, stating “NetView PPI send buffer rejected: 26”

– A return code of 9 in the Action Status pop-up window after a Take Action command is issued

– Message KRAIRA002 in RKLVLOG, similar to "KRAIRA002, Executed <DA,L> with status 9,Producer(Automation Command)

v If you see “NetView PPI send buffer rejected: 24” in the RKLVLOG, the NetView for z/OS SubsystemInterface is not active.

v If you see “NetView PPI send buffer rejected: 28” in the RKLVLOG, the Program-to-Program Interfacehas not been enabled.


Enable RACF authorization of Take Action commandsAs of fix pack 1 for IBM Tivoli Monitoring Version 6.2.3, all z/OS Take Action commands issued by theOMEGAMON XE agents, plus any other agents based on the Tivoli Management Services framework thatrun on z/OS, can now be associated with the Tivoli Enterprise Portal userid instead of the userid of thestarted task running the agent; this allows you to authorize the use of Take Action commands by individualportal server users while restricting it from others. You can secure these userids (or the RACF groups theyare in) via standard security objects provided by your site's security product; for RACF, these are theOPERCMDS facility class and its profiles.

Note: This enhancement does not alter the existing behavior of:

v Prefix-style Take Action commands such as those issued by OMEGAMON XE for CICS and prefixedwith CP:. These are still secured by the agent-specific security profiles set up for that purpose.

v Commands already protected by the OMEGAMON NetView Take Action command security facility.

v Commands issued by either the OMEGAMON classic interfaces or the OMEGAMON CUA interfacesand covered by their command security.

As initially installed, z/OS Take Action commands are associated with the userid of the agent started task(the previous behavior). To take advantage of the new security behavior for all agents in a particularruntime environment, create a new member called KGLUMAP in your RKANPARU data set, and add to itat least a one-line comment such as the following:* z/OS Take Action commands now secured

This turns on the new security feature so that all z/OS Take Action commands issued by all agents in thisruntime environment will be associated with the Tivoli Enterprise Portal userid instead of the started taskuserid.

To revert to the old behavior of using the userid of the started task as the issuer of the z/OS commandsfor a particular agent (while retaining the new behavior for other agents), place this line in the appropriateKxxENV member in RKANPARU, where xx is the two-character agent identifier:KGL_COMMAND_AUTHOR_SECURITY_REQUIRED=N

All successful and failed command executions create entries in the console log. The agent also createsaudit records for all automation command actions. On z/OS, these audit records are written to the SMFaudit repository (as described in “Whether to enable the auditing function” on page 17).

Before activating this feature, you also must ensure that every Tivoli Enterprise Portal userid (and theRACF groups that contain it) that either manually invokes Take Action commands or indirectly invokesthem via situations or policies are connected to the appropriate RACF OPERCMDS profiles. Otherwise,RACF may fail some of your z/OS Take Action commands.

1. The user ID that last updated an enterprise situation or a policy is the user ID that gets authenticatedfor the Take Action command associated with the situation or policy.

2. The user ID defined in the <LSTUSRPRF> segment for a private situation is the user ID that getsauthenticated for the Take Action command associated with the situation. If the segment is not defined,the default user ID is AGENTCFG.

If your Tivoli Enterprise Portal userids aren't currently set up in RACF (for example, if you're usingdistributed LDAP to authenticate your site's Tivoli Enterprise Portal userids), you must either:

v Add your Tivoli Enterprise Portal userids to RACF, and connect them to the appropriate OPERCMDSprofiles.

v Use the userid mapping capability (as described in the next section) to map Tivoli Enterprise Portaluserids to new or existing RACF userids that you will connect to the appropriate OPERCMDS profiles.


Setting up the userid mapping capabilityTo map Tivoli Enterprise Portal userids to new or existing RACF userids for Take Action validation, createmember KGLUMAP in the RKANPARU data set, and add to it one or more one-line mappings of this form:tepuser1 racfuser1tepuser2 racfuser2tepuser3 racfuser3

where tepuser is the 1- to 10-character Tivoli Enterprise Portal userid, and racfuser is the 1- to8-character RACF userid. The tepuser field (but only that field) allows a trailing * to indicate a wildcard, asin these examples:tepuser* racfuserAsys* racfuserB

Note that no TSO or OMVS segments are required for any new RACF userids you choose, since theywon't be used to actually log on to z/OS. Instead, they are used only for authorization against theOPERCMDS facility profiles.



Part 4. Appendixes



Appendix A. Documentation library

This appendix contains information about the publications related to the OMEGAMON XE products and toIBM Tivoli Monitoring and the commonly shared components of Tivoli Management Services. Thesepublications are listed in the following categories:

v “IBM Tivoli Monitoring library”

v “Shared OMEGAMON XE publications” on page 161

v “Related publications” on page 162

See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide, SC23-8816, forinformation about accessing and using the publications. You can find the Documentation Guide in the IBMTivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

To find a list of new and changed publications, click What's new on the Welcome page of the IBM TivoliMonitoring and OMEGAMON XE Information Center. To find publications from the previous version of aproduct, click Previous information centers on the Welcome page for the product.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring and about the commonly sharedcomponents of Tivoli Management Services:

v IBM Tivoli Monitoring: Quick Start Guide, GI11-8058

Introduces the components of IBM Tivoli Monitoring.

v IBM Tivoli Monitoring: Installation and Setup Guide, GC32-9407

Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows, Linux,and UNIX systems.

v IBM Tivoli Management Services on z/OS: Program Directory for IBM Tivoli Management Services onz/OS, GI11-4105

Gives instructions for the SMP/E installation of the Tivoli Management Services components on z/OS.

v IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS,SC27-2313

Gives detailed instructions for using the Configuration Tool to configure Tivoli Enterprise MonitoringServer on z/OS systems. Includes scenarios for using batch mode to replicate monitoring environmentsacross the z/OS enterprise. Also provides instructions for setting up security and for adding applicationsupport to a Tivoli Enterprise Monitoring Server on z/OS.

v IBM Tivoli Monitoring: Administrator's Guide, SC32-9408

Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v IBM Tivoli Monitoring: High-Availability Guide for Distributed Systems, SC23-9768

Gives instructions for several methods of ensuring the availability of the IBM Tivoli Monitoringcomponents.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/


v Tivoli Enterprise Portal online help

Provides context-sensitive reference information about all features and customization options of theTivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli Enterprise Portal.

v IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide, SC32-9409

Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons and detailedinstructions for all Tivoli Enterprise Portal features.

v IBM Tivoli Monitoring: Command Reference, SC32-6045

Provides detailed syntax and parameter information, as well as examples, for the commands you canuse in IBM Tivoli Monitoring.

v IBM Tivoli Monitoring: Troubleshooting Guide, GC32-9458

Provides information to help you troubleshoot problems with the software.

v IBM Tivoli Monitoring: Messages, SC23-7969

Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS andTMS:Engine).

v IBM Tivoli Universal Agent User's Guide, SC32-9459

Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM TivoliUniversal Agent enables you to use the monitoring and automation capabilities of IBM Tivoli Monitoringto monitor any type of data you collect.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461

Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and providesdescriptions, syntax, and return status codes for the API calls and command-line interface commands.

v IBM Tivoli Monitoring: Agent Builder User's Guide, SC32-1921

Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

Documentation for the base agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents as partof the product. If you purchased a monitoring agent product (for example, an OMEGAMON XE product)that includes the commonly shared components of Tivoli Management Services, you did not receive thebase agents.

The following publications provide information about using the base agents.

v Operating system agents:

– IBM Tivoli Monitoring: Windows OS Agent User's Guide, SC32-9445

– IBM Tivoli Monitoring: UNIX OS Agent User's Guide, SC32-9446

– IBM Tivoli Monitoring: Linux OS Agent User's Guide, SC32-9447

– IBM Tivoli Monitoring: i5/OS Agent User's Guide, SC32-9448

– IBM Tivoli Monitoring: UNIX Log Agent User's Guide, SC32-9471


v Agentless operating system monitors:

– IBM Tivoli Monitoring: Agentless Monitoring for Windows Operating Systems User's Guide,SC23-9765

– IBM Tivoli Monitoring: Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761

– IBM Tivoli Monitoring: Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763

– IBM Tivoli Monitoring: Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764

– IBM Tivoli Monitoring: Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762

v Warehouse agents:

– IBM Tivoli Monitoring: Warehouse Summarization and Pruning Agent User's Guide, SC23-9767

– IBM Tivoli Monitoring: Warehouse Proxy Agent User's Guide, SC23-9766

v System P agents:

– IBM Tivoli Monitoring: AIX Premium Agent User's Guide, SA23-2237

– IBM Tivoli Monitoring: CEC Base Agent User's Guide, SC23-5239

– IBM Tivoli Monitoring: HMC Base Agent User's Guide, SA23-2239

– IBM Tivoli Monitoring: VIOS Premium Agent User's Guide, SA23-2238

v Other base agents:

– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490

Shared OMEGAMON XE publicationsThe following publications provide information common to the OMEGAMON XE products:

v IBM Tivoli OMEGAMON XE Monitoring Agents on z/OS: Quick Start Guide, GI11-8918

Summarizes the installation and setup of an OMEGAMON XE monitoring agent on z/OS.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning andConfiguration Guide, SC23-9734

Gives instructions for planning and configuration tasks common to the components of TivoliManagement Services on z/OS and the OMEGAMON XE monitoring agents on z/OS.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Upgrade Guide, SC27-2500

Gives instructions for complete and staged upgrades to V4.2.0 of the OMEGAMON XE products.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common ParameterReference, SC14-7280

Provides reference information on parameters used for setting up runtime environments and configuringhub and remote Tivoli Enterprise Monitoring Servers on z/OS, including detailed descriptions of thePARMGEN parameters.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: PARMGEN Reference,SC22-5435

Provides detailed instructions and common configuration scenarios for creating and maintaining runtimeenvironments using the PARMGEN configuration method.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Enhanced 3270 User InterfaceGuide, IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Enhanced 3270 UserInterface Guide

Describes the features of the OMEGAMON enhanced 3270 user interface and provides operatinginstructions and reference material.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: End-to-End Response TimeFeature Reference, SC27-2303

Provides instructions and reference information for the End-to-End Response Time Feature, whichsupplies response time data to several OMEGAMON XE products.

Appendix A. Documentation library 161

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Reports for Tivoli CommonReporting, SC27-2304

Explains how to use the Tivoli Common Reporting tool to create reports from data displayed in the TivoliEnterprise Portal and stored in the Tivoli Data Warehouse database.

Related publicationsYou can find useful information about the OMEGAMON XE monitoring agents in the IBM Tivoli Monitoringand OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/, or inthe task-oriented OMEGAMON Integrated Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp.



http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp

http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp

Other sources of documentationYou can also obtain technical documentation about IBM Tivoli Monitoring and the OMEGAMON XEmonitoring agents from the following sources:

v Integrated Service Management Library


Integrated Service Management Library is an online catalog that contains integration documentation andother downloadable product extensions and accelerators.

v Redbooks

http://www.redbooks.ibm.com/

IBM Redbooks® and Redpapers include information about products from platform and solutionperspectives.

v Technotes

Technotes provide the latest information about known product limitations and workarounds. You can findTechnotes through the IBM Software Support website at http://www.ibm.com/software/support.

v Tivoli wikis on the IBM developerWorks® website

Tivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the home forinteractive wikis that offer best practices and scenarios for using Tivoli products. The wikis contain whitepapers contributed by IBM employees, and content created by customers and business partners.

Two of these wikis are of particular relevance:

– Tivoli Distributed Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home provides information about IBM Tivoli Monitoringand related distributed products, including IBM Tivoli Composite Application Management products.

– Tivoli System z® Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about the OMEGAMON XEproducts, NetView for z/OS, Tivoli Monitoring Agent for z/TPF, and other System z monitoring andapplication management products.

Appendix A. Documentation library 163


http://www.redbooks.ibm.com/


http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home


Appendix B. Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the followingways for you to obtain support:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html andfollow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the product's Troubleshooting Guide.


http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa


Appendix C. Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Any referenceto an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication. IBMmay make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including this one)and (ii) the mutual use of the information which has been exchanged, should contact:


IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the resultsobtained in other operating environments may vary significantly. Some measurements may have beenmade on development-level systems and there is no guarantee that these measurements will be the sameon generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at“Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registered trademarksof Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.


http://www.ibm.com/legal/copytrade.shtml

Glossary

Aactivity. One phase within a sequence of predefinedsteps called a policy that automate system responsesto a situation that has fired (that is, become true).

administration mode. See “workspace administrationmode” on page 181.

Advanced Encryption Standard. An encryptionalgorithm for securing sensitive but unclassified materialdesigned by the National Institute of Standards andTechnology (NIST) of the U.S. Department ofCommerce. AES is intended to be a more robustreplacement for the Data Encryption Standard. Thespecification calls for a symmetric algorithm (in whichthe same key is used for both encryption anddecryption), using block encryption of 128 bits andsupporting key sizes of 128, 192 and 256 bits. Thealgorithm was required to offer security of a sufficientlevel to protect data for the next 20 to 30 years. It hadto be easily implemented in hardware and software andhad to offer good defenses against various attacktechniques. AES has been published as FederalInformation Processing Standard (FIPS) 197, whichspecifies the encryption algorithm that all sensitive,unclassified documents must use.

AES. See “Advanced Encryption Standard.”

affinity. A label that classifies objects by managedsystem.

agent. Software installed on systems you want tomonitor that collects data about an operating system,subsystem, or application running on each such system.Because an executable file gathers information about amanaged system, there is always a one-to-onecorrespondence between them. Also called a TivoliEnterprise Monitoring Agent.

agentless monitor. An agentless monitor uses astandard API (such as SNMP or CIM) to identify andnotify you of common problems with the operatingsystem running on a remote computer. Thus, as theirname implies, the agentless monitors can retrievemonitoring and performance data without requiring OSagents on the computers being monitored. Theagentless monitors provide monitoring, data gathering,and event management for Windows, Linux, AIX,HP-UX, and Solaris systems.

agentless monitoring server. A computer that hasone or more agentless monitors running on it. Eachagentless monitoring server can support up to 10 activeinstances of the various types of agentless monitors, inany combination. Each instance can communicate with

up to 100 remote nodes, which means a singleagentless monitoring server can support as many as1000 monitored systems.

alert. A warning message or other indication thatappears at a console to indicate that something hasoccurred or is about to occur that may requireintervention.

alert monitor. A monitoring agent that monitors andrelays alert information to the monitoring server.Sources of alerts include message logs, systemconsoles, and network and system managementproducts.

algorithm. A set of well-defined rules for the solutionof a problem in a finite number of steps. For example, afull statement of an arithmetic procedure for evaluatingsin(x) to a stated precision.

API. See “Application Programming Interface.”

application. A software component or collection ofsoftware components that performs specificuser-oriented work (a task) on a computer. Examplesinclude payroll, inventory-management, andword-processing applications.

Application Programming Interface. A set of multiplesubprograms and data structures and the rules for usingthem that enables application development via aparticular language and, often, a particular operatingenvironment. An API is a functional interface suppliedby the operating system or by a separately licensedprogram that allows an application program written in ahigh-level language to use specific data or functions ofthe operating system or the licensed program.

arithmetic expression. A statement containing anycombination of values joined together by one or morearithmetic operators in such a way that the statementcan be processed as a single numeric value.

arithmetic operator. A symbol representing amathematical operation (addition, subtraction,multiplication, division, or exponentiation), such as +, -,*, /, or ^.

associate. The process of linking a situation with aNavigator item that enables a light to go on and asound to play for an open event. Predefined situationsare associated automatically, as are situations createdor edited through the Navigator item pop-up menu.When you open the Situation editor from the toolbar,any situations you create cannot be associated with aNavigator item during this editing session. You need toclose the Situation editor, and then open it again fromthe pop-up menu of the Navigator item with which thesituation is associated.


attribute. (1) A system or application element beingmonitored by the monitoring agent, such as DiskName and Disk Read/Writes Per Second. (2) Acharacteristic of a managed object; that is, a field inthe data structure of a managed object or in theworkspace associated with that managed object. (3) Afield in an ODBC-compliant database.

attribute group. A set of related attributes that canbe combined in a data view or a situation. When youopen the view or start the situation, data samples of theselected attributes are retrieved. Each type ofmonitoring agent has its own set of attribute groups.

autonomous-mode monitoring agents. Thesemonitoring agents run without communicating directlywith a Tivoli Enterprise Monitoring Server. Anautonomous agent can emit Simple NetworkManagement Protocol (SNMP) traps and EventIntegration Facility (EIF) events directly to an OMNIbusObjectServer for private situations (but not forenterprise situations) that have turned true.

Bbaroc files. Basic Recorder of Objects in C files defineevent classes for a particular IBM Tivoli EnterpriseConsole server. Baroc files also validate event formatsbased on these event-class definitions.

browser client. The software installed with the TivoliEnterprise Portal Server that is downloaded to yourcomputer when you start the Tivoli Enterprise Portal inbrowser mode. The browser client runs under thecontrol of a Web browser.

Ccapacity planning. The process of determining thehardware and software configuration required toaccommodate the anticipated workload on a system.

chart. A graphical view of data returned from amonitoring agent. A data point is plotted for eachattribute chosen and, for bar and pie charts, a dataseries for each row. Types of charts include pie, bar,plot, and gauge.

CIM. See “Common Information Model.”

class file. A file containing Java object code for asingle Java object class.

class loader. A Java component that loads Java classfiles.

client. An application that receives requested datafrom a server.

client/server architecture. An architecture in whichthe client (usually a personal computer or workstation)is the machine requesting data or services and the

server is the machine supplying them. Servers can bemicrocomputers, minicomputers, or mainframes. Theclient provides the user interface and may performapplication processing. In IBM Tivoli Monitoring theTivoli Enterprise Portal is the client to the TivoliEnterprise Portal Server, whereas the portal server isthe client to the Tivoli Enterprise Monitoring Server.

A database server maintains the databases andprocesses requests from the client to extract data fromor to update the database. An application serverprovides additional business-support processing for theclients.

Common Information Model. An XML-basedstandard for defining device and applicationcharacteristics so that system administrators andmanagement programs can monitor and control themusing the same set of tools, regardless of their differingarchitectures. CIM provides a more comprehensivetoolkit for such management functions than the SimpleNetwork Management Protocol.

Common Object Request Broker Architecture. Anindustry specification for the design and standardizationof different types of object request brokers (ORBs).ORBs allow different computers to exchange objectdata; CORBA enables ORBs from different softwarevendors (often running under dissimilar computersystems and operating systems) to exchange objectdata. CORBA facilitates communication among programcomponents in a network using objects. The TivoliEnterprise Portal Server is a CORBA implementation.

condition. An expression that evaluates to either trueor false. It can be expressed in natural language text, inmathematically formal notation, or in amachine-readable language.

Configuration Tool, z/OS (ICAT). A REXX-based toolfor configuring OMEGAMON XE products running onzSeries® systems, after they have been installed usingthe System Modification Program/Extended (SMP/E)tool.

Configure History permission. Your userid musthave Configure History permission to open the HistoryCollection Configuration window for setting up historyfiles and data rolloff. If you do not have this permission,you cannot see the menu item or tool for historicalconfiguration.

CORBA. See “Common Object Request BrokerArchitecture.”

critical state. The indication that a situationassociated with a Navigator item is in an unacceptablestate and that you must take corrective action. Thecritical state is represented by the color red.

Custom Navigator Views permission. Your useridhas a Modify check box for the Custom Navigator Views


feature. This permission must be enabled for you toopen the Navigator view editor to maintain and updateNavigator views.

DData Encryption Standard. A widely used method ofprivate-key data encryption that originated at IBM in1977 and was adopted by the U.S. Department ofDefense. DES supports 72 quadrillion or more possibleencryption keys; for each message, the key is chosen atrandom from among this enormous number of possiblekeys. Like all other private-key cryptographic methods,both the sender and the receiver must know and usethe same private key.

DES applies a 56-bit key to each 64-bit block of data.Although this is considered strong encryption, manycompanies use triple DES, which applies three keys insuccession.

database. A collection of both interrelated andindependent data items that are stored together on acomputer disk to serve multiple applications.

data source name. The name that is stored in thedatabase server and that enables you to retrieveinformation from the database through ODBC. The DSNincludes such information as the database name,database driver, userid, and password.

data sources. Data pertaining to J2EE data sources,which are logical connections to database subsystems.

data warehouse. A central repository for all orsignificant parts of the data that an organization'sbusiness systems collect.

DB2 for the workstation. IBM's DB2® Database forLinux, UNIX, and Windows systems is a relationaldatabase management system that runs on desktopcomputers. You install a DB2 database on the samesystem as the Tivoli Enterprise Portal Server; it storesthe portal server's queries, customized workspaces,userids, and custom Navigator views. DB2 for theworkstation can also serve as the data repository for theTivoli Data Warehouse, which stores historicalmonitoring information.

default. Pertaining to an attribute, value, or optionthat is assumed when none is explicitly specified.

Demilitarized Zone. The area of a World Wide Webapplication that a company can use to host Internetservices without allowing unauthorized access.

Derby. An open-source, public-domain, relationaldatabase management system implemented in Javaand designed to conform to accepted databasestandards (such as SQL and JDBC). Derby came aboutwhen IBM contributed its Cloudscape databasemanager to the Apache project and features a smallmachine footprint. IBM Tivoli Monitoring implements

Derby as an embedded database within its TivoliEnterprise Portal Server; in other words, the databaseis installed with the portal server, and it runs within theportal server's Java virtual machine.

DES. See “Data Encryption Standard.”

desktop client. Software supplied with IBM TivoliMonitoring that you install on a workstation that youplan to use for interacting with the Tivoli EnterprisePortal Server and the Tivoli Enterprise MonitoringServer. The desktop Tivoli Enterprise Portal clientprovides the graphical user interface into the IBM TivoliMonitoring network.

detailed attribute name. The name used in formulas,expert advice, Take Action commands, and headersand footers when referencing a monitoring agentattribute. In the Properties and Situation editors, youclick Show Formula, and then check Show detailedformula to see the detailed attribute name.

display item. An attribute designated to furtherqualify a situation. With a display item set for amultiple-row attribute group, the situation continues tolook at the other rows in the sample and opens moreevents if other rows qualify. The value displays in theevent workspace and in the message log and situationevent console views. You can select a display itemwhen building a situation with a multiple-row attributegroup.

distribution. The managed systems on which thesituation is running.

DLL. See “Dynamic Link Library.”

DMZ. See “Demilitarized Zone.”

drill down. To access information by starting with ageneral category and moving through the hierarchy ofinformation, for example, in a database, to move fromfile to record to field.

DSN. See “data source name.”

DVIPA. See “Dynamic Virtual IP Addressing.”

Dynamic Link Library. A composite of one or moreexecutable objects that is bound together by a linkingprocedure and loaded at run time (rather than when theapplication is linked). The code and data in a dynamiclink library can be shared by several applicationssimultaneously. DLLs apply only to Windows operatingenvironments.

Dynamic Virtual IP Addressing. This feature of IPallows System Z to reassign IP addresses in event of afailure in an application, TCP/IP stack, or LPAR.

Glossary 171

EEIB. See “Enterprise Information Base.”

EIF. See “Event Integration Facility.”

endcode. You assign endcodes in a policy when youconnect one activity to another. The endcode indicatesthe result of this activity that triggers the next activity.

Enterprise Information Base. A database used by theTivoli Enterprise Monitoring Server that serves as arepository of shared objects for all systems across yourenterprise. The EIB stores all persistent data, includingsituations, policies, user definitions, andmanaged-object definitions.

enterprise situation. A situation that is created for aTivoli Enterprise Monitoring Agent that reports events tothe Tivoli Enterprise Monitoring Server to which itconnects. Enterprise situations are centrally defined atthe monitoring server and distributed at agent startup.See also “situation” on page 178.

event. An action or some occurrence, such as runningout of memory or completing a transaction, that can bedetected by a situation. Events cause a change in thestate of a managed object associated with a situation,thereby make the situation true and causing an alert tobe issued.

event indicator. The colored icon that displays over aNavigator item when an event opens for a situationrunning on that item.

Event Integration Facility. An applicationprogramming interface that external applications caninvoke to create, send, or receive events. These eventsare in the same format as Tivoli Enterprise Consoleevents and are referred to as either EIF events orTEC/EIF events.

event item. A Navigator item that shows when youopen the event workspace for a true situation (byselecting it from the event flyover listing or from thesituation event console pop-up menu).

event sound. The sound file that plays when an eventopens. This sound file is set in the Situation editor whenthe situation is associated with a Navigator item andcan differ for different Navigator items.

expert advice. A description within the Situation editorof each situation provided with a monitoring agent tohelp you quickly understand and interpret events arisingfrom it.

Extensible Markup Language. A data-descriptionlanguage derived from Standard Generalized MarkupLanguage (SGML); also a tool for encoding messagesso they describe their own fields. You use XML toformat a document as a data structure. As programobjects, such documents can have their contents and

data hidden within the object, which allows you tocontrol who can manipulate the document and how. Inaddition, documents can carry with them theobject-oriented procedures called methods. The XMLstandard aids in exchanging data between applicationsand users.

Ffilter criteria. These criteria limit the amount ofinformation returned to the data view in response to aquery. You can apply a prefilter to the query to collectonly certain data, or apply a postfilter to the viewproperties to show only certain data from theinformation collected.

fix pack. A tested collection of all cumulativemaintenance for a product, up to the release of the fixpack. It can also contain fixes that have not beenshipped previously, but it might contain no new function.

Ggeoreferenced map. A special type of graphic thathas built-in knowledge of latitude and longitude and canbe zoomed into and out of quickly. The TivoliEnterprise Portal uses proprietary .IVL files generatedwith the map-rendering component. These files cannotbe opened or saved in a graphics editor.

GSKit. The Global Security Toolkit provides SSL(Secure Sockets Layer) processing within protocolssuch as SPIPE and HTTPS. On z/OS systems, GSKit isknown as the Integrated Cryptographic Service Facility,or ICSF.

Hhierarchical. Describes data that is organized oncomputer systems using a hierarchy of containers, oftencalled folders (that is, directories) and files. In thisscheme, folders can contain other folders and files. Thesuccessive creation of folders within folders creates thelevels of organization, which is the hierarchy.

historical collection. A definition for collecting andstoring data samples for historical reporting. Thehistorical collection identifies the attribute group, anyrow filtering you have assigned, the managed systemdistribution, frequency of data collection, where tostore it for the short term, and whether to save datalong term (usually to the Tivoli Data Warehouse).

historical data management. The procedures appliedto short-term binary history files that roll off historicaldata to either the Tivoli Data Warehouse or todelimited text files (the krarloff utility on UNIX orWindows systems; ddname KBDXTRA for the z/OSPersistent Datastore), and then delete entries in the


short-term history files over 24 hours old, therebymaking room for new entries.

hot standby. A redundant Tivoli EnterpriseMonitoring Server running on a distributed platformthat, if the primary or hub monitoring server shouldfail, assumes the responsibilities of the failed monitoringserver.

HTTP. The Hypertext Transfer Protocol is a suite ofInternet protocols that transfer and display hypertextdocuments within Web browsers.

HTTP sessions. Data related to invocations of specificWorld Wide Web sites.

HTTPS. The Secure Hypertext Transport Protocol is animplementation of the Hypertext Transport Protocol(HTTP) that relies on either the Secure Sockets Layer(SSL) API or the Transport Layer Security (TLS) API toprovide your users with secure access to your site'sWeb server. These APIs encrypt and then decrypt userpage requests as well as the pages returned by theWeb server.

hub. (1) A central host system that collects the statusof situations running on your systems. (2) Themonitoring server that your site has selected to act asthe focal point to which all portal servers and remotemonitoring servers in this monitored network connect. Aremote monitoring server passes its collected data tothe hub to be made available to clients, creating anenterprise-wide view.

IIBM Tivoli Monitoring. A client/serverimplementation for monitoring enterprise-wide computernetworks that comprises a Tivoli EnterpriseMonitoring Server, an application server known as theTivoli Enterprise Portal Server, one or more TivoliEnterprise Portal clients, and multiple monitoringagents that collect and distribute data to the monitoringserver.

IIOP. See “ Internet Inter-ORB Protocol.”

input data. Data provided to the computer for furtherprocessing. See also “output data” on page 176.

integral Web server. A proprietary Web serverdeveloped for IBM Tivoli Monitoring that is installedand configured automatically with the Tivoli EnterprisePortal Server. You enter the URL of the integral Webserver to start the Tivoli Enterprise Portal client inbrowser mode.

Internet Inter-ORB Protocol. An Internetcommunications protocol that runs on distributedplatforms. Using this protocol, software programs writtenin different programming languages and running ondistributed platforms can communicate over the Internet.

IIOP, a part of the CORBA standard, is based on theclient/server computing model, in which a clientprogram makes requests of a server program that waitsto respond to client requests. With IIOP, you can writeclient programs that communicate with your site'sexisting server programs wherever they are locatedwithout having to understand anything about the serverother than the service it performs and its address(called the Interoperable Object Reference, IOR, whichcomprises the server's port number and IP address).

Interoperable Object Reference. Connects clients tothe Tivoli Enterprise Portal Server. The IOR identifiesa remote object, including such information as name,capabilities, and how to contact it. The URL may includean IOR because it goes through the Web server; theportal server uses it to tell the client which IOR to fetch.After it does that, the portal server extracts the host andport information and tells the client where to route therequest.

interval. The number of seconds that have elapsedbetween one sample and the next.

IOR. See “Interoperable Object Reference.”

JJava Database Connectivity. A standard API thatapplication developers use to access and updaterelational databases (RDBMSes) from within Javaprograms. The JDBC standard is based on the X/OpenSQL Call Level Interface (CLI) and complies with theSQL-92 Entry Level standard; it provides aDBMS-independent interface that enablesSQL-compliant database access for Java programmers.

Java Management Extensions. A set of Java classesfor application and network management in J2EEenvironments. JMX provides Java programmers a set ofnative Java tools called MBeans (managed beans) thatfacilitate network, device, and application management.JMX provides a Java-based alternative to the SimpleNetwork Management Protocol.

JDBC. See “Java Database Connectivity.”

JMX. See “Java Management Extensions.”

LLDAP. See “Lightweight Directory Access Protocol.”

Lightweight Directory Access Protocol. A protocolthat conforms to the International StandardsOrganization's X.500 directory standard that usesTCP/IP to access directory databases whereapplications can store and retrieve common namingand location data. For example, applications can use

Glossary 173

LDAP to access such directory information as emailaddresses, service configuration parameters, and publickeys.

location broker. The component that managesconnections for the hub monitoring server, enabling it tofind all other Tivoli Management Servicescomponents, including remote monitoring servers, theTivoli Enterprise Portal Server, and monitoringagents.

Mmanaged object. An icon created in the TivoliEnterprise Portal from a managed object template thatrepresents resources you monitor using situations.Managed objects are converted to items in theNavigator's Logical view.

managed system. A particular operating system,subsystem, or application in your enterprise where amonitoring agent is installed and running. A managedsystem is any system that IBM Tivoli Monitoring ismonitoring.

managed system group. (Formerly managed systemlist.) A named, heterogeneous group of both similar anddissimilar managed systems organized for thedistribution of historical collections, situations, andpolicies, and for assignment to queries and items incustom Navigator views. For example, you might createa managed system group named IT_London for ageographic region and another named Credit_Approvalfor a functional area of your organization.

If a managed system group is updated (usually when aconstituent managed system is added or deleted), thenall the historical collections, situations, and policies thatuse that group are redistributed to all managed systemsin the group. Managed system groups are created,modified, or deleted either by the Tivoli EnterprisePortal's Object Group editor or via the tacmd CLIcommand with the createsystemlist, editsystemlist, ordeletesystemlist keywords; they are maintained by theTivoli Enterprise Monitoring Server.

MBeans. Managed beans are Java objects thatrepresent managed resources such as devices,services, and applications. The management functionsare provided by the MBean server.

MDM. See “Multi-domain Management.”

method. In object-oriented programming, the softwarethat implements an object's behavior as specified by anoperation.

Microsoft Management Console. This feature ofMicrosoft's various Windows Server environmentsprovides a centralized, consistent, and extensibleinterface to Windows' various monitoring andmanagement utilities. In particular, MMC manages

directory services, job scheduling, event logging,performance monitoring, and user environments.

middleware. Software that enables the exchange ofinformation between components in a distributedcomputing environment. The middleware is thedata-exchange and communications channel that allowsprograms to cooperate with each other without having toknow details about how they are implemented or wherethey are deployed. Middleware typically provides arange of related facilities such as persistence, auditing,and the ability to build a transactional unit of work.IBM's CICS and WebSphere® MQ are examples ofmiddleware.

migrating. Preserving your customized configurationdata so you can use it again after installing a newerversion of the product.

MMC. See “Microsoft Management Console.”

monitor. An entity that performs measurements tocollect data pertaining to the performance, availability,reliability, or other attributes of applications or thesystems on which those applications rely. Thesemeasurements can be compared to predefinedthresholds. If a threshold is exceeded, administratorscan be notified, or predefined automated responses canbe performed.

monitor interval. A specified time, scalable toseconds, minutes, hours, or days, for how often themonitoring server checks to see if a situation hasbecome true. The minimum monitor interval is 30seconds; the default value is 15 minutes.

monitoring. Running a hardware or software tool tomonitor the performance characteristics of a system.

Multi-domain Management. This feature gives youthe ability to administer multiple IBM Tivoli Monitoringdomains from a single, central location. This type ofmanagement consolidates Tivoli Monitoringconfiguration artifacts into a central database wherethey can be managed independently of the monitoringserver. Your hub monitoring server operations will begeneralized across multiple IBM Tivoli Monitoringdomains. MDM has the following capabilities:v Promotion of existing configuration artifacts from an

editor domain into a standard store.v Export of configuration artifacts from multiple domains

into a single relational database under a singlenamespace for management and reporting purposes.

v Import of configuration artifacts into multiple IBMTivoli Monitoring domains.

v Ease of monitoring agent migration operations,configuration changes, and compliance withconfiguration standards.

v Server-side audit of all operations.


Nnamespace. A namespace uniquely identifies a set ofnames so that there is no ambiguity when objectshaving different origins but the same names aremingled. For example, within the Extensible MarkupLanguage (XML), an XML namespace is a collection ofelement type and attribute names. These elementtypes and attribute names are uniquely identified by thename of the unique XML namespace that containsthem. In an XML document, any element type orattribute name can thus require a two-part nameconsisting of the name of its namespace and then itslocal (functional) name, separated by a colon (:).

It is possible (and often desirable) to create multiplenamespaces; this may be essential in environmentswhere different sets of information are maintained in acommon repository like LDAP.

NAT. See “Network Address Translation.”

Navigator. The upper-left pane of the TivoliEnterprise Portal window. The Navigator Physical viewshows your network enterprise as a physical hierarchyof systems grouped by platform. You can also defineother views that create logical hierarchies grouped asyou specify, such as by department or function.

Network Address Translation. A scheme used bylocal-area networks (LANs) to establish an internal andexternal set of IP addresses. Internal IP addresses arekept private and must be translated to and from theexternal addresses for outbound and inboundcommunications. NAT is often used in firewallconfigurations.

Network File System. A client/server file systemdeveloped by Sun Microsystems that, once mounted(that is, made accessible), allows a user on an NFSclient to view, store, and update files on a remotecomputer (the NFS server) as though they were on theuser's own computer. The portion of the mounted filesystem that each user can access and in what ways isdetermined by the user's own file-access privileges andrestrictions.

Both the NFS server and client use TCP/IP's UserDatagram Protocol as the mechanism for sending filecontents and updates back and forth. NFS has beendesignated a file server standard; it uses the RemoteProcedure Call method of communication betweencomputers.

NFS. See “Network File System.”

node. (1) In networking, a point capable of sendingand receiving data. A node can be a device, such asprinter or workstation, a system, a storage location on adisk, or a single computer. (2) Any managed system,such as an AIX-based pSeries® server, that IBM TivoliMonitoring is monitoring. A node can also be a

managed system of subnodes, all of which are beingmanaged as components of the primary node.

non-agent bundles. You can use these custombundles to remotely deploy components that need notconnect to a Tivoli Enterprise Monitoring Server,such as those that support other Tivoli products like IBMTivoli Netcool/OMNIbus.

Oobject. An instance of a class, which comprises animplementation and an interface. An object reflects itsoriginal, holding data and methods and responds torequests for services. CORBA defines an object as acombination of state and a set of methods characterizedby the behavior of relevant requests.

ODBC. See “Open Database Connectivity” on page176.

OMEGAMON Dashboard Edition (OMEGAMON DE).The OMEGAMON implementation that includes all thefeatures of the Tivoli Enterprise Portal provided withOMEGAMON XE, plus application-integrationcomponents that facilitate an enterprise-wide view ofyour computing environment. OMEGAMON DE'sworkspaces integrate the data from multipleOMEGAMON Monitoring Agents into onenetwork-wide view.

OMEGAMON Extended Edition (OMEGAMON XE).The IBM Tivoli Monitoring implementation of a singleOMEGAMON Monitoring Agent. OMEGAMON XEdisplays the monitoring data from each OMEGAMONMonitoring Agent independently, without integrating itinto the enterprise-wide workspaces provided byOMEGAMON DE.

OMEGAMON Monitoring Agent. The softwareprocess that probes a managed z/OS system orsubsystem (such as CICS) for data. The monitoringagent sends that monitoring information back to theTivoli Enterprise Monitoring Server and then on tothe Tivoli Enterprise Portal Server to be formatted intotable and chart views for display on a Tivoli EnterprisePortal client.

OMEGAMON Tivoli Event Adapter. Invokes theEvent Integration Facility API to synchronize IBMTivoli Monitoring events with the IBM Tivoli EnterpriseConsole product. OTEA is a component of the TivoliEnterprise Monitoring Server; it forwards IBM TivoliMonitoring events to Tivoli Enterprise Console andmaps them to their corresponding Tivoli EnterpriseConsole event classes based on the situation name'ssuffix, either _Warning or _Critical.

Integrating these products requires two parts: a TivoliEnterprise Monitoring Server piece (included with IBMTivoli Monitoring version 6.1 and subsequent releases)called the OMEGAMON Tivoli Event Adapter, and a

Glossary 175

Tivoli Enterprise Console piece called the SituationUpdate Forwarder that is installed on the TivoliEnterprise Console server.

Open Database Connectivity. A standard API foraccessing data in both relational and nonrelationaldatabase systems using procedural, non-object-basedlanguages such as C. Using this API, databaseapplications can access data stored in databasemanagement systems on a variety of computers even ifeach database management system uses a differentdata storage format and programming interface.

Tivoli Enterprise Portal users can access the Queryeditor to write custom SQL queries for creating viewsthat retrieve data from ODBC-compliant databases.

operator. (1) The action to be performed on one ormore attributes when evaluating an expression. Thetypes of operators the Tivoli Enterprise Portalsupports are arithmetic, comparison, Boolean, andlogical. (2) The symbol (such as +, -, or *) thatrepresents that operation (in these examples, addition,subtraction, multiplication).

OTEA. See “OMEGAMON Tivoli Event Adapter” onpage 175.

output data. Data resulting from computer processing.See also “input data” on page 173.

Pparameter. A value or reference passed to a function,command, or program that serves as input or to controlactions. The value is supplied by a user or by anotherprogram or process.

PDS. See “Persistent Datastore.”

PerfMon. See “Performance Monitor”

performance. A major factor in measuring systemproductivity. Performance is determined by acombination of throughput, response time, andavailability.

performance analysis. The use of one or moreperformance tools to investigate the reasons forperformance improvement or deterioration.

Performance Monitor (PerfMon). The WindowsPerformance Monitor is an SNMP-basedperformance-monitoring tool for Windows environments.PerfMon monitors network elements such as computers,routers, and switches.

Persistent Datastore. A set of z/OS data sets whereIBM Tivoli Monitoring running on z/OS systems storeshistorical monitoring data.

platform. The operating system on which themanaged system is running, such as z/OS or Linux.

The Navigator's Physical mapping places the platformlevel under the Enterprise level.

policy. A set of automated system processes that canperform actions, schedule work for users, or automatemanual tasks, frequently in response to events.Policies are the IBM Tivoli Monitoring automation tool;they comprise a series of automated steps, calledactivities, whose order of execution you control.

In most cases, a policy links a Take Action commandto a situation that has turned true. When started, thepolicy's workflow progresses until all activities havebeen completed or until the Tivoli Enterprise Portaluser manually stops the policy. You can create bothpolicies that fully automate workflow strategies andthose that require user intervention. As with situations,policies are distributed to the managed systems youwant to monitor and to which you are sendingcommands.

presentation files. Two files installed with the TivoliEnterprise Portal Server, presentation.dat andpresentation.idx, that store workspace definitions, linkdefinitions, and terminal emulator scripts.

private situation. A situation that is defined in anXML-based private configuration file for the local TivoliEnterprise Monitoring Agent or Tivoli System MonitorAgent and that does not interact with a TivoliEnterprise Monitoring Server. Such events can besent via either EIF or SNMP alerts to a receiver suchas IBM Tivoli Enterprise Console or Netcool/OMNIbus.See also “situation” on page 178.

product code. The three-letter code used by IBMTivoli Monitoring to identify the product component. Forexample, the product code for IBM Tivoli Monitoring forWebSphere Application Server is KWE.

Properties editor. A multi-tabbed window forspecifying the properties of the individual views thatmake up a workspace, as well as the generalworkspace properties.

pure event. A pure event is one that occursautomatically, such as when a paper-out conditionoccurs on the printer or when a new log entry is written.Situations written to notify you of pure events remaintrue until they are manually closed or automaticallyclosed by an UNTIL clause. See also “event” on page172.

Qquery. A particular view of specified attributes ofselected instances of a set of managed-object classes,arranged to satisfy a user request. Queries are writtenusing SQL.


query permissions. . The set of Tivoli EnterprisePortal Server authorities that allow your user ID tocreate or update queries.

v If you do not see the Queries tool, your user ID doesnot have View or Modify Query permissions.

v If you can see the tool but it is disabled, your user IDdoes not have Workspace Author Mode permission.

v If you can open the Query editor but the tools aredisabled, your user ID does not have Modify Querypermission.

Rremote. A remote monitoring server collectsmonitoring data from a subset of your site's monitoringagents and passes its collected data to the hub TivoliEnterprise Monitoring Server to be made available toone or more Tivoli Enterprise Portal clients throughthe Tivoli Enterprise Portal Server, thereby creatingan enterprise-wide view.

remote deployment. Using IBM Tivoli Monitoringsoftware, you can deploy agents and other non-agent,Tivoli Management Services-based components toremote nodes without your having to sign onto thosenodes and perform the installation and configurationsteps yourself. Remote deployment requires two pieceson the destination node: (1) a bundle containing thecomponent code and the instructions for installing andconfiguring it and (2) an operating-system agent to readthe bundle and perform the installation andconfiguration steps.

Remote Procedure Call. A protocol based on theOpen Software Foundation's Distributed ComputingEnvironment (DCE) that allows one program to requestservices from a program running on another computerin a network. RPC uses the client/server model: therequesting program is the client, and the respondingprogram is the server. As with a local procedure call(also known as a function call or a subroutine call),an RPC is a synchronous operation: the requestingprogram is suspended until the remote procedurereturns its results.

rolloff. The transfer of monitoring data to a datawarehouse.

RPC. See “Remote Procedure Call.”

RTE. See “runtime environment.”

runtime environment. A group of execution librariesthat provide an operational environment on a z/OSsystem. RTEs execute OMEGAMON products on az/OS image.

runtime libraries. Libraries in the runtimeenvironment that the product uses when it is startedand running.

Ssample. The data that the monitoring agent collectsfor the monitoring server instance. The interval is thetime between data samplings.

sampled event. Sampled events happen when asituation becomes true. Situations sample data atregular intervals. When the situation becomes true, itopens an event, which gets closed automatically whenthe situation goes back to false (or when you close itmanually). See also “event” on page 172.

Secure Sockets Layer. A security protocol forcommunication privacy that provides secureclient/server conversations. SSL provides transportlayer security (authenticity, integrity, and confidentiality)for a secure connection between a client and a server.

seed data. The product-provided situations,templates, policies, and other sample data includedwith a monitoring agent to initialize the TivoliEnterprise Monitoring Server's EnterpriseInformation Base. Before you can use a monitoringagent, the monitoring server to which it reports must beseeded, that is, initialized with application data.

SELinux. The National Security Agency'ssecurity-enhanced Linux (SELinux) is a set of patchesto the Linux kernel plus utilities that together incorporatea strong, flexible mandatory access control (MAC)architecture into the kernel's major subsystems.SELinux enforces the separation of information basedon confidentiality and integrity requirements, whichallows attempts to tamper with or bypass applicationsecurity mechanisms to be recorded and enables theconfinement of damage caused by malicious or flawedapplications.

server. An application that satisfies data and servicerequests from clients.

Simple Network Management Protocol. A TCP/IPtransport protocol for exchanging network managementdata and controlling the monitoring of network nodes ina TCP/IP environment. The SNMP software protocolfacilitates communications between different types ofnetworks. IBM Tivoli Monitoring uses SNMP messagingto discover the devices on your network and theiravailability.

Simple Object Access Protocol. The Simple ObjectAccess Protocol is a lightweight, XML-based interfacethat vendors use to bridge remote procedure callsbetween competing systems. SOAP makes itunnecessary for sites to choose betweenCORBA/Java/EJB and Microsoft's COM+.

Because XML and SOAP are platform- andlanguage-neutral, users can mix operating systems,programming languages, and object architectures yetmaintain business-component interoperability acrossplatforms: using SOAP, applications can converse with

Glossary 177

each other and exchange data over the Internet,regardless of the platforms on which they run.

single sign-on. This feature lets your IBM TivoliMonitoring users start other Tivoli web-enabledapplications from any Tivoli Enterprise Portal client(desktop, browser, or Java Web start), or to start theTivoli Enterprise Portal from those applications, withouthaving to re-enter their user credentials (userid andpassword). For SSO to function, User Authenticationmust be configured through the Tivoli Enterprise PortalServer for an external LDAP registry (such as MicrosoftActive Directory) that is shared by all participating Tivoliapplications. All the participating applications must beconfigured for SSO and must belong to the samesecurity domain and realm.

situation. The set of monitored conditions running ona managed system that, when met, creates an event.A situation comprises an attribute, an operator such asgreater than or equal to, and a value. It can be read as“If system_condition compared_to value is_true”. Anexample of a situation is: If CPU_usage > 90% TRUE.The expression “CPU_usage > 90%” is the situationcondition.

Situation Event Forwarder. This component of TivoliManagement Services maps situation events to EventIntegration Facility (EIF) events and uses the EIFinterface to send the events to a Tivoli EnterpriseConsole event server or to an OMNIbus EIF probe (theEIF receivers). The event receivers receive theforwarded events, and expand and format them for theevent servers. On the Tivoli Enterprise Console orOMNIbus console, users can view, acknowledge, orreset situation events. The updated situation status isreturned to the originating hub monitoring server andreflected in the Tivoli Enterprise Console or OMNIbusconsole.

Situation Update Forwarder. The Situation UpdateForwarder is a Java- and CORBA-based backgroundprocess for communication between IBM TivoliEnterprise Console and a particular Tivoli EnterpriseMonitoring Server running under IBM Tivoli Monitoringversion 6.1 and subsequent releases. Your site mustinstall this component on the Tivoli Enterprise Consoleserver; for instructions, see the IBM Tivoli EnterpriseConsole Installation Guide.

SNMP. See “Simple Network Management Protocol”on page 177.

SOAP. See “Simple Object Access Protocol” on page177.

sockets. Refers to the sockets method of passing databack and forth between a networked client and serveror between program layers on the same computer.

sound. The WAV file that plays whenever a situationbecomes true for the current Navigator item. Sound is

assigned to the Navigator item for a situation in thesame way a state is assigned.

SPIPE. A secure pipe is an implementation of theInternet Protocol's pipe specification that uses theSecure Sockets Layer API. Using SPIPE, yourcorporate Web server can securely access internalservers that are not based on the HTTPS protocol,while retaining their ability to process HTTP requests.

SQL. See “Structured Query Language.”

SSL. See “Secure Sockets Layer” on page 177.

SSM. See “System Service Monitors” on page 179.

SSO. See “single sign-on.”

state. The severity of the situation event: critical,warning, or informational. Indicated by a colored eventindicator, state is set in the Situation editor and can bedifferent for different Navigator items.

status. The true or false condition of a situation.

Structured Query Language. A standards-basedprogramming language for extracting information fromand updating information within a relational database.The Query editor enables you to write SQL queries toODBC data sources for retrieval and display in tableand chart views.

subnetwork. A configuration wherein a single IPnetwork address is split up so it can be used on severalinterconnected local networks. Subnetworking is a localconfiguration; outside it appears as a single IP network.

SUF. See “Situation Update Forwarder.”

Summarization and Pruning agent. One of the IBMTivoli Monitoring base agents, the Summarization andPruning agent keeps the data warehouse from growingtoo large by summarizing and pruning your storedhistorical data at intervals you set. For every attributegroup that has data collection configured, you specifyhow often to aggregate (summarize) data in the TivoliData Warehouse and the length of time to delete(prune) data from the warehouse.

symbol. Represents a variable that can be added toheader or footer text for data views, expert-advice text,or query specification. The detailed attribute name isenclosed in dollar signs, such as $ORIGINNODE$, andresolves to the attribute's value. For Tivoli EnterpriseMonitoring Server queries, == $NODE$ specifies themanaged systems from which to retrieve data. Forqueries to be used in link target workspaces, you cancreate symbols for attributes using the $symbolname$format.

System Monitor Agent. These agents wereintroduced with IBM Tivoli Monitoring V6.2.2 for nodesthat run the desktop operating systems (Windows,


Linux, UNIX). These agents operate only autonomously(that is, they run without a connection to a TivoliEnterprise Monitoring Server) and pass SNMP trapdata about operating system performance to an SNMPEvent Collector such as IBM Tivoli Netcool/OMNIbus'sMTTRAPD receiver.

No other IBM Tivoli Monitoring agents or othercomponents should be installed on the same node as aSystem Monitor Agent. The only exception to this rule isagents created with the Agent Builder tool for V6.2.2 orsubsequent.

System Service Monitors. The IBM TivoliNetcool/OMNIbus product provides System ServiceMonitors that support basic system-level monitoring ofnetwork components such as operating systems. Inaddition, OMNIbus provides ISMs (Internet ServiceMonitors) and ASMs (Application Service Monitors).

IBM System Z. Umbrella family name used whenreferring to multiple product lines or the IBM mainframeclass of products in general.

TTake Action. A Tivoli Enterprise Portal dialog boxfrom which you can enter a command or choose from alist of predefined commands. It also lists systems onwhich to effect the command, which is usually aresponse to an event.

Take Action command. A Take Action commandallows you to send commands to your managedsystems, either automatically, in response to asituation that has fired (that is, turned true), ormanually, as the Tivoli Enterprise Portal operatorrequires. With Take Action commands, you can enter acommand or select one of the commands predefined byyour product and run it on any system in your managednetwork. Thus you can issue Take Action commandseither against the managed system where the situationfired or a different managed system in your network.

target libraries. SMP/E-controlled libraries that containthe data installed from the distribution media.

task. A unit of work representing one of the steps in aprocess.

TCP/IP. See “Transmission Control Protocol/InternetProtocol” on page 180.

TDW. See “Tivoli Data Warehouse.”

telnet. A terminal emulation program used on TCP/IPnetworks. You can start a telnet session with anothersystem and enter commands that execute on thatsystem. A valid userid and password for that remotesystem are required.

TEPS/e. See “Tivoli Enterprise Portal Server extendedservices.”

threshold. (1) A level set in the system at which amessage is sent or an error-handling program is called.For example, in a user auxiliary storage pool, the usercan set the threshold level in the system values, andthe system notifies the system operator when that levelis reached. (2) A customizable value for defining theacceptable tolerance limits (maximum, minimum, orreference limit) for an application resource or systemresource. When the measured value of the resource isgreater than the maximum value, less than the minimumvalue, or equal to the reference value, an exception israised.

time-scheduling services. The Tivoli CommonReporting module uses the time-scheduling services toquery and manage report schedules and tasks.

timestamp. A data type that contains a seven-partvalue consisting of a date and a time expressed inyears, months, days, hours, minutes, seconds, andmicroseconds.

Tivoli Common Reporting. This reporting moduleallows a single point of access to reports generated bymultiple products. It interacts with either the BusinessIntelligence and Reporting Tools (BIRT) Designer or withthe Cognos® product for customizing reports andrunning defined reports. The time-scheduling serviceallows you to schedule report extraction and creation.

Tivoli Data Warehouse. This member of the IBMTivoli Monitoring product family stores Tivoli Monitoringagents' monitoring data in separate relationaldatabase tables so you can analyze historical trendsusing that enterprise-wide data. Reports generated fromTivoli Data Warehouse data provide information aboutthe availability and performance of your monitoredenvironment over different periods of time.

Tivoli Enterprise Monitoring Server. The hostdata-management component for IBM Tivoli Monitoring.It receives and stores data from either the agents orother monitoring servers.

Tivoli Enterprise Portal. The client component of aTivoli Enterprise Portal Server. The Tivoli EnterprisePortal provides the graphical user interface intomonitoring data collected by the Tivoli EnterpriseMonitoring Server and prepared for user display by theportal server. The Tivoli Enterprise Portal comes in twoversions: the desktop client and the browser client.

Tivoli Enterprise Portal Server. The server you logonto and connect to through the Tivoli EnterprisePortal client. The portal server connects to the hubTivoli Enterprise Monitoring Server; it enablesretrieval, manipulation, and analysis of data from yourenterprise's monitoring agents.

Tivoli Enterprise Portal Server extended services.An embedded, colocated extension of the TivoliEnterprise Portal Server that provides J2EE-basedApplication Server integration facilities. TEPS/e supports

Glossary 179

a federated user repository built on the LightweightDirectory Access Protocol (LDAP).

Tivoli Enterprise Services user interfaceextensions. A component provided as part of TivoliManagement Services running on distributed systemsthat provides access to the command line interface forother Tivoli Management Services components. Thiscomponent includes the tacmd command, which isused for, among other things, administering theself-describing agents feature. The GUI installer ondistributed operating systems automatically installs thiscomponent when you install the Tivoli Enterprise Portaldesktop client, the Tivoli Enterprise Portal Server, or theTivoli Enterprise Monitoring Server. Additionally, it is anoptional installable component of the Tivoli EnterpriseMonitoring Agent component. The component code isKUE.

The Tivoli Enterprise Services user interface extensionsare not available on z/OS.

Tivoli Enterprise Web Services. An openstandards-based interface to the monitoring server thatuses SOAP requests. Using SOAP, any monitoringagent can be dynamically queried, which means thatits performance and availability data can be processedby external applications not a part of IBM TivoliMonitoring.

Tivoli Integrated Portal. The Tivoli Integrated Portalprovides a single, task-based navigation panel forWeb-based Tivoli products; it offers a common userinterface with which you can launch applications, launchfrom one application to another, and share informationbetween applications. It provides a rich, Web-baseduser interface with which you can access resultsgenerated by such applications as Tivoli ApplicationDependency Discovery Manager (TADDM), TivoliBusiness Service Manager (TBSM), andNetcool/OMNIbus. The Tivoli Integrated Portal enablesthe secure passing of data between Tivoli products viathis common portal. With it, you can manage differentaspects of your enterprise from a single dashboardview.

Tivoli Management Services. An integrated, layeredarchitecture consisting of data-access, communication,and presentation components that enable cross-platformoperation and integration of enterprise-wide data forsystems-management applications. The softwarefoundation that supports the development andoperations of the Tivoli Enterprise Monitoring Server,the Tivoli Enterprise Portal Server and TivoliEnterprise Portal, and their monitoring agents.

Transmission Control Protocol/Internet Protocol.An open, portable communications protocol that is thesoftware basis for the Internet.

TSO. Time Sharing Option, the interactive interfaceinto the z/OS operating system.

UUser Datagram Protocol. A TCP/IP communicationsprotocol that exchanges messages ("datagrams")between networked computers linked by the InternetProtocol (IP). UDP is an alternative to the TransmissionControl Protocol (TCP), which, like UDP, uses IP tomove a message from one computer to another. UnlikeTCP, however, UDP does not divide the message intopackets and reassemble them at the other end.

The Network File System uses UDP to move filecontents and file updates between the NFS server andthe NFS client.

UDP. See “User Datagram Protocol.”

Vvalue of expression. A function in a situationcondition, query specification, or data view filter orthreshold that uses the raw value of an attribute. Avalue can be a number, text string, attribute, or modifiedattribute. Use this function with any operator.

view. A window pane, or frame, in a workspace. Itmay contain data from an agent in a chart or table, or itmay contain a terminal session or browser, for example.A view can be split into two separate, autonomousviews.

WWarehouse Proxy agent. One of the IBM TivoliMonitoring base agents, the Warehouse Proxy agentpasses historical monitoring data from either amonitoring agent or the Tivoli Enterprise MonitoringServer to the Tivoli Data Warehouse. Thismultithreaded server process can handle concurrentrequests from multiple data sources to roll off data fromtheir short-term history files to the data warehouse.

WAV file. Waveform audio format for storing sound infiles, developed jointly by Microsoft and IBM.

wildcard. An asterisk (*) used to represent anycharacters that may follow or precede those entered,such as Sys* to find System and SysTray. Used informulas with the VALUE function or MISSING function(in the Missing Task List). Used also with the SCANfunction, but at the beginning of the text as in *Z to findmarkZ and typeZ.

Windows Management Instrumentation. Microsoft'sWindows Management Instrumentation API provides atoolkit for managing devices and applications in anetwork of Windows-based computers. WMI providesboth the data about the status of local or remotecomputer systems and the tools for controlling the data.WMI is included with the Windows XP and WindowsServer 2003 operating systems.


WMI. See “Windows Management Instrumentation” onpage 180.

workload. A percentage that shows how much of itsresources a managed system is using. Workload iscalculated using a weighted combination of resourceuse statistics.

workspace. The viewing area of the Tivoli EnterprisePortal window, excluding the Navigator. Eachworkspace comprises one or more views. EveryNavigator item has its own default workspace and mayhave multiple workspaces.

workspace administration mode. A global parameterset in the Administer Users editor but which is availableonly for userids with administrator authority. Whenenabled for a userid, customization of workspaces,links, and terminal-session scripts automaticallybecomes available to all users connected to the sameTivoli Enterprise Portal Server.

XXML. See “Extensible Markup Language” on page172.

Zz/OS. IBM's operating system for its line of mainframe,zSeries computers known for its processing speed andits ability to manage large amounts of memory,direct-access storage, and data.

Glossary 181


Index

AAdd Runtime Environment panel

full 34, 37sharing 34, 37

address translation 54, 73, 94, 95, 114Advanced Encryption Standard 169AES

See Advanced Encryption Standardagents

grouping 48, 70, 90alert monitor 169APF-authorizing the load libraries 121application server 170Application Service Monitors, Netcool/OMNIbus 179application support

adding 7application support, installing

catalog and attribute files 129seed data 129SQL files 129

applids, VTAM 38, 74, 97, 115APSERV command 43, 67, 86, 105architecture 3audit collection level, setting 48, 69, 90audit collection parameters 48, 69, 89audit records cache, setting size of 48, 70, 90audit records, associating 48, 70, 90AUDIT_MAX_HIST environment variable 48, 70, 90AUDIT_SMF environment variable 18AUDIT_TRACE environment variable 18, 48, 69, 90auditing function 8, 17

configurationvia PARMGEN 30via the Configuration Tool 48, 69, 89

tracing levels for 18automation 13, 46, 67, 87, 106

BBackup maintenance function 62baroc files 9, 22, 170Basic Recorder of Objects in C files

See baroc filesbrowser client 170BufEvtMaxSize parameter 50, 91Buffer events maximum size field 50, 91buffers, VSAM 47, 68, 88, 108building runtime libraries 39

CCA-ACF2

KLV@ASM member 145KLVA2NEV member 145MUSASS started task 146setting up security 145

CA-TOP SECRETFacility Matrix Table 146setting up security 146SIGN parameter 146

CANCTDCS logmode 38CANSDSST procedure 41, 66, 84, 103CANSDSST started task 119catalog and attribute files 129chgrp USS command 60, 76chmod USS command 60, 76CIM

See Common Information Modelclient/server architecture 170CMS_NODEID environment variable 110CNMLINK data set 120, 151, 152CNMSTYLE member 43, 67, 86, 105commands

APSERV 43, 67, 86, 105PWD 43, 86, 105

Common Event Console view 5Common Information Model 170Common Object Request Broker Architecture 170,

177, 178communication protocols

DVIPA 47, 88dynamic VIPA 68, 108specifying 51, 91, 111VIPA type 47, 68, 88, 108

Communication Selection panel 71, 109, 110communications trace 46, 68, 87, 107completing the configuration 119components

architecture 3event synchronization 5overview 3

configurationcompleting 119copying values 37decisions 13high-availability hub 39persistent datastore 61planning 13security

runtime environment 37Tivoli Enterprise Monitoring Server 41, 85, 104

Tivoli Enterprise Monitoring Server on z/OS 102Tivoli Enterprise Monitoring Server security 41, 85,

104via PARMGEN 7

Configuration Tool panelsAdd Runtime Environment 34, 37, 39Communication Selection 71, 110Configure Persistent Datastore 61Configure Products 33Configure the TEMS 40Create LU6.2 Logmode 65Eligible Products for HA Hub TEMS 44Exclusion Verification for HA Hub TEMS 44


Configuration Tool panels (continued)KCIPCMSS 71, 110KCIPMCU 64KCIPPLST 33KCIPRCM 33KCIPRIM 32KCIPRTA1 37KCIPRTA2 39KCIPRTE 34KCIPRTEA 34KDS62MCU 40KDS62PLU 65KDS62PP1 41KDS62PP2 110KDS62PP3 45, 51, 71KDS62PPA 111KDS62PPB 74KDS62PPD 52, 72, 112KDS62PPE 54KDS62PPF 56KDS62PPG 55KDS62PPH 57KDS62PPI 57KDSPEIF 49KDSPHUBH 44KDSPHUBV 44KDSPNST1 49, 90, 109KPD62PP0 61KPD62PP3 61KSHXHUBS List 56KSHXHUBS Security Access List 57KSHXHUBS User Access List 57KSHXHUBS Values 55Main Menu 32Modify and Review Datastore Specifications 61Product Component Selection Menu 64Product Selection Menu 33Runtime Environments (RTEs) 34SOAP server KSHXHUBS List 56SOAP server KSHXHUBS Security Access List 57Specify Advanced Configuration Values 45Specify Communication Protocols

hub monitoring server 51, 71remote monitoring server 111

Specify Configuration - Hub Values for RemoteTEMS 110

Specify Configuration Values 41Specify IP.PIPE Communication Protocol 52, 72,

112Specify IP.PIPE Partition References 54Specify Nonstandard Parameters 49, 90, 109Specify SNA Communication Protocol 74Specify TEMS KSHXHUBS User Access List 57Specify TEMS KSHXHUBS Values 55Specify Values for Event Destination 49

Configuration Tool, z/OS 170Configure Persistent Datastore panel 61Configure Products panel 33Configure the TEMS panel 40CORBA

See Common Object Request Broker Architecture

Count field 62Create LU6.2 Logmode panel 65CTDDSN node ID 121

DDASD

See storageData Encryption Standard 171data files, application support 129data sets

CNMLINK 120, 151VTAMLST 121

data storeSee persistent datastore

database server 170ddname KBDXTRA 172DDNAMEs 10decisions

Event Integration Facility (EIF) 22high-availability hub 13placement of monitoring servers 13

deploymentdecisions 13planning 13

DESSee Data Encryption Standard

desktop client 171developerWorks website 163diagnostic SYSOUT class 36Disable Workflow Policy/Emitter Agent event forwarding

field 50, 91disk space

See storageDLL

See Dynamic Link Librarydocumentation

See publicationsdomain name resolution 119DSIPARM initialization member 43, 67, 86, 105DVIPA 13, 47, 88Dynamic Link Library 171dynamic VIPA

See DVIPA

EEIB

See Enterprise Information BaseEIF

See also Event Integration FacilitySee Event Integration Facility (EIF)

Eligible Products for HA Hub TEMS panel 44emitter activities 23, 50, 91Enable Tivoli Event Integration Facility (EIF) field 45,

87encryption 42, 66, 85, 104encryption key

batch mode parameter 43, 86, 105changing 43, 86, 105disabling 43, 86, 105


encryption key (continued)parameter 148resetting 43, 86, 105, 147setting 42, 66, 85, 104

enhancements 7Enterprise icon

Managed System Lists workspace 17Enterprise Information Base 172enterprise situation 172environment variables

See also parametersCMS_NODEID 110KDC_DEBUG 46, 68, 87, 107KDC_PARTITIONFILE 54, 95KDE_TRANSPORT 53, 94KDEB_INTERFACELIST 52, 73, 93, 113KGLHC_PPI_RECEIVER 43, 67, 86, 105KGLHC_PPI_SENDER 44, 67, 87, 106KMS_DISABLE_TEC_EMITTER 50, 91KMS_OMTEC_INTEGRATION 45, 87LANG 47, 69, 89, 108MINIMUM 47, 68, 89, 108

Ephemeral Pipe Support (EPS) 54, 73, 94, 95, 114Est Cyl Space field 62Event Forwarder 22Event Integration Facility 172, 175Event Integration Facility (EIF)

configuring 49decisions 22enabling 45, 87KMSOMTEC member 49new feature 9requirements 22rule base 22

Event server location field 50, 91Event server port field 50, 91Event server type field 50, 91event synchronization component 5EventListenerType parameter 50, 91events

determined by situation name 23duplicate, preventing 23, 50, 91forwarding 9, 22, 45, 49, 87integration 9, 22, 45, 49, 87severity 23situation names 23synchronization 9, 22, 45, 49, 87

Exclusion Verification for HA Hub TEMS panel 44Export maintenance function 62extended storage 9Extensible Markup Language 172Extract maintenance function 63

FFacility Matrix Table 146failover, agent 9features, new 7FIPS 197 169firewalls

address translation 54, 73, 94, 95, 114

firewalls (continued)Ephemeral Pipe Support (EPS) 54, 73, 94, 95, 114partition address 54, 55, 74, 95, 115partition name 54, 73, 94, 114with IP.PIPE protocol 54, 73, 94, 95, 114

folding passwords to uppercase 38full runtime environments 34, 37

GGENHIST 62georeferenced map 172global location broker applid 111Global Security Toolkit

See GSKitGroup name field 62GSKit 172

HHA hub

See high-availability hubhigh-availability hub 8

automation 13configuration steps 39designating 41eligible monitoring agents 44exclusion verification of monitoring agents 44monitoring agents, eligible 44monitoring agents, exclusion verification 44requirements 14

high-level qualifiersnon-VSAM libraries 35persistent datastore 49, 70, 90, 109VSAM libraries 35

host namehub 52, 72, 111remote 93, 113runtime environment 38TCP/IP 52, 72, 93, 111, 113

hot-standby monitoring server 173HTTP 173HTTP server port number 53, 94HTTPS 172, 173, 178hub monitoring server

configuring with monitoring agents 79decisions 13defined 4designating 41, 84, 103high-availability 8, 13, 27, 39location 13requirements 53, 94selection for remote monitoring server

connection 71, 110SOAP server 53, 94type 41values for remote monitoring server connection 110

Hub TEMS name field 110Hub TEMS type field 41Hypertext Transport Protocol

See HTTP

Index 185

IIBM Support Assistant 165IBM Tivoli Management Services on z/OS

See Tivoli Management ServicesICAT 170ICSF

See also Integrated Cryptographic Service FacilitySee Integrated Cryptographic Service Facility (ICSF)

ICSF load library field 42, 66, 85, 104IIOP

See Internet Inter-ORB Protocolinstall.sh script 135installing application support

catalog and attribute files 129seed data 129SQL files 129

integral Web server 173Integrated Cryptographic Service Facility 172Integrated Cryptographic Service Facility (ICSF) 104

encryption key 42, 66, 85, 104load library 42, 66, 85, 104resetting encryption key 147specifying 42, 66, 85, 104

Integrated Service Management Library 163Integrated Service Management Library website 128integration, event 9, 22, 45, 49, 87interfaces, network 11, 52, 73, 93, 113Internet Inter-ORB Protocol 173Internet Service Monitors, Netcool/OMNIbus 179Interoperable Object Reference 173IOR

See Interoperable Object ReferenceIP address 38, 52, 54, 55, 72, 74, 93, 95, 111, 113,

115IP.PIPE protocol

address translation 54, 73, 94, 95, 114Ephemeral Pipe Support (EPS) 54, 73, 94, 95, 114specifying 52, 72, 92, 112with firewalls 54, 73, 94, 95, 114

ISA 165ITM_DOMAIN environment variable 48, 70, 90ITMSUPER Tools 128

Jjar utility

command failure with 17dearchive failure with 17use with self-describing agents 17

Java Database Connectivity 173Java Management Extensions API 173Java Runtime Entironment 8, 17Java USS directory 17JCL suffix 36JDBC

See Java Database ConnectivityJMX

See Java Management Extensions APIjobs

KDSDVSRF 10

jobs (continued)KDSDVSRN 10sample VSAM refresh 10

KKCIPCMSS panel 71, 110KCIPMCU panel 64KCIPPLST panel 33KCIPRCM panel 33KCIPRIM panel 32KCIPRTA1 panel 37KCIPRTA2 panel 39KCIPRTE panel 34KCIPRTEA panel 34KDC_DEBUG environment variable 46, 68, 87, 107KDC_FAMILIES environment variable

See KDE_TRANSPORT environment variableKDC_PARTITIONFILE environment variable 54, 95KDCPART member 54, 95KDE_TRANSPORT environment variable

port numbers 53, 94well-known port 53, 94

KDEB_INTERFACELIST environment variable 52, 73,93, 113

KDS_CMS_SEC_ENC_KEY parameter 148KDS62MCU panel 40KDS62PLU panel 65KDS62PP1 panel 41KDS62PP2 panel 110KDS62PP3 panel 51, 71KDS62PP3 penal 45KDS62PPA panel 111KDS62PPB panel 74KDS62PPD panel 52, 72, 112KDS62PPE panel 54KDS62PPF panel 56KDS62PPG panel 55KDS62PPH panel 57KDS62PPI panel 57KDSDVSRF job 10KDSDVSRN job 10KDSMA001 message ID 46, 67, 87, 107KDSMTAB1 logmode table 38KDSPEIF panel 49KDSPHUBH panel 44KDSPHUBV panel 44KDSPNST1 49, 90, 109KDSSYSIN member 145, 146key, encryption

See also encryption keychanging 105disabling 105resetting 105

KFWITM217E 137, 138KGLHC_PPI_RECEIVER environment variable 43, 67,

86, 105KGLHC_PPI_SENDER environment variable 44, 67,

87, 106KLV@ASM member 145KLVA2NEV member 145


KLXINTCP member 46, 68, 88, 107KMS_DISABLE_TEC_EMITTER environment

variable 50, 91KMS_OMTEC_INTEGRATION environment

variable 45, 87KMSOMTEC member 50, 91KO4SRV032 message ID 46, 67, 87, 107KPD62PP0 panel 61KPD62PP3 panel 61KPDPROC* procedures 120krarloff utility 172KSHXHUBS List panel 56KSHXHUBS member 53, 94KSHXHUBS Security Access List panel 57KSHXHUBS Values panel 55

LLANG environment variable 47, 69, 89, 108Language locale field 47, 69, 89, 108LDAP

See Lightweight Directory Access ProtocolLIBPATH environment variable 17libraries

IBM Tivoli Monitoring 159ICSF 42, 66, 85, 104macro 65, 84, 103non-VSAM 10OMEGAMON XE shared publications 161runtime

building 39loading 63, 77, 98, 116

VSAM 10VTAMLIB 65, 84, 103

Lightweight Directory Access Protocol 173, 175listening port numbers

See port numbersload libraries

APF-authorizing 121ICSF 42, 66, 85, 104VTAMLIB 65, 84, 103

load optimization 36location brokers

global 55, 96, 111, 122local 122

loggingcommunications trace data 46, 68, 87, 107storage detail 46, 68, 88, 107

logmode table 38, 65, 84, 103logmodes

creating 65, 102LU6.2 102

Lowlev field 62LU6.2 logmodes 38, 65, 84, 102, 103

MMain Menu panel 32maintenance options, persistent datastore 61maintenance procedure prefix 49, 70, 90, 109

managed Java beansSee MBeans

master facility accessor identifier 146maximum storage request size 47, 69, 89, 108MBeans 173, 174members, user-modified 36menu, main 32messages, startup 46, 67, 87, 106Mgmtclas field 35, 49, 70, 90, 109Microsoft Management Console 174mid-level qualifiers 36migration

See upgradeMINIMUM environment variable 47, 68, 89, 108minimum extended storage 9, 47, 68, 89, 108missing data 137, 138mixed-case passwords 38mkdir USS command

access permissions set by 60, 76MMC

See Microsoft Management ConsoleModify and Review Datastore Specifications panel 61monitoring agents

base 6completing the configuration 119defined 6eligible for high-availability hub 44exclusion verification for high-availability hub 44failover 9OMEGAMON 6registering 8

monitoring serverSee also Tivoli Enterprise Monitoring ServerPARMGEN configuration 7

MUSASS started task 146MVS MODIFY command 146

NNAT

See Network Address Translationnational languages

See languagesnavigation 1, 25, 117Netcool/OMNIbus 9, 22, 179

MTTRAPD trap receiver for 179NETID parameter 38, 74, 97, 111, 115NetView

APSERV command 43, 67, 86, 105CNMLINK data set 120, 151CNMSTYLE member 43, 67, 86, 105, 152DSIPARM initialization member 43, 67, 86, 105enabling command authorization 122PPI values

receiver 43, 67, 86, 105sender 44, 67, 87, 106specifying 43, 66, 86, 105

Take Action command authorization 43, 67, 86, 105configuring 149

Network Access Method (NAM)NAM SET statements 147

Index 187

Network Access Method (NAM) (continued)passwords 147setting up security 146user IDs 147

Network address (Hostname) 52, 72, 93, 111, 113Network Address Translation 175Network File System 175network ID 38, 74, 97, 111, 115network interface list 11, 52, 73, 93, 113new features 7NFS

See Network File Systemnode ID 139, 141

OODBC

See Open Database ConnectivityOMEGAMON Tivoli Event Adapter 175OMNIbus

See Netcool/OMNIbusOpen Database Connectivity 176optimization, loading runtime libraries 36OTEA

See also Event ForwarderSee OMEGAMON Tivoli Event Adapter

Ppanels, Configuration Tool

See Configuration Tool panelsparameters

See also environment variablesBufEvtMaxSize 50, 91encryption key 43, 86, 105EventListenerType 50, 91KDS_CMS_SEC_ENC_KEY 43, 86, 105, 148KMS_OMTEC_INTEGRATION 45, 87maintenance procedure prefix 49, 70, 90, 109persistent datastore 48, 70, 90, 109ServerLocation 50, 91ServerPort 50, 91TOLERATERECYCLE 46, 68, 88, 107

PARMGEN configuration 7partition address 54, 55, 74, 95, 115partition name 54, 73, 94, 114passwords

encryption 42, 66, 85, 104, 147mixed-case 38NAM SET statements 147uppercase 38

PATH environment variable 17PDS

See also persistent datastoreSee Persistent Datastore

PDSE field 35PerfMon

See Performance Monitor, WindowsPerformance Monitor, Windows 176persistent data store

copying data sets 63

persistent data store (continued)creating runtime members 63maintenance functions 62providing access to data sets 63

persistent datastoreallocating space 61configuring 61DASD unit 49, 70, 90, 109DASD volume 49, 70, 90, 109file prefix 49, 70, 90, 109maintenance 9maintenance options 61maintenance procedure prefix 49, 70, 90, 109management class 49, 70, 90, 109parameters 48, 70, 90, 109specifying file placement 61storage class 49, 70, 90, 109

Persistent Datastore 172, 176planning 13policies, workflow 23, 50, 91port numbers

default 53, 94high-availability hub 39HTTP server 53, 94hub 53, 73, 94, 111, 114

portal clientSee Tivoli Enterprise Portal client

portal serverSee Tivoli Enterprise Portal Server

prefixapplid 38, 74, 97, 115maintenance procedure 49, 70, 90, 109persistent datastore files 49, 70, 90, 109started task procedures 36

prerequisitesapplication support 129encryption 42, 66, 85, 104ICSF 42, 66, 85, 104

private situation 176Product Component Selection Menu panel 64Product Selection Menu panel 33program-to-program (PPI) information

receiver 43, 67, 86, 105sender 44, 67, 87, 106specifying 43, 66, 86, 105

protocolsSee communication protocols

publicationsdeveloperWorks website 163Integrated Service Management Library 163OMEGAMON XE 161Redbooks 163related 162shared 161Technotes 163Tivoli Management Services on z/OS 161types 159wikis 163

PWD command 43, 86, 105


Qqualifiers, high-level

See high-level qualifiers

RRACF

MIXEDCASE option 38OPERCMDS facility class 154, 155passwords 38setting up security 145, 154

userid mapping file for 155RAS1 trace data 46, 68, 87, 107reconnecting after TCP/IP recycle 46, 68, 88, 107recycle, TCP/IP 46, 68, 88, 107Redbooks 163registering monitoring agents 8, 129remote monitoring server

Communication Selection panel 71, 110configuring in interactive mode 99decisions 13, 14defined 4designating 41, 66, 84, 103hub selection 71, 110hub TEMS name 110hub values panel 110location 13, 14reporting to distributed hub 99specifying hub 110

Remote Procedure Call 177Remote RTE for Transport field 36requirements

See also prerequisitesapplication support 129encryption 42, 66, 85, 104Event Integration Facility (EIF) 22high-availability hub 14ICSF 42, 66, 85, 104Web Services SOAP server 53, 94

RESERVE parameter 145, 146RGENHIS 62RKANDATV data set 137, 138RKANMOD load library 121RKANMODL load library 121RKANMODL statement 120, 151RKANMODU load library 121RKANSAMU data set 120RPC

See Remote Procedure CallRTE

See runtime environmentsrule base 22runtime environments

building libraries 39completing the configuration 119copying configuration values 37full 34, 37load optimization 36optimization 36security 37

runtime environments (continued)sharing 34, 37transporting 36

Runtime Environments (RTEs) panel 34runtime libraries

building 39loading 63, 77, 98, 116

runtime membersanalyzing 36creating 61

Ssample procedures 120scenarios

high-availability hub 27hub with monitoring agents 79remote monitoring server with distributed hub 99

Secure Hypertext Transport ProtocolSee HTTPS

secure pipeSee SPIPE

Secure Sockets Layer API 172, 173, 177, 178security

CA-ACF2 145CA-TOP SECRET 146changing 147enabling 143NAM 146RACF 145requirements 143runtime environment 37setting up 143SOAP server 56, 96supported packages 143Tivoli Enterprise Monitoring Server 41, 85, 104

security-enhanced LinuxSee SELinux

seeding 129seeding the monitoring server 7self-describing agents 7, 15, 129

configurationvia PARMGEN 29via the Configuration Tool 58, 74

SELinux 177ServerLocation parameter 50, 91ServerPort parameter 50, 91shared publications 161short-term historical data

See persistent datastoreSIGN parameter 146Simple Network Management Protocol 170, 173, 176,

177Simple Object Access Protocol 177Simple Object Access Protocol (SOAP)

See SOAP serversingle sign-on 178SISTMAC library 65, 84, 103Situation Event Console 5situation events

See events

Index 189

Situation Update Forwarder 176, 178SMF type-112 records 18SMP/E

See System Modification Program/ExtendedSMS considerations 35SNA communication protocol

applid prefix 74, 97, 115global location broker applid 111network ID 74, 97, 111, 115selection 51, 52, 92, 112values 74

SNMPSee Simple Network Management Protocol

SOAPSee Simple Object Access Protocol

SOAP serverenabling 45, 67, 87, 106KSHXHUBS List panel 56KSHXHUBS member 53, 94KSHXHUBS Security Access List panel 57KSHXHUBS User Access List panel 57remote monitoring servers 8security 56, 96user access 56, 96user access list 56, 96

Software Support 165Specify Advanced Configuration Values panel 45Specify Communication Protocols panel

hub monitoring server 51, 71remote monitoring server 111

Specify Configuration - Hub Values for Remote TEMSpanel 110

Specify Configuration Values panel 41Specify IP.PIPE Communication Protocol panel 52, 72,

112Specify IP.PIPE Partition References panel 54Specify Nonstandard Parameters panel 49, 90, 109Specify SNA Communication Protocol panel 74Specify TEMS KSHXHUBS User Access List panel 57Specify TEMS KSHXHUBS Values panel 55Specify Values for Event Destination panel 49SPIPE 172, 178SQL

See Structured Query LanguageSQL files 129SSL

See Secure Sockets Layer APISSM

See System Service Monitors, Netcool/OMNIbusSSO

See single sign-onstarted tasks

adding NetView CNMLINK data set 120, 151CANSDSST 41, 66, 84, 103DDNAMEs 10monitoring server 41, 66, 84, 103MUSASS 146prefix 36RKANMODL statement 120, 151sample procedures 120TCP/IP 11

started tasks (continued)TCP/IP server 38, 52, 73, 93, 113Tivoli Enterprise Monitoring Server 119

startup messages 46, 67, 87, 106STC prefix 36STC record 146storage

logging, detail 46, 68, 88, 107maximum request size 47, 69, 89, 108minimum 47, 68, 89, 108minimum extended 9persistent datastore files 49, 70, 90, 109virtual 9

Storclas field 35, 49, 70, 90, 109Structured Query Language 178SUF

See Situation Update Forwardersuffix, JCL 36Summarization and Pruning agent 5support assistant 165synchronization, event 9, 22, 45, 49, 87SYSOUT class

diagnostic 36non-diagnostic 36

SYSTCPD DDNAME support 119System Modification Program/Extended 170, 179System Service Monitors, Netcool/OMNIbus 179system variables

enabling 37incompatible with high-availability hub 14

Ttacmd createsystemlist command 174tacmd deletesystemlist command 174tacmd editsystemlist command 174Take Action command authorization

NetView 43, 67, 86, 105, 154configuring 149enabling 152

RACF 154TCP/IP

See also Transmission Control Protocol/InternetProtocol

communication values 38host name 38, 52, 72, 93, 111, 113interface list 52, 73, 93, 113IP address 38network interfaces 52, 73, 93, 113recycle 46, 68, 88, 107server started task 38, 52, 73, 93, 113started task name 11

TDWSee Tivoli Data Warehouse

TECSee Tivoli Enterprise Console

Technotes 163telnet 179TEMS name

for application support 139, 141hub, specified for remote configuration 110


TEMS name (continued)specifying 37

TEMS_JAVA_BINPATH environment variable 17TEPS/e 5, 179Tivoli Application Dependency Discovery Manager 18,

104Tivoli Business Service Manager 17Tivoli Common Reporting 8, 17Tivoli Data Warehouse 5, 8, 17, 171, 179Tivoli Enterprise Console 9, 22, 170, 172, 175, 178

event synchronization 5integration 5

Tivoli Enterprise Console event view 5Tivoli Enterprise Console integration 5Tivoli Enterprise Monitoring Agents

See monitoring agentsTivoli Enterprise Monitoring Server

adding application support 7adding NetView CNMLINK 120, 151changing security system 147completing the configuration 119configuring on z/OS 102defined 4high-availability 41

eligible monitoring agents 44exclusion verification of monitoring agents 44

high-availability hub 13, 27, 39hub

configuring with monitoring agents 79defined 4high-availability 8, 13, 27, 39location 13

node ID 139, 141placement of hub 13placement of remote 13, 14remote

configuring in interactive mode 99configuring on z/OS 102defined 4location 13, 14reporting to distributed hub 99

requirements 53, 94runtime members 61security

CA-ACF2 145CA-TOP SECRET 146changing 147NAM 146RACF 145requirements 143settings 41, 85, 104setup 143supported packages 143

seeding 7SOAP server 53, 94started task 146supported security packages 143TEMS name 139, 141type 41, 66, 84, 103

Tivoli Enterprise Portal 179client, defined 4

Tivoli Enterprise Portal clientEnterprise icon 17

Tivoli Enterprise Portal Server 4Tivoli Enterprise Portal Server extended services

See TEPS/eTivoli Event Integration Facility

See Event Integration Facility (EIF)Tivoli Integrated Portal 180Tivoli Management Services

architecture 3components 3defined 3distributed components 3

TKANMOD load library 121TKANMODL load library 121TLS

See Transport Layer Security APITMS:Engine, defined 5TOLERATERECYCLE keyword 46, 68, 88, 107trace level, setting 48, 69, 90trace, communications 46, 68, 87, 107Transmission Control Protocol/Internet Protocol 180Transport Layer Security API 173

UUDP

See User Datagram ProtocolUnit field 35, 49, 70, 90, 109UNIX System Services, z/OS 8, 17Update Runtime Environment panel 147uppercase passwords 38user access list 57User Datagram Protocol 180user IDs for SOAP server access 56, 96user-modified members 36USS CLIST library 59, 75USS directories

permissions for 60, 76

Vvariables, environment

See environment variablesvariables, system

See system variablesVIPA

dynamic 47, 68, 88, 108static 47, 68, 88, 108type 47, 68, 88, 108

Virtual IP AddressingSee VIPA

Volser field 35Volume field 49, 70, 90, 109VSAM buffers 47, 68, 88, 108VSAM libraries

high-level qualifiers 35new 10sample refresh jobs 10

VTAMapplids 38, 74, 97, 115

Index 191

VTAM (continued)communication values 38definitions, copying to VTAMLST 121load library 65, 84, 103logmode table 38, 65, 84, 103LU6.2 logmodes 65, 84, 103macro library 65, 84, 103major node, varying active 121network ID 38, 74, 97, 111, 115

VTAMLIB load library 65, 84, 103VTAMLST data set 121VTAMLST startup member 38, 74, 97, 111, 115

WWarehouse Proxy agent 5WAV file 180Web Services 53, 94Web Services support

remote monitoring servers 8well-known port 39wikis 163wildcard 180Windows Dynamic Link Library

See Dynamic Link LibraryWindows Management Instrumentation API 180Windows Performance Monitor

See Performance Monitor, WindowsWMI

See Windows Management Instrumentation APIworkflow policies 23, 50, 91

XXML

See Extensible Markup Language


��

Printed in USA

SC27-2313-03

Date post:	27-Mar-2020
Category:	Documents
Upload:	others
View:	11 times
Download:	1 times

Configuring theTivoli Enterprise Monitoring Server on z/OS · OMEGAMON XE and IBM Tivoli Management...

Documents