Tivoli IBM Tivoli Monitoring


Version 6.1.0

Exploring IBM Tivoli Monitoring

SC32-1803-00
 Tivoli IBM Tivoli Monitoring
®


Version 6.1.0

Exploring IBM Tivoli Monitoring

SC32-1803-00
First Edition (November 2005)
This edition applies to version 6, release 1 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. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . v Validating the workflow logic and saving the
policy . . . . . . . . . . . . . . . 52
Tables . . . . . . . . . . . . . . . vii Starting the policy . . . . . . . . . . . 52
Exercise 6: Launching an application . . . . . . 53
Launch application . . . . . . . . . . . 53
About this guide . . . . . . . . . . . ix Take action . . . . . . . . . . . . . 53
Who should use this workbook . . . . . . . . ix Exercise 7: Using historical data . . . . . . . 55
Publications . . . . . . . . . . . . . . ix Historical reporting, setting a time span . . . . 55
IBM Tivoli Monitoring library . . . . . . . ix Creating a monitoring server query . . . . . 56
Accessing terminology online . . . . . . . xi Exporting query results . . . . . . . . . 58
Accessing publications online . . . . . . . xi Exercise 8: Creating a graphical view and using the
Ordering publications . . . . . . . . . . xi business navigator . . . . . . . . . . . . 59
Accessibility . . . . . . . . . . . . . . xii Creating a graphic view . . . . . . . . . 59
Tivoli technical training . . . . . . . . . . xii Creating a Business Navigator view . . . . . 60
Support information . . . . . . . . . . . xii
Conventions used in this guide . . . . . . . . xii
Chapter 4. Product administration . . . 63
Typeface conventions . . . . . . . . . . xii
Exercise 9: Configuring the Summarization and
Tivoli command syntax . . . . . . . . . xiii
Pruning Agent . . . . . . . . . . . . . 63
Changing system-wide configuration settings
Chapter 1. Introduction . . . . . . . . 1 using the Manage Tivoli Enterprise Services
window . . . . . . . . . . . . . . 63
Chapter 2. Installation and basic Changing the default configuration settings for
monitoring . . . . . . . . . . . . . 3 selected products and attribute groups . . . . 65
Exercise 1: Installing IBM Tivoli Monitoring . . . . 3 How to disable the Summarization and Pruning
Determining the layout of your environment . . 4 Agent . . . . . . . . . . . . . . . 66
Preinstallation configuration . . . . . . . . 5 Exercise 10: Viewing managed system status and
Installing and configuring the hub Tivoli testing the heartbeat . . . . . . . . . . . 66
Enterprise Monitoring Server . . . . . . . . 7 Viewing managed system status . . . . . . 67
Installing the Tivoli Enterprise Portal server . . 22 Testing the heartbeat . . . . . . . . . . 67
Installing Tivoli Enterprise Monitoring Agents . . 26 Exercise 11: Using the CLI . . . . . . . . . 68
Installing Tivoli Enterprise Portal desktop client 30 Creating and managing a situation . . . . . 68
Installing support for agents on the monitoring Starting and stopping an agent . . . . . . . 69
server, portal server, and browser and desktop Viewing what your monitoring server is
clients . . . . . . . . . . . . . . . 33 monitoring . . . . . . . . . . . . . 69
Starting the Tivoli Enterprise Portal client . . . 36 Exercise 12: IBM Tivoli Enterprise Console
Exercise 2: Verifying and configuring your integration . . . . . . . . . . . . . . . 70
installation . . . . . . . . . . . . . . 37 Installing the IBM Tivoli Enterprise Console
Verifying your installation . . . . . . . . 37 event synchronization . . . . . . . . . . 70
Configuring history collection . . . . . . . 39 Configuring your monitoring server to forward
Exercise 3: Creating and using situations . . . . 43 events . . . . . . . . . . . . . . . 72
Creating a situation . . . . . . . . . . . 43 Configuring a Tivoli Enterprise Console view . . 73
Editing a situation . . . . . . . . . . . 44 What the view shows . . . . . . . . . . 73
Managing events . . . . . . . . . . . 45 Saving the Tivoli Enterprise Console view . . . 75
Exercise 4: Creating new views for the Tivoli Exercise 13: Filtering and responding to events . . 76
Enterprise Portal. . . . . . . . . . . . . 48 Opening the Enterprise TEC workspace . . . . 76
Creating a view . . . . . . . . . . . . 48 Acknowledging an event . . . . . . . . . 76
Defining a workspace . . . . . . . . . . 48 Filtering events . . . . . . . . . . . . 76
Editing a workspace . . . . . . . . . . 49 Closing an event. . . . . . . . . . . . 77
Creating ranges and sub-ranges on linear and
circular gauge views . . . . . . . . . . 49 Chapter 5. Advanced features . . . . . 79
Exercise 14: Performing an upgrade from Tivoli
Chapter 3. Basic product function . . . 51 Distributed Monitoring . . . . . . . . . . 79
Exercise 5: Creating a policy . . . . . . . . . 51 Software requirements for the test scenario . . . 79
Adding a new policy . . . . . . . . . . 51 Information to gather before you begin . . . . 80
Adding and connecting activities . . . . . . 51 Overview of test scenario steps . . . . . . . 81

© Copyright IBM Corp. 2005 iii

 Conventions used in these instructions . . . . 81 Dynamically refreshing the monitoring agent 109
Installing the upgrade toolkit . . . . . . . 82 Sending a refresh signal to the monitoring agent
Creating managed resources for the test scenario 83 on AIX . . . . . . . . . . . . . . 110
Creating an infrastructure road map: baseline file 84 Generic user log support . . . . . . . . 110
Installing the IBM Tivoli Monitoring servers and Monitoring system conditions using situations 127
updating status . . . . . . . . . . . . 89 Monitoring system conditions using workspaces 127
Upgrading endpoints . . . . . . . . . . 90 Exercise 22: Using IBM Tivoli Monitoring: IBM
Upgrading profiles and profile managers . . . 91 Tivoli Monitoring 5.x Endpoint Agent . . . . . 128
Completing the test scenario . . . . . . . . 95 Install the IBM Tivoli Monitoring: IBM Tivoli
Exercise 15: Creating embedded situations . . . . 96 Monitoring 5.x Endpoint Agent . . . . . . 129
Exercise 16: Configuring Hot Standby . . . . . 97 Configuring and distributing the IBM Tivoli
Installing the backup monitoring server . . . . 98 Monitoring: IBM Tivoli Monitoring 5.x Endpoint
Configuring Hot Standby on monitoring servers 98 Agent . . . . . . . . . . . . . . . 130
Configuring agents . . . . . . . . . . . 98 Monitoring system conditions using workspaces 131
Verifying that Hot Standby is working . . . . 99
Exercise 17: Creating a custom monitor from a script 99 Appendix A. Hardware and software
Step 1: Select the data provider . . . . . . . 99 requirements . . . . . . . . . . . 133
Step 2: Create the monitoring application script 100
Supported operating systems . . . . . . . . 133
Step 3: Import the metafile . . . . . . . . 100
Required hardware . . . . . . . . . . . 135
Step 4: View the data in the Tivoli Enterprise
Required software . . . . . . . . . . . . 136
Portal . . . . . . . . . . . . . . . 100
Exercise 18: Monitoring a URL . . . . . . . 101
Step 1: Configuring and starting the Universal Appendix B. Uninstalling IBM Tivoli
Agent . . . . . . . . . . . . . . . 101 Monitoring . . . . . . . . . . . . 139
Step 2: Monitoring a URL . . . . . . . . 102 Uninstalling the entire IBM Tivoli Monitoring
Exercise 19: Reviewing the problem determination environment . . . . . . . . . . . . . . 139
information . . . . . . . . . . . . . . 102 Uninstalling on the environment Windows . . 139
Uninstalling the environment on Linux or UNIX 142
Chapter 6. Working with agents . . . 103 Uninstalling an individual IBM Tivoli Monitoring
Exercise 20: Using IBM Tivoli Monitoring for agent or component . . . . . . . . . . . 142
Databases: DB2 Agent . . . . . . . . . . 103 Uninstalling a component on Windows . . . . 142
Installation options for the monitoring agent 103 Uninstalling a component on Linux or UNIX 143
Monitoring agent application support . . . . 103 Uninstalling the Warehouse Proxy . . . . . 143
Starting and stopping the IBM Tivoli Monitoring Uninstalling the IBM Tivoli Monitoring 5.x
for Databases: DB2 Agent on Linux or UNIX endpoint agent from the Tivoli management region 144
operating systems . . . . . . . . . . . 103 Uninstalling the IBM Tivoli Enterprise Console
Creating an ODBC data source . . . . . . 104 event synchronization . . . . . . . . . . 144
Using situations to monitor system conditions 105
Using workspaces to monitor system conditions 106 Appendix C. Notices . . . . . . . . 145
Exercise 21: Using IBM Tivoli Monitoring: UNIX Trademarks . . . . . . . . . . . . . . 146
Log Agent . . . . . . . . . . . . . . 106
Specifying the log files to monitor . . . . . 106 Index . . . . . . . . . . . . . . . 147
Environment variables for IBM Tivoli
Monitoring: UNIX Log Agent . . . . . . . 108

iv IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figures
1. Installation welcome window . . . . . . . 8 17. Installing agent support . . . . . . . . 34
2. Software license agreement window . . . . . 9 18. Logging into the Tivoli Enterprise Portal 38
3. Prerequisite software window . . . . . . 10 19. Managing default situations . . . . . . . 39
4. Installation location window . . . . . . . 11 20. Example linear gauge for memory allocation 50
5. Data encryption key window . . . . . . 12 21. Tivoli Enterprise Console view . . . . . . 75
6. Component selection window . . . . . . 13 22. Unedited sample baseline file (baseline.xml) 85
7. Agent deployment window . . . . . . . 14 23. Edited baseline file (baseline.xml) . . . . . 88
8. Program folder name window . . . . . . 15 24. Output file from the Scan tool, showing
9. Post-installation configuration window 16 current status of the infrastructure upgrade . . 90
10. Hub monitoring server configuration . . . . 17 25. Output file (DM_TEST_PROF.xml) from
11. Hub monitoring server communication running the Assess tool against the
protocols . . . . . . . . . . . . . 17 DM_TEST_PROF profile . . . . . . . . 93
12. Default communications protocol for all 26. Example format diagram . . . . . . . . 112
components . . . . . . . . . . . . 18 27. Uninstalling IBM Tivoli Monitoring . . . . 139
13. Completing the installation . . . . . . . 19 28. Confirming the uninstallation . . . . . . 140
14. Installing a new component on a computer 29. Stopping Tivoli components before
with an existing IBM Tivoli Monitoring uninstallation . . . . . . . . . . . 140
component . . . . . . . . . . . . . 22 30. Removing the portal database . . . . . . 140
15. Installing a new component on a computer 31. DB2 database information . . . . . . . 140
with an existing IBM Tivoli Monitoring 32. Uninstallation progress window . . . . . 141
component . . . . . . . . . . . . . 27 33. GSKit uninstallation . . . . . . . . . 141
16. Installing a new component on a computer 34. Successful uninstallation . . . . . . . . 141
with an existing IBM Tivoli Monitoring
component . . . . . . . . . . . . . 31

© Copyright IBM Corp. 2005 v

vi IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
Tables
1. IBM Tivoli Monitoring high-level installation 16. Placeholder information for Tivoli
steps . . . . . . . . . . . . . . . 3 infrastructure components used in the test
2. Windows-based test environment . . . . . 4 scenario . . . . . . . . . . . . . . 87
3. UNIX-based test environment . . . . . . . 5 17. Placeholder information for IBM Tivoli
4. Linux-based test environment . . . . . . . 5 Monitoring infrastructure components used in
5. Installing a monitoring server on a UNIX the test scenario . . . . . . . . . . . 87
computer . . . . . . . . . . . . . 19 18. File format for customer configuration of
6. Installing a portal server on a Linux computer 24 UNIX Log Agent . . . . . . . . . . 107
7. Installing a monitoring agent on UNIX 28 19. UNIX Log Agent environment variables 108
8. Installing the portal client on Linux . . . . 32 20. Valid alphanumeric data types . . . . . . 115
9. IBM Tivoli Enterprise Console integration 70 21. Valid column names and minimum
10. What you need for the test scenario . . . . 79 abbreviations . . . . . . . . . . . . 118
11. Information to gather about Tivoli 22. Log Entries table view mapping options 120
infrastructure components to use for the test 23. Integer family data types . . . . . . . 123
scenario . . . . . . . . . . . . . . 80 24. Floating point family data types . . . . . 123
12. Information to gather about the IBM Tivoli 25. Escape character sequence . . . . . . . 124
Monitoring infrastructure components to use 26. Installation and configuration procedures 128
for the test scenario . . . . . . . . . . 80 27. Supported operating systems . . . . . . 133
13. Overview of steps for the test scenario . . . 81 28. Hardware requirements for IBM Tivoli
14. Long and short names of components . . . . 81 Monitoring components . . . . . . . . 135
15. Managed resource configurations used in the 29. Required software for IBM Tivoli Monitoring 136
test scenario . . . . . . . . . . . . 83

© Copyright IBM Corp. 2005 vii

viii IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
About this guide
The series of exercises in this workbook can help you maximize your investment in
the IBM® Tivoli® Monitoring product. After completing the workbook exercises,
you will have installed and configured your environment, explored the graphical
and command line interfaces of the product, used several of the new features in
this release of IBM Tivoli Monitoring (such as creating a monitor based on a
custom script), and worked with several monitoring agents.

This workbook describes the following topics and gives you hands-on experience
with the following tasks:
v Installing IBM Tivoli Monitoring, verifying the installation, and configuring
history collection
v Managing history data collection and the Tivoli Data Warehouse
v Creating and using situations for notification of system conditions
v Creating and editing new views for the Tivoli Enterprise Portal
v Creating policies to perform actions, schedule work, or automate manual tasks
on managed systems in your enterprise
v Configuring and managing the Summarization and Pruning Agent to generate,
store, and prune data that is based on historical records of activity and
conditions in your enterprise
v Using historical reporting and the Business Navigator
v Viewing managed system status and testing the heartbeat
v Synchronizing events between Tivoli Enterprise Portal and the IBM Tivoli
Enterprise Console, and filtering and responding to events
v Performing a test scenario to upgrade from Tivoli Distributed Monitoring
v Exploring the capabilities of agents to monitor system conditions

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

Publications
This section lists publications in the IBM Tivoli Monitoring library. It also describes
how to access Tivoli publications online and how to order Tivoli publications.

IBM Tivoli Monitoring library

The following documents provide information about the IBM Tivoli Monitoring
product:
v Introducing IBM Tivoli Monitoring, GI11-4071

© Copyright IBM Corp. 2005 ix

 Introduces the components of IBM Tivoli Monitoring and also compares
concepts and function of IBM Tivoli Monitoring to Tivoli Distributed
Monitoring.
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring, GC32-9462
Provides information about upgrading from Tivoli Distributed Monitoring.
v IBM Tivoli Monitoring Installation and Setup Guide, GC32-9407
Provides information about installing and setting up IBM Tivoli Monitoring and
upgrading from OMEGAMON® V350 or V360.
v IBM Tivoli Monitoring User’s Guide, SC32-9409
Complements the Tivoli Enterprise™ Portal online help. The guide provides
hands-on lessons and detailed instructions for all Tivoli Enterprise Portal
features.
v IBM Tivoli Monitoring Administrator’s Guide, SC32-9408
Describes the support tasks and functions required for the Tivoli Enterprise
Portal Server and clients, including Tivoli Enterprise Portal user administration.
v IBM Tivoli Monitoring Services on z/OS® Program Directory
Provides installation information for installing a Tivoli Enterprise Monitoring
Server on a z/OS system.
v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS, SC32-9463
Describes how to configure and customize the Tivoli Enterprise Monitoring
Server running on a z/OS system.
v IBM Tivoli Monitoring Problem Determination Guide, GC32-9458
Provides information and messages to assist users with troubleshooting
problems with the software.
v Exploring IBM Tivoli Monitoring, SC32-1803
Provides a series of exercises that help users explore IBM Tivoli Monitoring.
After completing the activities in this workbook, you will have installed and
configured your environment, explored both the graphical and command-line
interfaces of the product, used several of the new features in this release of IBM
Tivoli Monitoring (such as creating a monitor based on a custom script), and
worked with several monitoring agents.
v IBM Tivoli Universal Agent User’s Guide, SC32-9459
Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli
Monitoring. The IBM 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,
SC32-9461
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 IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint Agent User’s Guide
The IBM Tivoli Monitoring 5.x Endpoint Agent extends the capabilities of IBM
Tivoli Monitoring V5.1.2. It enables data collected by deployed IBM Tivoli
Monitoring V5.1.2 endpoints to be displayed in the Tivoli Enterprise Portal and
stored in Tivoli Data Warehouse.

x IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Accessing terminology online
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. TheTivoli 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/ibm/terminology

Accessing publications online

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by going first to the Tivoli
software library at the following Web address:

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

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window so that Adobe Reader can print letter-sized pages
on your local paper.

The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:

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

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

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

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.

About this guide xi

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/

Support information
For information about obtaining support, see the Support Appendix in the user’s
guide for this product.

Conventions used in this guide

This guide uses several conventions for special terms and actions.

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,
multicolumn 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

xii IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Tivoli command syntax
The following special characters define Tivoli command syntax:
[] Identifies elements that are optional. Required elements do not have
brackets around them.
... 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.
{} Delimits a set of mutually exclusive elements when a command requires
one of them. Brackets ([ ]) are around elements that are optional.

In addition to the special characters, Tivoli command syntax uses the typeface
conventions described in “Typeface conventions” on page xii. 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 guide xiii

xiv IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
Chapter 1. Introduction
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 installed and configured your environment, explored graphical and command
line interfaces of the product, used several of the new features in this release of
IBM Tivoli Monitoring (such as creating a monitor that is based on a custom
script), and worked with several monitoring agents.

The workbook is divided into the following sections:

v Chapter 2, “Installation and basic monitoring,” on page 3
v Chapter 3, “Basic product function,” on page 51
v Chapter 4, “Product administration,” on page 63
v Chapter 5, “Advanced features,” on page 79
v Chapter 6, “Working with agents,” on page 103

© Copyright IBM Corp. 2005 1

2 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
Chapter 2. Installation and basic monitoring
Perform the following exercises to install your test environment and begin basic
monitoring:
1. “Exercise 1: Installing IBM Tivoli Monitoring”
2. “Exercise 2: Verifying and configuring your installation” on page 37
3. “Exercise 3: Creating and using situations” on page 43
4. “Exercise 4: Creating new views for the Tivoli Enterprise Portal” on page 48

Exercise 1: Installing IBM Tivoli Monitoring

The following sections provide detailed steps for installing IBM Tivoli Monitoring
in your environment. Table 1 shows the steps for installation and initial
configuration of your environment:
Table 1. IBM Tivoli Monitoring high-level installation steps
Steps Where to find information
Determine the layout of your test “Determining the layout of your
environment. environment” on page 4
Ensure that your computers meet the Appendix A, “Hardware and software
product requirements. requirements,” on page 133
Install DB2® for use by the Tivoli Enterprise See the DB2 information center for detailed
Portal Server. installation instructions. Usually, you can
accept the default installation values.
Perform preinstallation steps required for “Preinstallation configuration” on page 5
warehouse support.
Install a hub Tivoli Enterprise Monitoring “Installing and configuring the hub Tivoli
Server. Enterprise Monitoring Server” on page 7
Install the Tivoli Enterprise Portal Server. “Installing the Tivoli Enterprise Portal
server” on page 22
Install any Tivoli Enterprise Monitoring “Installing Tivoli Enterprise Monitoring
Agents. Agents” on page 26
Configure any agents, as required. “Exercise 20: Using IBM Tivoli Monitoring
for Databases: DB2 Agent” on page 103

“Exercise 21: Using IBM Tivoli Monitoring:

UNIX Log Agent” on page 106
Install required support for non-operating “Installing support for agents on the
system agents on the monitoring server, monitoring server, portal server, and
portal server, and portal desktop client. browser and desktop clients” on page 33
Install the portal desktop client (optional). “Installing Tivoli Enterprise Portal desktop
client” on page 30
Start the Tivoli Enterprise Portal to verify “Starting the Tivoli Enterprise Portal client”
your installation. on page 36
Install IBM Tivoli Enterprise Console event “Installing the IBM Tivoli Enterprise Console
synchronization on your event server. event synchronization” on page 70

© Copyright IBM Corp. 2005 3

 Determining the layout of your environment
The installation procedures in this exercise provide Windows® and UNIX®
procedures for installing the various components. Use the procedure that is better
for your environment layout.

Note: The Warehouse Proxy, which is used for historical data collection, is
supported only on Windows computers.

The installation procedures in the following sections provide information for

installing a single component such as the monitoring server on one computer. If
you want to install multiple components such as the monitoring server and the
portal server on the same computer, as described in the following environment
scenarios, and you want to install them simultaneously, the actual steps might vary
from the following procedures. Refer to the individual sections for required
configuration information during your installation.

The following sections provide suggested layouts for your environment, based on
the type of monitoring server that you plan to use or the required environment for
a specific exercise.
v “Windows monitoring server environment”
v “UNIX (non-Linux) monitoring server environment”
v “Linux monitoring server environment” on page 5
v “Tivoli Distributed Monitoring upgrade environment” on page 5

Windows monitoring server environment

If you plan to install the hub monitoring server and portal server on a Windows
computer, you might also want to install a Windows operating system agent on a
separate Windows computer and a UNIX operating system agent on a UNIX
computer to communicate with the monitoring server. Table 2 shows how your
environment would look in this scenario:
Table 2. Windows-based test environment
Computer 1 (Windows) Computer 2 (Windows) Computer 3 (UNIX)
Tivoli Enterprise Monitoring Windows operating system UNIX or Linux® operating
Server agent system agent

Tivoli Enterprise Portal Tivoli Enterprise Portal (Linux only) Tivoli Enterprise
server desktop client Portal desktop client

Tivoli Enterprise Portal

desktop client

Windows operating system

agent

Warehouse Proxy

Warehouse Summarization
and Pruning Agent

UNIX (non-Linux) monitoring server environment

If you plan to install the hub monitoring server on a UNIX (non-Linux) computer,
you must install the Tivoli Enterprise Portal on a Windows or Linux computer. You
might also want to install a separate UNIX operating system agent on a UNIX
computer to communicate with the monitoring server. Table 3 on page 5 shows
how your environment would look in this scenario:
4 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
 Table 3. UNIX-based test environment
Computer 2 (Windows or
Computer 1 (UNIX) Linux) Computer 3 (UNIX)
Tivoli Enterprise Monitoring Tivoli Enterprise Portal UNIX or Linux operating
Server server system agent

UNIX or Linux operating Tivoli Enterprise Portal (Linux only) Tivoli Enterprise
system agent desktop client Portal desktop client

Warehouse Summarization Windows or Linux operating

and Pruning agent system agent

(Windows only) Warehouse

Proxy

Linux monitoring server environment

If you are installing the hub monitoring server on a Linux computer, you can
install the portal server on the same system. You might also want to install a
separate Windows or UNIX operating system agent on a Windows or UNIX
computer to communicate with the monitoring server. Table 4 shows how your
environment would look in this scenario:
Table 4. Linux-based test environment
Computer 2 (Windows or
Computer 1 (Linux) Linux) Computer 3 (UNIX)
Tivoli Enterprise Monitoring Windows or Linux operating UNIX or Linux operating
Server system agent system agent

Tivoli Enterprise Portal Tivoli Enterprise Portal (Linux only) Tivoli Enterprise
server desktop client Portal desktop client

Tivoli Enterprise Portal (Windows only) Warehouse

desktop client Proxy

Linux operating system

agent

Warehouse Summarization
and Pruning agent

Tivoli Distributed Monitoring upgrade environment

If you plan to test the upgrade from Distributed Monitoring to IBM Tivoli
Monitoring, install a monitoring server and portal server on one Windows
computer. Accept all defaults during the installation. For more information about
the upgrade scenario, see “Exercise 14: Performing an upgrade from Tivoli
Distributed Monitoring” on page 79.

Preinstallation configuration
The following steps are required for data warehousing:
v “Create a Windows user” on page 6
v “Create a database for the Warehouse Proxy” on page 6
v “Setting up the ODBC connection” on page 6

Note: These instructions assume that you installed DB2 for data warehousing on
the computer where you plan to install the Warehouse Proxy.

Chapter 2. Installation and basic monitoring 5

 Create a Windows user
Use the following steps to create a Windows user:
1. Open the Computer Management window.
2. In the navigation pane of the Computer Management window, expand Local
Users and Groups by clicking on the plus sign (+).
3. Right-click the Users folder and click New User.
4. Type ITMUser in the User Name field.
5. Type marath0n in the Password field. Type the password again in the Confirm
password field to confirm it.

Note: “marath0n” is case-sensitive and must be typed exactly as shown.

6. Clear User must change password at next logon.
7. Click Create to create the user.
8. Click Close to close the window.
9. Click the Groups folder.
10. Double-click DB2ADMNS in the right pane of the window.
11. Do the following step if you are using Windows 2003:
a. Click Add.
b. Type ITMUser in the Enter the names to select (examples) field and click
Check Names.
c. Click OK and then click OK again.
12. Do the following step if you are using Windows 2000:
a. Click Add in the Administrator Properties window.
b. Locate ITMUser, the new user you created, and select it.
c. Click Add.
13. Click OK successively twice to close the Administrator Properties window.
14. Close the Computer Management window.

Create a database for the Warehouse Proxy

Use the following procedure to create a database for the Warehouse Proxy. Before
you begin, consider the following information:
v These steps use IBM DB2 as an example. If you are using a different database,
see the documentation for that information.
v This procedure is optional if you are using DB2. You can create a DB2 database
during the configuration of the Warehouse Proxy. This procedure is required if
you are using any other database.
1. Click Start → Programs → IBM DB2 → Command Line Tools → Command
Window.
For Windows 2003, click Start → All Programs → IBM DB2 → Command Line
Tools → Command Window
2. Run the following command:
db2 create database warehous using codeset utf-8 territory US
3. Close the command window after the command runs.

Setting up the ODBC connection

Use the following steps to set up an ODBC connection.

6 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Note: This procedure is optional if you are using DB2. You can set up the DB2
ODBC connection during the configuration of the Warehouse Proxy. This
procedure is required if you are using any other database.
1. Click Start → Settings or Start → Control Panel on Windows 2003.
2. Click Administrative Tools → Data Sources (ODBC).
3. Click Add in the System DSN tab in the ODBC Data Source Administrator
window.
4. Select IBM DB2 ODBC DRIVER from the list.
5. Click Finish.
6. In the ODBC DB2 Driver - Add window
a. Enter ITM Warehouse in Data source name.
b. Enter warehous in Database Alias.
c. Click OK.
7. Test the ODBC database connection before continuing:
a. In the ODBC Data Source Administrator window, select ITM Warehouse.
b. Click Configure.
c. In the CLI/ODBC Settings - ITM Warehouse window, the data source name,
ITM Warehouse, is displayed.
d. Enter ITMUser for the User ID.
e. Enter marath0n for the Password.
f. Click Connect.
g. A Connection tested successfully message is displayed.
h. Click OK twice to close the window.
If you have problems, see the documentation for your DB2 database software.

Installing and configuring the hub Tivoli Enterprise Monitoring

Server
The following sections provide detailed information for installing and initially
configuring the hub monitoring server:
v “Windows: Installing the monitoring server”
v “Linux or UNIX: Installing a monitoring server” on page 19

Windows: Installing the monitoring server

Use the following steps to install the hub monitoring server on a Windows
computer:
1. Double-click the setup.exe file on the installation media to launch the
installation wizard.

Note: If you are running Windows 2003 or Windows XP and have security set
to check the software publisher of applications, you might receive an
error message that the setup.exe file is from an unknown publisher.
Click Run to disregard this error message.
A welcome window (Figure 1 on page 8) is displayed:

Chapter 2. Installation and basic monitoring 7

 Figure 1. Installation welcome window

2. Click Next on the welcome window.

8 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 2. Software license agreement window

3. Click Accept (Figure 2) to accept the license agreement.

Chapter 2. Installation and basic monitoring 9

 Figure 3. Prerequisite software window

Note: If your computer meets all prerequisites, this window (Figure 3) is not
displayed.
4. If you do not have a DB2 or MS SQL database installed on this computer, a
message regarding potentially missing software is displayed (Figure 3).
Because you do not need a database to use this computer as a monitoring
server, you can click Next and ignore the message.

10 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 4. Installation location window

5. Choose the directory where you want to install the product (Figure 4). The
default directory is C:\IBM\ITM. Click Next.

Chapter 2. Installation and basic monitoring 11

 Figure 5. Data encryption key window

6. Type a 32-bit encryption key (Figure 5). You can use the default key.
Notes:
a. Do not use any of the following characters in your key:
v Equal sign (=)
v Apostrophe (’)
v Pipe key, also known as the bar key or vertical bar (|)
b. Ensure that you document the value that you use for the key. Use this key
during the installation of any components that communicate with this
monitoring server.
Click Next and then click OK to confirm the encryption key.

12 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 6. Component selection window

7. Select Tivoli Enterprise Monitoring Server (Figure 6).

8. Click Next.

Chapter 2. Installation and basic monitoring 13

 Figure 7. Agent deployment window

9. In this window (Figure 7), if you want to do remote deployment of agent

software, select those agents that you want to deploy. This step creates and
populates the deployment depot, from which you can deploy agents at a later
time (as described in the IBM Tivoli Monitoring Installation and Setup Guide).
Click Next.

14 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 8. Program folder name window

10. Select a program folder (Figure 8) and click Next. The default program folder
name is IBM Tivoli Monitoring.
11. Review the installation summary details. This summary identifies what you
are installing and where you chose to install it. Click Next to begin the
installation of components.
After the components are installed, a configuration window (Figure 9 on page
16) is displayed.

Chapter 2. Installation and basic monitoring 15

 Note: This window (Figure 9) might differ from the window that you see, depending on the
components you chose to install on this computer.

Figure 9. Post-installation configuration window

12. Click Next.

16 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 10. Hub monitoring server configuration

13. Click OK on this window (Figure 10) to accept the default values.

Figure 11. Hub monitoring server communication protocols

14. Click OK on this window (Figure 11) to accept the default values for the
communications protocol for the monitoring server. The next configuration
step adds application support to the monitoring server.
15. Specify the location of the monitoring server. You have two choices:
v On this computer
v On a different computer

Chapter 2. Installation and basic monitoring 17

 Click OK.
16. Because the monitoring server is not currently running, it is started
automatically before the application support is added. Click OK on the
message telling you this information.
17. Select the data that you want to add to the monitoring server. By default, all
available product data is selected. Click OK.
18. Click Next on the message that provides information about the process. The
next configuration step configures the default communication between any
IBM Tivoli Monitoring component and the hub monitoring server.
19. Click OK to accept the default values for the connection between all
components and the hub monitoring server.
A window (Figure 12) is displayed.

Figure 12. Default communications protocol for all components

20. Click OK to accept the default values for the communications protocol for the
monitoring server.
Now you can complete the installation (Figure 13 on page 19).

18 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 13. Completing the installation

21. Clear the check box next to Display the README file (Figure 13).
22. Click Finish to complete the installation.
For Windows 2003, click Next and then click Finish.

The configuration utility, Manage Tivoli Enterprise Monitoring Services, is

displayed. You can start, stop, and configure IBM Tivoli Monitoring components
from this utility.

Linux or UNIX: Installing a monitoring server

Table 5 shows the steps to install and configure the hub monitoring server on a
UNIX computer:
Table 5. Installing a monitoring server on a UNIX computer
Steps Where to find information
Install the hub monitoring server. “Installing the monitoring server”
Configure the hub monitoring server. “Configuring the monitoring server” on
page 20
Add application support to the hub “Adding application support to the hub
monitoring server. monitoring server” on page 21

Installing the monitoring server: Use the following steps to install the monitoring
server on a UNIX computer:
1. In the directory where you extracted the installation files, run the following
command:
./install.sh

Chapter 2. Installation and basic monitoring 19

 2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (opt/IBM/ITM). If you want to use a different installation
directory, type the full path to that directory and press Enter.
3. If the directory you specified does not exist, you are prompted to create it.
Type y to create this directory.
4. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment
(which requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

5. Type the number that corresponds to the language in which you want to
display the software license agreement and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type a 32-bit encryption key and press Enter. If you want to use the default
key, press Enter without typing any characters.
Notes:
a. Do not use any of the following characters in your key:
v Equal sign (=)
v Apostrophe (’)
v Pipe key, also known as the bar key or vertical bar (|)
b. Ensure that you document the value you use for the key. Use this key
during the installation of any components that communicate with this
monitoring server.
A numbered list of available operating systems is displayed.
9. Type the number for the operating system on which you are installing. The
default value is your current operating system. Press Enter.
10. Type y to confirm the operating system and press Enter.
A numbered list of available components is displayed.
11. Type the number that corresponds to the monitoring server. Press Enter.
A list of the components to install is displayed.
12. Type y to confirm the installation.
The installation begins.
13. When prompted, type a name for your monitoring server. Use the following
format: HUB_hostname. Press Enter.
14. After all of the components are installed, you are prompted to install
components for a different operating system. Type n and press Enter.
Installation is complete. The next step is to configure your monitoring server.

Configuring the monitoring server: Use the following steps to configure the hub
monitoring server:
1. At the command line change to the opt/IBM/ITM/bin directory (or the
directory where you installed IBM Tivoli Monitoring).
2. Run the following command:
./itmcmd config -S -t ms_name

20 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 where ms_name is the name of your monitoring server (for example,
HUB_itmdev17).
3. Press Enter to indicate that this system is a hub monitoring server (indicated
by the *LOCAL default).
4. Press Enter to accept the default host name for the monitoring server, which is
the host name for your computer. If it is not, type the correct host name and
press Enter.
5. Press Enter to use the default communications protocol (IP.PIPE).
6. Press Enter to skip identifying any backup protocols.
7. Press Enter to accept the default port number (1918).
8. Press Enter to not specify the name of the KDC_PARTITION. The default
value is null.
9. Press Enter when prompted for the path and name of the KDC_PARTITION.
10. Press Enter to accept the default setting for Configuration Auditing.
11. Press Enter to accept the default setting for Hot Standby (NO).
12. Press Enter to accept the default for the Optional Primary Network Name
(NONE).
13. Press Enter for the default Security, which is Validate User setting (NO).
14. If you plan to use IBM Tivoli Enterprise Console during week 4 to view
situation events, type y and press Enter to enable Event Integration. Complete
the following additional steps:
a. Type the name of the IBM Tivoli Enterprise Console event server and press
Enter.
b. Type the port number for the event server and press Enter.
15. Type S to save and exit the installation.
The monitoring server is now configured.

A configuration file is generated in the install_dir/config directory with the format

host_name_ms_ms_name.config (for example, itmdev17_ms_HUBitmdev17.config).

Adding application support to the hub monitoring server:

Use the following steps to add application support to the hub monitoring server:
1. Start the monitoring server by running the following command:
./itmcmd server start ms_name
2. Run the following command to add the application support to the monitoring
server, where pc is the product code:
./itmcmd support -t ms_name pc pc pc

Use the following product (agent) codes:

a4 OS/400® agent
lz Linux agent
nt Windows agent
sy Warehouse Summarization and Pruning agent
tm IBM Tivoli Monitoring 5.x Endpoint agent
ul UNIX Log agent
um Universal Agent

Chapter 2. Installation and basic monitoring 21

 ux UNIX agent

For example:
./itmcmd support -t hub_itmdev17 a4 lz nt sy tm ul um ux
3. Stop the monitoring server by running the following command:
./itmcmd server stop ms_name
4. Restart the monitoring server by running the following command:
./itmcmd server start ms_name

Installing the Tivoli Enterprise Portal server

You can install the Tivoli Enterprise Portal server on either a Windows computer
or Linux computer. Use the following sections for the these steps:
v “Windows: Installing the portal server”
v “Linux: Installing the portal server” on page 24

Windows: Installing the portal server

Use the following steps to install the Tivoli Enterprise Portal Server on a Windows
computer.
1. Launch the installation wizard by double-clicking the setup.exe file in the
WINDOWS subdirectory of the installation media.
2. Click Next on the Welcome window to start the installation.

Note: If you are installing this component on a computer where you have
already installed an IBM Tivoli Monitoring component (such as the
monitoring server), you see the another window (Figure 14) instead of
the Welcome window:

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

Click Modify and skip to step 7.

3. Read and accept the software license agreement by clicking Accept.
4. If you do not have a DB2 or MS SQL database or the IBM Java™ software
development kit (SDK) installed on this computer, a message regarding
potentially missing required software is displayed. If you are missing a
database, stop the installation, install the required database, and begin the
installation again.
If you are missing the IBM Java SDK, the installation program installs it
automatically during a later step. Click Next.

22 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Note: If your computer has all required software, you cannot see this step.
5. Specify the directory where you want to install the portal software and
accompanying files. The default location is C:\IBM\ITM. Click Next.
6. Type an encryption key to use. This key must be the same key that was used
during the installation of the monitoring server where this portal server will
connect. Click Next and then OK to confirm the encryption key.
7. Select Tivoli Enterprise Portal Server from the list of components to install.
8. Expand Tivoli Enterprise Portal Server and ensure that Tivoli Enterprise
Console® GUI Integration is selected. Do not select any agents.
9. Click Next.
10. Type a name for the program folder. The default is IBM Tivoli Monitoring.
Click Next.

Note: This step applies only if this component is the first that you are
installing on this computer. Otherwise, the existing program folder
name is used.
11. Click Next to start the installation.
A configuration window is displayed.
12. Clear any components that you have already installed and configured (if you
are installing multiple components on the same computer) and click Next to
begin configuring the portal server and the connection to the monitoring
server and to open Manage Tivoli Enterprise Monitoring Services.
13. Type the host name of the computer where you are installing the portal server
and click Next.
14. Configure the portal server connection to the data source (such as your DB2
database). Type the password for the database administrator in the Admin
Password field.
15. Type a database user ID and password. Click OK.

Note: If your environment requires complex passwords (passwords that

require both alpha and numeric characters), change the password to
comply with these requirements.
16. Click OK on the message that tells you that the portal server configuration
was successful.
17. Type ITMUser in the User ID field and type marath0n in the Password field for
the warehouse connection information. Click Next.
18. Check the protocol that the portal server will use to communicate with the
monitoring server. If you used the instructions in this chapter to install the
monitoring server, the protocol is IP.PIPE. Click OK.
19. Type the host name or IP address and the port number for the hub monitoring
server. Click OK.
20. Click No when you are prompted to configure or reconfigure the warehouse
connection. This connection was configured during the preinstallation
configuration.
21. Click OK to accept the default values for the default way in which any agents
installed on this computer will connect to the monitoring server.
22. Ensure that the host name and port number of the Tivoli Enterprise
Monitoring Server are correct.
23. Click OK to accept the default values for the communications protocol for the
agents to use to communicate with the hub monitoring server.
24. Clear the check box next to Display the README file.

Chapter 2. Installation and basic monitoring 23

 25. Click Finish to close the installation wizard.

After the installation completes, a README about Tivoli Enterprise Portal

configuration is displayed. Close this README.

Linux: Installing the portal server

Table 6 shows the steps to install and configure the portal server on a Linux
computer:
Table 6. Installing a portal server on a Linux computer
Steps Where to find information
Install the portal server and desktop client “Installing the portal server and desktop
on the Linux computer. client”
Configure the portal server. “Configuring the portal server on Linux” on
page 25
Start the portal server. “Starting the portal server” on page 26

Installing the portal server and desktop client: Use the following steps to install
the portal server and desktop client:

Note: Run these installation and configuration procedures as either the root user
or as the DB2 administrator.
1. In the directory where you extracted the installation files, run the following
command:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (opt/IBM/ITM).
3. Type y and press Enter to create this directory.
If you have already installed an IBM Tivoli Monitoring component on this
computer (such as the monitoring server), this directory already exists. In that
case, you are prompted to indicate whether you want to use the same
directory. Type y and press Enter.
4. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment
(which requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

5. Type the number that corresponds to the language in which you want to
display the software license agreement and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type a 32-bit encryption key and press Enter. This key must be the same key
that was used during the installation of the monitoring server to which this
portal server will connect.

Note: If you have already installed another IBM Tivoli Monitoring component
on this computer, this step does not occur.
A numbered list of available operating systems is displayed.

24 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 9. Type the number for the operating system on which you are installing. The
default value is your current operating system. Press Enter.
10. Type y to confirm the operating system and press Enter.
A numbered list of available components is displayed.
11. Type the number that corresponds to the portal server and press Enter.
A list of the components to install is displayed.
12. Type y to confirm the installation.
The installation begins.
13. After all of the components are installed, you are prompted about installing
components for a different operating system. Type y and press Enter.
14. Type the number that corresponds to Tivoli Enterprise Portal Browser support
and press Enter.
15. Type y to confirm the installation.
16. When you are prompted to install components for a different operating
system, type y and press Enter.
17. Type the number that corresponds to Tivoli Enterprise Portal Server support
and press Enter.
18. Type y to confirm the installation.
19. When you are prompted to install components for a different operating
system, type n and press Enter.
Installation is complete. The next step is to configure the portal server and desktop
client.

Configuring the portal server on Linux: Use the following steps to configure the
portal server:
1. At the command line change to the opt/IBM/ITM/bin directory.
2. Run the following command:
./itmcmd config -A cq
3. Press Enter when you are prompted to indicate whether the agent connects to
a monitoring server.
4. Type the host name for the hub monitoring server and press Enter.
5. Press Enter when you are prompted to indicate whether the agent must
connect through a firewall. The default value is NO.
6. Type the protocol to use to communicate with your hub monitoring server,
and press Enter.
7. Press Enter without specifying a backup protocol.
8. Press Enter to accept the default IP port number (1918).
9. Press Enter when you are prompted to indicate whether you want to
configure the connection to a secondary monitoring server. The default value
is NO.
10. Press Enter to accept the default for the Optional Primary Network Name
(NONE).
11. Type the DB2 instance name. The default value is db2inst1. Press Enter.
12. Type the DB2 administrator ID. The default is db2inst1. Press Enter.
13. Type the password for the DB2 administrator ID and press Enter.
14. Confirm the password for the DB2 administrator ID by typing it again. Press
Enter.

Chapter 2. Installation and basic monitoring 25

 15. Type the name of the database for the portal server. The default is TEPS. Press
Enter.
16. Type the name (or “login”) of the database user that the portal server will use
to access the database. The default is itmuser. Press Enter.
17. Type the password for the database user and press Enter.
18. Confirm the password for the database user by typing it again. Press Enter.
19. You are prompted to confirm that a DB2 login user can be created if it does
not exist. Type y and press Enter.
20. Type WAREHOUS for the name of the database that the Tivoli Data Warehouse
will use. Press Enter.
21. Type the name of the database user that the Tivoli Data Warehouse will use.
The default is itmuser. Press Enter.
22. Type the password for the Warehouse user ID and press Enter.
23. Confirm the password for the Warehouse user by typing it again. Press Enter.
Configuration is complete. The next step is to start the portal server.

Starting the portal server: Run the following command to start the portal server:
./itmcmd agent start cq

Installing Tivoli Enterprise Monitoring Agents

The following sections provide detailed instructions for installing a monitoring
agent:
v “Windows: Installing a monitoring agent”
v “Linux or UNIX: Installing a monitoring agent” on page 28

The agent that you are installing might require additional configuration steps. See
the agent documentation (specifically the configuration chapter in the user’s guide)
for more information.

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 Universal Agent
v Warehouse Proxy
v Warehouse Summarization and Pruning
v Windows OS

If you are installing any other agents (for example, DB2 or Exchange), launch the
agent installation using the setup.exe or install.sh files that are part of the different
agent installation packages.

Windows: Installing a monitoring agent

Use the following steps to install a monitoring agent:
1. Launch the installation wizard by double-clicking the setup.exe file on the
installation media.
2. Double-click the setup.exe file.

26 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Note: If you are running Windows 2003 and have set security to check the
software publisher of applications, you might receive an error message
stating that the setup.exe file is from an unknown publisher. Click Run
and disregard this error message.
The Welcome window is displayed.

Note: If you are installing this component on a computer where you have
already installed an IBM Tivoli Monitoring component such as the
monitoring server, you see the another window (Figure 15) instead of
the Welcome window:

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

Click Modify and skip to step 8.

3. Click Next.
4. Click Accept on the Software License Agreement window.
5. If you do not have a database such as DB2 or MS SQL, or do not have the
IBM Java SDK installed on this computer, a message regarding potentially
missing required software is displayed. You do not need any of this software
installed on this computer if you are installing only the monitoring agent on
this computer. Click Next to continue.

Note: If your computer has all required software, including the IBM Java
SDK, you cannot see this window.
6. Click Next to use the default installation directory.

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. If you are installing an agent
from an agent installation image, skip to step 8.
7. Specify an encryption key to use. This key must be the same key that was
used during the installation of the monitoring server to which this agent will
connect. Click Next and then OK to confirm the encryption key.
8. Click the plus sign (+) next to Tivoli Enterprise Monitoring Agents and select
the following agents:
v Monitoring Agent for Windows OS
v Universal Agent

Chapter 2. Installation and basic monitoring 27

 Notes:
a. This list applies to the agents installed from the IBM Tivoli Monitoring
installation image. The list of available agents is different for other agents.
b. If you want to install additional agents on this computer, select them now.
9. Click Next.
10. Click Next. Do not select any agents to deploy.
Notes:
a. 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.
b. This step applies only if this component is the first that you are installing
on this computer. Otherwise, the existing program folder name is used.
11. Click Next.
12. Review the installation summary details. This summary identifies what you
are installing and where you chose to install it. Click Next to begin installation
of components.
After the components are installed and the configuration environment is
initialized (indicated by a window), a configuration window is displayed.
13. Clear any components that you have already installed and configured if you
are installing multiple components on the same computer and click Next.
14. Click OK to accept the default values for the connection between all
components and the hub monitoring server.
15. Click OK to accept the default values for the communications protocol for the
monitoring server.
16. Clear the check box next to Display the README file.
17. Click Finish to complete the installation.
For Windows 2003, click Next and then click Finish.
18. Open the Manage Tivoli Enterprise Monitoring Services utility to see if the
monitoring agent was configured and started. If Yes is in the Configured
column, the agent was configured and started during the installation process.
19. 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:
a. Click Configure Using Defaults.
b. Use the agent-specific configuration settings in the User’s Guide for your
agent to complete any windows that require information.

Linux or UNIX: Installing a monitoring agent

Table 7 shows the steps to install and configure a monitoring agent on an UNIX
computer:
Table 7. Installing a monitoring agent on UNIX
Steps Where to find information
Install the monitoring agent. “Installing the monitoring agent” on page 29

28 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 7. Installing a monitoring agent on UNIX (continued)
Steps Where to find information
Configure the monitoring agent. “Configuring the monitoring agent” on page
30

Some agents require additional,

agent-specific configuration parameters. See
the agent documentation for the specific
agents that you are configuring.
Start the monitoring agent. “Starting the monitoring agents” on page 30

Installing the monitoring agent: Use the following steps to install a monitoring
agent on a UNIX computer:
1. In the directory where you extracted the installation files, run the following
command:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (opt/IBM/ITM).
3. Type y and press Enter to create this directory.
If you have already installed an IBM Tivoli Monitoring component, such as
the monitoring server, on this computer, this directory exists. In that case, you
are prompted to indicate whether you would like to use the same directory.
Type y and press Enter.
4. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment
(which requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

5. Type the number that corresponds to the language in which you want to
display the software license agreement and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type a 32-bit encryption key and press Enter. This key must be the same key
that was used during the installation of the monitoring server to which this
monitoring agent connects.

Note: If you have already installed another IBM Tivoli Monitoring component
on this computer, this step does not occur.
A numbered list of available operating systems is displayed.
9. Type the number for the operating system on which you are installing. The
default value is your current operating system. Press Enter.
10. Type y to confirm the operating system and press Enter.
A numbered list of available components is displayed.
11. Type the number that corresponds to the monitoring agent or agents that you
want to install. If you want to install more than one agent, use a comma (,) or
a space to separate the numbers for each agent. Press Enter.
A list of the components to install is displayed.

Chapter 2. Installation and basic monitoring 29

 12. Type y to confirm the installation.
The installation begins.
13. After all of the components are installed, you are prompted to indicate
whether you want to install components for a different operating system. Type
n and press Enter.

Installation is complete. The next step is to configure the monitoring agent to

connect to the monitoring server.

Configuring the monitoring agent: Use the following steps to configure your
monitoring agent:
1. Run the following command:
./itmcmd config -A pc

where pc is the product code for your agent. For the UNIX agent, use the ux
product code; for Linux, use lz. Running the cinfo command shows the
agents that are installed.
2. Press Enter when you are prompted to indicate whether the agent connects to
a monitoring server.
3. Type the host name for the monitoring server.
4. Press Enter when you are prompted to indicate whether the agent must
connect through a firewall. The default value is NO.
5. Type the protocol that you want to use to communicate with the monitoring
server. Ensure that this protocol is the same communications protocol that you
selected when you configured the monitoring server.
6. Press Enter without specifying a backup protocol.
7. Press Enter to accept the default port number (1918).
8. Press Enter to not specify the name of the KDC_PARTITION.
9. Press Enter when you are prompted to indicate whether you want to
configure the connection to a secondary monitoring server. The default value
is NO.

Note: This step applies only to agents installed from the IBM Tivoli
Monitoring installation image.
10. Press Enter to accept the default for the Optional Primary Network Name
(none).

Starting the monitoring agents:

You can start all agents running on a computer or start individual agents by using
the product codes:
v To start all monitoring agents, run the following command:
./itmcmd agent start all
v To start specific agents, run the following command:
./itmcmd agent start pc pc pc

Installing Tivoli Enterprise Portal desktop client

The following sections provide detailed information for installing the desktop
client:
v “Windows: Installing the desktop client” on page 31
v “Linux: Installing the desktop client” on page 32

30 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Windows: Installing the desktop client
Use the following steps to install the desktop client for Tivoli Enterprise Portal:
1. On the computer where you want to install the desktop client, start the
installation wizard by launching the setup.exe file from the installation media.
2. Click Next on the welcome window.

Note: If you are installing this component on a computer where you have
already installed an IBM Tivoli Monitoring component such as the
monitoring server, you see this window (Figure 16) instead of the
Welcome window:

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

Click Modify.
3. Accept the software license by clicking Accept.
4. If you do not have a DB2 or MS SQL database or the IBM Java SDK installed
on this computer, a message regarding potentially missing required software is
displayed. You do not need any of this software installed on this computer if
you are not installing the portal server on this computer. Click Next to
continue.
5. Read the information regarding potentially missing prerequisites and click
Next.
6. Specify the directory where you want to install the portal software and
accompanying files. The default location is C:\IBM\ITM. Click Next.
7. Type an encryption key to use. This key must be the same key that was used
during the installation of the portal server to which the client will connect.
Click Next and then OK to confirm the encryption key.
8. Select Tivoli Enterprise Portal client.
9. Expand Tivoli Enterprise Portal client and ensure that Tivoli Enterprise
Console GUI Integration is selected.
10. Click Next without selecting any agents to deploy.
11. Specify the program folder name and click Next.

Note: This step applies only if this component is the first that you are
installing on this computer. Otherwise, the existing program folder
name is used.
12. Confirm the installation details and click Next to start the installation.
After the installation is complete, a configuration window is displayed.

Chapter 2. Installation and basic monitoring 31

 13. Clear any components that you have already installed and configured (if you
are installing multiple components on the same computer) and click Next to
configure the connection to the portal server, the connection to the monitoring
server, and to launch Manage Tivoli Enterprise Monitoring Services.
14. Type the host name of the portal server and click OK.
15. Identify the type of protocol that the desktop client uses to communicate with
the monitoring server:
v If this client will communicate with a Windows monitoring server, select
IP.UDP.
v For a UNIX monitoring server, select IP.PIPE.
Click OK.
16. Type the host name and port number for the monitoring server and click OK.
17. Click Finish to complete the installation.

Linux: Installing the desktop client

Table 8 shows the steps to install and configure the portal desktop client on a
Linux computer:
Table 8. Installing the portal client on Linux
Step Where to find information
Install the desktop client. “Installing the desktop client”
Configure the desktop client. “Configuring the portal desktop client on
Linux” on page 33

Installing the desktop client: Use the following steps to install the portal server
and desktop client:
1. In the directory where you extracted the installation files, run the following
command:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (opt/IBM/ITM).
3. Type y and press Enter to create this directory.
If you have already installed an IBM Tivoli Monitoring component such as the
portal server on this computer, this directory already exists. In that case, you
are prompted to indicate whether you would like to use the same directory.
Type y and press Enter.
4. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment
(which requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

5. Type the number that corresponds to the language in which you want to
display the software license agreement and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.

32 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 8. Type an encryption key to use and press Enter. This key must be the same key
used during the installation of the portal server to which the client will
connect.
A numbered list of available operating systems is displayed.
9. Type the number for the operating system on which you are installing. The
default value is your current operating system. Press Enter.
10. Type y to confirm the operating system and press Enter.
A numbered list of available components is displayed.
11. Type the number that corresponds to the desktop client and press Enter.
A list of the components to install is displayed. Select the number of the
product that you want to install.
12. Type y to confirm the installation.
The installation begins.
13. After all of the components are installed, you are prompted to indicate
whether you want to install components for a different operating system. Type
y and press Enter.
14. Type the number that corresponds to the Tivoli Enterprise Portal Desktop
Client support and press Enter.
15. Type y to confirm the installation.
16. Type n when you are prompted to indicate whether to install components for
a different operating system. Press Enter.
Installation is complete. The next step is to configure the desktop client.

Configuring the portal desktop client on Linux: Use the following steps to
configure the desktop client on Linux:
1. At the command line change to the opt/IBM/ITM/bin directory.
2. Run the following command:
./itmcmd config -A cj
3. Press Enter to use the default instance name.
4. Type the host name for the portal server and press Enter.
5. Press Enter when you are prompted to indicate whether to use HTTP Proxy
support. The default value is No.
The desktop client is now configured. The next step is to start the portal server
and portal desktop client.

Installing support for agents on the monitoring server, portal

server, and browser and desktop clients
All agents require installing support files that contain agent-specific information
into the monitoring server, portal server, and portal desktop client. Support for
operating system agents (such as Windows OS Monitoring Agent) is included on
the base IBM Tivoli Monitoring installation, and support for non-operating system
agents (such as the Exchange monitoring agent) is provided with the agent
installation code.

When you installed the monitoring server, portal server, and portal desktop client
using the instructions earlier in this chapter, the support for agents on the IBM
Tivoli Monitoring installation image was installed by default. Now you must
return to each component and install the support for all agents installed from
agent installation images.

Chapter 2. Installation and basic monitoring 33

 Use the instructions in the following sections to install agent support:
v “Installing agent support on Windows components”
v “Installing agent support on Linux or UNIX components” on page 35

Installing agent support on Windows components

Use the following steps to install required agent support on Windows:

Note: This steps assume that you have installed the monitoring server and portal
server on one computer. If you are installing the support on a Windows
portal server or portal client (without another component), select only those
options that apply to what is installed on your computer.
1. Open Manage Tivoli Enterprise Monitoring Services.
2. Stop the portal server by right-clicking and then clicking Stop.
3. Right-click the component and click Change startup.
4. Select Manual and click OK.
5. Restart the computer.
6. In the directory where you downloaded and extracted the agent installation
files, double-click the setup.exe file to launch the agent installation.
7. Click Next on the Welcome window.

Note: If you are installing the support separately from the agent itself and
you have already installed an agent on this computer, you see another
window (Figure 17):

Figure 17. Installing agent support

Click Modify and skip to step 9.

8. Click Accept on the software license.
9. If you see a message that installed versions are newer than the agent
installation, click OK to ignore this message.
10. Expand Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server,
and Tivoli Enterprise Portal Desktop Client.
11. Select all options available under each section and click Next.
12. If you are on the monitoring server and you want to add the agent to the
deployment depot, select the agent and click Next.
13. Click Next on the installation summary window.
14. Click Next on the configuration window.

34 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Depending on where you are installing the support, additional configuration steps,
such as adding application support to the monitoring server, might be necessary.
Continue with these steps, referring to the installation sections for the appropriate
component as required.

Installing agent support on Linux or UNIX components

Use the following steps to install the support on a UNIX computer:
1. Stop the monitoring server by running the following command:
./itmcmd server stop ms_name
2. If you are installing the support on the Linux portal server, run the following
command to stop the portal server:
./itmcmd agent stop cq
3. In the directory where you downloaded and extracted the agent installation
files, run the following command:
./install.sh
4. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (opt/IBM/ITM).
5. The following prompt is displayed:
Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment
(which requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

6. Type the number that corresponds to the language in which you want to
display the software license agreement and press Enter.
7. Press Enter to display the agreement.
8. Type 1 to accept the agreement and press Enter.
9. Type a 32-bit encryption key and press Enter. This key must be the same key
that was used during the installation of the monitoring server to which this
monitoring agent connects.

Note: If you have already installed another IBM Tivoli Monitoring component
on this computer or you are installing support for an agent from an
agent installation image, this step is not included.
A numbered list of available operating systems and component support is
displayed.
10. Type the number that corresponds to one of the following:
v Tivoli Enterprise Portal Browser Client support
v Tivoli Enterprise Portal Desktop Client support
v Tivoli Enterprise Portal Server support
v Tivoli Enterprise Monitoring Server support

Note: Portal Browser Client support, Portal Desktop Client support, and
Portal Server support apply only to a Linux monitoring server that also
has an installed portal server. If your monitoring server is on AIX® or
Solaris, these options do not apply to you. You must separately install
the portal browser client, desktop client, and server support on the
computer where your portal server is installed.

Chapter 2. Installation and basic monitoring 35

 11. On the list of products available for the component that you selected, type the
number that corresponds to all of the above and press Enter.
A list of the components to install is displayed.
12. Type y to confirm the installation.
The installation begins.
13. After all of the components are installed, you are prompted to indicate
whether you want to install components for a different operating system. Type
y and press Enter.
14. Repeat steps 10 through 13 for each additional component for which you must
install support.
15. After you have finished installing all the agent support you need, type n when
you are prompted to indicate whether you want to install components for a
different operating system.
16. If you installed the support on the monitoring server, do the following:
a. Start the monitoring server by running the following command:
./itmcmd server start ms_name
b. Run the following command to add the application support for the new
agent to the monitoring server:
./itmcmd support -t ms_name pc

where ms_name is the name of the monitoring server and pc is the product
code for the agent.
To view the product code for the agent support you just installed, run the
following command:
./cinfo

Type 1 when prompted to display the product codes for the components
installed on this computer.
Add application support only for the agent you installed. For example, if
you installed the support for the DB2 agent, run the following command:
./itmcmd support -t hub_itmdev17 ud

The product code for the DB2 agent is ud.

c. Stop the monitoring server by running the following command:
./itmcmd server stop ms_name
d. Run the following command to restart the monitoring server:
./itmcmd server start ms_name
17. If you installed the support on the Linux portal server, do the following:
a. Run the following command to configure the portal server with the new
agent information:
./itmcmd config -A cq
b. Complete the configuration as prompted.
c. Run the following command to restart the portal server:
./itmcmd agent start cq

Starting the Tivoli Enterprise Portal client

After you have successfully installed all the components of your IBM Tivoli
Monitoring environment, you can verify the installation by launching the Tivoli

36 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Enterprise Portal to view monitoring data. You can access the Tivoli Enterprise
Portal through two clients, the desktop client and the browser client. See the
following sections:
v “Starting the desktop client”
v “Starting the browser client”

Starting the desktop client

Use the following steps to start the desktop client.

On Windows:
1. Click Start → Programs → IBM Tivoli Monitoring → Tivoli Enterprise Portal.
2. Type the user name in the login field. The default user name is sysadmin.
3. Do not type a password in the Password field. By default, the sysadmin ID
does not require a password.
4. Click OK.

On Linux, run the following command to start the portal desktop client:
./itmcmd agent start cj

Starting the browser client

Use the following steps to start the browser client.

Note: If you do not have the IBM Java SDK 1.4.2 installed on the computer where
you are using the browser client, it is installed automatically. Follow the
prompts on the window to install the SDK.
1. Start the Microsoft® Internet Explorer browser.
2. Type the URL for the Tivoli Enterprise Portal into the Address field of the
browser. The URL is http://systemname:1920///cnp/client, where the
systemname is the host name of the machine where the Tivoli Enterprise Portal
Server and browser component are installed.
3. Click Yes on the Warning - Security window.
4. Type the user name in the login field. The default user name is sysadmin.
5. Do not type a password in the Password field. By default, the sysadmin ID
does not require a password.
6. Click OK.

Exercise 2: Verifying and configuring your installation

The second exercise is to verify that your installation was successful and perform
basic configuration tasks.
v “Verifying your installation”
v “Configuring history collection” on page 39

Verifying your installation

Use the following steps to verify that your installation is complete:
v “Viewing default situations”
v “Generating a situation event” on page 39

Viewing default situations

A situation describes a condition you want to test. When you start a situation,
Tivoli Enterprise Portal compares the situation with the values that the monitoring

Chapter 2. Installation and basic monitoring 37

 agent collected and registers an event if the condition is met. You are alerted to
events by indicator icons that are displayed in the Navigator and, optionally,
sounds that play. The graphic view also shows event indicators.

Every Tivoli Enterprise Monitoring Agent (also called monitoring agents or agents)
provides a default set of situations that you can use to begin monitoring your
environment immediately.

Use the following steps to view a default situation:

1. Start the Tivoli Enterprise Portal browser client:
a. Start the Microsoft Internet Explorer browser.
b. Type the URL for the Tivoli Enterprise Portal into the Address field of the
browser. The URL is http://systemname:1920///cnp/client, where the
systemname is the host name of the machine where the Tivoli Enterprise
Portal Server and browser component are installed.
c. Click Yes on the Warning - Security window.
A window (Figure 18) is displayed.

Figure 18. Logging into the Tivoli Enterprise Portal

d. Type the user name in the login field. The default user name is sysadmin.
e. Click OK.
f. Click Accept on the certificate window.
2. In the Navigation tree (on the left side of the portal), expand the tree until you
see the operating system such as Windows Systems that you installed.
3. To view the default situations, right-click the agent and click Manage
Situations.
A list of all available situations is displayed (Figure 19 on page 39). You can
view the status of each situation, as well as other information.

38 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Figure 19. Managing default situations

Generating a situation event

One way to verify that your installation is working correctly is to create a basic
situation that monitors a process on your computer. You can use the situation to
stop the process manually, which triggers a situation event. For information about
creating a basic situation, see “Creating a situation” on page 43.

Configuring history collection

Complete the following procedures to configure your environment for history
collection:
v “Configuring and registering the Warehouse Proxy”
v “Configuring historical data collection” on page 40

Note: Before you can use history collection, you must install the Warehouse Proxy
on a Windows computer, preferably the portal server. See “Exercise 1:
Installing IBM Tivoli Monitoring” on page 3 for installation steps. You must
also perform the preinstallation configuration steps, which are documented
in “Preinstallation configuration” on page 5.

Configuring and registering the Warehouse Proxy

Use the following steps to configure the Warehouse Proxy:
1. In Manage Tivoli Enterprise Monitoring Services, right-click Warehouse Proxy.
2. Click Reconfigure.
3. Click OK on the message regarding connection to a hub monitoring server.
4. Click OK to accept the default values for connecting to the hub monitoring
server.
5. Click OK to accept the default values for the hub monitoring server.

Chapter 2. Installation and basic monitoring 39

 6. If you have already configured your ODBC data source connection, which is
described in “Preinstallation configuration” on page 5, click NO when you are
prompted to indicate whether you want to configure the data source.
7. If you have not configured the ODBC data source connection, click Yes and
complete the following steps:

Note: These steps are based on a DB2 database. The steps might be different if
you are using another type of database.
a. Select the database that you are using for the Warehouse Proxy and click
OK. You have the following choices:
v DB2
v SQL Server
v Oracle
v Other database type
b. Complete the following fields as appropriate:
Data Source Name
The name of the data source. The default is ITM Warehouse. If you
want to define a new data source, type a new name here.
Otherwise, leave the default value.
Database Name
The name of the database. If you used the steps in “Create a
database for the Warehouse Proxy” on page 6 to create the database,
the name is wproxy. If you are defining a new data source and want
to specify a different database, type the name here. Otherwise, leave
the default value.
Admin User ID
The user ID for the database administrator. The default for DB2 is
db2admin.
Admin Password
The password for the database administrator.
Database User ID
The name of the user that accesses the IBM Tivoli Monitoring data
warehouse. The default name is ITMUser.
Database Password
Type a password for the database user. If your environment requires
complex passwords, include a numeric character in the password.
Reenter Password
Confirm the password by typing it again.
c. If this information is different from what you used when you configured the
Tivoli Enterprise Portal server, select Synchronize TEPS Warehouse
Informationto update the portal server configuration with the same values.
d. Click OK.

Restart the Warehouse Proxy by right-clicking it and clicking Start.

Configuring historical data collection

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:

40 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

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. Start the Tivoli Enterprise Portal client. You can start either the browser client
or the desktop client.
To start the browser client, do the following:
a. Start the Microsoft Internet Explorer browser.
b. Type the URL for the Tivoli Enterprise Portal into the Address field of the
browser. The URL is http://systemname:1920///cnp/client, where the
systemname is the host name of the machine where the Tivoli Enterprise
Portal Server and browser component are installed.
c. Type the user name in the login field. The default user name is sysadmin.
d. Click OK.
To start the desktop client, do the following steps:
a. Double-click the Tivoli Enterprise Portal Desktop Client icon on your

desktop:
b. Type the user name in the login field. The default user name is “sysadmin”.
c. Click OK.
2. Click Edit → History Configuration to open the History Collection
Configuration window.
3. Do one of the following steps:
For Windows, do the following steps:
a. Select Windows OS in the Select a product list.
b. Select all attribute groups that start with NT_ from the Select Attribute
Groups table.

Note: Click the Group column heading in the Select Attribute Groups
table to sort the attribute groups by name.

For UNIX, do the following steps:

a. Select UNIX in the Select a product list.
b. Select all of the attribute groups.
4. In the Collection Interval section, select 15 minutes as your interval.
5. In the Collection Location, select TEMA, Tivoli Enterprise Monitoring Agent.

Note: Collecting data at the agent minimizes performance impact on the

monitoring server from historical data management tasks.

Chapter 2. Installation and basic monitoring 41

 6. In the Warehouse Interval section, select 1 day as the interval for the data you
want to collect.
7. Click Configure Groups to save your settings.
8. Select all of the groups and click Start collection.

Configuring data collection for logs

Use the following procedure to configure historical data collection for the Tivoli
Monitoring Services Logs:

Note: The Tivoli Monitoring Services Logs apply to all applications. If you want to
save the information in these logs, configure them for warehousing.
1. Select CCC Logs in the Select a product list.
2. Select all groups from the Select Attribute Groups table except for Universal
Message and TWORKLST.

Note: Query support is not provided for Universal Message Log or

TWORKLST (Worklist Log).
3. In the Collection Interval section, select 15 minutes as your interval.
4. In the Collection Location, select TEMA.

Note: Collecting data at the Tivoli Enterprise Monitoring Agent minimizes

performance impact on the monitoring server from historical data
management tasks.
5. In the Warehouse Interval section, select 1 day as the interval for the data you
wish to collect.
6. Click Configure Groups to save your settings.
7. Select all of the groups (hold the Shift key while you click in the list of groups)
and click Start collection.
8. Select the monitoring server on which you want to collect the log file
information.
9. Click Close to exit the History Collection Configuration window.

Note: Some of the logs have historical configuration values that cannot be
changed. After you click Configure, values that are different from those that
you specified might be displayed. The collection occurs at the values that
the product determines.

42 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Exercise 3: Creating and using situations
Situations notify you when certain conditions have been met at the system.
Additionally, you can use situations to send a message or command. Use the
following procedures to create and use situations:
v “Creating a situation”
v “Editing a situation” on page 44
v “Managing events” on page 45

Creating a situation
Use the following procedures to create a situation:
v “Creating a new situation on Windows”
v “Creating a new situation on Linux or UNIX” on page 44

Creating a new situation on Windows

First, create a situation to monitor whether the Windows Alerter service is running.
1. Start the Tivoli Enterprise Portal client, as described in “Viewing default
situations” on page 37.
2. Expand Windows Systems in the navigation tree.
3. Expand the computer where you are working.
4. Expand Windows OS.
5. Right-click System and click Situations.
6. In the Situation editor, click the Create new Situation icon.
7. Type My_Situation in the Name field and click OK.
8. Select NT_Services in the Attribute Group list and Service Name in the
Attribute Item list. Click OK.
9. In the Formula pane, click the field in Row 1 under Service Name.
10. Type Alerter. This input is case-sensitive.

Note: Ensure that the Alerter service is not disabled.

11. Click Add conditions.
12. Select Start Type in the Attribute Item list and click OK.
13. Click the field in Row 1 under Start Type.
14. Click Automatic in the drop-down list.

Note: If the Alerter service on your computer is not configured to start

automatically, select the type of start that matches the start type of the
Alerter service on your computer.
15. Click Add conditions.
16. Select Current State in the Attribute Item list and click OK.
17. Click the field in Row 1 under Current State.
18. Type Stopped.
19. Change the Sampling Interval to 30 seconds by typing 30 in the ss box and 0
in the mm box.
20. Click the Distribution tab and ensure that the host name for your computer is
listed in the Assigned list. The situation is monitored at this computer.
21. Click OK.

Next, stop the Alerter service to trigger the situation. Use the following steps:

Chapter 2. Installation and basic monitoring 43

 1. Open a command line window.
2. Type the following command and press Enter:
net stop Alerter

Now, return to the Tivoli Enterprise Portal to see the situation event. In the
Navigation tree, click Enterprise to display the Enterprise Status workspace, which
might take up to 30 seconds to display. An event is listed in the Situation Event
Console on Enterprise View, and red Xs are displayed for Windows Systems,
Windows OS, and System.

Creating a new situation on Linux or UNIX

Use the following steps to create a situation that monitors the percentage of disk
space currently in use.
1. Start the Tivoli Enterprise Portal client, as described in “Viewing default
situations” on page 37.
2. Expand UNIX Systems in the navigation tree.
3. Expand the computer where you are working.
4. Expand UNIX OS.
5. Right-click Disk Usage and click Situations.
6. In the Situation editor, click the Create new Situation icon.
7. Type My_Situation in the Name field and click OK.
8. Select Disk in the Attribute Group list and Space Used Percent in the
Attribute Item list.
9. Click OK.
10. Click the field in Row 1 under Space Used Percent.
11. Click the equals signs (==) and click > Greater than in the list.
12. Type 1 in the text box.
13. Change the Sampling Interval to 30 seconds by typing 30 in the ss box and 0
in the mm box.
14. Click the Distribution tab and ensure that the host name for your computer is
listed in the Assigned list.
15. Click OK.

Now, return to the Tivoli Enterprise Portal to see the situation event. In the
Navigation tree, click Enterprise to display the Enterprise Status workspace. (This
might take up to 30 seconds to display.) An event is listed in the Situation Event
Console on Enterprise View, and red Xs are displayed next to UNIX Systems,
UNIX OS, and Disk Usage.

Editing a situation
Use the following steps to edit an existing situation.

Editing your Windows situation

Use the following steps to edit the situation, my_situation, you created in the
previous section. Next, you will add an action that occurs when the situation is
triggered.
1. Open the Situation editor by clicking in the portal.
2. Expand Windows OS.
3. Click My_Situation.
4. Click the Action tab.

44 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 5. Type the following in the System Command field:
net send host_name Alerter Service has stopped

where host_name is the host name of your computer.

6. Click OK.

Editing your Linux or UNIX situation

Use the following steps to edit the situation, my_situation, you created in the
previous section to change the percent of used space that triggers the situation.
1. Open the Situation editor by clicking in the portal.
2. Expand UNIX OS.
3. Click My_Situation.
4. Click the field in Row 1 under Space Used Percent.
5. Change the value in the text box from 1 to 10.
6. Click OK.

Managing events
Use the following options to manage events:
v “Opening the event workspace”
v “Creating or removing an acknowledgement”
v “Closing an event” on page 46
v “Adding an Event Console view to the workspace” on page 46
v “Adding a message log view to the workspace” on page 47
v “Setting the Universal Message console view” on page 47

Opening the event workspace

When the conditions of a situation are met, event indicators are displayed in the
Navigator. You can investigate the event by opening its workspace.
1. Move the mouse over a status indicator icon in the Navigator or graphic view
to open a flyover listing of the situation or situations that caused the event or
events.
2. In the flyover listing, click the linked chain icon next to the situation to open its
event workspace. A new Navigator item is displayed below the one that is
associated with the event, and the event workspace opens.

Creating or removing an acknowledgement

When you see an event indicator in the Navigator, you can create an
acknowledgement to notify other users that you have taken ownership of the
problem related to the event and are working on it.
1. Move the mouse over an event indicator in the Navigator to open the flyover
list of open events and right-click the event you want to acknowledge.
2. Click the Acknowledge icon.
3. Do one of the following:
v Adjust the Expiration settings for the time when the acknowledgement
would expire, type any notes associated with the event, and click the clock
icon to insert an event timestamp.
After you click OK, the Navigator displays an acknowledged event icon and
the flyover list shows a check mark after the event timestamp. The

Chapter 2. Installation and basic monitoring 45

 acknowledgement indicator turns off if the situation becomes false. If the
situation is still true when the acknowledgement expires, the icon changes to
a clock placed over a check mark.
v Click Remove.
After you click OK, the acknowledgement is removed and the
acknowledgement status for the open event changes to Reopened.

Closing an event
There are two types of events:
Pure Occur automatically, such as when a paper out condition occurs on the
printer or when a new log entry is written. Situations written to notify you
of pure events remain true until they are manually closed or automatically
closed by an UNTIL clause. You can close pure events.
Sampled
Occur when a situation becomes true. Situations sample data at regular
intervals. When the situation is true, it opens an event, which is closed
automatically when the situation reverts to false. You can close it manually
also. To close a sampled event, you must first stop the situation.

Use one of the following methods to close the event.

Before you can close an event, you must stop the situation that triggered the event.
To do that, right-click the situation row in the Situation Event Console and click

.
Situation flyover list: Do the following to close an event from the event flyover
list:
1. In the Navigator move the mouse over the event indicator to open a flyover
listing of the true situations.
2. In the flyover list right-click the situation whose event you want to close.
3. Click the Close Situation Event icon.

Navigator item: Do the following steps to close a pure event that is also known as
an unsampled event, from the Navigator item for a situation. You can tell if the
event is a pure event by looking at the Type column in the message view.
1. In the Navigator move the mouse over the event indicator to open a flyover
listing of the true situations.
2. In the flyover list click a situation name to open its event workspace.
3. In the Navigator right-click the situation name and click the Close Situation
Event icon.

Event console view: To close an event from the event console view:
1. In the Enterprise workspace where the event console view displays, right-click
the event you want to close.
To access this workspace, click Enterprise in the Navigation tree.
2. Click the Close Situation Event icon.

Adding an Event Console view to the workspace

1. From any workspace, click the Split Vertically icon or the Split
Horizontally icon.
2. Click the Event Console icon.

46 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

3. Click inside the view where you want the event console.
4. Click the Save icon to save the view with this workspace.

Setting event console properties:

1. Right-click anywhere in the Event Console view.
2. Click Properties.
3. Set Filters to report only the values or value ranges you specify.
4. Set the Thresholds icon to highlight areas of interest.
5. Add a header or footer in the Style tab.
6. Click Apply or OK to close the window.

Adding a message log view to the workspace

1. From any workspace, click the Split Vertically icon or the Split Horizontally
icon.
2. Click the Message Log icon.
3. Click inside the view where you want the message log.
4. Click the Save icon to save the view with this workspace.

Applying quick settings: Set a row limit

1. Right-click anywhere in the message log view.
2. Click Set Max Rows50.

Setting a quick threshold

1. Right-click the cell on whose value you want to apply a threshold indicator.
2. Click Set Quick Threshold (attribute name == value).

Setting the Universal Message console view

1. From any workspace, click the Split Vertically icon or the Split Horizontally
icon.
2. Click the Universal Message Console icon.
3. Click inside the view where you want the Universal Message console.
4. Click File → Save Workspace as to save the workspace properties with the new
view.
5. Type a name for this new workspace and click OK.

Chapter 2. Installation and basic monitoring 47

Exercise 4: Creating new views for the Tivoli Enterprise Portal
Use the following procedures to create and customize views and workspaces:
v “Creating a view”
v “Defining a workspace”
v “Editing a workspace” on page 49
v “Creating ranges and sub-ranges on linear and circular gauge views” on page 49

Creating a view
1. In any view in your workspace, click the Split Vertically icon or the Split
Horizontally icon.
2. Click the Browser icon.
3. Click inside the view where you want the Browser view.
4. Click Save to update the workspace properties with the new view.
5. Try creating any of the additional views by repeating steps 1 through 5:
v Table
v Pie chart
v Bar chart
v Plot chart
v Graphic
v Terminal
v Notepad

Note: These view options are available at the top of the portal window. Hover
over each icon to see the type of view.

Defining a workspace
Defining a workspace includes the following tasks:
v “Changing the view type”
v “Editing view properties”
v “Saving a new workspace” on page 49

Changing the view type

1. Click the Notepad icon.
2. Click inside the Browser view that you just created. The Notepad chart view
replaces the Browser view.

Editing view properties

1. Right-click inside the Notepad view and click Properties. The Properties
window for the workspace is displayed.
2. In the Text style section of the Style tab, select the following:
v Courier New from the Font name list.
v 14 from the Size list.
3. Click OK.

48 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Saving a new workspace
1. Click File → Save Workspace As. If you are running Tivoli Enterprise Portal in
browser mode, be sure to select its File menu and not the browser’s File menu.
2. Type My Workspace in the Name field.
3. Select Assign as default for this Navigator Item.
4. Click OK.
5. Now test your workspace by opening another workspace and clicking this
Navigator item again.

Editing a workspace
Use the Properties editor to change the general characteristics of a workspace and
to edit the style and content of any of its views.
1. Click the Properties icon.
The Properties editor opens. The tree on the left shows the workspace name
selected, with the workspace properties on the right.
2. Make changes to the Workspace Identity and Workspace Options sections.
3. If you want to edit the properties for a particular view, select a view from the
Properties tree and make changes to the view properties.
4. Click OK to save your changes and close the Properties editor.

Creating ranges and sub-ranges on linear and circular gauge

views
1. In the Navigation tree, expand Windows Systems → <Windows host name> →
Windows OS.
2. Click Memory to display the Memory workspace.
3. Split the Memory Allocation view horizontally.
4. Click the Notepad icon and add it to one of the new windows that you
created in the previous step.
5. Click the Linear Gauge icon and click inside the Notepad view.
6. Select Yes in the Select option window.
7. Do the following to assign a query to the gauge:

a. Click Click here to assign a query.

b. Expand Windows OS → NT_Memory.
c. Click Memory Allocation.
d. Click OK.
8. Click the Filters tab.
9. Select Available Bytes and click Apply.
10. Do the following to change the appearance of the gauge, including the range
of values:
a. Click the Style tab.
b. Click the Linear Gauge icon.

Chapter 2. Installation and basic monitoring 49

 c. On the Scale tab, change the color to blue.
d. On the Needle tab, change the Style to pointer and the Width to 10.
e. On the Range tab, clear the Use default boxes.
f. Type 0 in the Minimum Value field.
g. Type a value greater than the total bytes available (shown in the Preview
gauge) in the Maximum Value field. For example, if your total bytes
available is 111362048, type 120000000.
h. Click Edit Subranges to add threshold coloring.
1) Click Create New.
2) Type a name to create for definition and click OK.
3) Select the color yellow from the list.
4) In the Minimum Value and Maximum Value fields, type two numbers
between the minimum and maximum range for the gauge. For
example, for the minimum value, type 60026016 and for the maximum
value, 72251219. (These values are between 0 and 12000000, the range
for the gauge.)
5) Click Apply and click OK.
11. Click Apply and then OK.
The new linear gauge is displayed in the workspace.

Figure 20. Example linear gauge for memory allocation

12. Try creating a Circular Gauge view by repeating steps 1 through 11.

50 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Chapter 3. Basic product function
Perform the following exercises to explore the graphical interface and monitoring
capabilities of IBM Tivoli Monitoring:
1. “Exercise 5: Creating a policy”
2. “Exercise 6: Launching an application” on page 53
3. “Exercise 7: Using historical data” on page 55
4. “Exercise 8: Creating a graphical view and using the business navigator” on
page 59

Exercise 5: Creating a policy

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. Use the following procedures to
build and run a policy:
v “Adding a new policy”
v “Adding and connecting activities”
v “Validating the workflow logic and saving the policy” on page 52
v “Starting the policy” on page 52

Adding a new policy

Use the following steps to add a new policy, name it, and adjust any settings:
1. Click Edit  Workflow Editor to open the Workflows window.
2. Click the New Policy icon. New_Policy is added to the Policy Details list in
the Policy Details section and a blank Grapher view opens in the Workflow
Editor section.
3. Edit the options in the New_Policy row of the Policy Details section.
Policy name
Click inside this field and type My_Policy.

Note: You cannot rename the policy after you click Apply or OK.
Instead, you must copy the policy and change the name for the
new policy.
Distributed
Click the check box to open the Change Policy Distribution window;
select the computer on which you want to run this policy (either your
monitoring server or one of the standalone agents that you installed).
Click OK to close this window.
Description
The description for the policy.

Adding and connecting activities

After creating the policy, use the following steps to add activities and connect them
to construct the event workflow:

© Copyright IBM Corp. 2005 51

 1. Stop the My_Situation situation that you created. To stop a situation, do the
following:
a. In the Navigation tree, right-click the managed system (under the agent)
with which you associated the situation and click Manage Situations.
b. Select the situation and click .
2. In the Workflow editor, click Wait until a situation is True in the General
activities tab of the Workflow components frame.
3. Click inside the Grapher view to place the activity icon. The Select a situation
window is displayed.
4. Select the My_Situation situation.
5. Click OK. The activity icon with the name of the situation is displayed in the
Grapher view.
6. Click Start/Stop a situation and click in the Grapher view.
7. Select My_Situation2 from the list of situations and click OK. Leave Start
selected by default.
8. Click Wait until a Situation is True in the Grapher view.
9. Click the arrow (the Connect tool) in the General activities tab of the
Workflow components frame to draw connecting lines to direct the workflow.
10. Click the Wait until a situation is True activity and then click Start/Stop a
situation. The Select a Link condition window is displayed with a list of
possible conditions that will run the next activity.
11. Select Situation is true from the Select a link condition window and click OK.
12. Click Apply.

Validating the workflow logic and saving the policy

After you add and connect activities, use the following steps to validate the
workflow logic and save the policy:
1. Click one of the activities in your policy.
2. Click Validate to ensure that you have a valid logic flow.
If you get an error message, you must fix the problem before you can save the
policy. The following changes indicate an activity that is not valid:
v The border 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.
3. Click Apply to save the changes and continue working with policies.

Starting the policy

If you accepted the default setting of autostart, the policy starts running as soon as
you save it. You can bypass the following steps for starting the policy.
1. Select My_Policy from the Policy Details list.
2. Click Start Policy to start the policy.
3. Select the monitoring server from the Start/Stop Policy window and click Start.

Do the following steps to test the policy:

1. Right-click Windows OS in the Navigator tree and click Manage situations.
2. Select My_Situation2 and make sure that it is stopped.

52 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 3. Start the My_Situation situation.
4. In the console, watch the My_Situation2 situation start.

Exercise 6: Launching an application

Use the following Tivoli Enterprise Portal features for launching an application and
Take Action :
v “Launch application” for starting applications from your workstation and
adding substitutable variables
v “Take action” for invoking commands at managed systems
v “Creating a reflex action in a situation” on page 54 for creating a situation that
when true, sends a command through the Take Action feature

Launch application
Your user ID must have Launch permission for the Launch Application feature.
The default user, sysadmin, has this permission by default. If you create additional
users, you must grant this permission to them.

Use the following steps to launch an application:

1. Expand the following Navigator items by clicking on the plus (+) sign by each
subsequent item until you get to the Windows OS .
a. Enterprise
b. Windows System
c. <system you are monitoring>
d. Windows OS
2. Click Disk in the Navigator view to open the workspace.
3. Right-click Disk.
4. Click Launch.
5. In the Create or Edit Launch Definitions window:
a. Click Create New.
b. Type WordPad in the Name field.
c. Click Browse to locate and select write.exe in the Target field.
d. Click OK.
e. Right-click Disk.
f. Click Launch.
g. Double-click WordPad or select Launch to open WordPad.
h. In the WordPad window, create a dummy file and save it to your local disk.
i. In the Arguments field:
v Click Browse,
v Select Filename and locate and select the file you just created. Click OK.
v Click Launch.
v When you are prompted to indicate whether you want to save, click Yes.
Your file is opened in WordPad.

Take action
The Take Action feature lets you interact directly with your applications and
operating system. Take Action has a text box for entering your own system

Chapter 3. Basic product function 53

 command, or you can choose from a list of predefined commands. It also has a list
of managed systems on which to make the command effective.

The Messenger Services must be running for this exercise.

Creating and sending a take action command

Use the following steps for the Take Action feature:
1. Right-click Disk in the Navigator view.
2. Select Take ActionCreate or Edit from the menu.
You can also right-click a row in a table view, slice in a pie chart, or bar of a
bar chart.
3. Select <Create New Action> and click OK.
4. Type MyMessage in the Name field in the Action Identity section of the Create
New Action window.
5. Type the following in the Command field in the Action Command section:
Net send <local host> The server is running out of memory.
Close some applications.
6. Click OK.
7. Right-click Disk in the Navigator view.
8. Select Take ActionSelect from the pop-up menu.
9. Select the MyMessage in the Name field.
10. Select your system from the Destination Systems section.
11. Click OK.
12. The Take Action message is displayed on your desktop.

Editing a take action command

1. Select Disk in the Navigator view or right-click the bar of the bar chart.
2. Click Take Action  Create or Edit from the pop-up menu.
The Edit Action and Select Action windows open.
3. Select MyMessage from the list and click OK.
4. In the Edit Action window, edit the command to reflect a full path name for
your local host.
5. When you are finished editing the command, click OK to save your changes.

Creating a reflex action in a situation

You can create a situation that when true, sends a command through the Take
Action feature.

Note: The portal must be running on the computer where you want to take this
action.
1. Click Process in the Navigator view to open the workspace.
2. Right-click Process and select Workspace → Process Overview.
3. Right-click Process → Launch.
4. In the Create or Edit Launch Definitions window, select WordPad.
5. Click Launch.
6. Click OK.
7. In the Tivoli Enterprise Portal, find the wordpad process in the Process Name
column of the Process Overview section at the bottom of the window.

Note: Click the Process Name column to sort by name.

54 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 8. If it is not listed, click View → Refresh Now (F5).
9. Right-click Process Navigator item and select Situations.
10. Click Create New Situation from the tool bar at the top of the Situation
Editor window.
11. Type MyTakeAction in the Name field of the Create Situation window.
A name cannot contain spaces.
12. Click OK.
The Select condition window displays automatically.
13. Select NT-Process as the Attribute Group.
14. Select Process Name as the Attribute Item.
15. Click OK.
16. In the Formula tab in the Situations for - Process window, click in the first
row of the Process Name column.
17. Type wordpad.
18. In the Action tab, type taskmgr in the System Command field.
19. Click OK.

Exercise 7: Using historical data

You started the collection of data in Exercise 2. Use the following Tivoli Enterprise
Portal features for setting a time span, creating a query and exporting the results:
v “Historical reporting, setting a time span”
v “Creating a monitoring server query” on page 56 to create your own query and
create a table or chart view
v “Exporting query results” on page 58 to export the results to a file that can be
read in any spreadsheet.

Historical reporting, setting a time span

Use the following procedure for setting a time span:
1. Expand the following Navigator items by clicking on the plus (+) sign by each
subsequent item until you get to the Windows OS.
a. Enterprise
b. Windows System
c. <system you are monitoring>
d. Windows OS
2. Click System in the Navigator view.
3. Click Time Span. It is located under the Monitored Logs menu title on the
right side of the window.
4. Click Custom.
5. Click Use detailed data in the Custom parameters section:
6. Specify an exact Start Time and End Time:
a. For Start Time and End Time, click the adjacent list box to open the date
editor.
b. Click the arrows next to the element to change (hour, minute, second or
AM/PM) to adjust up or down.
c. Day is set to the current day. Click the current day or another day in the
calendar, which also closes the editor.

Chapter 3. Basic product function 55

 If you close the date editor without clicking the day of the month, the changes
you just made do not take effect.
7. Select Apply to all views associated with this view’s query to apply the time
span to all views associated with this view’s query (set of attributes).
When Apply to all views associated with this view’s query is enabled.
Because the query is modified to include the time span set here, any other
views using this query report the same time range.
8. Click OK.
The view shows data from earlier samplings for the period specified.
9. To keep the time span settings for this view, click File → Save Workspace.

Note: Even if data collection was started, you cannot use the time span feature if
the query for the chart or table includes any column functions. In that case,
you can select or create another query to activate the Time Span feature.

Disabling historical reporting

Use the following procedure to set your historical view back to showing only
current data samplings:
1. Expand the following Navigator items by clicking on the plus (+) sign by each
subsequent item until you get to the Windows OS.
a. Enterprise
b. Windows System
c. <system you are monitoring>
d. Windows OS
2. Click System in the Navigator view.
3. Click Time Span. It is located under the Monitored Logs menu title on the
right side of the window.
4. Select Real time and click OK.
The view now shows data from the current sampling only. The exception is
views of attribute groups that are normally historical, such as the Situation
Status and the Windows Event Log. By selecting Real time, you enable these
attribute groups to show all data they have collected, up to 2000 of the most
recent entries.
5. To keep the time span settings for this view, click File → Save Workspace.

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.

56 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 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. Edit the specification for any changes you want to make:
v Click Add Attributes and select the Virtual Kbytes Peak attribute. Click OK.
The attributes available are from the group used in the original query.
v Add filter criteria by clicking in the Virtual Kbytes Peak (you might want to
shift the horizontal scroll bar to the right to see this column) and writing an
expression. Click the equal sign (=) to choose your operator.
EQ $NODE$ (or any name enclosed in dollar signs) is a required filter; you
must not delete it.
v Clear the filter criteria by right-clicking the cell, column or row and selecting
Clear Contents.
v Add a column function by clicking in the column heading and selecting a
function from the list; then click Advanced. Select the column to Group By.
v Specify a sort order by clicking Advanced, and selecting the column to Sort
By.

Note: If you selected a Group By column, you cannot specify a sort order.
v Specify the exact number of rows to show in the view by clicking Advanced
and selecting First to retrieve.
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.

Use the following steps to create a query of ODBC database attributes:

1. Click Queries located in the toolbar.

2. Click , 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.

Chapter 3. Basic product function 57

 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.

Deleting a query
If you delete a query that is being used by a view, the view is subsequently not
associated with a query and does not have data the next time that you open its
workspace.

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 the Query you want to delete and click Delete Query.
4. Click OK to confirm.

Exporting query results

Table and chart views show the results of the assigned query, plus any filters you
have applied. You can use the export feature to save the results as a text file, either
TXT or Comma Separated Values (CSV), for use in other programs.

When saving the results, you can select additional columns from the query, even if
they were filtered out of the view, or fewer columns. Furthermore, you can save all
the rows that were returned or, if there are multiple pages, just those on the
current page.

Use the following steps to export your query results:

1. Expand the following Navigator items by clicking on the plus (+) sign by each
subsequent item until you get to the Windows OS.
a. Enterprise
b. Windows System
c. <system you are monitoring>
d. Windows OS
2. Click System.
3. Open the workspace with the table or chart view whose query results you want
to save.
4. Right-click inside the table or chart view and select Export from the popup
menu.
5. In the Export window, select the location for the exported data, the file type,
and enter a file name.
6. To export all rows of the columns shown (Assigned column), click OK; or if
you have a query that is more than one page in length, do any of the
following:
v For the displayed page instead of all rows, click Current page.

58 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 v To add a column to those being exported, select from Available Columns
and click the left arrow; to exclude a column, select from the Assigned list
and click the right arrow.
v To change the order, select a column and click the up arrow or down arrow.
7. Click OK to close the window.

Use Ctrl+click to select multiple columns or Shift+click to select all columns from
the first one selected to this point.

Exercise 8: Creating a graphical view and using the business

navigator
Use the following procedures to create and work with custom views in Tivoli
Enterprise Portal:
v “Creating a graphic view” to create a graphic view within a workspace. To
create a graphic view, you create a new view in which to create a graphic. Then
use the graphic view tools to create a graphic consisting of icons, labels, and
background.
v “Creating a Business Navigator view” on page 60 to create a business navigator
view. To create a business navigator view, use the Navigator Editor.

Creating a graphic view

The graphic view provides a canvas to cover with icons that represent the
Navigator items and any event indicators. For example, you might create a graphic
view of your company’s floor plan or organization chart.

Follow these steps to add a graphic view to the workspace:

1. Open the workspace where you want the view.
2. To create a new view for the graphic, click Split Vertically or Split
Horizontally in one of the existing views.
3. Click Graphic View.
4. Click inside the new view that you created.
The mouse changes to as you move inside the workspace. After you click,
the old view is replaced by the default graphic, and the child Navigator items
of the current item are displayed as icons on the graphic.
5. If you want to change the background image or the style of the icons or their
labels, edit the graphic view properties.
6. Click Select, then drag icons into position; use this and other graphic view
tools to manipulate the view.
7. If you want to add other Navigator items to the view, drag them from the
Navigator view.
You can drag items one at a time or use Ctrl+click to select multiple items, then
drag them as a group. To select an item to drag without opening it, press Ctrl
before you click it.
8. To keep the graphic view in this workspace for future work sessions, do one of
the following:
v Click Save to update the workspace properties with the new view.
v Select Save Workspace As from the File menu to save this as a new
workspace and leave the original workspace intact.

Chapter 3. Basic product function 59

 Tip: If a new item is displayed on the Navigator after you created the graphic
view, you can add it at any time by dragging its name from the Navigator view to
the graphic view; if an item gets removed from the Navigator after you created the
graphic view, you can remove its icon by selecting it with , then clicking .

More about the Graphic Editor: For additional information and procedures for
using the Graphic Editor, refer to the Graphic Editor section of the online help.
From the Help menu, select Contents and Index. In the Contents pane, click
Customizing Your Environment
Views
Graphic View.

Creating a Business Navigator view

You can use the Navigator Editor to create new Navigator views. You can build a
hierarchical structure within the new Navigator view by sharing items from a
source Navigator view and by creating new items that are not shared.

This lesson shows you how to create a new Navigator view and customize it. The
purpose of this view is to ensure that coffee gets made.

Creating a new view

1. In the Navigator toolbar, click Edit Navigator View.
The Edit Navigator View window opens with the Navigator Physical view as
the Source view (on the right), and the Business view or most recently opened
view as the Target View for editing.
2. Click Create New Navigator View.
A window opens for you to enter the Navigator view identity.
3. Type Coffee as the name for the Navigator and, optionally, a description, then
click OK.
The description is displayed in a flyover message when you move the mouse
over the Navigator view tab at the bottom of the view pane. After you click
OK, the Navigator view name is displayed as the enterprise level item in the
left frame with this icon:

Sharing items
Navigator items are shared by selecting them from the source view on the right,
dragging to the target view, and dropping on the item they follow.
1. Open the Windows Systems branch.
If you do not have Windows Systems, choose another operating platform:
Linux, OS/390® or UNIX.
2. Select your managed system if you can see it; or select another one such as
Primary:MYSYSTEM:NT.
3. Drag and drop it on Coffee.

As you begin to drag, the mouse pointer changes to .

When positioned over the target item, the pointer changes to and a border
is displayed around the item.
Notice the over the icon of the original and copied Navigator items. The
indicates that the following source Navigator item designations are also shared
with the new Navigator item:
v Assigned managed systems
v Defined workspaces

60 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 v Defined links
v Associated situations
From then on, changes to one item (such as editing a workspace) are applied to
the other. The indicator reminds you of this shared relationship so that you
do not unintentionally change or delete an item from one Navigator view that
might affect another Navigator view.

Creating new items

Now create some new items:
1. Select the enterprise item in the target view: Coffee.
2. Click Create Child Item.
3. In the dialog that opens, type the following:
Name: Floor 1
Description: Floor support personnel: Receptionist, Facilities Manager
4. Click OK.
5. Repeat steps 1 to 4, naming the next item Floor 2.
6. Select Floor 1, click Create Child Item, and name the new item Reception.
7. Select a managed system from Available Managed Systems and click to
move them to Assigned, then click OK.
This system is the managed system whose situations you want to associate
with the Navigator item. This assignment has no effect on what data the
workspace for this Navigator item can show, only the event indicators for
situations. If a Navigator item does not have assigned managed systems, no
events are displayed for it unless they are part of a rollup display of events.
The Situation editor is not available from the pop-up menu.

Deleting items
Delete one of the Navigator items:
1. Select the Floor 2 item and click Delete Item.
2. When a message prompts you for reassurance, click OK.
Navigator items are listed in the view in the order in which they are created on
that branch. If you must move an item to a different location, you must delete
it and create it again where you want it to be displayed and in the order in
which it should be displayed.

Renaming items
Rename one of the Navigator items.
1. Right-click Reception (under Floor 1) and select Properties.
2. In the Name field, change the name to Front Desk.
3. Click OK.

Closing the Navigator editor

The Navigator view you just created could be expanded to cover every managed
system where you want a reminder to make coffee. For this exercise, we added
only one managed system.

Click Close to close the Navigator view editor.

Selecting a Navigator view

1. Click the list box down arrow in the Navigator view toolbar.
2. Select Coffee.

Chapter 3. Basic product function 61

 Your new Navigator view opens in place of the Navigator Physical view.
3. Click each Navigator item to open its default workspace.
Except for the system Navigator item, the shared items have defined
workspaces and the new items (Coffee, Floor 1, Front Desk) have undefined
workspaces.

Associating situations
Some items in the Coffee view—the shared items—might have associated
situations, so that when the situation becomes true an event indicator lights up the
Navigator item and the items above it.

The Front Desk Navigator item you created and to which you assigned a managed
system can also show event indicators, but only after situations have been
associated with it.
1. In the Coffee Navigator view, right-click the Front Desk item and select
Situations from the pop-up menu.
2. Click the Situation Filter icon to open the Show Situations window.
3. Select the Eligible for Association check box and click OK.
4. Select a situation from the list.
5. Right-click the situation, then select the Associate icon.
6. Check your work: Click the Situation Filter icon, clear the Eligible for
Association check box, then click OK.
The situation you associated is displayed in the list, but situations that were not
associated with this Navigator item are not displayed.
7. Click OK to close the Situation editor. The next time the situation becomes true,
an event indicator will be displayed over this Navigator item and over its icon
in the graphic view in the Coffee workspace.

62 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Chapter 4. Product administration
Perform the following exercises to explore basic product administration:
v “Exercise 9: Configuring the Summarization and Pruning Agent”
v “Exercise 10: Viewing managed system status and testing the heartbeat” on page
66
v “Exercise 11: Using the CLI” on page 68
v “Exercise 12: IBM Tivoli Enterprise Console integration” on page 70
v “Exercise 13: Filtering and responding to events” on page 76

Exercise 9: Configuring the Summarization and Pruning Agent

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. 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.

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. To change the system-wide default
settings for data summarization or pruning configurations, use the Manage Tivoli
Enterprise Monitoring Services window to make your changes, which affect all
products and attribute groups. 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 GUI.

Changing system-wide configuration settings using the

Manage Tivoli Enterprise Services window
After installing IBM Tivoli Monitoring, use the following steps to change the
system-wide default configuration settings for the Summarization and Pruning
Agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Enterprise
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, click (instead of right-clicking) Warehouse
Summarization and Pruning Agent.
3. Click OK and OK on the Warehouse Summarization and Pruning Agent: Agent
Advanced Configuration windows.
4. Click Yes on the window that prompts you to indicate if you want to configure
the agent.

© Copyright IBM Corp. 2005 63

 5. In the Configure Summarization and Pruning Agent window, do the following
steps:
a. In the Sources tab:
v 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.
v In the list, select DB2 as the type of database that your warehouse is
using.
v Enter the Warehouse URL and Driver information, which might be
completed by default.
v Enter ITMUser as the User ID and marath0n as the password.
v Click Test database connection to ensure that you can communicate with
your warehouse database.
v Take the default settings for the Tivoli Enterprise Portal Server Host and
Port.
b. In the Defaults tab, select the settings for your summarization and pruning
information:
v Click Reset to initial settings at the bottom on the window to see the
initial default settings for all monitoring agents. Whenever you click this
button, you change all settings in this window back to the default
settings.
1) Collection Interval is 5 minutes.
2) The data is being collected at the TEMA- Tivoli Enterprise Monitoring
Agent. (Collection Location).
3) Warehouse Interval is 1 hour.
4) Default summarization settings are set for:
– monthly
– weekly
– daily
– hourly
5) Default pruning settings are set to keep data:
– Monthly for 6 months
– Weekly for 6 months
– Daily for 6 months
– Hourly for 6 months
– Details for 30 days
v Select 15 minutes in the Collection Interval, and leave the Collection
Location and the Warehouse Interval the same.
v Select Weekly, Daily, Hourly as your Summarization settings. Clear
Monthly.
v In the pruning settings change how you want to prune your data:
– Clear Keep monthly data for.

64 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 – In the Keep weekly data for, change 6 to 3.
You can use these settings to keep weekly data for 3 months.
– Keep daily and hourly pruning settings the same.
v Select Apply settings to default attribute groups for all agents to keep
the changes you have made.
c. In the Scheduling tab:
1) Keep Run every 1 days.
2) Select 00:00 in the at field.

Note: Because the time is expressed in military time, 00:00 is midnight.

d. In the Work Days tab:
1) Select Monday in the Week starts on drop-down list.
2) Select Specify shifts.
3) Select 12:00 and click the left arrow to move 12:00 to Off Peak Shift
Hours.
4) Select Specify vacation days.
5) Click Count weekends as vacation and select No.
6) Click Add and choose December 30 as a vacation day in the Add
Vacation Days window.
7) Click OK.
You see 20051230 displayed in the field to the left of the Add and
Delete.
8) After changing information in this tab, when you click another tab, you
get a message that states: If you have already collected summarized
data, changing the shifts can disrupt the continuity of the data
being summarized. Do you want to continue? Click Yes.
e. In the Additional Parameters tab, keep the default settings.
f. Click Save when you have all your settings correct and click Close to close
the window.

Changing the default configuration settings for selected

products and attribute groups
To change any of your configurations by product and attribute group, complete the
following steps:
1. In the Tivoli Enterprise Portal GUI, click History Configuration Collection
that is located on the toolbar. You can also click Edit → History Configuration.
2. In the History Configuration Collection window, select Windows OS as the
product for which you want to change the configurations.

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.
3. Click the Groups column to sort the attribute groups.
4. Click Show Default Groups at the bottom of the window.
5. If you want to select more than the default groups, select any of the NT_
attribute groups for which you want to change configurations.
6. Click Stop Collection.
7. In the Configuration Controls section:

Chapter 4. Product administration 65

 a. Select 5 minutes in the Collection Interval section.
b. Leave TEMA selected in the Collection Location.
Collect data at the agent to minimize performance impact on the
monitoring server from historical data management tasks.
c. Select the interval for the data that you want to collect in the Warehouse
Interval section.
d. Select Weekly as the time period for data summarization in the
Summarization section.

Note: By selecting Weekly, by default, Daily and Hourly are

automatically checked too. Leave all the time periods checked.
e. Select the way that you want to prune your data in the Pruning section:
1) Select Hourly for the time period for the table to be pruned.
2) Type 30 in the next field after keep.
3) Select Days for the pruning time period.
You can use these settings to keep hourly data for 30 days.
8. Click Configure groups to apply the configuration selections to the NT_
attribute groups that you selected.
9. Look at the Select Attribute Groups table to see your changes.
10. Ensure that all the attribute groups you have changed are selected and click
Start Collection.
The Select TEMS window displays with a list of the available servers so that
you can choose a server or servers from which to start collection.
11. Click Refresh Status until all your selections have Started in the Collection
column.
12. Click the Collection column for any of the NT_ attribute groups to see the
servers that are started.
If you have multiple servers for this attribute group, they are displayed here.

How to disable the Summarization and Pruning Agent

To disable summarization and pruning for your entire enterprise:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Enterprise
Services.
2. Right-click Summarization and Pruning Agent.
3. Select Stop from the list of options.

To turn off summarization and pruning for the NT–System attribute group in the
Historical Collection Configuration window:
1. Select the Windows Servers in the Select Attribute Groups window.
2. Select NT_System.
3. Click Stop Collection.
4. Click Unconfigure Groups.

Exercise 10: Viewing managed system status and testing the 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. Within a short time interval after a missed heartbeat, the
monitoring server considers the monitoring agent to be offline. The online or
offline status of the monitoring agent is also called the managed system status.

66 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Use the following procedures to view managed system status in the Tivoli
Enterprise Portal and to test the heartbeat functionality:
v “Viewing managed system status” to verify the online status of the monitoring
agents that you installed on Days 1 to 3 of the workbook.
v “Testing the heartbeat” to take the monitoring agents offline and then verify the
offline status after the heartbeat interval has passed.

Viewing managed system status

Use the following steps to verify the online status of the Windows and UNIX
monitoring agents that you installed:
1. Start the Tivoli Enterprise Portal.
2. Right-click Enterprise in the Navigator Physical 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.

Testing the heartbeat

Use the following steps to test the heartbeat:
1. Take the monitoring agents that you installed offline:
v To take the Windows monitoring agent offline, remove the network cable.
v To take the UNIX agent offline, you must stop the six daemons that make up
the agent. The six daemons are kuxagent, kux_vmstat, stat_daemon, ifstat,
nfs_stat, and iostat. You can stop all daemons by stopping just the main
daemon, which is kuxagent. Follow these steps:
a. Find the product ID (PID) number of the kuxagent daemon:
ps -ef | grep kuxagent
Look for a line in the output similar to the following. In this example, the
PID number of kuxagent is 75560.
root 75560 1 0 12:33:36 pts/3 0:00 /home/candle/bvt/e4/agent/
aix513/ux/bin/kuxagent
b. Stop the kuxagent process:
kill -9 pid

where pid is the PID number of kuxagent.

v For the Linux agent, stop the klzagent daemon.
2. Wait 10 minutes and then manually refresh the Tivoli Enterprise Portal by
pushing F5 (or click View -> Refresh Now).
3. Verify that the agents are offline by following the steps in the preceding section,
“Viewing managed system status.”

Chapter 4. Product administration 67

Exercise 11: Using the CLI
You can now perform the following tasks from the command line interface (CLI):
v “Creating and managing a situation”
v “Starting and stopping an agent” on page 69

Note: Run the tacmd.bat command only once (that is, only when setting up the
environment at the beginning of the exercise.) Thereafter, to avoid
duplications of environment variables, specify tacmd, which runs the
tacmd.exe command.

Each of these commands has more detailed help information than what is
provided in the tasks below. To see all of the parameters and functions for a
command, run the following command:
tacmd help command

where command is the name of the specific command for which you want
information.

Note: On UNIX, run tacmd.sh instead of tacmd.

Creating and managing a situation

Before you do this task, run through the task of creating a basic situation (in
“Creating a situation” on page 43) so that you have a situation to work with.

For this procedure, create a new situation based on the My_Situation situation.
Run the following steps on the computer where you installed the monitoring
server:
1. Open a command line window (or terminal window).
2. Change to the directory where you installed IBM Tivoli Monitoring.
3. Change to the \BIN (Windows) or /bin (UNIX) subdirectory.
4. Run the following command to log into the computer:
For Windows:
tacmd login -s hostname -u sysadmin
For UNIX:
CANDLEHOME=/opt/IBM/ITM; export CANDLEHOME
tacmd.sh login -s hostname -u sysadmin

where hostname is the host name of your monitoring server.

5. Press Enter when you are prompted for a password. Do not type a password.

Note: You might still see a blinking cursor after you press Enter. Do not press
Enter again. Wait a few minutes for the command to process.
6. Run the following command to export the details of my_situation to a file:
tacmd viewSit -s My_Situation -e viewmysituation.out
7. Edit the output file in a text editor to change one situation variable - Interval.
Change the following values:
SITNAME
Change from My_Situation to new_situation
REEV_TIME
Change from 000030 to 001500

68 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 8. Run the following command to create the new situation.
tacmd createSit -i viewmysituation.out

To view your new situation, you can either run the tacmd viewSit command
again, using the new situation name, or open the Tivoli Enterprise Portal and look
there.

To view all of the situations on your monitoring server, run the following
command:
tacmd listSit

Now we’ll delete new_situation. Run the following command:

tacmd deleteSit -s new_situation -f

The -f parameter prevents a confirmation from displaying before the situation is

deleted.

You can use the preceding commands to export a situation from one monitoring
server and import it on another. To import a situation from Computer A to
Computer B do the following steps:
1. On Computer A, where the situation already exists, run the tacmd viewSit -s
situation_name -e filename command.
2. Transfer the output file to Computer B.
3. On Computer B, where you want to create the situation, run the tacmd
createSit -i filename command. If a situation with the same name does not
already exist on Computer B, you need not edit the output file to change the
situation name (as in the preceding procedure).

Starting and stopping an agent

Run the following command to stop an agent:
tacmd stopAgent -t type

where type is one of the following two-letter agent identifiers:

nt Identifies the Windows operating system agent.
ux Identifies the UNIX operating system agent.
lz Identifies the Linux operating system agent.

This command stops all agents of the specified type on the monitoring server. You
are prompted for confirmation before the agents are stopped.

Run the following command to start that same agent:

tacmd startAgent -t type

This command starts all agents on the monitoring server. Again, you are prompted
for confirmation before the agents are started.

Viewing what your monitoring server is monitoring

You can use the commands to view the IBM Tivoli Monitoring components and
systems that are being monitored by the monitoring server.

Use ListSystems to view a list of managed systems (both computers themselves

and the applications and resources that you are monitoring).

Chapter 4. Product administration 69

 tacmd listSystems

Exercise 12: IBM Tivoli Enterprise Console integration

If your monitoring environment is configured for the IBM Tivoli Enterprise
Console, you can forward situation events to the Tivoli Enterprise Console event
server and view events on the event server through the Tivoli Enterprise Portal.

If you want to view Tivoli Enterprise Console events (and not IBM Tivoli
Monitoring events) only, you need not install the event synchronization or
configure event forwarding.

Table 9 outlines the features of the IBM Tivoli Enterprise Console integration and
the required steps to use those features.
Table 9. IBM Tivoli Enterprise Console integration
Goal Where to find information
Send IBM Tivoli Monitoring events to Tivoli “Installing the IBM Tivoli Enterprise Console
Enterprise Console and keep the situation event synchronization”
events displayed in the Tivoli Enterprise
Portal in synch with updates made on the
event server.
Forward situation events from the “Configuring your monitoring server to
monitoring server to the event server. forward events” on page 72
View events (both situation events from IBM “Configuring a Tivoli Enterprise Console
Tivoli Monitoring and other events on the view” on page 73
event server) through the Tivoli Enterprise
Portal.

Installing the IBM Tivoli Enterprise Console event

synchronization
If you want to view updates to events from IBM Tivoli Enterprise Console in the
Tivoli Enterprise Portal, you must install the event synchronization component on
the event server.

Information to gather before you begin

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

70 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 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.

Installing event synchronization on the event server

Use the following steps to install event synchronization on your IBM Tivoli
Enterprise Console event server.

Note: After you install the event synchronization, your event server is recycled.
1. Launch the event synchronization installation:
v On Windows, double-click the setupwin32.exe file in the \TEC subdirectory
on the IBM Tivoli Monitoring installation media.
v On Linux or UNIX, change to the /os_type/TEC subdirectory of the IBM
Tivoli Monitoring installation media, where os_type is the one of the
following operating types that corresponds to the installation CD that you
are using:
– “unix” for AIX and Solaris
– “hpux” for HP-UX
– “xlinux” for Linux for Intel®
– “zlinux” for Linux for z/OS
Run the following command:
setup operating system.bin

where operating system is the operating system on which you are installing.
For example, run the following command on an AIX computer:
setupAix.bin.
2. Click Next on the Welcome window.
3. Select I accept the terms in the license agreement and click Next.
4. Click Next to accept the default configuration values.
5. Click Next to accept the default values for the files where events will be
written.
6. 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.

Chapter 4. Product administration 71

 Confirmation
The password, again.
7. When you have provided information about all of the monitoring servers,
click Next.
8. Specify the rule base that you want to use to synchronize events. You have
two choices:
v Create a new rulebase
v Use existing rulebase
9. 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.
10. If you are using an existing rule base, type the name of the rule base.
11. 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.
12. Click Next.
13. Click Next on the preinstallation summary panel.
The installation begins.
14. When the installation and configuration steps are finished, 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.

Configuring your monitoring server to forward events

Before you can view situation events in the event view, you must perform the
following configuration steps:
1. For Windows monitoring servers only, open Manage Tivoli Enterprise
Monitoring Services.
Do the following steps in Manage Tivoli Enterprise 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 OK.
d. Complete the following fields on the TEC Server: Location and Port
Number window and click OK:
TEC Server Location
Type the host name or IP address for the computer where the IBM
Tivoli Enterprise Console event server is installed.
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.

72 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 2. For UNIX monitoring servers: You configured the TEC Server and TEC Port
information for the UNIX monitoring server during installation, if you installed
the monitoring server using the configuration instructions in this workbook.
However, if you did not configure this information, see “Configuring the
monitoring server” on page 20 for the procedure.
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 is stopped automatically, you can just start it.)

Configuring a Tivoli Enterprise Console view

Use the following steps to add the Tivoli Enterprise Console view:
1. Open the Enterprise Status workspace.
2. Click File → Save Workspace as and name the new workspace Enterprise TEC.
3. Click OK.
4. Click , then click inside the bar chart (Open Situation Counts — Last 24
hours).
5. In the Tivoli Enterprise Login window that opens, configure the view for your
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.

What the view shows

The following sections describe the view.

Tivoli Enterprise Console view and console toolbars

This tool opens the Preferences window. The changes you make are
for your user ID and affect this and all new Tivoli Enterprise
Console views. General preferences set the refresh rate for
displaying new events, the age of closed events to display, and the
number of events to display. The Working Queue/All Events
preferences determine the column sort order in the Working Queue
and All Events queue. Severity Colors preferences determine
whether or not flyover and column highlighting are activated, and
what colors to use for event severity.
This tool opens a window for configuring automated tasks, which
run when a particular event is received by the event console. For
example, you can configure an automated task to send an e-mail
message to an administrator when an event matching the criteria
you defined ahead of time is received by the event console.

Chapter 4. Product administration 73

 When an automated task completes, it issues information about its
success or failure and any results created by the task. An icon is
displayed in the Task Completion column of the Event Viewer
when an automated task completes. You can double-click this icon
to view the task results. This icon also is displayed for rule-based
tasks that have completed. Automated task results are written to a
text file, which is configured in the Console Properties editor for
each console.
This tool is used to refresh the view. A query is sent to the event
database and the results are displayed in the view.
Use this tool to open the Automated Task window for viewing,
editing, creating, and deleting automated tasks.

These tools show the number of events for each severity and
enable you to filter out Unknown, Harmless, Warning, Minor,
Critical, or Fatal events or any combination thereof. The example
here shows that Harmless events have been excluded and the
number received is 0. These are toggle tools: click again to resume
display of that event severity.

These tools filter events by their status: Open, Response,

Acknowledged, and Closed. These are toggle tools: click again to
resume display of events of that status.

These tools hide the events for your user ID or those of all other
operators signed on to the event server. These are toggle tools:
click again to resume display of the events for your user ID or
other operators.
This tool is used to retrieve new and updated events. If no events
were selected in the Working Queue, it is updated. If any events
are selected in the Working Queue, the Tivoli Enterprise Console
icon button is available in the row of buttons at the bottom of the
Working Queue. Click the button to refresh the Working Queue
with new updates. This button applies only to the Working Queue.
The All Events queue is updated immediately upon retrieval.
An automated task is configured ahead of time and run when a
particular event is received by the event console. For example, you
can configure an automated task to send an e-mail message to an
administrator when an event matching the criteria you defined
ahead of time is received by the event console. Automated tasks
are configured using the Automated Tasks menu in the Event
Viewer.
When an automated task completes, it issues information about its
success or failure, and any results created by the task. The
task-completion icon is displayed in the first column of the Event
Viewer when an automated task completes. You can double-click
this icon to view automated task results.
Buttons Select an event row (Figure 21 on page 75) to enable the buttons to
Acknowledge the event, Close the event, open a tabbed window
with event Details, or to display Information about the event. The

74 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Refresh icon is disabled when no events have arrived since the
last refresh of the view, and enabled when new events have
arrived.

Figure 21. Tivoli Enterprise Console view

Forwarding events
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.
Thus, you can see events and any actions taken such as acknowledgements, from
any location in your network that these servers monitor.

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 (located in <install_dir>\cms\TECLIB\ on Windows and
<install_dir>/tables/<ms_name>/TECLIB on UNIX), if the situation and
appropriate severity is defined in it
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.

Saving the Tivoli Enterprise Console view

Your Enterprise TEC workspace shows the three different types of event tables
available: Tivoli Enterprise Console; situation event console; and message log.
Complete the workspace by hiding the Navigator view and adding another Tivoli
Enterprise Console view that filters the events differently.

Chapter 4. Product administration 75

 To hide the Navigator view, select View and Show Navigator Item, which should
not be checked.

Use the following steps to split the situation event console view and add another
enterprise console view:
1. Click in the situation event console view toolbar.
2. Click , then click inside the situation event console view on the left.
3. In the Tivoli Enterprise Console Configure window, select an event group for
the Filter Type and the name of a specific group for Filter Name. Click OK.
4. Click to save the workspace with the Navigator view collapsed and with
the two new Tivoli Enterprise Console views.

Exercise 13: Filtering and responding to events

Today you can work with some of the enterprise console display features and
activities.

Opening the Enterprise TEC workspace

Use the following steps to open the workspace you created yesterday:
1. If it is not already displayed, open the Enterprise Status workspace by clicking
the Enterprise item at the top of the Navigator view.
2. Right-click the Enterprise item and click Workspace → Enterprise TEC.
3. In the Tivoli Enterprise Login window that opens, complete the following
fields:
a. Host is host_computer_name:94 (default port number or change to the
number used by your managed node).

Note: Use the same event server that you specified when you configured
the Tivoli Enterprise Console view.
b. Name is your Tivoli Management Framework login ID.
c. Password is your Tivoli Management Framework login password.
The Enterprise TEC workspace is displayed.

Acknowledging an event
Use the following steps to acknowledge an open event:
1. Click a row inside one of the Tivoli Enterprise Console views that has an event
showing Open in the Status column.
2. 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.
3. Click Maximize in the event console view toolbar so that you can better
observe the activities in this view.

Filtering events
Use the following steps to filter the events:

1. Click each of the filters: once to hide the events of that

severity, and again to show them.

76 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 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

2. Click each of the filters: once to hide the events of that

status─Open, Response, Acknowledged, Closed─and again to show them.

3. Click each of the filters: once to hide your events or other operators’,
and again to show them.

Closing an event
Use the following steps to close the acknowledged event:
1. If it is not selected, click the row of the event you just acknowledged.
2. 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 4. Product administration 77

78 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
Chapter 5. Advanced features
Perform the following exercises to explore additional advanced features of IBM
Tivoli Monitoring:
1. “Exercise 14: Performing an upgrade from Tivoli Distributed Monitoring”
2. “Exercise 15: Creating embedded situations” on page 96
3. “Exercise 16: Configuring Hot Standby” on page 97
4. “Exercise 17: Creating a custom monitor from a script” on page 99
5. “Exercise 19: Reviewing the problem determination information” on page 102

Exercise 14: Performing an upgrade from Tivoli Distributed Monitoring

This section of the workbook describes an upgrade scenario that you can perform
in a test environment.

Software requirements for the test scenario

Table 10 shows the setup you need in your test environment to perform the test
scenario:
Table 10. What you need for the test scenario
Infrastructure setup Required software
The Tivoli management region in your test The following software must be installed on
environment must include the following your Tivoli server:
Tivoli infrastructure components: v Tivoli Management Framework, version
v A Tivoli management region server on a 3.7 or higher
Windows or UNIX system v Java for Tivoli, version 1.3.0 or higher, or
v A gateway system where Tivoli IBM JRE version 1.4.2
Distributed Monitoring is installed. The v Tivoli Distributed Monitoring, version 3.7
gateway can reside on the Tivoli server or
v The w2k_Memory Monitoring Collection
on a separate managed node.
v A Windows endpoint that is assigned to
the gateway
In addition, you need the hub Tivoli Enterprise Monitoring Server and Tivoli Enterprise
Portal Server that you already installed in preparation for this exercise. See “Tivoli
Distributed Monitoring upgrade environment” on page 5.

To keep the upgrade simple, the test scenario describes the steps for upgrading
from a Tivoli management region where Tivoli Distributed Monitoring is installed
on only one gateway. A single Windows endpoint is assigned to the gateway.
However, you need not duplicate this setup in your test environment. If you have
a Tivoli management region with multiple gateways or endpoints where Tivoli
Distributed Monitoring is running, you can simulate the environment of the test
scenario by using a sample infrastructure file that is provided in the upgrade
toolkit.

During the test scenario, you use a script provided with the toolkit to create and
distribute a Tivoli Distributed Monitoring profile to a Windows endpoint. You can
distribute the profile to an existing Windows endpoint that already has other
profiles, or you can create or use a clean endpoint. The advantage of using a clean

© Copyright IBM Corp. 2005 79

 endpoint is that it reduces the time it takes for the upgrade tools to operate on the
endpoint and it limits the size of the output files.

Information to gather before you begin

Perform the following activities to prepare for the test scenario:
1. Identify the Tivoli server, gateway, and Windows endpoint in your test
environment that you want to use for the test scenario. Optionally create a
clean Windows endpoint on the gateway.
2. Verify that the required software is installed on the Tivoli server.
3. Gather the information listed in Table 11 about the Tivoli infrastructure
components that you are using for the test scenario.
Table 11. Information to gather about Tivoli infrastructure components to use for the test scenario
Information to gather Notes
Tivoli server name Use the following Tivoli commands to look up the names (labels) of Tivoli
infrastructure components and the operating systems of endpoints:
v To look up the names (labels) of the Tivoli server and policy region, type:
wlookup -r ManagedNode -a -L
Policy region name for region that wlookup -r PolicyRegion -a -L
contains the gateway and Windows
endpoint that you want to use for the v To list the names (labels) of all gateways and their assigned endpoints,
test scenario type:
wep ls

In the following sample result, gw1 is the gateway label and ep1 is the
Gateway name name of an endpoint assigned to the gateway:
G 150509384.1.593 gw1
150509384.2.522+#TMF_Endpoint::Endpoint# ep1
v To list the operating systems of all endpoints assigned to a particular
Name of the Windows endpoint gateway, type:
assigned to the gateway
wep ls -g gateway_label -i interp

where gateway_label is the name of the gateway.

Fully qualified host name of the An example of a fully qualified host name is fso66.testlab.abc.com.
Tivoli server
Fully qualified host name of the
endpoint

4. Gather the information listed in Table 12 about the hub Tivoli Enterprise
Monitoring Server and Tivoli Enterprise Portal Server that you installed in
preparation for this exercise. (See “Tivoli Distributed Monitoring upgrade
environment” on page 5.)
Table 12. Information to gather about the IBM Tivoli Monitoring infrastructure components to use for the test scenario
Information to gather Notes
Hub monitoring server name When you installed the hub Tivoli Enterprise Monitoring Server, you
selected the default name for the server. The default name is HUB_hostname,
Fully qualified host name of the where hostname is the short host name of the server.
Windows computer where the hub
monitoring server and portal server For example, if itmserv16.lab.company.com is the fully qualified host name
are installed of the computer where the hub monitoring server is installed, the default
name for the server is HUB_itmserv16.

80 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Overview of test scenario steps
Table 13 describes the high-level steps for the test scenario.
Table 13. Overview of steps for the test scenario
Steps Description
1 Install the upgrade toolkit on the Tivoli server.
2 Create Tivoli Distributed Monitoring managed resources for the test scenario.
3 Use the Scan tool (witmscantmr command) from the upgrade toolkit to create an
infrastructure road map. The infrastructure road map is an output file that maps
the Tivoli management region infrastructure (Tivoli server, gateways, and
endpoints) to IBM Tivoli Monitoring infrastructure components (Tivoli Enterprise
Monitoring Servers and Tivoli Enterprise Monitoring Agents). The Scan tool
ignores gateways and endpoints where Tivoli Distributed Monitoring is not
running.
4 Install IBM Tivoli Monitoring servers based on the infrastructure road map. After
the servers are installed, run the Scan tool to verify the installation and update
the status of the upgrade.
5 Upgrade endpoints. Use the Assess tool (witmassess command) from the upgrade
toolkit to determine which operating system monitoring agents are required on
the endpoints. Then use the Upgrade tool (witmupgrade command) to deploy the
monitoring agents.
6 Upgrade profiles and profile managers. Use the Assess and Upgrade tools to
create situations and managed system lists.
7 Complete the test scenario. Perform final verification and cleanup activities.

Note: You can usually determine the number and types of IBM Tivoli Monitoring
servers to install (Step 3) before you install the servers (Step 4). However,
because the test scenario simulates a very small Tivoli management region,
it is known in advance that you can use the single Tivoli Enterprise
Monitoring Server and Tivoli Enterprise Portal Server that you already
installed in preparation for this exercise. See “Tivoli Distributed Monitoring
upgrade environment” on page 5.

Conventions used in these instructions

The instructions for the test scenario use the UNIX convention for system
commands and for directory notation.

When using the Windows command line, replace $directory with %directory% and
replace each forward slash (/) with a backslash (\) in directory paths. Also, replace
the names of UNIX system commands with Windows commands where needed.
For example, replace mv with rename.

Table 14 lists the long and short names of IBM Tivoli Monitoring components:
Table 14. Long and short names of components
IBM Tivoli Monitoring component Short name
Hub Tivoli Enterprise Monitoring Server hub monitoring server
Remote Tivoli Enterprise Monitoring Server remote monitoring server
Tivoli Enterprise Portal Server portal server
Tivoli Enterprise Monitoring Agent monitoring agent

Chapter 5. Advanced features 81

 The phrase Tivoli infrastructure component refers to a component of the Tivoli
Management Framework environment, such as a Tivoli server or gateway.

Installing the upgrade toolkit

The IBM Tivoli Monitoring V6.1 Upgrade Toolkit is included in the IBM Tivoli
Monitoring V6.1.0 eAssembly Multiplatform Multilingual eAssembly package, which is
available from the IBM Passport Advantage® Web site. You can also install the
toolkit from physical CDs if they are available.

The upgrade toolkit is contained in three CDs or CD images. For the test scenario,
you need only the CD or CD image entitled IBM Tivoli Monitoring V6.1.0 Upgrade
Toolkit: Base Install and Windows Support. The Base Install CD contains the upgrade
tools. The other CDs support UNIX and Linux endpoints, which are not used in
the test scenario. The instructions that follow describe how to install files from the
Base Install CD image.

Note: The file that you download from the Passport Advantage site for the Base
Install image is named C86H41E.tar. In these instructions, the file is renamed
to upgradetools.tar.

Follow these steps to install the upgrade toolkit on the Tivoli server:
1. Log on to the Tivoli server and set up the Tivoli environment variables:
v If the Tivoli server is on a UNIX operating system, enter the following
commands:
bash
. /etc/Tivoli/setup_env.sh
v If the Tivoli server is on a Windows operating system, do one of the
following:
– From a bash shell, enter the following command:
.$SystemRoot/system32/drivers/etc/Tivoli/setup_env.sh
– From a Windows command prompt, enter the following command:
%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
2. Create a directory on the Tivoli server where you can place the toolkit image
file. For example:
cd /usr
mkdir toolkit
3. Download the image file (C86H41E.tar) directly from the Passport Advantage
Web site or copy it from its current location.
The following example uses FTP commands to copy the image file (renamed
upgradetools.tar) from a remote server (host name remote.lab.company.com) to
the /usr/toolkit directory on the local Tivoli server. All commands are issued
from the Tivoli command line:
cd /usr/toolkit
ftp remote.lab.company.com
bin
get toolkit_location/upgradetools.tar
quit

where toolkit_location specifies the path name of the directory on the remote
server that contains the TAR file. For example, if the toolkit is located in the
C:\itm61\ directory on a remote Windows server, type:
get C:\itm61\upgradetools.tar
4. Unzip the compressed file:

82 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 tar -xvf upgradetools.tar
5. Use the Tivoli winstall command to install the toolkit:
winstall -c toolkit_dir/BASE -i OPMT -y

where:
-c toolkit_dir/BASE
Specifies the full path name of the directory that contains he Base Install
product index file (OPMT.IND), for example: -c /usr/toolkit/BASE. On
Windows systems, enclose the path name in double quotes, for
example:
-c ″C:\toolkit\BASE″
-i OPMT
Specifies the product index file, OPMT.IND, from which the toolkit is
installed.
-y Installs the product without requesting confirmation.
6. Enter the following command to complete the installation:
wchkdb -u
7. After the installation is complete, enter the following command to set the Java
path for the upgrade toolkit:
witmjavapath your/jre/bin

where your/jre/bin is that path to the Java binary files for either Tivoli for Java
1.3.x or IBM JRE 1.4.2. The following example sets the Java path to Java 1.3.0
on a Windows system:
witmjavapath "C:\Program Files\Tivoli\bin\w32-ix86\JRE\1.3.0\jre\bin"

Creating managed resources for the test scenario

When you uncompressed the toolkit image file, the following directory was created
on your Tivoli server:

toolkit_dir/BASE/SAMPLES

where toolkit_dir is the directory where you uncompressed the toolkit file.

The toolkit_dir/BASE/SAMPLES directory includes a shell script (config.sh) and a

data input file (config.conf) to create the Tivoli managed resources listed in
Table 15. The shell script subscribes the profile manager to a Windows endpoint
that you specify and distributes the profile to the endpoint.
Table 15. Managed resource configurations used in the test scenario
Managed resource Name
One profile manager DM_TEST_PM
One Tivoli Distributed Monitoring profile in DM_TEST_PROF
the profile manager
One monitor in the profile Available Bytes (AvailBytes) from the
w2k_Memory monitoring collection. The
monitor defines a Critical and a Warning
threshold.

Do the following steps to create and distribute the managed resources listed in
Table 15:

Chapter 5. Advanced features 83

 1. Change to the toolkit_dir/BASE/SAMPLES directory and open the input data
file, config.conf, for editing. The data file contains the following lines:
# policy region in which to create the profile manager
REGION=indint02-region

# name of Windows endpoint to use for this demo

NT_EP=w2k
2. Change indint02-region to the name of your policy region.
3. Change w2k to the name of the Windows endpoint where you want to
distribute the profile.
The Windows endpoint must be connected to a gateway where Tivoli
Distributed Monitoring is installed.
4. Save and close the input data file.
5. Enter the following commands to run the config.sh script from a bash shell:
bash
config.sh

Creating an infrastructure road map: baseline file

The Scan tool surveys the Tivoli management region and produces an XML output
file that describes a proposed equivalent IBM Tivoli Monitoring infrastructure
layout in a hierarchical map. The output file from the initial scan is called the
baseline file. Later scans produce output files that validate the progress of the
infrastructure upgrade.

To complete the infrastructure road map, edit the baseline file to include specific
information for IBM Tivoli Monitoring components, such as host names for hub
and remote monitoring servers and managed system names. You can add or
remove XML elements to change the proposed infrastructure layout.

To create a baseline file, run the Scan tool against your actual test environment.
However, in subsequent steps you will substitute the sample baseline file provided
with the toolkit so that you can simulate an upgrade of the infrastructure used for
the test scenario: a Tivoli management region with one Tivoli Server, one gateway,
and one Windows endpoint assigned to the gateway.

Creating the baseline file

Follow these steps to run the Scan tool (witmscantmr command) and create a
baseline file:
1. Log on to the Tivoli server and source the Tivoli environment.
2. Enter the following command from any directory:
witmscantmr -c

where -c indicates that you are creating a baseline file.

The resulting baseline file is named tmroid.xml, where tmroid is the OID (object
ID) number that uniquely identifies the Tivoli management region. The baseline
file is placed in the following directory:

$DBDIR/AMX/shared/analyze/scans

where $DBDIR is the path name of the object database directory.

In the following example path name, the baseline file is named 1505093874.xml.
The object database directory ($DBDIR) is /usr/Tivoli_94/db/martin.db.
/usr/Tivoli_94/db/martin.db/AMX/shared/analyze/scans/1505093874.xml

84 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 3. Open and examine the tmroid.xml file.
The tmroid.xml file describes a proposed IBM Tivoli Monitoring infrastructure
that matches your actual test environment.

Analyzing the baseline file

Figure 22 shows the sample baseline file that is provided with the upgrade toolkit.
The sample baseline file (named baseline.xml) is located in the
toolkit_dir/BASE/SAMPLES directory, where toolkit_dir is the directory to which
you uncompressed the toolkit image file.

Because the baseline.xml file is a sample file, the italicized items in Figure 22 are
placeholders for information that you must provide. In a real baseline file (such as
the tmroid.xml file that you created in the previous step), this information is
automatically supplied by the Scan tool.

<?xml version="1.0" encoding="UTF-8"?>

<!--Copyright IBM Corporation 2005-->
<ITM6.1Infrastructure aggregateStatus="INCOMPLETE"
xmlns="http://www.ibm.com/Tivoli/ITM/scantmr"
xmlns:itmst="http://www.ibm.com/Tivoli/ITM/MigrateStatus"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="h
ttp://www.ibm.com/Tivoli/ITM/scantmr tmr.xsd">
<HubServer aggregateStatus="INCOMPLETE" hostname="server0.hub.com:1918"
hub_installDir="" protocol="IP.PIPE" source="ServerManagedNode:MYTMR"
status="NOT_DEPLOYED" target="Hub:HUB_Server0" tec_forwarding_endpoint=""
unix_OSAgent_installDir="/opt/IBM/ITM/" windows_OSAgent_installDir="C:\IBM\ITM\">
<SOAPConnectionInfo SOAPencoding=""
hostname="server0.hub.com:1920" password=""
status="NOT_DEPLOYED" user="SYSADMIN"/>
<PortalServerInfo hostname="portalserver0.portal.com:1920" password=""
status="NOT_DEPLOYED" user="SYSADMIN"/>
<RemoteServer aggregateStatus="INCOMPLETE"
hostname="server0.remote.com:1918" protocol="IP.PIPE" source="Gateway:mygateway"
status="NOT_DEPLOYED" target="Remote:REMOTE_Server0"
unix_OSAgent_installDir="" windows_OSAgent_installDir="">
<OSAgent hostname="myendpoint.lab.company.com"
osAgent_installDir="" interp="w32-ix86"
locale="US" source="Endpoint:MYENDPOINT"
status="NOT_DEPLOYED" target="ManagedSystem:myendpoint"/>
</RemoteServer>
</HubServer>
</ITM6.1Infrastructure>

Figure 22. Unedited sample baseline file (baseline.xml)

Baseline file characteristics: The nesting of XML elements defines a logical

hierarchy of IBM Tivoli Monitoring infrastructure components. In this example
(Figure 22 ), reading from the bottom of the file upward, an operating system
monitoring agent reports to a single remote monitoring server, which reports to a
single hub monitoring server.

Whenever you run the Scan tool, the status and aggregateStatus attributes show
the progress of the upgrade. Before the baseline file is edited, the upgrade tools
cannot determine whether any servers or agents were deployed. For this reason,
the initial status shows that they are not deployed.

Each of the XML elements that represents an IBM Tivoli Monitoring component
contains a source attribute that identifies the Tivoli infrastructure component to be

Chapter 5. Advanced features 85

 replaced or upgraded. For example, the <HubServer> element in Figure 22 on page
85 contains the reference source="ServerManagedNode:MYTMR", which identifies the
Tivoli server named MYTMR. This mapping indicates that the Tivoli server named
MYTMR (the source) is replaced by a hub monitoring server (the target) whose host
name you add when you edit the baseline file.

The source-to-target mapping of servers in the sample baseline file is one-to-one.

Preferred server mappings for larger Tivoli management regions might include
one-to-many relationships. For example, the Tivoli server might map to multiple
hub servers (indicated by multiple <HubServer> elements with the same source).
Similarly, a Tivoli gateway might map to multiple remote servers. The Scan tool
ignores gateways that do not run Tivoli Distributed Monitoring.

<OSAgent> elements identify the computers where you deploy operating system
monitoring agents. You want to deploy operating system monitoring agents to
existing endpoints so that you can monitor resources on those computers.
Therefore, the Scan tool automatically adds the endpoint host names (and other
endpoint information) to the <OSAgent> elements. The Scan tool includes <OSAgent>
elements only for endpoints that run Tivoli Distributed Monitoring.

In contrast, the Scan tool does not add host names (or other information) for the
hub and remote monitoring servers. Add this information yourself when you edit
the baseline file. In these cases, the assumption is that you do not want to install
the hub or remote monitoring servers on computers that currently host the Tivoli
server or a gateway. However, no technical reason prevents you from installing
IBM Tivoli Monitoring components on existing Tivoli server or Tivoli gateway
hardware. You might want to leverage existing hardware to save resources.

Editing the baseline file

The purpose of editing the baseline file is to produce an accurate representation of
the IBM Tivoli Monitoring environment that you want to deploy. The completed
baseline file is used as input to later upgrade procedures that deploy agents, verify
connectivity, and update status. When you edit the baseline file, you make the
following changes:
v Specify missing information, such as the host names of the hub and remote
monitoring servers.
v Optionally change the suggested deployment of IBM Tivoli Monitoring
components. For example, you might want to add or delete monitoring servers.
Follow these steps to edit the baseline file for the test scenario:
1. Copy the sample baseline file (baseline.xml) from the
toolkit_dir/BASE/SAMPLES directory to the
$DBDIR/AMX/shared/analyze/scans directory (where toolkit_dir is the
directory to which you uncompressed the toolkit image file). For example:
cd $DBDIR/AMX/shared/analyze/scans
cp /usr/toolkit/BASE/SAMPLES/baseline.xml
2. Open the sample baseline.xml file for editing.
3. Replace the italicized placeholder items in Figure 22 on page 85 and with actual
names from your environment. The placeholder items in this step identify the
Tivoli infrastructure components from which you are upgrading. Note that
when you edit a real baseline file, this step is not necessary because the
information is automatically supplied by the Scan tool.
Table 16 on page 87 lists the attribute values to be replaced (in italics). You
gathered the information that you need for the replacement values at the start
of the test scenario. See Table 11 on page 80.

86 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 16. Placeholder information for Tivoli infrastructure components used in the test scenario
Element and attribute in the unedited baseline file Replacement for placeholder attribute value
<HubServer source="ServerManagedNode:MYTMR" The name of the Tivoli server
<RemoteServer source="Gateway:mygateway" The name of the gateway
<OSAgent hostname="myendpoint.lab.company.com" The fully qualified host name of the Windows endpoint
assigned to the gateway
<OSAgent source="Endpoint:MYENDPOINT″ The name of the endpoint
<OSAgent target="ManagedSystemName:myendpoint The name of the endpoint

4. Replace the non-italicized placeholder items in Figure 22 on page 85 with actual

names from your environment. In contrast to Step 3 on page 86, this step is
necessary when you are editing a real baseline file because the information is
not supplied by the Scan tool.
The placeholder items in this step represent the Tivoli Enterprise Monitoring
Server and Tivoli Enterprise Portal Server that you installed earlier to prepare
for this exercise. (See “Tivoli Distributed Monitoring upgrade environment” on
page 5.) The Tivoli Enterprise Monitoring Server was configured as a hub
monitoring server even though it is not connected to any remote monitoring
servers.
Table 17 lists the attribute values to be replaced (between quotation marks). You
gathered the information that you need for the replacement values at the start
of the test scenario. See Table 12 on page 80.
Table 17. Placeholder information for IBM Tivoli Monitoring infrastructure components used in the test scenario
Element and attribute in the unedited baseline file Replacement for placeholder attribute value
<HubServer hostname="server0.hub.com:1918" The fully qualified host name of the Windows system
that hosts the hub monitoring server and the port that
the hub monitoring server uses to communicate with OS
monitoring agents and other IBM Tivoli Monitoring
servers. Use the default port, 1918.
<HubServer target="Hub:HUB_Server0" The default name of the hub monitoring server

The default name is HUB_Server0, where Server0 is the

short host name of the monitoring server. For example, if
the hostname attribute for the hub server is
hostname=itmserv16.lab.company.com, specify
target="Hub:HUB_itmserv16".

<SOAPConnectionInfo hostname="server0.hub.com:1920" The fully qualified host name of the hub monitoring
server and the port used for SOAP communications. Use
the default port, 1920.

The upgrade tools communicate with the hub monitoring

server through IBM Tivoli Monitoring Web Services
(SOAP server). When you installed the hub monitoring
server, the SOAP service was enabled by default on port
1920.
<PortalServerInfo The fully qualified host name of the computer that hosts
hostname="portalserver0.portal.com:1920" the Tivoli Enterprise Portal Server and the port that the
upgrade tools use to communicate with the portal server.
Use the default port, 1920. Type the same host name that
you entered for the hub monitoring server.

Chapter 5. Advanced features 87

Table 17. Placeholder information for IBM Tivoli Monitoring infrastructure components used in the test
scenario (continued)
Element and attribute in the unedited baseline file Replacement for placeholder attribute value
<RemoteServer Because the test scenario does not include a remote
hostname="server0.remote.com:1918" monitoring server, use the same hostname and target
target="Remote:REMOTE_Server0" attribute values that you specified for the hub monitoring
server (first two rows of this table). For example:
<RemoteServer
hostname="itmserv16.lab.company.com:1918
"target="Remote:HUB_itmserv16"

The output of the initial scan always produces a baseline file that maps each
gateway to at least one remote monitoring server. If the load on one or more
gateways is small, the resulting IBM Tivoli Monitoring infrastructure layout might
include more remote servers than necessary. In the test scenario, the load is small
enough to eliminate the remote server entirely. Managed systems can be monitored
directly from the hub server. To eliminate the remote server from the proposed
IBM Tivoli Monitoring infrastructure map in this scenario, type the same name on
the target attribute of both the <HubServer> and <RemoteServer> elements.

Your edited baseline file should be similar to the one shown in Figure 23:

<?xml version="1.0" encoding="UTF-8"?>

<!--Copyright IBM Corporation 2005-->
<ITM6.1Infrastructure aggregateStatus="INCOMPLETE"
xmlns="http://www.ibm.com/Tivoli/ITM/scantmr"
xmlns:itmst="http://www.ibm.com/Tivoli/ITM/MigrateStatus"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="h
ttp://www.ibm.com/Tivoli/ITM/scantmr tmr.xsd">
<HubServer aggregateStatus="INCOMPLETE" hostname="itmserv16.lab.company.com:1918"
hub_installDir="" protocol="IP.PIPE" source="ServerManagedNode:TMR1"
status="NOT_DEPLOYED" target="Hub:HUB_ITMSERV16" tec_forwarding_endpoint=""
unix_OSAgent_installDir="/opt/IBM/ITM/" windows_OSAgent_installDir="C:\IBM\ITM\">
<SOAPConnectionInfo SOAPencoding=""
hostname="itmserv16.lab.company.com:1920" password=""
status="NOT_DEPLOYED" user="SYSADMIN"/>
<PortalServerInfo hostname="itmserv16.lab.company.com:1920" password=""
status="NOT_DEPLOYED" user="SYSADMIN"/>
<RemoteServer aggregateStatus="INCOMPLETE"
hostname="itmserv16.lab.company.com:1918" protocol="IP.PIPE" source="Gateway:gw1"
status="NOT_DEPLOYED" target="Remote:HUB_ITMSERV16"
unix_OSAgent_installDir="" windows_OSAgent_installDir="">
<OSAgent hostname="ep1.lab.company.com"
osAgent_installDir="" interp="w32-ix86"
locale="US" source="Endpoint:EP1"
status="NOT_DEPLOYED" target="ManagedSystem:ep1"/>
</RemoteServer>
</HubServer>
</ITM6.1Infrastructure>

Figure 23. Edited baseline file (baseline.xml)

88 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Installing the IBM Tivoli Monitoring servers and updating
status
You already completed the step of installing a Tivoli Enterprise Monitoring Server
and a Tivoli Enterprise Portal Server earlier in preparation for this exercise. (See
“Tivoli Distributed Monitoring upgrade environment” on page 5.) At this point,
run the Scan tool again to verify connectivity to the servers that you installed and
to update the status of the infrastructure upgrade. In an upgrade that involves
several hub or remote monitoring servers, it is good practice to run the Scan tool
after each server is installed.

Each time that you use the Scan tool to update status, specify the baseline file as
input. The Scan tool does not change the baseline file but instead produces a
separate output file. The output file is identical to the baseline file except that the
status and aggregateStatus elements are updated. The output file is a status file or
report.

Follow these steps to update the status of the infrastructure upgrade:

1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Enter the following command to run the Scan tool:
witmscantmr -v -f scans/baseline.xml

where:
-v Indicates that the purpose of this scan is to validate that the installed
IBM Tivoli Monitoring components are running and able to
communicate with the Tivoli server.
-f scans/baseline.xml
Specifies the name and location of the baseline file to use as input for
this command. In this case, you are using the sample baseline file that
you edited.
The command returns a message that specifies the name and location of the
output file. The format of the file name is baseline_timestamp, where baseline is
the name of the baseline file that you specified with the –f option.
3. For this exercise, rename the output file to a file named validate.xml. For
example:
cd scans
mv baseline_20050802_16_31_07.xml validate.xml
4. Open the validate.xml file.

The validate.xml file should be similar to the output shown in Figure 24 on page
90. Notice that the aggregate status of the infrastructure upgrade is PARTIAL. For
the test scenario, this status indicates that all target infrastructure components have
been deployed except for the operating system monitoring agent.

Chapter 5. Advanced features 89

 .
.
<ITM6.1Infrastructure aggregateStatus="PARTIAL"
.
.
<HubServer aggregateStatus="PARTIAL"
hostname="itmserv16.lab.company.com:1918"
hub_installDir="" protocol="IP.PIPE" source="ServerManagedNode:TMR1"
status="DEPLOYED" target="Hub:HUB_ITMSERV16" tec_forwarding_endpoint=""
unix_OSAgent_installDir="/opt/IBM/ITM/" windows_OSAgent_installDir="C:\IBM\ITM\">
<SOAPConnectionInfo SOAPencoding=""
hostname="itmserv16.lab.company.com:1920"
password="" status="DEPLOYED" user="SYSADMIN"/>
<PortalServerInfo hostname="itmserv16.lab.company.com:1920" password=""
status="DEPLOYED" user="SYSADMIN"/>
<RemoteServer aggregateStatus="PARTIAL"
hostname="itmserv16.lab.company.com:1918" protocol="IP.PIPE"
source="Gateway:gw1" status="DEPLOYED" target="Remote:HUB_ITMSERV16">
<OSAgent
comment="AMXUT2535E OS agent was not found.

Explanation:
The specified OS agent hostname is incorrect or is not deployed.

Operator Response:
Verify the OS agent hostname is correct and the OS agent is deployed, before attempting
the operation again."
hostname="ep1.lab.company.com"
osAgent_installDir="" interp="w32-ix86"
locale="US" source="Endpoint:EP1"
status="NOT_DEPLOYED" target="ManagedSystem:ep1"/>
</RemoteServer>
</HubServer>
</ITM6.1Infrastructure>

Figure 24. Output file from the Scan tool, showing current status of the infrastructure upgrade

Upgrading endpoints
In this step of the test scenario, you use the Assess and Upgrade tools to deploy
the appropriate operating system monitoring agent to the Windows endpoint
where you distributed the Tivoli Distributed Monitoring profile. The Assess tool
examines the endpoint and determines which operating system monitoring agent
to deploy. The Upgrade tool deploys the operating system monitoring agent.

When the Upgrade tool deploys the operating system monitoring agent to the
endpoint, it also assigns the endpoint to the target Tivoli Enterprise Monitoring
Server identified in the baseline file. The endpoint now becomes a managed system
that is part of the IBM Tivoli Monitoring infrastructure.

Follow these steps to deploy an operating system monitoring agent to the

Windows endpoint and to validate the final status of the infrastructure upgrade:
1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Enter the following command to run the Assess tool:
witmassess -e myendpoint -f scans/baseline.xml

90 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 where myendpoint is the name of the Windows endpoint that you are using for
the test scenario (specified in the baseline file).
The output file from this command is located in the following directory:

$DBDIR/AMX/shared/analyze/endpoints

The format of the file name is myendpoint.xml. You need not open or edit the
myendpoint.xml file. This file contains the product code of the operating system
monitoring agent to deploy. It is used as input to the Upgrade tool.
3. Run the Upgrade tool from the $DBDIR/AMX/shared/analyze directory to
deploy the operating system monitoring agent to the Windows endpoint:
witmupgrade -x endpoints/myendpoint.xml -u -f scans/baseline.xml

where:
-x myendpoint.xml
Specifies the name of the output file from the Assess command. In this
scenario, the output file from the Assess command identifies the
Windows endpoint and the operating system monitoring agent to
deploy to the endpoint.
-u Specifies that you are using the witmupgrade command to perform an
upgrade.
-f scans/baseline.xml
Specifies the name and location of the baseline file. In this scenario,
specify the sample baseline file that you edited. The baseline file
identifies the Tivoli Enterprise Monitoring Server to which the
Windows endpoint will be assigned.
The output file from this command is located in the following directory:

$DBDIR/AMX/shared/analyze/endpoints/upgrade

The format of the file name is myendpoint_timestamp.xml, where myendpoint

matches the file name that you specified with the -x option.
4. Open the output file from the witmupgrade command and verify that the
operating system agent was deployed to the endpoint. The aggregateStatus tag
for the endpoint should specify COMPLETE.

Upgrading profiles and profile managers

The final step of the test scenario is to upgrade the profile (DM_TEST_PROF) and
profile manager (DM_TEST_PM) that you created earlier with the config.sh script.

When you assess a profile manager, the situations are associated with a managed
system list. After you upgrade the profile manager, the situations are distributed to
the managed systems on the list and activated. In the test scenario, the managed
system list includes only one managed system: the Windows operating system of
the endpoint to which the OS monitoring agent was deployed.

In larger test environments or in a production environment, where a profile

manager might contain many profiles or profiles with hundreds of monitors, you
can upgrade the profiles and the profile manager in stages. You can also upgrade a
subset of monitors within a profile. After you assess and upgrade each set of
monitors or profiles, repeat the assessment and upgrade of the profile manager.
Each time you repeat the upgrade of the profile manager, the new situations are

Chapter 5. Advanced features 91

 associated with managed system lists and activated. The Upgrade tool does not
attempt to distribute or activate situations that have already been activated in
previous profile manager upgrades.

Upgrading profiles
To upgrade profiles, use the Assess and Upgrade tools. The Assess tool produces an
output file that describes equivalent situations for all the monitors in the profile.
The Upgrade tool creates the situations on the hub Tivoli Enterprise Monitoring
Server.

Follow these steps to upgrade the profile (DM_TEST_PROF) for the test scenario:
1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Enter the following command to run the Assess tool against the
DM_TEST_PROF profile:
witmassess -p DM_TEST_PROF -f scans/baseline.xml
The output file from this command is DM_TEST_PROF.xml, located in the
following directory:

$DBDIR/AMX/shared/analyze/profiles
The contents of the DM_TEST_PROF.xml file are shown in Figure 25 on page
93.
3. Run the Upgrade tool from the $DBDIR/AMX/shared/analyze directory to
send the information in the DM_TEST_PROF.xml file to the hub Tivoli
Enterprise Monitoring Server and to the Tivoli Enterprise Portal Server:
witmupgrade -x profiles/DM_TEST_PROF.xml -u -f scans/baseline.xml
The output file from this command is located in the following directory:

$DBDIR/AMX/shared/analyze/profiles/upgrade

The format of the output file name is DM_TEST_PROF_timestamp.xml.

4. Open the DM_TEST_PROF_timestamp.xml file. Verify that the aggregate status
of the profile upgrade is COMPLETE.

Analyzing the output file from the profile assessment

The contents of the DM_TEST_PROF.xml file are shown in Figure 25 on page 93:

92 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 .
.
<Profile aggregateStatus="COMPLETE" name="DM_TEST_PROF"
source="SentryProfile:1433701144.1.838#Sentry::All#" target="N/A"
.
.
<Monitor aggregateStatus="COMPLETE" name="AvailBytes"
source="Monitor:83800" target="N/A">
<Threshold source="Threshold:critical" status="COMPLETE"
target="Situation:NT_MAB_83800_critical">
<TargetSituation application="0008000000000000000000000000000000000000000"
association="Memory"
autoStart="true"
description="w2k_Memory:AvailBytes:NT_MAB_83800_critical"
distribution="DM_TEST_PM_1_837_KNT"
multipleIntervals="TRUE"
name="NT_MAB_83800_critical"
samplingInterval="1:H">
<Conditions>*IF *VALUE NT_Memory.Available_Bytes *LT 15000000</Conditions>
</TargetSituation>
</Threshold>
<Threshold source="Threshold:warning" status="COMPLETE"
target="Situation:NT_MAB_83800_warning">
<TargetSituation application="0008000000000000000000000000000000000000000"
association="Memory"
autoStart="true"
description="w2k_Memory:AvailBytes:NT_MAB_83800_warning"
distribution="DM_TEST_PM_1_837_KNT"
multipleIntervals="TRUE"
name="NT_MAB_83800_warning" samplingInterval="1:H">
<Conditions>*IF *VALUE NT_Memory.Available_Bytes *LT 25000000</Conditions>
</TargetSituation>
</Threshold>
</Monitor>
<ResponseLevelMapping responseLevel="E.EXEC" state="Warning"/>
<ResponseLevelMapping responseLevel="always" state="Informational"/>
<ResponseLevelMapping responseLevel="critical" state="Critical"/>
<ResponseLevelMapping responseLevel="normal" state="Informational"/>
<ResponseLevelMapping responseLevel="severe" state="Critical"/>
<ResponseLevelMapping responseLevel="warning" state="Warning"/>
</Profile>

Figure 25. Output file (DM_TEST_PROF.xml) from running the Assess tool against the DM_TEST_PROF profile

Note the following features of the DM_TEST_PROF.xml file:

v The name attribute of the <Monitor> element identifies the single monitor in this
profile, AvailBytes. For each threshold in the monitor, a <TargetSituation>
element defines an equivalent situation. The AvailBytes monitor maps to two
situations.
v The target attribute of the <Threshold> element and the name attribute of the
<TargetSituation> element specify the situation names: NT_MAB_83800_critical
or NT_MAB_83800_warning. The situation name is also part of the description
attribute of the <TargetSituation> element. The situation names are displayed in
the Tivoli Enterprise Portal. Each situation name consists of three parts:
– The prefix (NT_MAB_ in this example) is a special key that enables the new
situation to generate Tivoli Enterprise Console events with the same event
classes and slots used for the original monitor. (The prefix is used in the
situation name even if the original monitor does not generate Tivoli
Enterprise Console events as a response.) If you edit the situation name in the
XML output file, do not edit this prefix.

Chapter 5. Advanced features 93

 – The monitor key (83800).
– The response level or threshold (critical or warning in this example). A
separate situation is created for each response level in a monitor.
v The <TargetSituation> element also includes the following attributes:
– The description attribute specifies the description of the situation that is
displayed in the Situation Editor of the Tivoli Enterprise Portal. The
description identifies the monitoring collection, w2k_Memory, the monitor
name, AvailBytes, and the situation name, NT_MAB_83800_critical or
NT_MAB_83800_warning.
The <Conditions> element defines the situation condition.
v The <ResponseLevelMapping> elements show how monitor response levels are
mapped to situation event states. All possible monitor response levels are listed,
not only the response levels used by the monitors that are represented in the
output file. The event state determines what kind of alert indicator is displayed
in the Navigator tree of the Tivoli Enterprise Portal when a situation becomes
true. For example, a target situation generates a Critical alert indicator if the
situation was derived from a monitor response level of either critical or severe.

Upgrading profile managers

To upgrade profile managers, use the Assess and Upgrade tools. The Assess tool
produces an output file that contains the name of one or more managed system
lists with which situations are associated. The output file also shows the upgrade
status of all Tivoli Distributed Monitoring profiles in the profile manager. When
you run the Upgrade tool, all situations associated with profiles that have an
upgrade status of COMPLETE, and whose subscribers have an update status of
COMPLETE, are distributed to managed system lists.

Follow these steps to upgrade the profile manager (DM_TEST_PM) for the test
scenario:
1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Enter the following command to run the Assess tool against the DM_TEST_PM
profile manager:
witmassess -pm DM_TEST_PM -f scans/baseline.xml
The output file from this command is DM_TEST_PM.xml, located in the
following directory:

$DBDIR/AMX/shared/analyze/profilemanagers
3. Run the Upgrade tool from the $DBDIR/AMX/shared/analyze directory to
distribute the situations listed in the DM_TEST_PM.xml file to the managed
systems identified in that file:
witmupgrade -x profilemanagers/DM_TEST_PM.xml -u -f scans/baseline.xml
The output file from this command is located in the following directory:

$DBDIR/AMX/shared/analyze/profilemanagers/upgrade

The format of the output file name is DM_TEST_PM_timestamp.xml.

4. Open the DM_TEST_PM_timestamp.xml file. Verify that the aggregate status of
the profile manager upgrade is COMPLETE.

94 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Completing the test scenario
This section shows you how to view the upgrade results in the Tivoli Enterprise
Portal and how to perform cleanup activities. These tasks are optional.

Viewing results in the Tivoli Enterprise Portal

If the upgrade is successful, the new situation, managed system, and managed
system list is displayed in the Tivoli Enterprise Portal. Follow these steps to view
these items in the Tivoli Enterprise Portal:
1. Log on to the Tivoli Enterprise Portal:
a. Double-click the Tivoli Enterprise Portal icon on the Windows desktop.
b. Type SYSADMIN in the Logon ID field. This is the default user name. A
password is not required.
c. Click OK.
2. Verify that Physical is selected in the View drop-down menu above the
Navigator view.
3. Click Navigator updates pending to refresh the Navigator view.
This icon is displayed just above the Navigator. If you started the Tivoli
Enterprise Portal after performing the upgrade, the icon is dimmed. You need
not refresh the view.
4. Expand the Windows Systems node in the Navigator and look for the name of
the Windows endpoint that you used for the test scenario.
5. Expand the endpoint node to display the agents that were deployed, the
Windows OS monitoring agent and the Universal Agent. (The Universal Agent,
which is used for custom monitors, is always deployed when you deploy an
operating system monitoring agent.)
6. Click Situation Editor.
7. Expand the Windows OS node in the situation tree.
8. Look for the new situations created by the upgrade:

NT_MAB_83800_critical
NT_MAB_83800_warning
9. Select the NT_MAB_83800_critical situation in the situation tree, then click the
Distribution tab:
v The new managed system list is displayed in the Assigned box.
The name of the managed system list is based on the profile manager name,
for example, DM_TEST_PM_1_837_KNT.
v The Windows endpoint is displayed in the Available Managed Systems box,
for example, Primary:EP1:NT.

Rolling back the upgrade

You can use the rollback option (–r option) of the witmupgrade command to
remove the new IBM Tivoli Monitoring resources that you created. This is a
necessary step if you want to repeat the test scenario. Rolling back the upgrade for
the test scenario removes the Windows OS monitoring agent from the Windows
endpoint and also removes the new situations and managed system list.

Follow these steps to roll back the upgrade:

1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Enter the following command to roll back the upgrade:

Chapter 5. Advanced features 95

 witmupgrade -x profilemanagers/DM_TEST_PM.xml -r -f scans/baseline.xml

where:
-x profilemanagers/DM_TEST_PM.xml
Specifies the name and location of the output file that resulted from the
assessment of the DM_TEST_PM profile manager. (See Step 2 on page
94.)
-r Indicates that the purpose of this command is to perform a rollback.
-f scans/baseline.xml
Specifies the name and location of the baseline file to use as input for
this command.
3. Restart the Windows endpoint.
4. Remove the Windows OS monitoring agent and the Universal Agent items
from the Navigator in the Tivoli Enterprise Portal.
Because you rolled back the upgrade, the agents are no longer available and
their Navigator icons are dimmed. To remove the items from the Navigator,
right-click the agent name and select Remove Managed System from the
pop-up menu.
The rollback option can also be used to roll back an endpoint upgrade or a profile
upgrade independently. By rolling back the profile manager upgrade, you roll back
all upgrades (profile manager, profile, and endpoint) in one step.

Uninstalling the upgrade toolkit

You can use the Tivoli wuninst command to uninstall the upgrade toolkit from
your Tivoli server. You must run this command from a bash shell. Enter the
following commands to uninstall the toolkit:
bash
wuninst opmt Tivoli_server -rmfiles
wchkdb -u

where opmt identifies the upgrade toolkit and Tivoli_server is the name of your
Tivoli server.

Uninstalling the test resources

You can use the config.sh script to remove the Tivoli Distributed Monitoring
profile manager (DM_TEST_PM) and profile (DM_TEST_PROF) that were used for
the test scenario.
1. Change to the toolkit_dir/BASE/SAMPLES directory, where toolkit_dir is the
directory to which you uncompressed the upgrade toolkit file.
2. Enter the following commands:
bash
config.sh -r

Exercise 15: Creating embedded situations

Embedded situations simplify monitoring conditions for your applications by
enabling you to define common metrics and then use those metrics to define other
situations.

For example, imagine you have the following three situations:

v CPUHigh (CPU% > 90)
v SwapRateHigh (SWAP_Rate > 500)

96 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 v CPULow (CPU% < 10)
You can use these metrics to create situations that do the following:
v Monitor for a high swap rate and a low CPU rate
v Monitor for a high swap rate and a high CPU rate
v Monitor for either a high or low CPU rate

Use the following steps to create an embedded situation:

1. Right-click the Navigator item from which you want the associated situation
alert to originate and click Situations.
2. Click New Situation.
3. Type a name and description for the situation.
4. Select the type of monitoring agent from the list and click OK.
5. In the Condition Type section, select Situation Comparison and then select
one or more situations that you want to embed.
For our preceding scenario, you’d select SwapRateHigh and CPULow to
create the situation to monitor for high swap rate and low CPU.
6. Click OK.
7. Click in the cell below each new column in the formula editor to add ==True.
Putting ==True for each condition in the same row is the equivalent of using
AND. Putting it on different rows is the equivalent of using OR.
8. Embedding situations require at least two conditions. If you have more
conditions, click Add Condition and repeat steps 4 through 7.
9. Set the monitoring interval in the Sampling interval section.
10. Click the Distribution tab to assign the situation to one or more managed
systems.
11. Click Apply to save your changes and start the situation.
12. A Distribution Change window might be displayed if the situations embedded
in the current situation haven’t been distributed to the indicated managed
systems. Click OK.
13. Click OK to close the Situation window.

As the new embedded situation is distributed to the managed system, that system
is checked to ensure that the situations embedded in the new situation have also
been distributed to that system. If they have not, they are distributed by default.

Exercise 16: Configuring 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 steps:

1. “Installing the backup monitoring server” on page 98

Chapter 5. Advanced features 97

 2. “Configuring Hot Standby on monitoring servers”
3. “Configuring agents”
4. “Verifying that Hot Standby is working” on page 99

Installing the backup monitoring server

See “Installing and configuring the hub Tivoli Enterprise Monitoring Server” on
page 7 for information about installing a monitoring server. Install the backup
monitoring server as a hub monitoring server, specifying identical configuration
parameters as the primary monitoring server.

Configuring Hot Standby on monitoring servers

Use the following steps to configure monitoring servers for Hot Standby. You must
configure the hub server, the standby hub server, and any remote servers
associated with the hub server to make them aware of the backup topology.

Note: The hub and standby monitoring servers should be configured as mirrors of
each other.
1. In Manage Tivoli Enterprise Monitoring Services, right-click the name of the
hub monitoring server and click Reconfigure (on Windows) or Configure (on
UNIX).
2. Do the following on Windows:
a. Select Configure Standby TEMS.
b. 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).
c. Click OK.
d. 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.
e. Type the host name or IP address for the standby monitoring server in the
Hostname or IP Address field and click OK.
3. Do the following on UNIX:
a. Click the Advanced Settings tab.
b. Select Specify Hot Standby.
c. Type the host name for the hot standby monitoring server in the Standby
TEMS Site field.
d. Select the type of protocol to use for hot standby. This protocol should be
the same on the hub monitoring server and the monitoring server that you
plan to use for hot standby.
e. If you specified any backup protocols for the hub monitoring server,
identify identical protocols for the standby monitoring server.
f. Click Save.
4. Stop and restart the monitoring server. (On Windows, the monitoring server
stops automatically.)
5. Repeat these steps for the standby monitoring server.

Configuring agents
Agents use a feature called Secondary TEMS to ensure their availability. If the
monitoring server to which the agent connects is unavailable, they switch the
defined secondary monitoring server. Use the following steps to configure
Secondary TEMS for any agents that connect to the hub monitoring server.

98 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 1. In Manage Tivoli Enterprise Monitoring Services, right-click an agent and click
Reconfigure (on Windows) or Configure (on UNIX).
2. Select Optional: Secondary TEMS Connection and specify the protocol for the
backup monitoring server.
On UNIX agents, click Protocols to display the window where you configure
Secondary TEMS.
3. Click OK.
4. Type the host name or IP address for the hub monitoring server (if you have
not already) and the port number and click OK.
5. Type the host name or IP address for the secondary monitoring server and click
OK.
6. Restart your agent.

Verifying that Hot Standby is working

To verify that Hot Standby is working, take your hub monitoring server offline by
stopping its servers in Manage Tivoli Enterprise Monitoring Services. When the
hub monitoring server stops, reconfigure the Tivoli Enterprise Portal Server to
point to the standby monitoring server and restart the portal server. Open the
Tivoli Enterprise Portal. If everything is configured correctly, you are still able to
open the portal and view data.

Exercise 17: Creating a custom monitor from a script

Use the following steps to use the Universal Agent to create a custom monitor
from a script. There are four major steps to create a custom monitor:
1. “Step 1: Select the data provider”
2. “Step 2: Create the monitoring application script” on page 100
3. “Step 3: Import the metafile” on page 100
4. “Step 4: View the data in the Tivoli Enterprise Portal” on page 100

Before you begin this task, ensure that the computer where you want to create the
monitor has the Universal Agent installed and it is up and running. If the
Universal Agent is not installed, install it, using the directions in “Installing Tivoli
Enterprise Monitoring Agents” on page 26.

Step 1: Select the data provider

For this task, we will monitor a script that runs on your computer. Create the
following script:

For UNIX computers:

#!/bin/sh
ls -l | wc -l

For Windows computers:

@echo OFF
echo 1

Save the file as test.sh (on UNIX) or test.bat (on Windows).

Note: This is a very basic script, intended only to show you the functionality.

Chapter 5. Advanced features 99

 Step 2: Create the monitoring application script
The script that the Universal Agent uses is called the metafile (*.MDL). Create the
following metafile in a flat text editor and save it as script.mdl in the metafiles
directory on your computer.

For UNIX, create the following file:

//APPL Sample
//Name NumericScript K 1200 AddTimeStamp SkipNonNumericData=Y
//Source script /bin/sh /tmp/test.sh Interval=3600
//Attributes
HostName (GetEnvValue = HOSTNAME)
Script (GetEnvValue = PROBE)
PreviousValue (GetEnvValue = PREV_VALUE)
Stdout C 999999999999

For Windows, create the following 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

This metafile identifies the data source (the script file), as well as the attribute
group for which to gather data.

Step 3: Import the metafile

Use the following steps to import the metafile. This adds it to the Universal Agent.
1. Do one of the following to start the Universal Agent console:
On UNIX:
a. At a command line, change to the <itm_install>/bin directory.
b. Run the following command:
um_console -h <itm_install>

where <itm_install> is the installation location for IBM Tivoli Monitoring

(/opt/IBM/ITM by default on UNIX).
On Windows:
a. At a command line, change to the C:\IBM\ITM\TMAITM6 directory:
b. Run the following command:
kumpcon
2. At the prompt, type the following and press Enter:
For UNIX:
import /tmp/script.mdl
For Windows:
import script.mdl
3. Type yes to confirm the import and press Enter.
4. Press Enter to exit the console.

Step 4: View the data in the Tivoli Enterprise Portal

You can view the data collected by the new monitor in the Tivoli Enterprise Portal.
Do the following:

100 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 1. From a command line, run the test script.
2. Open the Tivoli Enterprise Portal.
3. Click Apply Pending Updates. This updates the Universal Agent with the
new monitor.
4. Expand the Navigator until you see the Universal Agent (on the computer
where you installed it).
5. Click the <host_name>:Sample Navigator item (where <host_name> is the name
of the computer) to display the workspace.

You can create a situation to monitor the information gathered by this new
monitor. To do so, use the instructions in “Creating a situation” on page 43.

Exercise 18: Monitoring a URL

Take the following steps to use the Universal Agent to monitor a URL from the
Tivoli Enterprise Portal:
1. “Step 1: Configuring and starting the Universal Agent”
2. “Step 2: Monitoring a URL” on page 102

Before you begin this task, ensure that the computer where you want to monitor
the URL has the Universal Agent installed and it is up and running. If the
Universal Agent is not installed, install it, using the directions in “Installing Tivoli
Enterprise Monitoring Agents” on page 26.

Step 1: Configuring and starting the Universal Agent

Use the following steps to configure and start the Universal Agent:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli
Monitoring Services to open the Manage Tivoli Enterprise Monitoring
Services window.
2. Right-click Universal Agent.
3. Select Configure Using Defaults from the list of options.

Note: If you have already configured the Universal Agent, select

Reconfigure... from the list of options.
4. Click Yes when you are prompted to indicate whether you want to update the
KUMENV file before configuring the Universal Agent.
5. Click OK when notified that the configuration will wait to continue until you
close out your Notepad edit session. The KUMENV Notepad edit session
opens.
6. Scroll down to the following line:
KUMA_STARTUP_DP=asfs
7. Edit KUMA_STARTUP_DP=asfs as follows:
KUMA_STARTUP_DP=asfs,http
8. Click File → Save to save your edit and exit Notepad.
9. Click Yes to configure the Universal Agent.
10. Ensure that the status of the Tivoli Enterprise Portal client, Tivoli Enterprise
Portal Server, and Tivoli Enterprise Monitoring Server is Started. If you must
start one, right-click the Service/Application and select Start.
11. Right-click Universal Agent.
12. Select Start from the list of options.

Chapter 5. Advanced features 101

 Step 2: Monitoring a URL
Use the following steps to begin monitoring a URL:
1. Start the Tivoli Enterprise Portal client.
2. Click the Apply pending updates icon in the upper left-hand corner of the
Navigator.
3. Expand Windows Systems to locate Universal Agent.
4. Expand Universal Agent. The following managed systems are displayed:
v <localhostname>:INTERNET00
v <localhostname>:ASFSdp:UAGENT00
v <localhostname>:HTTPdp:UAGENT00
5. Click any of the managed systems under Universal Agent so that the
managed system is highlighted.
6. Right-click the highlighted managed system.
7. Click Take Action... → Select.... The Take Action window is displayed.
8. From the Take Action window, select URL Add from the Name: list. The Edit
Argument Values window is displayed.
9. From the Edit Argument Values window, type in a URL with an http://
prefix.
10. Optionally, type in the other fields in the Edit Argument Values window.
11. Click OK.
12. From the Take Action window, select <localhostname>:INTERNET00 from
Destination Systems.
13. Click OK. The Action Status window is displayed.
14. Click OK.
15. Expand <localhostname>:ASFSdp:UAGENT00 or
<localhostname>:HTTPdp:UAGENT00 in the Navigator.
16. Click ACTION and verify that the data row contains the URL Add action
from step 8.
17. Expand <localhostname>:INTERNET00 in the Navigator.
18. Click MANAGED_URL to see the status of the URL that you are monitoring.

Exercise 19: Reviewing the problem determination information

For this task, you must download the IBM Tivoli Monitoring Problem Determination
Guide from the Tivoli Information Center. If you are working with non-operating
system agents such as DB2, check the problem determination appendix in the
user’s guide for each agent.

Review the trace and logging information. Ensure that you can change the trace
level as appropriate for your environment.

Review the messages - do they provide the type of information that you can use to
debug your problem? If they do not, where do they fail?

102 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Chapter 6. Working with agents
Perform the following exercises to explore the capabilities of Tivoli Enterprise
Monitoring agents.
v “Exercise 20: Using IBM Tivoli Monitoring for Databases: DB2 Agent”
v “Exercise 21: Using IBM Tivoli Monitoring: UNIX Log Agent” on page 106
v “Exercise 22: Using IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint
Agent” on page 128

Exercise 20: 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
“Installing Tivoli Enterprise Monitoring Agents” on page 26, along with the
options described in the next section.

Installation options for the monitoring agent

When installing locally on a Windows operating system, in the Manage Tivoli
Monitoring Services window, right-click the name of the monitoring agent in the
Service Application column that has ″Template″ in the Task/Subsystem column
next to the name. As you configure the monitoring agent, use the settings and
parameters specific to the IBM Tivoli Monitoring for Databases: DB2 Agent.

Monitoring agent application support

Application support files for the IBM Tivoli Monitoring for Databases: DB2 Agent
in the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or the
Tivoli Enterprise Portal are required for this agent.

When you add application support for the DB2 agent to the monitoring server, use
the “ud” product code.

See “Installing support for agents on the monitoring server, portal server, and
browser and desktop clients” on page 33 for the instructions to install this support.

Starting and stopping the IBM Tivoli Monitoring for Databases:

DB2 Agent on Linux or UNIX operating systems
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.

© Copyright IBM Corp. 2005 103

 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
You can start and stop this monitoring agent using the Manage Tivoli Monitoring
Services utility or using the itmcmd agent command.

Starting and stopping DB2 agents using Manage Tivoli Enterprise Monitoring
Services
1. When starting the DB2 agent using Manage Tivoli Enterprise Monitoring
Services, you are prompted for a database instance name.
2. When stopping the DB2 agent using Manage Tivoli Enterprise Monitoring
Services, you are prompted for the database instance name to stop.

Starting and stopping DB2 agents using the itmcmd agent command

When using the itmcmd agent command to start or stop this monitoring agent,
include the following command option:
-o Specifies the database instance to start or stop. The database instance name
must match the name used for starting the database.

For example:
itmcmd agent -o DB2inst1 start | stop ud
itmcmd agent -o Preface_DB2inst2 start | stop ud
itmcmd agent -o DB2inst3 _suffix start | stop ud

If you start the monitoring agent without specifying the -o option, you receive the
following error message: This agent requires the -o option...

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

104 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 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.

Chapter 6. Working with agents 105

 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.

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.

Exercise 21: Using IBM Tivoli Monitoring: UNIX Log 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: UNIX Log
Agent to operate:
v IBM Tivoli Monitoring: UNIX Log Agent
v Agent support on the monitoring server, portal server and portal client

The IBM Tivoli Monitoring: UNIX Log Agent software is located on the IBM Tivoli
Monitoring installation image. Install the agent using the steps in “Installing Tivoli
Enterprise Monitoring Agents” on page 26.

Specifying the log files to monitor

The runtime environment and behavior of the IBM Tivoli Monitoring: UNIX Log
Agent is controlled through a configuration file and environment variables. The
configuration file indicates the files that the monitoring agent monitors.

When the monitoring agent starts, it looks at two files to determine which logs to
monitor:
v Customer configuration file
v Syslog daemon configuration file

If, for any reason, the monitoring agent is unable to find at least one log to
monitor from either file, it writes a message to the RAS log that contains the text
Agent has no work to do and then automatically terminates.

Customer configuration file

The monitoring agent first looks for a customer configuration file. The absolute or
relative file name of this file is specified in the monitoring agent startup script
through the KUL_CONFIG_FILE environment variable. The configuration file
contains a line for each log to be monitored that includes the absolute file name of

106 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

the log along with the log type. If the monitoring agent is able to start monitoring
at least one of the logs specified in the customer configuration file, it does not
interrogate the syslog daemon configuration file.

A default customer configuration file is shipped with the product and is called
kul_configfile. This file is installed into the install_dir/config directory. All entries
in the default file are commented out.

Note: All references to install_dir refer to the destination directory that was
specified when the monitoring agent was installed.

Important! If the IBM Tivoli Monitoring: UNIX Log Agent is installed on top of a
previous version of the agent (the OMEGAMON agent), the file
install_dir/config/kul_configfile is replaced. You should rename the file or copy it
to another location before installing version 6.1 of the monitoring agent.

Customer configuration file format

Table 18 shows the file format to use for customer configuration of UNIX Log
Agent. Each entry in the customer configuration file consists of a single line with
these fields, which must occur in the given order. Each field is delimited by one or
more space or tab characters, and a semicolon (;) must precede all fields except the
first. White space cannot be placed between the semicolon and the first character
of the field it delimits.
Table 18. File format for customer configuration of UNIX Log Agent
Field Description
1 Absolute file name of monitored log.
2 Debug mode (optional: default is N)

N indicates debug mode off; Y indicates debug mode on.

If debug mode is on, each entry that is written to the monitored log is
recorded in a debug log. In addition, the formatted entry that is passed to a
situation is also written to the debug log. All logs that are monitored in
debug mode write to the same debug log.

The debug log is specified in the monitoring agent startup script using the
AGENT_DEBUG_LOG environment variable. If this variable is undefined or
the log cannot be opened, no debug logging occurs. Each time the
monitoring agent is started, new events are appended to the end of the
existing debug log.
3 Log type (optional: default is S)
v S indicates syslog
v E indicates errlog
v A indicates utmp log
v U indicates user-defined log
4 Format command. This command is valid only for type ‘E’ (errlog) and type
‘U’ (user-defined) logs.

For type ‘E’ logs, the format command must consist of an errpt command
that includes the ‘-c’ (concurrent mode) option. The default value is:
errpt -c -smmddhhmmyy

For user-defined logs, the format command describes both the format of the
log and how data will be mapped and formatted in the Tivoli Enterprise
Portal Log Entries table view. There is no default.

Chapter 6. Working with agents 107

 Syslog daemon configuration file
Kernel daemons and user applications use the UNIX syslog facility to record
messages in a log. By using the syslog facility an application ensures that its log
entries conform to a standard format.

The actual logging activities are performed by the syslog daemon, syslogd, which
is controlled through a configuration file usually called /etc/syslog.conf. The
system administrator usually maintains this file.

The syslog.conf file indicates the syslog messages that will be written, which have
a specific severity and originate from a specific application. You can consolidate
messages from more than one source into a single log file. Through the syslog
facility, you can also direct messages to be written to a different system, the log
host.

The monitoring agent attempts to build a default list of logs to monitor from the
syslog daemon configuration file under the following circumstances:
v The KUL_CONFIG_FILE environment variable is undefined.
v The specified customer configuration file does not exist or cannot be opened.
v No log names are in the customer configuration file.
v None of the logs contained in the customer configuration file are valid.

The file that the monitoring agent reads to build the default monitored logs list is
called /etc/syslog.conf, but this can be overridden using the KUL_SYSLOG_CONF
environment variable.

If you are interested only in monitoring syslogs, you can omit the
KUL_CONFIG_FILE environment variable from the startup script, or you may
leave the variable unassigned, thereby letting the monitoring agent determine the
syslogs that are active on each system, based on the syslogd configuration file.

Environment variables for IBM Tivoli Monitoring: UNIX Log

Agent
Environment variables are specified in the monitoring agent’s startup script. You
can use them to communicate to the agent information such as the name of your
customer configuration file. The agent startup script is called kul_configfile and is
located in the install_dir/config directory. Table 19 describes some of the variables
you can include.
Table 19. UNIX Log Agent environment variables
Variable name Purpose
KUL_CONFIG_FILE The absolute or relative file name of the IBM Tivoli
Monitoring: UNIX Log Agent configuration file. The default
value is: install_dir /config/kul_configfile.
KUL_SYSLOG_CONF The absolute or relative file name of the syslog daemon
configuration file. The default name is /etc/syslog.conf.
AGENT_DEBUG_LOG The absolute or relative file name of the IBM Tivoli
Monitoring: UNIX Log Agent debug log. This file is used to
record preformatted and postformatted images of each entry
written to a log that is being monitored in debug mode.
KUL_MAX_ROWS_ The maximum number of rows to be returned by IBM Tivoli
Monitoring: UNIX Log Agent for a Log Entries table view
request. The default value is 1000.

108 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Table 19. UNIX Log Agent environment variables (continued)
Variable name Purpose
KBB_RAS1 Specifies the trace entries to include in the monitoring
agent’s runtime log. Use the following syntax:
classes (COMP:component classes) (UNIT:unit classes)

A class specified outside of a parenthesis is global, that is, it

applies to all components and units. Valid classes are:
v ERROR
v FLOW
v STATE
v DETAIL
v ALL

Including one or more classes within parentheses includes

entries of the class that are generated by the associated
component or unit. A useful component to trace is
“MANAGER”; tracing units of “kul” or “kra” can also be
informative.
CTIRA_HOSTNAME Overrides the name with which the monitoring agent
identifies itself to the server. The default is the machine
name.
CTIRA_NODETYPE Overrides the default suffix that is appended to the host
name to differentiate the IBM Tivoli Monitoring: UNIX Log
Agent from another UNIX OMAs for UNIX Agent running
on the same machine. The default is KUL.

Environment variables syntax

The syntax for defining an environmental variable depends on the shell used to
interpret the script. In the Bourne and Korn shells, the following defines the VAR
variable, assigning to it the value “VALUE” and makes it available to other
programs that are invoked subsequently in the same script:
VAR=VALUE export VAR

If you are using the C shell, the following command would produce the same
result:
setenv VAR VALUE

Examples

If you are using the Bourne or Korn shells, use the following command to assign a
value of install_dir/config/myconfig to the KUL_CONFIG_FILE variable.
KUL_CONFIG_FILE=install_dir/config/myconfig export
KUL_CONFIG_FILE

If you’re using the C shell, use the following command:

setenv KUL_CONFIG_FILE install_dir/config/myconfig

Dynamically refreshing the monitoring agent

After the monitoring agent starts, you can dynamically change the list of logs
being monitored on managed systems; it is not necessary to stop and restart the
monitoring agent.

Chapter 6. Working with agents 109

 In addition, if one or more monitors were either unable to start, or ended
abnormally, they may be restarted without restarting the monitoring agent. In both
cases, it is only necessary to send the monitoring agent a refresh signal.

Sending a refresh signal to the monitoring agent on AIX

Use the following procedure to change the list of logs being monitored on a
managed system dynamically, or to restart individual monitors. This procedure
applies only to the AIX operating system.
1. Start a Telnet session or other remote login procedure to the managed system
on which you want to change the monitored logs list.
2. Modify the customer configuration file (if you have specified the
KUL_CONFIG_FILE environment variable in the ul.config file) or the syslog
daemon configuration file.
3. Send the monitoring agent a refresh signal such as the following one:
kill -HUP agentPID
4. Open the Monitored Logs table view for the appropriate managed system.
Monitoring has begun for logs that were added to the configuration file, and
stopped for logs that were deleted from the configuration file.

Note: A refresh occurs only if the monitoring agent determines that the
configuration file was modified since the agent was started, or since the
previous refresh. If you have not modified the configuration file, but want to
restart a monitor, change the modification date of the configuration file
before sending a refresh signal.

To change the modification date of the configuration file before sending a signal,
issue the following command from the directory where it resides on the managed
system where the monitoring agent is running:
touch kul_configfile

Generic user log support

You can use Generic User Log Support (GULS) to monitor an ASCII log that does
not conform to any of the three supported types, which are syslogs, errlogs, and
utmp logs. This feature relies on a format command that you supply in the
configuration file entry for each user log that you want to monitor. For more
information, see “Customer configuration file format” on page 107).

The format command describes:

v The format of the log to the Tivoli Enterprise Monitoring Agent
v How you want data that is read from the log to be mapped in the Tivoli
Enterprise Portal Log Entries table view
While the data is being mapped into the table view, you can perform data type
conversions (for example, decimal to hexadecimal), and do formatting to clarify the
table view and facilitate the creation of situations.

Format command
A format command is composed as follows:

A, “log format description” , data mapping [and formatting] specifications

A The letter A.

110 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

log format description
One or more scan directives enclosed within double quotation marks.
Details are provided in “Log format description” on page 112.
data mapping [and formatting] specifications
Indicates into which columns of the Log Entries table view the scanned
data is mapped. Details are provided in “Data mapping specifications” on
page 118.

The format description and formatting specifications both use a syntax based on
that used by the standard ‘C’ scanf and printf functions. The format command
syntax can be illustrated well through a simple example. The format command
syntax is explained in detail after the following example.

Example format command: Suppose you run an application at your site that
produces an ASCII log, myapp.log, and that you want to monitor messages that
are written to this log. Suppose also that a sample entry from this log is as follows:
MSG123 Dec 25 2004 03:15 pm system myapp: Server frodo not
responding

The following format command enables the Tivoli Enterprise Monitoring Agent to
monitor this log so that you can create situations that look for specific messages
and display the log contents within the Tivoli Enterprise Portal Log Entries table
view:
A , “%s %s %d %d %d:%d %s %s %[^:] : %[^\n]” , type month day year
hour minute hour system source description

Example format diagram: Figure 26 on page 112 illustrates how the format
command relates to each log entry and to the Tivoli Enterprise Portal Log Entries
table view.

Note: In the diagram, the format description and mapping specifications are
displayed on separate lines for illustration purposes only. In the
configuration file, each log entry must be contained within a single line.

Chapter 6. Working with agents 111

 myapp.log MSG123 Dec 25 2004 03 : 15 pm system1 myapp: Server frodo...\n

format A, "%s %s %d %d %d : %d %s %s %[^:]: %[^\n]"

type month day year hour min hour system source description
command

Monitoring
Agent

type MSG123

month Dec

day 25

year 2004

hour 3 pm

min 15

system system1

source myapp

description Server frodo not responding

Log Entries table view for myapp.log

Entry Time Description Source System Class Type
12/25/04 15:15:00 Server frodo not responding myapp system1 MSG123

Figure 26. Example format diagram

Format command syntax: A format command consists of two components:

v The log format description
v Data mapping and formatting specifications

Log format description: The format description is comprised of one or more scan
directives enclosed within double quotation marks (“...”). Generally, a scan directive
identifies a field or group of fields within a log entry, although a directive can
identify a single character within a log entry. A field is any sequence of space
characters that are not white that are ended by one or more white space characters
(that is, a tab or blank).

For example, the sequence below consists of five fields:

Dec 25 2004 03:15 pm

112 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

In addition to fields with content that varies from one log entry to another, an
entry can contain fixed character strings called literals that occur in the same
relative location in all log entries. Literals can be embedded anywhere within a
format description.

A scan directive has the following format. Items enclosed within brackets are
optional.

%[(offset)][*][width][size]datatype

All scan directives must include at least a percent sign, ‘%’, and a data type.

Each scan directive starts from where the previous one ended unless it is the first
(in which case it starts at column 1 in the log entry), or an offset option has been
included in the directive. Each scan directive consumes characters from a log entry
until any of the following occurs:
v An inappropriate character is encountered (that is, one that does not match the
expected data type).
v The field width, if specified, is exhausted.
v The end of the log entry is encountered.

Format description components: The following sections describe each of the format
description components. To simplify the discussion, all examples in the next
section include only the relevant scan directives from a format description. The
corresponding mapping specifications that must be included in a complete format
command have been omitted.

Literals: Literals describe a sequence of one or more characters that occur at the
same relative location in every entry in the log, and which you do not want to
map into a table view column.

Specifying a literal makes the Tivoli Enterprise Monitoring Agent look for and read
those characters from a log entry, and then discard them. If you include a literal, it
must match exactly the character sequence in a log entry. Otherwise, that entry is
ignored.

For example, to read a time from a log that has the following format:
03:15

The following scan directives can be used:

%d:%d

In this example, the colon ‘:’ preceding the second directive is a literal.

Any number of white space characters that immediately precede the start of a field
in a log entry are automatically consumed and discarded unless the data type of
the next scan directive is a character, for example %c. To consume any number of
white space characters that are embedded within a literal in a log entry, include
one or more white space characters in the format description literal. For example,
suppose a log entry has the following format:
MSG123 < Code 9 > System1

If you want to extract only the message field, the code number, and the system,
use the following format description:
%s < Code%d >%s

Chapter 6. Working with agents 113

 The first directive scans in the message field. The single blank following the first
directive consumes all the white space between the message field and the ‘<‘ sign
in the log entry. Similarly, the single blank between the ‘<‘ sign and the literal
‘Code’ in the format description consumes all the white space between those same
literals within the log entry. No white space is required between the literal ‘Code’
and the ‘%d’ directive or between the literal ‘>‘ and the ‘%s’ directive because this
white space is automatically consumed.

To include a percent sign, ‘%’, in a literal, specify two adjacent percent sign
characters in the format description. For example, if you want to extract the
percentages from a log that contains the following three fields:
45% 82% 2%

Use the following format description:

%d%% %d%% %d%%

(The blanks embedded within the description are not required but clarify the
example.)

Offsets: You can use offsets to specify the absolute column within a log entry at
which a scan directive starts; if no offset is specified, each succeeding scan starts
where the previous one ended. The first column in an entry is 1. Offsets can
facilitate the description of fixed field logs, that is, those in which a field starts in
the same column in every entry.

For example, suppose each log entry starts with a message number as in the
following example:
MSG123 Dec 25

If you want to extract only the message number, discarding the text “MSG” that
precedes it, you can use the following scan directive:
%(4)d

This causes the scan to start in column 4, skipping over and discarding the first
three characters.

Field suppression: The asterisk character ‘*’ in a scan directive indicates that the
scanned data is suppressed. That is, the data is read from the log entry but
discarded. For example, suppose a log entry has the following form:
MSG123 Dec 25

If you want to skip over the message number field entirely, you can use this
format description:
%*s %s %d

These directives cause the message number field to be ignored but the month and
day are stored and mapped to a column. Because the data is discarded for scan
directives that are suppressed, such directives have no corresponding data
mapping specifier (which associates log data with a table view column).

Width: You can use the width option to specify the maximum number of
characters that is consumed from a log entry to satisfy a scan directive. For
example, suppose you want to extract only the first 2 digits from the message
number from the following log entry:
MSG123 Dec 25

114 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 You can use the following scan directives:
%*3s %2d %*d

The first directive, “%*3s”, discards the first three characters of the message
number field (the text “MSG”). The second directive, “%2d”, saves the digits “12”
for mapping and the last directive, “%*d”, discards any digits that remain in the
message field. The digit ‘3’ is consumed and discarded.

For scan directives that have a data type of “string” (that is, %s or %[]), the default
width is 31.

Size: The size option can be used in numeric (that is, non-string) directives and
controls the amount of storage that is reserved to hold a scanned number.
Allocating more storage permits larger numbers to be scanned and stored. Unless
you must scan very large numbers or must increase the precision, the default sizes
are probably sufficient. The effect of including a size option in a numeric scan
directive depends on the operating system on which the Tivoli Enterprise
Monitoring Agent is run.

The following size options and data type combinations that you can specify are
valid:
Size Option Data Types
l d, i, o, u, x, e, f, g
ll d, i, o, u, x
L e, f, g
h d, i, o, u, x

If you explicitly include formatting in the data mapping specifier for a scanned
value rather than permitting the print directive to default, the size option that you
specify in the scan and print directives must be consistent.

Data type: The data type of a scan directive indicates whether the corresponding
characters in the log entry are alphanumeric or numeric and affects how the data is
stored by the Tivoli Enterprise Monitoring Agent when it has been scanned.
Specifying that log data is numeric instead of a simple alphanumeric string can
simplify the format description. Scanned data can be converted (for example,
displayed in hexadecimal or scientific notation instead of decimal) as it is being
mapped into a table view column.

Table 20 lists the valid data types you can use in a scan directive to describe
alphanumeric data.
Table 20. Valid alphanumeric data types
Data type Corresponding field in the log entry
s
A sequence of space characters that are not white. Characters from the log entry are
consumed until the first white space character is encountered or until the number of
characters specified in the field width has been exhausted. If no width is specified in
the directive, the default width is 31.

Chapter 6. Working with agents 115

Table 20. Valid alphanumeric data types (continued)
Data type Corresponding field in the log entry
c
A sequence of bytes. The number of bytes consumed is determined by the specified
width option. If no width is specified, the default is 1. Unlike all other data type
directives, white space immediately preceding the corresponding field in the log
entry is not automatically skipped. To skip over white space, you must explicitly
include a white space literal immediately preceding a directive with a data type of
character.

This feature is useful for describing fields in a log entry that might be blank
assuming the starting column and width of the optional field is known. For
example, suppose two entries from a log are as shown:
field1a field2a field3a
field1b field3b

Field 2, if present, always starts in column 12 and can be up to 9 characters long.

The following format description could be used:
%s %(12)9c %s

In this example, the second directive stores “field2a” when the first entry is
processed, and contains blanks when the second entry is processed.

116 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 20. Valid alphanumeric data types (continued)
Data type Corresponding field in the log entry
[inclusive scanset] or
[^exclusive scanset Any sequence of characters. A scanset data type is a generalized type ‘s’ (string) data
type. In fact, the type ‘s’ directive can be expressed by the following exclusive
scanset:
%[^ \t\n]

This scanset indicates that all non-blank, non-tab and non-newline characters will be
consumed. That is, the scan ends on the first white space character in the log entry.
(See “Escape characters” on page 123 for details on specifying escape characters in a
format command.)

In an inclusive scanset, characters from a log entry are consumed until a character is
encountered that is not in the scanset. In an exclusive scanset (for example, one that
has a ‘^’ (circumflex) character immediately following the left bracket), characters
from a log entry are consumed until a character is encountered that is in the scanset.

A scanset permits a single scan directive to consume multiple log entry fields. For
example, a scanset that you might use frequently is one that is to “read all the
remaining characters in an entry”:
%[^\n]

That is, consume everything from the current position in an entry up to the newline
character, which marks the end of the entry.

A scanset directive can also be used to terminate a scan before a simple type ‘s’
variable would, that is, when a white space character is found. For example,
suppose a log entry has embedded within it either one of the following two field
sequences:
Error code:24
Warning code:16

If you want only to extract the numeric code itself, the following directives could be
used:
%*[^:]:%d

This format description consumes and discards (field is suppressed) all characters
until a colon is found (exclusive scanset), then consumes and discards the colon
itself (an embedded literal) and finally consumes and stores the numeric code.

As with a string data type, if you wish to consume more than 31 characters with a
scanset directive, you must include a maximum width option in the directive. For
example, to consume up to 60 characters from the current location up to the end of
the entry use:
%60[^\n]

Some operating systems support the use of a ‘-’ (dash) to represent a range of
characters, for example:
%[a-z]

This example includes all lowercase letters in the scanset. The character that
precedes the dash must be lexically less than the character following it otherwise the
dash stands for itself. Also, the dash stands for itself whenever it is the first or last
character in the scanset.

To include the right bracket in an inclusive scanset, it must immediately follow the
opening left bracket. To include the right bracket in an exclusive scanset, it must
immediately follow the circumflex character. In both cases, a right bracket placed
there is not considered the closing right bracket of the scanset.

Chapter 6. Working with agents 117

Table 20. Valid alphanumeric data types (continued)
Data type Corresponding field in the log entry
d, u
An optionally signed decimal integer.
i An optionally signed integer with a base determined by the first characters of the
number:
v If the first character is in the range 1 to 9, the base is 10.
v If the first character is 0 and the second character is in the range 0 to 7, the base is
8.
v If the first 2 characters are 0x (or 0X), the base is assumed to be 16; that is, all
characters in the range 0 to 9 and a to f (or A to F) are considered part of the
number.
o
An optionally signed octal integer, that is, a string of integers in the range 0 to 7.
x
An optionally signed hexadecimal integer, that is, a string of characters in the range
0 to 9 and a to f or A to F.
e,f,g An optionally signed string of digits that can contain a decimal point or an exponent
component that consists of an ‘E’ or an ‘e’ followed by an optionally signed integer.

Data mapping specifications: The data mapping specifications that comprise the
second component of a format command are separated from the format description
by a single comma. Each mapping specification is separated from the next by
white space. Every non-suppressed scan directive in the format description must
have a single, corresponding data mapping specifier to indicate into which column
of the Log Entries table view the scanned data must be mapped. That is, the
general form of a format command is as follows:
A , “%scan1 %scan2 %*scan3 %scan4” , mapspec1 mapspec2
mapspec4

The third scan directive has no corresponding mapping specifier because it is

suppressed by an asterisk character (*).

As the data is mapped into a table view column you can also optionally specify
how you want it formatted and (for data read in and stored in numeric form), that
numeric data is converted to a different type (for example, decimal to hexadecimal
or exponent form). See “Specifying log entry times” on page 125 for further details.

The columns into which scanned data can be mapped correspond to columns in
the Log Entries table view. Table 21 lists all the valid column names and minimum
abbreviations that can be used.
Table 21. Valid column names and minimum abbreviations
Tivoli Enterprise Portal Log Format command mapping
Entries table view column name name Minimum abbreviation
Entry Time month mo
day da
year ye
hour ho
minute mi
second se

118 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 21. Valid column names and minimum abbreviations (continued)
Tivoli Enterprise Portal Log Format command mapping
Entries table view column name name Minimum abbreviation
Description description de
Source source so
System system sy
Class class cl
Type type ty

Referring again to the example at the beginning of this section (“Example format
command” on page 111), notice that there are 10 scan directives and also that there
are 10 mapping specifications. Each successive scan directive, reading the format
description left to right, is associated with each successive mapping specifier. That
is, the first log entry field, MSG123, is read by the first scan directive, %s, and is
mapped to the first column specifier, type. The second field, Dec, is read by the
second scan directive, %s, and is mapped to the second column specifier, month,
and so on.

As indicated in this same example, it is possible to concatenate two or more

nonadjacent log entry fields into the same table view column. The log entry time is
in 12-hour format; that is:
03:15 pm

The corresponding format description and data mapping specifiers in the example
format command are:
“%d:%d %s” , hour minute hour

This causes ‘03’ to be read by the first scan directive, ‘%d’, and mapped into the
hour column. The next character in the log entry, the colon, matches the colon
literal in the format description and is discarded. The ‘15’ is read by the second
scan directive, ‘%d’, and is mapped into the minute column. The ‘pm’ is read by
the third scan directive, ‘%s’, and is also mapped into the hour column. The result
is that the hour and minute columns contain ‘3pm’ and ‘15’ respectively. (If the
Tivoli Enterprise Monitoring Agent is passed an hour of ‘3pm’ it converts this into
24-hour format for display in the Log Entries table view. See “12-Hour format
times” on page 125 for more information concerning valid date and time formats
that can be passed to the Tivoli Enterprise Monitoring Agent.)

The preceding example shows that it is necessary only to supply a column name
into which scanned log data is mapped. For each mapping specification that has
no explicit format specifier, default formatting is applied. The Tivoli Enterprise
Monitoring Agent expands the mapping specifiers in the previous example as
follows:
“%d:%d %s” , hour=“%d” minute=“%d” hour=“%s”

How to override the default mapping format specifiers is the subject of the next
section.

Formatting mapped data: If no formatting is included for a specific mapping

specification, a default format specification is assigned based on the data type and
data type size in the corresponding scan directive. To specify explicitly how

Chapter 6. Working with agents 119

 scanned data is formatted as they are mapped into a given column, follow the
column map name with an equal sign (=) and enclose your format specifier in
double quotation marks (“...”).

The syntax for a data mapping specification that includes a format specifier is as
follows:

MappingName[=“[literals]%[options][width]
[.precision][size]datatype[literals]”]

The MappingName corresponds to one of the full or abbreviated names from

columns 2 and 3 of Table 21 on page 118 and items in brackets are optional.
Because a one-to-one relationship between a scan directive in the format
description and a mapping specification exists, include at most one “%datatype”
directive in a mapping format specification.

Mapping format specifier components: The following paragraphs describe each of the
mapping format specifier components.

Literals: Literals can be included before the scanned data is mapped into a table
view column, afterwards, or both, and can serve to clarify the Log Entries table
view and facilitate the creation of situations. For example, suppose you are
monitoring a log that includes the following three fields:
... 13303 15 4 ...

The first field indicates a process identifier, the second represents a return code
and the third a severity. You might choose to map and format the data as follows:
“... %d %d %d ...” , ... source=“proc id. = %d” desc=“RC = %d ” desc=“;
Severity = %d”...

Note: The ellipses represent omitted fields.

The following information is displayed in the source and description columns in

the Log Entries table view:
Source Description
proc id. = 13303 RC = 15 : Severity = 4

To include a single % (percent sign) in a column, include two consecutive %

characters in the format specifier. For example, desc=“%d%%” maps the integer 83
as “83%” into the description column.

Options: One or more options can be included in a mapping format specifier

although not all combinations are valid. The options and their meaning are shown
in Table 22.
Table 22. Log Entries table view mapping options
Option Description Notes
‘ Effect depends on the locale setting
Formats integer portions for i, d, u, f, on the managed system. Use the
g and G data types with the locale -a command to view available
appropriate thousands grouping locales and review the Tivoli
separator. Enterprise Monitoring Agent log to
determine the current locale.

120 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 22. Log Entries table view mapping options (continued)
Option Description Notes
- Left-justifies data if number of Use with field width.
characters mapped is less than the
minimum field width (see below).
+ Inserts a ‘+’ or ‘-’ sign before a
numeric value depending on Valid only for signed numeric data
whether it is greater or less than types.
zero.
space Inserts a space character before a Valid only for signed numeric data
character positive numeric value; inserts a ‘-’ types. Ignored if ‘+’ option is also
sign before a negative value. specified.
# For ‘o’ data type, increases precision Not valid for c, d, s or u data types.
to force the first digit of the result to
be a zero.

For ‘x’ and ‘X’ data types, precedes a

nonzero result with ‘0x’ or ‘0X’
respectively.

For ‘e’, ‘E’, ‘f’, ‘g’ and ‘G’ data types,

the result always contains a decimal
point even if no digits follow it. For
‘g’ and ‘G’ data types, trailing zeros
are not removed from the result.
0 Valid only for numeric data types.
Pads to the field width with leading Ignored if ‘-’ option is also specified.
zeros. Ignored also for d, i, o, u, x and X
data types if precision is specified.

For example, suppose a log entry contains the character sequence “65000” and the
format command contains:
“... %d ...” , ... type=“%’0+9d”

The type column is displayed as:

+0065,000

Width: A decimal digit string included in a mapping format specifier signifies the
minimum width of the field into which the data is mapped. If the mapped data
contains fewer characters than the minimum field width, it is right justified and
padded on the left to the length specified by the field width. If the ‘-’ (left-justify)
option has been specified, the data is padded on the right.

For example, suppose the log entry contains the following fields:
1 789 82 4567

You supplied the following format command:

A, “%d%d%d%d” , desc=“%8d” desc=“%8d” desc=“%8d” desc=“%8d”

The description column is formatted as follows:

1 789 82 4567

A field width with a leading zero is interpreted as meaning that the field must be 0
padded.

Chapter 6. Working with agents 121

 Precision: A precision is specified by a [ . ] (dot) followed by a decimal digit string.
The effect of a precision depends on the type of data being mapped. Use the
following guidelines for mapping precision and specified data types:
Data Type Precision specifies
d, i, o, u, x, X Minimum number of digits.
e, E, f Number of digits to be displayed after the decimal
point.
g, G Maximum number of significant digits.
strings Maximum number of bytes to be printed from a
string.

For example, suppose a log entry contains the following fields:

2 3.142857 123.45 On no account allow a vogon to read poetry at you

The format command is:

A,“%d%f%g%[^\n]” , de=“%.3d” de=“ %.3f” de=“ %.2g“ de=“ %.13s“

The description field contains the following:

002 3.143 1.2e+02 On no account

Size: The valid size options that you can specify in a format specification for
mapped data are the same as those that can be specified in a scan directive in the
log format description. The data size specified in a mapping format specifier must
be the same as that specified in the corresponding scan directive.

Data type: As with the size option, the data type in a mapping format specifier
must be consistent with that in the corresponding scan directive. This means that if
data is scanned and stored as an integer, it must be mapped as an integer. If it is
scanned as a floating point number, it must be mapped as a floating point number.
If it is scanned as a character or character string it must be mapped as a character
or character string.

Numeric data can be scanned and stored in one of two families: the integer family
and the floating point family. Within each family, data can be represented in
different ways. An integer can be displayed in decimal, octal, hexadecimal and
unsigned formats. A floating point number can be displayed in decimal or
exponent notation. When numeric data is mapped, you can use a different data
type to that in the scan directive as long as the format data type comes from the
same family. Data types from different numeric families cannot be mixed.

You can use this feature to perform type conversions as you map data into a table
view column to clarify the table view. For example, if a field in a log entry
contains the size of a file in bytes, you can display the size as a hexadecimal value
in the Log Entries table view by using the following in the format command:
A, “... %d ...” , ... desc = “File size is %#x bytes” ...

If the file size is, for example, 11259375 bytes, the description columns contain the
following information:
File size is 0xabcdef bytes

For an example that mixes data types from the floating point family, the size can
be displayed in exponent notation with the following format command:
A, “... %f ...” , ... desc = “File size is %.2e bytes” ...

122 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

This time, the description column would contain:
File size is 1.13e+07 bytes

The valid mapping data types are specified by family in Table 23 and Table 24.
Table 23. Integer family data types
Data type Format of data scanned and stored as integers
d, i
Signed decimal numbers.
u Unsigned decimal numbers.
o Unsigned octal numbers.
x, X Unsigned hexadecimal numbers. The letters abcdef are used for x;
the letters ABCDEF are used for X.

Table 24. Floating point family data types

Data type Format of data scanned and stored as integers
f
Signed decimal numbers with the number of digits after the decimal
point equal to the precision. If no precision is specified, the default is
6 digits.
e, E In exponent form, that is, [-].ddd+/-dd. One digit precedes the
decimal point and the precision specifies the number of digits that
follow it. The default precision is 6. The E data type produces a
number with E instead of e before the exponent.
g, G In either the f or g (G if E is used) formats, depending on the value
of the number with the precision specifying the number of significant
digits. The exponent form is used if the exponent is less than -4 or
greater than the precision.
c As a single character. The mapped data can have been read as a
single character, ‘%c’, or could be the first character of a string that
was stored using a scan directive such as ‘%s’, ‘%[]’, or ‘%nc’ (where
n is an integer field width).
s As a string. The mapped data must have been read and stored as a
string using a scan directive such as ‘%s’, ‘%[]’, or %nc’ (where n is
an integer field width greater than 1). All characters from the string
are printed up to the number of bytes indicated by the precision.

Escape characters: You might want to include characters in a format command that
either are not valid in the command itself (for example, the newline character), or
which have a special meaning to the Tivoli Enterprise Monitoring Agent when it is
interpreting the format command (for example, the double quote (“) character).
Such characters are represented in the format command by a sequence of two
characters:
v The backward slash (\) escape character
v Following the backward slash, a character that represents the character code that
is being escaped

The backward slash character removes any special meaning from the following
character and causes the latter’s single character code value to be substituted
instead.

Escape characters can be included in three areas of a format command:

Chapter 6. Working with agents 123

 v In the format description
– As part of a literal
– Inside a scanset (%[]) type scan directive
v In a mapping specifier
– As part of a literal

For example, suppose you want to monitor a log that contains the following
sample entry:
“http://www.acme.com” : GET /download/Acme.exe

Suppose that you want to extract the character string between the set of double
quotation marks and everything after the colon. Also, assume you want to map the
first string into the source column of the Log Entries table view and that you want
to map the second string into the description column enclosing it in quotation
marks. The following format command accomplishes this:
A,”\”%[^\”]\” :%[^\n]” , source desc = “\”%s\””

Following the double quotation mark that starts the format description is an
escaped double quotation mark literal that consumes the double quotation mark
preceding “http:” in the sample log entry. The exclusive scanset scan directive
contains an escaped double quotation mark that terminates the first scan; that is,
“http://www.acme.com” is stored by the scanset directive. The escaped double
quotation mark, white space character, and colon literal following the scanset
directive consumes all characters up to the text “GET” in the sample log entry. The
second scanset consumes and stores all characters until a newline character is
encountered (end of line). The next non-escaped double quotation mark terminates
the format description component of the format command.

The mapping specification for the description column contains two escaped double
quotation mark literals surrounding the scanned string. The preceding sample data
is displayed in the Log Entries table view using this format command:
Description Source
″GET /download/Acme.exe″ http://www.acme.com

Table 25 lists all the characters that can be represented by an escape sequence and
the associated escape sequence.
Table 25. Escape character sequence
Character Escape sequence representation
alert \a
backspace character (\) \\
backspace \b
carriage return \r
double quotation mark (“) \”
horizontal tab \t
newline \n
single quotation mark (‘) \’
vertical tab \v

124 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Specifying log entry times: The entry time displayed in the Log Entries table view is
extracted from each log entry and is not the time at which the log monitor
detected the event. The format command that you supply for each user-defined log
must, therefore, include scanning and mapping specifications for the entry time.

Because the format of dates and times varies so widely between logs, the Entry
Time column of the Log Entries table view is composed of six components: the
year, month, day, hour, minute, and second. You specify scanning and mapping
pairs explicitly for each component using one of the mapping names in Table 21 on
page 118.

When the Tivoli Enterprise Monitoring Agent formats an entry from a log, it
attempts to build a time stamp with a format of:
mm/dd/yy hh:mm:ss

‘YY’ is the 2 digit year, the first ‘mm’ is the month, ‘dd’ is the day of the month,
‘hh’ is the hour (in 24-hour format), the second ‘mm’ is the minute and ‘ss’ is the
second. The Tivoli Enterprise Monitoring Agent expects that the data that is
mapped into each of the entry time component fields is a valid integer. The data
type with which each component was scanned and mapped is not important; what
is important is that the formatted result is an integer.

For example, suppose the date and time in a log entry is in the form:
MSG123 2005 03 03 10 15 56 ...

Use the following format command to extract and map the entry time components:
A , “%s %s %s %s %s %s %s” , desc year month day hour minute
second

The following format command is also valid:

A , “%s %d %d %d %d %d %d” , desc year month day hour minute
second

There are two exceptions to the requirement that all time components consist of
numeric data only: text months and 12-hour format times.

Text months: If the month of the log entry is in text form, for example, Jan, Feb or
JAN, FEB, you can read and map the month as a string. When the Tivoli Enterprise
Monitoring Agent is passed for a month in this format, it translates the string to
the appropriate numeric value when constructing the entry time.

12-Hour format times: Some logs contain the entry time in 12-hour format, for
example, 03:15 PM. Because the Tivoli Enterprise Monitoring Agent displays entry
times in 24-hour format, for such logs you must pass the ‘am/pm’ indicator to the
Tivoli Enterprise Monitoring Agent in the hour column. An example format
command for reading and mapping the hour and minute from a log with this
format follows.
“%d:%d%s” , hour minute hour

This concatenates the ‘am/pm’ indicator to the 12-hour value so that, using the
previous time as an example, the value “3 pm” is passed to the Tivoli Enterprise
Monitoring Agent. When constructing the entry time for an event, the Tivoli
Enterprise Monitoring Agent translates such a time to its equivalent 24-hour
format, which in this case is ‘15’.

Chapter 6. Working with agents 125

 Hardcoding missing entry time components: If you omit a scan or map specification
pair for the seconds component of the entry time, the time takes the default, which
is zero. If you omit a scan or map pair for any of the other entry time components,
the Tivoli Enterprise Monitoring Agent assigns the default value to the
corresponding current value reported by the system clock both for real-time,
monitored events and for events that are formatted for a table view request. (See
the exception that follows for table view requests if the omitted value is the year).
This can be appropriate for the purposes of monitoring but can lead to
unpredictable or misleading results for table view requests (which return all entries
from a specific log that occurred within a certain time span).

If, for instance, the minute is not supplied within a log entry and you do not want
to let the minute default to the current system clock minute for either monitored
events or table view requests, you can hardcode a value such as ‘0’ for the minute
column. Suppose an entry from such a log has the following format:
MSG123 2005 Mar 6 10 pm Text of event ...

The following format command hardcodes a value of zero for the entry time
minute for every event:
A,“%s %d %s %d %d %s%c %[^\n]” , de ye mo da ho ho min=“0”
desc=“:%s”

The Tivoli Enterprise Portal Log Entries table view would contain the following
information in the Entry Time and Description columns.

Note: If omitted, seconds takes the default of zero.

Entry Time Description
03/06/05 22:00:00 Text of event

To include a mapping specifier for the ‘minute’ column, an associated scan

directive must exist. However, we are trying to hardcode a value of zero for this
column; the data consumed by the associated scan directive is not used and is,
therefore, totally arbitrary.

In this example, a dummy scan directive is supplied ‘%c’ that consumes the single
space character between the ‘PM’ and the start of the actual message. Because this
space would be discarded anyway and does not affect the data in interest, this
scan directive’s sole purpose is to permit inclusion of a ‘minute’ column mapping
specifier in which a ‘0’ character is forced to be displayed.

Defaulting the year entry-time component: Many logs omit the year from their event
entry times. For example, the following sample was taken from a syslog.
Mar 17 03:34:11 frodo unix: NFS server gandalf not responding

When monitoring such logs, the Tivoli Enterprise Monitoring Agent sets the
entry-time year component for each new event to the current system-clock year as
described in “Hardcoding missing entry time components.”

When handling table view requests for logs that do not include the entry-time
year, the Tivoli Enterprise Monitoring Agent attempts to determine the year of an
event based on the date in the next entry. This causes the Tivoli Enterprise
Monitoring Agent to make an assumption that a monitored log has never been
inactive for a period one year or longer. To show how this works, suppose two
entries from a syslog are as follows. (New log entries are appended to the end of
the log. The entry dated December 31st is older than that dated January 1st.)

126 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Dec 31 23:34:11 bilbo unix: NFS server gandalf not responding
Jan 1 03:34:11 frodo unix: NFS write error on host bilbo

Furthermore, suppose that the current date is March 15th, 2005. If you issued a
table view request and specified in the time span dialog a time range of December
31st, 2004 at 11:00 p.m. to January 1st, 2005 at 4:00 a.m., the preceding entries are
displayed (in reverse chronological order) in the Log Entries table view as follows:
Entry Time Description
01/01/05 03:34:11 NFS server gandalf not responding
12/31/04 23:34:11 NFS write error on host bilbo

Monitoring system conditions using situations

As two examples of the type of information you can view with situations:
v You can use the UNIX_LAA_Bad_su_to_root_Warning situation to determine if a
logon failure to root message is written to usr/adm/sulog more than three times
within a minute. The situation’s formula is the following:
Log_Entries.Log_Path EQ /usr/adm/
AND
Log_Entries.Log_Name EQ sulog
AND
*SCAN Log_Entries.Description EQ ’Badsu_root’
AND
Log_Entries.Frequency_Threshold GT 3
AND
Log_Entries.Period_Threshold EQ 60
v You can use the UNIX_LAA_Log_Size_Warning situation to determine if the size
of any monitored log exceeds 10 Mbytes. This situation’s formula is the
following:
Monitored_Logs.Log Size (Bytes) GT 10485760

Open a situation using the following steps:

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.

Monitoring system conditions using workspaces

As two examples of the type of information you can view with workspaces:
v You can use the Log Entries workspace to view entries from any monitored log
that occurs within a specified time range.
v You can use the Monitored Logs workspace to view basic information about the
logs you are monitoring.

Chapter 6. Working with agents 127

 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.

Exercise 22: Using IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x
Endpoint Agent
The IBM Tivoli Monitoring 5.x Endpoint Agent enables you to view data from IBM
Tivoli Monitoring version 5.1 within the IBM Tivoli Monitoring version 6.1 GUI.

After you install IBM Tivoli Monitoring and the Tivoli Enterprise Portal, you install
the following software that is required for the IBM Tivoli Monitoring: IBM Tivoli
Monitoring 5.x Endpoint Agent to operate:
v IBM Tivoli Monitoring, version 5.1.2 Fix Pack 5 and LA patch 119
v IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint Agent

Install all of these on the Tivoli management region server or gateway.

The IBM Tivoli Monitoring installation image contains the installation image for
this agent.

In addition to the procedures in this chapter, you must use procedures in the
following documentation to complete installation and configuration of the IBM
Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint Agent.
v IBM Tivoli Monitoring Installation and Setup Guide
v IBM Tivoli Monitoring, version 5.1.2 Fix Pack 5 Readme

Table 26 contains a list of the procedures for installing and configuring this
monitoring agent after you have installed IBM Tivoli Monitoring, 6.1 and the Tivoli
Enterprise Portal as described in “Exercise 1: Installing IBM Tivoli Monitoring” on
page 3. The table also contains references to where to find the information to
complete each procedure.
Table 26. Installation and configuration procedures
Procedure Where to find information
Ensure that you have added application “Exercise 1: Installing IBM Tivoli
support to the Tivoli Enterprise Monitoring Monitoring” on page 3
Server. This step should have been done
during the Tivoli Enterprise Monitoring
Server installation.
Install IBM Tivoli Monitoring, 5.1.2 Fix Pack Download these files from the following
5 and the IBM Tivoli Monitoring, 5.1.2 LA Web site:
Patch 0119 onto your system.
https://www14.software.ibm.com/webapp/
iwm/web/preLogin.do?source=itmcp

For a full description of the fix pack please

refer to the Readme contained at this site.

128 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 Table 26. Installation and configuration procedures (continued)
Procedure Where to find information
Install the IBM Tivoli Monitoring: IBM Tivoli The files for this installation image can be
Monitoring 5.x Endpoint Agent on your found on the preceding Web site.
Tivoli management region server or gateway.
The installation image for this agent is called Refer to the instructions in this chapter for
Monitoring Agent for IBM Tivoli Monitoring installing this image.
5.x Endpoint, Version 6.1.0. Note: The support files for this agent are
installed on the Tivoli Enterprise
Management System and Tivoli Enterprise
Portal Server automatically, as long as the
install directions in chapter 1 of the IBM
Tivoli Monitoring Installation and Setup Guide
are followed.
Configure IBM Tivoli Monitoring and the Refer to the instructions in this chapter.
IBM Tivoli Monitoring: IBM Tivoli
Monitoring 5.x Endpoint Agent

Install the IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x

Endpoint Agent
You can install this agent by either using the winstall command or by using the
Tivoli desktop.

To install using the winstall command, run the following command from the
command prompt:

winstall -c source_dir [-s server] -i IND_file [-y] [-n]

where:
-c source_dir
Specifies the complete path to the directory containing the installation
image.
-s server
Specifies the name of the managed node to use as the installation server.
By default, the installation server is the Tivoli server.
-i IND_file
Specifies the product index file (ITM61AGT.IND) to reference for the
installation.
-y Installs the product without requesting confirmation.
-n Installs the product on all managed nodes that do not currently have the
product installed.

Refer to the Tivoli Management Framework Reference Manual for more information
about this command.

To install using the Tivoli desktop complete the following steps:

1. Select Install from the Desktop menu.
2. Click Install Product in the menu to display the Install Product window.
3. If necessary, click OK to bypass a harmless error message about the media
settings.
4. Click Select Media to display the File Browser window.

Chapter 6. Working with agents 129

 5. In the Path Name text field, enter the full path to the .IND file for the
software that you are installing. Be sure to use backward slashes (\) for
Windows path names instead of forward slashes (/).
6. Click Set Path. The File Browser window displays the contents of the
specified media in the Files scrolling list.
7. Click Set Media & Close.
8. Select the software name from the Select Product to Install list in the Install
Product window.
9. Ensure that the list of clients to install on is complete and does not contain
any clients that you do not want this software installed on:
a. Disable software installation for some clients, as needed:
1) Take no action if the client is listed in the Available Clients list.
2) Select a client that does not require the software, but is listed in the
Clients to Install On list by default.
3) Click the right arrow to move the client to the Available Clients list.
b. Enable software installation for some clients, as needed:
1) Take no action if the client is listed in the Clients to Install On list.
2) Select a client requires the software, but is listed in the Available
Clients list by default.
3) Click the left arrow to move the client to the Available Clients list.
10. Click Install & Close to display the Product Install window and a list of
pending installation actions.
11. Click Continue Install to begin the installation process.

Configuring and distributing the IBM Tivoli Monitoring: IBM

Tivoli Monitoring 5.x Endpoint Agent
Use the following steps to configure and distribute this agent:

Note: This procedure requires that you have admin authority in the Tivoli
Framework environment.
1. Use the following command on each targeted system you have listed.
Additional information: This command skips any systems that are not running a
supported operating system.
witm61agt [-f] [-n] [-i seeding] [-o outfile] [[-D Variable=Value] ...] -c
CMSAddress [-p port]
{-a |endpoint [endpoint ...] | @filename}
Where:
-f Forces the distribution to proceed even if the operating system version
check fails.
-n No distribution of binaries, performs only configuration.
-i Invokes the IBM Tivoli Monitoring wdmepconfig command on each
endpoint. ″Seeding″ specifies where data goes. Valid values are ITM5,
ITM6, or BOTH.
-o Does not distribute binaries or configure, only puts the endpoint list in
an ″outfile″.
-D DataSeeding
Adds the setting ″Variable=Value″ to the environment file for the agent.
-c Specifies the network name of the management server.

130 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 -p Specifies the TCPIP port number on which the management server
listens.
-a All endpoints that have IBM Tivoli Monitoring profiles distributed to
them receive the distribution.
endpoint
Distributes to the named endpoint or endpoints.
@filename
Distributes to all endpoints named in the specified file.

Note: You can manually distribute the files and push only the configuration.
2. Use the following command to set the logging behavior of the IBM Tivoli
Monitoring engine:
wdmepconfig -e Myendpoint -D DataSeeding= ITM5 | ITM6 | BOTH
wdmepconfig -e {endpoint | @endpoints_file} {-D key=value [-D key=value]... }

wdmepconfig -e {endpoint | @endpoints_file} -G key

wdmepconfig -e {endpoint | @endpoints_file}

Where:
-e endpoint
For IBM Tivoli Monitoring, version 5.1, 5.1.1, or 5.1.2, a list of one or
more names of the target systems .
-e endpoints_file
IBM Tivoli Monitoring, version 6.1, the file that contains the list of
target systems ...
-D DataSeeding
Application where you want to log data. Use one of the following
values:
ITM5 IBM Tivoli Monitoring, version 5.1, 5.1.1, or 5.1.2. This is the
default value. The data is logged in the Tivoli Data Warehouse
and the Web Health Console, but not the Tivoli Enterprise
Portal.
ITM6 IBM Tivoli Monitoring, version 6.1. The data is logged in the
Tivoli Enterprise Portal, but not in the Tivoli Data Warehouse
and the Web Health Console.
BOTH IBM Tivoli Monitoring, version 5.1, 5.1.1, or 5.1.2 and IBM
Tivoli Monitoring, version 6.1. This is the preferred setting. You
can start with this option, decide which one is preferred, and
then reconfigure accordingly.
-G Retrieves a key value.

Note: This change is effective when the engine is restarted.

Monitoring system conditions using workspaces

As two examples of the type of information you can view with workspaces:
v You can use the Resource Model Health workspace to view information about
the health of your resource models.
v You can use the Agent Messages workspace to view information about various
agent messages.

Chapter 6. Working with agents 131

 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.

132 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Appendix A. Hardware and software requirements
The following sections provide specific information about the memory, software,
and hardware requirements for installing IBM Tivoli Monitoring.

Note: This section does not show agent-specific requirements (such as supported
application levels or any hardware requirements that are unique to a certain
agent). For this information, see the user’s guide for the agent that you are
installing.

Supported operating systems

Table 27 shows which operating systems are supported for the different IBM Tivoli
Monitoring components: monitoring server, portal server, portal client, monitoring
agent, and Warehouse Proxy.
Table 27. Supported operating systems
Monitoring Monitoring
Warehouse Proxy
Operating system server Portal server Portal client1 agent2
AIX 5.1 (32/64 bit) X
AIX 5.2 (32/64 bit) X X
AIX 5.3 (32/64 bit) X X
Solaris 8 (32/64
X
bit)
Solaris 9 and 10
X X
(32/64 bit)
HP-UX 11i (32/64
X
bit)
Windows 2000
X
Professional
Windows 2000
X X X X X
Server
Windows 2000
X X X X X
Advanced Server
Windows XP X X X
Windows 2003
Server SE (32 bit)
X X X X X
with Service Pack
1*
Windows 2003
Server EE (32 bit)
X X X X X
with Service Pack
1*
RedHat Enterprise
X
Linux 2.1 Intel
RedHat Enterprise
X
Linux 3.0 Intel
RedHat Enterprise
X X X X
Linux 4 Intel

© Copyright IBM Corp. 2005 133

Table 27. Supported operating systems (continued)
Monitoring Monitoring
Warehouse Proxy
Operating system server Portal server Portal client1 agent2
RedHat Enterprise
Linux 3 for X
z/Series
RedHat Enterprise
Linux 4 for X X X
z/Series 31-bit
SUSE Linux
Enterprise Server X
8 Intel
SUSE Linux
Enterprise Server
X X X
8 for z/Series
31-bit
SUSE Linux
Enterprise Server
X
8 for z/Series
64-bit
SUSE Linux
Enterprise Server X X X X
9 Intel
SUSE Linux
Enterprise Server
X X X X
9 for z/Series
31-bit
SUSE Linux
Enterprise Server
X
9 for z/Series
64-bit
OS/400 5.2 X
OS/400 5.3 X
4
z/OS 1.4 X X
z/OS 1.5 X X
z/OS 1.6 X X
z/OS 1.7 X

Notes:
1. The Tivoli Enterprise Portal desktop client is supported on marked platforms. However, the
browser client is supported only on Windows computers running Internet Explorer 6.
2. The Monitoring agent column indicates the platforms on which an agent is supported. It
does not indicate that any agent runs on any platform. For example, to monitor a Linux
computer, you must use a Linux monitoring agent, not a Windows monitoring agent.
3. * For Windows 2003 Server: If you do not plan to deploy Service Pack 1 in your environment
at this time, you must download and install Microsoft Installer 3.1, which is available from
the Microsoft Download Web site (www.microsoft.com/downloads).
4. For information about installing the Tivoli Enterprise Monitoring Server on z/OS, see the
Program Directory that comes with that product. For information about configuring the
monitoring server on z/OS, see the IBM Tivoli Monitoring Services on z/OS Program Directory,
GI11-4105.

134 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Required hardware
Table 28 details the minimum required hardware to install the components of IBM
Tivoli Monitoring.
Table 28. Hardware requirements for IBM Tivoli Monitoring components
Component Minimum requirements Optimum requirements
Processor Memory Disk Processor Memory Disk
Hub 1 GHz 512 MB 200 MB 1 GHz for 1 GB 250 MB
monitoring RISC
server architectures

2 GHz for Intel

architectures
Remote 1 GHz 512 MB 200 MB 1 GHz for 1 GB 250 MB
monitoring RISC
server architectures

2 GHz for Intel

architectures
Agent deploy 125 MB per 125 MB per
depot (for agent in the agent in the
remote depot depot
deployment)
Portal server 1 GHz 1 GB 800 MB 1 GHz for 2 GB 800 MB
RISC
architectures

2 GHz for Intel

architectures
Portal client 1 GHz 150 MB 2 GHz for Intel 300 MB
(browser or beyond the beyond the
desktop) needs of OS needs of OS
and other and other
applications applications
Tivoli Data 2-way (1 GHz 4 GB See TDW table 4-way 8 GB See TDW table
Warehouse for RISC, 2 processor 1
GHz for Intel) GHz for RISC,
2 GHz for Intel
Warehouse 2 GHz for Intel 512 MB 150 MB 2 GHz for Intel 1 GB 150 MB
Proxy agent architectures architectures
Summarization 1 GHz 512 MB 150 MB 1 GHz for 1 GB 150 MB
and Pruning RISC
agent architectures

2 GHz for Intel

architectures

The following requirements are additional:

v If multiple components are installed on a single server, their hardware
requirements are additive. For example, if the hub monitoring server and portal
server are installed on the same RISC server, it needs to be a two-processor 1
GHz machine with 2 GB of memory.

Appendix A. Hardware and software requirements 135

 v The best network connection possible is needed between the hub monitoring
server and portal server and also among the Tivoli Data Warehouse, Warehouse
Proxy agent, and Summarization and Pruning agent.
v A video card supporting 64,000 colors and 1024 x 768 required resolution on the
portal client is required.

Required software
Table 29 lists the required software for IBM Tivoli Monitoring.
Table 29. Required software for IBM Tivoli Monitoring
Component where the software is required

Product Supported version Portal

Portal browser
Management server Portal server desktop client client
IBM Runtime JRE 1.4.2 or higher X X X X
Environment for
Java
For UNIX X X X
computers: a Korn
shell interpreter
AIX only: xlC X
Runtime
Environment
(required for Global
Security Toolkit)
Microsoft Internet 6.0 with all critical X X
Explorer Microsoft updates
applied
Database1,2: To take advantage of X
v DB2 UDB version additional warehouse
8.1 or 8.23 capacity with DB2, use
OR DB2 version 8.2 with
Fix Pack 10
v Microsoft SQL
Server version
20004
OR
v Oracle 9.2 or 10.1
(for warehousing
only, not for the
Tivoli Enterprise
Portal)
IBM Tivoli Version 3.9 with Fix
Enterprise Console Pack 03

136 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Table 29. Required software for IBM Tivoli Monitoring (continued)
Component where the software is required

Product Supported version Portal

Portal browser
Management server Portal server desktop client client
For TCP/IP X X X X
communication:
v Windows 2000
Professional or
Server with
Service Pack 3 or
higher
v Microsoft
Winsock v1.1 or
later
v Microsoft TCP/IP
protocol stack
For SNA Microsoft SNA Server X
communication: v4.0 requires Service
v Windows 2000 Pack 1.
Professional or
IBM Communications
Server with
Server 5.0 requires fixes
Service Pack 3 or
JR10466 and JR10368.
higher
v Microsoft SNA
Server v3.0 or
later
v IBM
Communications
Server v5.0 or 5.2

Notes:
1. The only supported database for a Linux portal server is DB2.
2. Each database requires a driver:
v JDBC-DB2 driver for DB2
v MS SQL JDBC driver for MS SQL
v Oracle JDBC driver for Oracle
3. If you are installing Tivoli Enterprise Portal on a Linux computer, an OS user is required to support the
configuration of DB2. If such a user does not exist, the installation program attempts to create it. If the
installation program does not have the required authority, the installation fails.
4. IBM Tivoli Monitoring supports MS SQL Server 2000 only if the data is limited to code points inside the Basic
Multilingual Plane (range U+0000 to U+FFFF). This restriction does not apply to IBM DB2.

For all operating systems, see the GSKit documentation for the full set of
prerequisites related to that software, which is installed during the IBM Tivoli
Monitoring install. The GSKit documentation is available at http://www-
1.ibm.com/support/docview.wss?uid=pub1sc32136300.

Appendix A. Hardware and software requirements 137

138 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring
Appendix B. Uninstalling IBM Tivoli Monitoring
Use the following steps to uninstall IBM Tivoli Monitoring:
v “Uninstalling the entire IBM Tivoli Monitoring environment”
v “Uninstalling an individual IBM Tivoli Monitoring agent or component” on page
142
v “Uninstalling the IBM Tivoli Monitoring 5.x endpoint agent from the Tivoli
management region” on page 144
v “Uninstalling the IBM Tivoli Enterprise Console event synchronization” on page
144

Uninstalling the entire IBM Tivoli Monitoring environment

Use the following procedures to remove the entire IBM Tivoli Monitoring
environment from your computer.
v “Uninstalling on the environment Windows”
v “Uninstalling the environment on Linux or UNIX” on page 142
v “Uninstalling the Warehouse Proxy” on page 143

If you want to remove just one component such as an agent, see “Uninstalling an
individual IBM Tivoli Monitoring agent or component” on page 142.

Uninstalling on the environment Windows

Use the following steps to uninstall IBM Tivoli Monitoring from a Windows
computer:
1. From the desktop, click Start → Settings → Control Panel (for Windows 2000) or
Start → Control Panel (for Windows 2003).
2. Click Add/Remove Programs.
3. Select IBM Tivoli Monitoring and click Change/Remove. A window
(Figure 27) is displayed.

Figure 27. Uninstalling IBM Tivoli Monitoring

4. Select Remove and click Next.

Another window (Figure 28 on page 140) is displayed.

© Copyright IBM Corp. 2005 139

 Figure 28. Confirming the uninstallation

5. Click OK.
A progress window (Figure 29) is displayed.

Figure 29. Stopping Tivoli components before uninstallation

After Tivoli Enterprise services have stopped, you are prompted to indicate
whether you want to remove the Tivoli Enterprise Portal database (Figure 30).

Figure 30. Removing the portal database

6. Click Yes.
Another window (Figure 31) is displayed to request required information for
removing the database:

Figure 31. DB2 database information

7. Type the password for the DB2 administrator in the Admin Password field and
click OK.
The following progress window (Figure 32 on page 141) is displayed.

140 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Figure 32. Uninstallation progress window

A window that indicates that GSKit is being uninstalled is displayed

(Figure 33).

Figure 33. GSKit uninstallation

After GSKit is uninstalled, a window (Figure 34) is displayed:

Figure 34. Successful uninstallation

Appendix B. Uninstalling IBM Tivoli Monitoring 141

 8. Click Finish.

Uninstalling the environment on Linux or UNIX

Use the following steps to uninstall IBM Tivoli Monitoring from a UNIX computer:
1. From a command prompt, run the following command to change to the
appropriate /bin directory:
cd itm_installdir/bin

where $itm_installdir is the path for the home directory for IBM Tivoli
Monitoring.
2. Run the following command:
./uninstall.sh

A numbered list of product codes, architecture codes, version and release

numbers, and product titles is displayed for all installed products.
3. Type the number for the installed product that you want to uninstall. Repeat
this step for each additional installed product you want to uninstall.

Restart the computer to complete the uninstallation.

Note: If for any reason, the UNIX uninstallation is not successful, run the
following command to remove all IBM Tivoli Monitoring directories:
rm -r itm_installdir

Uninstalling an individual IBM Tivoli Monitoring agent or component

Use the following procedures to remove an agent or other individual IBM Tivoli
Monitoring component from your computer:
v “Uninstalling a component on Windows”
v “Uninstalling a component on Linux or UNIX” on page 143

Uninstalling a component on Windows

Use the following steps to remove a component on a Windows computer. You can
uninstall a single agent or the entire agent bundle (such as IBM Tivoli Monitoring
for Databases).
1. From the desktop, click Start → Settings → Control Panel (for Windows 2000) or
Start → Control Panel (for Windows 2003).
2. Click Add/Remove Programs.
3. Do one of the following:
a. To uninstall a single IBM Tivoli Monitoring component, such as the portal
server or portal client (but not all components), select IBM Tivoli
Monitoring.
b. To uninstall an agent bundle or a specific agent, select the agent bundle.
4. Click Change/Remove.
5. Do one of the following:
a. To uninstall a specific agent or component, select Modify.
b. To uninstall the entire agent bundle, select Remove.
6. Click Next.
7. If you are uninstalling an agent bundle, click OK to confirm the uninstallation.
8. If you are uninstalling an agent or component, do the following:

142 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

 a. For an agent, expand Tivoli Enterprise Monitoring Agents and select the
agent you want to uninstall.
b. For a component, select the component (such as Tivoli Enterprise Portal
Desktop Client).
c. Click Next.
d. Click Next on the confirmation screen.
e. Depending on the remaining components on your computer, there might be
a series of configuration panels. Click Next on each of these panels.
9. Click Finish to complete the uninstallation.

Uninstalling a component on Linux or UNIX

Use the following steps to remove a component on a UNIX computer. You can
uninstall a single agent or the entire agent bundle (such as IBM Tivoli Monitoring
for Databases).
1. From a command prompt, run the following command to change to the
appropriate /bin directory:
cd itm_installdir/bin

where $itm_installdir is the path for the home directory for IBM Tivoli
Monitoring.
2. Run the following command:
./uninstall.sh

A numbered list of product codes, architecture codes, version and release

numbers, and product titles is displayed for all installed products.
3. Type the number for the agent or component that you want to uninstall. Repeat
this step for each additional installed product you want to uninstall.

Restart the computer to complete the uninstallation.

Uninstalling the Warehouse Proxy

When you uninstall the Warehouse Proxy, the warehouse database is not dropped
and historical situations on the agent are not stopped.

Before you uninstall, do the following to account for this:

v Stop the historical situations.
v Drop the warehouse database.
v Remove the ODBC data source.
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 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>

Appendix B. Uninstalling IBM Tivoli Monitoring 143

 If you are using an MS SQL or Oracle database, see the documentation for your
database software for instructions on how to remove a data source.

Uninstalling the IBM Tivoli Monitoring 5.x endpoint agent from the
Tivoli management region
Run the following command to remove the IBM Tivoli Monitoring 5.x endpoint
agent from the Tivoli management region:
wuninst ITM61AGT <tmr_servername> -rmfiles

where <tmr_servername> is the name of the Tivoli management region server.

Uninstalling the IBM Tivoli Enterprise Console event synchronization

Use the following steps to uninstall the event synchronization from your event
server:
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.

144 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Appendix C. 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.

© Copyright IBM Corp. 2005 145

 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 logo,
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.

Intel is a trademark of Intel Corporation in the United States, other countries, or

both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.

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.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names can be trademarks or service marks of
others.

146 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

Index
Numerics C
12-hour format times 125 characters
asterisk 114
brackets 117
A dash relationship 117
escape 117
accessibility xii
floating point 122
Acknowledge icon 45
hexadecimal 115
acknowledgements 45, 75
hexadecimal integer 118
activities 51
inappropriate for encryption key 12
agents
literal 113
See monitoring agents
numeric 40
AIX servers
octal integer 118
event synchronization, installation 71
password usage 23
hardware requirements 135
percent sign 114
portal installation exceptions 35
scan directives 113
refresh signals to monitoring agent 110
scanset 117
supported versions for ITM components 133
scientific notation 115
Alerter Service 43
sequence in a log entry 113
alerts
signed decimal integer 118
See situations
special for commands xiii
application support
UNIX Log Agent fields 107
command for new agents 36
white space 113
definition and purpose 17
width option 114
hub monitoring server 19, 21
Circular Gauge icon 50
message information 18
clean endpoint on the gateway 80
product code for DB2 monitoring agent 103
CLI
Tivoli Enterprise Monitoring Server 128
See command line interface
ASCII logs, nonconforming 110
clock icon 45
Assess tool 92
Close Situation Event icon 46
automating manual tasks with policies 51
command line interface 68, 105
availability, continuous 97
commands
special characters xiii
syntax xiii
B components
backup agents
hub monitoring server 97, 98 support on Linux or UNIX 35
protocols 21, 25, 98 support on Windows 34
topology 98 encryption key use during installation 12
Bar chart icon 48 multiple, installing 4
baseline file 84 numbered list of those that are available 20
books post-installation window 16
feedback ix protocol communications 18
online ix starting, stopping 19
ordering ix configuration
see publications xi customer configuration file format 107
Bourne shells 109 customer file 106
Browser icon 48 environment variables
browsers syntax 109
See also Tivoli Enterprise Portal Browser UNIX Log Agent 108
client log files, specifying to monitor 106
installing 33 syslog daemon file 108
starting 37 conventions, typeface xii
files 129 Create New Situation icon 43
icon 48 customer configuration file 106
installing 33
Internet Explorer 37
path, default 33
support 35
D
daemons
view 48
kernel 108
business navigator 59

© Copyright IBM Corp. 2005 147

daemons (continued) endpoints (continued)
Linux 67 clean 79
stopping to test heartbeat 67 Windows 79
Syslog configuration file 106 Enterprise Level Item icon 60
UNIX 67 entry time format
data 12-hour format 125
agent-level collection 41 missing components 126
application support, adding 17 specifying 125
collecting for logs 42 text months 125
configuring 40 year, default 126
encryption key window 11 environment variables
historical duplication, avoiding 68
collection, configuring ix, 40 location for specifying 108
using 55 names in UNIX Log Agent 108
mapping specifications 118 syntax 109
ODBC-compliant 57 UNIX Log Agent control 106, 108
pruning ix environment, layout 4
samplings 40 escape characters 117
summarization and pruning 63 Event Console icon 46
type in format description 115 events
warehousing, required steps 5 acknowledgement 45
data types alerts 37
alphanumeric, valid 115 closing 45, 46
conversions 110 console
floating point 122, 123 properties 47
format specifications, default 119 view 46
inappropriate characters 113 forwarding 70, 75
integer 123 generating for situations 39
log entries 113, 120 icon 45
scan directives 113, 115 indicator 46
scanset 117 managing 45
signed numeric 121 notes 45
string, default width 115 open 46
white space 116 opening 45
database connection, testing 64 pure 46
DB2 receiving from monitoring servers 70
administrator registering 37
ID and password 25 rule base information 70
role during installation 24 sampled 46
agent 26, 36 severity 75
agent on UNIX operating systems 103 situation 21
creating database for warehouse proxy 6 SOAP information 70
data source 23 synchronization 3, 70
driver for ODBC connection 7 timestamp 45
exercise for using agent monitoring 103 trigger situation, stopping 46
installing 3 types 46
instance name 25 unsampled 46
located on computer with warehouse proxy 5 viewing 44, 70
login user 26 workflow 51
ODBC connection, setup 6 workspace 45
Dragging Mouse Pointer icon 60 exercises
dynamically refreshing the monitoring agent 109 application, launching 53
business navigator, creating view 59
CLI usage 68
E configuring after IBM Tivoli Monitoring install 3
configuring IBM Tivoli Monitoring 37
Edit Navigator View icon 60
custom monitors from script 99
education
embedded situations 96
See Tivoli technical training
events, filtering and responding 63
embedded situations, exercise 96
filtering and responding to events 76
encryption key
graphic view creation 59
inappropriate characters 12
graphical interface and monitoring capabilities 51
portal software installation 23
heartbeat test 66
using during component installation 12
historical data, using 55
window 11
Hot Standby 97
endpoints 80
IBM Tivoli Enterprise Console integration 63, 70
agent 26
IBM Tivoli Monitoring, installing 3
agent code 21

148 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

exercises (continued) gateways (continued)
managed system viewing 63, 66 multiple 79
overview 3 names (labels) of all, list 80
policies 51 naming 80
situations 43 operating systems of all endpoints, list 80
summarization and pruning agent 63 policy region 80
Take Actions 54 remote servers
Tivoli Enterprise Portal views 48 eliminating 88
upgrading 79 mapping 86
URL monitoring 101 Windows endpoint assigned 79
verifying IBM Tivoli Monitoring after install 37 Generic User Log Support (GULS) 110
Expert Advice for situations 106 Graphic icon 48

F H
field suppression in format description 114 heartbeat
fields frequency 66
Circular Gauge 50 missed 66
IBM Tivoli Enterprise Console server 72 purpose 66
Linear Gauge 49 testing exercise 66, 67
log entry 112, 116 history data
padding with zeros 121 configuring 39, 40, 65
Tivoli Enterprise Login window 76 permission to configure 40
UNIX Log Agent customer configuration 107 Warehouse Proxy prerequisite 39
URL monitoring 102 Hot Standby
Warehouse Proxy 40 backup for hub monitoring server 97
filters configuration 97, 98
clearing 57 continuous availability 97
color-coded 77 verifying 99
criteria, adding 57 hub monitoring server
dynamic type 73 application support, adding 21
events backup 97
console properties, setting 47 communication protocol 23, 25
types, controlled viewing 74 configuring 20
viewing 76 default values 39
names 76 failure fallback 97
operators 77 host name 25
prefilters and postfilters 56 information gathering 80
queries, using 56 installing and configuring 7
required 57 naming 72, 80
severity 76 planning to install 4, 5, 25
situations 62 purpose 66
status 77
tools 74
types 73, 76
floating point numbers 122
I
icons
format command 110
Acknowledge 45
format description components 113
Bar chart 48
data mapping specifications 118
Browser 48
data type 115
Circular Gauge 50
field suppression 114
clock 45
literals 113
Close Situation event 46
offsets 114
Close Situation Event 46
size 115
conventions xii
width 114
Create new Situation 44
formatting mapped data 119
Create New Situation 43
forwarding events 72
Dragging mouse pointer 60
Edit Navigator View 60
Enterprise level item 60
G Event Console 46
gateways event, acknowledged 45
ignored by Scan tool 81 Graphic 48
information gathering 80 Graphic View 59
infrastructure component 82 graphic view, creating 59
location 79 indicators 37
mapping 81 Linear Gauge 49

Index 149
icons (continued) Linux (continued)
linked chain 45 monitoring server environment 5
Message Log 47 portal desktop client 32, 33
Mouse hand pointer 59 portal server, installing 22, 24
Navigator editor 59 test environment 5
New Policy 51 literals in format description 113
Notepad 48, 49 Locking Conflict workspace 106
Pie chart 48 logs
Plot chart 48 ASCII 110
Properties 47, 48, 49 command syntax for generic users 112
Properties editor 49 daemons 106
Query 49, 56, 57 data collection, configuring 42
Query editor 57 dynamically changing during monitoring agent
removing 60 activity 109
Save 47 entry times 125
Saving 59 example format for generic user 111
Select 59 format description 112
selecting 60 monitoring other types 110
Situation editor 44, 45 selecting for monitoring 106
Split Horizontally 46, 59 supported types 110
Split Vertically 46, 59 timestamps 125
status indicator 45 user, generic 110
Stop situation 46, 52
Table 48
Target mouse pointer 60
Terminal 48
M
manuals
Thresholds 47
See also publications
Time span 55
feedback ix
Tivoli Enterprise Portal Desktop Client 41
online ix
Universal Message Console 47
ordering ix
infrastructure road map 84
mapping data
installing
format 119
agents 3
specifications 118
backup monitoring server 98
mapping format specifier components 120
basic 3
data type 122
DB2 3
escape characters 123
environment layout 3, 4
literals 120
high-level steps 3
options 120
hub server 3
precision 122
portal desktop client 3
size 122
portal server 3
width 121
preconfiguration 3
Message Log icon 47
requirements for hardware and software 3
messages 102, 108
metafiles
adding to the Universal Agent 100
J importing 100
Java SDK 22, 27, 31 monitoring application script 100
JDBC drivers 64 metrics, using to create situations 96
missed heartbeat from monitoring agent, meaning 66
monitoring agents
K application support 103
configuring 3, 98
kernel daemons 67, 108
daemons 67
keywords
deployment 13
conventions xii
heartbeats 66, 67
modifying configuration 105
installing 3
Korn shells 109
managed system status 66
non-operating system 3
online or offline status 66, 67
L product codes 21
layout of environment 4 refreshing 109
leading zeros 121 starting and stopping 69
legal notices 145 summarization and pruning 63
Linear Gauge icon 49 types 69
Linux users’ guides troubleshooting information 102
configuring portal server 25 monitoring application script 100
daemons 67

150 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

monitoring servers policies (continued)
AIX 35 usage 51
application support 21 portal desktop client
command for starting 21 installing 3
communication protocols 17 Linux
configuring 16, 20 configuring 33
encryption key when installing 23 installing 32
Hot Standby configuration 98 starting 37
hub 4, 5 required support 3, 33
installing and configuring 7 software required 136
Linux 5 uninstalling 143
location, specifying 17 portal server
naming format 20 See Tivoli Enterprise Portal Server
refresh signals 110 precision 122
restarting 22 problem determination 7, 102
secondary 98 product codes for monitoring agents 21
Solaris 35 profile managers
stopping 22, 34 See also profiles
UNIX, installing 19 tools for upgrading 94
upgrade environment 5 upgrade results 91
Windows environment 4, 7 profiles
months, text form 125 Assess and Upgrade tools 92
Mouse Hand Pointer icon 59 creating and distributing to a Windows endpoint 79
mouse pointer 60 exercise for upgrading 92
rollback option after upgrading 96
situations and managed system lists for upgrading 81
N staged upgrades 94
upgrading profile managers
Navigator editor icon 59
See profile managers
Navigator items, sharing 60
Properties icon 47, 49
New Policy icon 51
protocols
Notepad icon 48
backup 21
default for communications 18, 21
hub monitoring server 17
O pruning
ODBC criteria setting 63
configuration, previous 39 disabling 66
connection exercise 63
setup 6 frequency settings, default 64
testing 7 managing ix, 63
data source, creating 104 purpose and definition 63
registering databases 105 settings, system-wide 63
removing manually 143 publications
offsets in format description 114 accessing online xi
online publications, accessing xi feedback ix
Open Database Connectivity online ix
See ODBC ordering ix, xi
optimizing CLI settings 105
ordering publications ix, xi
Q
queries
P assigning to gauge 49
perform actions with policies 51 creating for monitoring servers 55, 56
Pie chart icon 48 deleting 58
Plot chart icon 48 editor 56, 57
policies exporting 58
activities 52 icon 58
adding 51 mixing attributes from different groups 57
creating 51 none for Universal Message Log or TWORKLST (Worklist
description 51 Log) 42
details 51 ODBC database 57
distribution 51 Query editor icon 57
icon 51 Query icon 49, 56
naming and renaming 51 quick settings, applying 47
region of gateway and endpoint 80 quick threshold, setting 47
saving 52
starting 52

Index 151
R system conditions, monitoring (continued)
using workspaces 106
RAS log 106 System Overview workspace 106
reflex action 54
refresh signal 110
replacements for placeholder attribute value 87
road map for the infrastructure 84 T
row limit, setting 47 Take Action commands, creating and sending 54
Target mouse pointer icon 60
Terminal icon 48
S text months 125
threshold
Save icon 47 indicator 47
scan directives quick 47
definition and purpose 112 Thresholds icon 47
examples of correct usage 113 Time span icon 55
scansets 117 time span, setting 55
scheduling work with policies 51 timestamps 125
Secondary TEMS 98 Tivoli Enterprise Portal Browser
Select icon 59 See also browsers
severity statuses 77 client support 35
sharing Navigator items 60 memory requirement 135
shells, Bourne, Korn, and C 109 mode 49
Situation editor icon 44 starting client 38
situations support 25
all, viewing 69 Tivoli Enterprise Portal Desktop Client icon 41
associated 61, 62 Tivoli Enterprise Portal Server 3
closing 46 agents support 34
creating 43 communication protocols 23
definition and purpose 37 configuring 23
editing 44, 45 configuring on Linux 25
editor 43 database name 25
embedded 96 encryption key when installing 23
Expert Advice 106 installing 4
exporting details to a file 68 Linux 5, 22, 24
flyover listings 45 required support 3, 33
forwarding 75 starting 26
generating 39 stopping 34
managing 68 upgrade environment 5
monitoring agents, default settings for each 38 Windows 4, 22
opening 105 Tivoli Monitoring Services logs 42
pure events 46 Tivoli software information center xi
reflex action 54, 70 Tivoli technical training xii
sampled events 46 toolkit image 83
status of each 38 tools
stopping 46, 51 access 92
triggering an event 39 upgrade 92
UDB_DB_SQL_Fail_High 105 trace and logging information 102
UDB_Status_Warning 105 trademarks 146
UNIX 44 training, Tivoli technical xii
viewing 38 typeface conventions xii
size in format description 115
SOAP
information 70, 87
port 87 U
server 87 UDB_DB_SQL_Fail_High situation 105
Solaris servers UDB_Status_Warning situation 105
hardware requirements 133 Universal Agent
portal installation exceptions 35 adding metafile 100
supported versions for ITM components 133 configuring and starting 101
Split Horizontally icon 46 customer monitor creation 99
Split Vertically icon 46 installing 99
Stop situation icon 46, 52 monitoring a URL 101
syntax for environment variables monitoring application script 100
See environment variables Universal Message Console icon 47
syslog daemon configuration file 108 Universal Message console view 47
system conditions, monitoring UNIX
using situations 105 commands help 68

152 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring

UNIX (continued) views and viewing (continued)
components, uninstalling 143 workspace properties 49
daemons 67
environment, uninstalling 142
event synchronization 71
identity code 69
W
warehouse proxy
monitoring agent
configuring and registering 39
collection attributes 41
database creation 6
configuring 30
DB2 installation, effect 5
installing 28, 29
limited platform support 4
new situations 44
ODBC connection setup 6
support 35
prerequisite for history collection 39
monitoring server
restarting 40
hub 4
uninstalling 143
installing 19
white space
protocol 25
data mapping specifications 118
situations, editing 45
examples of usage 114
test environment 4
limits in customer configuration file format 107
uninstalling event synchronization 144
literals 116
UNIX Log Agent
log entry fields 113, 115
caution when installing 107
scan directives 112
configuration file format 107
skipping over 116
debugging log 108
width in format description 114
environment variables 108
Windows
installing 106
agent code 21
location 106
creating a new user 6
logs monitored 106
environment setup 4
RAS log 106
installing monitoring server 7
UNIX monitoring agent
Tivoli Enterprise Portal server, installing 22
multiple copies 103
Tivoli Enterprise Portal Server, installing 22
starting 103
upgrading test 5
stopping 103
warehouse proxy supported 4
unsampled events 46
witmscantmr command 84
Upgrade tool 92
wizard, installation 7, 22, 26
upgrading
work, scheduling with policies 51
information gathering 80
workspaces
infrastructure 84
defaults 62
required software 79
defining 48
setup 79
editing 49
testing 79
Enterprise 46
toolkit 79
Enterprise Status 44, 73
URL monitoring 101
event 45
Event Console view, adding 46
graphic view within 59
V identity 49
views and viewing integrating data from agents in one place 57
Browser 48 locking conflicts 106
circular gauge 49 Log Entries 127
console 46 Managed System Status 67
creating and customizing 48 Memory 49
default situations 37, 38, 46 message log view, adding 47
Enterprise 44 Monitored Logs 127
events 44 multiple 106
Grapher 52 naming 47
graphic 37, 45 opening 46
linear gauge 49 options 49
log for messages 47 Process overview 54
Memory Allocation 49 properties
message 46 editing 48
Notepad chart 48 saving 47
product codes for agent support 36 properties, saving 47
properties, editing 48 saving 49
saving 47, 48 system overview 106
situation events 21 testing 49
statuses of situations 38 Universal message log view, setting 47
type, changing 48 using to monitor system conditions 106
Universal Message console 47 view, saving 47

Index 153
X
XML output file for infrastructure upgrade 84

Y
year, omitting from entry times 126

Z
zeros
leading 121
trailing 121

154 IBM Tivoli Monitoring: Exploring IBM Tivoli Monitoring




Printed in USA

SC32-1803-00