t l tivoli monitoring

Tivoli® IBM Tivoli Monitoring

Exploring IBM Tivoli Monitoring

Version 6.2.0

SC32-1803-01

��

Edition notice

This edition applies to version 6, release 2 of IBM Tivoli Monitoring (product number 5724-C04) and to all

subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2005, 2007. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

About this publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Who should use this workbook . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Overview of information and support resources . . . . . . . . . . . . . . . . . . . . . . ix

Accessing terminology online . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Accessing publications online . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Ordering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tivoli technical training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Conventions used in this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Tivoli command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Installation exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Components in the single-computer installation . . . . . . . . . . . . . . . . . . . . . 1

Summary of the IBM DB2 installation process . . . . . . . . . . . . . . . . . . . . . 2

Computers in addition to the single-computer installation . . . . . . . . . . . . . . . . . 3

Installing IBM Tivoli Monitoring on one Windows computer . . . . . . . . . . . . . . . . . . 3

(Optional) Installing a Tivoli Enterprise Monitoring Agent on remote computers . . . . . . . . . . 8

Chapter 2. Basic monitoring exercises . . . . . . . . . . . . . . . . . . . . . . . . 13

Verifying your installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Familiarizing yourself with workspaces . . . . . . . . . . . . . . . . . . . . . . . . . 14

Monitoring a process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Limitations of the exercises to monitor a process . . . . . . . . . . . . . . . . . . . . 16

Creating a query to monitor a process . . . . . . . . . . . . . . . . . . . . . . . . 16

Creating a situation to monitor a process . . . . . . . . . . . . . . . . . . . . . . . 19

Creating custom views of the monitoring environment . . . . . . . . . . . . . . . . . . . 21

Creating a custom Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Creating a graphic view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Embedded situations: combining multiple situations to trigger one event . . . . . . . . . . . . 24

Creating an embedded situation . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Creating a correlated situation . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Using trace logs to diagnose problems . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring options for a trace log . . . . . . . . . . . . . . . . . . . . . . . . . 28

Locating and viewing a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3. Advanced monitoring exercises . . . . . . . . . . . . . . . . . . . . . . 29

Automatically responding to a situation event, using a policy . . . . . . . . . . . . . . . . 29

Automatically responding to a situation event, using a Take Action command . . . . . . . . . . 32

Working in the CLI (command-line interface) . . . . . . . . . . . . . . . . . . . . . . 33

Basic commands of the tacmd shell . . . . . . . . . . . . . . . . . . . . . . . . . 34

Creating and managing a situation . . . . . . . . . . . . . . . . . . . . . . . . . 34

Starting and stopping an agent . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Creating agents based on the Tivoli Universal Agent . . . . . . . . . . . . . . . . . . . 35

Using a script to create an agent . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Creating an agent to monitor a URL . . . . . . . . . . . . . . . . . . . . . . . . 36

Building a custom monitoring agent using Agent Builder . . . . . . . . . . . . . . . . . . 37

Chapter 4. Historical reporting exercises . . . . . . . . . . . . . . . . . . . . . . . 45

The process of historical reporting . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring basic data collection for historical reports . . . . . . . . . . . . . . . . . . . 46

Customizing data collection for historical reports . . . . . . . . . . . . . . . . . . . . . 47

© Copyright IBM Corp. 2005, 2007 iii

Viewing historical reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Real-time data versus historical data . . . . . . . . . . . . . . . . . . . . . . . . 50

Stopping historical reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Creating custom queries for historical reports . . . . . . . . . . . . . . . . . . . . . . 52

Creating a monitoring server query . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5. Administrator exercises . . . . . . . . . . . . . . . . . . . . . . . . . 55

Viewing managed system status and heartbeat . . . . . . . . . . . . . . . . . . . . . 55

Setting up Hot Standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Integrating with IBM Tivoli Enterprise Console: new approach . . . . . . . . . . . . . . . . 57

Integrating with IBM Tivoli Enterprise Console: standard approach . . . . . . . . . . . . . . 59

Enabling communications with IBM Tivoli Enterprise Console . . . . . . . . . . . . . . . 59

Displaying situation events in IBM Tivoli Enterprise Console . . . . . . . . . . . . . . . . 60

Displaying console events in the portal . . . . . . . . . . . . . . . . . . . . . . . 61

Overview of the Tivoli Enterprise Console view (located in IBM Tivoli Monitoring) . . . . . . . . 61

Chapter 6. Agent exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Using IBM Tivoli Monitoring for Databases: DB2 Agent . . . . . . . . . . . . . . . . . . . 65

Starting and stopping the IBM Tivoli Monitoring for Databases: DB2 Agent . . . . . . . . . . 65

Creating an ODBC data source . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Using situations to monitor system conditions . . . . . . . . . . . . . . . . . . . . . 67

Using workspaces to monitor system conditions . . . . . . . . . . . . . . . . . . . . 68

Chapter 7. Migration exercises: IBM Tivoli Monitoring version 5.1.2 to version 6.2.0 . . . . . . 69

Valid scenarios for the Migration Toolkit . . . . . . . . . . . . . . . . . . . . . . . . 69

Custom resource model categories . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0, basic scenario (based on the

Migration Toolkit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Conventions in the exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Basic migration exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Exercise: Performing a basic migration . . . . . . . . . . . . . . . . . . . . . . . . 73

Overview of the basic migration exercise . . . . . . . . . . . . . . . . . . . . . . . 73

Migration stage 1: Installing the Migration Toolkit . . . . . . . . . . . . . . . . . . . . 76

About the commands for the first stages of migration: winstall, javapath, password-related

commands, trace, and scantmr . . . . . . . . . . . . . . . . . . . . . . . . . 80

Migration stage 2: Creating Initial Baseline File . . . . . . . . . . . . . . . . . . . . 82

Migration stage 3: Creating an IBM Tivoli Monitoring V6.2.0 Test Environment . . . . . . . . . 86

Migration stage 4: Updating the baseline file . . . . . . . . . . . . . . . . . . . . . 88

Migration stage 5: Validating the baseline file . . . . . . . . . . . . . . . . . . . . . 89

About the commands for the later stages of migration: assess and migrate . . . . . . . . . . 90

Migration stage 6: Assessing Endpoints . . . . . . . . . . . . . . . . . . . . . . . 93

Migration stage 7: Assessing Profiles . . . . . . . . . . . . . . . . . . . . . . . . 93

Migration stage 8: Assessing Profile Managers . . . . . . . . . . . . . . . . . . . . . 94

Migration stage 9: Migrating endpoint assessment files . . . . . . . . . . . . . . . . . . 95

Migration stage 10: Migrating Profile Assess Files . . . . . . . . . . . . . . . . . . . 95

Migration stage 11: Migrating Profile Manager Assess Files . . . . . . . . . . . . . . . . 95

Post-migration activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0, complex scenario (based on the

Agent Builder) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Appendix A. Uninstalling IBM Tivoli Monitoring . . . . . . . . . . . . . . . . . . . . 99

Uninstalling a monitoring agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Uninstalling the Warehouse Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Removing the ODBC data source connection . . . . . . . . . . . . . . . . . . . . . 101

Uninstalling the IBM Tivoli Enterprise Console event synchronization . . . . . . . . . . . . . 101

Uninstalling the entire IBM Tivoli Monitoring environment . . . . . . . . . . . . . . . . . 101

iv IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Appendix B. Creating a test environment for IBM Tivoli Monitoring version 5.1.2 . . . . . . . 103

Creating profile managers and profiles . . . . . . . . . . . . . . . . . . . . . . . . 103

Subscribing resources to profile managers . . . . . . . . . . . . . . . . . . . . . . . 104

Adding resource models to a profile . . . . . . . . . . . . . . . . . . . . . . . . . 104

Distributing profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix C. Documentation library . . . . . . . . . . . . . . . . . . . . . . . . 107

IBM Tivoli Monitoring library . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Documentation for the base agents . . . . . . . . . . . . . . . . . . . . . . . . 108

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Other sources of documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Contents v

vi IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

About this publication

Exploring IBM Tivoli Monitoring provides a series of exercises that help you explore IBM Tivoli Monitoring.

After completing the activities in this workbook, you will have learned about topics like these:

v Installation and configuration of the monitoring environment

v Graphical and command line interfaces of the product

v New features in this release of IBM Tivoli Monitoring

v Types of monitoring.

Unlike previous versions of this document that included exercises for the UNIX operating system, you

perform the exercises in this document on Windows. Similar functionality and procedures exist on other

operating systems, such as UNIX, AIX, and Linux. See the IBM Tivoli Monitoring Installation and Setup

Guide for additional information.

IBM Tivoli Monitoring proactively manages the health and availability of your IT infrastructure, end-to-end,

including operating systems, databases and servers, across distributed and host environments.

Version 6.2.0 of the product includes many new features. See the "New in this release" topic of the Tivoli

Enterprise Portal Help for a complete description of these features. Table 1 lists a few of the new features,

some of which are mentioned in the exercises later in this document.

Table 1. Highlights of the new functionality in Version 6.2.0 of IBM Tivoli Monitoring

Feature Description

Common event console

view

The common event console enables you to view and manage events from the Tivoli

Enterprise Monitoring Server in the same way as the situation event console.

This console also incorporates events from the IBM Tivoli Enterprise Console server and

the Tivoli Netcool/OMNIbus Object Server if your managed environment is configured for

those servers.

Topology view For monitoring products that support the topology view, you can add the view to a

workspace to graphically show objects and their logical relationships to one another. A

topology view that is available at the Enterprise level of the Navigator is the Tivoli

Management Services Infrastructure view, which visually expresses the relationships

and linking of monitoring agents and other components to the hub monitoring server.

Workspace linking A new link type has been added to the workspace link feature that enables the link

author to identify the target workspace by the host identifier. The dynamic link type adds

more opportunities for workspace linking, such as to provide links to workspaces of

other types of monitoring agents.

Acknowledging events Operators need to acknowledge the events that they are managing. Event

acknowledgement has several new enhancements to facilitate quick acknowledgements,

writing and reviewing notes, and attaching files to the acknowledgement.

Improved workspace

usability

You can move views in a workspace. Drag a view by its title bar to a new location in the

workspace.

You can search the views in a workspace. The view toolbar for the table, notepad, and

browser views has a new Find tool for quickly searching through text in the view.

Increased options for flagging severities of situations.

© Copyright IBM Corp. 2005, 2007 vii

This document provides the types of exercises listed in Table 2.

Table 2. Categories of exercises found in this document.

Categories of exercises Principal exercises in each category

Chapter 1, “Installation exercises” “Installing IBM Tivoli Monitoring on one Windows computer” on page 3

“(Optional) Installing a Tivoli Enterprise Monitoring Agent on remote

computers” on page 8

Chapter 2, “Basic monitoring exercises” “Verifying your installation” on page 13

“Familiarizing yourself with workspaces” on page 14

“Monitoring a process” on page 16

“Creating a query to monitor a process” on page 16

“Creating a situation to monitor a process” on page 19

“Creating custom views of the monitoring environment” on page 21

“Embedded situations: combining multiple situations to trigger one

event” on page 24

“Using trace logs to diagnose problems” on page 27

Chapter 3, “Advanced monitoring

exercises”

“Automatically responding to a situation event, using a policy” on page

29

“Automatically responding to a situation event, using a Take Action

command” on page 32

“Working in the CLI (command-line interface)” on page 33

“Creating agents based on the Tivoli Universal Agent” on page 35

“Building a custom monitoring agent using Agent Builder” on page 37

Chapter 4, “Historical reporting

exercises”

“Configuring basic data collection for historical reports” on page 46

“Customizing data collection for historical reports” on page 47

“Viewing historical reports” on page 49

“Stopping historical reporting” on page 51

Chapter 5, “Administrator exercises” “Viewing managed system status and heartbeat” on page 55

“Setting up Hot Standby” on page 56

“Integrating with IBM Tivoli Enterprise Console: new approach” on page

57

“Integrating with IBM Tivoli Enterprise Console: standard approach” on

page 59

“Filtering and responding to events” on page 62

Chapter 6, “Agent exercise” “Using IBM Tivoli Monitoring for Databases: DB2 Agent” on page 65

Chapter 7, “Migration exercises: IBM

Tivoli Monitoring version 5.1.2 to

version 6.2.0”

“Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0,

basic scenario (based on the Migration Toolkit)” on page 71

“Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0,

complex scenario (based on the Agent Builder)” on page 97

Appendix A, “Uninstalling IBM Tivoli

Monitoring”

“Uninstalling a monitoring agent” on page 99

“Uninstalling the entire IBM Tivoli Monitoring environment” on page 101

Who should use this workbook

This guide is designed for individuals who are responsible for installing, planning, customizing and

monitoring IBM Tivoli Monitoring, including:

v System administrators

v System programmers

v Network administrators

v IBM® Support and Field Systems Engineers

viii IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Overview of information and support resources

This section describes information and support resources. See Appendix C, “Documentation library,” on

page 107 for a list of the publications in the IBM Tivoli Monitoring library.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software.

The Tivoli Software Glossary is available at the following Tivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient

location. You can access the Terminology Web site at the following Web address:

http://www.ibm.com/software/globalization/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become available and whenever they

are updated, to the Tivoli Information Center Web site at http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp.

Note: If you print PDF documents on other than letter-sized paper, set the option in the File → Print

window that allows Adobe Reader to print letter-sized pages on your local paper.

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755

v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli publications. To locate the

telephone number of your local representative, perform the following steps:

1. Go to http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss.

2. Select your country from the list and click Go.

3. Click About this site in the main panel to see an information page that includes the telephone number

of your local representative.

Accessibility

Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to

use software products successfully. With this product, you can use assistive technologies to hear and

navigate the interface. You can also use the keyboard instead of the mouse to operate most features of

the graphical user interface.

For additional information, see the Accessibility Appendix in the user’s guide for this product.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:

http://www.ibm.com/software/tivoli/education/

About this publication ix

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

http://www.ibm.com/software/globalization/terminology

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.ibm.com/software/tivoli/education/

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following

ways for you to obtain the support you need:

Online

Go to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and

follow the instructions.

IBM Support Assistant

The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you

resolve questions and problems with IBM software products. The ISA provides quick access to

support-related information and serviceability tools for problem determination. To install the ISA

software, go to http://www.ibm.com/software/support/isa.

Problem determination guidance

For more information about resolving problems, see the problem determination information for this

product.

Conventions used in this guide

This guide uses several conventions for special terms and actions, and operating system-dependent

commands and paths.

Typeface conventions

This guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from

surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,

list boxes, items inside list boxes, multi-column lists, containers, menu choices, menu names,

tabs, property sheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

v Words defined in text

v Emphasis of words (for example, ″Use the word that to introduce a restrictive clause.″)

v New terms in text (except in a definition list)

v Variables and values you must provide

Monospace

v Code and other examples

v File names, programming keywords, and other elements that are difficult to distinguish from

surrounding text

v Message text and prompts addressed to the user

v Text that the user must type

v Values for arguments or command options

Operating system-dependent variables and paths

The publications in this library use the UNIX convention for specifying environment variables and for

directory notation.

When using the Windows command line, replace $variable with %variable% for environment variables and

replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables

are not always the same in Windows and UNIX environments. For example, %TEMP% in Windows

environments is equivalent to $TMPDIR in UNIX environments.

x IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa

Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.

Tivoli command syntax

The following special characters define Tivoli® command syntax:

[ ] Delimits elements that are optional. Required elements do not have brackets around them.

{ } Delimits a set of mutually exclusive elements when a command requires one of them.

Note: Command elements that are not enclosed in any type of brackets are required.

... Indicates that you can specify multiple values for the previous element. Separate multiple values

by a space, unless otherwise directed by command information.

If the ellipsis for an element follows a closing bracket, use the syntax within the brackets to specify

multiple values. For example, to specify two administrators for the option [-a admin]..., use -a

admin1 -a admin2.

If the ellipsis for an element is within the brackets, use the syntax of the last element to specify

multiple values. For example, to specify two hosts for the option [-h host...], use -h host1 host2.

| Indicates mutually exclusive information. You can use the element on either the left or right of the

vertical bar, which is sometimes called the pipe character.

The following example illustrates the typeface conventions used in Tivoli command syntax:

itmcmd agent [-l] [ -h install_dir ] [ -o instance ] [ -p option ] [-c] [-s] start|stop {pc|all}

The start|stop and {pc|all} parameters are the only required parameters for the itmcmd agent command.

The brackets around the -l, -h, -o, -p, -c, and -s parameters indicate that they are optional. The braces

around {pc|all} indicate that you must either specify a product code (pc) or choose to start or stop all

components.

About this publication xi

xii IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Chapter 1. Installation exercises

This chapter describes how to deploy a small IBM Tivoli Monitoring environment on a single Windows

computer. An single-computer installation can be useful as a test environment, a teaching environment, or

for monitoring a small server environment. The following topics are covered:

v “Installing IBM Tivoli Monitoring on one Windows computer” on page 3

v “(Optional) Installing a Tivoli Enterprise Monitoring Agent on remote computers” on page 8

These exercises describe procedures for Windows. Similar functionality and procedures exist on other

operating systems, such as UNIX, AIX, and Linux. See the IBM Tivoli Monitoring Installation and Setup

Guide for additional information, including the following topics:

v Hardware and software requirements and supported operating systems.

For comprehensive information about the operating systems that Tivoli products support, see

http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html.

v Sample installation scenarios and instructions for various operating systems.

Note: IBM Tivoli Monitoring requires database software to store the monitoring data that it collects and

manages. The database must be installed and running when you are installing IBM Tivoli

Monitoring.

IBM DB2 software is provided with IBM Tivoli Monitoring, but you can use other specific database

products. The IBM Tivoli Monitoring Installation and Setup Guide lists the valid types of database.

The “Database for monitoring data” on page 2 topic summarizes key issues regarding the database

requirement. “Summary of the IBM DB2 installation process” on page 2 describes a typical

installation process.

See Table 2 on page viii for an overview of all exercises provided in this document. See Table 1 on page

vii for an overview of new features.

Overview

This section describes the set of components that you install on one computer and the components on

remote computers. As a whole, this set of components enables you to explore key features of IBM Tivoli

Monitoring.

A few optional exercises in this document require “Computers in addition to the single-computer

installation” on page 3.

Components in the single-computer installation

The single-computer monitoring environment enables you to complete most of the exercises in this

document. The environment includes the following components:

Product components

v The hub Tivoli Enterprise Monitoring Server (hub monitoring server)

v The Tivoli Enterprise Portal Server (portal server)

v The Tivoli Enterprise Portal Client (portal client)

v The Tivoli Enterprise Portal Server database (portal server database)

v The Tivoli Data Warehouse database (warehouse database)

Note: The exercises in this document are based on the use of IBM DB2. However, the

Microsoft SQL Server and Oracle applications are also valid database options.

© Copyright IBM Corp. 2005, 2007 1

http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

Monitoring agents

For the sake of simplicity the Installing IBM Tivoli Monitoring on one Windows computer exercise

instructs you to install all available monitoring agents. You use most, but not all, agents in the

exercises.

v Agents that enable historical reporting. See Chapter 4, “Historical reporting exercises,” on page

45 for more information.

– The Warehouse Proxy agent

– The Summarization and Pruning agentv Agents that monitor operating systems

– Linux® OS

– UNIX® Logs

– UNIX OS

– Windows® OSv IBM Tivoli Monitoring 5.x Endpoint

v Tivoli Universal Agent

Note: Additional types of monitoring agents are sold separately. The categories of these additional

types of monitoring are as follows:

v Monitoring for Applications (including mySAP)

v Monitoring for Cluster Managers

v Monitoring for Databases (including DB2, Oracle, Microsoft SQL Server, and Sybase)

v Monitoring for Messaging and Collaboration (including Lotus Domino and Microsoft

Exchange Server)

v Monitoring for Virtual Servers (including Citrix, Microsoft, and VMware products)

v Monitoring Express

Database for monitoring data

IBM DB2 is the database software that is provided in the basic installation package. However, you

have many configuration options for your final production environment, as in these examples:

v You can provide a Microsoft SQL Server database for use by the portal server.

v You can provide an Oracle database or a Microsoft SQL Server database for use by the IBM

Tivoli Data Warehouse.

See the IBM Tivoli Monitoring Installation and Setup Guide for detailed examples and instructions.

Note: You must use one of the supported versions of database software that is listed in the IBM

Tivoli Monitoring Installation and Setup Guide. Also, the database must be installed and

running when you are installing IBM Tivoli Monitoring.

Summary of the IBM DB2 installation process

IBM Tivoli Monitoring requires database software to store the monitoring data that it collects and manages.

The database must be installed and running when you are installing IBM Tivoli Monitoring. IBM DB2

software is provided with IBM Tivoli Monitoring, although you can use other, specific database products.

This section provides an overview of the installation process for the version of IBM DB2 that is provided

with IBM Tivoli Monitoring. The overview describes typical settings to serve as a guideline. The settings

might not match the specific conditions and needs on the computer you are using. See the IBM Tivoli

Monitoring Installation and Setup Guide for further information on database procedures and options.

1. Access the installation DVD for IBM Tivoli Monitoring.

2. Navigate to the directory for IBM DB2.

3. Double-click the DB2 Enterprise Server Edition.msi file. The DB2 setup wizard is displayed.

4. Click Next to access the License Agreement panel.

5. Accept the terms of the agreement, as appropriate, and click Next.

2 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

6. Click Next to accept the default installation option, which is Typical.

7. Click Next to accept the default behavior for installation response file.

8. Click Next to accept the default installation path.

9. Type a password for the db2admin account and click Next to apply this setting. You can accept the

other default settings.

Note: You must provide the password for the db2admin account during installation of IBM Tivoli

Monitoring.

10. Click Next to accept the default setting in the Configure DB2 instances panel of the wizard.

11. Click Next to accept the default setting in the next window. (A DB2 tools catalog is not required for

the exercises in the current document.) The Set up notifications window is displayed.

12. Deselect the option to set up notifications and click Next.

13. Click Next to accept the default settings in the Enable operating system security for DB2 Objects

panel.

14. Click Finish to enable the completion of the installation. The process run several minutes.

15. Click Finish in the Setup is complete panel to exit the wizard. IBM DB2 is automatically launched at

this time, as shown by the green icon in the Windows system tray.

Further configuration is not required. The installation wizard for IBM Tivoli Monitoring detects IBM

DB2 and configures database instances as needed.

Note: The IBM DB2 software that comes with IBM Tivoli Monitoring is enabled for use only in the

IBM Tivoli Monitoring environment. Therefore, a license key for IBM DB2 is not required.

Computers in addition to the single-computer installation

The exercises in this document are based on a single-computer installation of IBM Tivoli Monitoring.

However, some of the exercises reference additional computers. For example, you configure historical

reporting and event correlation on remote computers.

Note: With the following exceptions, you can complete all exercises in this document using the software

that comes with the base installation package for IBM Tivoli Monitoring.

v Exception 1: You must obtain software for the IBM DB2 Agent from a separate installation

image.

v Exception 2: You must work with a preexisting IBM Tivoli Enterprise Console located on a

separate computer. No software is provided for that product. This document does not describe

how to install and set up IBM Tivoli Enterprise Console. See the following exercises:

– “Integrating with IBM Tivoli Enterprise Console: new approach” on page 57

– “Integrating with IBM Tivoli Enterprise Console: standard approach” on page 59

Installing IBM Tivoli Monitoring on one Windows computer

Perform the following steps to install the hub monitoring server on a Windows computer:

Note: IBM Tivoli Monitoring requires database software to store the monitoring data that it collects and

manages. The database must be installed and running when you are installing IBM Tivoli

Monitoring. See “Summary of the IBM DB2 installation process” on page 2.

IBM DB2 software is provided with IBM Tivoli Monitoring, although you can use other, specific

database products. The IBM Tivoli Monitoring Installation and Setup Guide lists the valid types of

database. The “Database for monitoring data” on page 2 topic summarizes key issues regarding the

database requirement.

1. Double-click the setup.exe file in the WINDOWS subdirectory of the installation media. A welcome

window (Figure 1 on page 4) is displayed:

Chapter 1. Installation exercises 3

Note: Windows 2003 and Windows XP optionally display a security prompt regarding the publisher of

software applications. If this option is enabled, you might receive an error message stating that

the setup.exe file is from an unknown publisher. Disregard this error message and click Run.

2. Click Next. A window is displayed offering to install software that is required in the monitoring

environment, including a Java Runtime Environment.

The installer automatically puts a check mark in the check box for each prerequisite that it fails to

detect. You must allow those prerequisites to be installed. If the installer has left the check mark is

blank, the installer has detected the prerequisite item on the target system. The item does not need

to be installed on the system.

3. Click Next to run the installers for the selected software. The installations, if any are required, require

no settings or responses by you. Then the Software License Agreement window is displayed.

4. Click Accept to accept the license agreement. The next window displays the Choose Destination

Location window.

5. Click Next. The default directory for this installation (C:\IBM\ITM) is valid for the exercises in this

document. In the next window, you are prompted to enter an encryption key.

6. Click Next. The default encryption key (IBMTivoliMonitoringEncryptionKey) is valid for the

exploration exercises in this document. You must use this key during the installation of any

components that communicate with this monitoring server.

7. Click OK in response to the key confirmation message. The Select Features window is displayed,

where you select components to install.

Figure 1. Installation welcome window


The components that come with the IBM Tivoli Monitoring base product are listed. The components

are stored in a nested hierarchy that includes the following major categories:

Tivoli Enterprise Monitoring Agent

Tivoli Enterprise Monitoring Server

Tivoli Enterprise Portal Server

Tivoli Enterprise Portal Desktop Client

IBM Eclipse Help Server

8. Select (put a check mark beside) all categories.

All nested components are automatically selected for installation. The exercises in this document use

many, although not all, of the components in the list. For the sake of simplicity and completeness, you

should install all components during this exploration of IBM Tivoli Monitoring.

9. Click Next. Make no selections in this window. Agent deployment is not required for the exercises

described in this document.

When you install the product in a production environment, you can select one or more of the agents

in the Agent Deployment list. You choose the types of agents that you want to be available for

deployment as your Tivoli environment expands. This step creates and populates the deployment

depot, from which you can deploy agents at a later time. The IBM Tivoli Monitoring Installation and

Setup Guide describes scenarios for the use of the deployment depot.

10. Click Next in the Select Program Folder window. The default location (IBM Tivoli Monitoring) is valid

for the exercises in this document.

In the next window, you set the password for the default user of the Tivoli Enterprise Portal.

11. Make no change to the default user ID (sysadmin) and type a password for the user. For example,

type pa55word. Type the password again to confirm it.

This window is not displayed if the sysadmin user ID has already been defined in the operating

system.

12. Click Next to save your settings. The Start Copying Files window is displayed.

Note: The information in the Start Copying Files window includes a list of features that are ready to

be installed (or uninstalled). Use this list to confirm your settings.

13. Click Next. A Setup Status window displays the status of installation.

In the next window, the installer prompts you to choose additional activities in the Setup Type window,

which offers the following options:

v *Configure Tivoli Enterprise Portal (The asterisk (*) symbol denotes that this setup activity is

mandatory.)

v *Configure Tivoli Enterprise Monitoring Server (The asterisk (*) symbol denotes that this setup

activity is mandatory.)

v Configure Agents default connection to the TEMS

v Launch Manage Tivoli Monitoring Services for additional configuration options and to start Tivoli

Monitoring services

14. Select all the options and click Next.

The TEPS Hostname window prompts you to confirm the name of the computer that hosts the Tivoli

Enterprise Portal Server. For the single-computer installation, that host computer is the same

computer on which you are performing this procedure. Therefore, the correct computer name is

provided by default.


Unusual characteristic of the single-computer installation

The single-computer installation described here is unusual, because a monitoring environment

normally spans multiple computers that host monitoring servers and agents. Also, the typical

environment dedicates a separate computer to the resource-intensive activity of managing

historical data. For this reason, parts of the configuration activities in Step 15 are typically

performed on a separate computers. However, in the current procedure all these activities

happen on a single computer. Therefore, Step 15 includes an unusually high number of

substeps.

15. Accept the defaults and provide required values in the following series of configuration windows:

TEPS Data Source Config Parameters - DB2

Note: See the “Database for monitoring data” on page 2 for information in the database that

IBM Tivoli Monitoring requires.

a. Type the password of the DB2 administrator account, db2admin.

b. Type a new password for a new database named TEPS. For example, set the password

pa55word. The portal server requires this database.

c. Click OK.

The installation program uses the information on this window to automatically perform the

following tasks:

v Create the TEPS portal server database.

v Create a database user for the portal server to use to access the database.

v Configure the ODBC connection between the portal server and the database.

Warehouse ID and Password for the TEP Server

Accept the default ID (ITMUser) and create a password for this user. For example, set the

password pa55word. Then click Next.

TEP Server Connection to a Hub TEMS

Click OK. The default selection, IP.PIPE protocol, is valid for the exercises in this document.

TEP Server Configuration

Click OK. The default settings for the IP.PIPE connection (host name and port) are valid.

Click Yes on the message prompting you to re-configure the warehouse connection

information for the portal server.

Warehouse Proxy

Would you like to configure your ITM Warehouse ODBC data source?

Yes No

Setting up a data warehouse for historical reports

Warehouse Proxy Database Selection

Select DB2 in the list and click OK.

Configure DB2 Data Source for Warehouse Proxy

Accept the defaults and type the password of the DB2 administrator account.

Also type the password of the user account ITMUser. The Warehouse Proxy agent,

and Summarization and Pruning agent use this account to access the Tivoli Data

Warehouse database.


In this window, you configure the connection between the portal server and the Tivoli

Data Warehouse database. This database is the source of data for the Warehouse

Proxy agent. The Warehouse Proxy agent sends information collected from

monitoring agents to the Tivoli Data Warehouse.

The installation program uses the information on this window to automatically perform

the following tasks:

v Create the Tivoli Data Warehouse database. Notice that the eight-character default

name of the database is Warehous.

v Create a database user (called the warehouse user) for the portal server,

Warehouse Proxy agent, and Summarization and Pruning agent to use to access

the warehouse database.

v Configure the ODBC connection between the portal server and the warehouse

database.

Click OK in the message box that indicates success of this operation.

Agent configuration

Click OK. The default values are valid for the exercises in this document.

Note: Click OK in the series of prompts regarding help conversions.

Tivoli Enterprise Monitoring Server Configuration


Hub TEMS Configuration

Click OK. The default settings for the IP.PIPE connection (host name and port) are valid.

Note: Click OK to confirm the addition of application support to the TEMS (Tivoli Enterprise

Monitoring Server) that is located on the current computer.

Add application support to the TEMS

Select On this computer in the TEMS Location area and click OK.

Select the application support to add to the TEMS

Click OK to confirm the types of applications support that will be added to the Tivoli

Enterprise Monitoring Server. Be sure that all items in the list are selected.

Application support files contain specific information, such as predefined situations, for the

monitoring agents included on the IBM Tivoli Monitoring installation media.

Note: Click Next in the list box that confirms your selections.

Configuration Defaults for Connecting to a TEMS



Click OK. Click OK. The default settings for the IP.PIPE connection (host name and port) are

valid.

The installer recycles the server, applies your settings and starts the monitoring agents. Then a final

window is displayed.

16. Clear the check box next to Display the README file and click Finish. (If prompted, you should

restart your computer at this point.)

The Manage Tivoli Monitoring Services utility automatically launches after installation. You use this

utility to start, stop, and configure IBM Tivoli Monitoring components.

17. If the Manage Tivoli Monitoring Services utility is not running at this time, select the item in the

following path of the Windows Start menu: All Programs > IBM Tivoli Monitoring > Manage Tivoli

Monitoring Services. The utility is launched.


18. Inspect the status of the IBM Tivoli Monitoring components. By default, the status of the portal server

and the monitoring server is Started.

Continue exploring IBM Tivoli Monitoring as follows:

v When the installation is complete, verify the monitoring environment as described in “Verifying your

installation” on page 13.

v (Optional) The procedure Installing IBM Tivoli Monitoring on one Windows computer includes the

installation of all monitoring agents that are required in this document. However, you can optionally add

remote monitoring agents (agents that run on separate computers) to your exploratory monitoring

environment. See “(Optional) Installing a Tivoli Enterprise Monitoring Agent on remote computers.”

(Optional) Installing a Tivoli Enterprise Monitoring Agent on remote

computers

The fundamental exercise in this section, “Installing IBM Tivoli Monitoring on one Windows computer” on

page 3, includes the installation of monitoring agents; the agents that you install are sufficient to perform

most of the exercises in this document.

The current procedure tells how to install additional monitoring agents. Typically you perform this

procedure on remote computers that you want to monitor.

Agents are divided into two basic categories. These categories and the location of their executable files for

installation are as follows:

Agent category one: monitoring agents that are part of the base IBM Tivoli Monitoring installation

package

If you are installing any of the following agents, launch the installation using the setup.exe or

install.sh files that are part of the base IBM Tivoli Monitoring installation package:

v ITM 5.x Endpoint

v Linux OS

v UNIX Logs

v UNIX OS

v Tivoli Universal Agent

v Warehouse Proxy

Figure 2. Manage Tivoli Monitoring Services window


v Warehouse Summarization and Pruning

v Windows OS

Some agents require additional configuration. For example, see the additional configuration steps

in “Setting up a data warehouse for historical reports” on page 6.

Agent category two: monitoring agents that are not part of the base package

If you are installing agents that are not included in the base package (for example, DB2® or

Microsoft Exchange agents), launch the agent installation using the setup.exe or install.sh files

that are part of the various agent installation packages.

See the appropriate agent documentation for more information. Typically, this information is

located in a configuration chapter in the user’s guide for the agent.

Use the following steps to install a monitoring agent on Windows.

Note: Use either an IBM Tivoli Monitoring base product DVD for Windows or a distributed agent product

CD for Windows. The IBM Tivoli Monitoring Data Files for z/OS CD is not valid for this procedure.

1. Double-click the setup.exe file in the WINDOWS subdirectory of the installation media.

Note: Windows 2003 and Windows XP optionally display a security prompt regarding the publisher of

software applications. If this option is enabled, you might receive an error message stating that

the setup.exe file is from an unknown publisher. Disregard this error message and click Run.

The Welcome window is displayed. If you are installing this monitoring agent on a computer where

any IBM Tivoli Monitoring components (including monitoring agents) are already installed, the

Welcome window displays the Modify and Remove options. Select Modify.


Note: As you use the installation wizard, keep in mind the following distinctions:

v First-time installations and upgrades: If you are performing a fresh install (or upgrading),

selecting a check box installs/upgrades the product/support selected.

v Updates/Modifications: If you are updating an existing installation (you selected Modify on

the Welcome window), all check boxes on the Select Features window reflect your choices

during the initial installation. Clearing a check box has the effect of uninstalling the

component. Clear a check box only if you want to remove a component.

2. Click Next.

v If IBM Tivoli Monitoring components (for example, a monitoring server or monitoring agents) are

already installed on this computer, go to Step 4 on page 11.

v If a monitoring agent is the first IBM Tivoli Monitoring component that you are installing on the

target computer, a window is displayed offering to install software that is required in the monitoring

environment, including a Java Runtime Environment.

If the correct level of a specific type of required software is already installed, the check box for a

prerequisite is not selected. Otherwise, the check box is selected to indicate that you must install

the software.

Note: This window is not displayed when the required software is detected by the installer. In that

case, you see the license agreement window and you should go to Step 3b on page 11.

3. Perform the following procedures when you install the first IBM Tivoli Monitoring component on a

computer:

Figure 3. Installing a new component on a computer with an existing IBM Tivoli Monitoring component


a. Click Next to run the installers for the selected prerequisite software. See Step 2 on page 10 for

background information. The installation of this software, if any is required, runs without requiring

settings or responses by you. Then the Software License Agreement window is displayed.

b. Click Accept to accept the license agreement. You see the Choose Destination Location window.

At this point, the installer warns you if required database software is missing or cannot be

detected. You must ensure that a supported type of database is available for use by IBM Tivoli

Monitoring.

c. Respond as follows:

v If you do not have a database (DB2 or MS SQL) installed on this computer, a message

regarding potentially missing software is displayed. You do not need a database for this

procedure, because you are installing only a management agent on this computer. Ignore this

message and click Next to access the Choose Destination Location window

v Click Next in the Choose Destination Location window. The default directory for this installation

(C:\IBM\ITM) is valid for the exercises in this document. In the next window, you are prompted

to enter an encryption key.

Note: This step applies only to those agents that you install from the IBM Tivoli Monitoring

installation image. Agents installed from the agent installation image do not have this

step. (See “Agent categories” on page 8 for a description of these types of agents.) If

you are installing an agent from an agent installation image, go to step 5.

d. Click Next. The default encryption key (IBMTivoliMonitoringEncryptionKey) is valid for the

exploration exercises in this document. You must use this key during the installation of any

components that communicate with this monitoring server.

e. Click Next and then OK in response to the key confirmation message. The Select Features

window is displayed, where you select components to install.

f. Go to Step 5.

4. If the monitoring agent that you are installing in this procedure is not the first product component on

the target computer, an information message is displayed. Read and click OK. The Add or Remove

Features window is displayed.

5. Click the plus sign (+) beside Tivoli Enterprise™ Monitoring Agents to open the nested list.

Note: As you use the installation wizard, keep in mind the following distinctions:

v First-time installations and upgrades: If you are performing a fresh install (or upgrading),

selecting a check box installs/upgrades the product/support selected.

v Updates/Modifications: If you are updating an existing installation (you selected Modify on

the Welcome window), all check boxes on the Select Features window reflect your choices

during the initial installation. Clearing a check box has the effect of uninstalling the

component. Clear a check box only if you want to remove a component.

6. Select the agents that you want to install.

Note: Agents available on the IBM Tivoli Monitoring installation image include the Warehouse Proxy

agent and the Summarization and Pruning agent. Before you install these agents, refer to the

instructions in this document for setting up a Tivoli Data Warehouse solution, beginning with

“Setting up a data warehouse for historical reports” on page 6. (You can do those procedures

while the current installer window is open.)

If you are installing the agent on a computer that already has a monitoring server installed, the next

step is to populate the depot. However, If you do not have a monitoring server on this computer, this

step is skipped.

Note: The following step applies only to those agents that you install from the IBM Tivoli Monitoring

installation image. Agents installed from the agent installation image do not have this step.


7. If the installer displays the option to specify a program folder to use in your Start menu, click Next to

accept the default folder name, IBM Tivoli Monitoring.

The next window displays the installation summary details, including a detailed list of what you are

installing.

8. Click Next to begin installation of components.

The components are installed and the configuration environment is initialized. Then a Setup Type

window is displayed where you select configuration options.

9. Select only the relevant configuration options in the Setup Type window:

v Clear configuration options for components that are already installed and configured.

v Clear configuration options for components that you are not installing at this time.

v For the current procedure, be sure to select (put a check mark beside) the Configure agents

default connection to the TEMS option.

10. Click Next in the successive windows, accepting the default settings and options. These settings and

options are valid for the exploration activities that are described in this document.

After all settings are specified, the installer configures and starts the agents that you chose to install.

This process can take several minutes.

11. Clear the check box next to Display the README file.

12. Click Finish to complete the installation.

13. Select Yes or No in response the prompt to restart your computer. You must restart you computer

prior to running the agent.

14. Confirm that the monitoring agent is configured and started, as follows:

a. Select the Manage Tivoli Monitoring Services utility in the following path of the Windows Start

menu: All Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. This

window is shown in Figure 2 on page 8.

b. If you see Yes in the Configured column for the agent, take no further action. The agent was

successfully configured and started during the installation process.

c. If the value in the Configured column is blank and Template is in the Task/Subsystem column,

right-click the Template agent and do the following steps:

1) Click Configure Using Defaults.

2) Use the agent-specific configuration settings in the User’s Guide for your agent to complete

any windows that require information.

3) Repeat this step as necessary to create monitoring agent instances for each application

instance you want to monitor.

Some agents require additional configuration. For example, see the additional configuration steps in

“Setting up a data warehouse for historical reports” on page 6.


Chapter 2. Basic monitoring exercises

The exercises in this chapter describe basic monitoring concepts and tasks. The exercises reference the

environment that you created in “Installing IBM Tivoli Monitoring on one Windows computer” on page 3.

The following topics are covered:

Note: The IBM Tivoli Monitoring User’s Guide provides detailed and comprehensive information on these

topics.

v “Verifying your installation”

v “Familiarizing yourself with workspaces” on page 14

v “Monitoring a process” on page 16

Note: These exercises describe procedures for Windows. Similar functionality and procedures exist on

other operating systems, such as UNIX, AIX, and Linux. For examples and instructions, see the

IBM Tivoli Monitoring Installation and Setup Guide.See Table 2 on page viii for an overview of all exercises provided in this document.

Verifying your installation

This section describes a quick method for verifying that installation of the product was successful.

Verification consists of two basic operations: launching the portal and confirming the existence of

situations.

A situation describes a condition that you want to test. When you start a situation, Tivoli Enterprise Portal

compares the situation with the values that the monitoring agent collected. An event is registered if the

condition is met. Indicator tools alert you to events, which are displayed in the Navigator.

Every Tivoli Enterprise Monitoring Agent (also called monitoring agents or agents) provides a default set of

situations. You can use these situations to begin monitoring your environment immediately.

1. Launch the Tivoli Enterprise Portal.

You use the portal to view monitoring data and to configure monitoring. You access the Tivoli

Enterprise Portal through the desktop client or the browser client, as described here:

v Desktop client:

a. In the Windows Start menu, select Programs > IBM Tivoli Monitoring > Tivoli Enterprise

Portal. The login message is displayed.

b. Type the name (sysadmin) and password of the account that you created during installation.

Figure 4. Login prompt for the Tivoli Enterprise Portal


c. Click OK.

v Browser client:

Note: Version 1.5 of the Java Runtime Environment is required for the browser client. If IBM Tivoli

Monitoring does not detect the software, it prompts you to run the required installation

routine.

a. Start the Microsoft® Internet Explorer browser.

b. Type the following URL for the Tivoli Enterprise Portal into the Address field of the browser:

http://systemname:1920///cnp/client

where the systemname is the host name of the machine where the Tivoli Enterprise Portal is

installed.

c. Click Yes in response to any security prompts.

d. In the login prompt, type the user name and password of the sysadmin account that you created

during installation.

e. Click OK.

f. Click Yes to accept Java Security certificates for this browser session

2. Verify that some of the default situations IBM Tivoli Monitoring are available.

a. In the Navigation tree (on the upper left side of the portal), expand the tree until you see the

Windows OS monitoring agent that you installed.

b. To view the default situations, right-click the icon of this agent and select Manage Situations in the

popup menu.

A list of all available situations is displayed. This window displays the status of each situation and

many other details.

To further verify that your installation is working correctly, you can create a situation that monitors a

process on your computer. You can use the situation to stop the process manually, which triggers a

situation event. See “Monitoring a process” on page 16.

Familiarizing yourself with workspaces

A workspace in the Tivoli Enterprise Portal is the fundamental user interface in IBM Tivoli Monitoring.

Workspaces allow you to track the situations that monitor events in your environment. You watch current

conditions in your system in the bar charts, pie charts, and table views of the workspaces. You notice

indicators or messages and drill down in the workspace to specific events that have been triggered by

situations.

Perform these activities to learn more about the concept of workspaces:

1. Click on the Navigator, the view that is located by default in the upper left corner of the portal. The first

display that you see in the Navigator view is Enterprise Status workspace.

2. Click the plus sign (+) beside the icons in the Navigator to access the nested workspaces. For

example, access the following path in the Navigator: Windows Systems > Localhost > Windows OS

> Disk, where Localhost is the name of the machine that hosts the Tivoli Enterprise Portal. The last

node, Disk, is one of many attribute groups available for the monitoring of the Windows operating

system.

Note: By default, most workspaces include the Navigator view, and it is positioned in the upper-left

corner of the workspace.

3. A typical workspace: Click the Disk icon to display the Disk workspace and experiment with the

workspace as follows:

a. Right-click the Disk icon select Workspace in the pop-up menu. You see a list of links to related

workspaces.


The IBM Tivoli Monitoring User’s Guide describes how to create new workspace links using the

Link Wizard.

b. Click a view in the workspace to select it.

c. Drag the title bar of a view to reposition it in the workspace. The view is dimmed until you have

positioned it in a valid drop site. When the view is not dimmed and you release the mouse button,

the view is moved to the new position.

d. Click the Enterprise icon in the Navigator to leave the Disk workspace. The system prompts you

with the option to save the modified workspace as a new workspace. The default workspaces in

IBM Tivoli Monitoring are read-only. You cannot modify them.

e. Click No.

Icons in the titlebar of a view

The icons in the upper-right corner of each view in a workspace give you basic control over the

appearance of the view (the six icons are described in order, from left to right):

1. Edit Properties icon

Launches the Edit Properties window.

2. Show View Bars

(Available in table views) Toggles display of an additional tool bar.

3. Split vertically icon

Creates two copies of the view in the left and right halves of the original view.

4. Split horizontally icon

Creates two copies of the view in the bottom and top halves of the original view.

Notes:

a. Typically you use the split option when you plan to replace one of the two new views with

a different type of view. “Creating a query to monitor a process” on page 16 includes a

description of this type of operation.

b. When you use the split icon in a Navigator view, the second view is empty, not a copy of

the original view.5. Maximize icon

Expands the view to occupy the entire area of the workspace.

6. Remove icon

Removes the view. The neighboring view expands to occupy the empty area.

4. The Topology view: Experiment with the topology view in a workspace, which is the newest

visualization option in IBM Tivoli Monitoring, as follows:

a. Select the Enterprise node at the top of the navigation tree, if it is not already selected.

b. Right-click the node and select Workspace > Self-Monitoring Topology to display the default

topology view, which is labeled TMS Infrastructure.

c. Click on the Maximize icon (see “Icons in the titlebar of a view”) in the upper-right of the view. The

topology view expands to occupy the entire display area of the workspace.

d. Use the slider control in the upper-left to zoom in and out on the topology view. This feature is

particularly useful for viewing large, complex monitoring environments. If necessary, use the scroll

bars to bring sections of the topology into view.

e. Drag the TEPS icon in the topology view to another position in the topology view. You can

reposition this icon and any other icon in the topology view, according to your preferences.

f. Select the TEPS icon again, and right-click and choose Zoom to Selected in the pop-up menu.

Chapter 2. Basic monitoring exercises 15

The selected item (the TEPS icon) becomes the center of the topology view. If you use the slider

control to zoom (as described in Step 4d on page 15), the selected icon remains the center point.

This feature is useful when you are analyzing a large, complex topology.

g. Hover with the mouse pointer over the TEPS icon (or any other icon you want to learn about) to

see status and problem determination data, including Last heartbeat and IP Address.

h. In the toolbar located at the top of the topology view, click on the View as Table icon (hover over

the icon to see its name). The topology view is transformed into a table format.

Note: This view displays additional data regarding components that is not provided in the topology

view.

i. Experiment with the other controls of the topology view, which give additional options for viewing the

topology of the monitoring environment.

Note: The exercises in this chapter and in Chapter 3, “Advanced monitoring exercises,” on page 29 give

you extensive additional experience with workspaces.

Monitoring a process

You can use multiple strategies to gather and display data in IBM Tivoli Monitoring. This set of exercises

presents two fundamental approaches to monitoring:

v “Creating a query to monitor a process.” A query specifies which attributes to retrieve, and from where,

for display in a workspace. Use a query to display monitoring data that you want to view frequently, but

not necessarily take action on.

v “Creating a situation to monitor a process” on page 19. A situation is a set of conditions that, when met,

triggers an event. Use a situation to alert you to important conditions that you don't always watch

frequently. You can use situations monitor large numbers of important conditions, without visually

monitoring their status in a workspace.

In the exercises, you monitor a process that runs when a software application (Notepad) is being used.

You can adapt what you learn to your monitoring environment.

Limitations of the exercises to monitor a process

Some of the practices in this exercise are not typical for a production environment:

v Process monitored: Notepad, the process monitored in this exercise, does not generate

business-critical data or events. You would not normally monitor Notepad. However, you can apply the

methods in the exercise to the monitoring of critical processes in your system.

v Time spans: The span of time for threshold triggers in these exercises are extremely short. This

configuration allows you to see results quickly, but is not typical in an enterprise where you are

monitoring system performance over hours, days, and weeks, not seconds.

v Time intervals: Despite the instructions that are given in “Creating a situation to monitor a process” on

page 19, it is not typical and is not recommended to set sampling intervals under 15 minutes. In fact,

the best practice is to maximize the length of the sampling interval. That practice ensures that a

maximum amount of resources are available for monitoring hundreds or thousands of resources in an

enterprise.

v Best practices for workspaces: Although you build a new workspace in this chapter, it is a best

practice to use the default workspaces as a starting point:

– Use default workspaces, as-is, to monitor your environment.

– Save of copy of a default workspace and build a custom workspace to match a special needs in your

environment.

Creating a query to monitor a process

Create a query to monitor a process as follows:


1. Launch the Tivoli Enterprise Portal. (“Verifying your installation” on page 13 describes how to launch

the portal.)

2. In the Navigator, go to the Process workspace for the Windows OS monitoring agent. (“Familiarizing

yourself with workspaces” on page 14 introduces workspaces.)

3. Click the icon of the Process workspace. The Process workspace is displayed. Also, the popup menu

for this workspace is activated.

4. Save a copy of the Process Overview workspace as follows:

a. Right-click the icon of the Process workspace and select Workspaces > Process Overview in

the popup menu. The Process Overview workspace is displayed.

b. Select Save Workspace As in the File menu to create a copy of this workspace.

c. Type Monitoring the notepad process in the Save Workspace As dialog box.

d. Click OK.

5. Click the Process Overview table in this workspace, then click the Split vertically icon (see “Icons in

the titlebar of a view” on page 15). Two versions of the table are positioned side by side.

6. Click the Table icon (

) in the toolbar at the top of the workspace. The mouse pointer changes

to a Table icon.

7. Click on the table view in the lower right of the workspace.

The original table (named ″Process Overview″) is replaced by a default table (named ″Table″). The

default table has no filters or thresholds assigned to it.

8. Assign a query to the ″Table″ view as follows:

a. Right-click on any cell in the table and select Properties in the popup menu. The Properties


b. In the Query tab, click on the bar labeled, ″Click here to assign a query.″ A navigation tree is

displayed on the left of the window.

c. Select the Process Overview (Unicode) query in the tree under the NT Process branch.

d. Click OK. The query is assigned to the table.

e. Click Apply to save changes to the properties of the table.

Note: Do not click OK in the Properties window at this time. If you click OK in error, you must

open the Properties window again.

9. Filter the ″Table″ view as follows:

a. Click the Filters tab.

b. Deselect (remove the check mark from) the following columns: Server Name, % Processor

Time, % Privileged Time, and % User Time. Those columns do not supply information that is

useful for this exercise.

c. In the Process Name column, apply the following filter setting:

The graphic shows a setting that captures any process name that begin with the letters note,

such as the Notepad process. You achieve this filtering effect by appending the wildcard character

(asterisk, *) to the letters.

10. Assign thresholds to the ″Table″ view as follows. You assign thresholds to the Elapsed Time

(Seconds) attribute.

a. Click the Thresholds tab.

b. Configure the appearance of status messages as follows, using three settings in three separate

rows:


v In row one, click the red Critical cell and choose Informational in the pull-down menu.

v In row two, click the red Critical cell and choose Minor in the pull-down menu.

v In row three, do not change the default, a red Critical cell.

v Select (place a check mark in) the Use Icons column in each of three rows. This setting

enables the display of status icons, instead of colored cell backgrounds.

v Scroll to the right to view the attribute column for Elapsed Time (Seconds).

c. Configure thresholds in three separate rows. Your threshold settings should match the following

graphic:

v In the Informational row that you created, choose the greater-than operator (>) in the popup

menu, and then type the value 20.

v In the Minor row that you created, choose the greater-than operator (>) in the popup menu,

and then type the value 40.

v In the Critical row, choose the greater-than operator (>) in the popup menu, and then type the

value 60.

11. Click the Style tab and type Status of the notepad process in the Text field. This text becomes the

title of the table.

12. Click OK.

No instances of Notepad should be running at this time, so no thresholds should be triggered in the

table view at this point. If thresholds are triggered, access the Properties view for the table and

ensure that all settings are completed as described in this procedure.

13. Launch instances of the Notepad process as follows:

a. Select Run in the Windows Start menu.

b. Type notepad and click OK. An Notepad text file is displayed.

c. Repeat Step 13a and 13b to create a second instance of Notepad.

d. Return to the workspace that you created and press F5. The workspace refreshes and the new

Notepad processes are displayed in the Status of the notepad process table.

Note: The bar chart at the top of this workspace changes each time you press F5, reflecting

changes in system conditions. These changes are not related to the Notepad process that

you are monitoring in this exercise.

14. During the 60 seconds after you complete the previous step, press F5 several times. The status icon

for the notepad processes changes as the time thresholds are reached, at 20, 40, and 60 seconds.

(Optional) Open additional instances of Notepad and repeat this step to observe the threshold display

system that you have created.

15. Close all instances of Notepad and return to the workspace. Press F5 to see how the Status of the

notepad process table is updated.


Creating a situation to monitor a process

Create a situation to monitor a process as follows:

Use the workspace created in “Creating a query to monitor a process” on page 16 as a starting point for

the current exercise.

Note: Regarding the practice in this exercise, it is not typical and is not recommended to set sampling

intervals under 15 minutes. In fact, it is a best practice to maximize the length of the sampling

interval. Longer intervals reduce the amount of monitoring data that is collected. By collecting less

data, you free the maximum amount of computer resources for monitoring hundreds and thousands

of server resources and application resources in an enterprise.

1. Ensure that the Monitoring the notepad process workspace is open in the Tivoli Enterprise Portal.

This workspace was created in “Creating a query to monitor a process” on page 16.

2. In the Navigator, right-click the icon of the Process workspace and select Situations. The Situation

Editor is displayed. Only the situations that apply to this workspace are displayed.

3. Create a situation as follows:

a. Click the Create new Situation icon in the upper left of the Situation Editor. The Create Situation

or Rule window is displayed.

b. Type Notepad_is_running_long in the Name field of the Create Situation or Rule window.

Note: If your situation name is invalid, you cannot continue from this dialog box. For example, a

name that includes blank spaces is invalid.

c. Click OK. The Select condition window is displayed.

d. Select NT Process in the Attribute Group list on the left. The Attribute Item list updates to

reflect the attributes in the NT Process group.

e. Select Elapsed Time (Seconds), and then Shift-click to also select Process Name.

f. Click OK. The Situation Editor window updates to reflect your choices.

g. Configure the new situation as follows:

1) Click in row one of the Elapsed Time (Seconds) column.

2) Select the greater-than operator (>) and then type the value 90.

Be sure to select the greater-than operator (>) in this step. Otherwise, the threshold for the

situation does not function properly.

3) Click in row one of the Process Name column and type notepad.

4) In the Sampling interval fields, set days, hours, and minutes to zero. Set seconds to 30.

5) In the State field, select Fatal in the pull-down menu. Be sure that the Run at startup option

is selected.

h. Click the Distribution tab and confirm that the computer on which you are performing this exercise

is listed in the Assigned list. This computer is the system that you configured in “Installing IBM

Tivoli Monitoring on one Windows computer” on page 3.

If the computer is not in the Assigned list, select the computer’s name in the Available Managed

Systems list and click the arrow key to move it to the Assigned list.

i. Click OK to complete creation of the situation.

4. Create instances of the notepad process as follows:

a. Select Run in the Windows Start menu.

b. Type notepad and click OK. A Notepad text file is displayed.

c. Repeat Step 4 a and 4 b to create a second instance of Notepad.

d. Return to the Monitoring the notepad process workspace and press F5. The workspace

refreshes and the new notepad processes are displayed in the Status column of the Status of

the notepad process table.


5. Wait for 90 seconds after you complete Step 4, and then press F5.

Note: In a normal production setting, operators do not bother to press F5 as described here. If

triggered, situation events display automatically at set intervals, usually 15 minutes or more.

Watch for the Fatal alert to appear in the Navigator. You configured the display conditions for this

Fatal alert in Step 3g on page 19. You have created the Fatal alert to indicate that a serious event

has occurred regarding the Notepad process.

6. In the Navigator, use the mouse pointer to hover over the Fatal icon that your situation has

generated. A popup window is displayed.

7. Select the workspace link icon (

) that is located beside Notepad_is_running_long situation.

The Situation event workspace for this situation is displayed. The workspace includes information on

the initial and current values for the situation that has been triggered.

8. (Optional) For convenience, insert a situation event view in the Monitoring the notepad process

workspace that you created:

a. Click the Back arrow in the upper-left corner of the Tivoli Enterprise Portal. The Monitoring the

notepad process workspace is displayed.

b. Click on the Process Overview table.

In the next steps, you replace this view with a Situation event table.

c. Click the Event Console tool in the portal toolbar. The mouse pointer becomes a copy of this tool

icon.

d. Click on the Process Overview table. The Situation event table replaces the Process Overview

table. (Do not bother setting additional properties for this exercise.)

9. Close the Notepad text files that you opened.

10. Press F5 to see how the new Situation event view updates in the Monitoring the notepad process

workspace.

Notice that the alert icons disappear from the Navigator, because your closed the instances of

Notepad. However, the Initial Situation Values table continues to display the data regarding the

situation event. This behavior ensures that you are made aware of any patterns of situation events,

even if they spontaneously resolve themselves.

This exercises (Creating a query to monitor a process and Creating a situation to monitor a process) show

the basic differences between a query and a situation:

Queries

If the Monitoring the notepad process workspace is currently visible in the portal, you see status

icons in the Status of the notepad process table. These status icons are the result of query

settings, and they are not related to the Notepad_is_running_long situation that you have set up

in the current exercise.

Query-related icons are displayed only in a workspace; they are never displayed in the Navigator;

they never generate a situation event.

Situations

Events that a situation generates are always easy to see, because the Navigator displays alerts at

the top-most level of the Navigator and on all nested nodes in the view.

Situation events generate a situation event console, which is set of views in a dedicated

workspace that tracks events pertaining to the situation.

Each alert icon for a situation event is linked to the situation event console. You hover over the

icon with the mouse to access the link.


Creating custom views of the monitoring environment

This exercise introduces custom views of the monitoring environment. You create a custom view as an

alternative to the default Navigator. Table 3 compares custom views to the default Navigator. The table

shows example views, and the following exercises describes how to build them:

v “Creating a custom Navigator” on page 22

v “Creating a graphic view” on page 23

Be sure to see the IBM Tivoli Monitoring User’s Guide for a complete description of the features and

capabilities of custom views.

Note: The value of custom views increases as you increase the number of managed resources and the

amount of specialization in work teams.

Table 3. Comparing custom views to the default Navigator

Type of view Example Purpose

Default Navigator

The default Navigator provides access to all managed

systems and related workspaces. This tool enables

system administrators and operators to quickly access

the entire monitoring environment. Additional capabilities

are listed here:

v Display alerts for situation events? Yes.

v Provide links to relevant workspaces? Yes.

v Provide links to product configuration tools? Yes.

Custom Navigator

The custom Navigator provides access to a subset of

managed systems and related workspaces. This tool also

enables specialized operators to quickly access the

systems they need to manage and monitor. Additional

capabilities are listed here:


v Provide links to relevant workspaces? Yes.

v Provide links to product configuration tools? Yes.

You build this Navigator in “Creating a custom Navigator”

on page 22.


Table 3. Comparing custom views to the default Navigator (continued)

Type of view Example Purpose

Graphic view

A graphic view provides the standard visual cues of the

Navigator, such as alert icons. This view enables you to

position alert icons in a graphic, such as a regional map,

that has meaning for your organization. Additional

capabilities are listed here:


v Provide links to relevant workspaces? No.

v Provide links to product configuration tools? No.

You build this view in “Creating a graphic view” on page

23.

Prerequisites: You must do the following to prepare for this exercise:

v Install the sample product environment, as described in “Installing IBM Tivoli Monitoring on one

Windows computer” on page 3.

v Launch the portal as described in “Verifying your installation” on page 13.

Creating a custom Navigator

Perform these steps to create a custom Navigator like the one in Table 3 on page 21:

1. In the Navigator toolbar, click the Edit Navigator View tool (

). The Edit Navigator View window is

displayed.

2. Click the Create New Navigator View tool (

). A window opens for you to name the view.

3. Type Windows hardware operations as the name for the new Navigator.

4. Click OK.

The left pane of the Edit Navigator View window now displays a Windows hardware operations root

node for the Navigator that you are creating. Under this root node, you can add any subnodes that

exist in the default Navigator. In this exercise, you are creating a view that is appropriate for an

operator who only works with Windows hardware. All the subnodes of the Windows hardware

operations custom Navigator will pertain to the monitoring of Windows hardware issues.

5. In the right pane of the window (which duplicates the tree view of the default Navigator) navigate to the

following path: Windows Systems > Localhost > Windows OS, where Localhost is the name of the

computer where you performed the exercise “Installing IBM Tivoli Monitoring on one Windows

computer” on page 3.

The nodes of the Windows OS monitoring agent for Localhost are displayed.

6. Drag the follow hardware-related nodes from the right pane to the left pane, and drop them on the

Windows hardware operations root node (

). If you drag multiple items at one time, press the Ctrl

key, so that each item remains selected:

v Disk

v Memory

v Processor

7. Click Close. The Tivoli Enterprise Portal is displayed again, and the Navigator view now displays a

green Navigator update pending button.


8. Update the default Navigator view as follows:

a. Click the Navigator update pending button.

b. In the View pull-down list of the Navigator view, select the Windows hardware operations, which

you created in Step 6.

The Navigator area now displays the custom Navigator Windows hardware operations. Also, a tab

is displayed at the bottom of the Navigator area to give you quick access to your custom Navigator

at any time.

Creating a graphic view

Perform these steps to create a graphic view, like the one in Table 3 on page 21:

1. Navigate to the following subnode in the Navigator: Windows Systems > Localhost > Windows OS,

where Localhost is the name of the computer where you performed the exercise “Installing IBM Tivoli

Monitoring on one Windows computer” on page 3.

2. Be sure to click the Windows OS icon so that the Windows OS workspace is displayed.

Note: Unlike most workspaces, the Windows OS workspace has subnodes. When you add a Graphic

view to the workspace that has subnodes, the subnodes are automatically included in the view.

3. Save a copy of the workspace as follows. You always must save a copy of any default workspace that

you use. You cannot modify the default workspaces in IBM Tivoli Monitoring.

a. Select Save Workspace As in the File menu.

b. Type Regional view in the Save Workspace As dialog box.

c. Click OK.

Linked workspaces

Tip: The new workspace is saved as a linked workspace for the default Windows OS

workspace. You can reach the new workspace as follows: access the Windows OS

workspace, right-click the icon of the Windows OS workspace in the Navigator, and selecting

Workspace > Regional view in the popup menu.

4. Click the Graphic View tool (

), which is located in the toolbar at the top of the Tivoli Enterprise

Portal. The mouse icon becomes a copy of the Graphic View icon.

5. Click inside the bar chart that is located in the upper right of the portal. The bar chart is replaced by a

default graphic view. Notice that the subnodes of the Windows OS workspace are automatically

pasted on top of the image in the graphic view.

Alternate graphics

Tip: The Graphic View tool inserts a map of the world by default. You can select a different

image for the view as follows:

a. Right-click the view and select Properties.

b. Click the middle "Plot Area" of the icon that is located inside the Style tab of the Properties

dialog box. The Graph tab is displayed inside the Style tab.

c. Click Browse in the Background area of the Graph tab to locate and select a different

graphic.

In the following step you modify the graphic view for an imaginary company that manages some

Windows resources in Asia-Pacific region.

6. Click the Select tool (

) in the toolbar of the Graphic view.


Note: This tool looks similar to the regular mouse pointer, but has the power to select and move

nodes that are positioned on top of an image in the graphic view.

7. Drag the following nodes to general spots in the Asia-Pacific area of the graphic:

v Drag the Disk node to China.

v Drag the Memory node to India.

v Drag the Processor node to Australia.

8. Use the magnifier icons in the toolbar of the Graphic view to zoom to the Asia-Pacific area.

9. Click File > Save Workspace to preserve your configuration.

The graphic view in this workspace now provides the following information for an imaginary company

that manages some Windows resources in Asia-Pacific region:

v It reminds users of the locations of teams that are responsible for specific types of resources.

v It reminds users of the division of responsibilities.

v When situation events occur, the relevant nodes display alert icons, so that the responsible teams

can take appropriate action.

Floor plan graphic?

Tip: If teams work in the same city and in the same building, you could create an image of the

floor plan of the building. You could position node icons to reflect the division of responsibilities

within the building.

Embedded situations: combining multiple situations to trigger one

event

This section explains and provides exercises regarding two ways to use situations:

v “Creating an embedded situation.” Embedded situations enable you to use define conditions in a

situation and use the defined conditions embedded within multiple situations.

v “Creating a correlated situation” on page 26. Correlated situations let you monitor activities across two

or more managed systems. For example, if you want to monitor CPU usage across several systems in

your environment, you can create a situation that spans those systems.

Creating an embedded situation

Embedded situations enable you to use define conditions in a situation and use the defined conditions

embedded within multiple situations. You set up embedded situations in two stages:

Stage One: Create

situations to embed

For example, you can establish thresholds in three situations as follows:

1. CPUHigh (CPU% > 90 )

2. CPULow (CPU% < 10 )

3. SwapRateHigh (SWAP_Rate > 500 )

Note: Like the processor (CPU) usage, swap rate is a typical metric to use as an

embedded situation. This exercise uses examples based on CPU usage, but the concepts

presented here can be applied to swap rates.

Stage Two: Embed

two or more

situations from

Stage One in a new

situation

A new situation can embed two or more of the Stage One situations, as in these examples:

1. 1 + 2: Monitor for either a high or low CPU rate

2. 1 + 3: Monitor for a high CPU rate and a high swap rate

3. 2 + 3: Monitor for a high swap rate and a low CPU rate

Prerequisites

Do the following to prepare for this exercise:


v Install the sample product environment, as described in “Installing IBM Tivoli Monitoring on one


v Launch the Tivoli Enterprise Portal as described in Reviewing the details of your installation.

v Create a CPUHigh situation to use in the exercise:

1. Access the following path in the Navigator: Windows Systems > Localhost > Windows OS,

where Localhost is the name of the machine that hosts the Tivoli Enterprise Portal.

2. Be sure to click the Windows OS icon so that the Windows OS workspace is displayed.

Note: You could perform this procedure in any workspace. Use of the Windows OS

workspace is an arbitrary choice.

3. Right-click the Windows OS icon and choose Situations. The Situation Editor is displayed.

4. Click the Create new Situation icon in the upper left of the Situation Editor. The Create

Situation or Rule dialog box is displayed.

5. Set up the situation as follows:

a. Type CPUHigh in the Name field.

b. Ensure that Windows OS is selected in the Monitored Application pull-down menu,

and click OK. The Select condition dialog box is displayed.

The Select condition dialog box includes the Attribute Comparison condition type,

which is selected by default.

c. Select % Processor Time in the Attribute Group section. The Attribute Item section is

updated to display your options.

d. Choose % Processor Time and click OK. The Situation Editor for the new CPUHigh

situation is displayed. The Formula tab is selected by default.

6. Click the top row in the Formula area of the Situation Editor to define a threshold value.

7. Type 90 as the value for this row.

8. Change the default setting, equality (==), to greater than (>).

9. Click OK. Now, whenever this value exceeds 90, a situation event is triggered.

Note: You associate this situation with a managed system in the exercise, Create an

embedded situation.

v Create a CPULow situation to use in the exercise. Repeat the procedure that you followed for

the CPUHigh situation, with these differences:

– Name the situation CPULow.

– Apply a threshold value of less than (<) 10 in the Formula area of the Situation Editor.

Exercise

Create an embedded situation as follows:

1. Click the Navigator item from which you want a situation alert to originate. For this exercise,

you must choose the Windows OS node. The workspace for the item is displayed.

2. Right-click the Navigator item and choose Situations in the popup menu. The Situation Editor


3. Click the Create new Situation icon in the upper left of the Situation Editor.

4. Type Embedded_situations in the Name field.

5. Set up the situation as follows:

6. Ensure that Windows OS is selected in the Monitored Application pull-down menu.

7. Click OK. The Select condition dialog box is displayed.

8. In the Condition Type section, select Situation Comparison. The Situation Name list is

displayed, including the situations that you created for this exercise, CPUHigh and CPULow,

in the “Prerequisites” on page 24 activity.


9. Click CPUHigh, and then shift-click to also select CPULow.

10. Click OK. The Situation Editor for the new Embedded situations situation is displayed.

11. Configure the situation as follows:

a. Click row one, column one. The ″Situation is True″ (==True) value is set.

b. Click row two, column two. The ″Situation is True″ (==True) value is set.

Notes:

1) Putting ==True for each condition in the same row is the equivalent of using AND.

2) Putting the ==True condition on a different row would be equivalent to using OR.

3) If you make an error, right-click the number of a row to clear that row’s values. Then

reenter the correct values.

c. Click the Distribution tab to assign the situation to one or more managed systems.

Ensure that the local host is moved into the list of Assigned targets for distribution. (The

local host is the computer where you performed the exercise “Installing IBM Tivoli

Monitoring on one Windows computer” on page 3.)

d. Click Apply to save your changes and start the situation.

12. Click OK if a Distribution Change window is displayed. This window is displayed when an

embedded situation needs to be distributed to the indicated managed systems.

13. Click OK to close the Situation window.

Creating a correlated situation

You use correlated situations to monitor activities across two or more managed systems. For example, if

you want to monitor CPU usage across several systems in your environment, you can create a situation

that spans those systems.

Correlated situations can be useful in the following scenario:

v Two computers share a processing task n your environment.

v Computer A has a very high CPU usage.

v Computer B has a very low CPU usage.

v You create a correlated situation to monitor the loads on these computers. This correlated situation

would be triggered when high CPU usage exists on Computer A and low CPU usage exists on

Computer B.

v You can cause a Take Action command to run when the situation event occurs. For example, you can

create a Load Balancer script and launch it as part of an Action.

Correlated situations differ from regular situations in two ways:

v They contain only embedded situation predicates. The embedded situation predicate contains only the

situation name and the name of the managed system where the situation runs.

v They can be distributed only to monitoring servers.

Prerequisites

Follow the prerequisites for the exercise regarding embedded situations, “Prerequisites” on page

24.

Exercise

Create a correlated situation as follows:

1. Open the Situation Editor by right-clicking the Enterprise Navigator item and clicking

Situations.

2. Click New Situation. The Create Situation or Rule dialog box is displayed.

3. Type Correlated_situations in the Name field.

4. Select Correlate Situations across Managed Systems.


5. Click OK. The Correlated Situation Selection dialog box is displayed. A correlated situation

requires at least two conditions. In the next step you add a second situation to correlate.

6. Embed and configure the first of two correlated situations as follows:

7. Select a situation from the Available Situations list.

8. Select the local host in the Available Managed Systems list and click OK.

In this exercise, the local host is the computer where you performed the exercise “Installing

IBM Tivoli Monitoring on one Windows computer” on page 3. This computer is the hub

monitoring server for the test environment.

An updated view of the Situation Editor for Correlated_situations is displayed. The Formula

tab is selected by default, and it displays values for the situation that you selected in step 7.

9. Click in the cell below the new column in the Formula area. The value ==True is inserted

automatically.

10. Click Add Condition. The Correlated Situation Selection dialog box is displayed.

11. Add the second of two correlated situations as follows:

12. Select a situation from the Available Situations list.

13. Select a remote monitoring server from the Available Managed Systems list and click OK.

At this point in the procedure, you would select a remote monitoring server in the Available

Managed Systems list. However, the monitoring environment that you are working with in this

document lacks a remote monitoring server. Because one is not now available, you cannot

run and test the correlated situation that you are building here. Complete the steps in this

exercise to learn about the details of setting up a correlated situation. This activity can

prepare you to build working correlated situations in the future.

The Situation Editor for the new Correlated_situations situation is displayed. The Formula

tab is selected by default

14. Click in the cell below the new column in the Formula area. The value ==True is inserted

automatically.

Putting ==True for each condition in the same row is the equivalent of using AND. (Putting

the ==True condition on a different row would be equivalent to using OR.)

15. Set the monitoring interval in the Sampling interval section. For the purposes of test and

experiment, you might want to decrease the default interval of 15 minutes.

Note: Intervals of 15 minutes or greater are recommended for a production environment with

large amount of monitoring agents. Otherwise the demand on computer resources can

become excessive.

16. Click the Action tab. Ensure that the System Command option is selected in the Action

Selection area.

17. Type a command in the System Command field to launch the load balancing program. This

command would run when the correlated situation is true. The command might look similar to

following:

LoadBalancer TargetComputerA TargetComputerB

18. Click Apply to save your changes and start the situation.

19. Click OK to close the Situation window.

Using trace logs to diagnose problems

Trace logs are a valuable troubleshooting tool. They capture information about the operating environment

when component software fails to operate as intended.

At some point, you might encounter an error with IBM Tivoli Monitoring that requires the help of IBM

Software Support. The support representative might ask you to submit a copy of one or more logs.


The principal type of log is the reliability, availability, and serviceability (RAS) trace log. RAS logs are in the

English language only. The RAS trace log mechanism is available on the Tivoli Enterprise Monitoring

Server, the Tivoli Enterprise Portal Server, and the computers that host monitoring agents. By default, the

logs are stored in the installation path for IBM Tivoli Monitoring.

Note: The following exercises introduce trace logging, but should not result in any changes to the default

configuration of logging. Do not change the logging configuration unless you are an experienced

IBM Tivoli Monitoring customer or are working with IBM Software Support staff.

Configuring options for a trace log

A kcjras1.log log file is created automatically the first time you start Tivoli Enterprise Portal. This log file

contains all RAS1 tracing for the Tivoli Enterprise Portal client. By default, the log captures error

information only. You can increase or decrease the amount of information collected as follows:

1. In the Tivoli Enterprise Portal, select Trace Options in the File menu. The Trace Options dialog box is

displayed.

2. Select NONE or ALL in the Trace components pull-down menu.

Note: Limit your use of the ALL setting to specific troubleshooting sessions. Otherwise, the amount of

data collected could fill the hard disk and consume excessive processor resources.

3. For this exercise, click Cancel instead of OK, because there is no need to change the default

configuration at this time.

To set trace log options for other components, see the instructions in the trace logging topic of the IBM

Tivoli Monitoring Problem Determination Guide.

Note: Unlike the kcjras1.log file, the log files for other components are configured through the Manage

Tivoli Monitoring Services window, as described in the problem determination guide.

Locating and viewing a log file

Inspect the RAS log file for the Tivoli Enterprise Portal client as follows:

1. Launch the Manage Tivoli Monitoring Services window as follows: select Manage Tivoli Monitoring

Services in the following path of the Windows Start menu: All Programs > IBM Tivoli Monitoring >

Manage Tivoli Monitoring Services.

2. Right-click on a Tivoli Enterprise Portal row.

3. Select Actions > Advanced > View Trace Log in the pop-up menu. The TMS Log Viewer is

displayed.

4. Scroll to the bottom of the log file view at the bottom of the viewer. The last line is the newest event

logged for the Tivoli Enterprise Portal.

Another option of viewing this log files is to use a text editor to open it. You can navigate

toinstall_dir\CNP\LOGS and open the kcjras1.log log file. The IBM Tivoli Monitoring Problem

Determination Guide describes the locations of all trace log files.


Chapter 3. Advanced monitoring exercises

This section provides the following advanced monitoring exercises:

v “Automatically responding to a situation event, using a policy”

v “Automatically responding to a situation event, using a Take Action command” on page 32

v “Working in the CLI (command-line interface)” on page 33

v “Creating agents based on the Tivoli Universal Agent” on page 35

v “Building a custom monitoring agent using Agent Builder” on page 37

Automatically responding to a situation event, using a policy

In this exercise, you create a policy that automatically responds to a situation event as follows:

1. At first, a situation is running to detect when a specific process runs beyond a time limit.

2. When the situation is triggered (the process runs beyond the limit), a situation event is generated.

3. A policy detects the situation event and automatically starts a second situation that tracks a relevant

metric in the Windows operating system.

In general, you use policies to perform actions, schedule work, and automate manual tasks on one or

more managed systems in your enterprise. The Workflows window shows all the policies available in your

enterprise and enables you to start or stop a policy, create new policies, and edit or delete a policy.

Prerequisites: You must complete the following exercises in preparation for this exercise:

1. “Installing IBM Tivoli Monitoring on one Windows computer” on page 3.

2. “Creating a situation to monitor a process” on page 19.

This exercise includes the launching of the Notepad_is_running_long situation. You must stop this

situation prior to configuring a related policy, as follows:

a. In the toolbar of the Tivoli Enterprise Portal, select Edit > Situation Editor. The Situation Editor is

displayed.

b. Click the plus (+) sign beside the Windows OS node. The list of situations for the Windows OS

agent is displayed.

c. Select the Notepad_is_running_long icon.

d. Right-click the icon and select Stop Situation in the pop-up menu.

e. Click Close to dismiss the Situation Editor.

Instructions for the exercise:

1. Click Edit > Workflow Editor. The Workflows window is displayed.

A Policy Details section is located at the top part of the window, including a table that lists all

available policies. The Workflow Editor section occupies the bottom part of the window.

2. Click the New Policy tool (

) at the top of the Policy Details section. The system prompts you to

name the new policy.

3. Type Notepad_Policy in the Policy name field of the prompt.

4. Click OK. The new policy is added to the table in the Policy Details section. The system also adds

the name to the title bar of the Grapher view in the Workflow Editor section.

5. Configure the behavior of this policy in the Notepad_Policy row of the table in the Policy Details

section as follows:

a. Click the Distributed check box. The Change Policy Distribution dialog box is displayed.

b. Keep the default Auto start setting, which is "selected" (a check mark is displayed in the Auto

start check box).


c. In Available Managed Systems section of the dialog box, select the item named

Primary:LocalHostName:NT, where LocalHostName is the name of the computer where you have

performed the Installing IBM Tivoli Monitoring on one Windows computer procedure.

d. Click the left-arrow button to move the item to the Assigned section.

e. Click OK to save your settings.

In the next steps, you continue to work in the Workflow Editor.

6. In the General activities tab of the Workflow components section, click the Wait until a situation is

True icon.

7. Click inside the Grapher view to position an instance of the icon. The Select a Situation dialog box is

displayed.

Note: You must stop situations that you want to add to a policy, as described in “Stopping the

situation” on page 29.

8. Select the Notepad_is_running_long situation.

9. Click OK. The activity icon is displayed in the Grapher view with a Wait until

Notepad_is_running_long is True label.

10. Scroll to the bottom of the General activities tab.

11. Click the Start/Stop a situation icon to select it.

12. Click inside the Grapher view to place the icon. The Start or Stop a Situation dialog box is displayed.

13. Complete the dialog box as follows:

a. Keep the default Action setting, which is Start situation.

b. Select the NT_Bottleneck_Memory situation.

c. Click OK. The activity icon is displayed in the Grapher view with a Start situation

NT_Bottleneck_Memory label.

14. Connect the two icons in a workflow as follows:

a. In the General activities tab, click the arrow (Connector) tool.

b. Click the Wait until Notepad_is_running_long is True icon, and then click the Start situation

NT_Bottleneck_Memory icon.

The Select a Link condition window is displayed with a list of possible conditions.

c. Select Situation is true in the Select a link condition window.

d. Click OK. A line connects the two icons and represents the workflow and conditions as the activity

flows from the first icon to the second icon.

Note: An additional, optional activity for the policy could be to stop the Notepad_is_running_long

situation.

15. Click the Validate tool (

) to confirm that the policy is valid. If the Validate tool detects an error,

you must fix the problem before you can save the policy.


Validation errors

The following example illustrates invalid policy logic and how the Validate tool detects a

problem:

a. The user configures the policy to wait for a situation to become true.

b. At that time, the policy starts monitoring activity by another, related situation. However, due

to user error, the policy references the same situation in both steps. In effect, the policy

attempts to start the situation that was already running and had just become true.

c. The Validate tool indicates errors as follows:

v The border of the icons changes from magenta to black.

v The label changes from black to red.

v The shape changes from a rounded rectangle to a rectangle.

v The tip changes to the last error that applies to the activity.

16. Start the policy as follows:

a. Select the Notepad_Policy row of the table in the Policy Details section.

b. Click the Start Policy tool (

) to start the policy. The system prompts you to save the policy.

c. Click Yes. The system prompts you to start the policy on specific monitoring servers.

d. Select the hub monitoring server that you created in Installing IBM Tivoli Monitoring on one

Windows computer.

e. Click Start.

f. Drag the Workflows window to one side, so that the Tivoli Enterprise Portal is visible. (You return

to the Workflows window later in this exercise.)

17. Test the policy as follows:

a. In the Tivoli Enterprise Portal, right-click Windows OS in the Navigator tree and click Manage

situations.

b. Ensure that the NT_Bottleneck_Memory situation is stopped.

c. Click Close to dismiss the window.

d. Open an instance of Notepad and allow it to run for a few minutes, so that it generates a situation

event.

e. Right-click Windows OS in the Navigator tree and click Manage situations.

f. Confirm that the NT_Bottleneck_Memory situation has started. This activity is the result of the

Notepad_Policy policy.

18. Stop the policy to end this exercise:

a. Drag the Workflow window to the center of the Windows desktop.

b. Select the Notepad_Policy row of the table in the Policy Details section.

c. Click the Stop Policy tool. The system prompts you to stop the policy on specific monitoring

servers.

d. Select the hub monitoring server that you created in “Installing IBM Tivoli Monitoring on one


e. Click Stop.

Chapter 3. Advanced monitoring exercises 31

Automatically responding to a situation event, using a Take Action

command

The goal of this exercise is to create a Take Action command that automatically responds to a situation

event that the Notepad_is_running_long situation generates. (This situation is created in “Creating a

situation to monitor a process” on page 19):

In this exercise, you create a Take Action command that automatically responds to a situation event as

follows:

1. At first, a situation is running to detect when a specific process runs beyond a time limit.

2. When the situation is triggered (the process runs beyond the limit), a situation event is generated.

3. A Take Action command detects the situation event and automatically runs a command to generate a

report.

Take Action commands interact directly with applications and the operating system. The current exercise

has the following limitations:

v The Take Action command in this exercise merely captures and records a metric from the operating

system. However, Take Action commands can perform a variety of operations. A Take Action command

can run a script, restart a process on the managed system, send a text message to a cell phone, and

more.

v In this exercise, you associate the Take Action with a situation event, but you can associate a Take

Action with a policy instead. Also, you can create a Take Action command that is available in the Take

Action > Select option of the pop-up menu of any view in a workspace. However, be aware that

attributes that you might capture in a Take Action command are not available in all contexts of the

portal.

Prerequisites: You must complete the following exercises to prepare for the current exercise:

v “Installing IBM Tivoli Monitoring on one Windows computer” on page 3

v “Creating a query to monitor a process” on page 16

v “Creating a situation to monitor a process” on page 19

Instructions for the exercise:

1. In the Tivoli Enterprise Portal, access the Manage Situations window.

You access this window by selecting Manage Situations in pop-up menu for the Windows OS node

in the Navigator.

2. Confirm that the status of the Notepad_is_running_long situation is Started.

3. Click Close to dismiss the window.

4. Open an instance of Notepad.

By running Notepad for a few minutes you trigger a situation event.

5. In the toolbar of the portal, select Edit > Situation Editor. The Situation Editor is displayed.

6. Navigate to and select the icon that represents the Notepad_is_running_long situation. The editor

view for the situation is displayed.

7. Select the Action tab. Ensure that System Command is selected in the Action Selection area.

8. Type the following string into the System Command field:

echo "Snapshot of the Notepad situation event"

9. Select data to add to the report generated by the Take Action command as follows:

a. Add a blank space after the string that you typed and click the Attribute Substitution button. The

Select attribute window is displayed.


Notice that only the NT Process attribute group is available in this window. The Take Action

command can utilize only the attributes that are referenced by the Notepad_is_running_long

situation.

b. Select the Server Name attribute item and click OK. The &{NT_Process.Server_Name} variable

is inserted into the System Command field.

When the Take Action command runs, this variable is resolved as the name of the affected server.

c. Add a blank space after the string that you typed and click the Attribute Substitution button

again.

d. Select the Timestamp attribute item and click OK. The System Command field is updated to

reflect your choice.

e. Add a blank space after the string that you typed and click the Attribute Substitution button

again.

f. Select the ID Process attribute item and click OK. The System Command field is updated to

reflect your choice.

10. Ensure that the cursor is positioned at the end of the System Command string and type the following

directive:

>> c:\data\snapshot.txt

This directive causes the string for the echo command and the variables in the Take Action command

to be output to the file and path that you specify.

11. Use the mkdir c:\data command in a command prompt window to create the required directory.

Note: The System Command of the Take Action creates the required text file automatically.

12. Return to the Tivoli Enterprise Portal and select Take action on each item in the "If the condition is

true for more than one monitored item" section.

13. Click OK to save the Take Action command.

14. In Windows Explorer, navigate to and open the c:data\snapshot.txt file. The following output is typical

and reflects the echo string, the process ID number for two instances of Notepad, host name, and

timestamp:

"Snapshot of situation event" 4004 Primary:IBM-99999999999:NT 1070725155718343

"Snapshot of situation event" 3244 Primary:IBM-99999999999:NT 1070725155718343

15. Important: Stop the situation as follows to prevent the Take Action command from accumulating

excessive report data:

a. In the toolbar of the Tivoli Enterprise Portal, select Edit > Situation Editor. The Situation Editor is

displayed.

b. Click the plus (+) sign beside the Windows OS node. The list of situations for the Windows OS

agent is displayed.

c. Select the Notepad_is_running_long icon.

d. Right-click the icon and select Stop Situation in the pop-up menu.

e. Click Close to dismiss the Situation Editor.

Working in the CLI (command-line interface)

You can use the command line interface (CLI) in IBM Tivoli Monitoring to perform administrative tasks like

the following:

v “Creating and managing a situation” on page 34

v “Starting and stopping an agent” on page 35

You perform these operations in the Tivoli administrative command (tacmd) shell. The tacmd commands

provide the following capabilities, among others:

v Create a node for deployment of monitoring agents.


v Stop, start, restart, and configure monitoring agents.

v Obtain details about installed IBM Tivoli Monitoring components.

Basic commands of the tacmd shell

The tacmd commands server both UNIX-based and Windows operating systems. In Windows, the tacmd

shell is available at all times in the command line interface. You do not need to launch or set up the shell

environment. For example, you can enter the command tacmd help from any directory on the computer

that hosts the monitoring server.

tacmd help

Enter this command to see a list of available commands and descriptions.

tacmd command help

Enter this command to see help for a specific command. You enter tacmd command help, where

command is the name of a tacmd command, such as viewagent or createnode.

tacmd login

Use this command to begin working with administrative commands. You enter the following

command to log in to the monitoring server:

tacmd login -s host -u username -p password

where host is the name of the computer that hosts the monitoring server and the username and

password values correspond to a valid user account in the IBM Tivoli Monitoring environment.

Note: The preceding command is targets a monitoring server on the local computer. See IBM

Tivoli Monitoring Administrator’s Guide for a complete description of options and syntax for

this command.

tacmd listSystems

Run the following command to list the managed systems (computers themselves and the

applications and resources that run on the computers) that you are monitoring. The list includes

the version number of each managed system.

tacmd listSystems

Creating and managing a situation

Before you do this task, complete the exercise “Creating a situation to monitor a process” on page 19 so

that you have a situation to work with.

Run the following steps on the computer where you installed the monitoring server in the exercise

“Installing IBM Tivoli Monitoring on one Windows computer” on page 3:

1. Open a command line window (or terminal window).

2. Log in to the monitoring server as described in “Basic commands of the tacmd shell.”

3. Run the following command to export the details of the NT_Bottleneck_Disk situation to a file:

tacmd viewSit -s NT_Bottleneck_Disk -e NewSituation.out

The NewSituation.out output file is exported to the Windows root directory, for example,

c:\NewSituation.out. The file is structured in XML format.

4. Open the file in a text editor, and enter new parameters inside the following XML tag sets:

v <SITNAME></SITNAME>: Change from NT_Bottleneck_Disk to NewSituation.

v <REEV_TIME></REEV_TIME>: Change from 000030 to 001500

5. Save and close the file.

6. Run the following command:

tacmd createSit -i NewSituation.out


The parameters in the .out file are used to construct a new situation in the Tivoli Enterprise Portal.

Note: The .out file is valid for use on other computers in the IBM Tivoli Monitoring environment. You

could run the tacmd createSit command against the .out file on another computer and create a

new situation there.

7. Run the following command to see a list of all situations:

tacmd listSit

8. (Optional) Run the following command to delete the new situation:

tacmd deleteSit -s NewSituation

Note: See IBM Tivoli Monitoring Administrator’s Guide for a complete description of options and syntax for

the tacmd commands.

Starting and stopping an agent

Run the following command to stop Windows OS (operating system) agents:

tacmd stopAgent -t nt

The nt parameter is the two-letter agent identifier for Windows OS agents. Other identifiers are lz (Linux)

and ux (UNIX).

Run the following command to start Windows OS agents:

tacmd startAgent -t nt

This command starts Windows OS agents on the monitoring server.

Creating agents based on the Tivoli Universal Agent

The Tivoli Universal Agent is included with IBM Tivoli Monitoring to help you create custom monitoring

agents. The following exercises describe two ways to work with the Tivoli Universal Agent:

v “Using a script to create an agent”

v “Creating an agent to monitor a URL” on page 36

Before you begin these exercises, ensure that the Tivoli Universal Agent is installed and running as

described in Step 1 of “Using a script to create an agent.”

Using a script to create an agent

Perform the following steps to create a custom monitor from a script.

1. Confirm that the Tivoli Universal Agent is available as follows:

a. Open the Manage Tivoli Monitoring Services window in the following path of the Window Start

menu: All Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services. The utility

is launched.

b. Confirm that the Tivoli Universal Agent is displayed in the list and has Started as its Status:

v If the status is not Started, right-click the Tivoli Universal Agent row and select Start in the

pop-up menu.

v If the Tivoli Universal Agent is not displayed in the list, install it as described in “(Optional)

Installing a Tivoli Enterprise Monitoring Agent on remote computers” on page 8.

2. Create a simple script to monitor as follows:

The source of monitoring data is called a data provider. The data provider in this agent is a script. In

this exercise, you build an agent to monitor whether this script is running or not running.

a. Enter the following commands in a text file:


@echo OFF

echo 1

b. Save the file as test.bat in a temp directory in the following path: c:\temp.

3. Create the Tivoli Universal Agent script

The script that the Tivoli Universal Agent uses is called the metafile (*.MDL). Create a metafile as

follows:

a. Copy and paste the following code into a text file:

//APPL Sample

//Name NumericScript K 1200 AddTimeStamp SkipNonNumericData=Y

//Source script c:\temp\test.bat Interval=60

//Attributes

HostName (GetEnvValue = HOSTNAME)

Script (GetEnvValue = PROBE)

PreviousValue (GetEnvValue = PREV_VALUE)

Stdout C 999999999999

Notice that the code identifies the data provider (the test.bat file), and the attribute group for which

to gather data.

b. Save the file as script.mdl in the metafiles directory. This directory is located in the following path

in the product installation path: install_dir\itm\tmaitm6\metafiles, where install_dir is the path

where you installed the product.

4. Import the metafile to the Tivoli Universal Agent.

a. Start the Tivoli Universal Agent console as follows:

1) Launch the command line interface for Windows.

2) Navigate to the following directory: install_dir\itm\tmaitm6, where install_dir is the path

where you installed the product.

3) Run the following command to invoke the console for the Tivoli Universal Agent:

kumpcon

b. Type the following command and press Enter:

import script.mdl

You are prompted to confirm the command.

c. Type yes and press Enter.

d. Press Enter again to exit the console.

5. Generate and view the data in the Tivoli Enterprise Portal as follows:

a. From a command line, run the test script.

b. Open the Tivoli Enterprise Portal.

c. Click

Apply Pending Updates. This action updates the Tivoli Universal Agent with the new

monitor.

d. In the Navigator, expand the nodes for the computer where you performed this exercise until you

see the Tivoli Universal Agent.

e. Click the host_name:Sample Navigator item (where host_name is the name of the computer) to

display the workspace.

f. (Optional) Create a situation to monitor the information gathered by this new monitor. “Creating a

situation to monitor a process” on page 19 introduces basic concepts of creating a situation.

Creating an agent to monitor a URL

Perform the following steps to create an agent to monitor a URL:

1. Configure the Tivoli Universal Agent to monitor URLs as follows:

a. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services to open

the Manage Tivoli Monitoring Services window.


b. Right-click the Tivoli Universal Agent in the list of components and select Configure Using

Defaults in the pop-up menu.

Note: If you previously configured the Tivoli Universal Agent, the Configure Using Defaults is

not active. You must select Reconfigure instead.

c. Click Yes when the system prompts you to update the KUMENV file.

d. Click OK in the next message that is displayed. The KUMENV file is displayed.

e. Scroll down to the KUMA_STARTUP_DP line and add http:

KUMA_STARTUP_DP=asfs,http

f. Save and close the file.

g. Click Yes when the system prompts you about applying your changes to the Tivoli Universal

Agent.

2. Ensure that the status of the Tivoli Enterprise Portal client, Tivoli Enterprise Portal Server, and Tivoli

Enterprise Monitoring Server is Started. Otherwise, right-click the item and select Start.

3. Right-click Tivoli Universal Agent.

4. Select Start from the list of options.

5. Start the Tivoli Enterprise Portal client.

6. Expand Windows Systems to locate Universal Agent.

7. Click the localhostname:HTTPdp:UAGENT00 node, where localhostname is the name of the

computer where you are performing this exercise.

8. Create a Take Action command to monitor a URL as follows:

a. Right-click the node and select Take Action > Select in the pop-up menu. The Take Action


b. Select URL Add from the Name pull-down menu. The Edit Argument Values window is

displayed.

c. Type http://www.ibm.com in the URL field.

d. Click OK. Items are added to the Destination Systems list.

e. Select localhostname:INTERNET00 in the list.

f. Click OK. The Action Status window is displayed.

g. Click OK.

9. Expand the localhostname:HTTPdp:UAGENT00 node in the Navigator.

10. Click the ACTION sub-node.

The corresponding workspace is displayed. The Report table view reflects the Take Action command

that you created.

11. Expand the localhostname:INTERNET00 node in the Navigator.

12. Click the MANAGED_URL sub-node to see the status and other details regarding the www.ibm.com

URL.

Building a custom monitoring agent using Agent Builder

The IBM Tivoli Monitoring Agent Builder tool provides a graphical user interface to help you build a

monitoring agent. The Agent Builder is a plug-in for the Eclipse 3.2 platform. Eclipse is an open-source

framework for construction of software development tools and desktop applications.

Note: Installation of Eclipse happens during the installation of the Agent Builder. A separate installation

operation is not needed.

This exercise provides a introduction to the overall process of using the Agent Builder tool. With slight

modifications to match the conditions on your computer, the following exercise could result in a functioning


monitoring agent, however, that is not the goal of this introductory exercise. The IBM Tivoli Monitoring

Agent Builder: User’s Guide provides comprehensive instructions for building functioning agents that

address special needs in your company.

Prerequisites: Before you can run IBM Tivoli Monitoring Agent Builder, you must meet the following

requirements.

v The user account that you use must have Administrator authorization for the following reasons:

– Consistency of the running environment for the distributed Agent Builder, with the ability to load, test,

and run an agent that is designed with the Agent Builder.

– Ability to access parts of the operating system, which requires Administrator authorization. The Agent

Builder is installed on a development system and is designed for developers who require this type of

access.

v To create an agent, you must first install IBM Tivoli Monitoring. And that product must be running on

your system. Also, one of the OS (operating system) agents must be running on your system. When

you complete the procedure “Installing IBM Tivoli Monitoring on one Windows computer” on page 3 you

create these prerequisites.

Note: The browsers in the Agent Builder operate on the data sources and information from the system

on which the Agent Builder is run. Ensure that you run the Agent Builder on either of the

following types of systems:

– A system that is running on the same level as the operating system and monitored

applications for which you are developing the agent

– A system that connects to one that is running on the same level as the operating system and

monitored applications for which you are developing the agent

1. Install the IBM Tivoli Monitoring Agent Builder:

a. Access the software image for Agent Builder. For example, you might download a copy of the

software image from the Passport Advantage web site.

b. Run the setup.exe executable. The Welcome panel is displayed.

Figure 5. Welcome panel of the installer for the Agent Builder tool

c. Click Next.

d. Select I accept the terms in the license agreement and click Next. The installer prompts you to

specify the directory path for the tool.


e. Click Next, accepting the default path: C:\Program Files\IBM\ITM\AgentBuilder. The summary

information for your installation is displayed.

f. Click Install. The window displays an installation progress bar.

g. Click Finish.

2. Create a monitoring agent:

a. Select the Agent Builder shortcut in the following path of the Windows Start menu: Start > All

Programs > IBM Tivoli Monitoring > Agent Builder.

b. Click OK in the Workspace Launcher box to accept the default location for the workspace of the

Agent Builder (C:\Documents and Settings\user_name\workspace). The Agent Builder workspace is

displayed.

Note: The Agent Builder "workspace" exists in the Eclipse, the open-source framework for

construction of software development tools and desktop applications. The Agent Builder

workspace is distinct from IBM Tivoli Monitoring workspaces, which display monitoring

data.

c. Select File > New > IBM Tivoli Monitoring Agent. The Welcome panel is displayed.

Figure 6. Welcome panel of the wizard for the Agent Builder tool

Note: You might not see the wizard at this time if you are not using the Resources or IBM Tivoli

Monitoring perspectives in Eclipse. The IBM Tivoli Monitoring perspective opens when

you end the wizard, and the problems view opens by default as well.

d. Click Next. The first panel of the wizard is displayed.

e. Type Event_Log_demo in the Project name field. The check box is selected (checked) by default;

do not remove the check mark.

f. Click Next. The Agent Information panel is displayed.


g. Specify the sample values listed in the following table:

Name of field Sample value to type

Service name Event_Log_demo

This name is carried over from the previous panel. This name becomes the name of the

agent that you build. It also becomes the name of the service that represents the agent

in the Windows operating system.

Company identifier mycompany

The company name in the URL of a corporate Web site makes a good company

identifier. For example, the example identifier here would derive from a company URL,

such as www.mycompany.com

Agent identifier Event_Log

Display name Event_Log

Product code K00

Customers who use Agent Builder can use the K00-K99. Other values are restricted.

Version 111

This value indicates that you are creating “Version 1.1.1” of your example agent.

Support multiple instances

(a check box)

Skip. It is not necessary to select this option.

Copyright My_Company Corporation, 2008

This copyright statement is inserted into all of the files that are generated for the agent

and can be edited when needed. After you supply the statement once, the IBM Tivoli

Monitoring Agent Builder remembers your copyright statement and displays it in the

copyright area each time that you start the wizard to create a new agent. If you are

unsure what information you want to supply about the copyright, contact your legal

department for your company.


h. Click Next. The Monitoring Information panel is displayed.

Figure 7. Monitoring Information panel of the Agent Builder tool

3. Configure the behavior of the new monitoring agent:

a. Select This agent will monitor Windows log events.

b. Click Next. The Windows Event Log Definition panel is displayed.

After you build and configure log filtering for the agent, this view will list the Windows Event Logs

for which you have constructed filters.

c. Click Add on the Windows Event Log Definition panel. The Windows Event Log window is

displayed.

Note: The fully-configured Windows Event Log window is shown in Figure Figure 8 on page 42.

The following steps describe how to fully configure this window.


Figure 8. Completed configuration window for the Agent

Builder exercise

d. Select Application in the Windows Event Log name pull-down list.

e. Select the Filter by event type option and select Error in the Event types area.

At this point, the agent is configured to capture (filter) all Errors that Windows logs for applications.

f. Configure the event source that you want the agent to monitor as follows:

1) Select the Filter by event source option and click Add. The Event Source window is

displayed.

2) Click Browse, select .NET Runtime in the browser, and click OK.

At this point, the agent is configured to capture only errors that Windows logs for the .NET

application.

Note: If .NET Runtime is not available, choose any other event source. The goal of this

exercise is to introduce you to the concepts and procedures of the Agent Builder. It is not

necessary to build a functioning agent.

3) Click OK in the next confirmation dialog box.

g. Configure the agent to monitor a specific event identifier as follows:

Note: You must know the number of each specific application event that you want to monitor.

These numbers are defined by the application.

1) Select the Filter by event identifier and click Add. Then Event Identifier window is displayed.

2) Type 444 and click OK to return to the Windows Event Log window.


At this point, the agent is configured to capture .NET errors, and errors that have the specific

identifier 444. (The number 444 is an arbitrary choice that does not necessarily have meaning

in an application's error logging scheme.)

The fully-configured Windows Event Log window is shown in Figure Figure 8 on page 42.

h. Click OK to save your settings and return to the Windows Event Log Definition panel.

i. Click Finish to complete creation of the agent. A new itm_toolkit_agent.xml file is displayed in the

Navigator of Agent Builder workspace.

Remote deployment is also an option

The remainder of this exercise describes how to locally install the agent that you have created.

The IBM Tivoli Monitoring Agent Builder: User’s Guide describes additional installation options

and features.

4. Generate the new agent within the Agent Builder tool:

a. In the Navigator of the Agent Builder window, right-click the itm_toolkit_agent.xml file.

b. In the bottom of the pop-up menu, select IBM Tivoli > Generate Agent. A Generate Agent Wizard

is displayed, prompting you to set Generation Type.

Figure 9. Launching the Generate Agent wizard

c. Make sure that the Generate the agent files in an IBM Tivoli Monitoring installation on this

machine option is selected. Notice the following details regarding this window:

v The C:\IBM\ITM path is specified by default in the IBM Tivoli Monitoring installation directory

field. The setting is valid if you followed the procedure in “Installing IBM Tivoli Monitoring on one

Windows computer” on page 3. Otherwise, you must specify the correct, alternate installation

path for the product.

v This panel of the wizard includes the Generate an ITM 5x mapping file option. Do not use this

option in the current exercise. However, be aware that the option exists, and that it is relevant to

the process described in “Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0,

complex scenario (based on the Agent Builder)” on page 97.

d. Click Finish. A progress bar is displayed and the process is completed after several minutes.


e. Click OK in the message box that confirms successful installation.

5. Configure the new monitoring agent in IBM Tivoli Monitoring:

a. Start Manage Tivoli Monitoring Services. (Step 17 on page 7 in “Installing IBM Tivoli Monitoring on

one Windows computer” on page 3 describes how to do so.) The new entry Monitoring Agent for

Event_Log_demo is included in the window that is displayed.

Note: If the Manage Tivoli Monitoring Services window is already open, select View > Refresh to

see the new entry.

b. Right-click on the entry and select Configure Using Defaults. Click OK to accept the defaults if

you are prompted.

c. If you added runtime configuration elements to your agent, you see configuration panels where you

must enter required information for your agent.

d. Right-click on the entry and select Start.

e. Open the Tivoli Enterprise Portal.

f. View the workspace of the new agent in the following path in the Navigator: Windows Systems >

Localhost > Event_Log > Event Log, where Localhost is the name of the machine that hosts the

Tivoli Enterprise Portal.

The agent that you built in this exercise is not intended for further configuration and use. When you

build an agent for use in your enterprise, you use standard procedures to configure situations and

set up workspaces, according to the needs of your enterprise. Those standard procedures are

introduced in the following chapters of this document:

v Chapter 2, “Basic monitoring exercises,” on page 13

v Chapter 3, “Advanced monitoring exercises,” on page 29

The concepts and procedures that the exercise presents prepare you to build custom monitoring agents.

Such agents can capture specific metrics to achieve specialized monitoring goals that the default

monitoring agents of IBM Tivoli Monitoring do not provide.

In addition, you can build custom monitoring agents that reproduce functionality from custom resource

models from IBM Tivoli Monitoring, version 5.x. See the guidelines and comment in “Migration from IBM

Tivoli Monitoring version 5.1.2 to version 6.2.0, complex scenario (based on the Agent Builder)” on page

97.


Chapter 4. Historical reporting exercises

IBM Tivoli Monitoring enables you to generate historical reports. Table 4 lists the basic components that

enable historical reporting.

Table 4. Components that enable historical reporting

Component Role of the component

A database Store raw historical data.

Note: You can use standard database queries to extract historical reports from the

database. This approach provides an alternative to displaying the data in the Tivoli

Enterprise Portal.

The Summarization and

Pruning agent

Aggregate historical data for display in the Tivoli Enterprise Portal.

The Tivoli Enterprise

Portal

Display historical data in the tables, bar charts, and pie charts that are typical for IBM

Tivoli Monitoring. The displays are updated automatically at intervals that you specify.

The process of historical reporting

The series of exercises in Exploring IBM Tivoli Monitoring cover the general process of historical reporting.

Table 5 lists the milestones in this process.

Note: The exercises in this document are able to demonstrate the fundamental components for historical

reporting quickly for the following reasons:

v You perform the exercises on a single Windows computer, instead of creating an environment

that has multiple computers and operating systems.

v You use the version of IBM DB2 that is supplied with the product, instead of installing and

configuring an alternate database product.

See the IBM Tivoli Monitoring Installation and Setup Guide for descriptions of the extra

configuration procedures for monitoring environments that include multiple computers on varied

operating systems.

The following list describes the set of exercises provided in this document regarding historical reporting:

Table 5. Milestones in the process of historical reporting

Milestone Exercise that demonstrates the milestone

1. Install the components that enable historical reporting.

v Specific types of monitoring agents

v A database to store historical data

You achieve these milestones as part of the installation of

the following two monitoring agents:

Warehouse Proxy Agent

Enables communication between IBM Tivoli

Monitoring and the database (data warehouse).

Summarization and Pruning Agent

Creates summarizations of detailed data into

groupings, such as hourly, daily, weekly, monthly,

quarterly, or yearly.

“Installing IBM Tivoli Monitoring on one Windows

computer” on page 3

This exercise results in the installation of all available

types of agents, including the agents that enable

historical reporting.

The “Setting up a data warehouse for historical reports”

on page 6 section of that exercise describes how to

create the database and to completely set up the

Warehouse Proxy agent.

In contrast, you must complete the activities in Milestone

3 listed in this table to complete the setup of the

Summarization and Pruning Agent.


Table 5. Milestones in the process of historical reporting (continued)

Milestone Exercise that demonstrates the milestone

2. Configure the basic data collection behavior of the

Summarization and Pruning Agent.

Note: This exercise shows options for managing data

collection to prevent the overloading of system storage

and processing capacity.

“Configuring basic data collection for historical reports”

3. Customize the data collection behavior of the

Summarization and Pruning monitoring agent.

Note: This exercise demonstrates additional methods for

managing data collection.

“Customizing data collection for historical reports” on

page 47

4. View and analyze historical reports in the Tivoli

Enterprise Portal.

“Viewing historical reports” on page 49

5. Disable historical reporting. “Stopping historical reporting” on page 51

This section also includes exercises regarding the following advanced topic for historical reporting:

“Creating custom queries for historical reports” on page 52.

The following documents provide additional information on historical reporting:

v IBM Tivoli Monitoring User’s Guide describes configuration procedures in greater detail that the current

document.

v IBM Tivoli Monitoring Administrator’s Guide describes general issues regarding planning and

implementing the collection of historical data.

Configuring basic data collection for historical reports

The Summarization and Pruning Agent uses information that is stored in the data warehouse to generate,

store, and prune data. The data in the data warehouse is a historical record of activity and conditions in

your enterprise.

v Summarizing the data is the process of aggregating your historical data into time-based categories such

as hourly, daily, weekly, and so on. You can summarize your data to perform historical analysis of the

data over time.

v Pruning data means that old data is deleted automatically, rather than manually. You can set pruning

criteria to remove old data from the data warehouse to limit the size of your database tables.

During installation of the Summarization and Pruning Agent, default values in the KSYENV file populate

configuration settings. If you want to change the data summarization or pruning configuration settings for

certain products and attribute groups, use the History Collection Configuration window in the Tivoli

Enterprise Portal.

1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services to open the

Manage Tivoli Monitoring Services window.

2. Right-click Warehouse Summarization and Pruning Agent and click Reconfigure to open the

Configure Summarization and Pruning Agent window.

Note: If the Configured column next to Warehouse Summarization and Pruning Agent says No,

double-click (instead of right-clicking) Warehouse Summarization and Pruning Agent.

3. Click OK in the confirmation dialog box.

4. Click OK in the Warehouse Summarization and Pruning Agent: Agent Advanced Configuration

windows.

Note: This option is not presented when you are configuring for the first time.

5. Click Yes on the window that prompts you to indicate if you want to configure the agent.


6. Apply settings in the Sources tab of the Configure Summarization and Pruning Agent window as

follows:

a. Click Add to invoke the file browser window to add your JDBC driver in the JDBC drivers field.

This field might be completed by default.

Click Add to invoke the file browser window to select your JDBC driver.

Note: If your data warehouse database is on UNIX, find the directory where your database is

installed, and in the JDBC drivers directory, select the db2jcc.jar (and the

db2jcc_license_cu.jar file if it exists in the directory). For example: db2installdir/java/db2jcc.jar.

Click OK to close the browser and add the JDBC drivers to the list.

b. In the list, select DB2 as the type of database that your warehouse is using.

c. Enter the URL and Driver information for the warehouse. This information might be completed by

default.

d. Enter ITMUser as the User ID and the password that you established in the exercise “Installing IBM

Tivoli Monitoring on one Windows computer” on page 3.

e. Click Test database connection to ensure that you can communicate with your warehouse

database.

f. Keep the default settings for the Tivoli Enterprise Portal Server Host and Port.

The remaining default settings for summarization and pruning are valid for this exercise. You can

review those settings at this time to become familiar with the options. See the Scheduling tab, the

Work Days tab, and the Additional Parameters tab.

7. Click Save to preserve your settings.

8. Click Close to close the window.

9. Right-click the Summarization and Pruning Agent row of the Manage Tivoli Monitoring Services

window and choose Start in the pop-up menu.

After you complete all exercises regarding use of historical reporting, refer to “Stopping historical reporting”

on page 51.

Customizing data collection for historical reports

To configure historical data collection, specify the attribute groups from which to save data samplings, the

collection interval, the rollup interval, if any, and where to store the collected data. Use the following

procedure to configure your historical data collection:

Note: Your user ID must have Configure History permission to see and use this feature. The default user,

sysadmin, has this permission by default. If you create additional users, you must grant them this

permission.

1. If you are not running the Tivoli Enterprise Portal, start the desktop client now.

“Verifying your installation” on page 13 describes how to launch the portal.

2. Click Edit > History Configuration. The History Collection Configuration window is displayed.

3. Selection, Part 1 of 2: Select a component for which to configure historical data collection as follows:

a. If not selected already, select Windows OS in the Select a product pull-down list at the top of the

window.

b. In the Select Attribute Groups table, press Shift and click several rows in the table.

4. Configuration, Part 1 of 2: Configure historical data collection for the selected Windows OS attributes

as follows:

Chapter 4. Historical reporting exercises 47

a. In the Configuration Controls section, the following settings are valid for this exercise:

Name of field Value to assign

Collection Interval: 1 hour (The default setting is 15 minutes.)

Collection Location: TEMA (This is the default setting.)

By collecting data at the Tivoli Enterprise Monitoring Agent (TEMA) level you minimize

performance impact on the monitoring server from historical data management tasks.

Warehouse Interval: 1 hour

Summarization: Daily

Pruning: Weekly

b. Click Configure Groups to apply your settings to the selected groups. The Select Attribute

Groups table refreshes to reflect your settings.

Note: The time periods for some attribute groups cannot be modified. In these cases, the Select

Attribute Groups table displays a (fixed) label beside the value that cannot be modified.

c. Press Shift and click to again select all of the groups that you configured.

d. Click Start collection. The Select Attribute Groups table refreshes to reflect the Collection

status.

e. Select the monitoring server on which you want to collect the log file information.

Note: This step is necessary only when multiple monitoring servers exist in the IBM Tivoli

Monitoring environment.

5. Selection, Part 2 of 2: Select another component for which to configure historical data collection as

follows:

a. Select Windows OS in the Select a product pull-down list at the top of the window. the Select

Attribute Groups table refreshes to reflect your choice.

Note: The attribute groups that you can change are displayed in a table. When you select a

product, you are configuring collection or pruning, or both, for all attribute groups for that

product.

b. If historical collection was previously started, click Stop Collection. Otherwise, you are not able to

modify all of the options.

This step is applicable only if you have previously started collection.

c. Click the Show Default Groups button at the bottom of the window to highlight the attribute groups

that users typically enable for historical reporting.

For example, NT Logical Disk is an attribute group that has predefined historical workspaces.

Scroll in the table to that group to see the highlighting.

6. Configuration, Part 2 of 2: Configure historical data collection for the selected attribute groups of the

Windows operating system as follows:

a. In the Configuration Controls section, the following settings are valid for this exercise:


Collection Interval: 1 hour (The default setting is 15 minutes.)

Collection Location: TEMA (This is the default setting.)

By collecting data at the Tivoli Enterprise Monitoring Agent (TEMA) level you minimize

performance impact on the monitoring server from historical data management tasks.

Warehouse Interval: 1 hour



Summarization: Weekly

Daily and Hourly are automatically checked when you select Weekly. These are valid

settings.

Pruning: Hourly keep 30 Days

This setting causes pruning to occur every hour, after data has been warehoused for 30

days.

Note: You must perform the following step. Otherwise, your changes are not saved.

b. Click the Configure Groups button to configure data collection for the selected groups. The Select

Attribute Groups table refreshes to reflect your settings.

c. Click the Collection Interval column heading to sort the table and group the items that you

configured to have the same collection interval.

d. Click and drag on the items that you have configured. Selected the Network Interface and NT

System groups and all groups in between.

e. Click the Start Collection button. The Select Attribute Groups table refreshes to reflect the

Collection status.

7. Click Close to exit the History Collection Configuration window.

Viewing historical reports

Historical reports reveal long-term trends. This exercise tells how to display and analyze historical reports.

Following this exercise, “Real-time data versus historical data” on page 50 provides an example that

explains what you see in the portal when you work with historical reports.

Prerequisites: Historical reports are available for viewing after you complete the following actions:

v Complete the following procedure: “Configuring basic data collection for historical reports” on page 46.

v Wait over 24 hours to ensure that historical data is captured for you to view. Data that is over 24 hours

old is considered historical. (Data for the most recent 24-hour period, called real-time data is always

available in IBM Tivoli Monitoring.)

Note: If you cannot wait for 24 hours, continue with this exercise. You learn how to access the view of

historical data in IBM Tivoli Monitoring. However, you see only real-time data. Later, when

historical data is available you will be able to use the same procedures to confirm that data is

being collected and displayed properly.

Exercise:

1. In the Tivoli Enterprise Portal, use the Navigator to access the following path: Windows Systems >

Localhost > Windows OS > Memory, where Localhost is the name of the machine that hosts the

Tivoli Enterprise Portal. The Memory workspace is displayed.

2. Click the title bar of the Paging Traffic view (see the lower right corner of the workspace) to activate it.

Figure 10 on page 51 shows a typical Paging Traffic view.

3. Click the Specify Time Span for Query (

) icon. The Select the Time Span window is displayed.

4. Select the Last radio button, and type 48 in the hours setting. You do not need to make other time

span settings.

5. Click OK. The Paging Traffic view is refreshed to display all available historical data. Figure 11 on page

51 shows typical historical data in a Paging Traffic view.

6. Review Table 7 on page 51 to understand the differences between the real-time view and the historical

view.


7. (Optional) Right-click on a bar in the historical Paging Traffic view and choose Export in the pop-up

menu. The data for the entire view is saved to the format you specify. For example, you can save the

data in the comma-separated-value format, which can be opened and further analyzed in a

spreadsheet application.

8. Stop historical reporting in this view as follows:

a. Click the Specify Time Span for Query (

) icon. The Select the Time Span window is

displayed.

b. Select the Real time radio button.

c. Click OK. The default real-time view is restored.

Real-time data versus historical data

This section compares real-time data and historical data. Table 6 describes the basic differences between

the types of data. Table 7 on page 51 describes the differences between two specific views of real-time

versus historical data.

Table 6. Comparison of real-time data and historical data

Type of data

Performance

issues Description

Real-time data None. IBM Tivoli Monitoring keeps monitoring data for 24 hours by default. This

set of data is called real-time data. You can view short-term (24-hour)

trends in the monitoring environment by default, without performing extra

configuration steps. This data is available without requiring additional

storage or processor resources. However, this data occupies storage at the

monitoring agent or monitoring server, so you must take that fact into

account when you configure collection.

Historical data Extensive. Historical data enables you to view trends during a period of days, weeks,

or even years. This long-term view provides a critical tool for

decision-making at many enterprises.

Figure 10 on page 51 shows a real-time data view for Paging Traffic. This view is provided in the Memory

workspace of the Windows OS monitoring agent. (In the Navigator, see Windows Systems > Localhost >

Windows OS > Memory, where Localhost is the name of the machine that hosts the Tivoli Enterprise

Portal.) Table 7 on page 51 summarizes the key differences between the real-time Paging Traffic view in

Figure 10 on page 51 and the historical view in Figure 11 on page 51.


Table 7. Comparison of a real-time view and a historical view

Real-time view Historical view

Figure 10. Real-time data

Figure 11. Historical data

Details regarding Figure 10

v Only two metrics, input and output of pages, are

displayed in a bar chart. The yellow bar displays pages

input per second. The blue bar displays pages output

per second.

v One set of yellow and blue bars is visible, providing a

current snapshot of paging traffic.

v No paging traffic is occurring in the current time period.

Details regarding Figure 11

v Same as bullet item one for Figure 10.

v Multiple sets of yellow and blue bars are visible,

corresponding to the patterns of paging traffic over a

two day period.

v Significant patterns and variations occur in a two-day

period.

Stopping historical reporting

You can stop historical reporting at two levels in IBM Tivoli Monitoring:

Stop historical reporting in a view of the Tivoli Enterprise Portal

Step 8 on page 50 in “Viewing historical reports” on page 49 describes this procedure. This action

alters the view in the portal, but does not stop collection of historical data.

Stop the activities of the Summarization and Pruning Agent

Stopping the activities of the Summarization and Pruning Agent stops collection of historical data.

You can stop specific activities of this agent.

The following example describes turning off summarization and pruning for the NT-System

attribute group in the Historical Collection Configuration window:

1. Select Windows OS in the Select Attribute Groups window.

2. Select NT_System.

3. Click Stop Collection.

4. Click Unconfigure Groups.

You can stop summarization and pruning for the entire IBM Tivoli Monitoring environment.

Completely stop summarization and pruning as follows:

1. Select Manage Tivoli Monitoring Services in the following path of the Windows Start

menu: Programs > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services.

The Manage Tivoli Monitoring Services window is displayed.

2. Right-click the Summarization and Pruning Agent row and select Stop in the pop-up

menu.


Creating custom queries for historical reports

This section describes how to create custom queries to feed data to historical reports in IBM Tivoli

Monitoring. This is an advanced topic that supplements the preceding exercises regarding the basic

process of using historical reporting.

Creating a monitoring server query

With the Query editor you can create your own queries to the monitoring server and add a prefilter

composed in the same way as a postfilter for a table or chart view. Additionally, you can add a column

function to average, count, total, or find the minimum or maximum value of a column and group the results

accordingly.

Use the following procedure to create a monitoring server query.

1. Click

Queries located in the toolbar.

2. On the left side of the window, click the plus sign (+) to expand Windows OS and scroll down to NT

Process and expand it to see the queries.

3. Select Top Process CPU time and click

to create another query.

4. In the Name field, type VirtualKbytes Peak and click OK.

A duplicate of the original query is displayed with the name you entered.

A name can have a maximum of 32 letters, numbers, underscores (_) and spaces.

5. In the Description field, type a new description, Total CPU time.

You have up to 256 characters and spaces in this field.

6. (Optional) Edit the specification for any changes you want to make:

v Click Add Attributes and select the Virtual Kbytes Peak attribute. Click OK.

Now the query contains a combination of the new attribute that you selected and the attributes from

the group used in the original query.

v Add filter criteria to the new attribute as follows:

a. Shift the horizontal scroll bar to the right to see the new Virtual Kbytes Peak column.

b. Click in the first row of the Virtual Kbytes Peak column.

c. Write an expression.

d. Click the equal sign (=) to access the pop-up menu.

e. Choose an operator for the expression

Note: EQ $NODE$ and any other names enclosed in dollar signs are required filters in a query;

you must not delete them.

7. Click Apply to save the query and keep the editor open.

8. Click OK to save the query and close the window.

Note: The attributes in a query can be from one group only; you cannot mix attributes from different

groups in the same query.

Creating a query for an ODBC database

The Query editor has a text editor for composing free-form SQL queries to any ODBC-compliant data

source located on the machine where your Tivoli Enterprise Portal Server is installed. You can integrate

systems management data from monitoring agents with data from other sources in one workspace.

However, to achieve this goal, you must configure those ODBC data sources in Tivoli Enterprise Portal

Server.

Use the following steps to create a query of ODBC database attributes:


1. Click the Queries icon (

) located in the toolbar.

2. Click Create a query icon icon (

), located in the upper left hand corner of the Query Editor

window, to create a query.

3. In the Name field, type a name of up to 32 letters, numbers, underscores (_) and spaces.

4. In the Description field, type a new description, up to 256 characters and spaces, in the Query Editor

window.

5. From the Category list, select the folder where you want the new query to be displayed in the

Queries tree. In this case, select AF/REMOTE® Agent.

6. Select the TEMS as the type in the Data Sources list.

7. Select Custom SQL.

8. Click OK.

The new query is displayed in the Queries tree under AF/REMOTE Agent. The Specification tab

opens with a Custom SQL text box for you to enter a SELECT statement. You must be familiar with

SQL commands and their syntax to write an SQL query.

9. Write the SQL statement in the text box using the proper syntax.

See the Tivoli Enterprise Portal help for examples.

10. When you are finished writing the SQL text, click Apply to save the query and keep the window

open, or click OK to save the query and close the window.


Chapter 5. Administrator exercises

This section provides the following exercises that system administrators typically perform:

v “Viewing managed system status and heartbeat”

v “Setting up Hot Standby” on page 56

v “Integrating with IBM Tivoli Enterprise Console: new approach” on page 57

v “Integrating with IBM Tivoli Enterprise Console: standard approach” on page 59

– “Enabling communications with IBM Tivoli Enterprise Console” on page 59. Note: If you want to view

IBM Tivoli Enterprise Console events only, this procedure is not required.

– “Displaying situation events in IBM Tivoli Enterprise Console” on page 60. Note: If you want to view

IBM Tivoli Enterprise Console events only, this procedure is not required.

– “Displaying console events in the portal” on page 61

– “Filtering and responding to events” on page 62

Terminology clarification: The term “IBM Tivoli Enterprise Console” refers to both a user interface (the

console) and a product. Table 8 shows how that convention is not true for the Tivoli Enterprise Portal.

Table 8. Terminology for the console versus the portal

Name of user interface Name of product Name of data Repository for data

IBM Tivoli Enterprise

Console (console)

IBM Tivoli Enterprise

Console

event event server

Tivoli Enterprise Portal

(portal)

IBM Tivoli Monitoring situation event monitoring server (also

called Tivoli Enterprise

Monitoring Server)

Viewing managed system status and heartbeat

The hub Tivoli Enterprise Monitoring Server listens for heartbeats to track the online or offline status of

monitoring agents. A monitoring agent sends a heartbeat every 10 minutes. If the monitoring server does

not detect a heartbeat the agent is classified as OFFLINE. Within a short time interval after a missed

heartbeat, the monitoring server considers the state (called the managed system status) of the monitoring

agent to be offline.

View the managed system status and heartbeat detection (OFFLINE or ONLINE) as follows:

1. Start the Tivoli Enterprise Portal.

2. Right-click the Enterprise node in the Navigator view.

3. Click Workspace > Managed System Status.

The Managed System Status table, similar to the following example, is displayed in the workspace

area. The online or offline status of the managed systems is displayed in the Status column on the

left.


Setting up Hot Standby

The optional Hot Standby function enables you to maintain continuous availability by defining a standby

monitoring server to provide backup for your hub monitoring server. If the hub monitoring server fails, hub

functions automatically switch to the standby monitoring server. IBM Tivoli Monitoring automatically

connects all remote monitoring servers and agents to the standby monitoring server.

No automatic switch returns control to the hub monitoring server when it is available. If you want to switch

back to the hub monitoring server, you must manually start the hub monitoring server and stop the standby

monitoring server.

Configuring Hot Standby involves the following process:

1. Create a backup monitoring server to take over if the primary server fails.

2. Configure the primary and backup server as mirrors of each other.

3. Configure monitoring agents to recognize the backup server.

4. Verify success of the configuration.

The following steps provide detailed instructions for setting up Hot Standby:

1. Create a backup monitoring server to take over if the primary server fails.

See “Installing IBM Tivoli Monitoring on one Windows computer” on page 3 for information about

installing a monitoring server. Install the backup monitoring server on a separate computer, as a hub

monitoring server. Specify configuration parameters that are identical to the parameters on the primary

monitoring server.

2. Configure the primary and backup server as mirrors of each other.

Note: In a more complex environment, you would also configure any remote servers associated with

the hub server to make them aware of the backup topology.

a. Access the Manage Tivoli Monitoring Services window.

b. Right-click the name of the hub monitoring server and click Reconfigure.

c. Apply the following settings:

1) Select Configure Standby TEMS.

2) Enter the name of this monitoring server and specify the protocols used by the standby server.

These protocols should be the same for both monitoring servers (the hub and the standby).

3) Click OK.

4) Type the host name or IP address for the hub monitoring server and click OK on the window

that displays the communication settings for this server.

5) Type the host name or IP address for the standby monitoring server in the Hostname or IP

Address field and click OK.

d. Stop and restart the monitoring server. The monitoring server stops automatically.

e. Repeat these steps for the standby monitoring server.

3. Configure monitoring agents to recognize the backup server.

Note: Agents use a feature called Secondary TEMS to ensure their availability. If the monitoring

server to which the agent connects is unavailable, they switch to the defined secondary

monitoring server.

a. Access the Manage Tivoli Monitoring Services window.

b. Right-click an agent and click Reconfigure (on Windows) or Configure (on UNIX).

c. Select Optional: Secondary TEMS Connection and specify the protocol for the backup monitoring

server.

d. Click OK.


e. Ensure that the correct host name (or IP address) for the hub monitoring server and the port

number are specified.

f. Click OK.

g. Type the host name or IP address for the secondary monitoring server and click OK.

h. Restart your agent.

4. Verify success of the configuration as follows.

a. In the Manage Tivoli Monitoring Services window, stop the monitoring server. After a moment, the

hub monitoring server stops.

b. Reconfigure the Tivoli Enterprise Portal Server to point to the standby monitoring server.

c. Restart the portal server.

d. Open the Tivoli Enterprise Portal. If everything is configured correctly, you are still able to open the

portal and view data.

Integrating with IBM Tivoli Enterprise Console: new approach

IBM Tivoli Monitoring, version 6.2.0, offers a new approach to integrating not only with IBM Tivoli

Enterprise Console, but also with Tivoli Netcool/OMNIbus.

Note: The IBM Tivoli Monitoring: Administrator’s Guide provides comprehensive information about this

feature.

The common event console is a Tivoli Enterprise Portal view that provides a single, integrated display of

events from multiple event systems. In one table, the common event console presents events from the

event systems, and users can sort, filter, and perform actions on these events. The following event

systems are supported:

v IBM Tivoli Monitoring

v IBM Tivoli Enterprise Console

v IBM Tivoli Netcool/OMNIbus

A common event connector (frequently called a connector) is software that enables the integrated display

of events from multiple event systems in the common event console. A connector retrieves event data from

an event system and sends user-initiated actions to be run in that event system. For example, if you

perform an action on a Tivoli Enterprise Console or Netcool/OMNIbus event in the common event console,

the associated common event console connector sends that action to the originating event system (Tivoli

Enterprise Console or Netcool/OMNIbus) for execution. To have the events from a specific event system

displayed in the common event console, you must configure a connector for that event system.

The connector for the IBM Tivoli Monitoring product is preconfigured when you install the product. For this

reason, the common event console includes the IBM Tivoli Monitoring events by default.

In this exercise, you configure a connector for IBM Tivoli Enterprise Console. You perform the same basic

procedure when you want to configure a connector for IBM Tivoli Netcool/OMNIbus events.

Note: Like other exercises in this chapter, this exercise requires that you have an installation of IBM Tivoli

Enterprise Console. Installation and configuration of that product is not described here.

Configure the connector for IBM Tivoli Enterprise Console as follows:

1. Open the Manage Tivoli Enterprise Monitoring Services window.

2. In the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli Enterprise Portal

Server.

3. In the pop-up window, click Reconfigure.

4. In the first TEP Server Configuration window, click OK.

Chapter 5. Administrator exercises 57

5. In the second TEP Server Configuration window, click OK.

6. Click No in answer to the question “Do you want to reconfigure the warehouse connection information

for the Tivoli Enterprise Portal Server?” The Common Event Console Configuration window is

displayed.

7. Click the TEC Connector tab to view or change the information for an IBM Tivoli Enterprise Console

connector.

8. Click New. The TEC Connector page is displayed.

9. Apply the following settings, which are essential for this exercise. The default values for other fields in

TEC Connector page are valid for this exercise.

Name of field Sample value to type

Connector name Events from TEC

This string becomes the name of the common event in the status window.

Computer name of event system Name

Name of computer that hosts the IBM Tivoli Enterprise Console.

Port number of event system port_number

The object dispatcher (oserv) port number (usually 94), which this connector

uses to retrieve events from the Tivoli Enterprise Console event system.

User name for accessing event

system

Name

The user name that you use to access IBM Tivoli Enterprise Console.

Password Password

The password that is associated with the user name.

Note: By default, all IBM Tivoli Enterprise Console events are available in the common event

console. The IBM Tivoli Monitoring: Administrator’s Guide describes the options for

customizing the display the event data in the common event console.

10. Click OK to save the configuration. The Tivoli Enterprise Portal is stopped, so that the changes can

be applied during the next startup of the portal.

11. Review the details of the new connector as follows:

a. Right-click Tivoli Enterprise Portal Server and select Start in the pop-up menu.

b. Right-click Tivoli Enterprise Portal | Desktop and select Start in the pop-up menu.

c. Provide a user name (for example, sysadmin) and password when the prompt is displayed. The

portal is displayed in the Enterprise Status workspace.

d. Select the Common Event Console icon (

) in the portal toolbar. The mouse pointer

changes to the icon image.

e. Click in one of the views of the Enterprise Status workspace. The Common Event Console view

replaces the view that you clicked on.

Note: You do not have to save your changes. If you want to save your changes, you must use

the Save As option and provide a new name for the workspace.

f. Click on the Connector Status icon (

). The Common Event Connector Status window is

displayed. This window identifies any connectors that are not operational.


Integrating with IBM Tivoli Enterprise Console: standard approach

If you configure the IBM Tivoli Monitoring environment to communicate with the IBM Tivoli Enterprise

Console, you can achieve the following visualization goals:

v View TEC events in the common event console of the Tivoli Enterprise Portal.

v View situation events (generated by IBM Tivoli Monitoring) in IBM Tivoli Enterprise Console.

v View events (generated by IBM Tivoli Enterprise Console) in the Tivoli Enterprise Portal of IBM Tivoli

Monitoring

Enabling communications with IBM Tivoli Enterprise Console

Note: If you want to view IBM Tivoli Enterprise Console events only, this procedure is not required.

To view updates to events from IBM Tivoli Enterprise Console in the Tivoli Enterprise Portal of IBM Tivoli

Monitoring, you must install the event synchronization component on the event server. This feature sends

IBM Tivoli Monitoring events to Tivoli Enterprise Console® and synchronizes the display of situation events

in the Tivoli Enterprise Portal with updates made on the event server.

Prerequisites

Note: These instructions assume that you use IBM Tivoli Enterprise Console and are familiar with basic

concepts and components, such as the baroc file (a set of event definitions) and the rule bases

that contain baroc files.

You need the following information to install and configure event synchronization between IBM Tivoli

Monitoring and IBM Tivoli Enterprise Console successfully:

v Host names (or IP addresses), user IDs, and passwords for the monitoring servers from which you want

to receive events

v SOAP information to send events to a monitoring server (the URL, the rate to send requests to the

server)

v Event rule base information (either the name of a new rule base to create or the name of an existing

rule base to use)

Note: For Windows, the existing rule base must have been created with a relative (not absolute) path.

To verify that your existing rule base uses an absolute path, run the following command from a

bash environment on your event server:

wrb -lsrb -path

If the returns path includes something like hostname:\Rulebase_directory with no drive letter

(such as C:\), you must copy the setupwin32.exe file from the \TEC subdirectory of the IBM

Tivoli Monitoring installation image to the drive where the rule base exists and run the installation

from that file.

Note: If your IBM Tivoli Enterprise Console event server is running on Windows 2003 and you are

planning to install the event synchronization remotely (using a program such as Terminal Services

to connect to that Windows 2003 computer), you must run the change user /install command

before you run the installation to put the computer into the required “install” mode. After the

installation, run the change user /execute command to return the computer to its previous mode.

Exercise

In this procedure you run an installer that automates the configuration process:

Note: After you enable event synchronization, your event server for IBM Tivoli Enterprise Console is

recycled.


1. Navigate the \TEC subdirectory on the IBM Tivoli Monitoring installation media.

2. Double-click the setupwin32.exe file.

3. Click Next on the Welcome window.

4. Select I accept the terms in the license agreement and click Next.

5. Click Next to accept the default configuration values.

6. Click Next to accept the default values for the files where events will be written.

7. Type the following information for each monitoring server with which you want to synchronize events

and click Add:

Host name

The fully qualified host name for the computer where the monitoring server is running. This

name must match the information that will be in events that come from this monitoring server.

User ID

The user ID to access the computer where the monitoring server is running.

Password

The password to access the computer.

Confirmation

The password, again.

8. When you have provided information about all of the monitoring servers, click Next.

9. Specify the rule base that you want to use to synchronize events. You have two choices:

v Create a new rulebase

If you are creating a new rule base, type the name for the rule base that you want to create and

the path to indicate the location of the new rule base.

v Use existing rulebase

If you are using an existing rule base, type the name of the rule base.

If you want to import an existing rule base into a new rule base, type the name of the existing rule

base in the Existing rulebase to import field.

Note: This step is available only if you are creating a new rule base.

10. Click Next and then click Next on the preinstallation summary panel. The installation begins.

11. When the installation and configuration steps are complete, click Finish on the Summary Information

window.

Note: If any configuration errors occurred during installation and configuration, you are directed to a

log file that contains additional troubleshooting information.

Displaying situation events in IBM Tivoli Enterprise Console

Note: If you want to view IBM Tivoli Enterprise Console events only, this procedure is not required.

Enable the display of situation events in the event view of IBM Tivoli Enterprise Console as follows:

1. Open Manage Tivoli Monitoring Services.

2. Perform the following steps in Manage Tivoli Monitoring Services:

a. Right-click the monitoring server and click Reconfigure.

b. On the configuration options window, select TEC Event Integration Facility.

c. Click OK and again OK.

d. Complete the following fields on the TEC Server:

v TEC Server Location: Type the host name or IP address for the computer where the IBM Tivoli

Enterprise Console event server is installed.


v TEC Port Number: Type the port number for the event server. If the event server is using port

mapping, set this value to 0. If the event server was configured to use a specific port number,

specify that number.

To determine the port number that the event server is using, search for the tec_recv_agent_port

parameter in the .tec_config file in the tec_installdir/TME/TEC directory on the event server. If

the parameter is commented out with a number sign (#), the event server is using port mapping.

If it is not, the event server is using the port number specified by this parameter.

e. Click OK.

3. Stop and restart the Tivoli Enterprise Monitoring Server. Right-click the monitoring server and click

Stop and then click Start. (Because your Windows monitoring server has been stopped automatically,

you can just start it.)

Displaying console events in the portal

Use the following steps to display events from IBM Tivoli Enterprise Console in the portal of IBM Tivoli

Monitoring:

1. Open the Enterprise Status workspace.

2. Click File > Save Workspace as and name the new workspace Enterprise TEC.

3. Click OK.

4. Click the Tivoli Event Console tool (

), then click inside the bar chart (Open Situation Counts — Last

24 hours). The Tivoli Enterprise Login window is displayed.

5. Configure the view for the Tivoli Enterprise Console host server:

a. Host is host_computer_name. If you are not using the default port number (54), add :port to the end,

where port is the port number used by your managed node).

b. Name is your Tivoli Management Framework login ID.

c. Password is your Tivoli Management Framework login password.

6. Click OK.

Your user ID is sent to the managed host for authentication. When the login is successful, you can add

other Tivoli Enterprise Console views to this workspace or others without having to log in to the

console during this portal work session.

7. In the Tivoli Enterprise Console Configure window, leave the Filter Type as Dynamic Filter to retrieve

events from the managed systems assigned to the current Navigator item and any items below it in the

same branch.

8. Select Host Name and click OK.

Overview of the Tivoli Enterprise Console view (located in IBM Tivoli

Monitoring)

This exercise helps you learn about the Tivoli Enterprise Console view. Situation events generated at the

Tivoli Enterprise Monitoring Server are forwarded to the Tivoli Event Console event server. When changes

are made to the events on the event server, those changes are forwarded to the monitoring server. You

are able to see events and any actions taken such as acknowledgements, from any location in your

network that these servers monitor.


Forwarding events

The severities for situation events forwarded from the Tivoli Enterprise Portal to the event server

are defined in one of the following places:

v The SITINFO field in the situation.

v The tecserver.txt file, if the situation and appropriate severity is defined in it. The file is located

in install_dir\cms\TECLIB\ on Windows and install_dir/tables/<ms_name/TECLIB on UNIX.

v The situation name suffix itself. For example, a situation named sit_name_WARN has a

WARNING severity in the event server.

If you want to modify the severities for events forwarded from Tivoli Enterprise Portal to the event

server, see the IBM Tivoli Monitoring Administrator’s Guide for information about editing the

tecserver.txt file.

Event view rows

Each event received by the Tivoli Event Console adds a row to the view showing summary

information. When you select an event (or multiple events with Ctrl+click or Shift+click), you can

right-click to get a pop-up menu of options. The buttons are also enabled.

If the view does not populate with events it means that no events were received for the managed

system associated with this Navigator item.

Filtering and responding to events

In this exercise, you go through the typical activities for the Tivoli Enterprise Console view, which is located

in the portal of IBM Tivoli Monitoring. The typical activities are as follows:

v Open the relevant workspace.

v Acknowledge an event.

v Apply filters an event.

v Close an event.

Perform the following exercise to learn about filtering and responding to events:

1. Open the relevant workspace as follows:

a. If it is not already displayed, open the Enterprise Status workspace by clicking the Enterprise item

at the top of the Navigator view.

b. Right-click the Enterprise item and click Workspace → Enterprise TEC.

c. In the Tivoli Enterprise Login window that opens, complete the following fields:

1) Host is host_computer_name:94 (default port number or change to the number used by your

managed node).

Figure 12. Tivoli Enterprise Console view


Note: Use the same event server that you specified when you configured the Tivoli Enterprise

Console view.

2) Name is your Tivoli Management Framework login ID.

3) Password is your Tivoli Management Framework login password.

The Enterprise TEC workspace is displayed.

2. Acknowledge an event as follows:

a. Click a row inside one of the Tivoli Enterprise Console views that has an event showing Open in the

Status column.

b. Click Acknowledge (or right-click the row and click Acknowledge).

The Status changes to Acknowledging while the action is being processed, then becomes

Acknowledged when the Tivoli Enterprise Console server has completed processing the action.

c. Click Maximize in the event console view toolbar so that you can better observe the activities in

this view.

3. Apply filters an event as follows:

a. Click each of the

filters: once to hide the events of that severity, and again to

show them.

Each color-coded filter shows a count of the events that have been received of that severity:

v Unknown

v Harmless

v Warning

v Minor

v Critical

v Fatal

b. Click each of the

filters: once to hide the events of that status─Open, Response,

Acknowledged, Closed─and again to show them.

c. Click each of the

filters: once to hide your events or other operators’, and again to show

them.

4. Close an event as follows:

a. If it is not selected, click the row of the event you just acknowledged.

b. Click Close (or right-click the row and click Close).

The Status changes to Closing while the action is being processed, then becomes Closed when

the Tivoli Enterprise Console server has completed processing the action.


Chapter 6. Agent exercise

This section provides an exercise regarding a member of agent category two: “Using IBM Tivoli Monitoring

for Databases: DB2 Agent.”

v Agent category one: monitoring agents that are part of the base IBM Tivoli Monitoring installation

package

v Agent category two: monitoring agents that are not part of the base package

The “Agent categories” on page 8 topic provides more details about the two basic categories of agents.

(Previous exercises in this document have been based on the Windows OS agent, which is a member of

agent category one, and monitors conditions in the Windows operating system.)

Using IBM Tivoli Monitoring for Databases: DB2 Agent

After you install IBM Tivoli Monitoring and the Tivoli Enterprise Portal, you install the following software that

is required for the IBM Tivoli Monitoring for Databases: DB2 Agent to operate:

v IBM Tivoli Monitoring for Databases: DB2 Agent

v Agent support on the monitoring server, portal server and portal client

The IBM Tivoli Monitoring for Databases: DB2 Agent software is located on the IBM Tivoli Monitoring for

Databases image. Install the agent using the steps in “(Optional) Installing a Tivoli Enterprise Monitoring

Agent on remote computers” on page 8. Instead of using the procedure to install the monitoring agent on a

remote computer, you perform the procedure on the computer where you installed the monitoring server

and portal server (see the procedure “Installing IBM Tivoli Monitoring on one Windows computer” on page

3).

Starting and stopping the IBM Tivoli Monitoring for Databases: DB2

Agent

This section provides additional relevant information for starting or stopping this monitoring agent for a

specific database instance.

Background information

The IBM Tivoli Monitoring for Databases: DB2 Agent does not require advanced configuration. However,

you must start this monitoring agent while you are logged on as the DB2 instance owner, and you must

have DB2SysAdmin, SysCtrl, and SysMaint authorities.

Note: If you perform this exercise using the user account that installed the product (see the procedure

“Installing IBM Tivoli Monitoring on one Windows computer” on page 3), you have all the required

privileges by default.

You can run multiple copies of this monitoring agent by specifying different database instance names. Only

one process can be started for each database instance.

Procedure

Start and stop this monitoring agent as follows:

1. If the Manage Tivoli Monitoring Services utility is not running at this time, select the item in the

following path of the Windows Start menu: All Programs > IBM Tivoli Monitoring > Manage Tivoli

Monitoring Services. The utility is launched.

2. Right-click the Monitoring Agent for DB2 row. Notice that this row has Template as its value in the

Task/SubSystem column.

3. Select Configure Using Defaults. The Enter DB2 instance name prompt is displayed.


4. Enter the name of a DB2 instance that you want to monitor. Enter the warehous instance name that

you created in an earlier exercise.

A new Monitoring Agent for DB2 row is displayed. Notice that the warehous instance name is

displayed in the Task/SubSystem column for this row.

5. Right-click the new row and select Start in the pop-up menu. the DB2 agent begins to run.

6. Launch the Tivoli Enterprise Portal to confirm that the DB2 agent is running:

a. In the Windows Start menu, select Programs > IBM Tivoli Monitoring > Tivoli Enterprise

Portal. The login message is displayed.

b. Type the name (sysadmin) and password of the account that you created during installation.

c. Click OK.

d. In the tree view of the Navigator, navigate to the following path: Windows Systems > Localhost >

DB2 - warehous..., where Localhost is the name of the computer where you performed the

exercise “Installing IBM Tivoli Monitoring on one Windows computer” on page 3.

Various nodes for the DB2 agent are displayed, such as Application, Database, Buffer Pool Activity,

and Table Space.

7. After you finish your inspection of the agent running in the portal you can stop the agent as follows:

a. Go to the Manage Tivoli Monitoring Services window.

b. Right-click the Monitoring Agent for DB2 row for the warehous instance.

c. Select Stop in the pop-up menu.

When stopping the DB2 agent using Manage Tivoli Monitoring Services, you are prompted to enter the

name of the database instance that you want to stop.

Command-line interface option: You can also start and stop DB2 agents using the command-line

interface for the product. The following example starts monitoring for the DB2inst1 database instance:

itmcmd agent -o DB2inst1 start ud

The database instance name must match the name used for starting the database. The host name of the

system is automatically added to the instance name in the managed system list of the user interfaces. For

more information about using the itmcmd agent command, see the IBM Tivoli Monitoring Installation and

Setup Guide.

Creating an ODBC data source

Some of the database attributes available with this monitoring agent require the use of an Open Database

Connectivity (ODBC) data source to maintain a connection with the database. You must create an ODBC

data source before you can use any of the following attributes:

v db cap err

v db cap lag

v db cap prun

v db tablespaces

v event monitors

v invalid pkgs

v invalid sys pkgs

v invalid triggers

v system tablespaces

v tables

v tablespaces

v tablespaces long data

v triggers


v user indexes

v views

The ODBC data source must be registered on the system where the monitoring agent runs, where the

DB2 resides. If you do not intend to use these attributes, you need not register an ODBC data source.

To register an ODBC data source for use with this monitoring agent, follow these steps (or refer to your

database documentation for current instructions):

1. In DB2, open the Add Data Source window.

2. Specify how the data source should be registered. Register the data source as a system data source

so that all users on the system have access to the database.

3. Specify the alias for the database in the Database alias field.

4. (Optional) In the Data source name field, you can specify a more meaningful name for the data

source. The name you enter is mapped to the Database alias.

Note: The data source name must be the same name as the database.

5. For Windows, select Register this database for ODBC if the database.

6. Select Register this database for CLI if the database will be accessed by DB2 CLI applications. In

UNIX, the data source is registered to CLI by default.

7. For Windows, specify one of the common applications in the Optimize for application field to optimize

the CLI settings for that type of application. Existing settings are overwritten where necessary. You

should optimize the settings for an application first, and then use the Settings page to modify specific

configuration keywords as required. If you have already set specific settings, back up your db2cli.ini file

before using the optimize feature. Modify any settings that you specifically want to be different from the

optimized values.

8. Click OK to register the data source and close the window.

Using situations to monitor system conditions

The following two examples show the type of information that you can view with situations:

v You can use the UDB_Status_Warning situation to determine if the DB2 instance is active. The formula

for this situation is the following:

db2_status NE active

v You can use the UDB_DB_SQL_Fail_High situation to determine if a monitored database experiences

more than 40% SQL statement failures. This formula for this situation is the following:

sql_stmts_failed_pct GT 40

Use the following steps to open a situation:

1. Right-click a system name in the Navigator and click Situations. The Situation editor opens with a list

of situations on the left. This is where you can view and edit situations or create new ones.

2. Click a situation name in the tree to see the Situation editor tabs.

3. You can use the Formula tab to view, add, and change the conditions being tested.

4. You can use the Distribution tab to view and specify the systems on which to run the situation.

5. You can use the Expert Advice tab to write comments or instructions to be read in the event

workspace.

6. You can use the Action tab to send a command to the managed system.

7. You can use Until tab to close the event after a period of time or when another situation is true.

8. Click Cancel to close the Situation editor.

Chapter 6. Agent exercise 67

Using workspaces to monitor system conditions

As two examples of the type of information you can view with workspaces:

v You can use the System Overview workspaces to view information about your database server.

v You can use the Locking Conflict workspace to view information about various locking activities and

resources.

The workspace is the working area of the application window. Select an item in the Navigator to open its

default workspace. If the item has multiple workspaces created for it, you can right-click the item, click

Workspaces and select another workspace to open.


Chapter 7. Migration exercises: IBM Tivoli Monitoring version

5.1.2 to version 6.2.0

The exercises in this chapter introduce the procedures and tools for migrating an IBM Tivoli Monitoring

version 5.1.2 environment to version 6.2.0.

v “Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0, basic scenario (based on the

Migration Toolkit)” on page 71

v The Resource Model Analyzer tool enables an migration scenario that is of intermediate complexity.

Specifically, you can use the tool to create a mapping file for complex resource models. The Migration

Toolkit uses the mapping file to migrate the complex resource model to IBM Tivoli Monitoring version

6.2.0. This tool is available in the IBM Tivoli Open Process Automation Library (OPAL) at the following

Web address: http://www.ibm.com/software/tivoli/opal. Keyword strings, such as "migration," "resource

model," and "analyzer" lead you to any available OPAL information about the tool. “Custom resource

model categories” on page 70 describes how to identify whether a given resource model should be

handled with the Resource Model Analyzer.

v “Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0, complex scenario (based on the

Agent Builder)” on page 97

See Table 2 on page viii for an overview of all exercises provided in this document.

The Web GUI, an alternative to the command-line interface:

The IBM Tivoli Monitoring Migration Toolkit: V5.1.2 to V6.2 comes with the Web GUI, a browser-based,

graphical user interface. As an alternative to the command-line interface, you can use the GUI to perform

the following operations:

v Run the Scantmr tool to create and subsequently re-validate the infrastructure baseline file

v Edit the infrastructure file online to insert new values of element attributes (including passwords) or

change the existing values (where permitted)

v Run the Assess and Migrate tools for small numbers of endpoints, profiles and profile managers (you

can only work on up to 10 objects in one action from the GUI).

See the IBM Tivoli Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 manual to learn

about using the GUI.

Valid scenarios for the Migration Toolkit

This section explains the valid scenarios for use of the Migration Toolkit.

The Migration Toolkit is a powerful tool for migration of IBM Tivoli Monitoring version 5.1.2 monitoring

environments to IBM Tivoli Monitoring version 6.2.0, including environments with large numbers of

gateways and endpoints. The following scenarios clarify the role and capabilities of the Migration Toolkit:

Scenario 1, Basic resource models

The toolkit can handle migration of resource models in which you have set indications and

thresholds for the unique conditions in your monitoring environment. See “Migration from IBM

Tivoli Monitoring version 5.1.2 to version 6.2.0, basic scenario (based on the Migration Toolkit)” on

page 71. This section includes the topic, "Assumptions in the basic migration exercise," which

clarifies how to build a test environment for migration.

Scenario 2, Customized resource models

The toolkit can handle customized resource models, which are resource models to which you have

added metrics or attributes. However, you must provide custom mapping files. You might be able

to use the Resource Model Analyzer to speed migration of customized resource models.


http://www.ibm.com/software/tivoli/opal

“Resource Model Analyzer tool” on page 69 describes how to obtain the tool. “Custom resource

model categories” describes the scenarios in which the tool is most effective.

You store your custom mapping files in the following path:

$BINDIR/../generic_unix/TME/ITMMTKupgrade/mapping/custom

The search process in the Assess phase works as follows:

1. The Migration Toolkit refers to the custom directory first, during the Assess phase. If you have

supplied a custom mapping file for the resource model, the Migration Toolkit uses this file.

2. Otherwise, the toolkit looks in the following path:

$BINDIR/../generic_unix/TME/ITMMTKupgrade/mapping/update

This path will contain future updates, if any, to the default resource model mapping files.

3. Finally, if the Migration Toolkit finds no resource model mapping files of the type it seeks, the

toolkit refers to the following path. The default mapping files for all product-provider resource

models are located here:

$BINDIR/../generic_unix/TME/ITMMTKupgrade/mapping/built-in

Scenario 3, Complex, customized resource models

When a customized resource model is complex (for example, when it includes scripts with

complex programming logic) advanced users can build a custom monitoring agent for the IBM

Tivoli Monitoring version 6.2.0 environment. See “Migration from IBM Tivoli Monitoring version

5.1.2 to version 6.2.0, complex scenario (based on the Agent Builder)” on page 97 for an

introduction to the Agent Builder, a tool that automates the creation of agents.

Note: Users who have built a complex custom resource model are familiar with the data providers

that supply data to the resource model. Knowledge of the data providers is critical to

success with the Agent Builder.

Custom resource model categories

A review of customer resource models reveals the following categories. The Resource Model Analyzer

helps map to version 6.2 of IBM Tivoli Monitoring in the ways described in Table 9:

Table 9. Potential for mapping specific types of resource model (RM)

Level

Similarity to default RMs

provided by the product

Visit Tree

characteristics Steps to complete migration

A Only thresholds or parameters are

changed.

Default metrics used.

Complexity same as in

default RM.

Can be collapsed into

Boolean expressions.

Modify the XML mapping files and run

Migration Tool.

Note: Metric parity is achieved at this level.

B1 Thresholds or parameters are

changed.

Metrics collected using IBM Tivoli

Monitoring version 5.1.2 pre-built

data-collectors.

Completely rewritten.




Migration Tool.

Note: Metric parity is achieved at this level.


Table 9. Potential for mapping specific types of resource model (RM) (continued)

Level

Similarity to default RMs

provided by the product

Visit Tree

characteristics Steps to complete migration

B2 Thresholds or parameters are

changed.

Metrics collected using specific

scripts directly invoked from the

VisitTree.

Note: Such custom scripts are not

available in IBM Tivoli Monitoring

version 6.x.

Completely rewritten.




Migration Tool to create situations only.

Use the Agent Builder Toolkit to implement

data providers and build an agent.

“Migration from IBM Tivoli Monitoring

version 5.1.2 to version 6.2.0, complex

scenario (based on the Agent Builder)” on

page 97 provides additional information.

C None. VisitTree and data-collectors

created by user.

Metrics not available in IBM Tivoli

Monitoring version 6.x.




Migration Tool to create situations only.

Use the Agent Builder Toolkit to implement

data providers and build an agent.

“Migration from IBM Tivoli Monitoring

version 5.1.2 to version 6.2.0, complex

scenario (based on the Agent Builder)” on

page 97 provides additional information.

The following general points derive from Table 9 on page 70:

v The Resource Model Analyzer provides analysis and output based on the complexity of the custom

resource models from any level.

v In all cases after the Resource Model Analyzer Tool is run, you must modify the resulting mapping file

before you process the file in the Migration Toolkit.

v In any cases where the Resource Model Analyzer Tool cannot provide metric parity, an XML mapping

file template is still created for the user to manually alter prior to using the Migration Toolkit.

Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0,

basic scenario (based on the Migration Toolkit)

This exercise introduces the procedures and tools for the Migration Toolkit.

Conventions in the exercise

This topic explains the conventions and terms used in the exercise.

Note: For the sake of conciseness, the following conventions are used in this chapter:

v ″V5.1.2″ refers to IBM Tivoli Monitoring version 5.1.2.

v ″V6.2.0″ refers to IBM Tivoli Monitoring version 6.2.0.

Resource models in IBM Tivoli Monitoring version 5.1.2 migrate to one of the following two main

categories of monitoring agents in IBM Tivoli Monitoring version 6.2.0:

Operating system (OS) monitoring agents

v OS monitoring agents monitor operating systems.

v These monitoring agents monitor operating system attributes, such as available disk space or

the amount of memory usage.

v OS monitoring agents are included with the IBM Tivoli Monitoring version 6.2.0 base product.

Application monitoring agents

v Application agents monitor entities other than operating systems.

Chapter 7. Migration exercises: IBM Tivoli Monitoring version 5.1.2 to version 6.2.0 71

v Application monitoring agents are included with the monitoring products that run on the IBM

Tivoli Monitoring version 6.2.0 base product. For example, the IBM Tivoli Monitoring for

Databases product in Version 6.2.0 product includes a DB2 monitoring agent.

v Application monitoring agents are available to monitor the following applications and

frameworks: Networks, Web systems, IBM DB2, mySAP, Oracle, Sybase, Lotus Domino,

Microsoft Virtual Server, VMWare, Citrix, Microsoft Exchange, and Microsoft .NET.

Note: Migration support currently exists for the following monitoring agents: the ADO agent, the

SAP agent, and and the Database agents.

v If you want the Migration Toolkit to deploy an application monitoring agent, the Migration Toolkit

depends on the presence of the OS monitoring agent on the target managed system.

Note: If the OS monitoring is not present, other features of the IBM Tivoli Monitoring version

5.1.2 monitoring environment are migrated, but certain endpoints do not migrate to

application monitoring agents. You must use another tool or method to deploy application

agents before you complete the migration process. You must complete this additional

process before you complete the migration. Otherwise, migration of the profile manager

does not happen.

Basic migration exercise

This topic lists the specific procedures provided in the basic migration exercise.

The following procedures are provided in “Exercise: Performing a basic migration” on page 73.

v “Migration stage 1: Installing the Migration Toolkit” on page 76

– “Installing the toolkit from the Tivoli command line” on page 78

– “Installing the toolkit from the Tivoli desktop” on page 79

– “Setting the Java path” on page 79

v “Migration stage 2: Creating Initial Baseline File” on page 82

– “Simplify baseline file for the migration exercise” on page 83

– “Using the topology view for XML mapping files” on page 85

v “Migration stage 3: Creating an IBM Tivoli Monitoring V6.2.0 Test Environment” on page 86

v “Migration stage 4: Updating the baseline file” on page 88

v “Migration stage 5: Validating the baseline file” on page 89

v “Migration stage 6: Assessing Endpoints” on page 93

v “Migration stage 7: Assessing Profiles” on page 93

v “Migration stage 8: Assessing Profile Managers” on page 94

v “Migration stage 9: Migrating endpoint assessment files” on page 95

v “Migration stage 10: Migrating Profile Assess Files” on page 95

v “Migration stage 11: Migrating Profile Manager Assess Files” on page 95

v “Post-migration activities” on page 96

Specifically, you migrate a Tivoli management region and its resources (sample endpoints, profiles, and

profile managers). These sample elements are mapped to components in an IBM Tivoli Monitoring V6.2.0

environment as shown in Table 10:

Table 10. Mapping of components from V5.1.2 to V6.2.0

Components in V5.1.2 Resulting component in V6.2.0

Tivoli management region Hub Tivoli Enterprise Monitoring Server

Gateways Remote Tivoli Enterprise Monitoring Server


Table 10. Mapping of components from V5.1.2 to V6.2.0 (continued)

Components in V5.1.2 Resulting component in V6.2.0

Endpoints and application objects

Note: Application objects include db instances, db2

databases, and miscellaneous objects associated with

specific applications, such as mySAP.

Tivoli Enterprise Monitoring Agent

Indications Situation events

Profile managers, which contain subscribers Managed system list

Note: The managed system list enables distribution of

situations that have been migrated from a profile in

V5.1.2. The profile contains the indications that are

mapped to situations.

Tivoli event server (encapsulating the monitoring goals for

your environment)

Tivoli event server (encapsulating the monitoring goals for

your environment)

Exercise: Performing a basic migration

This exercise describes the stages of a basic migration. The exercise teaches you the concepts and tools

for migration based on the Migration Toolkit.

Overview of the basic migration exercise

This section provides an overview regarding the basic migration exercise.

Assumptions in the basic migration exercise

The Migration Toolkit exercise is designed to be performed at the user’s workplace (not in a classroom). It

is assumed that you have specific conditions in your test environment and that you have experience with

specific Tivoli concepts and products.

The key exercise in this chapter describes how to use Migration Toolkit software to migrate the following

IBM Tivoli Monitoring version 5.1.2 components in a test environment:

v Tivoli management region server

v endpoints

v profiles

v profile managers

Assumptions regarding the test environment

The following table lists the assumptions in the exercise regarding the test environment.

Assumption Comment or counterpoint

You work in a test Tivoli environment. Do not use a production environment to test the Migration

Toolkit.

You use an existing Tivoli management region that you

maintain for test or staging purposes.

If this assumption is not correct, you can refer to the IBM

Tivoli Monitoring User’s Guide, Version 5.1.2

(SH19-4569) to learn how to deploy a Tivoli management

region for test purposes.

You deploy the managed resources to be migrated —

endpoints, profiles, and profile managers — as described

in these exercises. (The Beta software is capable of

performing more extensive migrations. However, for these

exercises, you should limit your migration activity to just a

few components.)

If you perform the migration exercises using components

that already exist in your test environment, you must

adapt the instructions in the procedures to match the

unique values for your environment.


Assumption Comment or counterpoint

The toolkit migrates version 5.1.2 components to a

version 6.2.0 environment. The target V6.2.0 environment

can exist on a separate computer. Alternatively, you can

install V6.2.0 components on existing Tivoli server or

Tivoli gateway hardware, as suggested in the following

example scenarios:

v The computer that you want to use to host both types

of Tivoli servers has sufficient CPU and storage

resources to handle the load.

v You plan to uninstall the Tivoli management region and

gateways after migrating to IBM Tivoli Monitoring

version 6.2.0.

For a complete discussion of the migration options and

procedures, including deployment across multiple

domains, see the separate document IBM Tivoli

Monitoring, version 6.2.0: Upgrading from IBM Tivoli

Monitoring V5.1.2.

Assumptions about the user

The person who performs these exercises must be familiar with XML technology and also with the

following Tivoli environments:

v IBM Tivoli Monitoring version 5.1.2

– The infrastructure in terms of the Tivoli management region server and the Tivoli gateways

– Profile manager hierarchies, profiles, profile copies, and subscribers

– Resource models (both built-in and custom, where appropriate), resource model configuration

– Endpoints and monitoring engines

v IBM Tivoli Monitoring version 6.2.0

– Tivoli Enterprise Monitoring servers (hub and remote)

– Tivoli Enterprise Portal servers

– Attribute groups, attributes and situations

– Agents

Note: At minimum, you must have read and understood IBM Tivoli Monitoring Problem Determination

Guide.

Prerequisite resources for the exercise

To conduct the exercises in this chapter, your test environment must contain several software components.

v A server that hosts an IBM Tivoli Monitoring V5.1.2 monitoring server. In this exercise, the assumption is

that your test environment already has a Tivoli management region.

v A separate server to host the IBM Tivoli Monitoring V6.2.0 environment.

v A Windows endpoint running the following IBM Tivoli Monitoring V5.1.2 resource models:

– Logical Disk

– Memory

– Physical Disk

– Processor

– Services

– TCP/IP

v A Windows computer to host the specified monitoring endpoints/agents. (One of these computers can

also be the Tivoli management region server.)

The Migration Toolkit depends on the remote deployment function provided by IBM Tivoli Monitoring

V6.2.0. This function enables endpoint migration. For this reason, you must accept the installation

option to install the agent deployment bundles in the depot of the Tivoli Enterprise Monitoring

serverTivoli Enterprise Monitoring Server.


Note: You have the option to modify the test environment. However, if you modify the environment, you

must adapt the instructions in this exercise.

Optional resources and ignored resources in the exercise

The migration exercise is designed to migrate a minimal amount of resources, for the sake of clarity.

This exercise can demonstrate the key concepts and procedures of the Migration Toolkit without having

gateways and without using endpoints that perhaps already exist in your test environment. Keep these

points in mind as you do the exercise:

v Use of pre-existing resources inside the Tivoli management region is optional: You can perform

the exercise using managed resources that you have already created. However, the type and location of

those managed resources might not match the characteristics of the managed resources that are

created during this exercise. In that case you must slightly adapt the instructions in the procedures to

match the unique values for your environment.

v Use of gateway servers is optional: You can perform the exercise using gateways. However, the

exercise instructs you to remove references to gateways that are detected during the analysis phase of

migration, because the exercise does not require them. At those points in the exercise, read the steps

carefully because they explain the XML tagging structure. If you understand the XML tagging structure,

you can easily modify the exercise to include migration of a gateway.

Note: Minimize the number of components that you migrate in this exercise. That way, the operations that

you perform are free from complexity that might distract from the key concepts and procedures. For

example, if you decide to add a gateway to your migration activity, add only one gateway.

Node identification in the migration process

Where possible, the Migration Toolkit names the resources in the XML mapping files that it generates

during the migration process. This topic describes the naming capabilities of the toolkit.

This topic also describes the following key points:

v Naming capabilities of the toolkit.

v A limitation and workaround that can affect all agents in IBM Tivoli Monitoring.

Names automatically assigned by the Migration Toolkit

In the XML mapping file for migration, an <OSAgent> element identifies each computer to which

you deploy OS monitoring agents. The Migration Toolkit automatically assigns values these IBM

Tivoli Monitoring version 6.2.0 agents, including an agent name. The assumption is that you want

to deploy OS monitoring agents to existing endpoints, so that you can monitor resources on those

computers. Therefore, the scantmr command automatically adds the existing endpoint host names

(and other endpoint information) to the <OSAgent> elements.

In contrast, the scantmr command does not add host names (or other information) for the hub

and remote monitoring servers. You enter this information manually, when you edit the baseline

file. You have the option to install the hub or remote monitoring servers on computers that

currently host the Tivoli server or a gateway. Alternatively, you can install the servers for the new

V6.2.0 on remote computers.

Note: You might want to install V6.2.0 components on existing Tivoli server or Tivoli gateway

hardware, as suggested in the following example scenarios:

v The computer that you want to use to host both types of Tivoli servers has sufficient

CPU and storage resources to handle the load.

v You plan to uninstall the Tivoli management region and gateways after migrating to IBM

Tivoli Monitoring version 6.2.0.

An IBM Tivoli Monitoring limitation and workaround regarding agent naming

After installation of multiple agents, an agent might not be displayed in the Tivoli Enterprise Portal

or in the output from the listSystems command. This problem arises when an agent has a node


name that consists of more than 32 characters. For example, the a monitoring agent for an

operating system (also known as an OS Agent) and another monitoring agent (for example, the

Tivoli Universal Agent or the UNIX-based systems Log Agent) might have same node name. The

original, complete form of the name is unique. However, truncation to 32 characters might remove

the unique part of the name. For example, the name might be truncated to be

vision90.tivlab.austin.ibm.com:K. As a result, only one of the agents displays in Tivoli

Enterprise Portal and in the output from the listsystems CLI command. Perform the following

steps to eliminate this problem:

1. Edit the following file:

install_dir/config/agent_name.ini

2. Add the following statement to the .ini file:

CTIRA_HOSTNAME=unique_name

where unique_name specifies a unique name that consists of less than 32 characters.

3. Save the .ini file.

4. Stop the agent.

5. Start the agent.

Migration stage 1: Installing the Migration Toolkit

This section describes how to install the Migration Toolkit in the V5.1.2 environment.

Creating resources to migrate

Appendix B, “Creating a test environment for IBM Tivoli Monitoring version 5.1.2,” on page 103 describes

how to create ITM512 resource to migrate. Use these instructions if you want to learn about the Migration

Toolkit and either of the following is true:

v You are unfamiliar with the ITM512 environment and need help creating resources to migrate.

The instructions generate resources with specific names that you can trace as you complete the

migration exercises. These names are displayed in the examples that are provided in the migration

exercises.

v You are familiar with the ITM512 environment and want to create new resources to migrate, instead of

migrating resources that already exist in your environment.

If you want to migrate existing resources, you do not need to use the resources created in Appendix B,

“Creating a test environment for IBM Tivoli Monitoring version 5.1.2,” on page 103. Instead, you would

need to adapt the example code in the migration exercises to account the differing names of managed

resources in your environment.

Note: The computers on which you run the Migration Toolkit must match the required operating systems

listed here. The toolkit generates the XML mapping file that enables migration of resources.

However, the computer on which you use the XML mapping file does not have to match the toolkit

requirements.

Where to install the toolkit

The toolkit must be installed on every Tivoli management region server and gateway to be migrated.

The toolkit must also be installed on every Tivoli management region server and gateway that hosts of

endpoints to migrated, even when you do not want to migrate a specific server or gateway.

Note: The toolkit commands are run from the version of the toolkit installed on the Tivoli management

region server only. However, the toolkit must be present on all of the managed nodes involved in

migration.


Software requirements

Several software applications are prerequisite. Installation of the Migration Toolkit is supported on multiple

operating systems.

Prerequisite software

The following prerequisite software must be present wherever the toolkit is installed:

v Tivoli Management Framework, version 3.7 or higher

v IBM Tivoli Monitoring, V5.1.2, with fix pack 10, or higher

v J2RE 1.4.2 IBM Windows 32 build cn142ifx-20060209 (SR4-1), or higher

Note: After the toolkit has been installed, you use the javapath command to enable the Migration Toolkit

to access the required Java software. See “Setting the Java path” on page 79 for details.

Supported operating systems

The toolkit can run on the operating systems listed in Table 11.

Note: The computers on which you run the Migration Toolkit must match the supported operating systems

listed here. The toolkit generates the XML mapping file that enables migration of resources.

However, the computer where you apply the specifications of the XML mapping file does not have

to match the required operating systems listed here. That computer must match the requirements

for installation of IBM Tivoli Monitoring V6.2.0. For example, IBM Tivoli Monitoring V6.2.0 does not

support the AIX V5.1 platform that is listed here in Table 11.

Table 11. Supported operating systems

Operating system Version

AIX 5.1 (32-64 bit)

5.2 (32-64 bit)

5.3 (32-64 bit)

Solaris Operating Environment V8 (32-64 bit)

V9 (32-64 bit)

V10 (32-64 bit)

HP-UX 11i (32-64 bit) with patch PHSS-30966

Windows 2000 Professional

2000 Server

2000 Advanced Server

XP

2003 Server Standard Edition (32 bit) with Service Pack 13

2003 Server Enterprise Edition (32 bit) with Service Pack 13

Red Hat Enterprise Linux 2.1 Intel 32-bit

4.0 Intel 32-bit

4.0 for zSeries 31-bit

SuSE Linux Enterprise Server 9 Intel

9 for zSeries 31-bit

Preparing the installation image

These steps describe an effective way to prepare for installation.


1. Locate the TAR file for the Migration Toolkit for IBM Tivoli Monitoring, and copy it to an empty directory

on the Tivoli management region server. You obtain this TAR file on the installation DVD or from the

IBM Passport Advantage Web site.

2. Access the bash shell in the Tivoli command-line interface.

v On UNIX or Linux, perform the following steps:

a. Run the appropriate setup script for the shell.

– For the Bourne, Korn, or bash shell, run the following command:

. /etc/Tivoli/setup_env.sh

– For the C shell, run the following command:

source /etc/Tivoli/setup_env.csh

b. Run one of the following commands in the command window to start the bash shell: sh OR bash

v On Windows, perform the following steps:

a. Open a command window.

b. Run the following command in the command window to set Tivoli environment variables:

%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

c. Run one of the following commands in the command window to start the bash shell: sh OR bash

3. Untar the distribution file using the following command: tar -xvf filename.tar

Note: Even on a Windows Tivoli management region, perform this task in the Tivoli bash environment

with the Tivoli environment sourced. A tar utility is available in this context. Otherwise, if you use

other tools to extract the distribution tar file you might see FILE.PKT errors during installation.

Tip: To access the Tivoli bash environment on a Windows Tivoli management region, you can create a

shortcut on a Windows desktop with the following target:

%SystemRoot%\system32\cmd.exe /k

%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd && bash

Installing the toolkit from the Tivoli command line

This topic describes how to install the toolkit using Tivoli commands.

1. Source the Tivoli environment. This step is described in “Preparing the installation image” on page 77.

2. Use the Tivoli winstall command to install the toolkit.

See the Tivoli Management Framework Reference Manual for complete information on command

parameters and settings. The key parameters for this command are provided in “About the commands

for the first stages of migration: winstall, javapath, password-related commands, trace, and scantmr” on

page 80. The following examples illustrate the use of this command for the Migration Toolkit:

v This command installs the migration toolkit on a Tivoli server on a Windows computer and to

managed nodes dan, don, and dave. The TAR file containing the toolkit was extracted to the

C:\toolkit directory:

winstall -c "C:\toolkit\" -i MTK.IND -y dan don dave

v This command installs the product on managed node a150wtmr without specifying the javapath:

winstall -c C:/20070120/IBM-Tivoli-Monitoring-Migration-Toolkit -i MTK.IND

-y a150wtmr

v This command installs the product on managed node a150wtmr and uses the @MtkJavaDir@

option to specify the javapath option:


-y @MtkJavaDir@="/Tivoli/bin/w32-ix86/TME/TEC/jre/bin" a150wtmr

v This command installs the product on managed node a150wtmr, specifies the javapath option, and

uses the @ScanValue@ option to initiate the witmmtk scantmr command:


-y @MtkJavaDir@="/Tivoli/bin/w32-ix86/TME/TEC/jre/bin" @ScanValue@=1 a150wtmr

Note: See IBM Tivoli Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 for

descriptions of all options and parameter for this command.


3. Run the wchkdb -u command to validate that the Tivoli database has been successfully updated during

the installation of the Migration Toolkit:

See “Setting the Java path” for an additional command that you must run.

Installing the toolkit from the Tivoli desktop

This topic describes how to install the toolkit using the Tivoli desktop.

The Tivoli desktop is an optional graphical user interface. The installer for the desktop is included in the

installation image for the Tivoli Management Framework.

1. Launch the Tivoli desktop through the Tivoli item in the Windows Start>Programs menu.

2. Respond to the logon prompts.

3. Use the tivoli command to launch the Tivoli desktop.

4. Select Install from the Desktop menu.

5. Select Install Product in the menu to display the Install Product window.

6. If necessary, click OK to ignore an error message about the media settings. Frequently, an installation

path is not set yet or is pointing to an older path for installation media. In this case, you see an error

message. You provide a path to the installation package as described here.

a. Click Select Media to display the File Browser window.

b. In the Path Name text field, type the full path to the MTK.IND file.

c. Click Set Path. The File Browser window displays the contents of the specified media in the Files

scrolling list.

d. Click Set Media & Close. The Install Product window is displayed again.

7. Select IBM Tivoli Monitoring Migration Toolkit 6.2 from the Select Product to Install scrolling list.

8. Click Install. The Set Install Options window opens.

9. Close the Set Install Options window, without making settings. Some settings are required, but you

can specify them later, as described in “Setting the Java path.”

10. In the Clients to Install On list of the Install Product window, all managed nodes that are gateways

to endpoints monitored by IBM Tivoli Monitoring version 5.1.2 are selected by default.

Note: Do not select any endpoints in the list.

During a full migration in a production environment, you might want to include or exclude specific managed nodes

from the migration process. Use the arrow keys to add managed nodes from the Available Clients list to the Clients

to Install On list or remove them from it. For example, you might have decided that a gateway that supports a trivial

number of endpoints should not be migrated. You can exclude that gateway from migration. You can reallocate

endpoints to a different remote Tivoli Enterprise Monitoring Server in IBM Tivoli Monitoring version 6.2.0.

11. Click Install to display the Product Install window and a list of pending installation actions.

12. Click Continue Install to begin the installation process. The Product Install window displays the

progress of the installation. View the messages in the task output window to determine whether the

product installation was successful.

13. Click Close to close the Product Install window.

14. Select Refresh from the View menu bar. The desktop displays the icon for the migration toolkit.

See “Setting the Java path” for an additional command that you must run.

Setting the Java path

The Migration Toolkit must have access to the Java Runtime Environment. This topic describes one of

several ways to set the Java path for the toolkit.

The toolkit requires version 1.4.2 of the IBM Java Runtime Environment or higher.


Note: The IBM Tivoli Monitoring V6.2.0 product images include IBM Java Runtime Environment version

1.5. (By default, the Java binaries are installed in the following path: C:\Program

Files\IBM\Java50\jre\bin.) This version is acceptable for the Migration Toolkit. The witmmtk

javapath command is used to set the Java runtime path.

1. Run the witmmtk javapath command without specifying parameters. The command returns the path for

the currently defined Java Runtime Environment. Alternatively, you can use the java -version

command.

2. Run this command:

witmmtk javapath "jre_path"

where jre_path is the path for the Java binary files that you located in Step 1. The following example

shows a typical path specification on Windows:

witmmtk javapath "C:\Program Files\IBM\Java50\jre\bin"

About the commands for the first stages of migration: winstall,

javapath, password-related commands, trace, and scantmr

This topic describes commands that are relevant in the early stages of a migration.

winstall

This command installs software in the IBM Tivoli Monitoring V5.1.2 environment.

Authorization

Requires install_product or senior authority in the Tivoli management region.

Syntax highlights

winstall

[-c source_dir]

-i MTK.IND

[-n | managed_node ...]

Description

The winstall command installs a Tivoli product from the command line when invoked on the Tivoli

management region.

Options

-c source_dir

For source_dir, specify the complete path of the directory that contains the MTK.IND file.

The MTK.IND file is located in the root directory of the downloaded product image that you

created in “Preparing the installation image” on page 77. If you are running the command

from a Tivoli server on a Windows system, enclose the path name in double quotation

marks.

-i MTK

Specify the index file for the Migration Toolkit, MTK.IND.

[-n | managed_node ...] -n

Specify to install the toolkit on all managed nodes that do not currently have the toolkit

installed. This option is ignored when you specify managed_node, a specific managed

node. Specify the managed nodes on which to install the toolkit. Provide the names of all

servers and managed node gateways with endpoints that you want to migrate from V5.1.2,

with the names separated by a space. If you do not specify either -n or managed_node,

the toolkit is installed on all managed nodes in the Tivoli region, including the server.

-y Specify to install the toolkit on each selected managed node without requesting

confirmation.


Example

See “Installing the toolkit from the Tivoli command line” on page 78.

witmmtk javapath

This command defines the java path for the toolkit.

Authorization

The command must be run by a user in the same group as the user that installed the Tivoli

environment. In addition, the user must be a Tivoli Administrator with the following Tivoli roles:

super, senior, admin, and user.

Syntax highlights

witmmtk javapath [{<path> | -? }]

Description

This command displays or sets the path for the supported version of Java Runtime Environment.

Options

path The path of the supported version of Java Runtime Environment to be used. The tools

require any IBM Java Runtime Environment at version 1.4.2 or higher. If this option is

omitted, the command returns the current path.

-? Displays the help message for this command.

Example

witmmtk javapath "C:\Program Files\IBM\Java50\jre\bin"

Password-related commands

During a migration, the toolkit automatically invokes command related to password protection. However,

when you want to run these commands manually, consult the following topics in the IBM Tivoli Monitoring,

version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2:

setpwd

Stores the access credentials (user ID and password) of any object in the baseline infrastructure

file created by a previous witmmtk scantmr command.

encpwd

Encrypts any passwords that have been stored manually in the baseline infrastructure file.

witmmtk trace

You have the option to enable tracing for the Migration Toolkit commands. However, the simplicity of the

migration exercises might prevent major problems that require tracing.

Troubleshooting overview: The witmmtk trace command is one of several sources of troubleshooting

information for the Migration Toolkit:

v When you need to debug the capturing of data for migration, you can activate tracing. You find the trace

results in the trace directory of the AMK directory tree (not the logs directory).

v Use the topology view to have an overview of the migration process and identify incomplete areas that

require further action. See “Using the topology view for XML mapping files” on page 85.

v The Transfer file for SOAP transactions in IBM Tivoli Monitoring V6.2.0 environment provides another

source of troubleshooting information. The Transfer file is located in the Tivoli installation path for IBM

Tivoli Monitoring version 6.2.0.

All witmmtk commands create log files that are located in the $DBDIR/AMK/logs directory. While you

experiment with the toolkit, you might want to enable tracing. The trace command turns tracing on or off

for the toolkit. The command can also to report the current trace setting.


Authorization




Syntax highlights

witmmtk trace [on | off | -?]

Description

Use this command to turn tracing on or off. If no parameters are supplied, the current state of

tracing is returned.

Options

on Turn tracing on (the witmmtk command trace output is placed in the $DBDIR/AMK/trace).

off Turn tracing off.

-? Displays the help message for this command.

witmmtk scantmr

This command creates or validates an baseline XML output file for a migration.

Authorization




Syntax highlights

witmmtk scantmr

[-o force]

[-f <baseline_file>]

[-?]

Description

This command creates or validates an infrastructure baseline file called:

$DBDIR/AMK/analyze/scans/tmr_oid.xml

where tmr_oid specifies the 10-digit prefix of the object ID (oid) for a Tivoli management region. If

the file does not exist, it is created. If the file already exists, the data in the file is validated, and

the file is updated if necessary. However, you can specify the -o force option to force a new file

to be created instead.

Options

See IBM Tivoli Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 for

descriptions of options that enable you to do the following:

v Specify an infrastructure baseline file to be used instead of the default file name.

v Specify that the command create a new file be instead of validating the existing file.

The -? parameter displays the help message for this command.

Migration stage 2: Creating Initial Baseline File

Use the Migration Toolkit to analyze the Tivoli management region. The Migration Toolkit references the

data from the scan and propose an IBM Tivoli Monitoring V6.2.0 environment with corresponding scale

and functionality.

In this exercise you begin to migrate the resources, such as the ones described in Appendix B, “Creating a

test environment for IBM Tivoli Monitoring version 5.1.2,” on page 103.


The first page of this chapter describes the Web GUI for the Migration Toolkit, which provides a graphical

user interface as an alternative to the command-line interface.

Run the following command: witmmtk scantmr

Note: This command requires access to the Java Runtime Environment, Version 1.4.2. See “Setting the

Java path” on page 79 for further information.

The command generates an XML mapping file that describes the Tivoli management region and an

analogous IBM Tivoli Monitoring V6.2.0 environment as described in the following table. The name of the

file is the Tivoli object ID for the Tivoli management region, 1472584478 in the following example.

File name and relative path * Resources that are mapped at this stage

v Tivoli management region to Hub Tivoli Enterprise Monitoring

Server

v Gateway to Remote Tivoli Enterprise Monitoring Server, as needed

v Tivoli management region Endpoints to OS Agent (Windows, AIX,

Solaris, HP-UX, Linux, Linux s/390, Linux-ppc)

v PAC Application Objects to non-OS Agents

* A Windows Explorer view is shown here. On UNIX or Linux computers, the directory structure is

comparable.

Note: Every time that you run the scantmr command, the previous version of the scan file receives a

unique name that include a time stamp and the letters bk. In this example of an old scan file, the

object ID of the Tivoli management region, 1472584478, is concatenated with a time stamp and bk:

1472584478.20070226_16_07_42.bk.xml

The initial baseline XML file represents only a proposal for the new IBM Tivoli Monitoring V6.2.0

environment. You can add, remove, or move the proposed configuration to meet any custom requirements.

What the scan proposes and why: Typically, the scan of the Tivoli management region results in the

following architecture for IBM Tivoli Monitoring V6.2.0:

V5.1.2 component ... ... maps to this V6.2.0 component

Tivoli management region server Hub Tivoli Enterprise Monitoring Server

Each gateway Remote Tivoli Enterprise Monitoring Server

Each Endpoint that has IBM Tivoli Monitoring V5.x

resource models running on it

OS Agent entry

The following scale rules apply to the IBM Tivoli Monitoring V6.2.0 Infrastructure configuration.

v Limit of 15 Remote Tivoli Enterprise Monitoring Server per Hub Tivoli Enterprise Monitoring

Server: If your Tivoli management region environment had more than 15 gateways, the toolkit proposes

that the environment be split between multiple hub Tivoli Enterprise Monitoring Servers for IBM Tivoli

Monitoring V6.2.0.

v Limit of 500 agents per Remote Tivoli Enterprise Monitoring Server: For example, in an

environment with 750 endpoints reporting to a single gateway, the toolkit proposes two remote Tivoli

Enterprise Monitoring Servers for IBM Tivoli Monitoring V6.2.0.

Simplify baseline file for the migration exercise

In this exercise, you take action on the baseline XML mapping file generated by the scantmr command of

the Migration Toolkit.

The migration described here works with a subset of a usual Tivoli management region. The scantmr

command identifies all elements of your Tivoli management region environment. However, consider


pruning the XML output file to contain only one Tivoli management region server, a gateway, and a few

endpoints that have some IBM Tivoli Monitoring V5.1.2 OS-related resource models distributed to them. In

the description of this exercise, it is assumed that some DB2 Database Objects that are being monitored

with IBM Tivoli Monitoring DB2 resource models are also located on the endpoint hosts.

For your own test environment for migration, you have the option to substitute endpoint platforms and IBM

Tivoli Monitoring Application PACs that are present in your IBM Tivoli Monitoring V5.x environment. Only

small adjustments will be required to the sample commands provided in these exercises.

1. Open the default XML mapping file that was generated by the scantmr command in your preferred

XML editing tool.

Table 13 on page 88 provides details regarding the required values. For further information on why the

Migration Toolkit names some components in the XML mapping file, see “Node identification in the

migration process” on page 75 section.

Note: Microsoft WordPad might be adequate for editing XML in this exercise, because the number of

components is relatively few. However, it can be helpful to use an XML editor that validates as

you edit, such as the editor provided with Eclipse, an open-source platform for application

development. SlickEdit is another common tool that can be used to edit and validate XML files.

2. Delete unnecessary elements from the XML mapping file. Ensure that the structure of the file matches

the structure that is presented in Table 12.

If your Tivoli management region contains components, such as gateways, in addition to the

components specified in Table 12, scantmr adds them to the XML mapping file. It is preferable that

you delete the XML references (element) for those additional components in this step. They add

complexity, but do not improve the migration exercise.

For example, the scantmr command creates a separate <Server></Server> tag set for each gateway

in the Tivoli management region, depending on the Migration Toolkit’s assessment of optimal load

balancing. This tag set represents an instance of the remote Tivoli Enterprise Monitoring Server in IBM

Tivoli Monitoring V6.2.0. The remote Tivoli Enterprise Monitoring Server is a component that is

equivalent to a gateway in IBM Tivoli Monitoring V5.1.2.

Delete all but the first <Server></Server> tag set. Only one such tag set is required in any XML

mapping file. In this case, the single, remaining <Server></Server> tag set refers to the hub Tivoli

Enterprise Monitoring Server. Because the IBM Tivoli Monitoring version 6.2.0 monitoring environment

for this exercise is small, the hub server can also act as the remote server.

This exercise requires only the elements presented in Table 12. The actions of the Migration Toolkit are

determined by the contents of the XML mapping file. Migration occurs for only the components that are

referenced in the XML mapping file. Other components are ignored.

Table 12. Hierarchy of the XML mapping file and components in the new IBM Tivoli Monitoring version 6.2.0

environment

Element hierarchy in XML Component in IBM Tivoli Monitoring version 6.2.0

<ITM6.2Infrastructure...

</HubServer> * Hub Tivoli Enterprise Monitoring server

<SOAPConsole... /> SOAP Console (enables communication connections)

<PortalConsole... /> Tivoli Enterprise Portal

<EventServer... /> Event Server

<Server> * Remote Tivoli Enterprise Monitoring server (See the Note

following this table)

<OSAgent... /> Monitoring agents

</Server>

</HubServer>

</ITM6.2Infrastructure>


Table 12. Hierarchy of the XML mapping file and components in the new IBM Tivoli Monitoring version 6.2.0

environment (continued)

Element hierarchy in XML Component in IBM Tivoli Monitoring version 6.2.0

* Be aware that this element contains nested, subordinate elements. This awareness can help you successfully edit

the XML file.

Note: In this exercise, the new IBM Tivoli Monitoring version 6.2.0 environment is small and simple, so

remote monitoring servers are not required. Nonetheless, at least one remote monitoring server,

<Server>, must be specified in the XML mapping file. For this exercise, you copy the values that

you specify in the <HubServer> element to the <Server> element.

You can have multiple <HubServer> tags with up to 15 Server tags nested below that each contain up

to 500 OSAgent tags. For the simple migration exercise, use one <HubServer>, one <Server>, and from

one to three <OSAgent> tag sets.

Using the topology view for XML mapping files

The migration toolkit provides a topology view for migration. The view is updated dynamically to reflect the

stages of migration.

Features of the topology view

The following features are visible in a topology view:

v Infrastructure elements are indicated by large icons.

v A red ″x″ icon indicates that an element is not in the ″deployed″ status.

v Elements can be ″collapsed″, or ″expanded″ by clicking the ″+″ and ″-″ icons.

v Where elements have multiple instances, the icon label shows the actual number of instances.

v When an element is expanded, the view is organized as follows:

– Basic attributes are listed horizontally beside the element type and name.

– Other attributes are listed individually below the element name.

v Green check marks show an object has been deployed.

v The percentage of progress with migration is shown with a thermometer control near the top of the view.

A typical topology view

The following screen capture shows a typical topology view. The browser window shows the XML output

file after the assessment of an endpoint:


Migration stage 3: Creating an IBM Tivoli Monitoring V6.2.0 Test

Environment

An earlier chapter in this document provides the basic instructions for installation of the product on

Windows: Installing IBM Tivoli Monitoring on one Windows computer. The current section provides

additional details related to setting up an environment where you can test migration.

1. For testing purposes, you can create an IBM Tivoli Monitoring V6.2.0 environment as described in

Installing IBM Tivoli Monitoring on one Windows computer. The installation process includes installation

of the required a database.

2. When you follow the instructions in Installing IBM Tivoli Monitoring on one Windows computer you use

a series of panels in an installation window. In the Agent Deployment panel, be sure to put a check

mark beside the Monitoring Agent for Windows OS. This selection stages the software for the Windows

operating system for later deployment. You must deploy this agent to create and populate the Tivoli

Enterprise Monitoring Server deployment depot.


3. Install any remote Tivoli Enterprise Monitoring Server that are required in your system.

To make the migration exercise simpler, skip installing a remote monitoring server. Configure the

monitoring agents to report directly to the hub monitoring server.

If you do want to expand the scale of the exercise, you can install a remote Tivoli Enterprise

Monitoring Server. You use the same step that were outlined in Chapter 2: Exercise 1: Installing IBM

Tivoli Monitoring. However, you install only the Tivoli Enterprise Monitoring Server and Tivoli Enterprise

Monitoring Server Agent Support Files.

When you configure the remote Tivoli Enterprise Monitoring Server, select Remote for the TEMS Type.

Then specify the hostname of the hub Tivoli Enterprise Monitoring Server on the next configuration

page.

Be sure to select the Windows OS Agent to configure for remote deployment to create and populate

the remote Tivoli Enterprise Monitoring Server deployment depot. Step 2 describes this crucial step in

the installation process.

4. Populate Tivoli Enterprise Monitoring Server depot for agent deployment.

You store deployment images as follows:

v On Windows systems: Deployment images for V6.2.0 Application Agents that you plan to deploy to

Windows hosts can be added to the Tivoli Enterprise Monitoring Server depots when you run the

setup.exe routine to install the Application Agent Tivoli Enterprise Monitoring Server Support Files. A

wizard panel is displayed that allows you to select the agent that you want to configure for remote

deployment. This panel is similar to the one pictured in Step 2.

v On UNIX and Linux systems: To add deployment images for OS Agents or Application Agents that

you plan to deploy to non-Windows hosts, you use the tacmd addbundles command.

set TIMEOUT=3600

tacmd login -s TEMSserver -u user -p password

tacmd addbundles -i path_to_image


where path_to_image is the directory path for the deployment images, usually image\unix directory.

By using the -i option you install all prerequisite bundles at the same time.

Repeat this command to add the deployment images of each type of OS Agent. Repeat this

command once for each Application/operating-system combination you plan to deploy in your

environment.

You must run these commands on each remote Tivoli Enterprise Monitoring Server that you plan to

use to deploy agents. The commands that you run on each remote Tivoli Enterprise Monitoring Server

is the same, except that you specify a new –i image location for each Application/operating-system

combination. Because of the similar syntax, it might be useful to extract the tar files for the installation

image in a location that you can access throughout the network. Record these commands in a script

that you can run on each Tivoli Enterprise Monitoring Server.

For more information regarding these commands see the IBM Tivoli Monitoring Installation and Setup

Guide.

5. Install an IBM Tivoli Monitoring 4.1.1 LCF (lightweight client framework) Endpoint on the hub Tivoli

Enterprise Monitoring Server.

The Tivoli management region server depends on this LCF Endpoint to enable migration based on the

witmmtk migrate command. However, this capability is available only for the OS (operating system)

agents in IBM Tivoli Monitoring.

Migration stage 4: Updating the baseline file

Update the baseline file with the names and attributes of the IBM Tivoli Monitoring V6.2.0 environment that

you have created.

The IBM Tivoli Monitoring V6.2.0 environment that is discussed in “Migration stage 3: Creating an IBM

Tivoli Monitoring V6.2.0 Test Environment” on page 86 gives you many values that are required in the XML

baseline file. You insert these values as described in this procedure.

Add attributes to the incomplete elements in the XML mapping file.

You must replace all instances of AMK-REQUIRED-AMK with actual values from your Tivoli management

region. You generate these values as discussed in “Migration stage 3: Creating an IBM Tivoli Monitoring

V6.2.0 Test Environment” on page 86. AMK is the unique code of the Migration Toolkit in IBM Tivoli

Monitoring V5.1.2. The values in Table 13typically have the AMK-REQUIRED-AMK string. You must

replace the string with actual values:

Table 13. Required values in the XML mapping file for components in the new IBM Tivoli Monitoring V6.2.0

environment

Element

″AMK-REQUIRED-AMK″

values to replace with

actual values Comment

<ITM6.2Infrastructure>

</ITM6.2Infrastructure>

(none) —

</HubServer></HubServer>

*

hub_installDir The directory where the hub Tivoli Enterprise Monitoring

server is installed.

remote_control_endpoint The Tivoli endpoint label for the LCF endpoint that you

installed on hub Tivoli Enterprise Monitoring server.

target Obtain this information from the list of managed systems

that the Migration Toolkit provides.


Table 13. Required values in the XML mapping file for components in the new IBM Tivoli Monitoring V6.2.0

environment (continued)

Element

″AMK-REQUIRED-AMK″

values to replace with

actual values Comment

<SOAPConsole... /> hostname Include the domain specification, if your test environment

spans multiple domains. The following example host

name includes a domain specification:

my_host.tivoli.ibm.com

password You set this value in Step 5.

port The default value 1920 is typically valid.

user You set this value in Step 5.

<PortalConsole... /> hostname Include the domain specification, if your test environment







<EventServer... /> eventServerLabel For this exercise, no changes are required.

<Server></Server> * hostname Include the domain specification, if your test environment





target Obtain this information from the list of managed systems

that the Migration Toolkit provides.

<OSAgent... /> hostname In this exercise, the Migration Toolkit detects the endpoint

that you installed in Appendix B, “Creating a test

environment for IBM Tivoli Monitoring version 5.1.2,” on

page 103 and assigns the endpoint names as the new

agent names. For related information, see “Node

identification in the migration process” on page 75.



* Be aware that this element contains nested, subordinate elements. This awareness can help you successfully edit

the XML file.

** See “Password-related commands” on page 81 for information on password protection.

Note: If you do not require password encryption during the migration exercise, you can ignore the next

step and type the required user names and passwords directly in the XML file. In this case, other

users can open the XML mapping file and view the passwords in raw, unencrypted text.

Migration stage 5: Validating the baseline file

You run the scantmr command again, to validate changes that you have made to the XML mapping file.

1. Run the following command to scan the Tivoli management region a second time:

witmmtk scantmr


A new version of the scan file is generated. The original XML map file, called the baseline file, does

not change unless you explicitly allow the command to change the file. See the IBM Tivoli Monitoring,

version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 for details regarding the scantmr

command.

Note: Successive analysis by the scantmr command do the following:

v Validate the edits that you made in the baseline file.

v Check communication links with the IBM Tivoli Monitoring V6.2.0 environment.

v As appropriate, change the value of the NOT_CONFIGURED status attributes to deployed.

Note: Old versions of the scan files, including the baseline file, receive unique names that include a

time stamp and the letters bk. In this example of an old scan file, the object ID of the Tivoli

management region, 1472584478 is concatenated with a time stamp and bk:

1472584478.20070226_16_07_42.bk.xml

2. Inspect the updated XML mapping file to ensure successful deployment of required components.

Before you proceed to the next step, all servers and services except for the OS Agents must be in the

DEPLOYED status. The agents are excepted from this requirement. At this stage, the status of each

agent, which is specified in an <OSAgents> XML tag, can remain as NOT_CONFIGURED.

About the commands for the later stages of migration: assess and

migrate

The section provides an overview of the commands used for the later stages of migration.

You use the assess and migrate commands in these stages of migration:

assess command

v “Migration stage 6: Assessing Endpoints” on page 93

v “Migration stage 7: Assessing Profiles” on page 93

v “Migration stage 8: Assessing Profile Managers” on page 94

migrate command

v “Migration stage 9: Migrating endpoint assessment files” on page 95

v “Migration stage 10: Migrating Profile Assess Files” on page 95

v “Migration stage 11: Migrating Profile Manager Assess Files” on page 95

v “Rolling back a migration” on page 96

v “Cleaning up after a migration” on page 96

See the IBM Tivoli Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 document for a

full description of options and usage for these commands.

Note: All commands that are specific to the Migration Toolkit require the initial witmmtk identifier, as in

this example: witmmtk assess.

witmmtk assess

This section provides an overview of the witmmtk assess command. Enter witmmtk assess -? to display

the help message for this command.

Authorization





Syntax highlights

witmmtk assess

{[-pm profile_manager ]...

| [-p profile]...

| [-e endpoint]...}

where profile_manager, profile, and endpoint are names of assess files. These files have the same

name as the V5.1.2 Tivoli resources that you are migrating..

Note: The best practice is to run the command multiple times for each type of resource. Each

time, use one option (-pm, -p, or -e).

Description

Performs the following assessment operations to prepare for a migration:

v Collects data about V5.1.2 managed resources to be migrated (endpoints, profiles, and profile

managers).

Note: It is an option and a best practice to run the witmmtk assess command successively for

endpoints, then profiles, and then profile managers. This option is demonstrated in the

current migration exercise. Separating the steps of migration helps maintain accuracy

when you are manually entering values in the baseline XML file. Also, debugging

problems is easier when fewer types of changes are happening in a given step of

migration.

v Provides data to the migrate command.

Output files

The assess command creates a separate XML output file for each resource that it assesses. The

name of the output file is the name of the endpoint, profile, or profile manager with a .xml

extension. The output files are created in the following directories on the Tivoli server:

$DBDIR/AMK/analyze/endpoints

$DBDIR/AMK/analyze/profiles

$DBDIR/AMK/analyze/profilemanagers

where $DBDIR is the path name of the Tivoli object database directory.

Options

Additional options permit you to customize assessment:

v Use the -a option to migrate all profile managers (local and remote) that are accessible from the

current Tivoli management region.

v Use the -i option to reference a file that lists the resource to migrate.

v Use the -rm option to limit the assessment to one or more specific resource models.

v Use the -o option to force creation of a new assess file or to assess a profile manager, but not

its nested profile managers

Enter witmmtk assess -? to display the help message for this command. See IBM Tivoli

Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 for a full description of

options and usage.

Example

The following command assesses the endpoints named EP1 and EP2, using the default baseline

file as input:

witmmtk assess -e EP1 -e EP2

The assess command determines the operating system and supported applications on each

endpoint. The output files from this command, EP1.xml and EP2.xml, specify the monitoring

agents to be deployed to the endpoints when they are migrated (using the migrate command).


witmmtk migrate

This section provides an overview of the witmmtk migrate command. Enter witmmtk migrate -? to

display the help message for this command. See IBM Tivoli Monitoring, version 6.2.0: Upgrading from IBM

Tivoli Monitoring V5.1.2 for a full description of options and usage.

Authorization




Syntax highlights

witmmtk migrate

{ [-x assess_file]

| [-d assess_directory]

| [-i assess_list_file] }

{ -u | -r | -c }

Description

Deploys V6.2.0 resources based on the specifications in the XML output files of the assess

command.

Note: The best practice is to run the command multiple times. Each time, migrate one type of

assess file (endpoint, profile, or profile manager).

Output files

The migrate command updates the XML output files from the assess command. View the files

after running the migrate command to verify that the mapped V6.2.0 resources (monitoring

agents, situations, and managed system lists) have been successfully deployed.

Options

You use one of the following options to specify which XML files to target with the migrate

command.

v -x assess_file Specifies a specific XML file. Repeat the option to migrate multiple files.

OR

v -d assess_directory Specifies a directory containing the XML files.

OR

v -i assess_list_file Specifies a text file listing the XML files. Each line must contain only the full

path name of the file to migrate.

v -u Triggers migration. Other options trigger roll back of a migration or cleanup after a migration..

Additional options are as follows:

v Use the -a agent_name option to identify a type of monitoring agent to migrate to V6.2.0, where

agent_name is the name of a type of agent in V6.2.0. If you do not specify any agent type to

migrate, all agents of all types are migrated.

v Use the -r option to roll back the migration of all the specified managed resources.

Note: You can roll back the migration of specific components or of all components, except for

the migration of V6.2.0 OS agents.

v Use the -c option to clean up the specified managed resources, removing them from the V5.1.2

environment.

Enter witmmtk migrate -? to display the help message for this command. See IBM Tivoli

Monitoring, version 6.2.0: Upgrading from IBM Tivoli Monitoring V5.1.2 for a full description of

options and usage.

Example

The following example migrates the objects defined in myProfile.xml using the default baseline:


witmmtk migrate -x /tmp/myProfile.xml -u

Migration stage 6: Assessing Endpoints

In this stage of the migration exercise, you begin to capture data from endpoints in the Tivoli management

region, including the capture of the thresholds, parameters, schedules, and other monitoring specifications.

The data is stored in a new XML mapping file for the endpoint-to-agent migration.

Consider enabling tracing for this and other Migration Toolkit commands. This command and other

troubleshooting options are listed in “witmmtk trace” on page 81

Note: The Migration Toolkit automatically deploys the IBM Tivoli Monitoring version 5.1.2 LCF endpoint to

the computer that you set up as the hub Tivoli Enterprise Monitoring Server for IBM Tivoli

Monitoring V6.2.0. The LCF endpoint enables the Tivoli management region to communicate with

the Tivoli Enterprise Monitoring Server.


witmmtk assess -e NT_Endpoint

Note: In this example command, the endpoint name is typed in directly. NT_Endpoint is the name of

an actual endpoint in the test environment described here: Appendix B, “Creating a test

environment for IBM Tivoli Monitoring version 5.1.2,” on page 103.For more information on this command see “About the commands for the later stages of migration:

assess and migrate” on page 90.

The preceding command generates a mapping file for the resource as shown here:

File name and relative path * Resources that are mapped at this stage

v Agent Mapping Files driven

v Endpoints become OS Agents

v Application Objects become non-OS Agents


comparable.

2. Analyze the proposed IBM Tivoli Monitoring V6.2.0 details in the browser-based topology view. See

“Using the topology view for XML mapping files” on page 85 for more information.

The XML mapping file specifies how each monitoring specification for an endpoint maps to a specific

situation in IBM Tivoli Monitoring V6.2.0. Situations describe conditions that you want to monitor. Some

endpoint specifications cannot be mapped automatically, and the XML mapping file identifies those

cases. For example indications for Network Interface Cards (NICs) cannot be mapped automatically.

Migration stage 7: Assessing Profiles

In this stage of the migration exercise, you continue capturing data from the Tivoli management region,

including the capture of the thresholds, parameters, schedules, and other monitoring specifications.

The profiles provide severities, intervals, and other monitoring details to IBM Tivoli Monitoring V6.2.0.


witmmtk assess -p NT_Profile

Note: In this example command, the profile name is typed in directly. NT_Profile is the name of an

actual endpoint in the test environment described here: Appendix B, “Creating a test

environment for IBM Tivoli Monitoring version 5.1.2,” on page 103.For more information on this command see “About the commands for the later stages of migration:

assess and migrate” on page 90.


The preceding command generates a mapping file for the resource as shown here:

File name and relative path * Specifications that are mapped at this stage

v Indication becomes one or more Situations

v Resource Model Logic and the specific Resource Model

Configuration (Parameters, Thresholds, Context Variables) mapped

to Situations


comparable.



Migration stage 8: Assessing Profile Managers

In this stage of the migration exercise, you continue capturing data from the Tivoli management region,

including the capture of the thresholds, parameters, schedules, and other monitoring specifications.


witmmtk assess -pm NT_ProfMgr

The Migration Toolkit renders the profile managers as Managed System Lists for IBM Tivoli Monitoring

V6.2.0. Table 14 describes the differences between the two constructs.

Note: In this example command, the profile manager name is typed in directly. NT_ProfMgr is the

name of an actual profile manager in the test environment described here: Appendix B,

“Creating a test environment for IBM Tivoli Monitoring version 5.1.2,” on page 103.For more information on this command see “About the commands for the later stages of migration:

assess and migrate” on page 90. The preceding command generates a mapping file for the resource

as shown here:

File name and relative path * Specifications that are mapped at this stage

v V5.1.2 subscriber lists becomes managed system lists (MSLs)

v One MSL for each Profile and Agent type

v The distribution relationship between Profiles and Subscribers is

replicated between Situations and Managed Systems

v It assesses all contained Profiles (unless a Filter -p is specified or

already assessed)

v It assesses all contained Endpoint (unless a Filter -e is specified

or already assessed)

v The subscription tree is traversed to generate the list.

v A flatten option tells the tool to ignore Profile copies


comparable.

The following table clarifies the discrepancies that the Migration Toolkit resolves in migrating profile

managers to IBM Tivoli Monitoring V6.2.0.

Table 14. Comparison of Profile Managers and Managed System Lists

Profile managers Managed system lists

v Hierarchical

v Groups monitoring clients as one entity

v Like an individual subscriber

v Heterogeneous subscribers

v Maintains Profile copies on each level in the hierarchy

v Not hierarchical. Migrated lists represent a flattened

version of subscriber lists.

v Groups managed systems as one entity

v Like individual managed systems

v Agent-type specific subscribers




Migration stage 9: Migrating endpoint assessment files

This procedure describes the use of the Migration Toolkit’s migrate command to migrate endpoints.

This procedure instructs you to run the several migration commands from the following specific directories

in the AMK directory structure that the Migration Toolkit creates in the Tivoli installation path:

..\AMK\analyze\endpoints

..\AMK\analyze\profiles

..\AMK\analyze\profilemanagers

This practice allows you to run the command without specifying the path to the relevant XML mapping file

for migration of endpoints, profiles, or profile managers.

Run the following command to migrate endpoints:

witmmtk migrate -u -x NT_endpoint.xml

Result of command:

v Deploys the OS Agent (unless it is already there). For deployment, the Migration Toolkit takes

advantage of the SOAP communication protocol that is available in the V6.2.0 environment

v The Migration Toolkit references a Tivoli LCF endpoint that is installed on the Hub Tivoli Enterprise

Monitoring Server.

Note: The Tivoli LCF endpoint enables the V5.1.2 environment to communicate with the V6.2.0

environment.

v Deploys the non-OS Agents (unless they already exist).

v Updates the status fields in the Endpoint Assess File.

Migration stage 10: Migrating Profile Assess Files

This procedure describes the use of the Migration Toolkit’s migrate command to migrate profiles.

Migrate profiles.

witmmtk migrate -u -x NT_Profile.xml

Result of command:

v Creates the required situations with migrated indications and events from the IBM Tivoli Monitoring

V5.1.2 monitoring environment. A separate situation is created for each indication from a resource

model.

Note: Situations that correspond to the resource models associated with a profile manager are

activated after the profile manager is migrated.

v Updates the status fields in the Profile Assess File.

Migration stage 11: Migrating Profile Manager Assess Files

This procedure describes the use of the Migration Toolkit’s migrate command to migrate profile managers.

Migrate profile managers.

witmmtk migrate -u -x NT_ProfMgr.xml

Result of command:

v Distributes situations to the corresponding endpoints.


v Creates the required managed system lists.

v Creates the distribution relationship between situations and managed system lists.

v Configures the situations association class for the portal.

v Updates the status fields in the profile manager assessment file.

Post-migration activities

After migration, verify that the migration was successful. Also, you can run commands to roll back parts of

the migration, uninstall IBM Tivoli Monitoring V5.1.2 components, and uninstall the toolkit itself.

Verifying the migration

You can confirm success of migration by inspecting several areas of the IBM Tivoli Monitoring V6.2.0

environment.

1. Check the message logs for IBM Tivoli Monitoring V6.2.0 to verify that monitoring events are taking

place.

2. Find the migrated components in the Tivoli Enterprise Portal. Look for a host name matching the name

of the Tivoli management region server.

Look for situations from the V5.1.2 environment. For example, situations derived from V5.1.2 on

Windows might have the NT5_ prefix. The complete naming convention for situations is a

concatenation of the following values, in succession:

v The first two digits designate the agent type.

v The next five digits identify the situations as coming from IBM Tivoli Monitoring V5.1.2

v Next comes the object ID for the original profile, in hexadecimal format.

v The last string in the name are characters derived from the name of the original Indication.

Rolling back a migration

The Migration Toolkit enables you to roll back part or all of a migration.

In this procedure, you roll back and migrate again one endpoint, the application-related endpoint specified

in the NT_endpoint.xml.

1. Run the following command to roll back the migration, using the -r (rollback) option:

witmmtk migrate -r -x NT_endpoint.xml

See “About the commands for the later stages of migration: assess and migrate” on page 90 for details

regarding parameters for this command.

2. Confirm that the rollback is successful by viewing the Tivoli Enterprise Portal.

3. Run the following command to repeat the migration, using the -u (migrate) option:

witmmtk migrate -u -x NT_endpoint.xml



4. Confirm that the remigration is successful by viewing the Tivoli Enterprise Portal.

Cleaning up after a migration

Although you can run IBM Tivoli Monitoring V5.1.2 and IBM Tivoli Monitoring V6.2.0 concurrently, the

Migration Toolkit enables you to perform clean up operations for the IBM Tivoli Monitoring V5.1.2

environment.

You can perform the following clean up operations for the IBM Tivoli Monitoring V5.1.2 environment:

v Remove the endpoint.

Note: Only one endpoint is removed. The resource model stops running, but the Tivoli LCF endpoint

remains in place.


v Unsubscribe the endpoint.

The clean up operation invokes the DMEndpointUninstall task from IBM Tivoli Monitoring V5.1.2. This

task stops the endpoint engine and removes all V5.1.2 components on the endpoint.

You can invoke the command one time to clean up all migrated endpoints, profile, and profile managers.

However, in this exercise you clean up only one endpoint, the application-related endpoint specified in the

ep_win_to_itm62.xml.

1. Run the following command to roll back the migration, using the -c (rollback) option:

witmmtk migrate -c -x NT_endpoint.xml



2. Confirm that the cleanup is successful by viewing the Tivoli installation path on the endpoint and by

looking at the process queue on the endpoint.

Uninstalling the migration toolkit

You use the Tivoli wuninst command to uninstall the migration toolkit from your Tivoli server.

1. Enter the following command to uninstall the toolkit:

Note: You must run this command from a bash shell. (“Preparing the installation image” on page 77

includes a description of how to source the bash shell.)wuninst MTK Tivoli_server -rmfiles

where MTK identifies the Migration Toolkit and Tivoli_server is the name of the Tivoli management

region server or gateway where you installed the toolkit.

2. Enter the following command to confirm that the Tivoli database was correctly updated during the

uninstall operation:

wchkdb -u

Migration from IBM Tivoli Monitoring version 5.1.2 to version 6.2.0,

complex scenario (based on the Agent Builder)

You have the option to create a new monitoring agent that maps the functionality of complex, custom

resource models that you built in IBM Tivoli Monitoring version 5.x. The data that a resource model

requires comes from external data providers. Because resource models capture complex sets of data and

can process the data they capture, it can be difficult to map their functionality to an agent that you build.

For this reason, migrating a complex, custom resource model to a new monitoring agent is an option that

requires extensive experience and knowledge.

For migration of resource models, you follow the general procedures for creating an agent in “Building a

custom monitoring agent using Agent Builder” on page 37. However, construction of a monitoring agent to

map functionality of a resource model differs from the exercise in the following specific respects:

v Instead of selecting This agent will monitor Windows log events in the Monitoring Information

window in Step 3a on page 41, you select This agent will gather data from an external data source.

v When generating the agent in Step 4c on page 43, you must select the Generate an ITM 5x mapping

file option in the Generation Type panel of the Generate Agent Wizard. When you perform a migration,

the assess command of the Migration Toolkit references this mapping file. You have the option to

copying and editing an existing mapping file or to create a file from scratch.

Upgrading a complex, custom resource model can differ from upgrading a standard resource model as

follows:


v When you perform a migration, the assess command of the Migration Toolkit must reference a mapping

file for the resource model. You have the option to copy and edit an existing mapping file or creating a

file from scratch. The mapping files for complex, custom resource models are more difficult to construct.

v To evaluate this mapping file, you might need to create a Java resource model plug-in class, which

allows you to add your own coding to the standard evaluation used by the Agent Builder.

v If the resource model data collection is different from that used by the standard resource models, you

might also have to create a new agent to collect the data, using the agent builder. For this agent, you

also need to create an agent mapping file, so that the migration works correctly.

v If the data collection in the agent cannot be provided by standard operating system facilities, you might

need to create a Java agent plug-in class to do the collection.

When these items have been developed and tested, the actual migration follows exactly the same steps

as the migration of standard resource models.


Appendix A. Uninstalling IBM Tivoli Monitoring

Use the following steps to uninstall the IBM Tivoli Monitoring components that you worked with in the

exercises in this document:

v “Uninstalling a monitoring agent”

v “Uninstalling the IBM Tivoli Enterprise Console event synchronization” on page 101

v “Uninstalling the entire IBM Tivoli Monitoring environment” on page 101

These procedures pertain to components that run on the Windows operating system. Similar functionality

and procedures exist on other operating systems, such as UNIX, AIX, and Linux. For examples and

instructions, see the IBM Tivoli Monitoring Installation and Setup Guide.

Uninstalling a monitoring agent

You can use this procedure to remove an agent or other individual component of IBM Tivoli Monitoring.

This procedure provides an alternative to uninstalling the entire environment as described in “Uninstalling

the entire IBM Tivoli Monitoring environment” on page 101.

In this exercise, you remove one of the monitoring agents that you installed in “Installing IBM Tivoli

Monitoring on one Windows computer” on page 3. Read “Uninstalling the Warehouse Proxy” on page 101

if you choose to uninstall the Warehouse Proxy agent.

1. From the Windows desktop, click Start > Settings > Control Panel (for Windows 2000) or Start >

Control Panel (for Windows 2003).

2. Click Add/Remove Programs. The Add or Remove Programs window is displayed.

Uninstalling separate monitoring packages

The exercises in this document do not discuss the separate monitoring products that you can

purchase for IBM Tivoli Monitoring. For example, you can purchase the products listed in

“Additional types of monitoring agents” on page 2.

You uninstall such products as follows:

a. Select the entry for that specific product (not IBM Tivoli Monitoring itself) in the Add or

Remove Programs window.

b. Click Remove/Change to launch the wizard for modification and removal of the product.

c. Select the Remove option and follow the remaining steps as instructed by the wizard.

3. Select IBM Tivoli Monitoring and click Change/Remove. The window shown in Figure 13 on page

100 is displayed.


4. Click OK in the confirmation message that is displayed.

IBM Tivoli Monitoring - InstallShield Wizard

On the following panel, items you have already installed are pre-selected.

Selecting a new item installs that item.

Deselecting an item uninstalls that item.

OK

The Add or Remove Feature panel of the wizard is displayed.

5. Clear (remove the check mark from) an item to uninstall it.

For example, to uninstall an agent, expand Tivoli Enterprise Monitoring Agents and remove the

check mark from the agent that you want to uninstall.

6. Click Next to begin the removal process for the items you cleared in Step 5.

The installation wizard goes through all the original steps for installation and configuration. Nothing is

changed, except that the monitoring agent that you specified is removed.

7. Click Finish to complete the uninstallation.

Figure 13. Change/Remove IBM Tivoli Monitoring


Uninstalling the Warehouse Proxy

The standard method for uninstalling a product component is valid for uninstalling the Warehouse Proxy

agent. See “Uninstalling a monitoring agent” on page 99. However, the following aspects of data

warehousing exist independently of the Warehouse Proxy agent:

v The warehouse database.

v Historical situations on the agent.

Prior to uninstalling the Warehouse Proxy agent, perform the following actions:

v Stop the historical situations.

v Drop (delete) the warehouse database.

v Remove the ODBC data source. See “Removing the ODBC data source connection.”

v Remove the Windows user, ITMUser, that was created to connect to a DB2 database.

Removing the ODBC data source connection

When you uninstall IBM Tivoli Monitoring, the ODBC data source created for the Warehouse Proxy agent

is not removed automatically. This action can cause problems when you reinstall IBM Tivoli Monitoring. To

prevent these problems, manually remove the ODBC data source after you uninstall IBM Tivoli Monitoring.

For example, to remove the DB2 data source from the DB2 command line, run the following command:

DB2

UNCATALOG SYSTEM ODBC DATA SOURCE <datasource_name>

If you are using an MS SQL Server or Oracle database, see the documentation for your database software

for instructions on how to remove a data source.

Uninstalling the IBM Tivoli Enterprise Console event synchronization

Use the following steps to uninstall the event synchronization from your event server:

Note: Event synchronization now encompasses both IBM Tivoli Enterprise Console and

Netcool/OMNIbus.The instructions for uninstalling the event synchronization component from

OMNIbus differ from those for IBM Tivoli Enterprise Console. Please see the IBM Tivoli Monitoring

Installation and Setup Guidefor more information.

1. Stop the event synchronization on the event server by running the following command:

On Windows:

<tec_installdir>\TME\TEC\OM_TEC\bin\stop.cmd

On UNIX:

<tec_installdir>/TME/TEC/OM_TEC/bin/stop.sh

2. Run the following uninstallation program:

v On Windows: <tec_installdir>\TME\TEC\OM_TEC\_uninst\uninstaller.exe

v On UNIX: <tec_installdir>/TME/TEC/OM_TEC/_uninst/uninstaller.bin

where <tec_installdir> is the location of the IBM Tivoli Enterprise Console installation.

3. Follow the prompts in the uninstallation program.

Uninstalling the entire IBM Tivoli Monitoring environment

Use the following procedure to remove the entire IBM Tivoli Monitoring environment from a Windows

computer. Instructions for other operating systems are provided in the IBM Tivoli Monitoring Installation

and Setup Guide.

Appendix A. Uninstalling IBM Tivoli Monitoring 101

If you want to remove just one component such as an agent, see “Uninstalling a monitoring agent” on

page 99.

1. From the desktop, click Start > Settings > Control Panel (for Windows 2000) or Start > Control

Panel (for Windows 2003).

2. Click Add/Remove Programs. The Add or Remove Programs window is displayed.

3. Select IBM Tivoli Monitoring and click Change/Remove. The window shown in Figure 13 on page

100 is displayed.

4. Select Remove and click Next.

5. Click OK in the confirmation message that is displayed. A progress window is displayed.

6. Click Yes in the confirmation message that is displayed regarding deletion of the portal database.

A dialog box prompts you to enter the user ID and password for the administrator of the database

that the IBM Tivoli Monitoring portal server uses. These values were set during the installation of the

product. For example, the db2admin user ID is used during the procedure “Installing IBM Tivoli

Monitoring on one Windows computer” on page 3.

7. Type the password for the database administrator in the Admin Password field and click OK.

A progress window is displayed for the uninstallation process.

8. Select Yes in response to the prompt to restart your computer.

9. Click Finish in the final window.

10. If you intend to reinstall the product at a later time, perform the procedure described in “Removing the

ODBC data source connection” on page 101. You must create a new connection for the ODBC data

source when you reinstall the product.

Figure 14. DB2 database information


Appendix B. Creating a test environment for IBM Tivoli

Monitoring version 5.1.2

This section describes how to create a simple test environment in IBM Tivoli Monitoring version 5.1.2. You

can use such an environment to experiment with IBM Tivoli Monitoring version 6.2.0, using the Migration

Toolkit.

This appendix describes how to create the resources in a test environment for migration. “Exercise:

Performing a basic migration” on page 73 is designed to work with the test environment that is described

here. This topic includes the following subtopics:

v “Creating profile managers and profiles”

v “Subscribing resources to profile managers” on page 104

v “Adding resource models to a profile” on page 104

v “Distributing profiles” on page 105

You can use these resources to complete the procedures described in “Exercise: Performing a basic

migration” on page 73.

Note: By creating the a few new resources in a test environment, you avoid unnecessary complexity in

the migration exercise. Also, you can use the new resources to avoid working with resources in a

pre-existing Tivoli management region that you might use for other purposes, such as testing or

staging deployments.

It is assumed that you have a pre-existing Tivoli management region. See “Assumptions in the basic

migration exercise” on page 73 for a discussion of other assumptions regarding the migration exercise.

Creating profile managers and profiles

Use the Tivoli command line or from the desktop to create profile managers and profiles.

v Using the Tivoli command line interface:

Note: For additional information about these commands, see IBM Tivoli Monitoring User’s Guide,

Version 5.1.2 (SH19-4569-03).

1. Use the wcrtprfmgr command to create a profile manager. For example, to create a profile

manager called NT_ProfMgr in the TestRegion policy region, enter the following command:

wcrtprfmgr @PolicyRegion:TestRegion NT_ProfMgr

2. Use the wsetpm command to make the profile manager operate in dataless mode.

wsetpm -d @ProfileManager:NT_ProfMgr

3. Use the wcrtprf command to create a profile. For example, to create a profile called NT_Profile in

the NT_ProfMgr profile manager, enter the following command:

wcrtprf @ProfileManager:NT_ProfMgr Tmw2kProfile NT_Profile

v Using the Tivoli desktop:

1. Double-click a policy region icon to open it.

2. Select Create > Profile Manager to open the Create Profile Manager window.

3. Type NT_ProfMgr in the Name/Icon Label text box.

4. Select the Dataless Endpoint Mode check box to create the profile manager in dataless mode.

5. Click Create & Close to close the Create Profile Manager window.

6. Double-click the NT_ProfMgr profile manager icon to open the Profile Manager window.

7. Select Create > Profile to open the Create Profile window.


8. Type NT_Profile for the profile in the Name/Icon text box.

9. Select the Tmw2kProfile resource from the Type list.

10. Click Create & Close. An icon for the new profile is displayed in the Profiles area of the Profile

Manager window

Subscribing resources to profile managers

Use the Tivoli command line or from the desktop to subscribe resources to profile managers.

v Using the Tivoli command line interface: Use the wsub command to add subscribers to the profile

manager. For example, to add a w32-ix86 Endpoint called winhost as a subscriber to the NT_ProfMgr

profile manager, enter the following command:

wsub @ProfileManager:NT_ProfMgr @Endpoint:NT_endpoint

Note: For additional information about this command, see Tivoli Management Framework Reference

Guide, Version 5.1.2 (SH19-4569-03).


1. Double-click a policy region icon to open it.

2. Double-click the NT_ProfMgr profile manager icon to open the Profile Manager window.

3. Select Profile Manager > Subscribers to open the Subscribers window.

4. Select the subscribers to receive the profile distribution from the Available to become Subscribers

scrolling list.

5. Click the left-arrow to move the selected subscribers to the Current Subscribers scrolling list.

6. Click Set Subscriptions & Close to add the subscribers. Subscribers are displayed in the

Subscribers field of the Profile Manager window.

Adding resource models to a profile

Use the Tivoli command line or from the desktop to add resource models to a profile.


Use the wdmeditprf command to add a resource model to a profile.

Note: For additional information about this command, see IBM Tivoli Monitoring User’s Guide, Version

5.1.2 (SH19-4569-03).


1. Open the IBM Tivoli Monitoring Profile window by following these steps:

a. Double-click a policy region icon to open the policy region.

b. Double-click the NT_ProfMgr profile manager icon to open the profile manager.

c. Double-click the NT_Profile profile icon to which you want to add a resource model.

2. Click Add With Defaults to open the Add Resource Models to Profile window.

3. Select the resource model category from the Category drop-down list, for example,Windows.

4. Select the resource models you want from the Resource Model drop-down list while holding down

the ctrl key.

– Logical Disk

– Memory

– Physical Disk

– Processor

– Services

– TCP/IP

Click Add & Close. The resource models are added to the NT_Profile profile.


Distributing profiles

Use the Tivoli command line or from the desktop to distribute profiles.


Use the wdmdistrib command to distribute the profile to the subscribers of the profile manager.

wdmdistrib -p NT_Profile @Endpoint:NT_endpoint

Note: For additional information about this command, see IBM Tivoli Monitoring User’s Guide, Version

5.1.2 (SH19-4569-03).

This command updates subscriber databases and configuration files. If no subscriber is specified,

wdmdistrib updates all subscribers.


1. Open the NT_Profile window by following these steps:

a. Double-click the policy region icon to open the policy region.

b. Double-click the NT_ProfMgr profile manager icon you want to open the Profile Manager

window.

c. Double-click the NT_Profile to open the Profile window.

Click Profile > Distribute. The Distribute Profile window opens.

2. Select All levels of subscribers.

3. Select Make each subscriber’s profile an EXACT COPY of this profile from the Distribution Will

options.

4. Select the subscribers to receive the profile using the following steps:

a. Select the list of subscribers that you want to distribute the profile to from the Do Not Distribute

to These Subscribers scrolling list.

b. Click the left arrow to move the subscribers to the Distribute to These subscribers scrolling

list.

Note: Make sure that each subscriber in the Distribute to These Subscribers scrolling list is

the correct type for this resource model profile.

6.Click Distribute & Close.

Appendix B. Creating a test environment for IBM Tivoli Monitoring version 5.1.2 105

Appendix C. Documentation library

This appendix contains information about the publications related to IBM Tivoli Monitoring and to the

commonly shared components of Tivoli Management Services. These publications are listed in the

following categories:

v IBM Tivoli Monitoring library

v Related publications

See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide, SC23-8816, for

information about accessing and using the publications. You can find the Documentation Guide in the IBM

Tivoli 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 Tivoli

Monitoring and OMEGAMON XE Information Center. To find publications from the previous version of a

product, click Previous information centers on the Welcome page for the product.

IBM Tivoli Monitoring library

The following publications provide information about IBM Tivoli Monitoring V6.2 and about the commonly

shared components of Tivoli Management Services:

v Quick Start Guide

Introduces the components of IBM Tivoli Monitoring.

v Exploring IBM Tivoli Monitoring

Provides a series of exercises to help you explore IBM Tivoli Monitoring. By completing the activities in

this workbook, you will install and configure your monitoring environment, explore both the graphical and

command-line interfaces of the product, use some of the new features, and work with several

monitoring agents.

v Installation and Setup Guide

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

Gives instructions for the SMP/E installation of the Tivoli Management Services components on z/OS®.

v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS

Gives detailed instructions for using the Configuration Tool to configure Tivoli Enterprise Monitoring

Server on z/OS systems. Includes scenarios for using batch mode to replicate monitoring environments

across the z/OS enterprise. Also provides instructions for setting up security and for adding application

support to a Tivoli Enterprise Monitoring Server on z/OS.

v Administrator’s Guide

Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,

including Tivoli Enterprise Portal user administration.

v Tivoli Enterprise Portal online help

Provides context-sensitive reference information about all features and customization options of the

Tivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli Enterprise Portal.

v User’s Guide

Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons and detailed

instructions for all Tivoli Enterprise Portal features.

v Command Reference

Provides detailed syntax and parameter information, as well as examples, for the commands you can

use in IBM Tivoli Monitoring.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/


v Problem Determination Guide

Provides information to help you troubleshoot problems with the software.

v Messages

Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-based

Tivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS and

TMS:Engine).

v Upgrading from V5.1.2

Gives instructions for upgrading custom resource models from IBM Tivoli Monitoring V5.1.2 to IBM Tivoli

Monitoring V6.2.

v IBM Tivoli Universal Agent User’s Guide

Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM Tivoli

Universal Agent enables you to use the monitoring and automation capabilities of IBM Tivoli Monitoring

to monitor any type of data you collect.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide

Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and provides

descriptions, syntax, and return status codes for the API calls and command-line interface commands.

v Agent Builder User’s Guide

Explains how to use the Agent Builder for creating monitoring agents and their installation packages,

and for adding functions to existing agents.

v Fix Pack Readme and Documentation Addendum

Describes the installation process for a fix pack and provides updated information on problems and

workarounds associated with the fix pack. A new version of this document is created for each fix pack.

Documentation for the base agents

If you purchased IBM Tivoli Monitoring as a product, you received 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

Tivoli Management Services, you did not receive the base agents.

The following publications provide information about using the base agents.

v Windows OS Agent User’s Guide

v UNIX OS Agent User’s Guide

v Linux OS Agent User’s Guide

v i5/OS® Agent User’s Guide

v UNIX Log Agent User’s Guide

Related publications

You can find useful information about the OMEGAMON XE monitoring agent products in the IBM Tivoli

Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

Other sources of documentation

You can also obtain technical documentation about IBM Tivoli Monitoring and OMEGAMON XE products

from the following sources:

v IBM Tivoli Open Process Automation Library (OPAL)


OPAL is an online catalog that contains integration documentation as well as other downloadable

product extensions. This library is updated daily.





v Redbooks

http://www.redbooks.ibm.com/

IBM Redbooks®, Redpapers, and Redbooks Technotes provide information about products from platform

and solution perspectives.

v Technotes

You can find Technotes through the IBM Software Support Web site at http://www.ibm.com/software/support/probsub.html, or more directly through your product Web site, which contains a link to

Technotes (under Solve a problem).

Technotes provide the latest information about known product limitations and workarounds.

Appendix C. Documentation library 109

http://www.redbooks.ibm.com/



Appendix D. Notices

This information was developed for products and services offered in the U.S.A. IBM can not offer the

products, services, or features discussed in this document in other countries. Consult your local IBM

representative for information about the products and services currently available in your area. Any

reference to an IBM product, program, or service is not intended to state or imply that only that IBM

product, program, or service can be used. Any functionally equivalent product, program, or service that

does not infringe any IBM intellectual property right can be used instead. However, it is the user’s

responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM can 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 license

inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property

Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such

provisions 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 NOT

LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this

statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically

made to the information herein; these changes is incorporated in new editions of the publication. IBM can

make improvements or changes in the products or the programs described in this publication at any time

without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in

any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of

the materials for this IBM product and use of those Web sites is at your own risk.

IBM can use or distribute any of the information you supply in any way it believes appropriate without

incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the

exchange of information between independently created programs and other programs (including this one)

and (ii) the mutual use of the information that has been exchanged, should contact:


IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information can be available, subject to appropriate terms and conditions, including in some cases

payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by

IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any

equivalent agreement between us.

Trademarks

IBM, the IBM logo, AF/Remote, AIX, Candle, DB2, Hummingbird, i5/OS, OMEGAMON, OS/390, OS/400,

Passport Advantage, RS/6000, Tivoli, Tivoli Enterprise, Tivoli Enterprise Console, and z/OS are trademarks

or registered trademarks of International Business Machines Corporation in the United States, other

countries, or both.

Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or

trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer Entertainment, Inc., in the United

States, other countries, or both and is used under license therefrom.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun

Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the

United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel

SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its

subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Office of Government

Commerce, and is registered in the U.S. Patent and Trademark Office

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications

Agency which is now part of the Office of Government Commerce.

Other company, product, or service names may be trademarks or service marks of others.


Index

Special characters$ (dollar sign) filters

queries 52

Aaccessibility ix

acknowledging events vii

Add application support to the TEMS option 6

administrator exercises 55

advanced monitoring exercises 29

agentConfigured column 12

uninstalling 99

Agent Builderbuilding a custom monitoring agent 37

migration of complex resource models 97

Agent configuration option 6

agent exercise 65

agentsbased on the Tivoli Universal Agent 35

created by a script 35

installing additional 8

remote 8

Summarization and Pruning Agent 45

Warehouse Proxy Agent 45

AMK-REQUIRED-AMK 88

assess command for migration 90

assessing endpoints for migration 93

assessing profile managers for migration 94

assessing profiles for migration 93

assumptions in the basic migration exercise 73

audience targeted in this workbook viii

automatically responding to a situation event, using a

policy 29

automatically responding to a situation event, using a

Take Action command 29

automating manual tasks with policies 29

availability, continuous 56

Bbackup

hub monitoring server 56

baseline filevalidating the 89

basic migration of resource models 69

basic monitoring exercises 13

booksfeedback ix

online ix

ordering ix

see publications ix

browser client 13

building a custom monitoring agent using Agent

Builder 37

Ccategories of monitoring agents

base 9

for applications 9

for operating systems 9

non-base 9

change user /execute 59

change user /install 59

cleaning up after a migration 96

CLIexercises 33

combine multiple situations, exercise 24

command line interface 67

command-line interfaceexercises 33

commandsspecial characters xi

syntax xi

tacmd help 33

tacmd listSystems 33

tacmd login 33

common event connector 57

common event console 57

common event console view vii

components 1

Computers in addition to the single-computer

installation 3


option 6

configuration parametersDB2 Data Source for data warehousing 6

historical reports 6

portal server 3, 6

trace logging 27

Configure DB2 Data Source for Warehouse Proxy

option 6

Configure Using Defaults option for monitoring

agents 12

Configured column for the agent 12

configuring basic data collection for historical

reports 46

configuring Hot Standby 56

connector, common event 57

consoleversus portal 55

console eventsdisplaying in the portal 61

console, common event 57

conventionstypeface x

correlated situations 24

CPU usage, monitoring across several managed

systems 26

creating a query for an ODBC database 52

creating a situationtacmd commands 34

creating an ODBC data source 66


creating an test environment for migration 86

creating custom queries for historical reports 52

creating Initial Baseline File for migration 82

custom monitoring agentbuilding, using Agent Builder 37

custom views of the monitoring environmentcreating 21

customizing data collection for historical reports 47

Ddata

real-time versus historical 50

data collection for historical reportsconfiguring 46

customizing 47

data source configuration parameters - DB2 3

data warehousesetup 6

data, monitoringdatabase for 2

database connection, testing 47

Database for monitoring data 2

Databases Agentusing 65

DB2installation for IBM Tivoli Monitoring 2

TEPS Data Source configuration parameters 3

DB2 Agentusing 65

DB2 data source for the Warehouse Proxy 6

default situations 14

desktop client 13

diagnose problemsusing trace logs 27

directory names, notation x

displaying console events in the portal 61

displaying situation events in IBM Tivoli Enterprise

Console 60

documentationSee publications

Eeducation

see Tivoli technical training ix

embedded situations 24

embedded situations, exercise 24

enabling communications, IBM Tivoli Enterprise

Console 59

encryption keyinappropriate characters 4, 11

using during component installation 4, 11

window 4, 11

endpoint assessment filesmigrating 95

environment variables, notation x

environment, layout 3

event systemssupported in IBM Tivoli Monitoring 57

eventsfiltering and responding to 62

exercisesadvanced monitoring 29

basic monitoring 13

categories viii

combine multiple situations 24

for administrators 55

historical reporting 45

list viii

summary viii

trigger one event 24

using an agent 65

Expert Advice for situations 67

FFamiliarizing yourself with workspaces 14

filtering and responding to events 62

filters, $ (dollar sign) 52

forwarding events 60

functionalitynew vii

Ggraphical views

creating custom 21

Hheartbeat

Last heartbeat view 15

heartbeat and managed system statusviewing 55

help, tacmd commandtacmd help 33

hierarchy of the XML mapping file for migration 85

historical dataversus real-time data 50

historical report configurationdata warehouse 6

historical reportingcomponents 45

configuration parameters 6

configuring basic data collection 46

creating custom queries for 52

customizing data collection for 47

milestones 45

prerequisites 49

process 45

queries 52

query editor 52

stopping 51

viewing 49

historical reporting exercises 45

Hot Standbysetting up 56

hub monitoring serverConnection with the portal server 6

installing and configuring 3


hub monitoring server (continued)naming 60

purpose 55

Hub TEMS Configuration option 6

IIBM DB2 installation

overview 2

summary 2

IBM Tivoli Enterprise Consoledisplaying situation events 60

enabling communications 59

versus Tivoli Enterprise Portal 55

IBM Tivoli Enterprise Console integrationstandard approach 59

IBM Tivoli Monitoringinstalling and configuring 3

uninstalling 99

IBM Tivoli Monitoring for Databases: DB2 Agentusing 65

IBMTivoliMonitoringEncryptionKey 11

iconsEdit Properties icon 15

list 15

Maximize icon 15

Remove icon 15

Show View Bars 15

Split horizontally icon 15

Split vertically icon 15

TEPS 15

install.sh 9

installationadditional agents 8

additonal computers 3

IBM DB2 2

on Windows 3

single-computer, described 1

verifying 13

installation exectuable files 3, 9, 38

installation executable files 87

installation mode in Windows 59

installation optionsfirst-time 10

Modify 10

pristine 10

reinstallation 10

Remove 10

installation overview 1

installation scripts and executable files 9

installing the Migration Toolkit 76

integrating with IBM Tivoli Enterprise Consolenew approach 57

integration with IBM Tivoli Enterprise Consolestandard approach 59

IP Address, view 15

ITMUser 6, 47

Jjavapath command 73

Kkcjras1.log 28

key, encryption 11

keywordsmodifying configuration 67

KSYENVand historical reporting 46

KUMA_STARTUP_DPenvironment variable 35

KUMENVenvironment variable file 35

KUMENV environment variable file 35

Llaunching the portal 13

layout of environment 3

legal notices 111

librariesIBM Tivoli Monitoring 107

Linked workspaces 24

listSystems, tacmd commandtacmd listSystems 33

Locking Conflict workspace 68

logging onportal 13

logical view 21

login, tacmd commandtacmd login 33

Logon dialog box 13

logslocating 28

trace 27

viewing 28

MManage Situations 14

Manage Tivoli Monitoring Services 12

Manage Tivoli Monitoring Services utility 8

managed system status and heartbeatviewing 55

managing a situationtacmd commands 34

manualsfeedback ix

online ix

ordering ix

see publications ix

mapping of componentsfor migration 73

messages 27

metafile (*.MDL)Tivoli Universal Agent 35

metrics, using to create situations 24

migrate command for migration 90

migration 71

Agent Builder 97

assess command 90

assessing endpoints for 93

Index 115

migration (continued)assessing profile managersfor 94

assessing profiles for 93

assumptions 73

basic exercise 71

cleaning up after a 96

complex resource models 97

component mapping 73

conventions 71

creating an test environment for 86

creating Initial Baseline File 82

endpoint assessment files 95

hierarchy of the XML mapping file 85

installing the Migration Toolkit 76

javapath command 73

migrate command 90

names automatically assigned 75

node identification 75

optional resources 75

overview 73

password-related commands 73

post-migration activities 96

prerequisite resources 74

prerequisite software for 77

profile assessment files 95

profile manager assessment files 95

rolling back 96

sample v512 environment to migrate 103

scantmr command 73

supported operating systems for 77

topology view for 86

trace command 73

uninstalling the migration toolkit 97

validating the baseline file 89

verifying 96

winstall 78

winstall command 73

wuninst command 97

Migration Toolkit 69

valid scenarios 69

milestones for historical reporting 45

Modify option 10

monitoringbasic exercises 13

monitoring a processexercise 16

limitations of exercise 16

overview 16

query approach 16

situation approach 16

monitoring agentConfigured column 12

uninstalling 99

monitoring agent exercise 65

monitoring agents 1

base 9

based on the Tivoli Universal Agent 35

categories 9

Configure Using Defaults option for 12

created by a script 35

installing additional 8

monitoring agents (continued)non-base 9

Summarization and Pruning Agent 45


monitoring datadatabase for 2

monitoring exercisesadvanced 29

monitoring system conditions with situations 67

monitoring system conditions with workspaces 68

montioringNotepad 16

Nnames automatically assigned by the Migration

Toolkit 75

Navigator viewscreating custom 21

Netcool/OMNIbus 57

new functionality vii

New Policy tool 29

node identification in the migration process 75

notationenvironment variables x

path names x

typeface x

Notepad processmontioring 16

OODBC data source

creating 66


OMNIbus 57

online publicationsaccessing ix

OPAL documentation 108

optimizing CLI settings 67

optional agents 8

optional resources for migration 75

ordering publications ix

overview of IBM DB2 installation 2

overview of installation 1

overview of the Tivoli Enterprise Console view 61

Ppassword-related commands 73

path names, notation x

perform actions with policies 29

policiesusing to automatically respond to a situation

event 29

port 1920, portal browser client 13

portalbrowser client 13

desktop client 13

displaying console events in 61

launching 13


portal (continued)versus console 55

portal serverconfiguration parameters 6

configuration parameters for the 3

Connection to a hub monitoring server 6

Warehouse ID and Password 6

portal server database ID 6

post-migration activities 96

prerequisite resources for migration 74

prerequisite software for migration 77

problem determinationusing trace logs 27

processesmonitoring 16

profile assessment filesmigrating 95

profile manager assessment filesmigrating 95

profile managersassessing for migration 94

profilesassessing for migration 93

publicationsaccessing online ix

feedback ix

online ix

OPAL 108

ordering ix

Redbooks 109

related 108

Technotes 109

types 107

Qqueries

$ (dollar sign) filters 52

for a monitoring server 52

for an ODBC database 52

for historical reports 52

query editor 52

used to monitro a process 16

query for an ODBC database 52

RRAS1 logs 28

real-time dataversus historical data 50

Redbooks 109

remote agents 8

Remove option 10

reports, See historical reporting 49

resource modelsbasic migration of 69

customized migration 69

responding to events 62

rolling back migration 96

rule base command 59

rulebases 59

Ssample v512 environment to migrate 103

scantmr command 73

scenariosMigration Toolkit 69

scheduling work with policies 29

Select the application support to add to the TEMS

option 6

Selecting a Warehouse Proxy Agent database 6

Self-Monitoring Topology 15

setting up Hot Standby 56

setup.exe 3, 9, 38, 87

setupwin32.exe 59

severity statuses 63

single-computer installationadditional computers 3

described 1

steps 3

situation eventsautomatically responding 29

displaying in IBM Tivoli Enterprise Console 60

situation, defined 13

situationscorrelated 24

embedded 24

severities vii

used to monitor a process 19

using to monitor system conditions 67

starting an agenttacmd command 35

starting the DB2 Agent 65

stopping an agenttacmd command 35

stopping historical reporting 51

stopping the DB2 Agent 65

summary of exercises viii

summary of IBM DB2 installation 2

supported operating systems for migration 77

sysadmin permission 47

system conditions, monitoringusing situations 67

using workspaces 68

System Overview workspace 68

Ttacmd shell 33

Take Action commandsusing to automatically respond to a situation

event 29

Technotes 109

template agent 12

Tivoli Enterprise Consoledisplaying situation events 60

enabling communications 59

integration supported in IBM Tivoli Monitoring 59

versus Tivoli Enterprise Portal 55

Tivoli Enterprise Console view 61

overview 61

Tivoli Enterprise Monitoring Agent, see agents 8

Index 117

Tivoli Enterprise Monitoring Server Configuration

option 6

Tivoli Enterprise Portalbrowser client 13

common event connector view 57

desktop client 13, 14

launching 13

Tivoli Management Framework for migration 103

Tivoli management region for migration 103

Tivoli Netcool/OMNIbus 57

Tivoli software information center ix

Tivoli technical training ix

Tivoli Universal Agentcreated by a script 35

creating agents based on the 35

KUMA_STARTUP_DP environment variable 36

KUMENV environment variable file 36

metafile (*.MDL) 35

TMS Infrastructure 15

toolbarsEdit Properties icon 15

icons in workspaces 14

list 15

Maximize icon 15

Remove icon 15

Show View Bars 15

Split horizontally icon 15

Split vertically icon 15

toolkit for migration 69

topology view vii

Topology view 15

topology view for migration 86

trace and logging information 27

trace command 73

trace logslocating 28

options 27

problem determination 27

using 27

viewing 28

trademarks 112

training, Tivoli technical ix

trigger one event, exercise 24

typeface conventions x

UUDB_DB_SQL_Fail_High situation 67

UDB_Status_Warning situation 67

uninstallinga monitoring agent 99

event synchronization 99

IBM Tivoli Enterprise Console event

synchronization 99

IBM Tivoli Monitoring 99

IBM Tivoli Monitoring entirely 99

ODBC data source connection removal 99

Tivoli Enterprise Console event synchronization 99


uninstalling IBM Tivoli Monitoring 99

uninstalling the migration toolkit 97

Universal Agentcreated by a script 35

creating agents based on the 35

metafile (*.MDL) 35

URL monitorcreated by a script 35

using IBM Tivoli Monitoring for Databases: DB2

Agent 65

using situations to monitor system conditions 67

using workspaces to monitor system conditions 68

Vv512 sample environment to migrate 103

valid scenarios for the Migration Toolkit 69

validating the baseline file for migration 89

variables, notation for x

verifyinginstallation 13

situations 14

verifying migration 96

viewingmanaged system status and heartbeat 55

viewing historical reports 49

viewing managed system status and heartbeat 55

viewscommon event console 57

creating custom graphical 21

creating custom Navigators 21

IP Address 15

Last heartbeat 15

Tivoli Enterprise Console view 61

Topology 15

workspace linking vii

WWarehouse ID and Password for portal server 6

Warehouse ProxyDB2 data source for the 6


ODBC data source 6

Warehouse Proxy Database Selection option 6

who should use this workbook viii

Windowsinstallation mode 59

single-computer installation 3

winstall command 73

winstall for migration 78

witmmtk commands, See migration. 90

wizard, installation 3, 9

work, scheduling with policies 29

working in the CLI (command-line interface) 33

workspace improvements vii

workspace linking vii

workspace viewscommon event console vii

topology vii

workspacesexercie 14

icons in toolbar 14


workspaces (continued)linking 24

overview 14

typical 14

using to monitor system conditions 68

wrb, rule base command 59

wuninst command 97

Index 119

��

Printed in USA

SC32-1803-01