Configuring the Tivoli Enterprise Monitoring Server on z/os

Transcription

1 IBM Tioli Management Serices on z/os Version Fix Pack 1 Configuring the Tioli Enterprise Monitoring Serer on z/os SC

2

3 IBM Tioli Management Serices on z/os Version Fix Pack 1 Configuring the Tioli Enterprise Monitoring Serer on z/os SC

4 Note Before using this information and the product it supports, read the information in Appendix C, Notices, on page 167. This edition applies to ersion 6, release 2, modification 3, Fix Pack 1 of IBM Tioli Management Serices on z/os (product number 5698-A79) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC Copyright IBM Corporation 2005, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures ii Tables ix Part 1. Preparing to configure the Tioli Enterprise Monitoring Serer on z/os.. 1 Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer 3 Tioli Management Serices Tioli Enterprise Monitoring Serer Tioli Enterprise Portal Serer and clients Tioli Data Warehouse TMS:Engine Eent synchronization component Tioli Enterprise Portal Serer extended serices Monitoring agents New in this release Chapter 2. Planning your deployment Decision 1: What kinds of monitoring serers to configure Whether to configure a high-aailability hub on z/os How many remote monitoring serers to configure Whether to enable the self-describing agents capability Whether to enable the auditing function Decision 2: Whether and how to enable eent forwarding Part 2. Configuring hub and remote monitoring serers on z/os Chapter 3. Configuring a high-aailability hub and the remote monitoring serers that report to it PARMGEN method Step 1. Create and configure a runtime enironment for the high-aailability hub Step 2. Configure a remote monitoring serer to report to the high-aailability hub Step 3. Configure monitoring agents to report to the remote monitoring serer Step 4. (Optional) Replicate the remote runtime enironment Configuration Tool (ICAT) method Step 1. Add a runtime enironment Step 2. Build the runtime libraries Step 3. Configure the high-aailability hub monitoring serer Step 4. Configure a remote monitoring serer to report to the high-aailability hub Step 5. Configure monitoring agents to report to the remote monitoring serer Step 6. Load the runtime libraries Chapter 4. Configuring the hub monitoring serer and monitoring agents in the same runtime enironment PARMGEN method Step 1. Create the runtime enironment and set the configuration parameters for the hub Step 2. Set configuration parameters for the monitoring agents in the same runtime enironment 81 Step 3. (Optional) Replicate the runtime enironment to a remote system Configuration Tool (ICAT) method Configuration steps Step 1. Configure the hub monitoring serer Step 2. Configure monitoring agents in the runtime enironment Copyright IBM Corp. 2005, 2012 iii

6 Step 3. Load the runtime libraries Chapter 5. Configuring a remote monitoring serer on z/os to report to a distributed hub PARMGEN method Step 1. Create the runtime enironment and set the configuration parameters for the remote monitoring serer Step 2. Set configuration parameters for the monitoring agents in the same runtime enironment 101 Step 3. (Optional) Replicate the remote runtime enironment Configuration Tool (ICAT) method Configuration steps Step 1. Configure the remote monitoring serer Step 2. Configure monitoring agents in the runtime enironment Step 3. Load the runtime libraries Part 3. Post-configuration procedures Chapter 6. Completing the configuration Typical tasks of completing the configuration of a monitoring serer (If applicable) Add support for the SYSTCPD DDNAME in the monitoring serer started task (If applicable) Add the NetView CNMLINK data set to the monitoring serer started task Copy the started task procedures to your procedure library Copy the VTAM definitions to your system VTAMLST Vary the VTAM major node actie APF-authorize the runtime load libraries (If applicable) Refresh the KSHXHUBS member in other runtime enironments Verify that you can start and stop the monitoring serer (If applicable) Enable NetView to authorize Take Action commands (If applicable) Edit the portal serer enironment file Enable historical data store maintenance (optional) Enable historical data collection (optional) Enable eent forwarding (optional) Run the ITMSUPER Tools (optional) Chapter 7. Adding application support to a monitoring serer on z/os Prerequisites Selecting the correct procedure Install the application support files on a distributed system where a portal serer is installed Installing application support files on Windows Installing application support files on Linux or UNIX Copy or transfer catalog and attribute files to the monitoring serer on z/os Transferring the catalog and attribute files from Windows Transferring the catalog and attribute files from Linux or UNIX Use Manage Tioli Monitoring Serices to add application support SQL files to the hub monitoring serer on z/os Adding application support SQL files from Manage Tioli Monitoring Serices on Windows Adding application support SQL files from Manage Tioli Monitoring Serices on Linux or UNIX 140 Chapter 8. Configuring security on a monitoring serer on z/os Enabling security alidation on a z/os hub Implementing security with RACF Implementing CA-ACF2 security Implementing security with CA-TOP SECRET Implementing security with Network Access Method (NAM) Changing the security system specification Resetting the password encryption key PARMGEN method i IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

7 Configuring NetView authorization of z/os commands Configure the monitoring serer to forward Take Action commands Add the NetView CNMLINK data set to the Tioli Enterprise Monitoring Serer started task Enable NetView to authorize Take Action commands Verifying the configuration Troubleshooting tips Enable RACF authorization of Take Action commands Setting up the userid mapping capability Part 4. Appendixes Appendix A. Documentation library IBM Tioli Monitoring library Documentation for the base agents Shared OMEGAMON XE publications Related publications Other sources of documentation Appendix B. Support information Appendix C. Notices Trademarks Glossary Index Contents

8 i IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

9 Figures 1. Agent/serer/client architecture High-aailability hub monitoring serer and its connections Configuration Tool Main Menu Configure Products panel Product Selection Menu Runtime Enironments (RTEs) panel Add Runtime Enironment (1 of 3) panel Add Runtime Enironment (2 of 3) panel Add Runtime Enironment (3 of 3) panel Configure the TEMS panel Specify Configuration Values panel Eligible Products for HA Hub TEMS panel Exclusion Verification for HA Hub TEMS panel Specify Adanced Configuration Values panel Specify Persistent Datastore Configuration Values panel Specify Values for Eent Destination panel Specify Communication Protocols panel Specify IP.PIPE Communication Protocol panel Specify IP.PIPE Partition References panel Specify TEMS KSHXHUBS Values panel SOAP serer KSHXHUBS List panel SOAP serer KSHXHUBS Security Access List panel Specify TEMS KSHXHUBS User Access List panel Configure TEMS Self-Describing Agent Parameters panel Specify TEMS Self-Describing Agent Values panel Configure Persistent Datastore panel Modify and Reiew Datastore Specifications panel Product Component Selection Menu Create LU6.2 Logmode panel Communication Selection panel Specify Communication Protocols panel Specify IP.PIPE Communication Protocol panel Specify SNA Communication Protocol panel Hub monitoring serer and monitoring agents in the same runtime enironment Remote monitoring serer on z/os reporting to a hub on a distributed system Communication Selection panel Specify Configuration - Hub Values for Remote TEMS panel Specify Communication Protocols panel for a remote monitoring serer Specify IP.PIPE Communication Protocol panel for a remote monitoring serer CNMSTYLE member after editing CNMLINK DD statement in the Tioli Enterprise Monitoring Serer started task CNMSTYLE member after editing Copyright IBM Corp. 2005, 2012 ii

10 iii IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

11 Tables 1. New monitoring serer runtime libraries and started task DDNAMEs SMF type-112 record subtypes SMF record 112 format Procedures for adding application support to a monitoring serer on z/os Copyright IBM Corp. 2005, 2012 ix

12 x IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

13 Part 1. Preparing to configure the Tioli Enterprise Monitoring Serer on z/os This publication is intended to be used together with IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide, which contains ital planning information. 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 Tioli Enterprise Monitoring Serer on z/os. See Appendix A, Documentation library, on page 159 for information on finding the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide and other related publications. The chapters in this part of Configuring the Tioli Enterprise Monitoring Serer on z/os proide information required for beginning to configure your monitoring serers on z/os. Chapter 1, Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer, on page 3 explains the architecture and the commonly shared components of IBM Tioli Management Serices. Chapter 1 also contains a New in this release section, which describes changes and enhancements that affect the configuration of the Tioli Enterprise Monitoring Serer. Chapter 2, Planning your deployment, on page 13 helps you plan a first-time deployment of the Tioli Enterprise Monitoring Serer on z/os. Chapter 2 coers basic planning decisions that are not coered in Part 1 of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide: Decision 1: What kinds of monitoring serers to configure on page 13 Decision 2: Whether and how to enable eent forwarding on page 22 Naigation tips If you are installing and configuring the Tioli Management Serices components for the first time, be sure to read all the chapters in Part 1 of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide and in Part 1 of this publication before you begin. 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 Tioli Enterprise Monitoring Serer. 2. Follow the upgrade instructions in IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Upgrade Guide. See Appendix A, Documentation library, on page 159 for information on finding the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Upgrade Guide and other related publications. Copyright IBM Corp. 2005,

14 2 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

15 Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer The Tioli Enterprise Monitoring Serer (also called the monitoring serer) is the central component of the commonly shared technology called Tioli Management Serices. The monitoring serer consolidates and distributes data; receies and distributes commands; and sends alerts when specified aailability and performance problems are detected in the monitored applications, systems, or networks. The monitoring serer can run on distributed or z/os systems. This guide describes how to configure and customize a monitoring serer on a z/os system. Tioli Management Serices The commonly shared components of Tioli Management Serices proide security, data transfer and storage, notification, user interface presentation, and communication for a number of Tioli monitoring products. The Tioli Management Serices components and the monitoring agents work together in an agent/serer/client implementation (Figure 1). Figure 1. Agent/serer/client architecture Some components of Tioli Management Serices, such as Tioli Enterprise Portal and the Warehouse Proxy and Summarization and Pruning agents, run only on distributed systems. The Tioli Enterprise Monitoring Serer and the Tioli Data Warehouse can run on either distributed or mainframe systems. Tioli Management Serices:Engine (TMS:Engine) runs only on mainframe systems. The Tioli Management Serices shared components are included with the IBM Tioli Monitoring product, with the OMEGAMON XE monitoring agent products, with the IBM Tioli Management Serices on z/os product, and with many other Tioli applications. Tioli Management Serices comprises the following commonly shared components: Copyright IBM Corp. 2005,

16 Tioli Enterprise Monitoring Serer Tioli Enterprise Portal Serer and clients Tioli Data Warehouse on page 5 TMS:Engine on page 5 Eent synchronization component on page 5 Tioli Enterprise Portal Serer extended serices on page 5 Tioli Enterprise Monitoring Serer Tioli Enterprise Monitoring Serer is the nere center of Tioli Management Serices. The monitoring serer performs the following tasks: Consolidates the data collected by monitoring agents and distributes the data to the Tioli Enterprise Portal Serer. Manages the connection status of the monitoring agents. Receies commands from Tioli Enterprise Portal and distributes them to the appropriate monitoring agents. Sends alerts to the Tioli Enterprise Portal Serer when specified aailability and performance problems are detected Stores historical data and configuration prototypes. The master monitoring serer is called the hub monitoring serer. The hub monitoring serer acts as the focal point for data collection and distribution. It communicates with monitoring agents, with remote monitoring serers, with the Tioli Enterprise Portal Serer, and with the Warehouse Proxy and Summarization and Pruning agents (see Tioli Data Warehouse on page 5). A remote monitoring serer is remote only with respect to the hub monitoring serer, not with respect to the monitoring agents. Remote monitoring serers communicate only with the monitoring agents that report to them and with the hub monitoring serer to which they report. Monitoring serers can run on z/os, Windows, AIX, HP-UX, Solaris, or Linux systems. Tioli Enterprise Portal Serer and clients Tioli Enterprise Portal (also called the portal or the portal client) is the user interface for products using Tioli Management Serices. The Tioli Enterprise Portal is a thin Jaa client application. It has its own serer, the Tioli Enterprise Portal Serer, that communicates with the hub monitoring serer to send requests to and retriee data from monitoring agents on managed systems. Tioli Enterprise Portal Serer (the portal serer) builds and formats the portal workspaces that display real-time and historical data collected by the monitoring agents. The portal serer can run on Windows, AIX, or Linux systems. You can access the portal client in any of the following ways: Browser client (Internet Explorer or Mozilla Firefox on Windows, Mozilla Firefox on Linux) connected to a web serer embedded in the portal serer. The desktop client is downloaded or updated eery time it starts up. Your site can now run the Tioli Enterprise Portal browser client using newer leels (3.6.x, V5.0, or V6.0.x) of the Firefox Web browser on Windows and Linux when used in conjunction with a Jaa V6 runtime enironment. Note: If your site is running a Jaa V5 runtime enironment instead, you must continue to run the V3.5 or earlier leel of Firefox. Desktop client installed on a Windows or Linux system. Desktop client downloaded and run by IBM Web Start for Jaa, and updated at eery startup. For setup information about the portal serer and client, see the IBM Tioli Monitoring: Installation and Setup Guide. 4 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

17 Tioli Data Warehouse Tioli Data Warehouse, an optional component of Tioli Management Serices, is a long-term data store for the performance and analysis data collected by the monitoring agents. The Warehouse Proxy agent periodically receies data indirectly from the hub monitoring serer or directly from the monitoring agents and inserts that data into the Tioli Data Warehouse. On z/os systems, short-term history data for monitoring agents is maintained in data sets allocated and initialized during product configuration. The Warehouse Proxy agent receies the short-term history data and deliers it to the warehouse. Two specialized agents interact with the Tioli Data Warehouse: The Warehouse Proxy agent receies the short-term history data and deliers it to the Tioli Data Warehouse. You can use the Summarization and Pruning agent to customize how long to sae (pruning) and how often to aggregate (summarization) the data in the Tioli 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: IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide IBM Tioli Monitoring: Installation and Setup Guide IBM Tioli Monitoring: Administrator's Guide TMS:Engine TMS:Engine proides common functions such as communications, multithreaded runtime serices, tracing, and logging for the monitoring serer and monitoring agents on z/os. This shared component enables common portable code to make platform-independent system calls. This allows Tioli Enterprise Monitoring Serer code to be compiled for and executed on z/os, Windows, Linux, and UNIX platforms. Eent synchronization component The eent synchronization component sends updates to situation eents that hae been forwarded to a Tioli Enterprise Console eent serer or a Netcool /OMNIbus ObjectSerer back to the hub monitoring serer. In the Tioli Enterprise Portal, the Situation Eent Console, the Common Eent Console and the Tioli Enterprise Console eent iews are synchronized with the updated status of the eents. For information about the configurations of eent serers that you can hae in your enironment, see the IBM Tioli Monitoring: Installation and Setup Guide. For information about forwarding eents from a hub monitoring serer on z/os, see Decision 2: Whether and how to enable eent forwarding on page 22. With Tioli Management Serices V6.2.2 and later, stand-alone monitoring agents (those that are configured in their own address spaces) can run in autonomous mode (without communicating directly with a monitoring serer). An autonomous agent can emit Simple Network Management Protocol (SNMP) traps and Eent Integration Facility (EIF) eents directly to an OMNIbus ObjectSerer for agent-specific situations (but not for enterprise situations). The IBM Tioli Monitoring: Installation and Setup Guide proides instructions for configuring OMNIbus ObjectSerers to receie the eents. For information on specifying which situation eents to forward, see the Tioli Enterprise Portal online help and the IBM Tioli Monitoring: Tioli Enterprise Portal User's Guide. For detailed information about managing autonomous agents, see the "Agent autonomy" chapter of the IBM Tioli Monitoring: Administrator's Guide. Tioli Enterprise Portal Serer extended serices Tioli Enterprise Portal Serer extended serices (TEPS/e) is an embedded, co-located extension of the Tioli Enterprise Portal Serer that proides J2EE-based Application Serer integration facilities. TEPS/e proides support for a federated user repository. Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer 5

18 Monitoring agents If you purchased IBM Tioli Monitoring as a product, you receied a set of operating system monitoring agents (also called OS agents or base agents) as part of the product. If you purchased a monitoring agent product (for example, an OMEGAMON XE product) that includes the commonly shared components of Tioli Management Serices, you did not receie the base agents. Monitoring agent products are aailable for systems, database products, and applications. You can see the complete list of monitoring agents at the following website: A monitoring agent on any platform can be part of an enterprise that includes monitoring serers on z/os systems. 6 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

19 New in this release This section describes enhancements that affect the configuration of Tioli Enterprise Monitoring Serer and that hae been added since the last release of this publication. Userid-leel security now aailable for Take Action commands. As of fix pack 1 for IBM Tioli Monitoring Version 6.2.3, all z/os Take Action commands issued by the OMEGAMON XE agents, plus any other agents based on the Tioli Management Serices framework that run on z/os, can now be associated with the Tioli Enterprise Portal userid instead of the userid of the started task running the agent. This allows you to authorize the use of Take Action commands by selected portal serer users while restricting it from others. You can secure these userids (or the RACF groups they are in) ia standard security objects proided by your site's security product; for RACF, these are the OPERCMDS facility class and its profiles. See Enable RACF authorization of Take Action commands on page 154. Later ersions of the Firefox browser now supported. Your site can now run the Tioli Enterprise Portal browser client using 3.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 Jaa V6 runtime enironment. In addition, AIX has been remoed as a Tioli Enterprise Portal client platform from this configuration guide. Only the Windows and Linux platforms are supported for the Tioli Enterprise Portal browser client. AIX is still fully supported as a Tioli Enterprise Portal serer platform. PARMGEN configuration method. The PARMGEN configuration method is now the preferred method of product configuration. The PARMGEN method is particularly suitable for the following types of customers: New OMEGAMON XE customers. Existing OMEGAMON XE customers in enironments in which one person is responsible for configuring all OMEGAMON XE products and components. With the PARMGEN configuration method, you edit a comprehensie list of parameters for configuring all installed products and components. You then submit a series of jobs to create a complete runtime enironment with the parameter alues you specified. The chapters in Part 2, Configuring hub and remote monitoring serers on z/os, on page 25 and Part 3, Post-configuration procedures, on page 117 now include procedural instructions for both PARMGEN and the Configuration Tool (ICAT) configuration methods. For more information about the PARMGEN configuration method, see IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide, IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Parameter Reference, and the PARMGEN Technote at Tip: Both the PARMGEN method and the Configuration Tool (ICAT) method are currently supported, but future product enhancements and updates will be aailable by the PARMGEN method only. Therefore, it is a good idea to begin using the PARMGEN method for configuring your products and components. Self-describing agents. Prior to ersion 6.2.3, before an agent could connect to a Tioli Enterprise Monitoring Serer, you were required to update the monitoring serer (as well as other Tioli Management Serices components such as the Tioli Enterprise Portal Serer and the Tioli Data Warehouse) with information necessary for it to recognize and process data sent by that agent, and then restart all affected components. As of V6.2.3, this "seeding" step (as it was once known) becomes unnecessary for the distributed (that is, non-z/os) agents: they hae been enhanced with a self-description capability that automatically distributes each agent's operating configuration directly to the local monitoring serer, which then replicates those agent configuration files first to the hub monitoring serer (if necessary) and then to the arious IBM Tioli Monitoring components that require it. Whether to enable the self-describing agents capability on page 15 has more information about the self-describing distributed agents. Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer 7

20 Note: Once your site actiates self-describing agents on a hub Tioli Enterprise Monitoring Serer, the monitoring serer must hae access to a Jaa Runtime Enironment running under IBM's 31-bit or 64-bit Jaa SDK Version 5 (or higher) and an HFS or zfs file system configured for UNIX System Serices (USS). As part of monitoring serer 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 enironment. In support of self-describing agents, this file is now processed as part of monitoring serer configuration; in this way, the monitoring serer started task is already set up to accommodate the C5 agent's hub monitoring serer requirements when the C5 Agent is later added to the RTE. New auditing function. The new auditing function allows you to capture significant eents occurring in your site's IBM Tioli Monitoring enironment and record them in permanent storage for later retrieal and analysis. Each audit record fully describes some eent that has changed the state of your Tioli Monitoring system. Platforms coered include Windows, UNIX/Linux, i5/os, and z/os. On z/os, the auditing facility optionally creates and stores Systems Management Facility format (SMF) records. These new auditing and logging records can be stored in the Tioli Data Warehouse. Standard reports are proided ia the Tioli Common Reporting feature. In addition, a new Tioli Enterprise Portal workspace enables you to iew auditing and logging records online; see the IBM Tioli Monitoring: Tioli Enterprise Portal User's Guide for information. Whether to enable the auditing function on page 17 has more information about the new auditing feature. Supporting the auditing function required the creation of a new ICAT panel, KDSPPDS (Specify Persistent Datastore Configuration Values) panel, where you supply the PDS definition parameters; see Figure 15 on page 48. Web Serices (SOAP serer) support extended to remote monitoring serers. IBM Tioli Monitoring's Web Serices solution proides you with an industry-standard, open interface into Tioli Monitoring's performance and aailability data. With it, your site can integrate Tioli Monitoring data with external automation and integration applications. Tioli Monitoring Web Serices implements a client/serer architecture in which the client sends Simple Object Access Protocol (SOAP) requests to the SOAP serer running within the Tioli Enterprise Monitoring Serer. The SOAP serer receies, processes, then responds to the client's SOAP requests. Preiously, the SOAP serer ran only within a hub monitoring serer. The SOAP serer now can run in a remote monitoring serer as well. This means that a policy running on a remote monitoring serer can now send a SOAP request to an agent that is connected to that same monitoring serer, which is important because ersion adds new SOAP-based, on-demand and actiities, which send SOAP requests to the monitoring serer on which the policy is running. In addition, this architecture is more efficient than haing all remote monitoring serers send their SOAP requests to the hub. It also means that a policy that is running on a remote monitoring serer can continue to process SOAP requests een when the hub or the connection to the hub becomes unaailable. To actiate the SOAP serer for a remote monitoring serer, ensure you set the Enable Web Serices SOAP Serer parameter to Y when completing step Specify configuration alues on page 103. Automatic registration of products with the local monitoring serer. The runtime enironment load processing option now automatically copies the KppATR and KppCAT members from the &thile.tkandatv target data set that was installed by SMP/E to the runtime enironment &rhile.&rte.rkandatv library. You do not hae to regenerate and rerun the "Register with local TEMS" (pp#4ssss) job for each product in the runtime enironment if you apply maintenance that updates the KppATR and KppCAT members only. Instead, you can just reload the runtime enironment to refresh the members. The "Register with local TEMS" step is still required the first time you configure a monitoring agent or wheneer you apply maintenance that updates parameters. High-aailability hub monitoring serer. You can now configure a high-aailability hub monitoring serer in any sysplex enironment with dynamic irtual IP addressing (DVIPA) and shared DASD. A 8 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

21 high-aailability hub is configured in its own runtime enironment, without any monitoring agents, and can be configured on the same LPAR with a remote monitoring serer. This configuration allows the hub monitoring serer to be relocated to any suitable LPAR in the sysplex with no changes, and with minimal disruption to the components connecting to the hub. Agent failoer. During configuration of stand-alone distributed monitoring agents, you can specify a primary and secondary monitoring serer for agent connections. If an agent's primary monitoring serer goes offline, the agent connects to the secondary monitoring serer. When the primary monitoring serer 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 Proxy Agent Serices feature of Tioli Monitoring, which is not aailable on z/os. Increased default alue for minimum extended storage. For a new runtime enironment containing a monitoring serer, the default alue for minimum extended storage is now This alue indicates the minimum amount of irtual storage to be made aailable to the monitoring agents and other components communicating with the monitoring serer. You can oerride the default by specifying a alue in the PARMGEN configuration profile or (in the Configuration Tool) on the Specify Adanced Configuration Values panel during monitoring serer configuration. Eent forwarding to the Tioli Enterprise Console and Netcool/OMNIbus eent management serers. You can now forward situation eents reported to a hub monitoring serer on z/os to the Tioli Enterprise Console or to OMNIbus for correlation and management. To forward situation eents, the Tioli Eent Integration Facility (EIF) on the hub monitoring serer must be enabled, and the host name and listening port of the eent receier must be specified in the Configuration Tool. In addition, seeral tasks must be completed outside the configuration software: The destination eent serer or serers must be configured to receie the eents. A situation update forwarding process (the eent synchronization component) must be installed on the eent serer or serers. If situation eents are forwarded to OMNIbus, an EIF probe must be installed. For situation eents forwarded to the Tioli Enterprise Console,.baroc files for the monitoring agents reporting to the hub must be installed and imported on the Tioli Enterprise Console serer, and the rule base must be updated. The "Eent integration scenarios" section of IBM Tioli Monitoring: Installation and Setup Guide describes the deployment possibilities for hubs and eent serers; and the section on "Integrating eent management systems" proides detailed instructions for configuring the Tioli Enterprise Console and OMNIbus eent serers to receie the eents, including installing the eent synchronization component and the.baroc files. Decision 2: Whether and how to enable eent forwarding on page 22 in this guide explains briefly how eent forwarding works, discusses issues to consider before you enable eent forwarding on a z/os hub, and points you to more complete documentation on eent forwarding. The information for Figure 14 on page 45 and Figure 16 on page 50 gies instructions for enabling EIF and specifying the destination eent serers during configuration of the hub. Enable eent forwarding (optional) on page 124 outlines further steps you must take to enable eent forwarding and points you to instructions for configuring the Tioli Enterprise Console and OMNIbus eent serers to receie forwarded eents. Simplified persistent data store maintenance processing. The maintenance processing of the persistent datastore has been simplified. KPDPROC1 now does all the work formerly done by the maintenance job (KPDJOBC), and KPDPROC2 has been eliminated. It is no longer necessary to authorize and submit the maintenance job; howeer, because the KPDPROCC REXX procedure runs in a TSO enironment, the KPDDSCO program has to be enabled to execute as an authorized program under TSO, by adding the KPDDSCO persistent datastore module name to the SYS1.PARMLIB(IKJTSO00) under the AUTHPGM section. If you are upgrading from a preious ersion of the monitoring serer, you can remoe the KPDPROC2 member from the library. After the enironment has been completely upgraded, you can remoe any Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer 9

22 special RACF or ACF2 rules set up for KPDPROC2. See the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide for further information. Sample VSAM refresh jobs. The Tioli Enterprise Monitoring Serer configuration now generates two sample VSAM jobs: KDSDVSRN and KDSVSRF. The KDSDVSRF job deletes all the &rhile.&rte.rkds* and &rhile.&rte.rkms* monitoring serer VSAM libraries, and allocates and initializes a new set. This job is useful if you must reinitialize a remote monitoring serer or conert a hub monitoring serer to a remote. Important: Use the KDSDVSRF job with caution. It deletes all monitoring serer VSAM libraries. The KDSDVSRN job renames the original VSAM libraries. If you prefer to rename the original VSAM libraries instead of deleting them, use the KDSDVSRN job to rename the original libraries before you submit the KDSDVSRF job. The monitoring serer must be stopped before you run either job. New libraries and started task DDNAMEs. A number of new runtime libraries support new features of the monitoring serer on z/os, and corresponding DDNAMEs are added to the monitoring serer started task. Table 1 lists the new libraries and DDNAMEs. Table 1. New monitoring serer runtime libraries and started task DDNAMEs DDNAME Library suffix Description VSAM or non-vsam Hub, remote, or both DSEVT RKDSEVT EIF eent 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 command VSAM Both configuration parameter QA1DDYST RKDSDYST Deploy asynchronous command VSAM Both status QA1DEPRM RKDSEPRM Deploy asynchronous command VSAM Both execution parameter QA1DGRPA RKDSGRPA TGROUP group VSAM Both QA1DGRPI RKDSGRPI TGROUPI indiidual 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 eent mapping VSAM Hub QA1DEVSR RKDSEVSR EIF eent VSAM Hub QA1DGRPB RKDSGRPB TGROUP group VSAM Hub QA1DGRPC RKDSGRPC TGROUPI indiidual group VSAM Hub QA1DPYMR RKDSPYMR Deploy group member VSAM Hub QA1DAPPL &&rhile.&&rte. RKDSAPPL VSAM library for the self-describing agents' application properties VSAM Both The new libraries are allocated as part of the runtime enironment build job in a new enironment or as part of the Tioli Enterprise Monitoring Serer upgrade job. Reconnect after TCP/IP recycle. This setting allows the monitoring serer address space to reconnect to its TCP/IP stack without being recycled after the stack is recycled. 10 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

23 Default TCP/IP started task name. Sets the default TCP/IP started task name to a wildcard * (asterisk) for new runtime enironments. This default, which uses the first TCP/IP stack that was started, is suitable 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 the number sign (#), which is translated to a blank and allows the TCP/IP enironment to choose the stack to use, either through TCP/IP definitions or through the use of the SYSTCPD DD statement. If the IP domain name resolution is not fully configured on the z/os system, you must specify the SYSTCPD DDNAME in the started task for each monitoring serer and monitoring agent. For further information, see "Decision 5: how to set up communications between components" in the "Planning your deployment" chapter of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide. Network interface support. If your site runs more than one TCP/IP interface or network adapter on the same z/os image, you can indicate the specific local network interfaces to be used by monitoring serers and monitoring agents on z/os. For further information, see "Decision 5: how to set up communications between components" in the "Planning your deployment" chapter of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide. Chapter 1. Oeriew of Tioli Management Serices and the Tioli Enterprise Monitoring Serer 11

24 12 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

25 Chapter 2. Planning your deployment The information in this chapter is intended to help you plan a first-time deployment. If you are upgrading your monitoring serers on z/os from a preious ersion, follow the instructions in the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Upgrade Guide. For a first-time deployment, reiew the prerequisites and make the planning decisions described in Part 1 of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide. Then make the planning decisions described in this chapter: Decision 1: What kinds of monitoring serers to configure Decision 2: Whether and how to enable eent forwarding on page 22 Decision 1: What kinds of monitoring serers to configure The hub monitoring serer is the focal point for the entire monitoring enironment. This serer is under a significant load. Work on the hub includes communicating with remote monitoring serers, with the Tioli Enterprise Portal Serer, and with local monitoring agents; authenticating users; consolidating and distributing data; storing and tracking situations and policies; and initiating and tracking all generated Take Action commands. Place the hub monitoring serer inside the data center on a high-performance network. Connectiity between the hub monitoring serer and the portal serer and between the hub and remote monitoring serers must be fast and reliable. Remote monitoring serers communicate only with the monitoring agents that report to them and with the hub monitoring serer to which they report. Note that a remote monitoring serer is remote with respect to the hub monitoring serer, not necessarily with respect to the monitoring agents. If monitoring agents are installed on the same system as a remote monitoring serer, that monitoring serer is local to the monitoring agents but remote to the hub. The load on remote monitoring serers is typically low. Load is drien higher if historical data collection is performed on the monitoring serers instead of on the monitoring agents. You can install monitoring serers on z/os, Windows, and some UNIX and Linux systems. See IBM Tioli Monitoring: Installation and Setup Guide for a complete list of supported platforms. See the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide for considerations in deciding where to place hub and remote monitoring serers, for information about monitoring serer names, and for planning information for the SOAP serer. Whether to configure a high-aailability hub on z/os An operational hub monitoring serer is essential to a monitoring enironment. If the hub monitoring serer address space fails, or if the system on which the hub is installed has a planned or unplanned outage, the flow of monitoring data comes to a halt. Therefore, it is important to restart the hub or moe it to another system as quickly as possible. You can configure a high-aailability hub monitoring serer in any sysplex enironment with dynamic irtual IP addressing (DVIPA) and shared DASD. A high-aailability hub is configured in its own runtime enironment, without any monitoring agents, and can be configured on the same LPAR with a remote monitoring serer. This configuration allows the hub monitoring serer to be relocated to any suitable LPAR in the sysplex with no changes, and with minimal disruption to the components connecting to the hub. Copyright IBM Corp. 2005,

26 If you hae purchased the Tioli System Automation for z/os product, you can automate the relocation of the hub. To find instructions, search for automating a high aailability hub on the Integrated Serice Management Library website. The high-aailability hub on z/os has the following requirements: It must be configured in a sysplex. It must hae a dynamic irtual IP address (DVIPA), so it can respond to the same IP address on any LPAR in the sysplex. It must be configured stand-alone (in its own runtime enironment without monitoring agents). Its runtime libraries must be stored on shared DASD, so that the hub can start on any LPAR in the sysplex without requiring replication of the libraries. Its runtime enironment cannot use system ariables. The hub is not defined to run on any specific system, and it retains the same parameter alues on any system in the sysplex. Tip: If your enironment fulfills the requirements for a high-aailability hub, it is a good idea to configure one. Before you begin configuring the high-aailability hub, create an application-instance-specific (priate) dynamic irtual IP address, and define it to DNS as a new name (for example, OMEGAHUB). For instructions on configuring a high-aailability hub on z/os if you are configuring components and products for the first time, see Chapter 3, Configuring a high-aailability hub and the remote monitoring serers that report to it, on page 27. For instructions on modifying an existing configuration to accommodate a high-aailability hub, search for high-aailability hub on the Integrated Serice Management Library website. For instructions on configuring a high-aailability hub on a distributed system, see the IBM Tioli Monitoring: High-Aailability Guide for Distributed Systems. How many remote monitoring serers to configure If possible, place a remote monitoring serer on eery z/os system where you are installing monitoring agents. In fact, two monitoring agents (OMEGAMON XE on z/os and OMEGAMON XE for Storage on z/os) require that you configure them in the same address space as a hub or remote monitoring serer. For adice about placing remote monitoring serers on distributed systems, see IBM Tioli Monitoring: Installation and Setup Guide. 14 IBM Tioli Management Serices on z/os: Configuring the Tioli Enterprise Monitoring Serer on z/os

27 Tips A remote monitoring serer can report to a high-aailability hub on the same LPAR. If the hub is not a high-aailability hub, it cannot be on the same LPAR as any of the remote monitoring serers that report to it and that are configured to use any TCP/IP protocol. If more than one remote monitoring serer is configured in a z/os image and if a TCP/IP protocol is being used for communication, the hub to which each remote monitoring serer reports must hae a unique port number. Otherwise, connectiity problems are likely. If more than one hub is configured in a z/os image, each hub must hae a unique port number for any nonsecure TCP/IP protocols being used and a unique port number for any secure TCP/IP protocols being used. For information about port number allocation, see the "Port number assignments" section of the IBM Tioli OMEGAMON XE and IBM Tioli Management Serices on z/os: Common Planning and Configuration Guide. If a remote monitoring serer is to communicate with any monitoring agents that require SNA, the remote monitoring serer must be configured for SNA communications. Examples of such monitoring agents include OMEGAMON XE on z/os (for the EPILOG facility of the OMEGAMON II 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 capability The self-describing agents enhancement is intended to reduce the time you spend getting the common components of Tioli Management Serices and the monitoring agents that use them up and running, as well as the time and cost of maintaining Tioli Monitoring products and components once you hae them running. In addition, self-describing agents make it unnecessary for you to bring Tioli Monitoring components down and then back up so these newly installed or upgraded agents can be recognized; this can sae your site significant wasted monitoring productiity. As of Version 6.2.3, the application data necessary for the Tioli Enterprise Monitoring Serer to recognize and process data from a distributed agent need no longer be "seeded" at installation into the agent's local monitoring serer and then replicated out to the hub monitoring serer and all other Tioli Management Serices components that require it (such as the Tioli Enterprise Portal Serer and the Tioli Data Warehouse). Instead, this application support data can now be automatically replicated from the agent to its local monitoring serer wheneer the agent starts up. Thus, it is also no longer necessary that you follow each seeding step by restarting all affected Tioli Management Serices components so they can recognize and process data generated by these newly installed or upgraded agents. After you actiate the self-describing agents capability, application support is automatically refreshed wheneer a newer ersion of a self-describing agent is detected. Also, components need not be recycled eery time an update is applied (similarly, its situations, policies, and actiities are automatically redistributed and restarted), nor is it necessary each time a newly updated agent connects to its monitoring serer each update is seeded once and only once. This means you need not interrupt your enterprise monitoring wheneer you add a new self-describing agent or update an existing agent. This enhancement also means that no mainframe agents' application data need be stored on distributed systems. All updates are logged for auditing purposes. If the hub monitoring serer is eer brought down, self-describing capabilities are terminated until it is brought back online. The self-describing agents capability can be selectiely disabled on the Tioli Enterprise Monitoring Serer running on z/os, and is initially disabled when installing a hub Tioli Enterprise Monitoring Serer. It is initially enabled for remote monitoring serers; this effectiely disables support for all self-describing agents Chapter 2. Planning your deployment 15