Tivoli IBM Tivoli Monitoring


Version 6.1.0

Installation and Setup Guide

GC32-9407-00
 Tivoli IBM Tivoli Monitoring
®


Version 6.1.0

Installation and Setup Guide

GC32-9407-00
 Note
Before using this information and the product it supports, read the information in Appendix I, “Notices,” on page 253.

First Edition (November 2005)

This edition applies to the 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
Tables . . . . . . . . . . . . . . . vii Required order of installation or upgrade of IBM
Tivoli Monitoring component products . . . . . 22
Figures . . . . . . . . . . . . . . . ix Windows installation consideration - user authority 22
Linux or UNIX Installation considerations . . . . 22
Create an IBM Tivoli account for installing and
About this guide . . . . . . . . . . . xi maintaining the installation directory . . . . . 22
Who should read this guide . . . . . . .
. xi . Host name for TCP/IP network services . . . . 23
Publications . . . . . . . . . . . .
. xi . Use of fully qualified path names . . . . . . 23
IBM Tivoli Monitoring library . . . . .
. xi . Multiple Network Interface Cards . . . . . . 23
Accessing terminology online . . . . . . . xii Installing into an NFS environment . . . . . 23
Accessing publications online . . . . . . . xii File descriptor (maxfiles) limit . . . . . . . 24
Ordering publications. . . . . . . . . . xiii Hardware and software requirements . . . . . . 24
Accessibility . . . . . . . . . . . . . . xiii Supported operating systems . . . . . . . 24
Tivoli technical training . . . . . . . . . . xiii Required hardware . . . . . . . . . . . 26
Support information . . . . . . . . . . . xiii Required software . . . . . . . . . . . 28
Conventions used in this guide . . . . . . . xiii Planning considerations for the Tivoli Data
Typeface conventions . . . . . . . . . . xiii Warehouse. . . . . . . . . . . . . . . 30
Tivoli command syntax . . . . . . . . . xiv Estimating the required size of your database . . 30
Understanding the disk requirements for your
Chapter 1. Overview of IBM Tivoli database . . . . . . . . . . . . . . 35
Monitoring . . . . . . . . . . . . . 1 Increasing the size of your database (DB2 only) 36
What’s new in this release . . . . . . . . . . 1
Moving to IBM Tivoli Monitoring . . . . . . . 3 Chapter 4. Upgrading from a previous
Components of IBM Tivoli Monitoring . . . . . . 3 installation . . . . . . . . . . . . . 39
Tivoli Enterprise Monitoring Server . . . . . . 4 Terminology changes . . . . . . . . . . . 40
Tivoli Enterprise Portal . . . . . . . . . . 5 Upgrade planning . . . . . . . . . . . . 40
Tivoli Enterprise Monitoring agents . . . . . . 6 When to run the upgrade . . . . . . . . . 40
Tivoli Data Warehouse . . . . . . . . . . 6 Installation directory for upgraded components 40
Tivoli Enterprise Console event synchronization Configuration settings for upgraded agents . . . 41
component . . . . . . . . . . . . . . 6 Candle Management Workstation coexistence . . 41
Additional unsupported OMEGAMON functions 41
Chapter 2. Planning a deployment of CandleNet Portal database . . . . . . . . 42
IBM Tivoli Monitoring . . . . . . . . . 9 Required Java JRE . . . . . . . . . . . 42
Overview of the design process . . . . . . . . 9 Migrated information when upgrading from a
Assessing the existing environment . . . . . . 10 previous version . . . . . . . . . . . . 42
Physical Perspective . . . . . . . . . . 10 Migrating data from an existing Warehouse Proxy
Organizational perspective . . . . . . . . 11 database . . . . . . . . . . . . . . . 42
Planning your design . . . . . . . . . . . 12 Before you run the tool . . . . . . . . . 42
Determining the number of monitoring servers Configuring the migration tool . . . . . . . 43
needed . . . . . . . . . . . . . . . 12 Running the warehouse migration tool . . . . 44
Determining server placement . . . . . . . 12 Status tables . . . . . . . . . . . . . 44
Determining when to use the IBM Tivoli Using existing OMEGAMON agents with IBM
Enterprise Console . . . . . . . . . . . 13 Tivoli Monitoring . . . . . . . . . . . . 45
Determining when to use the remote deployment
feature . . . . . . . . . . . . . . . 14 Chapter 5. Installing IBM Tivoli
Sample deployment scenarios . . . . . . . . 14 Monitoring . . . . . . . . . . . . . 47
Small monitoring environment . . . . . . . 14 Installing and configuring the hub Tivoli Enterprise
Medium monitoring environment . . . . . . 16 Monitoring Server . . . . . . . . . . . . 48
Large monitoring environment . . . . . . . 17 Windows: Installing the hub monitoring server 48
Linux or UNIX: Installing a hub monitoring
Chapter 3. Planning the installation of server . . . . . . . . . . . . . . . 51
your environment . . . . . . . . . . 21 Installing and configuring the remote monitoring
Overview of the installation process . . . . . . 21 servers . . . . . . . . . . . . . . . . 54
Specific information to have ready . . . . . . . 21 Windows: Installing the remote monitoring
Naming your monitoring server . . . . . . 22 server . . . . . . . . . . . . . . . 54

© Copyright IBM Corp. 2005 iii

 Linux or UNIX: Installing a remote monitoring Starting Manage Tivoli Enterprise Monitoring
server . . . . . . . . . . . . . . . 57 Services . . . . . . . . . . . . . . . 105
Installing the Tivoli Enterprise Portal Server . . . 59 Starting Manage Tivoli Enterprise Monitoring
Windows: Installing the portal server . . . . . 59 Services on Windows computers . . . . . . 105
Linux: Installing the portal server . . . . . . 61 Starting Manage Tivoli Enterprise Monitoring
Installing monitoring agents . . . . . . . . . 64 Services on Linux or UNIX computers . . . . 106
Windows: Installing a monitoring agent . . . . 65 Changing the configuration of the Tivoli Enterprise
Linux or UNIX: Installing a monitoring agent . . 67 Monitoring Server . . . . . . . . . . . . 106
Installing Tivoli Enterprise Portal desktop client . . 70 Configuring or changing the monitoring server
Windows: Installing the desktop client . . . . 70 connection for agents . . . . . . . . . . . 107
Linux: Installing the desktop client . . . . . 72 Starting and stopping components . . . . . . 108
Installing support for agents on the monitoring Configuring user security . . . . . . . . . 109
server, portal server, and desktop client . . . . . 73 Enabling security on the hub monitoring server 109
Installing application support on monitoring Creating a user on the Tivoli Enterprise Portal 109
servers . . . . . . . . . . . . . . . 73 Configuring failover support . . . . . . . . 110
Installing application support on the Tivoli Installing the hub and backup hub monitoring
Enterprise Portal Server . . . . . . . . . 77 servers at the same time . . . . . . . . . 110
Installing application support on the Tivoli Adding application support on the backup hub
Enterprise Portal desktop client . . . . . . . 79 monitoring server . . . . . . . . . . . 110
Installing the language packs . . . . . . . . 81 Configuring the Hot Standby feature on
Starting the Tivoli Enterprise Portal client . . . . 82 monitoring servers . . . . . . . . . . . 111
Starting the desktop client . . . . . . . . 82 Configuring agents . . . . . . . . . . 112
Starting the browser client . . . . . . . . 82 Verifying that failover support is working . . . 112
Adding application support to the monitoring
Chapter 6. Installing the IBM Tivoli server . . . . . . . . . . . . . . . . 112
Enterprise Console event Using Manage Tivoli Enterprise Monitoring
Services to add application support to a
synchronization . . . . . . . . . . . 85 monitoring server . . . . . . . . . . . 112
Planning the deployment of your IBM Tivoli Using the itmcmd support command to add
Enterprise Console integration . . . . . . . . 86 application support to a Linux or UNIX
One or more hub monitoring servers and a single monitoring server . . . . . . . . . . . 113
event server . . . . . . . . . . . . . 86 Configuring the heartbeat interval . . . . . . 114
A single hub monitoring server and multiple
event servers . . . . . . . . . . . . . 87
Multiple hub monitoring servers and multiple
Chapter 8. Advanced Linux or UNIX
event servers in a hub and spoke configuration . 87 monitoring server configuration . . . 117
Information to gather before you begin . . . . . 89 Configuring permissions for a monitoring server
Installing event synchronization on your event on a non-NIS Solaris . . . . . . . . . . . 117
server . . . . . . . . . . . . . . . . 89 Firewall support . . . . . . . . . . . . 117
Installing from a wizard . . . . . . . . . 90 Sample partition file . . . . . . . . . . 118
Installing from the command line . . . . . . 93 Editing the partition file in Manage Tivoli
Installing from the command line using a silent Enterprise Monitoring Services . . . . . . 118
install . . . . . . . . . . . . . . . 95
Manually importing the event synchronization Chapter 9. Additional Tivoli Enterprise
class files and rule set . . . . . . . . . . 99 Portal configuration . . . . . . . . 119
Installing monitoring agent .baroc files on the Using SSL between the portal server and the client 119
event server . . . . . . . . . . . . . . 101 Enabling and disabling SSL for the Tivoli
Configuring your monitoring server to forward Enterprise Portal Server . . . . . . . . . 120
events . . . . . . . . . . . . . . . . 102 Setting up asymmetric encryption . . . . . 120
Starting and stopping the Situation Update Disabling SSL . . . . . . . . . . . . 123
Forwarder process . . . . . . . . . . . . 103 Configuring an external Web server to work with
Changing the configuration of the event Tivoli Enterprise Portal . . . . . . . . . . 123
synchronization on the event server . . . . . . 103 Configuring Internet Information Server V5.0 123
Defining additional monitoring servers to the event Configuring Internet Information Server V6.0 124
server . . . . . . . . . . . . . . . . 104 Configuring IBM HTTP Server on Linux . . . 125
Changing the TCP/IP timeout setting on your Configuring a portal client connection to an
event server . . . . . . . . . . . . . . 104 external Web server . . . . . . . . . . . 126
Browser client . . . . . . . . . . . . 126
Chapter 7. Configuring IBM Tivoli Desktop client . . . . . . . . . . . . 126
Monitoring components . . . . . . . 105 Firewall network address translation (NAT) or
multiple network interface cards . . . . . . . 127

iv IBM Tivoli Monitoring: Installation and Setup Guide

 Defining a Tivoli Enterprise Portal Server Generic Windows monitoring agent worksheet . . 170
interface . . . . . . . . . . . . . . 127 Generic Linux or UNIX monitoring agent
Firewall scenarios for Tivoli Enterprise Portal . . 128 worksheet . . . . . . . . . . . . . . 171
Windows portal desktop client worksheet . . . . 172
Chapter 10. Deploying monitoring Linux portal desktop client worksheet . . . . . 173
across your environment . . . . . . 135 Monitoring server communications protocol details
worksheet . . . . . . . . . . . . . . 174
Populating your agent depot . . . . . . . . 135
Populating the agent depot from the installation
image . . . . . . . . . . . . . . . 136 Appendix B. Performing a silent
Populating the agent depot with the tacmd installation of IBM Tivoli Monitoring . 175
addBundles command . . . . . . . . . 138 Creating and using a Windows response file . . . 175
Managing your agent depot . . . . . . . . 139 Running the silent install from the command
Sharing an agent depot across your environment 139 line with parameters . . . . . . . . . . 176
Deploying OS agents . . . . . . . . . . . 140 Using SMS . . . . . . . . . . . . . 176
Requirements for the tacmd createNode Performing a silent installation on a Linux or
command . . . . . . . . . . . . . 140 UNIX computer . . . . . . . . . . . . 177
Using the tacmd createNode command . . . . 141 Installing components with a response file . . 177
Deploying non-OS agents . . . . . . . . . 142 Configuring components with a response file 179
Deploying through the portal . . . . . . . 142
Deploying through the command line . . . . 142 Appendix C. Firewalls . . . . . . . . 181
Deploying a Universal Agent . . . . . . . 143 Basic implementation . . . . . . . . . . . 181
Implementation with address translation . . . . 181
Chapter 11. Configuring the Sample scenarios . . . . . . . . . . . . 181
Warehouse Proxy for the Tivoli Data Scenario 1: Hub monitoring server INSIDE and
Warehouse . . . . . . . . . . . . 145 monitoring agents OUTSIDE . . . . . . . 182
Warehouse Proxy planning . . . . . . . . . 146 Scenario 2: Hub and remote monitoring servers
Creating a user for the Warehouse Proxy . . . . 147 INSIDE and monitoring agents OUTSIDE . . . 182
Create a Windows user for a DB2 database . . 147 Scenario 3: Hub monitoring server INSIDE,
Create the Tivoli Data Warehouse database . . . 147 remote monitoring server and agents OUTSIDE . 182
Configuring your DB2 or Microsoft SQL database 148
Setting up the ODBC connection . . . . . . . 148 Appendix D. IBM Tivoli Product Codes 185
Setting up a connection to a local database . . 149
Setting up a connection to a remote database 150 Appendix E. Command reference . . . 187
Configuring and registering the Warehouse Proxy 151 tacmd CLI commands . . . . . . . . . . 187
Additional environment variables that can be set tacmd addBundles . . . . . . . . . . 188
for the Warehouse Proxy . . . . . . . . . 153 tacmd addSystem . . . . . . . . . . . 190
Database initialization . . . . . . . . . 153 tacmd configurePortalServer . . . . . . . 192
Work queue . . . . . . . . . . . . . 153 tacmd configureSystem . . . . . . . . . 194
Connection pool . . . . . . . . . . . 155 tacmd createNode . . . . . . . . . . . 196
RPC threads and export requests . . . . . . 155 tacmd describeSystemType . . . . . . . . 201
Timeout . . . . . . . . . . . . . . 155 tacmd help . . . . . . . . . . . . . 202
WAREHOUSELOG table . . . . . . . . . 156 tacmd listBundles . . . . . . . . . . . 203
tacmd listSystems . . . . . . . . . . . 204
Chapter 12. Configuring IBM Tivoli tacmd login . . . . . . . . . . . . . 205
Monitoring Web Services (SOAP tacmd logout . . . . . . . . . . . . 206
Server) on Windows . . . . . . . . 159 tacmd removeBundles . . . . . . . . . 207
tacmd restartAgent . . . . . . . . . . 208
Defining hubs . . . . . . . . . . . . . 159
tacmd startAgent . . . . . . . . . . . 210
Adding users . . . . . . . . . . . . . 160
tacmd stopAgent . . . . . . . . . . . 212
Verifying the configuration . . . . . . . . . 160
tacmd updateAgent . . . . . . . . . . 214
tacmd viewAgent . . . . . . . . . . . 215
Appendix A. Installation worksheets 163 tacmd viewDepot . . . . . . . . . . . 216
Windows hub monitoring server worksheet . . . 164 tacmd viewNode . . . . . . . . . . . 217
Linux or UNIX hub monitoring server installation Return codes . . . . . . . . . . . . 218
worksheet . . . . . . . . . . . . . . 165 itmcmd commands . . . . . . . . . . . 218
Windows remote monitoring server worksheet . . 166 cinfo . . . . . . . . . . . . . . . 219
Linux or UNIX remote monitoring server itmcmd agent . . . . . . . . . . . . 222
installation worksheet . . . . . . . . . . 167 itmcmd config . . . . . . . . . . . . 224
Windows portal server worksheet . . . . . . 168 itmcmd dbagent . . . . . . . . . . . 226
Linux portal server worksheet . . . . . . . . 169 itmcmd manage . . . . . . . . . . . 228

Contents v
 itmcmd support . . . . . . . . . . . 229 Removing an agent through the Tivoli
itmcmd server . . . . . . . . . . . . 231 Enterprise Portal . . . . . . . . . . . 247
SetPerm . . . . . . . . . . . . . . 232 Uninstalling the Warehouse Proxy . . . . . . 247
IBM Tivoli Enterprise Console commands . . . . 233 Removing the ODBC data source connection 247
sitconfig.sh . . . . . . . . . . . . . 234 Uninstalling the IBM Tivoli Enterprise Console
sitconfsvruser.sh . . . . . . . . . . . 236 event synchronization . . . . . . . . . . 248
upg_sentry_baroc.pl . . . . . . . . . . 237
upg_tec_baroc.pl . . . . . . . . . . . 238 Appendix H. Support information . . . 249
Searching knowledge bases . . . . . . . . . 249
Appendix F. Maintaining the EIB on Searching the information center . . . . . . 249
Linux or UNIX . . . . . . . . . . . 239 Searching the Internet . . . . . . . . . 249
Obtaining fixes . . . . . . . . . . . . . 249
Appendix G. Uninstalling IBM Tivoli Receiving weekly support updates . . . . . . 250
Contacting IBM Software Support . . . . . . 250
Monitoring . . . . . . . . . . . . 241 Determining the business impact . . . . . . 251
Uninstalling the entire IBM Tivoli Monitoring Describing problems and gathering information 252
environment . . . . . . . . . . . . . . 241 Submitting problems . . . . . . . . . . 252
Uninstalling the environment on Windows . . 241
Uninstalling the environment on Linux or UNIX 243
Uninstalling an individual IBM Tivoli Monitoring
Appendix I. Notices . . . . . . . . . 253
agent or component . . . . . . . . . . . 244 Trademarks . . . . . . . . . . . . . . 254
Uninstalling a component on Windows . . . . 244
Uninstalling a component on Linux or UNIX 245 Index . . . . . . . . . . . . . . . 255
Uninstalling OMEGAMON agents . . . . . 245

vi IBM Tivoli Monitoring: Installation and Setup Guide

Tables
1. Planning a deployment of IBM Tivoli 30. IBM Tivoli Enterprise Console event
Monitoring . . . . . . . . . . . . . 9 synchronization configuration fields, continued 91
2. Overview of the design process . . . . . . 9 31. IBM Tivoli Enterprise Console event
3. Installation and configuration steps . . . . 21 synchronization configuration values . . . . 96
4. Supported operating systems . . . . . . 24 32. Configuration tasks available through
5. Hardware requirements for IBM Tivoli Manage Tivoli Enterprise Monitoring Services 105
Monitoring components . . . . . . . . 27 33. Parameters for the itmcmd manage command 106
6. Required software for IBM Tivoli Monitoring 28 34. Communications protocol settings . . . . 106
7. Tivoli Data Warehouse database size 35. Communications protocol settings . . . . 108
estimation worksheet . . . . . . . . . 34 36. Parameters for the itmcmd support command 113
8. Database size examples . . . . . . . . 35 37. Setting up asymmetric encryption . . . . . 120
9. Upgrading from OMEGAMON 350 or 360 39 38. Remote agent deployment tasks . . . . . 135
10. OMEGAMON to IBM Tivoli Monitoring 39. Agent depot management commands 139
terminology . . . . . . . . . . . . 40 40. Warehouse Proxy configuration steps 145
11. Unsupported OMEGAMON functions . . . 41 41. Overview of SOAP Server configuration steps 159
12. KHDENV_MIG file variables for warehouse 42. TCP/IP Fields in Hub Specification Dialog 159
migration . . . . . . . . . . . . . 43 43. SNA Fields in Hub Specification Dialog 160
13. IBM Tivoli Monitoring high-level installation 44. Windows hub monitoring server installation
steps . . . . . . . . . . . . . . . 47 worksheet. . . . . . . . . . . . . 164
14. Communications protocol settings . . . . . 49 45. Linux or UNIX hub monitoring server
15. Steps for installing a portal server on a Linux installation worksheet . . . . . . . . . 165
computer . . . . . . . . . . . . . 51 46. Windows remote monitoring server
16. UNIX monitoring server protocols and values 53 installation worksheet . . . . . . . . . 166
17. Remote monitoring server communications 47. Linux or UNIX remote monitoring server
protocol settings . . . . . . . . . . . 55 installation worksheet . . . . . . . . . 167
18. Steps for installing a remote monitoring server 48. Windows portal server worksheet . . . . . 168
on a Linux or UNIX computer . . . . . . 57 49. Linux portal server worksheet . . . . . . 169
19. UNIX monitoring server protocols and values 58 50. Generic Windows monitoring agent
20. Steps for installing a portal server on a Linux worksheet. . . . . . . . . . . . . 170
computer . . . . . . . . . . . . . 61 51. Generic monitoring agent for a Linux or
21. UNIX monitoring server protocols and values 63 UNIX computer worksheet . . . . . . . 171
22. Communications protocol settings . . . . . 66 52. Windows portal desktop client worksheet 172
23. Steps for installing a monitoring agent on 53. Linux portal desktop client worksheet 173
Linux or UNIX . . . . . . . . . . . 67 54. Monitoring server communications protocol
24. UNIX monitoring server protocols and values 68 details worksheet . . . . . . . . . . 174
25. Communications protocol settings . . . . . 71 55. Installation and configuration steps . . . . 175
26. Installing the portal client on Linux . . . . 72 56. Silent installation parameters for UNIX 178
27. Communications protocol settings . . . . . 75 57. Component product codes . . . . . . . 185
28. Tivoli Enterprise Console event 58. Return Codes for tacmd CLI commands 218
synchronization installation and configuration 59. EIB Files . . . . . . . . . . . . . 239
steps . . . . . . . . . . . . . . . 85 60. Candle OMEGAMON Release 04R1 . . . . 246
29. IBM Tivoli Enterprise Console event 61. Candle OMEGAMON Release BIV110 246
synchronization configuration fields . . . . 90

© Copyright IBM Corp. 2005 vii

viii IBM Tivoli Monitoring: Installation and Setup Guide
Figures
1. IBM Tivoli Monitoring environment . . . . . 4 15. Intranet with external Web server . . . . . 130
2. Event synchronization overview . . . . . . 7 16. Intranet with integral Web server; Internet
3. Comparison of event management options 8 with external Web server . . . . . . . . 131
4. Small IBM Tivoli Monitoring environment 15 17. Intranet and Internet with integral and
5. Medium IBM Tivoli Monitoring environment 16 external Web servers . . . . . . . . . 132
6. Large deployment of IBM Tivoli Monitoring 18 18. Two host addresses, intranet and Internet,
7. Installing application support . . . . . . 74 with integral and external Web servers . . . 133
8. Installing application support . . . . . . 78 19. Uninstalling IBM Tivoli Monitoring . . . . 241
9. Installing application support . . . . . . 80 20. Confirming the uninstallation . . . . . . 242
10. One or more hub monitoring servers 21. Stopping Tivoli components prior to
connecting to a single event server . . . . . 86 uninstallation . . . . . . . . . . . 242
11. Single hub monitoring server and multiple 22. Removing the portal database . . . . . . 242
event servers . . . . . . . . . . . . 87 23. Database information . . . . . . . . . 242
12. Multiple hub monitoring servers and multiple 24. Uninstallation progress window . . . . . 243
event servers in a hub and spoke configuration 88 25. GSKit uninstallation . . . . . . . . . 243
13. Hierarchy for the heartbeat interval . . . . 115 26. Successful uninstallation . . . . . . . . 243
14. Intranet with integral Web server . . . . . 129

© Copyright IBM Corp. 2005 ix

x IBM Tivoli Monitoring: Installation and Setup Guide
About this guide
This guide describes the installation and configuration of IBM® Tivoli® Monitoring
on both Windows® and Linux® or UNIX® computers.

Who should read this guide

This guide is designed for those responsible for planning and installing the IBM
Tivoli Monitoring environment. This includes the following:
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
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 on how to upgrade 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 Candle® OMEGAMON® 350 or 360.
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 Configuring IBM Tivoli Enterprise™ Monitoring Server on z/OS®, SC32-9463
Describes how to configure and customize the Tivoli Enterprise Monitoring
Server running on z/OS.
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

© Copyright IBM Corp. 2005 xi

 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.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

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

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

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

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Some products also include publications on a documentation CD. The
format of the publications is PDF, HTML, or both. Access the Tivoli software
information center by first going to the Tivoli software library at the following Web
address:

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

Click the Tivoli 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 that allows Adobe Reader to 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 tech notes for your product.
You can view this information at the following Web site:

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

xii IBM Tivoli Monitoring: Installation and Setup Guide

 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.

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
Appendix H, “Support information,” on page 249 describes the following options
for obtaining support for IBM products:
v “Searching knowledge bases” on page 249
v “Obtaining fixes” on page 249
v “Contacting IBM Software Support” on page 250

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:)

About this guide xiii

 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

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

xiv IBM Tivoli Monitoring: Installation and Setup Guide

Chapter 1. Overview of IBM Tivoli Monitoring
IBM Tivoli Monitoring monitors and manages system and network applications on
a variety of platforms and keeps track of the availability and performance of all
parts of your enterprise. IBM Tivoli Monitoring provides reports you can use to
track trends and troubleshoot problems.

You can use IBM Tivoli Monitoring to perform the following tasks:
v Visualize real-time monitoring data from your environment
v Monitor resources in your environment for certain conditions, such as high CPU
or an unavailable application
v Establish performance thresholds and raise alerts when thresholds are exceeded
or values are matched
v Trace the causes leading up to an alert
v Create and send commands to systems in your managed enterprise by means of
the Take Action feature
v Use integrating reporting to create comprehensive reports about system
conditions
v Monitor conditions of particular interest by defining custom queries using the
attributes from an installed agent or from an ODBC-compliant data source

What’s new in this release

The following features have been added to IBM Tivoli Monitoring:
v Easy to use, highly customizable Tivoli Enterprise Portal: The Tivoli Enterprise
Portal displays information through the use of workspaces in the form of charts
and tables. You can start monitoring activity and system status immediately with
the predefined workspaces. With just a few clicks of the mouse, you can tailor
workspaces to look at specific conditions, display critical threshold values in red,
and filter incoming data so you see only what matters. You can also change the
hierarchical order in which agents are displayed, enabling you to customize the
hierarchy as is appropriate for your business. See the IBM Tivoli Monitoring
User's Guide for information.
v Integration of multiple monitoring sources in one view: Using the Tivoli
Enterprise Portal, you can view monitoring data for your z/OS resources and
the applications monitored by the IBM Tivoli Composite Application Manager
for Response Time Tracking and IBM Tivoli Composite Application Manager for
WebSphere® products, in addition to the data collected by the IBM Tivoli
Monitoring agents.
v Support for a Linux Tivoli Enterprise Portal Server and Tivoli Enterprise
Portal desktop client: Both Linux for Intel® and 31-bit Linux for z/OS are now
supported operating systems for the Tivoli Enterprise Portal Server; and Linux
for Intel is supported for the desktop client. This Linux support is a change from
OMEGAMON V350.
v Easy to use Tivoli Data Warehouse with granular historical data rollup: The
new Tivoli Data Warehouse enables you to enable and disable history collection
for different components and attribute groups, define the periodic time period to
save data, define how you want to summarize your historical data, and define
how and when you want to prune your historical and detailed data, all through

© Copyright IBM Corp. 2005 1

 the Tivoli Enterprise Portal. For information about the Tivoli Data Warehouse,
see Chapter 11, “Configuring the Warehouse Proxy for the Tivoli Data
Warehouse,” on page 145.
v Integrated Warehouse reporting: You can view historical data, using the same
workspaces as real-time monitoring, through the Tivoli Enterprise Portal, instead
of needing to generate a report through a database reporting program, such as
Crystal Reports.
v Support for IBM DB2®, Oracle, and Microsoft® SQL warehouse databases:
Support for additional databases removes the inconvenience of needing one
brand of database for your monitoring environment and a different brand for
other applications.
v IBM Tivoli Enterprise Console® integration: You can view IBM Tivoli
Enterprise Console events through the Tivoli Enterprise Portal using the Tivoli
Enterprise Console event console. You can also configure your monitoring server
to forward events from IBM Tivoli Monitoring situations to the Tivoli Enterprise
Console event server (referred to as the event server) and install the Tivoli
Enterprise Console event synchronization component on the event server to send
situation event updates back to the monitoring server. In this way, updates made
to the situation events based on Tivoli Enterprise Console rules and operator
actions on the event server are reflected in both the Situation Event Console and
the Tivoli Enterprise Console event view. See Chapter 6, “Installing the IBM
Tivoli Enterprise Console event synchronization,” on page 85 for information
about installing the event synchronization component.
Managing situation events on the event server enables you to take advantage of
the event management and automation that the Tivoli Enterprise Console
product provides. For more information about the integration with Tivoli
Enterprise Console, see “Tivoli Enterprise Console event synchronization
component” on page 6.
The Tivoli Enterprise Portal also contains a Situation Event Console that displays
IBM Tivoli Monitoring events triggered by the situations you are monitoring. If
you do not need the enterprise event management capabilities provided by
Tivoli Enterprise Console, you can use this integrated event viewer to manage
your events.
v Failover support for the Tivoli Enterprise Monitoring Server: The Hot Standby
feature enables you to maintain failover support for your hub monitoring server
by defining a standby monitoring server to act as backup. See “Configuring
failover support” on page 110 for more information.
v Lightweight agents: Because the required infrastructure for IBM Tivoli
Monitoring agents is itself small, IBM Tivoli Monitoring agents use considerably
less CPU and memory than previous IBM Tivoli Monitoring component
products.
v Agentless monitoring with the Universal Agent: The Universal Agent is a
generic agent of IBM Tivoli Monitoring that you can configure to monitor any
data you collect. You can view that data in real-time and historical workspaces
on the Tivoli Enterprise Portal and manage the data with situations and
automation policies, the same as data from other Tivoli Enterprise Monitoring
Agents.
v Administration through the command line: A new set of commands (tacmd
option) has been added so that you can administer your environment from the
command line (both Windows and UNIX). See Appendix E, “Command
reference,” on page 187 for more information about these commands.
v SOAP and SQL interfaces to data: You can create SOAP and SQL scripts to
perform actions on the data in your environment.

2 IBM Tivoli Monitoring: Installation and Setup Guide

 v Remote agent deployment: You can now deploy monitoring agents across your
environment from a central location. You can also deploy maintenance to agents,
perform agent configuration, and start and stop agents. See Chapter 10,
“Deploying monitoring across your environment,” on page 135 for details about
deploying agents.
v Increased security: IBM Tivoli Monitoring enables Secure Socket Layer (SSL) for
communication between components. For information about using SSL, see
“Using SSL between the portal server and the client” on page 119..

Moving to IBM Tivoli Monitoring

You have the following choices when moving to IBM Tivoli Monitoring:

Upgrading from Tivoli Distributed Monitoring: The new IBM Tivoli Monitoring
is not dependant on the Tivoli Management Framework. An upgrade toolkit is
provided to facilitate your move from a Tivoli Distributed Monitoring environment
to the new IBM Tivoli Monitoring.

For information, see IBM Tivoli Monitoring: Upgrading from Tivoli Distributed
Monitoring.

Upgrading from OMEGAMON V350 and V360: Migration tools are provided to
facilitate the upgrade process to IBM Tivoli Monitoring. You can upgrade custom
situations, policies, and queries, and the historical data in your data warehouse.

Many of the existing OMEGAMON V350 and V360 agents have equivalent IBM
Tivoli Monitoring agents. For any that do not yet have an IBM Tivoli Monitoring
counterpart, you can continue to monitor those agents in your new IBM Tivoli
Monitoring environment.

See Chapter 4, “Upgrading from a previous installation,” on page 39 for

information about upgrading your OMEGAMON environment.

IBM Tivoli Monitoring 5.x interoperability: Using the IBM Tivoli Monitoring 5.x
Endpoint agent, you can view data from IBM Tivoli Monitoring 5.x resource
models in the Tivoli Enterprise Portal and warehouse granular data in the Tivoli
Data Warehouse. You can use this visualization to replace the Web Health Console
used in IBM Tivoli Monitoring V5.1. For information about using this visualization,
see the IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint Agent User’s Guide.

Components of IBM Tivoli Monitoring

IBM Tivoli Monitoring consists of the following components:
v A Tivoli Enterprise Monitoring Server (referred to as the monitoring server),
which acts as a collection and control point for alerts received from the agents,
and collects their performance and availability data. There are two types of
monitoring servers: hub and remote.
v A Tivoli Enterprise Portal Server (referred to as the portal server), placed between
the client and the monitoring server, that enables retrieval, manipulation, and
analysis of data from the agents.
The portal server uses a DB2 or Microsoft SQL database to store data.
v A Tivoli Enterprise Portal client, with a Java-based user interface for viewing
and monitoring your enterprise. Tivoli Enterprise Portal offers two modes of
operation: desktop and browser.

Chapter 1. Overview of IBM Tivoli Monitoring 3

 v Agents installed on the systems or subsystems you want to monitor. These
agents collect and distribute data to a monitoring server. In addition to the new
IBM Tivoli Monitoring monitoring agents, you can monitor OMEGAMON V350
or V360 agents through your IBM Tivoli Monitoring monitoring server.
v Tivoli Data Warehouse for storing historical data collected from agents in your
environment. The data warehouse is located on a DB2, Oracle, or Microsoft SQL
database. To collect information to store in this database, you must install the
Warehouse Proxy agent. To perform aggregation and pruning functions on the
data, install the Warehouse Summarization and Pruning agent.
v Tivoli Enterprise Console event synchronization component for synchronizing
the status of situation events that are forwarded to the event server. When the
status of an event is updated because of Tivoli Enterprise Console rules or
operator actions, the update is sent to the monitoring server, and the updated
status is reflected in both the Situation Event Console and the Tivoli Enterprise
Console event viewer. For more information, see “Tivoli Enterprise Console
event synchronization component” on page 6.
Adding the Tivoli Enterprise Console product, which is designed specifically for
enterprise computing environments, to your IBM Tivoli Monitoring environment
adds powerful event management capabilities to IBM Tivoli Monitoring. Adding
IBM Tivoli Business Systems Manager to your environment enables you to
graphically monitor and control interconnected business components.

Figure 1 shows the configuration of an IBM Tivoli Monitoring environment.

Figure 1. IBM Tivoli Monitoring environment

Tivoli Enterprise Monitoring Server

The Tivoli Enterprise Monitoring Server can run as a standalone server, or as a
remote server in a hierarchy of servers that report to a master server called the hub
monitoring server. The monitoring server runs on z/OS, Linux, UNIX, and Windows
operating systems.

4 IBM Tivoli Monitoring: Installation and Setup Guide

 Hub monitoring server
The hub monitoring server serves as the focal point for managing your
environment. The hub monitoring server receives data from the following
components:
v Agents running on the same or remote systems
v Other monitoring servers running as remote servers in a hierarchical
configuration
Depending on the complexity of your environment, the number of agents you
install, and the amount of data you want to collect, a single monitoring server
might be all that you need. Or, you might want to configure a hierarchical set of
monitoring servers where remote monitoring servers report to a hub monitoring
server to distribute the activity.

Remote monitoring servers

If you need to collect large amounts of distributed data, you can minimize network
traffic by using remote monitoring servers, which collect data from the agent and
forward it to the hub monitoring server. Each remote monitoring server must
reside on its own computer and have a unique monitoring server name (node), but
the architectures of various remote monitoring servers might differ from each other
and from the hub monitoring server. In other words, a remote monitoring server
running on UNIX can report to a hub monitoring server running on Windows.

Tivoli Enterprise Portal

Tivoli Enterprise Portal is the interface into your IBM Tivoli Monitoring products.
In the same way you use your browser home page as a starting point for
navigating the Internet, you use Tivoli Enterprise Portal to get a high-level
overview of your monitoring environment. One section of the window displays the
Navigator, a tree-like view of your monitored network, with alert icons that are
displayed when problems arise. The rest of the window is filled with views
pertinent to the chosen item in the Navigator tree. From the top level or from your
home workspace, you can navigate to specific locations to check activity and
investigate problems.

You can also view events on the Tivoli Enterprise Console through your Tivoli
Enterprise Portal.

There are two components to the Tivoli Enterprise Portal:

v The Tivoli Enterprise Portal Server communicates directly with your hub
monitoring server. Install at least one Tivoli Enterprise Portal Server in your
network to deploy Tivoli Enterprise Portal.
v The portal client, which provides access to the Tivoli Enterprise Portal. There are
two kinds of portal client:
– Browser client interface (automatically installed with Tivoli Enterprise Portal
Server): In your Internet browser, to start Tivoli Enterprise Portal browser
client, you can enter the URL for a specific Tivoli Enterprise Portal browser
client installed on your Web server. Running the browser client is supported
only on Windows computers.
– Desktop client interface: A Java-based graphical user interface on a Windows
or Linux workstation. After the desktop client is installed and configured, you
can use it to start Tivoli Enterprise Portal in desktop mode.

Chapter 1. Overview of IBM Tivoli Monitoring 5

 Tivoli Enterprise Monitoring agents
Monitoring agents are data collectors. Agents monitor systems, subsystems, or
applications, collect data, and pass the data to Tivoli Enterprise Portal through the
monitoring server. The agents pass commands from the user to the system,
subsystem, or application. An agent interacts with a single system or application
and, in most cases, resides on the same computer where the system or application
is running.

There are two types of monitoring agents:

v Operating system (OS) agents that monitor the availability and performance of
the computers in your monitoring environment. An example of an OS agent is
the Monitoring Agent for Windows OS, which monitors Windows XP, Windows
2000, and Windows 2003 operating systems.
v Other agents (referred to as application agents or non-OS agents) that monitor the
availability and performance of systems, subsystems, and applications. An
example of a non-OS agent is IBM Tivoli Monitoring for Microsoft Exchange,
which monitors the Microsoft Exchange Server.

IBM Tivoli Monitoring also provides a customizable agent called the Universal
Agent. You can use the Universal Agent to monitor any data that you collect in
your environment. For example, you can use the Universal Agent to monitor the
status of your company Web site to ensure that it is available. For more
information about the Universal Agent, see the IBM Tivoli Monitoring Universal
Agent User's Guide.

Agents run on z/OS, UNIX, Windows XP Professional Edition, Windows 2000,

Windows 2003 Server, HP-UX, and i5/OS™; however, not all agents are supported
on all platforms.

Tivoli Data Warehouse

With Tivoli Data Warehouse, you can analyze historical trends from monitoring
agents. The Tivoli Data Warehouse uses a DB2, Oracle, or Microsoft SQL Server
database to store historical data collected across your environment. You can
generate warehouse reports for short term or long term data through the Tivoli
Enterprise Portal. Warehouse reports provide information about the availability
and performance of your monitoring environment over a period of time. You can
also use third-party warehouse reporting software, such as Crystal Reports or Brio,
to generate reports.

The Tivoli Data Warehouse uses the Warehouse Proxy agent to move data from the
Tivoli Enterprise Portal Server to the data warehouse database. For information
about configuring the Warehouse Proxy, see Chapter 11, “Configuring the
Warehouse Proxy for the Tivoli Data Warehouse,” on page 145.

The Warehouse Summarization and Pruning agent provides the ability to

customize the length of time for which to save data (pruning) and how often to
aggregate granular data (summarization). For information about the Warehouse
Summarization and Pruning agent, see the IBM Tivoli Monitoring Administrator's
Guide.

Tivoli Enterprise Console event synchronization component

The Tivoli Enterprise Console event synchronization component sends updates to
situation events that are forwarded to the event server back to the monitoring
server. Figure 2 on page 7 shows the flow of situation events from the monitoring

6 IBM Tivoli Monitoring: Installation and Setup Guide

server to the event server as Tivoli Enterprise Console events and the flow of
updates to the situation events back to the monitoring server. The Situation Event
Console and the Tivoli Enterprise Console event viewer are synchronized with the
updated status of the events.

Note: Event forwarding is not supported from z/OS monitoring servers.

Figure 2. Event synchronization overview

For information about the various configurations of monitoring servers and event
servers that you can have in your environment, see “Planning the deployment of
your IBM Tivoli Enterprise Console integration” on page 86.

Figure 3 on page 8 compares event management through IBM Tivoli Monitoring

with the Situation Event Console (on the left) to event management through IBM
Tivoli Monitoring with Tivoli Enterprise Console (on the right).

Chapter 1. Overview of IBM Tivoli Monitoring 7

 Figure 3. Comparison of event management options

The Tivoli Enterprise Console product significantly reduces the number of events
displayed, enabling you to focus on the most critical, relevant events and manage
even the largest, most complex environments. The Tivoli Enterprise Console
product gives you the extensive control and flexibility that you need to manage
and maintain availability across your enterprise. Managing situation events with
the Tivoli Enterprise Console product gives you the following advantages:
v Aggregation of event information from a variety of different sources including
those from other Tivoli software applications, Tivoli partner applications, custom
applications, network management platforms, and relational database systems
v Pre-configured rules that automatically provide best-practices event management
v Persistence and processing of a high volume of events in an IT environment by:
– Prioritizing events by their level of importance
– Filtering redundant or low priority events
– Correlating events with other events from different sources
– Root cause analysis and resolution
– Initiating automatic corrective actions, when appropriate, such as escalation
v Unified system and network management by automatically performing the
following event management tasks:
– Correlating the status of a system or application to the status of the network
that it uses
– Determining if the root cause of a system or application problem is an
underlying network failure

8 IBM Tivoli Monitoring: Installation and Setup Guide

Chapter 2. Planning a deployment of IBM Tivoli Monitoring
This chapter provides information about planning your deployment of IBM Tivoli
Monitoring. The following topics are discussed:
Table 1. Planning a deployment of IBM Tivoli Monitoring
Goal Where to find information
Understand the steps required to design “Overview of the design process”
your environment.
Understand the needs of your existing “Assessing the existing environment” on
environment so that you can identify the page 10
components of IBM Tivoli Monitoring that
you need.
Design your environment based on planning “Planning your design” on page 12
guidelines, the components you need, and
security considerations.
Review sample environment configurations. “Sample deployment scenarios” on page 14

Overview of the design process

To create a monitoring design, you must know how the existing environment is
organized, as well as the current status of platforms, networks, applications,
procedures, and processes. With this information, you must determine what kind
of monitoring is needed, and what resources can be made available to IBM Tivoli
Monitoring software to provide the solution.

The tasks to create a design are as follows:

Table 2. Overview of the design process
Goal Additional information (if applicable)
Perform an assessment of the existing “Assessing the existing environment” on
environment, including what needs to be page 10
monitored.
Determine the number of hub monitoring “Determining the number of monitoring
servers required. servers needed” on page 12
If multiple hub monitoring servers are
required, divide the monitored environment
into individual regions.
Determine the number of remote monitoring “Determining the number of monitoring
servers and their placement in the network. servers needed” on page 12
Decide on the placement of the central “Determining server placement” on page 12
servers (hub monitoring servers, portal
servers, Tivoli Data Warehouse).
Decide on the number and placement of Chapter 11, “Configuring the Warehouse
Warehouse Proxy and Summarization and Proxy for the Tivoli Data Warehouse,” on
Pruning agents. page 145
Determine how to configure the Tivoli Data “Planning considerations for the Tivoli Data
Warehouse server. Warehouse” on page 30

© Copyright IBM Corp. 2005 9

 Table 2. Overview of the design process (continued)
Goal Additional information (if applicable)
Determine how to deploy the monitoring “Determining when to use the remote
agents. deployment feature” on page 14

Chapter 10, “Deploying monitoring across

your environment,” on page 135
Determine if the Tivoli Enterprise Console is “Determining when to use the IBM Tivoli
needed for correlation of events Enterprise Console” on page 13
Review the explanation of IBM Tivoli Appendix C, “Firewalls,” on page 181
Monitoring's implementation of firewalls.

Assessing the existing environment

Before selecting and installing the IBM Tivoli Monitoring components, fully review
and document the environment you plan to monitor. You can create an optimal
design only after carefully considering the organizational needs and limitations (for
example hardware availability) and understanding the technical capabilities of the
IBM Tivoli Monitoring software.

Understanding the following conditions accelerates your design efforts and ensures
that the solution performs as expected:
v A thorough and accurate picture of your networking environment.
v The business goals for system monitoring in your environment and how Tivoli
applications can achieve those goals.

The number of factors that need to be considered and their influence on the
architecture varies for each organization. Viewing these factors from both a
physical and organizational perspective offers a way to arrange factors into
manageable groups.

The physical perspective is the network physical topology, such as available

equipment and configuration of systems, in which IBM Tivoli Monitoring must
operate. The existing environment influences how and where you deploy systems.
In many ways, the physical environment forms baseline constraints for the entire
design. The relation between physical factors and IBM Tivoli Monitoring
deployment is particularly close.

The organizational perspective includes expectations and limitations derived from

the way you do business, and the division of authority and control of the systems
to be managed. Organizational factors can influence the goals and means to deploy
a monitoring solution.

The factors below, ordered by priority, are not a comprehensive list. Additional
factors might be important in your environment.

Physical Perspective
The following sections provide information about the physical perspective for a
monitoring environment.

10 IBM Tivoli Monitoring: Installation and Setup Guide

 Network factors
Prepare a network diagram or sketch of the network topology, if one is not already
available for your organization. This network design information is necessary for
the design process and should at a minimum provide details about the following
critical and important considerations:
v Line speed of each network connection. The line speed impacts the number of
hub monitoring servers and the placement of remote monitoring servers and the
Tivoli Data Warehouse.
v Firewalls and Network Address Translation (NAT) divisions in the network
v Bandwidth restrictions. Determine if there are bandwidth restrictions that must
be honored to share limited bandwidth with other applications. Also, determine
if the available network bandwidth varies by time of day.
v Number of resources to be monitored at remote locations
v Network reliability
v Host and IP address naming conventions and schemes used to identify
networking and computer equipment

Managed systems factors

Prepare a list of computers and applications to be monitored by IBM Tivoli
Monitoring. Include details about the following considerations:
v Hardware configuration of the computers to be monitored. Include the vendor,
memory available, CPU speed, and disk space available.
v Software configuration of the computers to be monitored. Include the operating
systems, patch levels, and network configuration.
v The applications on each computer that need to be monitored. Include version
levels and patch levels.
v The number of each type of computer (operating system) and application.
v The maximum failure detection interval needed for each computer and
application (for configuring heartbeat intervals).
v The computers and applications that are mission critical.
v A contingency plan for your mission critical applications.

Organizational perspective
Prepare a list of organizational factors that might have an impact on the
deployment. Include details about the following considerations:
v Organizational objective, business processes, IT processes, business needs, and
future plans. This aspect has a great impact in the design process and needs to
be looked at carefully from a physical perspective.
v Amount of growth anticipated for the environment. The growth could be in
terms of an increase in the number of monitored systems within existing
infrastructure or due to setting up of new offices.
v Internationalization considerations.
v Primary risks to this project.
v Number and responsibilities of existing system administrators.
v Major impediments to the IT service your organization offers.
v Immediate problems you are trying to solve with the deployment of IBM Tivoli
Monitoring.
v Your immediate and long-term goals.

Chapter 2. Planning a deployment of IBM Tivoli Monitoring 11

Planning your design
There are several different installation and configuration scenarios for IBM Tivoli
Monitoring. In a typical customer deployment, IBM Tivoli Monitoring can be
scaled to support up to 5000 agents per hub monitoring server. Several hub
monitoring servers can be deployed to expand monitoring capability to meet the
needs of your environment.

However, as the size of your environment grows, so does the load of data to be
processed, which can negatively impact performance. The following sections
provide information to help you plan your environment, based on the number of
agents and monitoring servers in your environment and the types of monitoring
that you want to do.

Determining the number of monitoring servers needed

Identifying the types and number of monitoring servers that you need in your
environment depends on a number of factors, such as the number of agents to
support, the types of agents to support, the network bandwidth, and the
geography of your environment.

A basic guideline for determining when to add remote monitoring servers to your
environment is the number of agents that you want to support. Each remote
monitoring server can support up to 500 agents (depending on the type of agent
and the data load). So, if you have 1000 agents in your environment, deploy one
hub monitoring server and two remote monitoring servers, each with 500 agents
reporting to them.

Note: Remember that a single managed system can include several agents such as
an Operating System agent (Windows, UNIX, or Linux) and an application
agent like the DB2 agent. For this reason, be sure to count the actual agents
to be supported and not managed systems.

For environments with more than 5000 agents, use multiple remote hub monitoring
servers. Using the basic guideline of 5000 agents per hub monitoring server and
500 agents per remote monitoring server, an environment with 25 000 agents might
use 5 hub monitoring servers each with 10 remote monitoring servers.

In addition to the number of agents, you need to also consider the type of agents
that you are supporting and what you choose to monitor with those agents. While
each monitoring server can support 500 agents, this number decreases if the agents
that you are supporting are more complex (a non-OS agent generates more data
than an OS agent), if you are collecting historical data for most attribute groups, or
if you are using complex situations. If this is the case in your planned deployment,
consider using fewer than 500 agents per monitoring server (and fewer than 5000
per hub) to ensure fast response time.

You might also choose to deploy remote monitoring servers for each type of agent
that you are supporting. For example, if you are monitoring a number of DB2
instances across your environment, you can have all of those agents communicate
with a single remote monitoring server.

Determining server placement

Consider the following when determining the needs of your monitoring
environment:

12 IBM Tivoli Monitoring: Installation and Setup Guide

 v Decide where (within the existing network topology, or geographically) you
want to accumulate data generated by the agents. This is where you will install
a monitoring server.
v Determine the amount of data you expect to collect. Depending on the
complexity of your environment, the number of agents you install and the
amount of data you choose to collect, you might need multiple monitoring
servers.

Note: Only a hub monitoring server can have a Tivoli Enterprise Portal Server
attached to it.
v Determine where you want to run the user interface to look at data and interact
with the system. This is where you install the portal server and portal client.
v Determine your need for continuous operation in your environment. If you need
continuous operation, consider using the Hot Standby feature to ensure the
availability of your monitoring servers.

A final factor to consider in determining the deployment of monitoring servers is

geography. You can divide your agents between monitoring servers based on their
geographical location. For example, if you have agents in two locations separated
by a wide area network (WAN), the agents closest physically to the monitoring
server have the best performance. The speed of the network connection between
components affects the performance of your environment. A slower connection
increases the client response time. To increase performance across the environment,
you can set up two remote monitoring servers on either side of the WAN
connection to service the agents close to them.

Security considerations
Firewalls and NAT translation require additional configuration steps (see
Chapter 3, “Planning the installation of your environment,” on page 21). If an
agent is across a firewall from its monitoring server or from the Warehouse Proxy
agent, then extra configuration is needed so that they know how to address each
other. This configuration could be a lot of work; for example, if you have 500
agents across a firewall, you might consider giving them their own monitoring
server to avoid this.

For additional information about IBM Tivoli Monitoring's implementation of

firewalls, see Appendix C, “Firewalls,” on page 181.

Determining when to use the IBM Tivoli Enterprise Console

IBM Tivoli Enterprise Console is a key element of a monitoring environment.
Because of its capabilities, Tivoli Enterprise Console is commonly used in a
Manager of Managers role, providing an enterprise level solution for aggregation,
consolidation, correlation, and management of events across the enterprise. It is
also used as an integration point with which other management applications
interact. Tivoli Enterprise Console provides the following capabilities:
v Aggregation of event information from a large number and variety of different
sources including those from other Tivoli software applications, Tivoli partner
applications, custom applications, network management platforms, and
relational database systems
v Pre-configured rules that automatically provide best-practices event management
and root cause determination from an end to end perspective
v Persistence, processing, and access to a high volume of events in an IT
environment

Chapter 2. Planning a deployment of IBM Tivoli Monitoring 13

 v Unified system and network management by automatically performing the
following event management tasks:
– Correlating the status of a system or application to the status of the network
that it uses
– Determining if the root cause of a system or application problem is an
underlying network failure

If you are monitoring less than 200 managed systems (and less than 1000 events)
and you want to view only situation events (not the other types of events that IBM
Tivoli Enterprise Console can monitor), you can use the Situation Event Console in
the Tivoli Enterprise Portal. If your monitoring environment is larger than 200
managed systems, consider moving to IBM Tivoli Enterprise Console for your
event aggregation and use the Tivoli Enterprise Console view within the Tivoli
Enterprise Portal to display the event information. The response time for the Tivoli
Enterprise Console view is better than the Situation Event Console view when a
large number of events is displayed.

For additional information about the integration with Tivoli Enterprise Console, see
“Tivoli Enterprise Console event synchronization component” on page 6.

For additional information about Tivoli Enterprise Console, see the Tivoli
Enterprise Console information center. For additional information about using the
Situation Event Console in the Tivoli Enterprise Portal, see the IBM Tivoli
Monitoring User's Guide.

Determining when to use the remote deployment feature

IBM Tivoli Monitoring adds the ability to deploy resource monitoring across your
environment from a central location, the monitoring server. You can use the remote
deployment feature of IBM Tivoli Monitoring to deploy and configure monitoring
agents, to deploy maintenance and upgrades to agents, and to start and stop
agents.

The remote deployment feature in IBM Tivoli Monitoring can be used in all
monitoring environments; however, the number of agents you want to deploy and
the deployment capabilities that you require affect whether the remote deployment
feature is the best choice for your environment. Consider using an enterprise
deployment tool, such as IBM Tivoli Configuration Manager, if you need any of
the following capabilities:
v Efficiently deploying a large number of agents in parallel, using caches that are
geographically close to the distribution points
v Limiting the amount of bandwidth used for deployment actions through the use
of network bandwidth throttling
v Restarting a failed deployment automatically

Sample deployment scenarios

This section presents small, medium, and large deployment examples. In the
interest of readability and understanding, these examples are simplified schematics
rather than actual real-world solutions. They serve as a convenient starting point
for deployment planning.

Small monitoring environment

You can deploy a small IBM Tivoli Monitoring environment on a single computer.
This type of environment might be useful for a teaching environment, for

14 IBM Tivoli Monitoring: Installation and Setup Guide

 advanced prototyping and testing of solutions, or for monitoring a small, but
critical, server environment. A single server environment with failover support
might be built and dedicated to monitoring heartbeats from the mail servers within
a medium size company.

Figure 4 shows a small monitoring environment.

Small monitoring environment

Tivoli Enterprise
Portal Client

Failover

Hub monitoring server Backup:

Portal server Hub monitoring server
Warehouse Proxy Portal server
Tivoli Data Warehouse Warehouse Proxy
Tivoli Data Warehouse

100-200
monitoring agents

Figure 4. Small IBM Tivoli Monitoring environment

The small environment would be limited to 100-200 agents. It can perform some
minimal historical data collection and does not use the IBM Tivoli Enterprise
Console. Adding significant data collection or enterprise-wide event correlation
requires additional servers.

The advantages of a small environment are that it is simple, the most reliable
(there is only 1 possible point of failure), and the least expensive.

The disadvantages of a small environment are that you can only support a small
number of agents and adding historical data collection or a significant number of
situation events could overwhelm capacity.

If you are going to use a small monitoring environment, choose a multiprocessor (2

or 4-way) for the monitoring server with at least 2 GB of memory. Configure the
software and begin monitoring. Observe the percentage of CPU used in routine
monitoring and during periods of processing a high number of situation events. If
the CPU utilization is greater than 80%, consider migrating the portal server to a

Chapter 2. Planning a deployment of IBM Tivoli Monitoring 15

 separate computer. If historical data collection is too demanding, you can deploy
another server to handle the Tivoli Data Warehouse and the Warehouse Proxy.
Keep the Tivoli Data Warehouse, Warehouse Proxy, and Summarization and
Pruning agent on the same computer for better performance.

Medium monitoring environment

You can build a medium monitoring environment with five to ten machines. This
level of deployment might be used in a medium-sized company, or it can be used
within a large company to monitor individual server-groups independently
according to organizational boundaries. For example, one environment might
monitor the mail servers, while another environment would monitor HTTP servers,
and a third might monitor transaction servers. The departments responsible for
each set of servers could maintain control over the monitoring and historical data.

Figure 5 shows a medium monitoring environment.

Figure 5. Medium IBM Tivoli Monitoring environment

The medium monitoring environment supports up to 5000 agents using a single

hub monitoring server and remote monitoring servers. Tivoli Enterprise Console is
used to correlate events, and a Tivoli Data Warehouse server collects and saves
historical data for debugging and reports.

16 IBM Tivoli Monitoring: Installation and Setup Guide

 The advantages of the medium monitoring environment include that significant
historical data collection and event correlation is possible across a large number of
agents, complex database queries do not interfere with the performance of
real-time monitoring tasks, and complex correlation is possible using Tivoli
Enterprise Console.

The disadvantage of the medium monitoring environment is that, if multiple

independent hub environments are deployed, enterprise-wide historical database
and event correlation is not available. The multi-hub deployment described in
“Large monitoring environment” resolves this disadvantage.

If you are going to use a medium monitoring environment, use the recommended
system configurations (see “Required hardware” on page 26) for the multiple
monitoring servers and the portal server. Scale the Tivoli Data Warehouse server
according to how much historical data you plan to collect and retain (see
“Planning considerations for the Tivoli Data Warehouse” on page 30 for
information). A simple one-server Tivoli Enterprise Console deployment can
handle the event correlation. Keep the Tivoli Data Warehouse, Warehouse Proxy,
and Summarization and Pruning agent on the same computer for better
performance.

Large monitoring environment

You can build a large monitoring environment to handle enterprise-wide historical
data collection and event correlation. Figure 6 on page 18 shows a large monitoring
environment.

Chapter 2. Planning a deployment of IBM Tivoli Monitoring 17

Figure 6. Large deployment of IBM Tivoli Monitoring

The large environment supports up to 5000 agents with each hub monitoring
server; multiple hubs can be deployed to extend across the whole enterprise. Tivoli
Enterprise Console is used to correlate events across all hub monitoring servers. A
single Tivoli Data Warehouse server collects and saves historical data for
debugging and reports.

The advantage of a large monitoring environment is that historical data and event
correlation is enterprise-wide. You can use complex database queries to access all
data.

The disadvantage of a large monitoring environment is that it is more difficult to

debug. The possibility of failure increases as the number of servers grows. Failure
recovery is also more complex.

If you are going to use a large monitoring environment, use the recommended
system configurations (see “Required hardware” on page 26) for the multiple
monitoring servers and portal servers. Scale the Tivoli Data Warehouse server
according to how much historical data you plan to collect and retain (see
“Planning considerations for the Tivoli Data Warehouse” on page 30 for
information). You might need to use a hub and spoke Tivoli Enterprise Console
deployment (described in “Multiple hub monitoring servers and multiple event
servers in a hub and spoke configuration” on page 87) to handle the additional
load of synchronizing events across hub monitoring servers. If possible, keep the

18 IBM Tivoli Monitoring: Installation and Setup Guide

Tivoli Data Warehouse, Warehouse Proxy, and Summarization and Pruning agent
on the same computer for better performance; if they are deployed separately, use
the fastest possible network connection between them.

Chapter 2. Planning a deployment of IBM Tivoli Monitoring 19

20 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 3. Planning the installation of your environment
The following sections provide information for planning the details for installing
your IBM Tivoli Monitoring environment.

Overview of the installation process

The following table provides an overview of the steps required to fully install and
deploy an IBM Tivoli Monitoring environment.
Table 3. Installation and configuration steps
Step Where to find detailed information
Assess your monitoring needs to determine “Assessing the existing environment” on
the best deployment of IBM Tivoli page 10
Monitoring components.
Ensure you have the required hardware and “Hardware and software requirements” on
software. page 24
Gather any information required for “Specific information to have ready”
successful installation (such as DB2 user
information and security specifications). Appendix A, “Installation worksheets,” on
page 163
Install the Tivoli Enterprise Monitoring “Installing and configuring the hub Tivoli
Server. Enterprise Monitoring Server” on page 48
Install the Tivoli Enterprise Portal Server. “Installing the Tivoli Enterprise Portal
Server” on page 59
Install the management agent software. “Installing monitoring agents” on page 64
Install support for IBM Tivoli Enterprise Chapter 6, “Installing the IBM Tivoli
Console. Enterprise Console event synchronization,”
on page 85
Install the portal desktop client on any “Installing Tivoli Enterprise Portal desktop
system where you want to use it. client” on page 70
Start the portal client to verify that you can “Starting the Tivoli Enterprise Portal client”
view the monitoring data. on page 82

If you are upgrading from OMEGAMON Platform 350 or 360 and CandleNet
Portal® 195, see Chapter 4, “Upgrading from a previous installation,” on page 39
before installing any IBM Tivoli Monitoring components.

If you are upgrading from Tivoli Distributed Monitoring to IBM Tivoli Monitoring,
see the IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring guide.

If you plan to use firewalls in your environment, see Appendix C, “Firewalls,” on

page 181 for an overview of the IBM Tivoli Monitoring implementation of
firewalls.

Specific information to have ready

During installation, you must supply the following information:
v Name of the monitoring server you are installing or to which the agent will
connect

© Copyright IBM Corp. 2005 21

 v Host name for the computer where you are installing the product (a monitoring
server or one instance of an agent).
v Whether the monitoring server being installed or being connected to is
configured as a hub or remote monitoring server
v Hub monitoring server host name
v Port number

Use the worksheets in Appendix A, “Installation worksheets,” on page 163 to

collect this information for each component that you want to install.

Naming your monitoring server

You must decide how the monitoring servers are to be named. In general, create
names that are short but meaningful within your environment. Use the following
guidelines:
v Each name must be unique. One name cannot match another monitoring server
name for its entire length. (For example, ″ibm″ and ″ibmremote″ are unique and
permitted.)
v Each name must begin with an alpha character. No blanks or special characters
(″$#@″) can be used.
v Each name must be between 2 and 32 characters in length.
v Monitoring server naming is case-sensitive on all platforms.

Required order of installation or upgrade of IBM Tivoli Monitoring

component products
If any of the following products will be installed on the same computer as
monitoring agents, they must be installed before the agent is installed:
v Hub Tivoli Enterprise Monitoring Server
v Remote monitoring server (if necessary)
v Tivoli Enterprise Management Agent Framework
v Tivoli Enterprise Portal Server
v Tivoli Enterprise Portal desktop client
In addition, these products must be installed on at least one computer before the
agent can be properly configured.

Windows installation consideration - user authority

To install IBM Tivoli Monitoring on a Windows computer, you must have
Administrator privileges on that computer. You must also run the IBM Tivoli
Monitoring components as a user with Administrator privileges.

Linux or UNIX Installation considerations

The following sections provide information about issues unique to Linux and
UNIX installations.

Create an IBM Tivoli account for installing and maintaining the

installation directory
Create an IBM Tivoli account for installing and maintaining the installation
directory. For best performance, follow these guidelines:

22 IBM Tivoli Monitoring: Installation and Setup Guide

 Note: This does not apply to installing the portal server on Linux. You must use
either the root user or the DB2 administrator to install and configure the
portal server. You can then use the IBM Tivoli account to run the portal
server.
v You can use any valid name.
You can install the IBM Tivoli Monitoring software as the root user, but you do
not have to. If you do not install as a root user, you must following the steps
outlined in “Changing the file permissions for agents” on page 69 after you
install any monitoring agents.
v Use the same user to install all components.
v If you are using NFS or a local file system, establish your installation directory
according to the guidelines used in your environment.
v Consider using the Korn shell for your IBM Tivoli account; however, you can
use any shell that is shipped with the UNIX operating system.

Note: IBM Tivoli products do not support third-party vendor shells such as
BASH and TCSH.

Host name for TCP/IP network services

TCP/IP network services such as NIS, DNS, and the /etc/hosts file must be
configured to return the fully qualified host name (for example:
HostName.ibm.com). Define the fully qualified host name after the dotted decimal
host address value and before the short host name in the /etc/hosts.

Use of fully qualified path names

Because of the wide variety of UNIX operating systems and possible user
environments, use fully qualified path names when entering a directory during the
installation process (do not use pattern-matching characters). IBM scripts use the
Korn shell. When a new process or shell is invoked, use of symbolic links,
environmental variables, or aliases can potentially cause unexpected results.

Multiple Network Interface Cards

When more than one Network Interface Card (NIC) exists in the computer on
which the monitoring server is installed, you need to identify which NIC to use
when specifying the monitoring server name and host name. Additionally, the host
name of the system might not match the interface name, even when only one NIC
exists. In either of these cases, to establish connectivity between the monitoring
server and agents, you must specify an additional variable when configuring the
monitoring server or agents. This variable is listed under the Optional Primary
Network Name option in the configuration windows or during the installation.

Installing into an NFS environment

IBM supports installing IBM Tivoli Monitoring in NFS environments. Using NFS,
you can concentrate your software and data in a specific location, minimizing
maintenance, administrative overhead, and disk space.

Although using NFS to support multiple hosts simplifies the maintenance of

installed IBM Tivoli products, its use can impact performance. If you are installing
into an NFS environment, consider the administrative savings to the possible
impact on the performance of your network.

Chapter 3. Planning the installation of your environment 23

 Consider the number of hosts that share a single installation directory, as well as
the effects of network congestion and file system performance on the overall
response time of your IBM Tivoli products.

NFS also has some trade-offs in how you manage your environment. While you
can have your entire IBM Tivoli Monitoring in one place, there might be additional
configuration required to define the use of specific products or processes in your
installation directory. Will every product on every host system execute using the
same configuration; or will you tailor the configuration to the particular
environment?

File descriptor (maxfiles) limit

The monitoring server requires a minimum of 256 file descriptors (maxfiles) for the
operating system. Consider increasing this number to 1000 file descriptors.

For the monitoring server to function properly, set the maximum file descriptor
(MAX_FILES parameter of the configurable kernel parameter) to greater than 256.
Under POSIX shell, running ulimit -a displays nofiles (descriptors) that should be
greater than 256 or unlimited.

To determine the number of per process file descriptors (maxfiles), run one of the
following commands:
sysdef | grep maxfiles
ulimit -a

For AIX® computers, run the following command:

ulimit -d

If the settings returned are less than 256, increase the maxfiles limit beyond 256.

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 unique to a certain agent).
For this information, see the user’s guide for the agent that you are
installing.

Supported operating systems

The following table 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 4. Supported operating systems
Warehouse
Monitoring Warehouse Summarization
Operating Monitoring agent2 Proxy and Pruning
system server Portal server Portal client1 agent
AIX V5.1
X X
(32/64 bit)
AIX V5.2
X X X
(32/64 bit)

24 IBM Tivoli Monitoring: Installation and Setup Guide

Table 4. Supported operating systems (continued)
Warehouse
Monitoring Warehouse Summarization
Operating Monitoring agent2 Proxy and Pruning
system server Portal server Portal client1 agent
AIX V5.3
X X X
(32/64 bit)
Solaris
Operating
X X
Environment
V8 (32/64 bit)
Solaris
Operating
Environment X X X
V9 and V10
(32/64 bit)
HP-UX 11i
(32/64 bit) with
X
patch
PHSS_30970
Windows 2000
X X
Professional
Windows 2000
X X X X X X
Server
Windows 2000
Advanced X X X X X X
Server
Windows XP X X X X
Windows 2003
Server SE (32
X X X X X X
bit) with
Service Pack 1*
Windows 2003
Server EE (32
X X X X X X
bit) with
Service Pack 1*
RedHat
Enterprise X X
Linux 2.1 Intel
RedHat
Enterprise and
X X X X X
Desktop Linux
4 Intel
RedHat
Enterprise and
Advanced X X
Linux 3 for
z/Series
RedHat
Enterprise
X X X
Linux 4 for
z/Series 31-bit

Chapter 3. Planning the installation of your environment 25

Table 4. Supported operating systems (continued)
Warehouse
Monitoring Warehouse Summarization
Operating Monitoring agent2 Proxy and Pruning
system server Portal server Portal client1 agent
SUSE Linux
Enterprise X X
Server 8 Intel
SUSE Linux
Enterprise
X X X
Server 8 for
z/Series 31-bit
SUSE Linux
Enterprise
X X
Server 8 for
z/Series 64-bit
SUSE Linux
Enterprise X X X X X
Server 9 Intel
SUSE Linux
Enterprise
X X X X
Server 9 for
z/Series 31-bit
SUSE Linux
Enterprise
X X
Server 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 can
only be accessed from 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 (KB893803), 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 Configuring
IBM Tivoli Enterprise Monitoring Server on z/OS, SC32-9463.

Required hardware
The following table details the minimum required hardware to install the
components of IBM Tivoli Monitoring.

26 IBM Tivoli Monitoring: Installation and Setup Guide

Table 5. Hardware requirements for IBM Tivoli Monitoring components
Component Minimum requirements Recommended 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 “Estimating 4-way 8GB for UNIX “Estimating
Warehouse for RISC, 2 the required processor 1 or Linux, 4GB the required
GHz for Intel) size of your GHz for RISC, for Windows size of your
database” on 2 GHz for Intel database” on
page 30 page 30
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

Additional requirements:
v If the portal server and a monitoring server 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
2-processor 1 GHz machine with 2 GB of memory.
v The best network connection possible is needed between the hub monitoring
server and portal server and also between the Tivoli Data Warehouse,
Warehouse Proxy agent, and Summarization and Pruning agent.
v The recommended machine requirement for the Tivoli Data Warehouse assumes
that the Warehouse Proxy agent and Warehouse Summarization and Pruning

Chapter 3. Planning the installation of your environment 27

 agent are installed on the same server, which is recommended for best
performance. Separate machine requirements listed for the Warehouse Proxy
agent and Summarization and Pruning agent are given for environments where
these agents are not installed on the same server as the Tivoli Data Warehouse.
v A video card supporting 64,000 colors and 1024 x 768 required resolution on
portal client.

Required software
The following table lists the software required for IBM Tivoli Monitoring.
Table 6. 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 V1.4.2 or higher X X X X
Environment for
Java™
For Linux pdksh-5.2.14 X X X
computers: a Korn
shell interpreter
AIX only: xlC X
Runtime
Environment
(required for Global
Security Toolkit)
Microsoft Internet V6.0 with all critical X X
Explorer Microsoft updates
applied
Database1,2: Fix Pack 10 for DB2 V8 X
v DB2 UDB version
83
OR
v Microsoft SQL
Server version
20004
OR
v Oracle 9.2 or 10.1
(for warehousing
only, not for the
Tivoli Enterprise
Portal Server)
IBM Tivoli Version 3.9 with Fix
Enterprise Console Pack 03

28 IBM Tivoli Monitoring: Installation and Setup Guide

Table 6. 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
above
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 V5.0 requires
Service Pack 3 or
fixes JR10466 and
above
JR10368.
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, in your environment, you are using products whose licenses require you to collect software use information
and report it to IBM using IBM Tivoli License Manager, you must ensure that use of this instance of the product
is not included in the report. To do this, create a Tivoli License Manager license, selecting a license type that
does not involve reporting to IBM, and associate this instance of the product with it.
4. IBM Tivoli Monitoring supports MS SQL Server 2000 only if the data is limited to codepoints 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.

Chapter 3. Planning the installation of your environment 29

Planning considerations for the Tivoli Data Warehouse
In a large or enterprise environment, you have the option of using multiple
databases for the Tivoli Data Warehouse or having all of your hub monitoring
servers use one single database. The benefit of using one database across your
environment is that the information is stored in one location, meaning that you can
more easily and accurately generate reports that reflect your entire environment (as
opposed to needing to collate reports from several different databases). However,
because the amount of data that is generated during history collection across a
large or enterprise environment can be immense, you need to carefully plan the
scale and performance of that database.

In addition to the planning information below, the IBM Tivoli Monitoring

Administrator's Guide provides database performance tuning information in an
appendix.

Estimating the required size of your database

One of the factors to consider when planning the size of database that you need is
the amount and type of information you will collect for agent history data
collection. Each of the agent user's guides provide capacity planning information to
help you calculate the amount of disk space required by data for each attribute
group. Use this information to complete the following calculations to determine
how large your data warehouse database needs to be:
v “Step 1: Determine the number of detailed records per day for the attribute
group”
v “Step 2: Determine the hard disk drive footprint for the attribute group” on
page 31
v “Step 3: Determine the amount of detailed data for the attribute group” on page
31
v “Step 4: Calculate the amount of aggregate data for the attribute group” on page
31

Use the worksheet in Table 7 on page 34 to record the values from these
calculations. You can also use the planning spreadsheet available in the IBM Tivoli
Monitoring information center.

Step 1: Determine the number of detailed records per day for the
attribute group
Determine the number of detailed records per day for each attribute group that
you want to collect data for. Use the following equation:
(60 / collection interval) * (24) * (# instances at each interval)

where:
60 Represents the 60 minutes in an hour.
collection interval
The data collection interval, in minutes. This value can be 5, 15, 30, or 60
minutes.
24 Represents 24 hours in one day.
# instances at each interval
The number of instances recorded at each interval. See the agent user's
guide for this value.

30 IBM Tivoli Monitoring: Installation and Setup Guide

Step 2: Determine the hard disk drive footprint for the attribute
group
Determine the hard disk drive footprint for each attribute group. The result
generated by this formula gives an estimate of the amount of disk space used for
this attribute group for 24 hours worth of data for a single agent.

Use the following equation:

(# detailed records) * (attribute group detailed record size) / 1024)

where:
# detailed records
The number of detailed records for the attribute. This is the value you
calculated in “Step 1: Determine the number of detailed records per day
for the attribute group” on page 30.
attribute group detailed record size
The detailed record size for the attribute group. See the agent user's guide
for this value.
1024 Represents 1 KB and causes the equation to generate a kilobyte number
instead of a byte number.

Step 3: Determine the amount of detailed data for the attribute

group
Determine the amount of detailed data in the warehouse database for each
attribute group. Use the following equation:
attribute group disk footprint * (# of agents) * (# days of detailed data) / 1024

where:
attribute group disk footprint
The disk footprint for the attribute group. This is the value you calculated
in “Step 2: Determine the hard disk drive footprint for the attribute
group.”
# of agents
The number of agents of the same agent type in your environment.
# days of detailed data
The number of days for which you want to keep detailed data in the
warehouse database.
1024 Represents 1 KB and causes the equation to generate a megabyte number.

Step 4: Calculate the amount of aggregate data for the attribute

group
Determine the amount of aggregate data in the warehouse for each attribute group.

First, calculate the number of aggregate records per agent. Use the following
equation:
(#hourly + #daily + #weekly + #monthly + #quarterly + #yearly)
* (# instances at each interval)

where:
#hourly
The number of hourly records for the attribute group. For example, if you
have hourly records for 60 days, the number of hourly records is 1440 (60
multiplied by 24 hours per day).

Chapter 3. Planning the installation of your environment 31

 #daily The number of daily records for the attribute group. For example, if you
have daily records for 12 months, the number of daily records is 365.
#weekly
The number of weekly records for the attribute group. For example, if you
have weekly records for a 2-year period, the number of weekly records is
104 (2 multiplied by 52 weeks per year).
#monthly
The number of monthly records for the attribute group. For example, if
you have monthly records for a 2-year period, the number of monthly
records is 24.
#quarterly
The number of quarterly records for the attribute group. For example, if
you have quarterly records for a 2-year period, the number of quarterly
records is 8 (2 years multiplied by 4 quarters in a year).
#yearly The number of yearly records for the attribute group. For example, if you
have yearly reports for a 10-year period, the number of yearly records is
10.
# instances at each interval
The number of instances recorded at each interval. See the agent user's
guide for this value.

Next, use the following equation to calculate the amount of attribute data in the
warehouse for the attribute group:
(# aggregate records per agent) * (attribute group aggregate record size)
* (# agents) / 1048576

where:
# aggregate records per agent
The number of aggregate records per agent for the attribute group.
attribute group aggregate record size
The size of the attribute group aggregate group. See the agent user's guide
for this value.
# agents
The number of agents of the same agent type in your environment.
1048576
Represents 1 MB and causes the equation to generate a megabyte number.

Step 5: Determine the estimated size of your database

First, determine the total space required for each attribute group. Add the amount
of detailed data and the amount of aggregate data for the attribute group. Use the
following equation:
(detailed data size) + (aggregate data size)

Second, determine the total space required for all attribute groups for the agent.
Add the total space for each attribute group that you want to collect. Use the
following equation:
aggGroup1 + aggGroup2 + aggGroup3 ...

Third, determine the total space required for all agents. Add the total space for
each agent. Use the following equation:
agent1 + agent2 + agent3 ...

32 IBM Tivoli Monitoring: Installation and Setup Guide

Finally, to estimate the total disk space requirement for the database, multiplying
the total amount of data (detailed + aggregate for all attribute groups) by 1.5 (to
increase the number by 50%). Compare this number to the Database data row in
Table 8 on page 35 to determine the number of disks you need for your database.

Use the following worksheet to estimate the size of your data warehouse database.

Chapter 3. Planning the installation of your environment 33

 Table 7. Tivoli Data Warehouse database size estimation worksheet

34
Total
Data from the User's Guide warehouse
Attribute Warehouse Warehouse space for
Record Record Detailed agent disk Days of space - space - attribute
Attribute Number size - size- Interval Collection records space detailed detailed Aggregate aggregated group
group of agents detailed aggregated instances interval per day* (KB)* data kept (MB)* records (MB)* (MB)
NT_System 1000 452 1308 1 15 96 42.38 30 1241.46 4582 5715.61 6957.07

IBM Tivoli Monitoring: Installation and Setup Guide

Total warehouse data size

(sum of all attribute group total warehouse space)

Total database size

(Total warehouse data size * 1.5)

*: Use the equations in “Estimating the required size of your database” on page 30 for these values.
Understanding the disk requirements for your database
Consider the following factors when designing a disk subsystem to support your
database processing:
v Disk crash: With sufficient funds and planning, you can build a system that can
continue running without interruption or be recovered in a few hours, despite a
system crash. You can provide disk protection by using some level of RAID on
parts, or all, of the disk subsystem. Some of the more popular types of RAID
include the following:
– RAID 1, also known as disk mirroring, uses data mirroring to achieve a high
level of redundancy. In a RAID 1 configuration, two copies of the data are
kept on separate disks, each mirroring the other.
– RAID 5 uses block-level striping with distributed parity. RAID 5 stripes both
data and parity information across three or more drives.
v The database log needs disk protection to enable database recovery of recent
transactions. The other disks can optionally be protected. If they are protected,
you can eliminate downtime while data is recovered.
v Consider the OS and paging space disks.
v Also, consider including one or two additional disks to speed up recovery and
reduce the risks while running after a disk failure.
v Because of the increasing capacity of disk drives, the configurations listed below
result in excess disk capacity but increase the number of disks available for I/O
throughput.

The following table provides some example sizes for a database:

Table 8. Database size examples
Number of disks to use
Absolute Small and safe
minimum disks Small RDBMS RDBMS Large RDBMS
Operating 1 1 1 + mirror 1
System
Paging and Use above 1 1 + mirror 1
RDBMS code
RDBMS data 1 1 1 + mirror 8
RDBMS indexes 1 1 1 + mirror 6
RDBMS temp Use above 1 1 + mirror 6
RDBMS logs 1 + mirror 1 + mirror 1 + mirror 2
Database data 12 GB 24 GB 48 GB 108+ GB
Number of disks 5 7 12 24

The Absolute minimum disks column specifies the minimum number of disks for
an RDBMS. In this column, the index and temporary space is allocated onto one
disk. While not an ideal arrangement, this might work in practice because
databases tend to use indexes for transactions or temporary space for index
creation and sorting full table scan large queries, but not both at the same time.
This is not a recommended minimum disk subsystem for a database, but it does
have the lowest cost.

The Small RDBMS column represents a minimum disk subsystem, although there
might be limits in I/O rates because of the data being place on only one disk.

Chapter 3. Planning the installation of your environment 35

 Striping the data, indexes, and temporary space across these three disks might help
reduce these I/O rate limits. This disk subsystem arrangement does not include
disk protection for the database or other disks (apart from the mandatory log disk
protection for transaction recovery).

The Small and safe RDBMS column adds full disk protection and can withstand
any disk crash with zero database downtime.

The Large RDBMS column represents a typical size database for a database
subsystem. Disk protection is not included in these sizings but can be added to
increase the stability of the database.

Increasing the size of your database (DB2 only)

DB2 Workgroup Edition has a default table size limit of 64 GB with a page size of
4K. To increase the capacity of your DB2 database, you can create a new
tablespace, IBMDEFAULTGROUP, and choose a larger page size (up to 32K). This
increases the capacity of the database up to 512 GB per table.

The following example creates the IBMDEFAULTGROUP tablespace with a page

size of 16 K. This increases the table size capacity to 256 GB.
CREATE REGULAR TABLESPACE IBMDEFAULTGROUP IN DATABASE PARTITION GROUP IBMCATGROUP
PAGESIZE 16384 MANAGED BY DATABASE
USING (FILE ’E:\DB2\NODE0000\SQL00001\IBMDEFAULTGROUP.001’1500000)
EXTENTSIZE 32
PREFETCHSIZE AUTOMATIC
BUFFERPOOL IBM16KBP
OVERHEAD 12.670000
TRANSFERRATE 0.180000
DROPPED TABLE RECOVERY ON

If 512 GB of space per table is not enough for your environment, move to DB2
Enterprise Edition and using physical or logical partitioning.

The following steps outline the process for using database partitioning with DB2
Enterprise Edition:
1. Add a new database partition to the DB2 instance by running the db2ncrt
command.
2. Use the ALTER TABLE statement to add a partitioning key to the tables that
you want to partition. For example:
ALTER TABLE "CANDLE "."NT_System" ADD PARTITIONING KEY ("Server_Name")
USING HASHING
3. Use the ALTER DATABASE PARTITION GROUP statement to assign the new
partition to the database partition group. You can do this either from the
command line or from the DB2 Control Center.
4. Redistribute the data in the database partition group, using the Redistribute
Data Wizard in the DB2 Control Center.
For additional information about database partitioning, see the following DB2
sources:
v IBM DB2 Universal Database™ Administration Guide: Planning
v IBM DB2 Universal Database Administration Guide: Implementation
v DB2 Information Center at
http://publib.boulder.ibm.com/infocenter/db2help/index.jsp.

36 IBM Tivoli Monitoring: Installation and Setup Guide

For additional database performance and tuning information, see the IBM Tivoli
Monitoring Administrator's Guide.

Chapter 3. Planning the installation of your environment 37

38 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 4. Upgrading from a previous installation
This chapter provides information for upgrading from OMEGAMON Platform 350
or 360 and CandleNet Portal 195 to IBM Tivoli Monitoring 6.1.

Note: You cannot upgrade directly to IBM Tivoli Monitoring from a version of
OMEGAMON Platform prior to 350 or 360. If you are using an older version
of OMEGAMON Platform, you must first upgrade to OMEGAMON 350 or
360 before upgrading to IBM Tivoli Monitoring.

If you are upgrading from Tivoli Distributed Monitoring, see the IBM Tivoli
Monitoring: Upgrading from Tivoli Distributed Monitoring guide.

Upgrading from Candle OMEGAMON 350 or 360 involves the following steps:
Table 9. Upgrading from OMEGAMON 350 or 360
Task Where to find information
Before installing IBM Tivoli Review the new terminology. Although “Terminology changes” on page 40
Monitoring the same components exist in IBM Tivoli
Monitoring, many have new names.
Review the upgrade planning information “Upgrade planning” on page 40
to identify what you can and cannot
upgrade.
Stop all components that you are “Starting and stopping components” on
upgrading and change their startup from page 108
Automatic to Manual.
If you are upgrading a hub monitoring
server and you have already configured it
to work with the Hot Standby feature,
stop all agents that connect to the
monitoring server.
Restart the computer on which you are
installing IBM Tivoli Monitoring.
Upgrading your monitoring Run the IBM Tivoli Monitoring Chapter 5, “Installing IBM Tivoli
environment installation program on all components Monitoring,” on page 47
that you want to upgrade. Use your
existing installation directory as your IBM
Tivoli Monitoring directory.
After installing IBM Tivoli Run the Warehouse Proxy migration tool “Migrating data from an existing
Monitoring to migrate your existing Warehouse Proxy Warehouse Proxy database” on page 42
database.
For any existing OMEGAMON monitoring “Using existing OMEGAMON agents
agents that you want to use with the IBM with IBM Tivoli Monitoring” on page 45
Tivoli Monitoring monitoring server,
change their configuration to point to the
new monitoring server.

Notes:
1. After you upgrade a UNIX monitoring server, you must run the itmcmd config
-S command to configure the upgraded monitoring server and the itmcmd
support command to update application support files.

© Copyright IBM Corp. 2005 39

 2. If you start your portal server before you upgrade your monitoring agents, you
must stop and restart the portal server to use the upgraded workspaces for
these agents.
3. You cannot use the agent deployment function in IBM Tivoli Monitoring to
upgrade OMEGAMON agents.

Terminology changes
The following terms have changed with the move from Candle OMEGAMON to
IBM Tivoli Monitoring:
Table 10. OMEGAMON to IBM Tivoli Monitoring terminology
OMEGAMON term IBM Tivoli Monitoring term
®
Candle Management Server (CMS) Tivoli Enterprise Monitoring Server
CandleNet Portal (CNP) Tivoli Enterprise Portal
CandleNet Portal Server (CNPS) Tivoli Enterprise Portal Server
®
OMEGAMON Monitoring Agent (OMA) Tivoli Enterprise Monitoring Agent
(monitoring agent)
OMEGAMON Platform Tivoli Monitoring Services
Manage Candle Services Manage Tivoli Enterprise Monitoring
Services
Event Situation event
Seeding Adding application support
OMEGAMON Web Services Tivoli Monitoring Web Services
Candle Customer Support IBM Software Support

Upgrade planning
This section discusses some issues you need to consider before upgrading IBM
Tivoli products.

When to run the upgrade

Run the upgrade to IBM Tivoli Monitoring immediately after you have rebooted
the computer on which you are running the upgrade. IBM Tivoli Monitoring does
not install if the computer has any locked files.

If your OMEGAMON components are currently set to start automatically, change

the startup to Manual in Manage Candle Services before you restart the
components.

Installation directory for upgraded components

When you upgrade an existing OMEGAMON component to the IBM Tivoli
Monitoring level, the installation process installs all new files in your existing
installation directory (instead of the new default installation directory for IBM
Tivoli Monitoring: IBM/ITM on Windows and /opt/IBM/ITM on Linux and
UNIX). Your existing files are overwritten.

If you have applied fixes or patches to the OMEGAMON product component,

those fixes and patches that were available when IBM Tivoli Monitoring was
released are included in the upgraded version.

40 IBM Tivoli Monitoring: Installation and Setup Guide

Configuration settings for upgraded agents
When OMEGAMON V350 or 360 agents are upgraded to IBM Tivoli Monitoring,
agent-specific configuration settings regarding the connection to the monitoring
server are not maintained. The IBM Tivoli Monitoring installation uses the default
settings for all agents (not the one change that you made for one agent). In order
to ensure that your upgraded agents can immediately connect to the monitoring
server, ensure that the default settings for all agents point to the new monitoring
server prior to upgrading. To change the default settings for all agents, right-click
an agent in Manage Candle Services and click Set defaults for all agents.

Candle Management Workstation coexistence

If you currently use Candle Management Workstation in your OMEGAMON
monitoring environment, you are migrated to IBM Tivoli Monitoring automatically
when you migrate the rest of your environment. However, the installed Candle
Management Workstation continues to function after the migration, although it is
not officially part of IBM Tivoli Monitoring and no new function has been added.

If you use the OMEGAMON XE for CICS® 3.1.0 product, you must continue to use
Candle Management Workstation to configure workloads for Service Level
Analysis. After you have configured the workloads, you can use the Tivoli
Enterprise Portal for all other tasks.

If you do not currently have Candle Management Workstation (for example, if you
are installing OMEGAMON XE for CICS 3.1.0 into an IBM Tivoli Monitoring
environment), you must install the Candle Management Workstation that is
shipped with the OMEGAMON XE for CICS 3.1.0 product. Install Candle
Management Workstation on a different computer than the Tivoli Enterprise Portal.
Otherwise, the Candle Management Workstation attempts to uninstall the Tivoli
Enterprise Portal.

Additional unsupported OMEGAMON functions

The following functions are no longer supported as part of IBM Tivoli Monitoring:
Table 11. Unsupported OMEGAMON functions
Function IBM Tivoli Monitoring equivalent function
CandleClone Agent deployment, as described in
Chapter 10, “Deploying monitoring across
CandleRemote your environment,” on page 135
Event emitters Event forwarding using the Tivoli Enterprise
Console event synchronization, as described
in Chapter 6, “Installing the IBM Tivoli
Event adapters Enterprise Console event synchronization,”
on page 85
GUI installation wizard on UNIX Use the command line installation option, as
described in Chapter 5, “Installing IBM
Tivoli Monitoring,” on page 47
Silent installation on UNIX using the Silent installation using custom response
multi-platform installation program files, as described in “Performing a silent
installation on a Linux or UNIX computer”
on page 177.

Chapter 4. Upgrading from a previous installation 41

 CandleNet Portal database
If you use a DB2 database for the CandleNet Portal, the database is converted to
UTF-8 format during the upgrade. This might take several minutes, depending on
the size of your database. If you used the default database password when you
created the CandleNet Portal database (cnps), you are prompted for a new
password to comply with the more stringent security provisions in IBM Tivoli
Monitoring.

Required Java JRE

The CandleNet Portal requires the Sun Java JRE; however Tivoli Enterprise Portal
requires the IBM Java JRE 1.4.2. You do not need to install this JRE prior to the
upgrade: it is installed automatically when you choose to install an IBM Tivoli
Monitoring component that requires it.

Migrated information when upgrading from a previous version

If you are installing over a previous release (into the same IBM directory) the
following information is migrated into the new version:
v On Windows:
– Port number and communication protocol settings
– Situations
v UNIX: Situations

Migrating data from an existing Warehouse Proxy database

You can migrate your existing data in an OMEGAMON 360 data warehouse to the
IBM Tivoli Monitoring Tivoli Data Warehouse using a migration tool provided
with IBM Tivoli Monitoring.

Before you migrate to the new data warehouse, you need to create a new ODBC
data source for the 6.1.0 version of the Warehouse Proxy agent and connect that
data source to a new database. The migration tool moves your data from the
existing database to the new database. For information about creating a new data
source and database, see Chapter 11, “Configuring the Warehouse Proxy for the
Tivoli Data Warehouse,” on page 145.

The warehouse migration tool is installed when you install the Warehouse
Summarization and Pruning Agent. The following files are installed in the
itm_installdir/tmaitm6 directory:
v khdmig.jar
v KHDENV_MIG
v migratewarehouse.bat

Note: Warehouse migration is only supported on Windows computers.

The tool also uses several files installed by the Warehouse Summarization and
Pruning Agent.

The following sections provide information on using the warehouse migration tool.

Before you run the tool

Perform the following tasks before you run the migration tool:
v Back up your existing database.

42 IBM Tivoli Monitoring: Installation and Setup Guide

 v If your existing database is a Microsoft SQL database, install a Microsoft SQL
JDBC driver on the computer where that database is installed. You can
download the JDBC driver from the Microsoft Web site for Microsoft SQL.
v Install the IBM Java JRE, version 1.4.2.
v If you have collected data for multiple agents in the past and you want to
migrate the data for all of those agents, you must install the new version 6.1
agents on the Tivoli Enterprise Portal Server.
v Start the Tivoli Enterprise Portal Server.
v Stop the Warehouse Summarization and Pruning and the Warehouse Proxy
agents.
v Do not start data collection with the Warehouse Summarization and Pruning
agent prior to running this migration tool. If you do, the information that you
migrate will not be pruned or summarized. If this is the case, delete the content
of the WAREHOUSEMARKER table to enable pruning of both migrated and
new data.

Configuring the migration tool

Before running the migration tool, use the following steps to configure the tool for
your environment:
1. Update the migratewarehouse.bat file to set the correct CLASSPATH for your
JDBC driver.
The file contains the following default installation directories for the 3
supported drivers. Update the location based on where your JDBC driver is
installed.
v Microsoft SQL Server:
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar
C:\Program Files\Microsoft SQL Server 2000 Driver for
JDBC\lib\mssqlserver.jar
C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar
v DB2: C:\Program Files\IBM\SQLLIB\java\db2java.zip
v Oracle: C:\oracle\ora92\jdbc\lib\classes12.zip
2. Update the following variables in the KHDENV_MIG file:
Table 12. KHDENV_MIG file variables for warehouse migration
Type of information Variable Description
Commit rate KHD_MAX_ROWS_PER_TRANSACTIONS The number of rows committed at each
insertion of data.
Bad rows to skip KHD_MAX_ROWS_SKIPPED_PER_TABLE The number of rows per table the tool skips
to migrate if the data that needs to be
inserted is incorrect. When this number is
reached, the tool stops the migration of the
table.
Tivoli Enterprise Portal KHD_CNP_SERVER_HOST The name of the Tivoli Enterprise Portal
connection information Server.
KHD_CNP_SERVER_PORT The port number of the Tivoli Enterprise
Portal Server.

Chapter 4. Upgrading from a previous installation 43

Table 12. KHDENV_MIG file variables for warehouse migration (continued)
Type of information Variable Description
Source database KHD_SOURCE_JDBC_DRIVER The JDBC driver used to connect to the
connection information source database.
KHD_SOURCE_URL The URL to use to connect to the source
database.
KHD_SOURCE_DATABASE_SCHEMA The owner or schema in the Candle tables
in the source database.
KHD_SOURCE_DATABASE_USER The user that connects to the source
database.
KHD_SOURCE_DATABASE_PASSWORD The password for the user to connect to the
source database.
Target database KHD_TARGET_JDBC_DRIVER The JDBC driver used to connect to the
connection information target database.
KHD_TARGET_URL The URL to use to connect to the target
database.
KHD_TARGET_DATABASE_SCHEMA The owner or schema in the tables in the
target database.
KHD_TARGET_DATABASE_USER The user that connects to the target
database.
KHD_TARGET_DATABASE_PASSWORD The password for the user to connect to the
target database.

For JDBC driver information, use the syntax appropriate to your driver vendor:
DB2 URL: jdbc:db2:<database>
Driver: COM.ibm.db2.jdbc.app.DB2Driver
MS SQL Server
URL:
jdbc:microsoft:sqlserver://<server>:<port>;DatabaseName=<database>
Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver
Default port: 1433
Oracle URL: jdbc:oracle:thin:@<server>:<port>:<database>
Driver: oracle.jdbc.driver.OracleDriver
Default port: 1521

Running the warehouse migration tool

After you update the files, as described in the previous section, run the
migratewarehouse.bat file.

Status tables
Part of the migration of data to the new warehouse requires shortening the table
and column names if the target database is not a Microsoft SQL database. When a
name is shortened, an entry is created inside the WAREHOUSEID table in your
new database. You can view this table to check which table names or column
names have been modified.

For each package of rows committed, an entry is also made in the new
WAREHOUSEMIGLOG table.

44 IBM Tivoli Monitoring: Installation and Setup Guide

 If the migration tool fails during the migration, you can look at the
WAREHOUSEMIGLOG table to identify those tables that migrated successfully. If
you want to restart the migration without migrating these tables again, delete the
tables from the source database. You must also delete all the data that has been
partially exported in the last tables. Use the writetime column in this table to
determine which data is old and which new.

Using existing OMEGAMON agents with IBM Tivoli Monitoring

Existing installed OMEGAMON 350 and 360 agents can be supported using the
Tivoli Enterprise Monitoring Server; however, the following restrictions apply:
v New features in IBM Tivoli Monitoring (such as remote deployment) are not
supported on these agents.
v Agents must use one of the following protocols to communicate with the
monitoring server:
– IP.UDP (formerly TCP/IP)
– IP.PIPE
– SNA
The IP.SPIPE protocol is not supported for OMEGAMON agents.
v You cannot install an OMEGAMON agent on the same computer as a Tivoli
Enterprise Portal Server. If you want to monitor something on the same
computer as the portal server, install an IBM Tivoli Monitoring agent, if one is
available.

To monitor the OMEGAMON agent, use Manage Candle Services to change the
monitoring server to which the agent sends data.

To enable the Tivoli Data Warehouse to collect data from these agents (through the
Warehouse Proxy), copy the product attribute file to the ATTRLIB directory on the
Warehouse Proxy agent.

For full interoperability between OMEGAMON agents and IBM Tivoli Monitoring,
you need to install the application support files for these agents on the monitoring
server, portal server, and portal desktop client. See the "OMEGAMON V350/360
agent interoperability" document in the IBM Tivoli Monitoring information center
for information about downloading and installing these support files.

Chapter 4. Upgrading from a previous installation 45

46 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 5. Installing IBM Tivoli Monitoring
The following sections provide detailed steps for installing IBM Tivoli Monitoring
in your environment. The installation and initial configuration of your environment
consists of the following steps:
Table 13. IBM Tivoli Monitoring high-level installation steps
Step Where to find information
Install the hub Tivoli Enterprise Monitoring “Installing and configuring the hub Tivoli
Server. Enterprise Monitoring Server” on page 48
Install any remote monitoring servers. “Installing and configuring the remote
monitoring servers” on page 54
Install the Tivoli Enterprise Portal Server. “Installing the Tivoli Enterprise Portal
Server” on page 59
Install any monitoring agents. “Installing monitoring agents” on page 64
Note: If you plan to use the remote
deployment function in IBM Tivoli
Monitoring to install monitoring agents
across your environment, see Chapter 10,
“Deploying monitoring across your
environment,” on page 135 for the required
steps.
Install the portal desktop client (optional). “Installing Tivoli Enterprise Portal desktop
client” on page 70
If you want to use the browser client, you
do not need to install it. However, if your
portal server is on Linux, you must install
the browser client support on the portal
server.
Install required application support on “Installing support for agents on the
monitoring server, portal server, and portal monitoring server, portal server, and desktop
desktop client. client” on page 73
Install the language pack for all languages “Installing the language packs” on page 81
other than English.
Start the Tivoli Enterprise Portal to verify “Starting the Tivoli Enterprise Portal client”
your installation. on page 82

The following sections contain both Windows and UNIX procedures for installing
the various components. Use the procedure that best applies to your environment
layout.

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

See Appendix A, “Installation worksheets,” on page 163 for a set of worksheets

that you can use to gather the information required for the installation of
components.

© Copyright IBM Corp. 2005 47

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 hub monitoring server”
v “Linux or UNIX: Installing a hub monitoring server” on page 51

Windows: Installing the hub monitoring server

Use the following steps to install the hub monitoring server on a Windows
computer
1. Launch the installation wizard by double-clicking the setup.exe file in the
\WINDOWS subdirectory on the installation media.

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 stating that the setup.exe file is from an unknown publisher. Click
Run to disregard this error message.
2. Click Next on the welcome window.
3. Click Accept to accept the license agreement.
4. If you do not have a database (DB2 or MS SQL) installed on this computer, a
message regarding potentially missing software is displayed. You do not need
a database to use this computer as a monitoring server, so you can click Next
and ignore this message.
5. Choose the directory where you want to install the product. The default
directory is C:\IBM\ITM. Click Next.
6. Type a 32 character encryption key. You can use the default key.
Notes:
a. Do not use any of the following characters in your key:
v =
v ’
v |
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.
Click Next and then click OK to confirm the encryption key.
7. Select the components that you want to install: Tivoli Enterprise Monitoring
Server.
8. If you want to use the Summarization and Pruning agent to work with data in
your data warehouse, expand Tivoli Enterprise Monitoring Agent and select
Windows Summarization and Pruning Agent.
See the IBM Tivoli Monitoring Administrator’s Guide for information about
configuring and using this agent.
9. Click Next.
10. 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
Chapter 10, “Deploying monitoring across your environment,” on page 135).
Click Next.

Note: By default, the depot is located in the <itm_installdir>/CMS/depot

directory on Windows and <itm_installdir>/tables/<ms_name>/depot

48 IBM Tivoli Monitoring: Installation and Setup Guide

 directory on Linux and UNIX. If you want to use a different directory,
add (if it does not exist) or change the DEPOTHOME value in the
KBBENV file.
11. Select a program folder and click Next. The default program folder name is
IBM Tivoli Monitoring.
12. 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 (called the "Setup
Type" window) is displayed.
13. Select what you want to configure and click Next.
The first step configures the monitoring server.
14. Select the type of monitoring server you are configuring: Hub or remote. For
this procedure, select Hub.
15. Verify that the name of this monitoring server is correct in the TEMS field. If
it is not, change it.
The default name is ″hub_host_name.″ For example, ″hub_itmserv16.″
16. Identify the communications protocol for the monitoring server. You have four
choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. You can specify three methods for
communication - this enables you to set up backup communication methods.
If the method you have identified as Protocol 1 fails, Protocol 2 is used.
17. If you want to forward situation events to IBM Tivoli Enterprise Console.
select TEC Event Integration Facility.
Do not select any of the other options on this window (for example Address
Translation) or the option to configure hot standby. You can configure these
options after installation is complete.

Important: Do not select Security: Validate User. You can configure security
after installing the monitoring server, as described in “Configuring
user security” on page 109.
18. Click OK.
19. Complete the following fields for the communications protocol for the
monitoring server.
Table 14. Communications protocol settings
Field Description
IP.UDP Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server. The default port is 1918.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.

Chapter 5. Installing IBM Tivoli Monitoring 49

 Table 14. Communications protocol settings (continued)
Field Description
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.

20. If you are certain that you have typed the values for all of these fields with
exactly the correct casing (upper and lower cases), you can select Use case as
typed. However, because IBM Tivoli Monitoring is case-sensitive, consider
selecting Convert to upper case to reduce the chance of user error.
21. Click OK to continue.
22. If you selected TEC Event Integration Facility, provide the host name and
port number for the event server that you want to forward events to and click
OK. Otherwise, skip this step.
The next configuration step is to add application support to the monitoring
server, such as the situations for agents.
23. Specify the location of the monitoring server to which to add application
support. You have two choices:
v On this computer
v On a different computer
Click OK.

Note: If you are installing a backup monitoring server, see “Adding

application support on the backup hub monitoring server” on page 110
for information about adding application support.
24. Because the monitoring server is not currently running, it is started
automatically before the process begins. Click OK on the message telling you
this.
25. Select the data that you want to add to the monitoring server. By default, all
available application support is selected. Click OK.
The process of adding application support files can take up to 20 minutes.
26. Click Next on the message that provides results for the process of adding
application support. A return code of 0 (RC=0) indicates that the process
succeeded.
The next configuration step configures the default communication between
any IBM Tivoli Monitoring component and the hub monitoring server.
27. Specify the default values for any IBM Tivoli Monitoring component to use
when they communicate with the monitoring server.
a. If agents must cross a firewall to access the monitoring server, select
Connection must pass through firewall.

50 IBM Tivoli Monitoring: Installation and Setup Guide

 b. Identify the type of protocol that the agents use to communicate with the
hub monitoring server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or
SNA. You can specify three methods for communication - this enables you
to set up backup communication methods. If the method you have
identified as Protocol 1 fails, Protocol 2 is used.
Click OK.
28. Complete the communication protocol fields for the monitoring server. See
step 19 on page 49 for definitions of these fields.

Note: Do not select Optional Secondary TEMS Connection. You can set up
the failover support for agents after install, as described in
“Configuring failover support” on page 110.
29. Click Finish to complete the installation.

The Manage Tivoli Enterprise Monitoring Services utility is opened. (This might
take a few minutes.) You can start, stop, and configure IBM Tivoli Monitoring
components with this utility.

Linux or UNIX: Installing a hub monitoring server

Use the following steps to install and configure the hub monitoring server on a
UNIX computer.
Table 15. Steps for installing a portal server on a Linux 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 52
Add application support to the hub “Adding application support to the hub
monitoring server. monitoring server” on page 54

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
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 asked whether 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 (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 in and press Enter.
6. Press Enter to display the agreement.

Chapter 5. Installing IBM Tivoli Monitoring 51

 7. Type 1 to accept the agreement and press Enter.
8. Type a 32 character 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 =
v ’
v |
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 for which you want to install
products. 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 Tivoli Enterprise Monitoring Server
option. 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. For example:
HUB_hostname. Do not use the fully qualified host name. Press Enter.
14. After all of the components are installed, you are asked 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 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 tems_name

where tems_name is the name of your monitoring server (for example,

HUB_itmdev17).
3. Press Enter to indicate that this is a hub monitoring server (indicated by the
*LOCAL default).
4. Press Enter to accept the default host name for the monitoring server. This
should be the host name for your computer. If it is not, type the correct host
name and then press Enter.
5. Enter the type of protocol to use for communication with the monitoring
server. You have four choices: ip, ip.pipe, ip.spipe, or sna. Press Enter to use
the default communications protocol (IP.PIPE).
6. If you want to set up a backup protocol, enter that protocol and press Enter. If
you do not want to use backup protocol, press Enter without specifying a
protocol.
7. Depending on the type of protocol you specified, provide the following
information when prompted:

52 IBM Tivoli Monitoring: Installation and Setup Guide

Table 16. UNIX monitoring server protocols and values
Protocol Value Definition
IP.UDP IP Port Number The port number for the
monitoring server. The
default is 1918.
SNA Net Name The SNA network identifier
for your location.
LU Name The LU name for the
monitoring server. This LU
name corresponds to the
Local LU Alias in your SNA
communications software.
Log Mode The name of the LU6.2
LOGMODE. The default
value is ″CANCTDCS.″
IP.PIPE IP.PIPE Port Number The port number for the
monitoring server. The
default is 1918.
IP.SPIPE IP.SPIPE Port Number The port number for the
monitoring server. The
default is 3660.

8. Press Enter to not specify the name of the KDC_PARTITION.

Note: You can configure the partition file at a later time, as described in
“Firewall support” on page 117.
9. Press Enter when prompted for the path and name of the KDC_PARTITION.
10. If you want to use Configuration Auditing, press Enter. If you do not want to
use this feature, type n and press Enter.
11. Press Enter to accept the default setting for the Hot Standby feature (NO).
For best results, wait until after you have fully deployed your environment to
configure the Hot Standby feature for your monitoring server. See
“Configuring failover support” on page 110 for information about configuring
Hot Standby.
12. Press Enter to accept the default for the Optional Primary Network Name
(none).
13. Press Enter for the default Security: Validate User setting (no).

Important: Do not change this to set Security: Validate User. You can
configure security after configuring the monitoring server, as
described in “Configuring user security” on page 109.
14. If you will be using IBM Tivoli Enterprise Console to view situation events,
type y and press Enter to enable TEC 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 accept the default SOAP configuration and exit the configuration.

Note: You can configure any SOAP information at a later time. See
Chapter 12, “Configuring IBM Tivoli Monitoring Web Services (SOAP
Server) on Windows,” on page 159 for information.

Chapter 5. Installing IBM Tivoli Monitoring 53

 The monitoring server is now configured.

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

host_name_ms_tems_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.
Application support includes the workspaces and situations for agents.

Note: If you are installing a backup monitoring server, see “Adding application
support on the backup hub monitoring server” on page 110 for information
about adding application support.
1. Start the monitoring server by running the following command:
./itmcmd server start tems_name
2. Run the following command to add the application support:
./itmcmd support -t tems_name pc pc pc

where pc is the product code for each agent whose data you want to send to
the monitoring server. See Appendix D, “IBM Tivoli Product Codes,” on page
185 for a list of agent product codes.
3. Stop the monitoring server by running the following command:
./itmcmd server stop tems_name
4. Restart the monitoring server by running the following command:
./itmcmd server start tems_name

Installing and configuring the remote monitoring servers

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

Windows: Installing the remote monitoring server

Use the following steps to install the remote monitoring server on a Windows
computer
1. Launch the installation wizard by double-clicking the setup.exe file in the
\WINDOWS subdirectory on the installation media.

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 stating that the setup.exe file is from an unknown publisher. Click
Run to disregard this error message.
2. Click Next on the welcome window.
3. Click Accept to accept the license agreement.
4. If you do not have a database (DB2 or MS SQL) installed on this computer, a
message regarding potentially missing software is displayed. You do not need
a database to use this computer as a monitoring server, so you can click Next
and ignore this message.
5. Choose the directory where you want to install the product. The default
directory is C:\IBM\ITM. Click Next.
6. Type a 32 character encryption key. You can use the default key.

54 IBM Tivoli Monitoring: Installation and Setup Guide

 Note: 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.
Click Next and then click OK to confirm the encryption key.
7. Select the components that you want to install: Tivoli Enterprise Monitoring
Server.
8. If you want to install any agents on this remote monitoring server, expand
Tivoli Enterprise Monitoring Agents and select the agent.
9. Click Next.
10. If you want to do remote deployment of agent software from this remote
monitoring server, 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 Chapter 10, “Deploying monitoring
across your environment,” on page 135). Click Next.

Note: By default, the depot is located in <itm_installdir>/CMS/depot

directory on Windows and <itm_installdir>/tables/<ms_name>/depot
directory on Linux and UNIX. If you want to use a different directory,
add (if it does not exist) or change the DEPOTHOME value in the
KBBENV configuration file.
11. Select a program folder and click Next. The default program folder name is
IBM Tivoli Monitoring.
12. 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 is displayed.
13. Select what you want to configure and click Next.
The first step configures the monitoring server.
14. Select the type of monitoring server you are configuring: Hub or Remote. For
this procedure, select Remote.
15. Verify that the name of this monitoring server is correct in the TEMS field. If
it is not, change it.
The default name is ″remote_host_name.″ For example, ″remote_itmserv16.″
16. Identify the communications protocol for the monitoring server. You have four
choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. You can specify three methods for
communication - this enables you to set up backup communication methods.
If the method you have identified as Protocol 1 fails, Protocol 2 is used.
17. Click OK.
18. Complete the following fields for the communications protocol for the
monitoring server.
Table 17. Remote monitoring server communications protocol settings
Field Description
IP.UDP Settings: Primary Hub TEMS
Host name or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server. The default port is 1918.
IP.PIPE Settings: Primary Hub TEMS

Chapter 5. Installing IBM Tivoli Monitoring 55

 Table 17. Remote monitoring server communications protocol settings (continued)
Field Description
Host name or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default value is 1918.
IP.SPIPE Settings: Primary Hub TEMS
Host name or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default value is 3660.
SNA Settings: Remote TEMS
Local LU Alias The LU alias.
TP Name The transaction program name for this
monitoring server.
SNA Settings: Primary Hub TEMS
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.

19. If you are certain that you have typed the values for all of these fields with
exactly the correct casing (upper and lower cases), you can select Use case as
typed. However, because IBM Tivoli Monitoring is case-sensitive, consider
selecting Convert to upper case to reduce the chance of user error.
20. Click OK to continue.
21. Specify the location of the monitoring server to which to add application
support. You have two choices:
v This computer
v On a different computer
Click OK.
22. Because the monitoring server is not currently running, it is started
automatically before the process begins. Click OK on the message telling you
this.
23. Select the data that you want to add to the monitoring server. By default, all
available application support is selected. Click OK.
The process of adding application support files can take up to 20 minutes.
24. Click Next on the message that provides results for the process of adding
application support. A return code of 0 (RC=0) indicates that the process
succeeded.
The next configuration step configures the default communication between
any IBM Tivoli Monitoring component and the monitoring server.
25. Specify the default values for any IBM Tivoli Monitoring component to use
when they communicate with the monitoring server.

56 IBM Tivoli Monitoring: Installation and Setup Guide

 Identify the type of protocol that the agents use to communicate with the hub
monitoring server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA.
You can specify three methods for communication - this enables you to set up
backup communication methods. If the method you have identified as
Protocol 1 fails, Protocol 2 is used.
Click OK.
26. Complete the communication protocol fields for the monitoring server and
click OK. See step 18 on page 55 for definitions of these fields.

Note: Do not select Optional Secondary TEMS Connection. You can set up
the failover support for agents after install, as described in
“Configuring failover support” on page 110.
27. Click Finish to complete the installation.

Linux or UNIX: Installing a remote monitoring server

Use the following steps to install and configure the remote monitoring server on a
Linux or UNIX computer.
Table 18. Steps for installing a remote monitoring server on a Linux or UNIX computer
Steps Where to find information
Install the remote monitoring server. Use the “Installing the monitoring server” on page
same instructions as for installing the hub 51
monitoring server.
Configure the remote monitoring server. “Configuring the remote monitoring server”
Add application support to the hub “Adding application support to the hub
monitoring server. monitoring server” on page 54

Configuring the remote monitoring server

Use the following steps to configure the remote 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 tems_name

where tems_name is the name of your monitoring server (for example,

remote_itmdev17).
3. Type remote to indicate that this is remote hub monitoring server.
4. Press Enter to accept the default host name for the monitoring server. This
should be the host name for your computer. If it is not, type the correct host
name and then press Enter.
5. Enter the type of protocol to use for communication with the monitoring
server. You have four choices: ip, ip.pipe, ip.spipe, or sna. Press Enter to use
the default communications protocol (IP.PIPE).
6. If you want to set up a backup protocol, enter that protocol and press Enter. If
you do not want to use backup protocol, press Enter without specifying a
protocol.
7. Depending on the type of protocol you specified, provide the following
information when prompted:

Chapter 5. Installing IBM Tivoli Monitoring 57

 Table 19. UNIX monitoring server protocols and values
Protocol Value Definition
IP.UDP IP Port Number The port number for the
monitoring server. The
default is 1918.
SNA Net Name The SNA network identifier
for your location.
LU Name The LU name for the
monitoring server. This LU
name corresponds to the
Local LU Alias in your SNA
communications software.
Log Mode The name of the LU6.2
LOGMODE. The default
value is ″CANCTDCS.″
IP.PIPE IP.PIPE Port Number The port number for the
monitoring server. The
default is 1918.
IP.SPIPE IP.SPIPE Port Number The port number for the
monitoring server. The
default is 3660.

8. Press Enter to not specify the name of the KDC_PARTITION.

Note: You can configure the partition file at a later time, as described in
“Firewall support” on page 117.
9. Press Enter when prompted for the path and name of the KDC_PARTITION.
10. If you want to use Configuration Auditing, press Enter. If you do not want to
use this feature, type n and press Enter.
11. Press Enter to accept the default setting for the Hot Standby feature (NO).
For best results, wait until after you have fully deployed your environment to
configure the Hot Standby feature for your monitoring server. See
“Configuring failover support” on page 110 for information about configuring
Hot Standby.
12. Press Enter to accept the default for the Optional Primary Network Name
(none).
13. Press Enter for the default Security: Validate User setting (no).

Important: Do not change this to set Security: Validate User. You can
configure security after configuring the monitoring server, as
described in “Configuring user security” on page 109.
14. If you will be using IBM Tivoli Enterprise Console to view situation events,
type y and press Enter to enable TEC 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 accept the default SOAP configuration and exit the configuration.

Note: You can configure any SOAP information at a later time. See
Chapter 12, “Configuring IBM Tivoli Monitoring Web Services (SOAP
Server) on Windows,” on page 159 for information.

58 IBM Tivoli Monitoring: Installation and Setup Guide

 The monitoring server is now configured.

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

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

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 these steps:
v “Windows: Installing the portal server”
v “Linux: Installing the portal server” on page 61

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.
3. Read and accept the software license agreement by clicking Accept.
4. If you do not have a database (DB2 or MS SQL) or the IBM Java JRE 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 JRE, the installation program installs it
automatically during a later step. Click Next.

Note: If your computer has all required software, you will not 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 should be the same as what was used
during the installation of the monitoring server to which 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. If you want to view events on the IBM Tivoli Enterprise Console event server
through the Tivoli Enterprise Portal, expand Tivoli Enterprise Portal Server
and ensure that Tivoli Enterprise Console GUI Integration is selected.
9. If you plan to monitor the IBM Tivoli Composite Application Manager for
Response Time Tracking agent, select IBM Eclipse Help Server. This help
server runs the help system for that agent. Otherwise, you do not need to
install this component.
10. Click Next.
If you are installing the portal server on a computer that already has a
monitoring server installed, the next step is to populate the depot. If you do
not have a monitoring server on this computer, this step is skipped.
11. Type a name for the program folder. The default is IBM Tivoli Monitoring.
Click Next.
12. Click Next to start the installation.
After installation is complete, a configuration window is displayed.
13. Click Next to begin configuring the portal server and the connection to the
monitoring server and to open Manage Tivoli Enterprise Monitoring Services.

Chapter 5. Installing IBM Tivoli Monitoring 59

 14. Type the host name of the computer where you are installing the portal server
and click Next.
15. Configure the portal server’s connection to the data source (such as your DB2
database). Type the password for the database administrator in the Admin
Password field.
16. 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.
17. Click OK on the message that tells you that the portal server configuration
was successful.
18. Type a user ID (such as ″ITMUser″) in the User ID field and type a password
for the user in the Password field. Click Next.
19. Click OK to accept the default values for the connection between the portal
server and the hub monitoring server.
20. Type the host name or IP address and the port number for the hub monitoring
server. Click OK.
21. You are asked if you want to reconfigure the warehouse connection. If you
have not configured the ODBC data source connection for the Warehouse
Proxy, click Yes and complete the following steps. Otherwise, click No.

Note: These steps are based on a DB2 database. The steps might be different
if you are using a different 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.″
Database Name
The name of the database. If you are defining a new data source
and want to specify a different database, type the name here.
Otherwise, leave the default value, "WAREHOUS."
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.

60 IBM Tivoli Monitoring: Installation and Setup Guide

 Reenter Password
Confirm the password by typing it again.
c. Click OK.
22. 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:
23. Ensure that the host name and port number of the Tivoli Enterprise
Monitoring Server are correct.
24. Click OK to accept the default values for the communications protocol for the
agents to use to communicate with the hub monitoring server.
25. Clear the check box next to Display the README file.
26. 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

Use the following steps to install and configure the portal server and portal client
on a Linux computer.

Important: Run these installation and configuration procedures as either the root
user or as the DB2 administrator. After you have installed and
configured the portal server, you can use a different user to run the
portal server, as long as that user has access to the binaries used by the
portal server.
Table 20. Steps for installing a portal server on a Linux computer
Steps Where to find information
Install the portal server on the Linux “Installing the portal server”
computer.
Configure the portal server. “Configuring the portal server on Linux” on
page 62
Start the portal server. “Starting the portal server” on page 64

Note: DB2 is the only database supported for Tivoli Data Warehouse with a Linux
portal server.

Installing the portal server

Use the following steps to install the portal server:
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) or type the full path to a different
directory.
3. If the installation directory does not already exist, you are asked if you want
to create it. Type y to create this directory and press Enter.
4. The following prompt is displayed:

Chapter 5. Installing IBM Tivoli Monitoring 61

 Select one of the following:
1) Install products to the local host.
2) Install products to depot for remote deployment (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 in and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type a 32 character encryption key and press Enter. This key should be the
same as what was used during the installation of the monitoring server to
which this portal server will connect.
A numbered list of available operating systems is displayed.
9. Type the number for the operating system that you are installing on. 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 asked whether you want to
install components for a different operating system. Type y and press Enter.
14. Type the number that corresponds to ″Tivoli Enterprise Portal Browser Client
support″ and press Enter.
15. Type y to confirm and press Enter.
A list of the components to install is displayed.
16. Type the number that corresponds to "all of the above" and press Enter.
17. Type y to confirm the installation.
The installation begins.
18. When you are asked whether you want to install components for a different
operating system, type y and press Enter.
19. Type the number that corresponds to ″Tivoli Enterprise Portal Server support″
and press Enter.
20. Type y to confirm and press Enter.
A list of the components to install is displayed.
21. Type the number that corresponds to "all of the above" and press Enter.
22. Type y to confirm the installation.
The installation begins.
23. After all of the components are installed, you are asked 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 portal server.

Configuring the portal server on Linux

Use the following steps to configure the portal server.

62 IBM Tivoli Monitoring: Installation and Setup Guide

Note: You can also use this procedure to reconfigure the Linux portal server, if
needed.
1. At the command line change to the /opt/IBM/ITM/bin directory (or the /bin
subdirectory where you installed the product).
2. Run the following command:
./itmcmd config -A cq
3. Press Enter when you are asked if the agent connects to a monitoring server.
4. Type the host name for the hub monitoring server and press Enter.
5. Type the protocol that you want to use to communicate with your hub
monitoring server. You have four choices: ip, sna, ip.pipe, or ip.spipe.
6. If you want to set up a backup protocol, enter that protocol and press Enter. If
you do not want to use backup protocol, press Enter without specifying a
protocol.
7. Depending on the type of protocol you specified, provide the following
information when prompted:
Table 21. UNIX monitoring server protocols and values
Protocol Value Definition
IP.UDP IP Port Number The port number for the
monitoring server. The
default is 1918.
SNA Net Name The SNA network identifier
for your location.
LU Name The LU name for the
monitoring server. This LU
name corresponds to the
Local LU Alias in your SNA
communications software.
Log Mode The name of the LU6.2
LOGMODE. The default
value is ″CANCTDCS.″
IP.PIPE IP.PIPE Port Number The port number for the
monitoring server. The
default is 1918.
IP.SPIPE IP.SPIPE Port Number The port number for the
monitoring server. The
default is 3660.

8. Press Enter when you are asked if you want to configure the connection to a
secondary monitoring server. The default value is no.
9. Press Enter to accept the default for the Optional Primary Network Name
(none).
10. Press Enter to accept the default setting for SSL between the portal server and
clients (N). By default, SSL is disabled. To enable SSL, type y and press Enter.
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.
15. Type the name of the database for the portal server. The default is "TEPS."
Press Enter.

Chapter 5. Installing IBM Tivoli Monitoring 63

 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 asked if it is okay to create the DB2 login user if it does not exist.
Type y and press Enter.
20. Type the name of the database that the Tivoli Data Warehouse will use. The
default is ″WAREHOUS.″ This database must be cataloged locally if the
warehouse database resides on a remote computer. Press Enter.

Note: If you are using a remote node and database, you must manually
configure (catalog) the remote node and the remote database from the
Linux DB2 command line. Run the following commands to do this:
db2 catalog tcpip node <node_name> remote <host_name> server <port>
db2 catalog db <db_name> as <dbalias> at node <node_name>
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.

Starting the portal server

From the bin directory of /opt/IBM/ITM (or where you installed IBM Tivoli
Monitoring), run the following command to start the portal server:
./itmcmd agent start cq

Installing monitoring agents

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

Depending on the agent that you are installing, there might be additional
configuration steps required. See the agent documentation 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.

64 IBM Tivoli Monitoring: Installation and Setup Guide

 All agents require that agent-specific support be installed on the other IBM Tivoli
Monitoring components. For agents available on the IBM Tivoli Monitoring
installation CD (such as the OS and Log Alert agents), this support is installed
when you install the components using the instructions in this chapter. For agents
installed from their own product CD, you must manually install this support. See
“Installing support for agents on the monitoring server, portal server, and desktop
client” on page 73 for more information.

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 in the
\WINDOWS subdirectory on the installation media.
2. Click Next on the welcome window.
3. Click Accept to accept the license agreement.
4. If you do not have a database (DB2 or MS SQL) installed on this computer, a
message regarding potentially missing software is displayed. You do not need
a database to install a management agent on this computer, so you can click
Next and ignore this message.
5. Choose the directory where you want to install the product. Click Next.

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 7.
6. Type a 32 character encryption key. This key should be the same as the key
that was used during the installation of the monitoring server to which this
monitoring agent connects.
Click Next and then click OK to confirm the encryption key.
7. Expand Tivoli Enterprise Monitoring Agents.
8. Select the name of the agent that you want to install and click Next.
If you are installing the agent on a computer that already has a monitoring
server installed, the next step is to populate the depot. If you do not have a
monitoring server on this computer, this step is skipped.

Note: The following step applies only to those agents that you install from the
IBM Tivoli Monitoring installation image. Agents installed from the
agent installation image do not have this step.
9. Type a program folder to use in your Start menu and click Next. The default
folder is ″IBM Tivoli Monitoring.
10. 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 and the configuration environment is
initialized (indicated by a pop-up window), a configuration window is
displayed.
11. Click Next to begin configuring the default values for your agent.
12. Specify the default values for any IBM Tivoli Monitoring agent to use when
they communicate with the monitoring server.
a. If the agent must cross a firewall to access the monitoring server, select
Connection must pass through firewall.

Chapter 5. Installing IBM Tivoli Monitoring 65

 b. Identify the type of protocol that the agent uses to communicate with the
monitoring server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or
SNA. You can specify three methods for communication - this enables you
to set up backup communication methods. If the method you have
identified as Protocol 1 fails, Protocol 2 is used.
Click OK.
13. Complete the following fields to define the communications between agents
and the monitoring server.
Table 22. Communications protocol settings
Field Description
IP.UDP Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.
Local LU Alias The LU alias.

Note: Do not select Optional Secondary TEMS Connection. You can set up
the failover support for agents after install, as described in
“Configuring failover support” on page 110.
14. Click Finish to complete the installation.
15. Open the Manage Tivoli Enterprise Monitoring Services utility (if it does not
open automatically) to see if the monitoring agent has been configured and
started. If ″Yes″ is in the Configured column, the agent has been configured
and started during the installation process.
16. 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:

66 IBM Tivoli Monitoring: Installation and Setup Guide

 a. Click Configure Using Defaults.
b. Complete any windows requiring information by using the agent-specific
configuration settings in the user’s guide for your agent.

Note: Do not enter non-ASCII characters on any of these windows.

Entering characters from other character sets has unpredictable
results.
c. Repeat this step as necessary to create monitoring agent instances for each
application instance you want to monitor.

Linux or UNIX: Installing a monitoring agent

Use the following steps to install and configure a monitoring agent on a Linux or
UNIX computer.
Table 23. Steps for installing a monitoring agent on Linux or UNIX
Steps Where to find information
Install the monitoring agent. “Installing the monitoring agent”
Configure the monitoring agent. “Configuring the monitoring agent” on page
68

Some agents require additional,

agent-specific configuration parameters. See
the agent documentation for the specific
agents that you are configuring.
Change the file permissions for files on the “Changing the file permissions for agents”
computer where you installed the agent. on page 69
Start the monitoring agent. “Starting the monitoring agents” on page 70

Installing the monitoring agent

Use the following steps to install a monitoring agent on a Linux or 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) or type the full path to a different
directory.
3. If the installation directory does not already exist, you are asked if you want
to create it. Type y to create this directory 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 (requires TEMS).
3) Exit install.

Please enter a valid number:

Note: This prompt might vary depending on the installation image from
which you are installing.
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 in and press Enter.
6. Press Enter to display the agreement.

Chapter 5. Installing IBM Tivoli Monitoring 67

 7. Type 1 to accept the agreement and press Enter.
8. Type a 32 character encryption key and press Enter. This key should be the
same as the key that was used during the installation of the monitoring server
to which this monitoring agent connects.

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 need to provide the encryption key.
A numbered list of available operating systems is displayed.
9. Type the number for the operating system that you are installing on. 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.
12. Type y to confirm the installation.
The installation begins.
13. After all of the components are installed, you are asked 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
product code ″ux″; for Linux, use ″lz″. See Appendix D, “IBM Tivoli Product
Codes,” on page 185 for a list of agent product codes.
2. Press Enter when you are asked if the agent connects to a monitoring server.
3. Type the host name for the monitoring server.
4. Type the protocol that you want to use to communicate with the monitoring
server. You have four choices: ip, sna, ip.spipe, or ip.pipe. Press Enter to accept
the default protocol (IP.PIPE).
5. If you want to set up a backup protocol, enter that protocol and press Enter. If
you do not want to use backup protocol, press Enter without specifying a
protocol.
6. Depending on the type of protocol you specified, provide the following
information when prompted:
Table 24. UNIX monitoring server protocols and values
Protocol Value Definition
IP.UDP IP Port Number The port number for the
monitoring server. The
default is 1918.

68 IBM Tivoli Monitoring: Installation and Setup Guide

Table 24. UNIX monitoring server protocols and values (continued)
Protocol Value Definition
SNA Net Name The SNA network identifier
for your location.
LU Name The LU name for the
monitoring server. This LU
name corresponds to the
Local LU Alias in your SNA
communications software.
Log Mode The name of the LU6.2
LOGMODE. The default
value is ″CANCTDCS.″
IP.PIPE IP.PIPE Port Number The port number for the
monitoring server. The
default is 1918.
IP.SPIPE IP.SPIPE Port Number The port number for the
monitoring server. The
default is 3660.

7. Press Enter to not specify the name of the KDC_PARTITION.

8. Press Enter when you are asked if you want to configure the connection to a
secondary monitoring server. The default value is no.
9. Press Enter to accept the default for the Optional Primary Network Name
(none).

Changing the file permissions for agents

If you used a non-root user to install a monitoring agent on a UNIX computer, the
file permissions are initially set to a low level. Run the following procedure to
change these file permissions:
1. Log in to the computer as root, or become the root user by running the su
command.
2. Create a new group (such as "itmusers") to own all of the files in the IBM
Tivoli Monitoring installation directory.
For Linux, Solaris, and HP-UX computers, run the following command:
groupadd itmusers
For an AIX computer, run the following command:
mkgroup itmusers
3. Run the following command to ensure that the CANDLEHOME environment
variable correctly identifies IBM Tivoli Monitoring installation directory:
echo $CANDLEHOME

Running the following steps in the wrong directory can change the
permissions on every file in every file system on the computer.
4. Change to the directory returned by the previous step:
cd $CANDLEHOME
5. Run the following command to ensure that you are in the correct directory:
pwd
6. Run the following commands:
chgrp -R itmusers .
chmod -R o-rwx .

Chapter 5. Installing IBM Tivoli Monitoring 69

 7. Run the following command to change the ownership of additional agent
files:
bin/SetPerm
8. If you want to run the agent as a particular user, add the user to the itmusers
group. To do this, edit the /etc/group file and ensure that the user is in the
list of users for the itmusers group.
For example, if you want to run the agent as user test1, ensure that the
following line is in the /etc/group file:
itmusers:x:504:test1
9. Run the su command to switch to the user that you want to run the agent as
or log in as that user.
10. Start the agent as described in “Starting the monitoring agents.”

Starting the monitoring agents

You can either start all agents running on a computer or start individual agents by
using the product codes.

To start all monitoring agents, run the following command:

./itmcmd agent start all

To start specific agents, run the following command:

./itmcmd agent start pc pc pc

where pc is the product code for the agent that you want to start. See Appendix D,
“IBM Tivoli Product Codes,” on page 185 for a list of agent product codes.

Installing Tivoli Enterprise Portal desktop client

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

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 in the \WINDOWS
subdirectory on the installation media.
2. Click Next on the welcome window.
3. Accept the software license by clicking Accept.
4. Read the information regarding potentially missing prerequisites and click
Next.
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 should be the same as what 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.
7. Select Tivoli Enterprise Portal client.
8. If you want to view IBM Tivoli Enterprise Console events through the Tivoli
Enterprise Portal, expand Tivoli Enterprise Portal client and ensure that
Tivoli Enterprise Console GUI Integration is selected.

70 IBM Tivoli Monitoring: Installation and Setup Guide

 9. Click Next.
If you are installing the portal client on a computer that already has a
monitoring server installed, the next step is to populate the depot. If you do
not have a monitoring server on this computer, this step is skipped.
10. Specify the program folder name and click Next.
11. Confirm the installation details and click Next to start the installation.
After the installation is complete, a configuration window is displayed.
12. Click Next to configure the connection to the portal server, the connection to
the monitoring server, and to launch Manage Tivoli Enterprise Monitoring
Services.
13. Type the host name of the portal server and click OK.
14. Configure the default connection to the monitoring server:
a. If the agent must cross a firewall to access the monitoring server, select
Connection must pass through firewall.
b. Identify the type of protocol that the agent uses to communicate with the
hub monitoring server.
Click OK.
15. Complete the following fields for the monitoring server.
Table 25. Communications protocol settings
Field Description
IP.UDP Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server. The default port is 1918.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.
Local LU Alias The LU alias.

16. Click Finish.

Chapter 5. Installing IBM Tivoli Monitoring 71

 Linux: Installing the desktop client
Use the following steps to install and configure the portal desktop client on a
Linux computer:
Table 26. 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 73

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) or type the full path to a different
directory.
3. If the installation directory does not already exist, you are asked if you want
to create it. Type y to create this directory 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 (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 in and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type an encryption key to use and press Enter. This key should be the same
key as that 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 that you are installing on. 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 (for example, 5). 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 asked whether you want to
install components for a different operating system. Type y and press Enter.
14. Type the number that corresponds to ″Tivoli Enterprise Portal Desktop
support″ and press Enter.

72 IBM Tivoli Monitoring: Installation and Setup Guide

 15. Type y to confirm and press Enter.
A list of the components to install is displayed.
16. Type the number that corresponds to "all of the above" and press Enter.
17. Type y to confirm the installation.
The installation begins.
18. After all of the components are installed, you are asked 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 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 /opt/IBM/ITM/bin directory (or the /bin subdirectory
where you installed the product).
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 asked if you want 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 desktop client
All agents require that application support files containing agent-specific
information be installed into the monitoring server, portal server, and portal
desktop client.

When you installed the monitoring server, portal server, and portal desktop client
using the instructions in this chapter, the support for agents available on the IBM
Tivoli Monitoring installation CD was installed. Now you must return to each
component and install the application support for any other agents that you have
installed (the Database, Messaging and Collaboration, and other application
agents).

Use the instructions in the following sections to install application support:

v “Installing application support on monitoring servers”
v “Installing application support on the Tivoli Enterprise Portal Server” on page 77
v “Installing application support on the Tivoli Enterprise Portal desktop client” on
page 79

Installing application support on monitoring servers

Use the following sections to install application support on each monitoring server
(hub and remote) in your environment:
v “Windows: Installing application support on a monitoring server” on page 74
v “Linux or UNIX: Installing application support on a monitoring server” on page
76

Chapter 5. Installing IBM Tivoli Monitoring 73

 Windows: Installing application support on a monitoring server
Use the following steps to install required application support on Windows
monitoring servers.

Note: The monitoring server is stopped during this process.

1. In the /WINDOWS subdirectory on the agent installation media, double-click
the setup.exe file to launch the agent installation.
2. 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 the
following window:

Figure 7. Installing application support

Click Modify and skip to step 4.

3. Click Accept on the software license.
4. If you see a message regarding installed versions being newer than the agent
installation, click OK to ignore this message.
5. Select Tivoli Enterprise Monitoring Server and click Next.

Note: If you have other components installed on the same computer, such as
the desktop client, also select those components to install the
component-specific application support.
6. If you want to add the agent to the deployment depot, select the agent and
click Next.
7. Review the installation summary details. Click Next to start the installation.
After installation is complete, a configuration window is displayed. By
default, all the components you just installed are selected for configuration.
Clear any components that you have already installed on this computer, such
as the monitoring server.
8. Click Next on the configuration window.
9. Specify the default values for any IBM Tivoli Monitoring agent to use when
they communicate with the monitoring server and click OK.
10. Identify the default communications protocols for agents to use to connect to
the monitoring server. See “Installing monitoring agents” on page 64 for a list
of these fields. Click OK to continue.
The next configuration step is to add application support to the monitoring
server, such as the workspaces and situations for agents.

74 IBM Tivoli Monitoring: Installation and Setup Guide

11. Specify the location of the monitoring server to which to add application
support. You have two choices:
v This computer
v On a different computer
Click OK.
12. Because the monitoring server is not currently running, it is started
automatically before the process begins. Click OK on the message telling you
this.
13. Select the data that you want to add to the monitoring server. By default, all
available application support is selected. Click OK.
14. Click Next on the message that provides information about the process of
adding application support.
15. Specify the default values for any IBM Tivoli Monitoring agent to use when
they communicate with the monitoring server.
a. If the agent must cross a firewall to access the monitoring server, select
Connection must pass through firewall.
b. Identify the type of protocol that the agent uses to communicate with the
monitoring server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or
SNA. You can specify three methods for communication - this enables you
to set up backup communication methods. If the method you have
identified as Protocol 1 fails, Protocol 2 is used.
Click OK.
16. Complete the following fields to define the communications between agents
and the monitoring server.
Table 27. Communications protocol settings
Field Description
IP.UDP Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.

Chapter 5. Installing IBM Tivoli Monitoring 75

 Table 27. Communications protocol settings (continued)
Field Description
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.
Local LU Alias The LU alias.

17. Click Finish to close the installation wizard.

Linux or UNIX: Installing application support on a monitoring

server
Use the following steps to install the support on a UNIX or Linux monitoring
server:
1. Stop the monitoring server by running the following command:
./itmcmd server stop tems_name
2. Run the following command from the installation media:
./install.sh
3. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory you used.
4. The following prompt is displayed:
Select one of the following:
11) Install products to the local host.
2) Install products to depot for remote deployment (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 in and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type a 32 character encryption key and press Enter. This key should be the
same as the key that was used during the installation of the monitoring
server.

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 does not occur.
A numbered list of available operating systems and installation components is
displayed.
9. Type the number that corresponds to ″Tivoli Enterprise Monitoring Server
support″ and press Enter.
10. Type y to confirm and press Enter.
A list of the components to install is displayed.
11. Type the number that corresponds to ″all of the above″ and press Enter.
12. Type y to confirm the installation.
The installation begins.

76 IBM Tivoli Monitoring: Installation and Setup Guide

 13. After all of the components are installed, you are asked whether you want to
install components for a different operating system. Type n and press Enter.
14. Start the monitoring server by running the following command:
./itmcmd server start tems_name
15. Run the following command to activate the application support on the
monitoring server:
./itmcmd support -t tems_name pc

where tems_name is the name of the monitoring server and pc is the product
code for the agent.
To view the product code for the application 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 only the support 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

ud is the product code for the DB2 agent.

16. Stop the monitoring server by running the following command:
./itmcmd server stop tems_name
17. Run the following command to restart the monitoring server:
./itmcmd server start tems_name

Installing application support on the Tivoli Enterprise Portal

Server
Use the following sections to install application support on your portal server:
v “Windows: Installing application support on a portal server”
v “Linux: Installing application support on a portal server” on page 78

Windows: Installing application support on a portal server

Use the following steps to install required application support on a Windows
portal server
1. Open Manage Tivoli Enterprise Monitoring Services.
2. Stop the portal server by right-clicking it and clicking Stop.
3. In the /WINDOWS subdirectory on the agent installation media, double-click
the setup.exe file to launch the agent installation.
4. 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 the
following window:

Chapter 5. Installing IBM Tivoli Monitoring 77

 Figure 8. Installing application support

Click Modify and skip to step 6.

5. Click Accept on the software license.
6. If you see a message regarding installed versions being newer than the agent
installation, click OK to ignore this message.
7. Select Tivoli Enterprise Portal Server and click Next.

Note: If you have other components installed on the same computer, such as
the desktop client, also select those components to install the
component-specific application support.
8. Click Next. Do not select any agents.
9. Review the installation summary details. Click Next to start the installation.
After installation is complete, a configuration window is displayed. By
default, all the components you just installed are selected for configuration.
Clear any components that you have already installed and configured on this
computer.
10. Click Next on the configuration window.
11. Type the host name for the portal server and click Next.
12. Click Finish to complete the installation wizard.
13. Restart the portal server.

Linux: Installing application support on a portal server

Use the following steps to install the support on a Linux portal server:

Note: Stop the portal server before performing this procedure.

1. Run the following command from the installation media:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory you used.
3. 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 (requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

78 IBM Tivoli Monitoring: Installation and Setup Guide

 4. Type the number that corresponds to the language in which you want to
display the software license agreement in and press Enter.
5. Press Enter to display the agreement.
6. Type 1 to accept the agreement and press Enter.
7. Type a 32 character encryption key and press Enter. This key should be the
same as the key that was used during the installation of the monitoring
server.

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 does not occur.
A numbered list of available operating systems and installation components is
displayed.
8. Type the number that corresponds to ″Tivoli Enterprise Portal Browser Client
support″ and press Enter.
9. Type y to confirm and press Enter.
A list of the components to install is displayed.
10. Type the number that corresponds to ″all of the above″ and press Enter.
11. Type y to confirm the installation.
The installation begins.
12. When you are asked whether you want to install components for a different
operating system, type y and press Enter.
13. Type the number that corresponds to "Tivoli Enterprise Portal Server support"
and press Enter.
14. Type y to confirm and press Enter.
A list of the components to install is displayed.
15. Type the number that corresponds to ″all of the above″ and press Enter.
16. Type y to confirm the installation.
The installation begins.
17. After all of the components are installed, you are asked whether you want to
install components for a different operating system. Type n and press Enter.
18. Stop the portal server by running the following command:
./itmcmd agent stop cq
19. Run the following command to configure the portal server with the new agent
information:
./itmcmd config -A cq

Complete the configuration as prompted. For information regarding

configuring the portal server, see “Configuring the portal server on Linux” on
page 62.
20. Restart the portal server by running the following command:
./itmcmd agent start cq

Installing application support on the Tivoli Enterprise Portal

desktop client
Use the following sections to install application support on each computer where
you are running the desktop client:
v “Windows: Installing application support on a desktop client” on page 80
v “Installing application support on a Linux desktop client” on page 80

Chapter 5. Installing IBM Tivoli Monitoring 79

 Windows: Installing application support on a desktop client
Use the following steps to install required application support on a Windows
desktop client:

Note: Stop the desktop client before performing this procedure.

1. In the /WINDOWS subdirectory on the agent installation media, double-click
the setup.exe file to launch the agent installation.
2. 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 the
following window:

Figure 9. Installing application support

Click Modify and skip to step 4.

3. Click Accept on the software license.
4. If you see a message regarding installed versions being newer than the agent
installation, click OK to ignore this message.
5. Select Tivoli Enterprise Portal Desktop Client and click Next.
6. Click Next. Do not select any agents.
7. Review the installation summary details. Click Next to start the installation.
After installation is complete, a configuration window is displayed. By
default, all the components you just installed are selected for configuration.
Clear any components that you have already installed and configured on this
computer.
8. Click Next on the configuration window.
9. Type the host name for the portal server and click Next.
10. Click Finish to complete the installation wizard.

Installing application support on a Linux desktop client

Use the following steps to install the support on a Linux desktop client:

Note: Stop the desktop client before performing this procedure.

1. Run the following command from the installation media:
./install.sh
2. When prompted for the IBM Tivoli Monitoring home directory, press Enter to
accept the default (/opt/IBM/ITM) or type the full path to the installation
directory you used.

80 IBM Tivoli Monitoring: Installation and Setup Guide

 3. 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 (requires TEMS).
3) Exit install.

Please enter a valid number:

Type 1 to start the installation and press Enter.

4. Type the number that corresponds to the language in which you want to
display the software license agreement in and press Enter.
5. Press Enter to display the agreement.
6. Type 1 to accept the agreement and press Enter.
7. Type a 32 character encryption key and press Enter. This key should be the
same as the key that was used during the installation of the monitoring
server.

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 does not occur.
A numbered list of available operating systems and installation components is
displayed.
8. Type the number that corresponds to ″Tivoli Enterprise Portal Desktop Client
support″ and press Enter.
9. Type y to confirm and press Enter.
A list of the components to install is displayed.
10. Type the number that corresponds to ″all of the above″ and press Enter.
11. Type y to confirm the installation.
The installation begins.
12. After all of the components are installed, you are asked whether you want to
install components for a different operating system. Type n and press Enter.
13. Run the following command to configure the portal client with the new agent
information:
./itmcmd config -A cj

Complete the configuration as prompted. For information regarding

configuring the desktop client, see “Configuring the portal desktop client on
Linux” on page 73.

Installing the language packs

By default, IBM Tivoli Monitoring is enabled for the English language. If you want
to use the product in another language, you must install the translated language
pack. The language packs are available on the language support image for each
component.

Before you can install a language pack, you must install the component in English.

Use the following steps to install a language pack:

1. In the directory where you extracted the language pack installation image,
launch the installation program as follows:
On Windows, double-click the setup.exe file.

Chapter 5. Installing IBM Tivoli Monitoring 81

 On Linux and UNIX, run the following command:
./setup<operating_system>.bin

If you want to perform a console installation on Linux or UNIX (instead of a

GUI installation), add the -console parameter to the above command.
2. Click Next on the Welcome window.
3. Select I accept the terms in the license agreement and click Next.
4. Type the directory where you installed the component in the Directory Name
field. This directory must match the installation where you installed the
component or the installation of the language pack will fail. Click Next.
5. Select the language that you want to install on this computer and click Next.
6. Review the installation summary and click Next.
7. If you are installing the language pack on the computer where you have
installed the portal client (client or browser), a message telling you to restart
the portal client is displayed. Click Next.
8. Click Finish.
.

Starting the Tivoli Enterprise Portal client

After you have successfully installed and configured all the components of your
IBM Tivoli Monitoring environment, you can verify the installation and
configuration by launching the Tivoli Enterprise Portal to view monitoring data.
You can access the Tivoli Enterprise Portal through two clients:
v “Starting the desktop client”
v “Starting the browser client”

Your monitoring server and portal server must be running for the portal client to
start successfully.

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. If your environment requires user validation, type the 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.
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 computer where the Tivoli Enterprise Portal
Server and browser component are installed.
3. Click Yes on the Warning - Security window.

82 IBM Tivoli Monitoring: Installation and Setup Guide

4. Type the user name in the login field. The default user name is ″sysadmin.″
5. Click OK.

After you start the browser client, change the memory settings for the Java Plug-in
used by the Tivoli Enterprise Portal:
1. Open the Windows Control Panel and double-click the Java Plug-in used by
Tivoli Enterprise Portal.
2. In the Advanced page, enter -Xms64m -Xmx256m in the Java Runtime Parameters
field and click Apply.
3. Log off the portal and then log in again.

Chapter 5. Installing IBM Tivoli Monitoring 83

84 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 6. Installing the IBM Tivoli Enterprise Console event
synchronization
If you use Tivoli Enterprise Console to monitor events from other sources in your
environment, you can configure IBM Tivoli Monitoring to forward situation events
to the Tivoli Enterprise Console event server (referred to as the event server), in
addition to viewing events on the event server through the Tivoli Enterprise Portal.

If you want to forward situation events to and view updates from Tivoli Enterprise
Console in the Tivoli Enterprise Portal, you need to install the event
synchronization component on the event server. However, if you just want to view
Tivoli Enterprise Console events through the portal, you do not need to install the
event synchronization. In this case, select an Event Group and not dynamic filter
as the filter type.

To view events through the Tivoli Enterprise Console view in Tivoli Enterprise
Portal, see the online help or the IBM Tivoli Monitoring User’s Guide for information
about adding the event viewer to your workspace.

To filter the types of events that are displayed in the Tivoli Enterprise Console
view, see the IBM Tivoli Monitoring Administrator’s Guide.

The following table provides an overview of the steps required to install and
configure the event synchronization:
Table 28. Tivoli Enterprise Console event synchronization installation and configuration
steps
Step Where to find information
Plan the deployment of your integration. “Planning the deployment of your IBM
Tivoli Enterprise Console integration” on
page 86
Gather information required during the “Information to gather before you begin” on
installation and configuration processes. page 89
Install the event synchronization on your “Installing event synchronization on your
event server. event server” on page 89
Install monitoring agent .baroc files on the “Installing monitoring agent .baroc files on
event server. the event server” on page 101
Configure your monitoring server to “Configuring your monitoring server to
forward events to Tivoli Enterprise Console. forward events” on page 102
Start and stop event synchronization on the “Starting and stopping the Situation Update
event server. Forwarder process” on page 103
Modify the configuration of event “Changing the configuration of the event
synchronization as your monitoring needs synchronization on the event server” on
change. page 103
Define additional monitoring servers to the “Defining additional monitoring servers to
event server. the event server” on page 104
Change the default TCP/IP settings if it is “Changing the TCP/IP timeout setting on
taking a long time to forward events back to your event server” on page 104
the monitoring server.

© Copyright IBM Corp. 2005 85

Planning the deployment of your IBM Tivoli Enterprise Console
integration
The following scenarios illustrate the various ways to forward situation events
from one or more monitoring servers to one or more event servers.

One or more hub monitoring servers and a single event server

You can configure one or more monitoring servers to forward situation events to
an event server. Figure 10 shows multiple hub monitoring servers that are
configured to forward situation events to the same event server. The event server
sends situation updates based on Tivoli Enterprise Console rules and operator
actions back to the hub monitoring server that is associated with that situation.

Figure 10. One or more hub monitoring servers connecting to a single event server

86 IBM Tivoli Monitoring: Installation and Setup Guide

 A single hub monitoring server and multiple event servers
Figure 11 shows a single hub monitoring server that is configured to forward
situation events to multiple event servers. The event servers send situation updates
based on Tivoli Enterprise Console rules and operator actions back to the hub
monitoring server.

For this configuration, you must install the Tivoli Enterprise Console event
synchronization component on each event server, and you must specify each
situation event and the event server to which the situation event is forwarded. You
cannot forward the same situation event to more than one event server. For
information about forwarding events, see the IBM Tivoli Monitoring Administrator's
Guide.

Tivoli Enterprise Console server Tivoli Enterprise Console server

Tivoli Enterprise Monitoring server

(Hub monitoring server)
Figure 11. Single hub monitoring server and multiple event servers

Multiple hub monitoring servers and multiple event servers in

a hub and spoke configuration
Figure 12 on page 88 shows multiple hub monitoring servers that are configured to
forward situation events to an event server that is connected to a hub event server.
The hub event server sends situation updates based on Tivoli Enterprise Console

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 87

 rules and operator actions back to the hub monitoring server that is associated
with that situation.

Figure 12. Multiple hub monitoring servers and multiple event servers in a hub and spoke configuration

Note: This graphic is intended to be an example of one possible scaled

configuration for the IBM Tivoli Monitoring and Tivoli Enterprise Console
integration. The procedures in this chapter do not provide all of the
information needed to set up this sort of configuration.

For this configuration, you must install the Tivoli Enterprise Console event
synchronization component on the hub event server. You must also load the
omegamon.baroc and Sentry.baroc files on the spoke event servers, as described in
“Modifying an existing rule base” on page 100. In addition, you must load each
.baroc file for any monitoring agent generating situations that are forwarded to
spoke event servers, as described in “Installing monitoring agent .baroc files on the
event server” on page 101.

88 IBM Tivoli Monitoring: Installation and Setup Guide

Information to gather before you begin
You need the following information to successfully install and configure event
synchronization between IBM Tivoli Monitoring and IBM Tivoli Enterprise
Console:
v Host names, user IDs, and passwords for the monitoring servers that you want
to receive events from
v Simple Object Access Protocol (SOAP or Web Services) information to send
events to a monitoring server (the URL, the rate to send requests to the server).
By default, all monitoring servers are configured as SOAP servers. If you did not
change this configuration to make it unique for your environment, you can
accept the default values during the installation.
If you did change this configuration, use the SOAP information unique to your
configuration.
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)
Notes:
1. For a Windows event server, any existing rule base that you use 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 returned path includes something like hostname:\Rulebase_directory,

with no drive letter (such as C:\), you must copy the setupwin32.exe file
from the \TEC subdirectory of the IBM Tivoli Monitoring installation image
to the drive where the rule base exists and run the installation from that file.
2. If you are using a Windows event server, if you have any rule base that was
created with an absolute path and that has the Sentry2_0_Base class
imported, you must copy the setupwin32.exe file from the \TEC subdirectory
of the of the IBM Tivoli Monitoring installation image to the drive where the
rule base exists and run the installation from that file.
To determine if you have any rule bases that were created with an absolute
path, run the wrb -lsrb -path command as described in the previous note.
To determine if your rule bases have the Sentry2_0_Base class imported, run
the following command against all of your rule bases:
wrb -lsrbclass rule_base

where rule_base is the name of the rule base.

Installing event synchronization on your event server

There are three methods for installing the event synchronization:
v “Installing from a wizard” on page 90
v “Installing from the command line” on page 93
v “Installing from the command line using a silent install” on page 95

When you install the event synchronization on your event server, the following
changes are made:
v If you select to use an existing rule base, the event synchronization .baroc class
files (omegamon.baroc and Sentry.baroc [if not present]) and the omegamon.rls
rule set file are imported into your existing rule base.

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 89

 Note: If you do not want to modify your existing rule base during the
installation, you can choose to create a new rule base at install time and
then manually import the event synchronization class files and rule set
file into your existing rule base. See “Manually importing the event
synchronization class files and rule set” on page 99 for more information.
v For all rule bases that have Sentry.baroc imported, the Sentry2_0_Base class is
updated to define additional integration attributes for the situation events
received from IBM Tivoli Monitoring.
v A new process, Situation Update Forwarder, is installed along with its
supporting binary and configuration files. This process is used to forward
updates to the situation events back to the monitoring server. On Windows, a
Tivoli Situation Update Forwarder service is also created.
Notes:
1. 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 need to run the change user /install command before you run the
installation. This puts the computer into the required ″install″ mode. After the
installation, run the change user /execute command to return the computer to
its previous mode.
2. If you have a UNIX monitoring server, you must configure your TCP/IP
network services in the /etc/hosts file to return the fully qualified host name.
See “Host name for TCP/IP network services” on page 23 for more
information.

Installing from a wizard

Use the following steps to install event synchronization from the installation
wizard:
1. On the event server, launch the event synchronization installation:
On Windows, double-click the setupwin32.exe file in the \TEC subdirectory
on the IBM Tivoli Monitoring installation media.
On Linux or UNIX, change to the /<os_type>/tec subdirectory of the IBM
Tivoli Monitoring installation media, where <os_type> is the operating system
type that corresponds to the installation CD that you are using ("unix" for AIX
and Solaris, "hpux" for HP-UX, "xlinux" for Linux for Intel, and "zlinux" for
Linux for z/OS). Run the following command:
setup<operating_system>.bin

where <operating_system> is the operating system you are installing on. 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. Complete the following fields and click Next:
Table 29. IBM Tivoli Enterprise Console event synchronization configuration fields
Field Description
Name of configuration file The name of the file where event
synchronization configuration information is
stored. The default name is situpdate.conf.

90 IBM Tivoli Monitoring: Installation and Setup Guide

Table 29. IBM Tivoli Enterprise Console event synchronization configuration
fields (continued)
Field Description
Number of seconds to sleep when no new The polling interval, in seconds. The
situation updates minimum value is 1, while the default value
is 3. If there are no situation events, the
Situation Update Forwarder rests for 3
seconds.
Number of bytes to use to save last event Number of bytes that the long running
process will use when it saves the location
of the last event it processes. This value
must be an integer. The minimum (and
default) is 50.
URL of the CMS SOAP Server The URL for the SOAP Server configured on
the computer where the monitoring server is
running. The default value is cms/soap. This
value is used to create the URL to which
IBM Tivoli Enterprise Console sends event
information. For example,
http://hostname:port///cms/soap, where
hostname is the host name of the monitoring
server and port is the port.
Rate for sending SOAP requests to CMS The maximum number of event updates sent
from TEC via web services to the monitoring server at one time. The
minimum (and default) value is 10 events.
Level of debug detail for log The level of information for event
synchronization that will be logged. You
have the following choices:
v Low (default)
v Medium
v Verbose

5. Complete the following information about the files where events will be
written and click Next:
Table 30. IBM Tivoli Enterprise Console event synchronization configuration fields,
continued
Field Description
Maximum size of any single cache file, in The maximum permitted size, in bytes, for
bytes any one event cache file. The minimum (and
default) value is 50000. Do not use commas
when specifying this value (specify 50000
instead of 50,000).
Maximum number of caches files The maximum number of event caches files
at any given time. The minimum value is 2,
while the default value is 10. When this
value is reached, the oldest file is deleted to
make room for a new file.
Directory for cache files to reside The location where event cache files are
located. The default locations are as follows:
v On Windows:
C:\tmp\TME\TEC\OM_TEC\persistence.
v On UNIX:
/var/TME/TEC/OM_TEC/persistence

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 91

 6. Type the following information for each monitoring server with which you
want to synchronize events and click Add. You must specify information for
at least one monitoring server.
Host name
The fully qualified host name for the computer where the monitoring
server is running. This should match the information that will be in
events coming from this monitoring server.
User ID
The user ID to access the computer where the monitoring server is
running.
Password
The password to access the computer.
Confirmation
The password, again.
You can add information for up to 10 monitoring servers in this wizard. If you
want to add additional monitoring servers, do so after install by using the
steps provided in “Defining additional monitoring servers to the event server”
on page 104.
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
If you select to use an existing rule base, the event synchronization .baroc
class files (omegamon.baroc and Sentry.baroc [if not present]) and the
omegamon.rls rule set file are imported into your existing rule base. Also, if
Sentry.baroc has already been imported into the existing rule base, the
Sentry2_0_Base class is extended to define additional integration attributes for
the situation events from IBM Tivoli Monitoring.
9. If you are creating a new rule base, type the name for the rule base you want
to create and the path to where the new rule base will be located. There is no
default location; you must specify a location.
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 only available if you are creating a new rule base.
12. Click Next.
13. Click Next on the pre-installation summary panel.
The installation begins.
14. When the installation and configuration steps are finished, a message telling
you to stop and restart the event server is displayed. Click OK.
15. 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.

You must stop and restart the event server for these changes to take effect.

92 IBM Tivoli Monitoring: Installation and Setup Guide

Installing from the command line
Use the following steps to install the event synchronization from the command line
on your event server:
1. Run the following command to launch the installation:
On Windows:
setupwin32.exe -console
On UNIX:
setup<operating_system>.bin -console

where <operating_system> is the operating system you are installing on. For
example, run the following command on an AIX computer:
setupAix.bin -console
The following prompt is displayed:
Press 1 for Next, 3 to Cancel or 4 to Redisplay [1]
2. Type 1 to start the installation and press Enter.
The following prompt is displayed:
Software Licensing Agreement:
Press Enter to display the license agreement on your screen. Please
read the agreement carefully before installing the Program. After
reading the agreement, you will be given the opportunity to accept it
or decline it. If you choose to decline the agreement, installation
will not be completed and you will not be able to use the Program.
3. Press Enter to display the software license agreement.
4. Type 1 and press Enter to accept the license.
The following prompt is displayed:
Press 1 for Next, 2 for Previous, 3 to Cancel, or 4 to Redisplay [1]
5. Type 1 and press Enter to continue.
The following prompt is displayed:
Name of configuration file [situpdate.conf]
6. Press Enter to use the default configuration file, situpdate.conf. If you want to
use a different configuration file, type the name and press Enter.
The following prompt is displayed:
Number of seconds to sleep when no new situation updates [1]
7. Type the number of seconds that you want to use for the polling interval. The
default value is 3, while the minimum value is 1. Press Enter.
The following prompt is displayed:
Number of bytes to use to save last event [50]
8. Type the number of bytes to use to save the last event and press Enter. The
default and minimum value is 50.
The following prompt is displayed:
URL of the CMS SOAP server [cms/soap]
9. Type the URL for the monitoring server SOAP server and press Enter. The
default value is cms/soap (which you can use if you set up your monitoring
server using the defaults for SOAP server configuration).
The following prompt is displayed:
Rate for sending SOAP requests to CMS from TEC via Web Services [10]
10. Type maximum number of event updates to send to the monitoring server at
one time and press Enter. The default and minimum value is 10.
The following prompt is displayed:

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 93

 Level of debug for log

[x] 1 low
[ ] 2 med
[ ] 3 verbose

To select an item enter its number, or enter 0 when you are finished: [0]
11. Type the level of debugging that you want to use and press Enter. The default
is Low, indicated by an x next to Low.
12. Type 0 when you have finished and press Enter.
The following prompt is displayed:
Press 1 for Next, 2 for Previous, 3 to Cancel, or 4 to Redisplay [1]
13. Type 1 and press Enter to continue.
The following prompt is displayed:
Maximum size of any single cache file, in bytes [50000]
14. Type the maximum size, in bytes, for the cache file and press Enter. The
default is 50000. Do not use commas (,) when specifying this value.
The following prompt is displayed:
Maximum number of cache files [10]
15. Type the maximum number of cache files to have at one time and press Enter.
The default is 10, while the minimum is 2.
On Windows, the following prompt is displayed:
Directory for cache files to reside [C:/tmp/TME/TEC/OM_TEC/persistence]
On UNIX, the following prompt is displayed:
Directory for cache files to reside [/var/TME/TEC/OM_TEC/persistence]
16. Type the directory for the cache files and press Enter. The default directory on
Windows is C:\tmp\TME\TEC\OM_TEC\persistence; on UNIX,
/var/TME/TEC/OM_TEC/persistence.
The following prompt is displayed:
Press 1 for Next, 2 for Previous, 3 to Cancel, or 4 to Redisplay [1]
17. Type 1 and press Enter to continue.
18. The following prompt is displayed:
--- Tivoli Enterprise Monitoring Server 1 ---

Host name []

Type the fully qualified host name for the computer where the monitoring
server is running. This should match the information that will be in events
coming from this monitoring server. Press Enter.
The following prompt is displayed:
User ID []
19. Type the user ID to use to access the computer where the monitoring server is
running and press Enter.
The following prompt is displayed:
Password:
20. Type the password to access the computer and press Enter.
The following prompt is displayed:
Confirmation:
21. Type the password again to confirm it and press Enter.
The following prompt is displayed:

94 IBM Tivoli Monitoring: Installation and Setup Guide

 --- Tivoli Enterprise Monitoring Server 2 ---

Host name []
22. Repeat steps 18 to 21 for each monitoring server for which you want to
receive events on this event server.
When you have provided information for all the monitoring servers and you
specified information for less than 10 monitoring servers, press Enter to move
through the remaining fields defining additional monitoring servers. Do not
specify any additional monitoring server information.
23. When you see the following prompt, type 1 and press Enter to continue:
Press 1 for Next, 2 for Previous, 3 to cancel or 4 to Redisplay [1]
The following prompt is displayed:
[x] 1 - Create a new rulebase (name and path required)
[ ] 2 - Use Existing Rulebase (path is optional)

To select an item, enter its number, or press 0 when you are finished: [0]
24. Type 1 to create a new rule base or 2 to use an existing rule base. Press Enter.
25. Type 0 when you are finished and press Enter.
26. If you are creating a new rule base, the following prompt is displayed:
Rulebase Name []

type the name for the rule base and press Enter.
The following prompt is displayed:
Rulebase Path []
27. If you are creating a new rule base, type the path for the new rule base and
press Enter.
28. If you are using an existing rule base, the following prompt is displayed:
Rulebase Name []

Type the name of the rule base and press Enter.

29. If you are creating a new rule base, the following prompt is displayed:
Existing rulebase name to import: []

If you want to import an existing rule base into the new rule base, type the
name of the existing rule base and press Enter.
The following prompt is displayed:
Press 1 for Next, 2 for Previous, 3 to Cancel, or 4 to Redisplay [1]
30. Type 1 and press Enter to continue.
The event synchronization is installed.
The following prompt is displayed:
Installation and Configuration has completed. Please stop and restart the
Tivoli Enterprise Console Server.

Press 3 to Finish, or 4 to Redisplay [1]

31. Type 3 to finish and press Enter.

You must stop and restart the event server for these changes to take effect.

Installing from the command line using a silent install

Use the following steps to install the event synchronization using a silent
installation from the command line on your event server. This installation method
runs silently, so you will not see status messages during the actual installation.
Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 95
 1. Run the following command to generate the configuration file:
On Windows:
setupwin32.exe -options-template filename

where filename is the name of the configuration file to create, for example,
es_silentinstall.conf.
On UNIX:
setup<operating_system>.bin -options-template filename

where <operating_system> is the operating system you are installing on. For
example, run the following command on an AIX computer:
setupAix.bin -options-template filename
2. Edit the output file to specify the following values.
Notes:
a. Remove the pound signs (###) from the beginning of any value that you
want to specify.
b. Do not enclose any values in quotation marks (").
c. You must specify the following values:
v configInfoPanel2.fileLocn
v Information for at least one monitoring server (the
cmdSvrsPnlNotGuiMode.hostname1, cmdSvrsPnlNotGuiMode.userID1,
cmdSvrsPnlNotGuiMode.pswd1, and
cmdSvrsPnlNotGuiMode.retypePswd1 values)
v rulebasePanel.chooseNewOrExistingRB
v rulebasePanel.rbName
If you are creating a new rule base, rulebasePanel.rbPath is also required.
If you do not specify any of the other values, the default values are used.
d. For your monitoring servers, use the cmdSvrsPnlNotGuiMode.<value>
values.
e. If you specify values, ensure that the value you specify meets the minimum
required values. Otherwise, the installation stops and an error is written to
the log file.
Table 31. IBM Tivoli Enterprise Console event synchronization configuration values
Value Description
configInfoPanel.filename The name of the file where event
synchronization configuration information is
stored. The default file name is
situpdate.conf.
configInfoPanel.pollingInt The polling interval, in seconds. The
minimum value is 1, while the default value
is 3. If there are no situation events, the
process that forwards events to IBM Tivoli
Enterprise Console rests for 3 seconds.
configInfoPanel.crcByteCnt Number of bytes that the long running
process will use when it saves the location
of the last event it processes. This value
must be an integer. The minimum (and
default) is 50.

96 IBM Tivoli Monitoring: Installation and Setup Guide

Table 31. IBM Tivoli Enterprise Console event synchronization configuration
values (continued)
Value Description
configInfoPanel.cmsSoapURL The URL for the SOAP Server configured on
the computer where the monitoring server is
running. The default value is cms/soap. This
value is used to create the URL to which
IBM Tivoli Enterprise Console sends event
information. For example,
http://hostname:port///cms/soap, where
hostname is the host name of the monitoring
server and port is the port.
configInfoPanel.bufFlushRate The maximum number of event updates sent
to the monitoring server at one time. The
minimum (and default) value is 10 events.
configInfoPanel.logLevel The level of information for event
synchronization that is logged. You have the
following choices:
v Low (default)
v Medium
v Verbose
configInfoPanel2.filesize The maximum permitted size, in bytes, for
any one event cache file. The minimum (and
default) value is 50000. Do not use commas
when specifying this value (50,000 instead of
50000).
configInfoPanel2.fileNumber The maximum number of event caches files
at any given time. The minimum value is 2,
while the default value is 10. When this
value is reached, the oldest file is deleted to
make room for a new file.
configInfoPanel2.fileLocn The location where event cache files are
located. The default locations are as follows:
v On Windows:
C:\tmp\TME\TEC\OM_TEC\persistence.
v On UNIX:
/var/TME/TEC/OM_TEC/persistence
cmsSvrsPnlNotGuiMode.hostname# The host name of each monitoring server
Note: The pound sign (#) stands for a that will send events to the event server.
number between 1 and 10. For example,
"hostname1, hostname2."
cmsSvrsPnlNotGuiMode.userID# The user ID for the monitoring server,
identified in hostname#, to use to access the
computer where the monitoring server is
running.
cmsSvrsPnlNotGuiMode.pswd# The password for the user ID used to access
the computer where the monitoring server is
running.
cmsSvrsPnlNotGuiMode.retypePswd# The password confirmation for the user ID.
rulebasePanel.chooseNewOrExistingRB Specifies whether you are going to create a
new rule base or use an existing rule base.
Specify either new or existing.
rulebasePanel.rbName The name of the rule base (existing or new).

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 97

 Table 31. IBM Tivoli Enterprise Console event synchronization configuration
values (continued)
Value Description
rulebasePanel.rbPath The path for the new rule base. There is no
default location - you must specify a path.
rulebasePanel.fromRB If you are creating a new rule base, identify
any existing rule bases that you want to
import into the new rule base.

3. Save the file.

4. Run the following command:
On Windows:
setupwin32.exe -options filename -silent

where filename is the name of your configuration file.

On UNIX:
setup<operating_system>.bin -options filename -silent

where <operating_system> is the operating system you are installing on. For
example, on AIX, run the following command:
setupAix.bin -options filename -silent

You must stop and restart the event server for these changes to take effect.

When installation is complete, the results are written to the

itm_tec_event_sync_install.log file. On UNIX, this log file is always created in the
/tmp directory. For Windows, this file is creates in the directory defined by the
%TEMP% environment variable. To determine where this directory is defined for
the current command line window, run the following command:
echo %TEMP%

If you specified the monitoring servers in the silent installation configuration file,
you might consider deleting that file after installation, for security reasons.

If you want to define additional monitoring servers (in addition to the one
required monitoring server), run the following command to add them now:
sitconfsvruser.sh add serverid=server userid=user password=password

where:
serverid=server
The fully qualified host name of the monitoring server.
userid=user
The user ID to access the computer where the monitoring server is
running.
password=password
The password to access the computer.

Repeat this command for each monitoring server.

If you specified your monitoring servers after the installation, you must stop and
restart the Situation Update Forwarder process manually. See “Starting and
stopping the Situation Update Forwarder process” on page 103 for information.

98 IBM Tivoli Monitoring: Installation and Setup Guide

Manually importing the event synchronization class files and
rule set
The event synchronization installation modifies your existing rule base. If you do
not want to permit the installation program to modify your rule base, you can
choose to create a new rule base during the installation and then use one of the
following methods to manually modify your rule base:
v “Creating a new rule base”
v “Creating a new rule base and importing an existing rule base into it”
v “Modifying an existing rule base” on page 100

Before you can run any of the commands in the following sections, you must
source your Tivoli environment by running the following command:

On Windows, run the following command from a command prompt:

C:\Windows\system32\drivers\etc\Tivoli\setup_env.cmd

On Linux or UNIX, run the following command from a shell environment:

. /etc/Tivoli/setup_env.sh

See the IBM Tivoli Enterprise Console Command and Task Reference for more
information about the wrb, wstopesvr, and wstartesvr commands.

Creating a new rule base

Use the following steps to create a new rule base after you install the event
synchronization:
1. Create the new rule base by running the following command:
wrb -crtrb -path <newrb_path> <newrb_name>

where <newrb_path> is the path to where you want to create the new rule base
and <newrb_name> is the name for the new rule base.
2. Import the event synchronization class and rule files into the new rule base.
These class and rule files are located in the new rule base that you created
when you installed the event synchronization. Run the following commands:
wrb -imprbclass <path_to Sentry_baroc_file> <newrb_name>

wrb -imprbclass <path_to_omegamon_baroc_file> <newrb_name>

wrb -imprbrule <path_to_omegamon_rls_file> <newrb_name>

wrb -imptgtrule omegamon EventServer <newrb_name>

3. Compile and load the new rule base by running the following commands:
wrb -comprules <newrb_name>

wrb -loadrb <newrb_name>

4. Stop and restart the event server by running the following commands:
wstopesvr

wstartesvr

Creating a new rule base and importing an existing rule base

into it
Use the following steps to create a new rule base and import an existing rule base
into it:
1. Create the new rule base by running the following command:

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 99

 wrb -crtrb -path <newrb_path> <newrb_name>

where <newrb_path> is the path to where you want to create the new rule base
and <newrb_name> is the name for the new rule base.
2. Import the existing rule base into the new rule base by running the following
commands:
wrb -cprb -overwrite <existing_rbname> <newrb_name>

where <existing_rbname> is the name of the existing rule base that you want to
import.
3. If the existing rule base is an older rule base, you must upgrade the tec.baroc
file to include the TEC_Generic class. Run the following command:
perl $BINDIR/TME/TEC/OM_TEC/bin/upg_tec_baroc.pl <newrb_name>
4. If the rule base already contains a Sentry.baroc file, you must upgrade it with
the event synchronization event class attributes. Run the following command:
perl $BINDIR/TME/TEC/OM_TEC/bin/upg_sentry_baroc.pl
5. If the rule base does not contain a Sentry.baroc file, you must import it from
the rule base you created during event synchronization installation. Run the
following command:
wrb -imprbclass <path_to_Sentry_baroc_file> <newrb_name>

where <path_to_Sentry_baroc_file> is the path to the new rule base that you
created during event synchronization installation.
6. Import the omegamon.baroc and rules file into the rule base from the new rule
base that you created during event synchronization installation. Run the
following commands:
wrb -imprbclass <path_to_omegamon_baroc_file> <newrb_name>

wrb -imprbrule <path_to_omegamon_rls_file> <newrb_name>

wrb -imptgtrule omegamon EventServer <newrb_name>

7. Compile and load the new rule base by running the following commands:
wrb -comprules <newrb_name>

wrb -loadrb <newrb_name>

8. Stop and restart the event server by running the following commands:
wstopesvr

wstartesvr

Modifying an existing rule base

Use the following steps to modify an existing rule base to include the class files
and rule set for the event synchronization:
1. If the existing rule base is an older rule base, you must upgrade the tec.baroc
file to include the TEC_Generic class. Run the following command:
perl $BINDIR/TME/TEC/OM_TEC/bin/upg_tec_baroc.pl <newrb_name>
2. If the rule base already contains a Sentry.baroc file, you must upgrade it with
the event synchronization event class attributes. Run the following command:
perl $BINDIR/TME/TEC/OM_TEC/bin/upg_sentry_baroc.pl
3. If the rule base does not contain a Sentry.baroc file, you must import it from
the rule base you created during event synchronization installation. Run the
following command:
wrb -imprbclass <path_to_Sentry_baroc_file> <newrb_name>

100 IBM Tivoli Monitoring: Installation and Setup Guide

 where <path_to_Sentry_baroc_file> is the path to the new rule base that you
created during event synchronization installation.
4. Import the omegamon.baroc and rules file into the rule base from the new rule
base that you created during event synchronization installation. Run the
following commands:
wrb -imprbclass <path_to_omegamon_baroc_file> <newrb_name>

wrb -imprbrule <path_to_omegamon_rls_file> <newrb_name>

wrb -imptgtrule omegamon EventServer <newrb_name>

5. Compile and load the new rule base by running the following commands:
wrb -comprules <newrb_name>

wrb -loadrb <newrb_name>

6. Stop and restart the event server by running the following commands:
wstopesvr

wstartesvr

Installing monitoring agent .baroc files on the event server

The monitoring server generates Tivoli Enterprise Console events with classes that
are unique to each monitoring agent. Each monitoring agent provides a .baroc file
with the Tivoli Enterprise Console classes that are generated by IBM Tivoli
Monitoring. In order to view this event data in the event console, you must install
these monitoring agent .baroc files on the event server.

After you have added application support for each agent to the monitoring server,
the monitoring agent .baroc files are located in the following directory:
v On Windows, in the <itm_installdir>\cms\TECLIB directory, where
<itm_installdir> is the directory where you installed IBM Tivoli Monitoring.
v On Linux and UNIX, in the <itm_installdir>/tables/<ms_name>/TECLIB
directory, where <itm_installdir> is the directory where you installed IBM Tivoli
Monitoring and <ms_name> is the name of the monitoring server.

Use the following steps to install the monitoring agent .baroc files on the event
server:
1. Copy the monitoring agent .baroc files from the computer where the
monitoring server is installed to a temporary directory on the event server
computer (for example, /tmp). The location of the agent .baroc files is
described above. Do not copy the om_tec.baroc file; this file contains classes
that are duplicates of classes in the omegamon.baroc file.
2. Set up the Tivoli Management Framework environment by running the
following command:
On Windows, run the following command:
C:\WINDOWS\system32\drivers\etc\Tivoli\setup_env.cmd
On Linux and UNIX, run the following command from a shell environment:
. /etc/Tivoli/setup_env.sh
3. For each monitoring agent .baroc file to load into the rule base, run the
following command from the same command prompt:
wrb -imprbclass /tmp/<agent_baroc_file> <rb_name>

where:

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 101
 /tmp/<agent_baroc_file>
Specifies the location and name of the monitoring agent .baroc file. The
example above uses the /tmp directory as the location.
rb_name
The name of the rule base that you are using for event synchronization.
4. Compile and load the rule base by running the following commands
wrb -comprules <rb_name>

wrb -loadrb <rb_name>

5. Stop and restart the event server by running the following commands:
wstopesvr

wstartesvr

When you have loaded each of the agent .baroc files into the rule base and
restarted the event server, the event server is ready to receive and correctly parse
any events it receives from the monitoring server from one of the installed
monitoring agents.

See the IBM Tivoli Enterprise Console Command and Task Reference for more
information about the wrb, wstopesvr, and wstartesvr commands.

Configuring your monitoring server to forward events

Before the monitoring server forwards any situation events to Tivoli Enterprise
Console, you have to enable that forwarding of events. Use the following steps to
enable event forwarding on your monitoring server.

For Windows monitoring servers only, do the following:

1. Open Manage Tivoli Enterprise Monitoring Services.
2. Right-click the monitoring server and click Reconfigure.
3. On the configuration options window, select TEC Event Integration Facility.
4. Click OK and OK.
5. 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
$BINDIR/TME/TEC directory on the event server. If the parameter is
commented out with a pound sign (#), the event server is using port
mapping. If it is not, the event server is using the port number
specified by this parameter.

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

102 IBM Tivoli Monitoring: Installation and Setup Guide

 However, if you did not configure this information, see “Configuring the
monitoring server” on page 52 for the procedure.

Starting and stopping the Situation Update Forwarder process

To send event updates to a monitoring server, you must start the Situation Update
Forwarder. This process is started automatically when the event server starts. To
start the process manually, change to the $BINDIR/TME/TEC/OM_TEC/bin
directory (where $BINDIR is the location of the Tivoli Management Framework
installation) and run the following command:

On Windows:
startSUF.cmd

On UNIX:
startSUF.sh

To stop the process, run the following command:

On Windows:
stopSUF.cmd

On UNIX:
stopSUF.sh

On Windows, you can also start and stop the Tivoli Situation Update Forwarder
service to start or stop the forwarding of event updates. You can start and stop this
service either from the Windows Service Manager utility or with the following
commands:
net start situpdate
net stop situpdate

Changing the configuration of the event synchronization on the event

server
If you want to change any of the settings for the event synchronization on the
event server, use the sitconfig.sh command. You have two options for running this
command:
v Manually modify the configuration file for event synchronization (named
situpdate.conf by default and located in the $BINDIR/TME/TEC/OM_TEC/etc
directory, where $BINDIR is the location of the Tivoli Management Framework
installation) and then run the following command:
sitconfig.sh update <config_filename>
v Run the sitconfig.sh command directly, specifying only those settings that you
want to change. See “sitconfig.sh” on page 234 for the full syntax of this
command.

After you change the configuration of the event synchronization, you must
manually stop and restart the Situation Update Forwarder process. See “Starting
and stopping the Situation Update Forwarder process” for information.

Chapter 6. Installing the IBM Tivoli Enterprise Console event synchronization 103
Defining additional monitoring servers to the event server
Run the following command to add additional monitoring servers to the list from
which you want to receive events:
sitconfsvruser.sh add serverid=server userid=user password=password

where:
serverid=server
The fully qualified host name of the monitoring server.
userid=user
The user ID to access the computer where the monitoring server is
running.
password=password
The password to access the computer.

Repeat this command for each monitoring server.

You can also delete monitoring servers. See “sitconfsvruser.sh” on page 236 for the
full syntax of this command.

After you change the configuration of the event synchronization, you must
manually stop and restart the Situation Update Forwarder process. See “Starting
and stopping the Situation Update Forwarder process” on page 103 for
information.

Changing the TCP/IP timeout setting on your event server

If the Situation Update Forwarder cannot reach a monitoring server to send an
update, depending on the TCP/IP settings for the computer where your event
server is running, it could be up to 15 minutes before the Situation Update
Forwarder tries to connect to the monitoring server again. This might occur if your
event server is running on an AIX, Solaris, or HP-UX computer.

Use the following steps to change the TCP/IP timeout for your computer.

On AIX, run the following command:

no -o tcp_keepinit=<timeout_value>

where <timeout_value> is the length of the timeout period, in half seconds. To

configure a timeout of 30 seconds, set the <timeout_value> value to 60.

On Solaris and HP-UX, run the following command:

ndd -set /dev/tcp tcp_ip_abort_cinterval <timeout_value>

where <timeout_value> is the length of the timeout period, in milliseconds. To

configure a timeout of 30 seconds, set the <timeout_value> value to 30000.

104 IBM Tivoli Monitoring: Installation and Setup Guide

Chapter 7. Configuring IBM Tivoli Monitoring components
Although the majority of configuration is done during the product installation, you
can use the Manage Tivoli Enterprise Monitoring Services tool to configure
components at any time. You can also use the Manage Tivoli Enterprise Monitoring
Services tool to start and stop components.

Note: You can also perform many of these configuration and start and stop
procedures from the command line. Where this is possible, the command is
included. See Appendix E, “Command reference,” on page 187 for a
complete description, including parameters, of the commands that you can
use in the installation and configuration of IBM Tivoli Monitoring.

You can perform the following tasks with the Manage Tivoli Enterprise Monitoring
Services tool:
Table 32. Configuration tasks available through Manage Tivoli Enterprise Monitoring
Services
Task Where to find information
Start Manage Tivoli Enterprise Monitoring “Starting Manage Tivoli Enterprise
Services Monitoring Services”
Change the configuration of the monitoring “Changing the configuration of the Tivoli
server Enterprise Monitoring Server” on page 106
Configure agents and other monitoring “Configuring or changing the monitoring
components server connection for agents” on page 107
Start and stop components “Starting and stopping components” on
page 108
Configure security “Configuring user security” on page 109
Configure failover support for monitoring “Configuring failover support” on page 110
servers
Add application support to the monitoring “Adding application support to the
server monitoring server” on page 112
Monitor the status of remote monitoring “Configuring the heartbeat interval” on page
servers and agents by configuring heartbeat 114
monitoring.

Starting Manage Tivoli Enterprise Monitoring Services

Depending on the operating system you are using, the procedure for starting
Manage Tivoli Enterprise Monitoring Services is different.

Starting Manage Tivoli Enterprise Monitoring Services on

Windows computers
Use the following steps to start Manage Tivoli Enterprise Monitoring Services on a
computer running Windows:
1. Click Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring
Services.

© Copyright IBM Corp. 2005 105

 Starting Manage Tivoli Enterprise Monitoring Services on
Linux or UNIX computers
Use the following steps to start Manage Tivoli Enterprise Monitoring Services on a
computer running Linux or UNIX:
1. Change to the bin directory:
cd install_dir/bin
2. Run the following command:
./itmcmd manage [-h install_dir] [-s]

where:
Table 33. Parameters for the itmcmd manage command
-h (optional) An option used to specify the
installation directory.
install_dir The installation directory for IBM Tivoli
Monitoring.
-s (optional) Option to specify safe mode
operation.

Safe mode invokes the JRE with the -nojit

option (no just-in-time compiler). If you
encounter a Java failure error, try running
the command as before, but also specifying
the -s option.

Entering the above commands with -?

displays the syntax for using the -s option.

The Manage Tivoli Enterprise Monitoring Services utility is displayed.

Note: Note that the Platform column for agents lists the platform that the binary
code was built on, not the platform that you are running on.

Changing the configuration of the Tivoli Enterprise Monitoring Server

You can change the basic configuration of the monitoring server through Manage
Tivoli Enterprise Monitoring Services. Use the following steps:
1. In the Manage Tivoli Enterprise Monitoring Services window, right-click the
monitoring server.
2. Click Reconfigure (on Windows) or Configure (on UNIX).
3. Identify the communications protocol for the monitoring server. You have four
choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. You can specify three methods for
communication - this enables you to set up backup communication methods. If
the method you’ve identified as Protocol 1 fails, Protocol 2 is used.
4. Click OK.
5. Complete the following fields for the communications protocol for the
monitoring server and click OK.
Table 34. Communications protocol settings
Field Description
IP.UDP Settings

106 IBM Tivoli Monitoring: Installation and Setup Guide

 Table 34. Communications protocol settings (continued)
Field Description
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.

6. Restart the monitoring server.

On Linux and UNIX, you can also use the itmcmd config -S command to change
the configuration of a monitoring server.

Configuring or changing the monitoring server connection for agents

To configure or change the monitoring server connection to the agents, use the
following procedure.
1. In the Manage Tivoli Enterprise Monitoring Services window, select the agent
whose connection you want to configure. You can select multiple agents by
holding down the Shift key or Control key and selecting agents.
2. Click Actions → Reconfigure.
3. Identify the communications protocol for communication with the monitoring
server. You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. You can
specify three methods for communication - this enables you to set up backup
communication methods. If the method you’ve identified as Protocol 1 fails,
Protocol 2 is used.
4. Click OK.

Chapter 7. Configuring IBM Tivoli Monitoring components 107

 5. Complete the following fields and click OK:
Table 35. Communications protocol settings
Field Description
IP.UDP Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port # and/or Port Pools The listening port for the hub monitoring
server.
IP.PIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port Number The listening port for the monitoring server.
The default number is 1918.
IP.SPIPE Settings
Hostname or IP Address The host name or IP address for the hub
monitoring server.
Port number The listening port for the hub monitoring
server. The default value is 3660.
SNA Settings
Network Name The SNA network identifier for your
location.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU 6.2 LOGMODE The name of the LU6.2 LOGMODE. The
default value is ″CANCTDCS.″
TP Name The transaction program name for the
monitoring server.

6. Restart the agent.

On Linux and UNIX, you can also use the itmcmd config -A command to change
the configuration of a monitoring agent.

Note: Note that the Platform column for agents lists the platform that the binary
code was built on, not the platform that you are running on.

Starting and stopping components

You can start and stop the IBM Tivoli Monitoring components from Manage Tivoli
Enterprise Monitoring Services. Use the following steps:
1. Right-click the component (such as a specific agent or the Tivoli Enterprise
Portal Server) that you want to start or stop.
2. Click Start, Stop, or Recycle (Windows only) from the menu.

You can also use the following commands to start and stop components:
itmcmd server
Starts and stops a UNIX monitoring server.
itmcmd agent
Starts and stops a UNIX monitoring agent
108 IBM Tivoli Monitoring: Installation and Setup Guide
 tacmd startAgent
Starts both Windows and UNIX monitoring agents.
tacmd stopAgent
Stops both Windows and UNIX monitoring agents.

See Appendix E, “Command reference,” on page 187 for the syntax of these
commands.

Configuring user security

You can control who has access to the Tivoli Enterprise Portal through the use of
user IDs and passwords. Initially, the Tivoli Enterprise Portal has only one valid
user ID, sysadmin. This enables the administrator to log on and create other users.

There are three steps to enabling user security in your monitoring environment:
1. “Enabling security on the hub monitoring server”
2. “Creating a user on the Tivoli Enterprise Portal”
3. Define a matching user ID with password to the network domain user accounts
or to the operating system where the hub monitoring server resides:
v User Accounts on Windows
v Password file on UNIX
v RACF® or ACF/2 host security system on OS/390® or z/OS
See your operating system documentation for information on creating users.

Enabling security on the hub monitoring server

Use the following steps to enable user security for the hub monitoring server:
1. In Manage Tivoli Enterprise Monitoring Services, right-click the hub monitoring
server and click Reconfigure (on Windows) or Configure (on UNIX).
2. Do the following:
On Windows: In the configuration window, select Security: Validate User and
click OK.
On UNIX: Click the Advanced Setting tab. Select Security: Validate User and
click OK.
3. Click OK on the next configuration window.
4. Restart the hub monitoring server.

Creating a user on the Tivoli Enterprise Portal

Use the following steps to create a user on the Tivoli Enterprise Portal. See the IBM
Tivoli Monitoring Administrator’s Guide for detailed information about creating and
maintaining users.
1. In the Tivoli Enterprise Portal, click Edit → Administer Users.
2. Click Create New User.
3. Type a user ID, user name, and optional description for the user.
4. Click OK and then OK again to close the window.

Chapter 7. Configuring IBM Tivoli Monitoring components 109

Configuring failover support
The optional Hot Standby feature enables you to maintain continuous availability
by defining a standby monitoring server to provide failover support for your hub
monitoring server. If the hub monitoring server fails, hub functions automatically
switch to the backup monitoring server. IBM Tivoli Monitoring automatically
connects all remote monitoring servers and agents to the backup monitoring server.

There is no automatic switch that 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 stop the backup monitoring server.

Configuring the Hot Standby feature involves the following steps:

1. “Installing the hub and backup hub monitoring servers at the same time”
2. “Adding application support on the backup hub monitoring server”
3. “Configuring the Hot Standby feature on monitoring servers” on page 111
4. “Configuring agents” on page 112
5. “Verifying that failover support is working” on page 112

Installing the hub and backup hub monitoring servers at the

same time
If you are installing both the hub and backup monitoring servers at the same time,
see “Installing and configuring the hub Tivoli Enterprise Monitoring Server” on
page 48 for information about installing a hub monitoring server. When you are
installing the backup hub monitoring server, use identical values to those you used
when installing the primary hub monitoring server. If you have previously
installed the hub monitoring server and are returning now to install the backup
monitoring server, see “Adding application support on the backup hub monitoring
server” for information about installing and configuring the backup monitoring
server.

Adding application support on the backup hub monitoring

server
If you are installing the hub and backup monitoring servers at the same time, you
can add application support as normal, either through the Windows installation
program or by running the itmcmd support command on Linux or UNIX
monitoring servers. If you add additional applications to your monitoring
environment, add the support for these applications to both monitoring servers
and restart the servers.

However, if you have previously installed your hub monitoring server and are
now setting up failover support, the two monitoring servers might not be in synch
if you add the default application support to the backup monitoring server during
install. Any changes that you made to situations on the hub monitoring server are
not replicated on the backup monitoring server. To address this issue, use the
following steps to add applications support to your backup monitoring server.

For a Windows backup monitoring server, install the monitoring server using the
installation program. When you come to the step to add application support, click
Cancel instead of OK. When your installation is complete, start the backup
monitoring server. The backup monitoring server connects to the hub monitoring
server and automatically synchronizes with it.

110 IBM Tivoli Monitoring: Installation and Setup Guide

 For a Linux or UNIX backup monitoring server, install and configure the
monitoring server using the CLI commands, as described in “Linux or UNIX:
Installing a hub monitoring server” on page 51. However, instead of running the
itmcmd support command described in that section, run the following command:
./itmcmd support -m -t tems_name pc pc pc

The -m parameter copies the support files to the monitoring server without adding
it. When you are finished, start the backup monitoring server. The backup
monitoring server connects to the hub monitoring server and automatically
synchronizes with it.

After the initial configuration of your backup monitoring server, if you add an
application to the hub monitoring server, you can add application support to both
monitoring servers at the same time.

Configuring the Hot Standby feature on monitoring servers

Use the following steps to configure monitoring servers for the Hot Standby
feature. 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 backup 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 (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 backup monitoring server in the Standby TEMS
Site field.
d. Select the type of protocol to use for hot standby. This should be the same
protocol on both the hub monitoring server and the monitoring server you
are going to use for failover support.
e. If you specified any backup protocols for the hub monitoring server,
identify identical protocols for the backup 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 backup monitoring server and any remote
monitoring servers.

Chapter 7. Configuring IBM Tivoli Monitoring components 111

 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.
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 failover support is working

To verify that the failover support provided by the Hot Standby feature is working,
take your hub monitoring server offline by stopping its servers in Manage Tivoli
Enterprise Monitoring Services. Once the hub monitoring server has stopped,
reconfigure the Tivoli Enterprise Portal Server to point to the backup monitoring
server and restart the portal server. Open the Tivoli Enterprise Portal. If everything
is configured correctly, you can open the portal and view data.

Adding application support to the monitoring server

Adding application support adds required support files, such as situations, to the
monitoring server. For Windows, you add the application support to the
monitoring server both during install and through Manage Tivoli Enterprise
Monitoring Services. For UNIX, you add the application support to the monitoring
server through Manage Tivoli Enterprise Monitoring Services and from the
command line.

Note: If the application support is for an agent that reports to a remote monitoring
server, complete this process for both the hub and the remote monitoring
server. A hub monitoring server should be running before proceeding to
install the application support on a remote monitoring server.

Using Manage Tivoli Enterprise Monitoring Services to add

application support to a monitoring server
Use the following steps to add application support to the monitoring server:
1. Right-click the monitoring server to which you want to add application
support.
2. Click Advanced → Add TEMS Application Support.
3. Specify the location of the monitoring server and click OK:
v On this computer
v On a different computer

112 IBM Tivoli Monitoring: Installation and Setup Guide

 4. If you selected a monitoring server on a different computer, provide the TEMS
Node ID and communications protocol to use to communicate with the
monitoring server. Click OK.

Note: To view the Node ID, right-click the monitoring server and click Browse
Settings.
5. Select the products for which you want to add application support. Click Select
All to choose all available products. Click OK.
6. When the process is complete, a message is displayed containing information
about the procedure. Click Close.
7. If the monitoring server is not already stopped, stop it.
8. Restart the monitoring server.

Using the itmcmd support command to add application

support to a Linux or UNIX monitoring server
Use the following steps to add application support to a UNIX monitoring server
from the command line.
1. If the monitoring server is not running, run the following command to start it:
./itmcmd server start tems_name

where tems_name is the name of the monitoring server.

2. Run the following command to add the application support:
./itmcmd support [-h install_dir] [-s] -t tems_name pc pc pc pc pc ...

where:
Table 36. Parameters for the itmcmd support command
-h (optional) Parameter to specify the
installation directory if it is not the one in
which this script is located. Usually not
necessary. Also use this option to take action
on an installation directory other than this
one.
install_dir The home directory that you created for IBM
Tivoli Monitoring.
-s (optional) Option to specify safe mode
operation.

Safe mode invokes the JRE with the -nojit

option (no just-in-time compiler). If you
encounter a Java failure error, try running
the command as before, but also specifying
the -s option. This might solve some Java
exceptions that occur on a small number of
computers.

Entering the above commands with -?

displays the syntax for using the -s option.
-t Use this required option to specify the
monitoring server name.

Chapter 7. Configuring IBM Tivoli Monitoring components 113

 Table 36. Parameters for the itmcmd support command (continued)
tems_name Specifies the name of the monitoring server
you are configuring. This argument is
required.
Note: The monitoring server must be
specified within the structure of install_dir.
pc The product code of the product that will
connect to this monitoring server. You can
specify one or more products for which to
add application support. If you are
specifying multiple products, you must
separate the product codes with either a
space or comma as illustrated above.

See Appendix D, “IBM Tivoli Product

Codes,” on page 185 for a list of product
codes.

3. Run the following command to stop the monitoring server:

./itmcmd server stop tems_name
4. Restart the monitoring server by running the following command:
./itmcmd server start tems_name

Configuring the heartbeat interval

IBM Tivoli Monitoring uses a heartbeat mechanism to monitor the status of remote
monitoring servers and monitoring agents. The different monitoring components in
the monitoring architecture form a hierarchy (shown in Figure 13 on page 115)
across which the heartbeat information is propagated.

The hub monitoring server maintains status for all monitoring agents. Remote
monitoring servers offload processing from the hub monitoring server by receiving
and processing heartbeat requests from monitoring agents, and communicating
only status changes to the hub monitoring server.

114 IBM Tivoli Monitoring: Installation and Setup Guide

Figure 13. Hierarchy for the heartbeat interval

v At the highest level, the hub monitoring server receives heartbeat requests from
remote monitoring servers and from any monitoring agents that are configured
to access the hub monitoring server directly (rather than through a remote
monitoring server). The default heartbeat interval used by remote monitoring
servers to communicate their status to the hub monitoring server is 3 minutes.
v At the next level, remote monitoring servers receive heartbeat requests from
monitoring agents that are configured to access them. The default heartbeat
interval used by monitoring agents to communicate their status to the
monitoring server is 10 minutes.

You can specify the heartbeat interval for a node by setting the
CTIRA_HEARTBEAT environment variable. For example, specifying
CTIRA_HEARTBEAT=5 sets the heartbeat interval to 5 minutes.
v For remote monitoring agents, you can set this variable by adding an entry to
the KBBENV file. You can access this file from Manage Tivoli Enterprise
Monitoring Services by right-clicking Tivoli Enterprise Monitoring Server and
clicking Advanced → Edit ENV File. You must stop and restart the monitoring
server for changes to the KBBENV file to take effect.
v For Windows OS agents, you can set this variable by adding the entry to the
KNTENV file. You can access this file from Manage Tivoli Enterprise Monitoring
Services by right-clicking Windows OS Monitoring Agent and clicking

Chapter 7. Configuring IBM Tivoli Monitoring components 115

 Advanced → Edit ENV File. You must stop and restart the monitoring agent for
the changes to the KNTENV file to take effect.
v For agents on Linux and UNIX computers, you can set the CTIRA_HEARTBEAT
variable by adding an entry to the agent .ini file (for example, lz.ini, ux.ini,
ua.ini). When the agent is stopped and restarted, the agent configuration file is
recreated using settings in the .ini file.

When a monitoring agent becomes active and sends an initial heartbeat request to
the monitoring server, it communicates the desired heartbeat interval for the agent
in the request. The monitoring server stores the time the heartbeat request was
received and sets the expected time for the next heartbeat request based on the
agent heartbeat interval. If no heartbeat interval was set at the agent, the default
value is used.

Changes to offline status typically require two missed heartbeat requests for the
status to change. Offline status is indicated by the node being ″grayed out″ in the
portal client Navigator View. If the heartbeat interval is set to 10 minutes, an
offline status change would be expected to take between 10 and 20 minutes before
it is reflected on the portal client Navigator View.

Lower heartbeat intervals require more processing on the monitoring servers to

process the heartbeat requests. For a remote monitoring server receiving requests
from a large number of monitoring agents, setting the heartbeat interval too low
may cause high CPU utilization on the monitoring servers.

116 IBM Tivoli Monitoring: Installation and Setup Guide

Chapter 8. Advanced Linux or UNIX monitoring server
configuration
The following sections provide information about advanced configuration on a
Linux or UNIX monitoring server.

Configuring permissions for a monitoring server on a non-NIS Solaris

If your monitoring server is installed on a non-NIS Solaris computer, you must set
the permissions. You do not need to do this for monitoring servers running on AIX
or Linux.

Set permissions for a monitoring server on a non-NIS Solaris system as follows:

1. Go to the /bin directory where kdsvlunx is located. (install_dir/arch/ms/bin,
where arch is the operating system on which the monitoring was installed).
2. Change the su to ″root″ if you have the root password, otherwise obtain the
password from an administrator:
chown root kdsvlunx
chmod u+s kdsvlunx
3. Return to your regular ID after you have changed the su to ″root.″

Firewall support
IBM Tivoli Monitoring supports firewalls using the IP.PIPE communications
protocol, which supports network address translation (NAT). Agents connecting to
the monitoring server must use the IP.PIPE communications protocol.

If your site is using address translation, you must create a partition file, a text file
containing the name of a partition and its constituent interface address. You must
create or modify this file before implementing firewall support with the CMS and
agents.

When IBM Tivoli Monitoring components need to communicate across a firewall

that performs NAT, those components must be able to retrieve an IP address of the
other component that is valid on its side of the firewall. To support this capability,
the location broker namespace is logically divided into partitions with unique
partition IDs. Partition IDs are specified using the KDC_PARTITION environment
variable. The partition file is the means to insert appropriate IP addresses into the
location broker namespaces.

When an IBM Tivoli Monitoring component performs a location broker lookup

operation, the partition ID of its partition is automatically supplied. The location
broker returns only addresses that have been defined for that partition namespace
and no other. In effect, the IBM Tivoli Monitoring component sees only addresses
that are valid for its partition.

A partition file is a standard text file (like this one) and is defined to the system
using the KDC_PARTITIONFILE environment variable. Within this file, each line
describes a partition name with its constituent IP addresses using space delimited
tokens. The format is as follows:
PARTITION-ID IP.PIPE:nn.nn.nn.nn IP.PIPE:nn.nn.nn.nn

© Copyright IBM Corp. 2005 117

 The first token on each line is used as a case-insensitive partition id. The partition
id can be any alphanumeric string with a maximum length of 32 characters.
Subsequent tokens specified are treated as interface addresses in standard NCS
format (address-family:address). For communication across firewalls, use only
IP.PIPE for address-family.

The expected default location of the file is /install_dir/tables/ctems_name.

Sample partition file

Below is a sample partition file illustrating the format and content expected.
# SAMPLE PARTITION FILE
#
# IMPORTANT: Do not overwrite this file. Copy to another directory
# before making changes.
#
# Lines beginning with a ‘#’ are treated as comments and are ignored.
# Note: Do not specify a line that starts with an ‘*’ as it might prevent
# the proper functioning of CCC.
#
# Basic Format
# PARTITION-ID IP.PIPE:nn.nn.nn.nn IP.PIPE:nn.nn.nn.nn
#
# Procedure to edit this sample partition file.
# To create a CMS partition file for a typical CCC scenario (TEMA outside of a #
# NAT firewall connecting to a CMS behind the firewall). Do the following:
# 1) Replace the “$OUTSIDE-PID$” with the partition id of your TEMA
# 2) Replace the “$OUTSIDE-CMS-HOST-ADDRESS$” with the ip address of the TEMS host
# outside of the firewall.
# 3) Add additional IP.PIPE:nn.nn.nn.nn addresses on a single line for multiple
# Network Interface Cards (NICs) as in the format above.
# Separate entries with 2 spaces.
# Lines can be continued by placing a backslash (‘\’) char at the end of the
# line.
#
##############################################################################
$OUTSIDE-PID$ IP.PIPE:$OUTSIDE-CMS-HOST-ADDRESS$

Editing the partition file in Manage Tivoli Enterprise

Monitoring Services
You can create or modify the partition file using the CMS Configuration option in
Manage Tivoli Enterprise Monitoring Services. Use the following steps:
1. Select the monitoring server you want to configure.
2. Click Action → Configure → Basic Settings.
3. Select IP.PIPE as the communications protocol.
4. Select Use Address Translation.
5. Enter the full path and file name for the partition file.
6. Click Create to create the file (if it does not exist) or Modify to edit the file.
7. Enter the partition ID in the first column.
8. Enter the IP address in the second column. If you require a second IP address,
enter it in the third column. (If more than two IP addresses are required for a
partition ID, use a text editor to add the additional addresses. See “Sample
partition file.”)
9. Click Save to save the file and exit or Cancel to return to the previous screen
without modifying the file.

118 IBM Tivoli Monitoring: Installation and Setup Guide

Chapter 9. Additional Tivoli Enterprise Portal configuration
This chapter discusses how to perform the following advanced configuration of
Tivoli Enterprise Portal components:
v “Using SSL between the portal server and the client”
v “Configuring an external Web server to work with Tivoli Enterprise Portal” on
page 123
v “Configuring a portal client connection to an external Web server” on page 126
v “Firewall network address translation (NAT) or multiple network interface
cards” on page 127
v “Firewall scenarios for Tivoli Enterprise Portal” on page 128
It also includes illustrations of firewall scenarios that can help in defining the
Tivoli Enterprise Portal Server interface.

Using SSL between the portal server and the client

You can choose to encrypt all communication between the portal server and portal
client. IBM Tivoli Monitoring uses two protocols to provide this level of security
between portal server and client server:
v Secure Hypertext Transport Protocol (HTTPS) to retrieve files and Interoperable
Object Reference (IOR). The integrated browser in the client provides HTTPS
support on the client side; for the server, consider using a third party web server
that supports HTTPS, such as the IBM HTTP Server. See “Configuring an
external Web server to work with Tivoli Enterprise Portal” on page 123 for more
information.
v Internet Inter-ORB Protocol (IIOP) to secure the communications between the
portal server and client. This uses Secure Socket Layer (SSL) provided by
VisiBroker. This secure communication uses public key cryptography.

When you install IBM Tivoli Monitoring, the Global Sign-On Toolkit (GSKit) and
iKeyman utilities are installed by default on all components. These utilities are
used to create and manage the encryption of data between components through
the use of digital certificates.

Digital certificates are the vehicle that SSL uses for public-key cryptography.
Public-key cryptography uses two different cryptographic keys: a private key and a
public key. Public-key cryptography is also known as asymmetric cryptography,
because you can encrypt information with one key and decrypt it with the
complement key from a given public-private key pair.

Public-private key pairs are simply long strings of data that act as keys to a user's
encryption scheme. The user keeps the private key in a secure place (for example,
encrypted on a computer’s hard drive) and provides the public key to anyone with
whom the user wants to communicate. The private key is used to digitally sign all
secure communications sent from the user; the public key is used by the recipient
to verify the sender’s signature.

Public-private key pairs are validated by a trusted third party, called a Certificate
Authority (CA). An example of a CA is Verisign. If you are setting up your own
key pairs, you submit them to the CA for validation.

© Copyright IBM Corp. 2005 119

 You can configure your portal server and client are configured to use asymmetric
cryptography, using the default keys provided with IBM Tivoli Monitoring. See
“Setting up asymmetric encryption” for information about setting up this
encryption.

For additional information about using public-private key pairs, see the iKeyman
documentation available at http://www-
1.ibm.com/support/docview.wss?uid=pub1sc32136300.

Enabling and disabling SSL for the Tivoli Enterprise Portal

Server
IBM Tivoli Monitoring is shipped with SSL disabled as the default.

If you want to use Secure Socket Layer communication between the portal server
and the portal client, use the following steps to enable it:

On a Windows system:
1. In the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli
Enterprise Portal Server.
2. Click Advanced → Configure TEPS Interfaces.
3. Highlight cnps and click Edit in the TEPS Interface Definitions window.
4. Select Enable SSL for TEP Clients.
5. Click OK to save your changes and close the window.
6. Recycle the service by stopping and starting it.

On a Linux system:
1. Change to the install_dir/bin directory
2. Run the following command:
./itmcmd manage
3. In the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli
Enterprise Portal Server.
4. Click Configure
5. In the first tab, select Enable SSL for TEP Clients to enable SSL in the Tivoli
Enterprise Portal Server window.
6. Click OK to save your changes and close the window.
7. Recycle the service by stopping and starting it.

Setting up asymmetric encryption

Setting up asymmetric encryption through the use of public-private key files
requires the following steps:
Table 37. Setting up asymmetric encryption
Goal Where to find information
Create a new key database. “Creating a new key database” on page 121
Create a request for a new public-private “Creating a new public-private key pair and
key pair and send that request to a trusted certificate request” on page 121
Certificate Authority.
Optionally use a temporary, self-signed key “Using a temporary self-signed certificate”
pair while you wait for your CA-signed on page 122
certificate.

120 IBM Tivoli Monitoring: Installation and Setup Guide

Table 37. Setting up asymmetric encryption (continued)
Goal Where to find information
Add the CA-signed digital certificate to your “Receiving the CA-signed certificate” on
key database. page 122
Enable components to access the certificate “Save the password to a stash file” on page
by saving the key database password to a 123
stash file on your computer.

Important: If you do not use the recommended names for the key database, stash
file, and certificate label as described below, you must change the
following environment variables in the KFWSERVICES file on the
portal server:
v KDEBE_KEYRING_FILE=C:\IBM\ITM\keyfiles\keyfile.kdb
v KDEBE_KEYRING_STASH=C:\IBM\ITM\keyfiles\keyfile.sth
v KDEBE_KEY_LABEL=IBM_Tivoli_Monitoring_Certificate

Creating a new key database

Use the following steps to create a new key database:
1. Start iKeyman:
v On Windows, double-click the gsk7ikm.exe file, located in the c:\Program
Files\IBM\gsk7\bin directory.
v On UNIX, change to the GSKit directory and run one of the following
commands:
For 32-bit operating systems, run gsk7ikm.
For 64-bit operating systems, run gsk7ikm_64.
2. Click Key Database File → New.
3. Select CMS in the Key database type field.
4. Type keyfile.kdb in the File Name field.
5. Type the following location in the Location field: <itm_installdir>/keyfiles.
6. Click OK. The Password Prompt window is displayed.
7. Enter a password in the Password field, and confirm it again in the Confirm
Password field. Click OK.
8. A confirmation window is displayed. Click OK.
The IBM Key Management window is displayed. This window reflects the new
CMS key database file and your signer digital certificates.

Creating a new public-private key pair and certificate request

Use the following steps to create a new public-private key pair and certificate
request:
1. Start iKeyman.
2. Click Key Database File → Open.
3. Select the keyfile.kdb key database and click Open.
4. Type the password for the key database and click OK.
5. Select Personal Certificate Requests from the pull-down list and click New.
6. Click New.
7. Type IBM_Tivoli_Monitoring_Certificate in the Key Label field.
8. Type a Common Name and Organization, and select a Country. For the
remaining fields, either accept the default values, or type or select new values.

Chapter 9. Additional Tivoli Enterprise Portal configuration 121

 9. At the bottom of the window, type a name for the file.
10. Click OK. A confirmation window is displayed, verifying that you have
created a request for a new digital certificate.
11. Click OK.

The IBM Key Management window is displayed.

Send the file to a CA to request a new digital certificate, or cut and paste the
request into the request forms on the CA's Web site.

Using a temporary self-signed certificate

It can take between two and three weeks to receive a CA-signed digital certificate.
If you want to use a digital certificate other than the one provided with IBM Tivoli
Monitoring and you have not yet received the CA-signed digital certificate, you
can create a self-signed certificate on the portal server and import it on the client.
A self-signed digital certificate is not as secure as a CA-signed certificate; this is
strictly a temporary measure until the CA-signed certificate arrives.

Creating and using a self-signed certificate involves the following steps:

1. Create a CA key database.
2. Create the self-signed certificate.
3. Export the self-signed certificate.
4. Receive the self-signed certificate into the key databases on the portal server
and client.

When you receive the CA-signed certificate, you need to delete the self-signed
certificate.

For information on all of these steps, see the iKeyman documentation available at
http://www-1.ibm.com/support/docview.wss?uid=pub1sc32136300.

Receiving the CA-signed certificate

After the CA returns your new digital certificate, save it on the computer where
the portal server is running. Repeat for the client. If the CA returns the certificate
as part of an e-mail message, copy and paste it from the e-mail into a text file.

Use the following steps to receive the digital certificate from the CA into key
database on each computer.
1. Start iKeyman.
2. Click Key Database File → Open.
3. Select the keyfile.kdb database and click Open.
4. Type the password for the database and click OK.
5. Select Personal Certificates from the pull-down list.
6. Click Receive.
7. Click Data type and select the data type of the new digital certificate, such as
Base64-encoded ASCII data.
8. Type keyfile.sth for the Certificate file name and
<itm_installdir>/keyfiles as the Location for the new digital certificate.
9. Click OK.
10. Type IBM_Tivoli_Monitoring_Certificate for the new digital certificate and
click OK.

122 IBM Tivoli Monitoring: Installation and Setup Guide

 Save the password to a stash file
Because many of the IBM Tivoli Monitoring components work without user
intervention, you need to save the key database password to a stash file on your
computer. This enables the components to use SSL without requiring any
intervention from you. Use the following steps to save the password to a stash file:
1. Start iKeyman.
2. Select Key Database File → Stash File.
An information window is displayed telling you that the password was saved
to a stash file.
3. Click OK.

Disabling SSL
If you do not want to use Secure Socket Layer communication between IBM Tivoli
Monitoring components and the Tivoli Enterprise Portal Server, use the following
steps to disable it:
1. In Manage Tivoli Enterprise Monitoring Services, right-click Tivoli Enterprise
Portal Server.
2. Click Advanced → Edit ENV file.
3. Find the following line:
kfw_interface_cnps_ssl=Y
4. Change the Y to N.
5. Save the file and exit.
6. Click Yes when you are asked if you want to recycle the service.

Configuring an external Web server to work with Tivoli Enterprise

Portal
If you want to use an external Web server to view the Tivoli Enterprise Portal, you
need to configure that Web server. The following sections provide configuration
information for Microsoft Internet Information Server versions 5.0 and 6.0.
v “Configuring Internet Information Server V5.0”
v “Configuring Internet Information Server V6.0” on page 124
v “Configuring IBM HTTP Server on Linux” on page 125

Configuring Internet Information Server V5.0

Use the following steps to configure Internet Information Server V5.0 to work as a
Tivoli Enterprise Portal browser client.
1. Start the Internet Services Manager.
2. Right click the WWW service (the system host name).
3. Select Master Properties and click Edit.
4. Click the Directory Security tab.
5. Click Edit.
6. Ensure that Anonymous access and Integrated Windows authentication are
selected and click OK.
7. Click the Documents tab.
8. Click Add.
9. Type index.html in the Default Document Name field.
10. Click OK and then click OK to close the Master Properties notebook.

Chapter 9. Additional Tivoli Enterprise Portal configuration 123

 Use the following steps to set up the Web site:
1. From the Internet Services Manager, right-click the WWW service.
2. Click New → Web Site.
3. Click Next.
4. Type a description for the Web site (for example, ″ITM 6.1″).

Note: Refer to the documentation for Internet Information Server before

changing any of the default values in the next steps.
5. If you have multiple IP addresses, select the one that is appropriate for this site.
6. If you want to use a separate port of this site, type the port number in the TCP
Port field.
7. Type the path to the Tivoli Enterprise Portal browser client. The default path is
C:\IBM\ITM\CNB.
8. Ensure that Read and Run Scripts are selected. Do not select Execute.
9. Click Next and then click Finish.

If the site does not start automatically, right-click it and click Start.

Configuring Internet Information Server V6.0

Use the following steps to configure Internet Information Server V6.0 on Windows
2003 to work as a Tivoli Enterprise Portal browser client:
1. Start IIS Manager.
2. Right-click Web Sites and click New → Web Site.
3. Click Next.
4. Type the name of a Web site (for example ″Tivoli″) and click Next.
5. Type the IP address for the Tivoli Enterprise Portal Server computer (this
should be the same computer where IIS 6.0 is running) and click Next.
6. Type the path to the IBM Tivoli Monitoring home directory that is the root of
the Web Content subdirectories. The default path is C:\IBM\ITM\CNB. Click
Next.
7. Select Read, Run scripts, and Execute. Click Next.
8. Click Finish.
9. Right-click the new Web site and click Properties.
10. Click the Documents tab.
11. In the Add Content Page field, type index.html. This is the main page for the
Tivoli Enterprise Portal.
12. Click the Move Up button to move index.html to the top of the list.
13. Click the HTTP Headers tab.
14. Click MIME Types.
15. Click New next to MIME Types.
16. Type *.asp in the Extension field.
17. Type application/x-asp in the MIME Type field.
18. Click OK.
19. Repeat Steps 15 to 18 for each of the following:
Extension MIME Type
.class application/java-class
.ior application/octet-stream

124 IBM Tivoli Monitoring: Installation and Setup Guide

 .jar application/java-archive
.jks application/octet-stream
.jnlp application/x-java-jnlp-file
.js application/x-javascript
.llser application/octet-stream
.pl application/x-perl
.ser application/java-serialized-object
.txt text/plain
.zip application/zip
20. Click OK.
21. Click Apply.
22. Click OK.

Configuring IBM HTTP Server on Linux

Use the following steps to configure IBM HTTP Server to work on a Linux
computer:
1. Install IBM HTTP Server with the default settings. See the product
documentation (www-306.ibm.com/software/webservers/httpservers/library)
for additional information.
2. Open the IHS_install_dir/conf/httpd.conf file in a text editor. The default
installation directory is /opt/IBMIHS.
3. Find the line that begins with DocumentRoot. Change the value (between the
double quotation marks [″″]) to itm_installdir/linux_dir/cw, where
itm_installdir is the directory where IBM Tivoli Monitoring is installed and
linux_dir is li6243 (Red Hat systems), li6263 (SLES9 for Intel systems) or li3263
(SLES9 for z/Series systems). For example:
DocumentRoot "/data/candle/li6243/cw"
4. Find the line that begins with <Directory>/opt. Change the path to the value
used for DocumentRoot. (From our previous example, it would be
itm_installdir/li6243/cw).
5. Save and close the file.
6. Open the IHS_install_dir/conf/mime.types file in a text editor.
7. Add the following lines:
application/java-archive jar
application/java-serialized-object ser
image/icon ico
8. Modify the line that begins with application/octet-stream to include cab ior
jks llrser jbf jnlp vbs at the end. For example:
application/octet-stream bin dms lha lzh exe class so dll cab ior jks llrser
jbf jnlp vbs
9. Modify the line that beings with text/plain to include bat ini inf ivl log
lng lvl mf properties at the end. For example:
text/plain asc txt bat ini inf ivl log lng lvl mf properties
10. Save and close the file.
11. Stop the IBM HTTP Server services, then start it again to enable the
configuration changes.

Chapter 9. Additional Tivoli Enterprise Portal configuration 125

Configuring a portal client connection to an external Web server
Use the following sections to configure your portal client to work with an external
Web server:
v “Browser client”
v “Desktop client”

Browser client
During installation, the IBM Tivoli integral Web server is installed as a component
of the Tivoli Enterprise Portal Server. You can also use an external Web server on
your Tivoli Enterprise Portal Server computer, as shown in “Firewall scenarios for
Tivoli Enterprise Portal” on page 128.

Currently, IBM supports an external Web server for browser client access only
when installed on the same computer as the Tivoli Enterprise Portal Server.

Desktop client
Although the desktop client does not need a Web server to start Tivoli Enterprise
Portal, it does use it for common files stored on the Tivoli Enterprise Portal Server,
such as the graphic view icons and style sheets. If your Tivoli Enterprise Portal
Server setup disables the integral Web server and uses only an external Web server,
you need to specify the Interoperable Object Reference (IOR) for every desktop
client.

Updating the IOR for Windows

Use the following steps to specify the IOR for the desktop client:
1. On the computer where Tivoli Enterprise Portal desktop client is installed, open
Manage Tivoli Enterprise Monitoring Services
2. Right-click Tivoli Enterprise Portal – Desktop and click Reconfigure.
3. Double-click cnp.http.url.DataBus in the parameters list. The Edit CandleNet
Portal Parm window is displayed.
4. In the Value field, type the Web server address where the cnps.ior can be
found. For example, if the Web server name is xyz.myserver.com and the
document root for the Web server is \candle\cnb, the value is
http://xyz.myserver.com/cnps.ior.
5. Select In Use and click OK.
6. Click OK to close the window.

Updating the IOR for Linux

In order to update the IOR for a Linux portal client, you must change the default
shell script that launches the browser client.
1. Go to the install_dir/bin/cnp.sh and edit the cnp.sh shell script.
2. Add your Web browser location to the last line of the file. In the example
below, the Web browser location is /opt/foo/bin/launcher.
-Dkjr.browser.default=/opt/foo/bin/launcher

Note: The line is very long and has various options on it, including several
other –D options to define other properties. It is very important to add
the option in the correct place.
If the last line of your bin/cnp.sh originally looked like this:

126 IBM Tivoli Monitoring: Installation and Setup Guide

 ${JAVA_HOME}/bin/java -showversion -noverify -classpath ${CLASSPATH}
-Dkjr.trace.mode=LOCAL -Dkjr.trace.file=/opt/IBM/ITM/logs/kcjras1.log
-Dkjr.trace.params=ERROR -DORBtcpNoDelay=true -Dcnp.http.url.host=
-Dvbroker.agent.enableLocator=false
-Dhttp.proxyHost=
-Dhttp.proxyPort=candle.fw.pres.CMWApplet 2>& 1 >> ${LOGFILENAME}.log

To set the browser location to /opt/foo/bin/launcher, change the line to look like the
following:
${JAVA_HOME}/bin/java -showversion -noverify -classpath ${CLASSPATH}
-Dkjr.browser.default=/opt/foo/bin/launcher
-Dkjr.trace.mode=LOCAL -Dkjr.trace.file=/opt/IBM/ITM/logs/kcjras1.log
-Dkjr.trace.params=ERROR -DORBtcpNoDelay=true -Dcnp.http.url.host=
-Dvbroker.agent.enableLocator=false
-Dhttp.proxyHost=
-Dhttp.proxyPort=candle.fw.pres.CMWApplet 2>& 1 >> ${LOGFILENAME}.log

Firewall network address translation (NAT) or multiple network

interface cards
The URL for starting Tivoli Enterprise Portal browser mode includes the Tivoli
Enterprise Portal Server host name or IP address. The address for starting Tivoli
Enterprise Portal is set for the desktop client during installation or through
Manage Tivoli Enterprise Monitoring Services. If any of the following is true in
your configuration, you need to define a Tivoli Enterprise Portal Server interface
through Manage Tivoli Enterprise Monitoring Services:
v A firewall with Network Address Translation (NAT) is used between the client
and the Tivoli Enterprise Portal Server.
v The Tivoli Enterprise Portal Server is configured to be accessed through a
secondary Network Interface Card (NIC).

Note: The Linux portal server does not support the use of multiple interfaces.

Defining a Tivoli Enterprise Portal Server interface

Use the following steps to define a Tivoli Enterprise Portal Server interface:
1. On the computer where the Tivoli Enterprise Portal Server is installed, click
Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Enterprise
Monitoring Services.
2. Right-click Tivoli Enterprise Portal Server.
3. Click Advanced → Configure TEPS Interfaces.
Initially, the list has one definition named ″cnps,″ using port 15001 for the
Tivoli Enterprise Portal Server and the IBM Tivoli integrated Web server at
http://mysystem:1920///cnp/client (where the variable mysystem is the host
name). Port 80, for an external Web server, is assumed if the URL does not
specify 1920 for the integrated Web server.
4. Click Add.
5. Define the interface. Complete the following fields:
Interface Name
Type a one-word title for the interface.
Host If you are defining an interface for a specific NIC or different IP
address on this computer, type the TCP/IP host address. Otherwise,
leave this field blank.

Chapter 9. Additional Tivoli Enterprise Portal configuration 127

 Proxy Host
If you are using address translation (NAT), type the TCP/IP address
used outside the firewall. This is the NATed address.
Port Type a new port number for the Tivoli Enterprise Portal Server. The
default 15001 is for the server host address, so a second host IP address
or a NATed address requires a different port number.
Proxy Port
If the port outside the firewall will be translated to something different
than what is specified for Port, set that value here.
6. Click OK to add the new Tivoli Enterprise Portal Server interface definition to
the list.

Firewall scenarios for Tivoli Enterprise Portal

The following diagrams illustrate several firewall scenarios using various
combinations of the IBM Tivoli integral Web server, a third-party Web server, NAT,
and a second NIC on the Tivoli Enterprise Portal Server computer. They can help
you to define the Tivoli Enterprise Portal Server interface.

Figure 14 on page 129 shows a configuration that has or does the following:
v Has an intranet firewall
v Has no NAT
v Uses the integral Web server

128 IBM Tivoli Monitoring: Installation and Setup Guide

Figure 14. Intranet with integral Web server

The default Tivoli Enterprise Portal Server interface ″cnps″ is used. No additional
interface definitions are needed. Browser mode users, whether going through the
firewall or not, start Tivoli Enterprise Portal at
http://10.10.10.10:1920///cnp/client or substitute the host name for the IP
address.

For configurations using the integrated Web server and these port numbers, use
the default cnps interface definition.

In this scenario, the monitoring server and agents can be installed on the Tivoli
Enterprise Portal Server computer.

Figure 15 on page 130 shows a configuration that has or does the following:
v Has an intranet firewall
v Has no NAT
v Uses an external Web server (such as Apache or IIS)

Chapter 9. Additional Tivoli Enterprise Portal configuration 129

Figure 15. Intranet with external Web server

Browser mode users, whether going through the firewall or not, start Tivoli
Enterprise Portal Server with http://10.10.10.10 or http://10.10.10.10/mydirectory
(where mydirectory is the alias), or substitute the host name for the IP address.

For intranet configurations using an external Web server, with no NAT, you do not
need to add a new interface definition. Web server port 80 is used automatically
when non is specified in the URL.

In this scenario, the monitoring server and agents can be installed on the Tivoli
Enterprise Portal Server computer.

Figure 16 on page 131shows the following two-part configuration:

v Intranet firewall without NAT and using the integral Web server
v Internet firewall with NAT and using an external Web server

130 IBM Tivoli Monitoring: Installation and Setup Guide

Figure 16. Intranet with integral Web server; Internet with external Web server

Intranet users can enter the URL for either the integral Web server or the external
Web server: http//10.10.10.10:1920///cnp/client or http://10.10.10.10.

Internet users enter the URL for the NATed address:

http://198.210.32.34/?ior=internet.ior (or substitute the host name for the IP
address).

The Internet configuration requires a new Tivoli Enterprise Portal Server interface
definition: proxy host address 198.210.32.34 and port number 15002. The intranet
firewall uses the ″cnps″ definition.

In this scenario, the monitoring server and agents cannot be installed on the Tivoli
Enterprise Portal Server computer.

Figure 17 on page 132 shows the following three-part configuration:

v Intranet firewall with NAT through the firewall to the external Web server
http://192.168.1.100/?ior=intranet.ior
v Without NAT inside the DMZ to the integral Web server
http://10.10.10.10:1920///cnp/client
v Internet firewall with NAT through the firewall to the external Web server
http://198.210.32.34/?ior=internet.ior

Chapter 9. Additional Tivoli Enterprise Portal configuration 131

Figure 17. Intranet and Internet with integral and external Web servers

The intranet firewall configuration requires a new Tivoli Enterprise Portal Server
interface definition: proxy host 192.168.1.100 and port 15003.

The Internet DMZ configuration requires a new Tivoli Enterprise Portal Server
interface definition.

The Internet configuration uses the same Tivoli Enterprise Portal Server ″internet″
interface definition as the previous scenario: proxy host 198.210.32.34 and port
15002.

In this scenario, the monitoring server and agents cannot be installed on the Tivoli
Enterprise Portal Server computer.

Figure 18 on page 133 shows the following two-part configuration:

v Intranet firewall with NAT through the firewall to the external Web server uses
http://192.168.1.100, and without NAT inside the DMZ to the integral Web
server uses http://10.10.10.10:1920///cnp/client
v Internet firewall with NAT through the firewall to the external Web server uses
http://198.210.32.34.

132 IBM Tivoli Monitoring: Installation and Setup Guide

Figure 18. Two host addresses, intranet and Internet, with integral and external Web servers

The intranet firewall configuration uses the same Tivoli Enterprise Portal Server
interface definition (named ″intranet″) as in the previous scenario:
http://10.10.10.10; proxy host 192.168.1.100; and port 15003.

The intranet DMZ configuration uses the default Tivoli Enterprise Portal Server
interface definition. Tivoli Enterprise Portal Server interface definition: host
192.168.33.33; proxy host 198.210.32.34; port 15002; and proxy port 444.

In this scenario, the monitoring server and agents cannot be installed on the Tivoli
Enterprise Portal Server computer.

Chapter 9. Additional Tivoli Enterprise Portal configuration 133

134 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 10. Deploying monitoring across your environment
IBM Tivoli Monitoring 6.1 adds the ability to deploy monitoring agents from a
central location, the monitoring server. Just as there are two types of monitoring
agents, there are two types of agent deployment:
v OS agent deployment from the installation image or using the tacmd createNode
command
v Non-OS agent (such as the DB2 agent) deployment using the Tivoli Enterprise
Portal GUI (for other non-OS agents) or the tacmd addSystem command

The following table describes the steps required to set up and manage remote
agent deployment:
Table 38. Remote agent deployment tasks
Goal Where to find information
Create and populate the agent deploy depot “Populating your agent depot”
with installable agent images.
View and change the contents of the agent “Managing your agent depot” on page 139
depot.
Use one agent depot for all the monitoring “Sharing an agent depot across your
servers in your monitoring environment. environment” on page 139
Deploy an OS agent. “Deploying OS agents” on page 140
Deploy a non-OS agent. “Deploying non-OS agents” on page 142

You can also use the remote agent deployment function to configure deployed
agents and install maintenance on your agents. For information, see the IBM Tivoli
Monitoring Administrator's Guide. You can also see the Appendix E, “Command
reference,” on page 187 for the commands that you can use to perform these tasks.

Populating your agent depot

The agent depot is an installation directory on the monitoring server from which
you deploy agents and maintenance packages across your environment. Before you
can deploy any agents from a monitoring server, you must first populate the agent
depot with bundles. A bundle is the agent installation image and any prerequisites.

When you add a bundle to the agent depot, you need to add the bundle that
supports the operating system to which you want to deploy the bundle. Because
the different IBM Tivoli Monitoring components provide different CDs for each
platform type (for example, Windows, AIX and Solaris, HP-UX, Linux), you need
to add the bundle from the specific platform CD for the component. For example,
if you want to deploy a DB2 agent bundle to a computer running HP-UX, add the
HP-UX-specific agent bundle to the depot. If your depot directory is on Windows
and you want to deploy the DB2 agent to HP-UX, load the HP-UX bundle from
the DB2 agent CD for HP-UX.

You can have an agent depot on each monitoring server in your environment or
share an agent depot, as described in “Sharing an agent depot across your
environment” on page 139. If you choose to have an agent depot for each
monitoring server, you can customize the agent depot based on the types of

© Copyright IBM Corp. 2005 135

 bundles that you want to deploy and manage from that monitoring server. For
example, if you have a monitoring server dedicated to monitoring the DB2 agents
in your environment, populate the depot with DB2-related agent bundles.

Note: Agent depots cannot reside on a z/OS monitoring server.

There are two methods to populate the agent depot:

v “Populating the agent depot from the installation image”
v “Populating the agent depot with the tacmd addBundles command” on page 138

Populating the agent depot from the installation image

Use the following sections to populate your agent depot from the installation
image:
v “Windows: Populating the agent depot during installation”
v “Linux and UNIX: Populating the agent depot during installation” on page 137

You can use the installation image to populate the agent depot only when you are
populating the depot with bundles for the same operating system as your
monitoring server. For example, you can use the installation image to add a bundle
for a Windows agent to a Windows monitoring server, but you cannot use the
Linux installation image to add a Linux bundle to a Windows monitoring server. If
you need to add bundles for operating systems other than that used by your
monitoring server, use the tacmd addBundles command, as described in
“Populating the agent depot with the tacmd addBundles command” on page 138.

Windows: Populating the agent depot during installation

The procedure to populate the agent depot from the Windows installation image
differs based on the installation image (base IBM Tivoli Monitoring or application
agent) that you are using. Use the procedure below that applies to the image you
are using:
v “Base IBM Tivoli Monitoring installation image”
v “Application agent installation image” on page 137

Base IBM Tivoli Monitoring installation image: Use the following steps to
populate the agent depot from the IBM Tivoli Monitoring installation image:
1. Launch the installation wizard by double-clicking the setup.exe file in the
\Windows subdirectory of the installation image.
2. Select Modify on the Welcome window and click Next.
3. Click OK the warning message regarding existing components on this
computer.
4. Click OK on the Add or Remove Features window without making any
changes. (Do not clear any selected items because this removes them from the
computer.)
5. On the Agent Deployment window, select the agents that you want to add to
the depot and click Next.
6. Review the installation summary and click Next to begin the installation.
After the agents are added to the agent depot, a configuration window (called
the Setup Type window) is displayed.
7. Clear all selected components. You have already configured all components on
this computer and do not need to reconfigure any now. Click Next.
8. Click Finish to complete the installation.
9. Click Finish on the Maintenance Complete window.

136 IBM Tivoli Monitoring: Installation and Setup Guide

Application agent installation image: Use the following steps to populate the
agent depot from an application agent installation image:
1. Launch the installation wizard by double-clicking the setup.exe file in the
\Windows subdirectory of the installation image.
2. Select Next on the Welcome window.
3. Click Next on the Select Features window without making any changes.
4. On the Agent Deployment window, select the agents that you want to add to
the depot and click Next.
5. Review the installation summary and click Next to begin the installation.
After the agents are added to the agent depot, a configuration window (called
the Setup Type window) is displayed.
6. Clear all selected components. You have already configured all components on
this computer and do not need to reconfigure any now. Click Next.
7. Click Finish to complete the installation.

Linux and UNIX: Populating the agent depot during installation

Use the following steps to populate the agent depot from the Linux or UNIX
installation image:
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). 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 asked whether 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 (requires TEMS).
3) Exit install.

Type 2 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 in and press Enter.
6. Press Enter to display the agreement.
7. Type 1 to accept the agreement and press Enter.
8. Type the number that corresponds to the agent or agents that you want to add
to the agent depot and press Enter. If you are going to add more than one
agent, use a comma (,) to separate the numbers.
To select all available agents, type all.
You can select multiple agents with consecutive corresponding numbers by
typing the first and last numbers for the agents, separated by a hyphen (-). For
example, to add all of the agents between 8 and 12, type 8-12.
To clear an agent that you previously selected, type the number for the agent
again.

Note: Use the following keys to navigate the list of agents:

U Moves up a line in the list.
D Moves down a line in the list.

Chapter 10. Deploying monitoring across your environment 137

 F Moves forward one page in the list.
B Moves back one page in the list.
9. When you have specified all the agents that you want to add to the agent
depot, type E and press Enter to exit.

Populating the agent depot with the tacmd addBundles

command
To populate the agent depot using the tacmd addBundles command, run the
following command:
tacmd addBundles [-i IMAGE_PATH]
[-t PRODUCT_CODE]
[-p OPERATING_SYSTEM]
[-v VERSION]
[-n]
[-f]

For the full syntax, including parameter descriptions, see “tacmd addBundles” on
page 188.

Examples:
v The following example copies every agent bundle, including its prerequisites
into the agent depot on a UNIX from the installation media (cd image) located
at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix
v The following example copies all agent bundles for the Oracle agent into the
agent depot on a UNIX computer from the installation media (cd image) located
at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t or
v The following example copies all agent bundles for the Oracle agent into the
agent depot on a Windows computer from the installation media (cd image)
located at D:\WINDOWS\Deploy:
tacmd addbundles -i D:\WINDOWS\Deploy -t or
v The following example copies the agent bundle for the Oracle agent that runs on
the AIX version 5.1.3 operating system into the agent depot on a UNIX
computer from the installation media (cd image) located at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t or -p aix513

By default, the tacmd addBundles command puts the agent bundle in the location
defined in the monitoring server configuration file for DEPOTHOME. If you want
to change this location, do the following before you run the tacmd addBundles
command:
1. Open the KBBENV monitoring server configuration file located in the
<itm_installdir>\CMS directory on Windows and the
<itm_installdir>/tables/<tems_name> directory on Linux and UNIX.
2. Locate the DEPOTHOME variable. By default, the agent depot is located in the
<itm_installdir>/CMS/depot directory on Windows and
<itm_installdir>/tables/<tems_name>/depot directory on UNIX.
3. Type the path to the directory that you want to use for the agent depot.
4. Save and close the file.

138 IBM Tivoli Monitoring: Installation and Setup Guide

Managing your agent depot
Use the following commands to manage your agent depot:
Table 39. Agent depot management commands
Command Description
“tacmd listBundles” on page 203 Lists the details for one or more bundles
available to be added to the local agent
depot.
“tacmd removeBundles” on page 207 Deletes one or more bundles from the local
agent depot.
“tacmd viewDepot” on page 216 Lists the types of bundles available in either
the local or remote agent depot.

See the Appendix E, “Command reference,” on page 187 for the full syntax of these
commands.

Sharing an agent depot across your environment

If your monitoring environment includes multiple monitoring servers (a hub
monitoring server and remote monitoring servers), you can put your agent depot
in a central location, such as a shared file system, and access the depot from all of
the monitoring servers.

After populating your agent depot with either of the methods described in
“Populating your agent depot” on page 135, use the following steps to share the
agent depot:
1. Open the KBBENV monitoring server configuration file located in the
<itm_installdir>\CMS directory on Windows and the
<itm_installdir>/tables/<tems_name> directory on Linux and UNIX.
2. Locate the DEPOTHOME variable. By default, the agent depot is located in the
<itm_installdir>/CMS/depot directory on Windows and
<itm_installdir>/tables/<tems_name>/depot directory on UNIX.
3. Type the path to the shared agent depot for the DEPOTHOME variable.
4. Save and close the file.

If you are using a Windows monitoring server connecting to a depot on another

Windows computer, you must set the service ID for the Windows monitoring
server to "Administrator." Also, instead of specifying a mapped drive letter for the
path to the depot directory, use the UNC path (such as \\server\share).

Use the following steps to change the service ID:

1. From the Control Panel, double-click Administrative Tools.
2. Double-click Services.
3. Right-click Tivoli Enterprise Monitoring Svcs and click Properties.
4. On the Log On tab, select This Account.
5. Type Administrator in the This Account field.
6. Type the password for the administrator in the Password field. Confirm the
password by typing it again in the Confirm password field.
7. Click Enable.

Chapter 10. Deploying monitoring across your environment 139

 If the Administrator user does not have Logon as a service right, you are
prompted to add it.

Deploying OS agents
Before you can deploy any non-OS agent, you must first install an OS agent on the
computer where you want the non-OS agent to be deployed. In addition to
monitoring base OS performance, the OS agent also installs the required
infrastructure for remote deployment and maintenance.

Note: Ensure that you have populated your agent depot, as described in
“Populating your agent depot” on page 135, before attempting to deploy
any agents.

You can install the OS agent locally, as described in “Installing monitoring agents”
on page 64 or remotely using the tacmd createNode command.

The tacmd createNode command creates a directory on the target computer called
the node. This is the directory into which not only the OS agent is installed, but
where any non-OS agents are deployed.

The tacmd createNode command uses one of the following protocols to connect to
the computers on which you want to install the OS agent:
v Server Message Block (SMB), used primarily for Windows servers
v Secure Shell (SSH), used primarily by UNIX servers, but also available on
Windows
v Remote Execution (REXEC), used primarily by UNIX servers, but not very
secure
v Remote Shell (RSH), used primarily by UNIX servers, but not very secure
You can specify a protocol to use; if you do not, the tacmd createNode command
selects the appropriate protocol dynamically.

Requirements for the tacmd createNode command

Before you can use the tacmd createNode command to deploy OS agents, ensure
the following:
v The user ID that you are going to use during the deployment has administrative
privileges on the target computer.
v Any computer to which you want to deploy the OS agent must have a
supported protocol installed.
v Security in your environment should be configured to permit createNode to pass
through the firewall, using the protocol that you specify in the command
parameters.
v On Windows computers:
– SMB requires that the default, hidden, and administrative share are available
on the drive being accessed and on the drive that hosts the System temporary
directory.
– SMB signing is not supported when connecting using SMB. The computer to
which you are deploying an OS agent cannot require SMB signing.
– For Windows XP, disable Simple File Sharing. Simple File Sharing requires
that all users authenticate with guest privileges. This is not supported for
createNode. To disable Simple File Sharing, do the following:
1. Open the Windows Explorer.

140 IBM Tivoli Monitoring: Installation and Setup Guide

 2. Click Tools → Folder Options.
3. Click the View tab.
4. Scroll through the list of settings to Use Simple File Sharing.
5. Clear the check box next to Use Simple File Sharing and click OK.
– For Windows XP computers with Service Pack 2, disable the Internet
Connection Firewall.
– For Windows XP computers, set Network Access Sharing and Security to
″Classic - local users authenticate as themselves.″ Use the following steps:
1. From the Control Panel, double-click Administrative Tools.
2. Double-click Local Security Policy.
3. Expand Local Policies and click Security Options.
4. Right-click Network access: Sharing and security for local accounts and
click Properties.
5. Select Classic - local users authenticate as themselves from the list and
click OK.
– For all Windows computers, enable remote registry administration. (This is
enabled by default.)
v On UNIX systems, if you are using the RSH protocol, run the tacmd createNode
command as root on the monitoring server.
v If you are deploying the OS agent to a UNIX or Linux computer, that computer
must have either the ksh or bash shell.
v If you are using SSH (for either Windows or UNIX), configure SSH on the target
computers to permit the use of password authentication. To permit this, do the
following:
1. Edit the /etc/ss/sshd_config file on the target computer.
2. Locate the following line:
PasswordAuthentication no
3. Change the no to yes and save the file.
4. Restart the daemon.

Note: If you are using private key authentication in your environment, you do
not need to set SSH to permit password authentication.

Using the tacmd createNode command

To deploy an OS agent using the tacmd createNode command, run the following
command:
tacmd createNode [-h HOST_NAME]
[{smb|ssh|rexec|rsh}://]HOST[:PORT]]
[-u USERNAME]
[-w PASSWORD]
[-o NAME=VALUE ...]
[-d NODEDIR]
[-i IMAGE_PATH]
[-p NAME=VALUE ...]
[-f]

For the full syntax, include parameter descriptions, see “tacmd createNode” on
page 196.

For example, the following command deploys the UNIX OS monitoring agent on
the server1.ibm.com computer in the /opt/IBM/ITM directory. The installation is
done as the root user.

Chapter 10. Deploying monitoring across your environment 141

 tacmd createNode -h server1.ibm.com -d /opt/IBM/ITM -u root

Important: Unless you specifically indicate otherwise, the agent that you deploy
using this command assumes that the monitoring server to which it
connects is the monitoring server from which you run the command.
The agent also uses the default settings for the communications
protocol (IP.PIPE for protocol type and 1918 for the port). To change
these defaults (especially if you are not using the IP.PIPE protocol), use
the following property (specified with the -p parameter) when running
the command: SERVER=[PROTOCOL://][HOST|IP][:PORT]. For
example, SERVER=IP.PIPE://server1.ibm.com:1918.

Deploying non-OS agents

You can deploy non-OS agents through the Tivoli Enterprise Portal or from the
command line.
Notes:
1. The deployment and configuration of agents varies depending on the specific
agent. The following procedures provide generic deployment information. For
the exact values required for your agent, see the configuration information in
the user’s guide for the agent.
2. Ensure that you have populated your agent depot, as described in “Populating
your agent depot” on page 135, before attempting to deploy any agents.
3. You must have already installed or deployed an OS agent on the computer
where you are now deploying the non-OS agent.

Deploying through the portal

Use the following steps to deploy an agent through the portal GUI:
1. Open the Tivoli Enterprise Portal.
2. In the Navigation tree, navigate to the computer where you want to deploy the
agent.
3. Right-click the computer and click Add Managed System.
4. Select the agent that you want to deploy and click OK.
5. Complete the configuration fields required for the agent. For information about
these fields, see the configuration documentation for the agent that you are
deploying.
6. Click Finish.
7. If the computer where you are deploying the agent already has a version of
that agent installed, you can stop the deployment, add a new instance of the
agent, if possible, or reconfigure the existing agent.
8. Click Finish on the message that tells you that deployment was successful.

Deploying through the command line

Run the following command to deploy an agent from the command line:
tacmd addSystem -t pc
[-n MANAGED-OS]
[-p NAME=VALUE ...]

See “tacmd addSystem” on page 190 for the full syntax of this command, including
parameter descriptions. See Appendix D, “IBM Tivoli Product Codes,” on page 185
for a list of product codes for agents. You can also run the cinfo command to list
the product codes for agents installed on the current computer.

142 IBM Tivoli Monitoring: Installation and Setup Guide

 For example, the following command deploys the Universal Agent (type um) to
the stone.ibm.com computer and specifies the UA.CONFIG property:
tacmd addSystem -t um -n stone.ibm.com:LZ -p UA.CONFIG="file_unix.mdl"

Each agent bundle has its own unique configuration parameters that you need to
provide in this command. If you have an installed agent of the same type that you
want to deploy, you can view the configuration parameters by running the
following command:
tacmd describeSystemType -t pc -p platform

You can also get more information about agent-specific parameters in the agent
user's guide for the agent that you want to deploy.

Deploying a Universal Agent

You can use both of the deployment methods described in the previous sections to
deploy a Universal Agent instance. When you deploy the Universal Agent, you
specify an .mdl file and any scripts referenced by that .mdl file. Before you can
deploy the Universal Agent, put the .mdl file in the agent depot in a UACONFIG
subdirectory and the scripts in a UASCRIPT subdirectory. You must create both of
these subdirectories. Use the agent depot on the monitoring server to which the
Universal Agent connects.

Chapter 10. Deploying monitoring across your environment 143

144 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 11. Configuring the Warehouse Proxy for the Tivoli
Data Warehouse
With Tivoli Data Warehouse, you can analyze historical trends from monitoring
agents. The Tivoli Data Warehouse uses a DB2, Oracle, or Microsoft SQL Server
database to store historical data collected across your environment. You can
generate warehouse reports for short term and long term data through the Tivoli
Enterprise Portal. You can also use third-party warehouse reporting software, such
as Crystal Reports or Brio, to generate long term data reports. Warehouse reports
provide information about the availability and performance of your monitoring
environment over a period of time.

The Tivoli Data Warehouse uses the Warehouse Proxy agent to move data from
monitoring agents or the monitoring server to the data warehouse database. The
Warehouse Proxy is an ODBC export server for warehousing historical data. It is a
special agent that uses an ODBC connection to transfer historical data collected
from agents to a database. You can then analyze this data using the workspaces in
the Tivoli Enterprise Portal or any third-party software.

Note: The Warehouse Proxy agent is supported only for Windows computers,
although your Tivoli Data Warehouse can use a database on a Linux or
UNIX computer.

The Warehouse Summarization and Pruning agent provides the ability to

customize the length of time for which to save data (pruning) and how often to
compress data (summarization). For information about the Warehouse
Summarization and Pruning agent, see the IBM Tivoli Monitoring Administrator's
Guide.

If you do not intend to use historical reporting or save historical data to a database
for reference, then you do not need to install or configure the Warehouse Proxy.

The following table outlines the steps to configure the Warehouse Proxy:
Table 40. Warehouse Proxy configuration steps
Step Where to find information
Review the planning information regarding “Planning considerations for the Tivoli Data
estimating the size of database you need for Warehouse” on page 30
the amount of historical data you plan to
store in the Tivoli Data Warehouse.
Create the Warehouse Proxy user. “Creating a user for the Warehouse Proxy”
on page 147
Create the Tivoli Data Warehouse database. “Create the Tivoli Data Warehouse database”
on page 147
Create the ODBC connection to the database. “Setting up the ODBC connection” on page
148

© Copyright IBM Corp. 2005 145

 Table 40. Warehouse Proxy configuration steps (continued)
Step Where to find information
Install the Warehouse Proxy. If your RDBMS is on Windows, for the best
performance, install the Warehouse Proxy on
the same computer as the database that you
plan to use as the data warehouse. See
“Installing monitoring agents” on page 64
for installation information.
Configure and register the Warehouse Proxy. “Configuring and registering the Warehouse
Proxy” on page 151
Customize the configuration of the “Additional environment variables that can
Warehouse Proxy by changing the be set for the Warehouse Proxy” on page 153
environment variables.

Warehouse Proxy planning

Consider the following when planning the deployment of your Warehouse Proxy
agent:
v You can use only one Warehouse Proxy per hub monitoring server. However, if
you have multiple hub monitoring servers, the Warehouse Proxy agents for
those monitoring servers can share a single Tivoli Data Warehouse database,
enabling you to consolidate your historical data in one location. To configure
multiple Warehouse Proxy agents to use the same warehouse, when you create
the ODBC connection for each Warehouse Proxy, point to the same remote
database and connect with the same user. See “Setting up a connection to a
remote database” on page 150 for information about setting up this type of
connection.
v The Warehouse Proxy agent is supported only on Windows computers. For
optimal performance, install the Warehouse Proxy on the same computer as the
Tivoli Data Warehouse database. However, because non-Windows operating
systems are supported for the Tivoli Data Warehouse database, you can install
the Warehouse Proxy on a Windows computer while using a non-Windows
computer, such as Linux or AIX, for the database.
v If you have a large monitoring environment, install the Warehouse Proxy and
the Warehouse Summarization and Pruning agent on different computers. If the
Tivoli Data Warehouse database is on a UNIX or Linux computer, install the
Warehouse Summarization and Pruning agent on the same computer as the
Tivoli Data Warehouse database. However, the Warehouse Summarization and
Pruning agent does not support all hardware configurations, so ensure that the
computer where you install this agent meets the requirements for the agent.
v The following databases are supported:
– DB2 Universal Database Version 8 Fix Pack 10 on AIX V5.3, Solaris V10,
Windows 2003 Server, SUSE Linux Enterprise Server 9 for Intel, and RedHat
Enterprise Linux 4 for Intel
– Oracle Version 9.2 and 10.1 on Solaris V10
– Microsoft SQL Server 2000 on Windows
v You can configure historical data collection to store data at any combination of
the monitoring server or the agents. To ensure that history data is received from
all sources, you must configure a common communication protocol between the
Warehouse Proxy and the component that is sending history data to it (either
from a monitoring server or from an agent).

146 IBM Tivoli Monitoring: Installation and Setup Guide

 For example, you might have a monitoring server configured to use both IP.UDP
and IP.PIPE. In addition, one agent might be configured with IP.UDP and a
second agent with IP.PIPE. In this example, configure the Warehouse Proxy to
use both IP.UDP and IP.PIPE.
v The default user ID that the Warehouse Proxy uses to access the database is
ITMUser.

Creating a user for the Warehouse Proxy

If you are using a DB2 database for the Tivoli Data Warehouse, you need a
Windows user with Administrator authority to use the Warehouse Proxy. You can
either have this user created automatically during the configuration of the
Warehouse Proxy or create a user manually, as described in “Create a Windows
user for a DB2 database.” If you are using an existing user, you can point to that
user during the configuration of the Warehouse Proxy.

If you are using a Microsoft SQL or Oracle database, you need to create a database
user. You must create this user manually before configuring the Warehouse Proxy,
as the configuration process does not create this user. See the documentation for
your database for information on how to create a database user.

Create a Windows user for a DB2 database

Use the following steps to create a Windows user:
1. Right-click the My Computers icon on the Windows desktop and click
Manage.
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 and Password fields. Confirm the password
by typing it again in the Confirm password field.
5. Clear User must change password at next logon.
6. Click Close.
7. Click the Groups folder.
8. Double-click Administrators in the right pane of the window.
9. Click Add in the Administrator Properties window.
10. Locate the new user you created (ITMUser) and select it.
11. Click Add.
12. Click OK and then OK again to close the Administrator Properties window.
13. Close the Computer Management window.

If you are configuring multiple Warehouse Proxy agents to connect to the same
database, ensure that you use the same user ID and password for each Warehouse
Proxy. This enables the Tivoli Data Warehouse to store all received data in one set
of tables, as opposed to one table for each Warehouse Proxy.

Create the Tivoli Data Warehouse database

The Warehouse Proxy agent sends data collected from the agents to the Tivoli Data
Warehouse database. You can use an IBM DB2, Oracle, or Microsoft SQL database
for the Tivoli Data Warehouse.

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 147
 If you are using Oracle V9.2, you must use upgrade the ODBC Driver to the 9.2.0.4
version or higher. You can download this driver from the Oracle company Web
site.

Also, if you are using an Oracle database, you must create the database with UTF8
encoding.

Before you create the Tivoli Data Warehouse database, review the database scaling
information in “Planning considerations for the Tivoli Data Warehouse” on page 30
to determine what size of database you need for your history collection. The
following procedure creates a very basic database; however, because your Tivoli
Data Warehouse will most likely need to be a large, high performance database,
have a database administrator create the database for you, following the
recommendations in “Planning considerations for the Tivoli Data Warehouse” on
page 30. Creating your database should include placing the database data files and
logs on multiple disks, possibly on SAN disks.

Use the following steps to create a basic database for the Warehouse Proxy.

Note: These steps are for IBM DB2. If you are using a different database, see that
database’s documentation for information.
1. Click Start → IBM DB2 → Command Line Tools → Command Window.
2. Run the following command:
db2 create database Warehous using codeset utf-8 territory US

You can use any database name - for this and the following configuration
procedure, we used the default of ″Warehous.″
3. Close the command window after the command runs.

Configuring your DB2 or Microsoft SQL database

If you are using DB2, set the DB2CODEPAGE=1208 environment variable as a
system variable on the Windows computer where the Warehouse Proxy is installed.

If you are using Oracle, set the NLS_LANG=AMERICAN-AMERICA.AL32UTF8

environment variable as a system variable on the Windows computer where the
Warehouse Proxy is installed.

After you set either of these environment variables, you must restart the Windows
computer.

Setting up the ODBC connection

The ODBC connection enables the Warehouse Proxy agent to export data to the
warehouse database. You can use a database installed on the same computer as the
Warehouse Proxy or on a different computer.

You have two choices when defining your warehouse database and connection
information:
v Use the native Windows ODBC Data Source configuration (described in this
section)
v Reconfigure the Warehouse Proxy agent through Manage Tivoli Enterprise
Monitoring Services (as described in the next section)

148 IBM Tivoli Monitoring: Installation and Setup Guide

 You must create your ODBC connection manually in the following scenarios:
v You are using a Microsoft SQL or Oracle database.
v You are using a remote Tivoli Data Warehouse
If you are using a local DB2 database, the ODBC connection can be created
automatically during the configuration of the Warehouse proxy.

If you are configuring multiple Warehouse Proxy agents to connect to the same
database, ensure that you use the same user ID and password in the ODBC
connection for each Warehouse Proxy. This enables the Tivoli Data Warehouse to
store all received data in one set of tables, as opposed to one table for each
Warehouse Proxy.

Use one of the following procedures to set up your ODBC connection through the
Windows ODBC Data Source configuration utility:
v “Setting up a connection to a local database”
v “Setting up a connection to a remote database” on page 150

Setting up a connection to a local database

Use the following steps to set up an ODBC connection to a database installed on
the same computer as the Warehouse Proxy:
v “Setting up a connection to a DB2 database”
v “Setting up a connection to a Microsoft SQL database” on page 150
v “Setting up a connection to an Oracle database” on page 150

Setting up a connection to a DB2 database

Use the following steps to set up an ODBC connection to a local DB2 database:
1. Open the Control Panel.
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, perform the following steps:
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, you see the data
source name, ITM Warehouse.
d. Enter ITMUser for the User ID.
e. Type a password for the user in the Password field. The default password is
"itmpswd1."
f. Click Connect.
g. A Connection test successful message is displayed.
h. Click OK.
i. Click OK to close the window.

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 149
 Setting up a connection to a Microsoft SQL database
Use the following steps to set up a connection to a local Microsoft SQL database:
1. Open the Control Panel.
2. Click Administrative Tools → Data Sources (ODBC)
3. Click Add in the System DSN tab in the ODBC Data Source Administrator
window.
4. Select SQL Server and click Finish.
5. Enter ITM Warehouse in the Name field.
6. Select the Microsoft SQL server that you want to connect to from the
drop-down list and click Next.
7. Select With SQL Server authentication using a login ID and password
entered by the user.
8. Enter ITMUser for the Login ID.
9. Type the Password for the ITMUser ID. The default password is "itmpswd1."
10. Click Next.
11. Click Next again.
12. Click Finish.
13. Click Test Data Source to test the connection to the database.
14. Click OK.

Setting up a connection to an Oracle database

Use the following steps to create an ODBC connection to a local Oracle database:
1. Open the Control Panel.
2. Click Administrative Tools → Data Sources (ODBC)
3. Click Add in the System DSN tab in the ODBC Data Source Administrator
window.
4. Select Microsoft ODBC for Oracle and click Finish.
5. Enter ITM Warehouse in the Data Source Name field.
6. Type ITMUser in the User Name field.
7. Type the database alias or connect string for the Oracle Server in the Server
field.
For example, the following is a connect string pointing to an Oracle database
on the myServer computer:
jdbc:oracle:thin:@myServer.ibm.com:1521:orcl
8. Click OK.

Setting up a connection to a remote database

Use the following steps to set up an ODBC connection to a database installed on a
remote computer, such as an AIX computer.

Before you can connect to a remote database, you must install the database client
software for the database to which you want to connect on the computer where the
Warehouse Proxy is installed.

Note: These steps create the ODBC driver for IBM DB2 as an example of how this
is done. If you are using a different database, these steps might vary. See
that database’s documentation for information.
1. On the Windows computer where you are installing the Warehouse Proxy,
open the Control Panel.

150 IBM Tivoli Monitoring: Installation and Setup Guide

 2. Click Administrative Tools → Data Sources (ODBC)
3. On the System DSN tab, click Add.
4. Select IBM DB2 ODBC DRIVER from the list.
5. Click Finish.
The ODBC IBM DB2 Driver window is displayed.
6. Type the name of the data source in the Data source name field.
7. Click Add next to the Database alias field.
The CLI/ODBC Settings window is displayed.
8. Enter ITMUser for the User ID.
9. Type a password for the user in the Password field. The default password is
"itmpswd1."
10. Click the TCP/IP tab.
11. Complete the following fields:

Field Description
Database name Type the name of the database that you
want to create the ODBC connection to.
Database alias Type the alias for the database.
Host name Type the host name for the computer where
the database is installed.
Port number Type the port number used to communicate
with the computer where the database is
installed.

12. Click OK.

13. Click OK to close the window.

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.
6. If you have already configured your ODBC data source connection and you
used the default values (as described in “Setting up the ODBC connection” on
page 148), click No when you are asked if you want to configure the data
source.
You must click Yes as described in the next step if any of the following applies
to you:
v You created your data source with a name other than "ITM Warehouse."
v You used a user ID other than ITMUser.
v You used a password other than the default password ("itmpswd1").
Clicking Yes sets the values in the Windows registry and enables the
Warehouse Proxy to retrieve them.

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 151
 7. If you have not configured the ODBC data source connection or if you have
configured the data source and you did not use the default values, 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 a different 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 the
Tivoli Data Warehouse database” on page 147 to create the database,
the name is "warehous." 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.″ This user ID is used to create the DB2 database for
Tivoli Data Warehouse.
Admin Password
The password for the database administrator. This password is used
to create the DB2 database for Tivoli Data Warehouse.
Database User ID
The name of the user that is used to connect to the Tivoli Data
Warehouse database. The default name is ″ITMUser.″
Database Password
Type a password for the database user. The default password is
"itmpswd1." 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 than what you used when you configured the
Tivoli Enterprise Portal Server, select Synchronize TEPS Warehouse
Information. This updates the portal server configuration with the same
values.

Note: This only applies when your portal server and warehouse proxy are
on the same computer.
d. Click OK.

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

152 IBM Tivoli Monitoring: Installation and Setup Guide

Additional environment variables that can be set for the Warehouse
Proxy
You can set the following environment variables to control the way that the
Warehouse Proxy works:
v “Database initialization”
v “Work queue”
v “Connection pool” on page 155
v “RPC threads and export requests” on page 155
v “Timeout” on page 155
You can set that these variables in the KHDENV file.

Database initialization
When the Warehouse Proxy starts, the following tests are done:
v Checks that the Warehouse Proxy can connect to the database.
v If the database is Oracle or Microsoft SQL, checks that the encoding is set to
UTF8.
v If the database is DB2, checks that a bufferpool of page size 8KB is created. If it
is not, one is created, along with three new tablespaces that use the 8KB
bufferpool. The bufferpool is called "ITMBUF8K" and the tablespaces are named
"ITMREG8K," "ITMSYS8K," and "ITMBUF8K."
v Creates a database cache that contains a list of all the tables and columns that
exist in the database.
If any of these tests fail, a message is written to the log file and messages are
displayed in the Event Viewer.

These tests are repeated every 10 minutes.

You can change this default start up behavior by changing the following
environment variables:
KHD_CNX_WAIT_ENABLE
Enables the Warehouse Proxy to wait in between attempts to connect to the
database. By default, this variable is set to Y. If you do not want the
Warehouse Proxy to wait, change the variable to N. However, this can
generate a large log file if the connection to the database fails with each
attempt.
KHD_CNX_WAIT
Defines the amount of time, in minutes, that the Warehouse Proxy waits
between attempts to connect to the database. The default value is 10
minutes.

Work queue
The work queue consists of a single STL (Standard Template Library in C++)
queue instance and a configurable number of work threads that run work places
on it. There are two primary configuration parameters that you can set. You can set
these parameters in the KHDENV file before starting the Warehouse Proxy.
KHD_QUEUE_LENGTH
The length of the KHD work queue. This is an integer that identifies the
maximum number of export work requests that can be placed on the work

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 153
 queue before the work queue begins rejecting requests. The default value is
1000. Setting this value to 0 means that the work queue has no limit.
KHD_EXPORT_THREADS
The number of worker threads exporting data to the database. The default
value is 10.

Queue performance statistics are enabled by setting the (UNIT:khd error) trace
parameter. If set, a performance summary for each worker thread and the work
queue is written to the KHD RAS log after the queue is stopped and has finished
all work (this occurs when the Warehouse Proxy is shut down). The following
statistics are reported:
v Thread statistics:
– Total suspensions: The number of times the thread was suspended. A thread
becomes suspended when the controlling application suspends the work
queue.
– Empty queue occurrences: The number of times the thread checked the queue
and found it empty.
– Null work occurrences: An error condition that indicates that the pointer to a
unit of work (in this case an export object reference) places on the queue was
NULL.
– Total waits: The total number of times the thread blocked, waiting for new
work.
– Max wait time: The maximum time, in seconds, that a thread waited for new
work.
– Min wait time: The minimum time, in seconds, that a thread waited for new
work.
– Total executions: The total number of times the thread completed a unit of
work successfully.
– Total execution time: The total time, in seconds, that all executions required.
– Max execution time: The maximum time, in seconds, that a single execution
required.
– Min execution time: The minimum time, in seconds, that a single execution
required.
v Queue statistics:
– Queue start time: The time that the worker threads for the queue started
processing work.
– Total work queue: The total number of units of work placed on the work
queue.
– Total work un-queued: The total number of units of work removed from the
work queue.
– Total rejected requests: The total number of work requests rejected by the
work queue. This occurs when the work queue is full.
– Total illegal queues: An "illegal" queue occurs when a unit of work is placed
on the queue and the current queue length is greater than the length defined
in the KHD_QUEUE_LENGTH variable. This is not an error condition.
During a data export, an export request is opened with the Warehouse Proxy.
At that time, the queue length is checked to see if the data export con
proceed. If the queue length does not exceed the KHD_QUEUE_LENGTH
variable, the export request is created and the data is sent from the client to
the Warehouse Proxy. After all data is received, the export request is placed
on the work queue, even if the queue length is greater than the

154 IBM Tivoli Monitoring: Installation and Setup Guide

 KHD_QUEUE_LENGTH variable. Other threads might have placed export
requests on the queue during the time that the data was being collected.
– Max queue size: The maximum size that the work queue has grown to. Note
that this might be greater than the size defined in the
KHD_QUEUE_LENGTH variable because of illegal queues.
– Total suspensions: The total number of time the work queue has been
suspended.

Connection pool
The Warehouse Proxy uses several pre-initialized ODBC connections to access the
target database. The use of these ODBC connection objects is synchronized through
a single connection pool. The connection pool is initialized when the Warehouse
Proxy starts.

You can configure the number of connections in the pool by defining the following
environment variable in the KHDENV file:
v KHD_CNS_POOL_SIZE: The total number of pre-initialized ODBC connection
objects available to the work queue export threads. The default value is 10.

All export work threads request connections from the connection pool and must
obtain a connection before the work of exporting data can continue.

You will only see the connections established when a request will be active. It is
important to set the number of worker threads to greater or equal to the number of
ODBC connections. To do this, set KHD_KHD_EXPORT_THREADS >=
KHD_CNX_POOL_SIZE.

RPC threads and export requests

In addition to the configurable environment variables discussed previously, the
standard agent framework provides some control over the scalability and
performance profile for the Warehouse Proxy. When the Warehouse Proxy starts, it
initializes RPC and registers a group of function pointers that respond to incoming
RPC calls.

Use the CTIRA_NCSLISTEN variable to set the number of RPC threads.

Timeout
You can set two environment variables to control the timeout. One variable is set
on the application agent, the other on the Warehouse Proxy.
v KHD_STATUSTIMEOUT: The time, in seconds, to wait for a status from the
Warehouse Proxy before sending an export request again. The default value is
900 seconds, or 15 minutes.
v KHD_SRV_STATUSTIMEOUT: The timeout value, in seconds, for the work
queue to perform work. The default value is 600 seconds, or 10 minutes.

Export requests are rejected by the Warehouse Proxy are the following four
reasons:
v The time between when an export request is sent to the work queue and when it
is extracted from the queue exceeds the timeout. If you have tracing for the
Warehouse Proxy set to ERROR, an error similar to the following is logged in
the Warehouse Proxy log file:

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 155
 REJECTED: The export for the originnode <OriginNodeName>, the application
<applicationName> and the table <tableName> has been rejcted for timeout
reason in stage END_QUEUE.
v The time between when an export request is sent to the work queue and when
the work queue starts to do existence checking in the database exceeds the
timeout. If you have tracing for the Warehouse Proxy set to ERROR, an error
similar to the following is logged in the Warehouse Proxy log file and the
WAREHOUSELOG table:
Sample data rejected for timeout reason at stage START EXPORT
v The time between when an export request is sent to the work queue and when
the work queue fetches all the rows in the sample exceeds the timeout. If you
have tracing for the Warehouse Proxy set to ERROR, a message similar to the
following is logged in the Warehouse Proxy log file and the WAREHOUSELOG
table:
Sample data rejected for timeout reason at stage START SAMPLE
v The time between when an export request is sent to the work queue and when
the work queue commits the rows in the database exceeds the timeout. If you
have tracing for the Warehouse Proxy set to ERROR, a message similar to the
following is logged in the Warehouse Proxy log file and the WAREHOUSELOG
table:
Sample data rejected for timeout reason at stage COMMIT

The KHD_SRV_STATUSTIMEOUT variable should be set less than

KHD_STATUSTIMEOUT by at least 60 seconds.

WAREHOUSELOG table
The WAREHOUSELOG table lets you know how many exports succeed and how
many failed because of an ODBC error or a TIMEOUT issue.

The WAREHOUSELOG table has the following columns:

ORIGINNODE
The name of the computer that made the request. This name is the node
name for the agent. For example, Primary::box1:NT.
OBJECT
The attribute group that submitted the request. For example, NT_System.
STARTQUEUE
The time when the request was inserted in the work queue. For example,
10508201154000000.
ENDQUEUE
The time when the request exited the work queue. For example,
10508201155000000.
STARTEXPORT
The amount of time that elapsed before the first row of the sample request
was retrieved. For example, 105082011562000000.
EXPORTTIME
The amount of time after the export request transaction was committed.
For example, 10508201157000000.
ROWSINSERTED
The number of row inserted in the database for the request. For example,
1000.

156 IBM Tivoli Monitoring: Installation and Setup Guide

ROWSRECEIVED
The number of rows retrieved from the RPC source. For example, 1000.
ROWSSKIPPED
This column is not used.
STARTTIME
The start time of the collection for that sample. For example,
10508150920000000.
ENDTIME
The end time of the collection for that sample. For example,
1050815092000000.
ERRORMSG
An error message when no rows are inserted in the database. The error
message can indicate an ODBC error or a TIMEOUT error. For example:
Sample data rejected for timeout reason at stage COMMIT EXPORT

Chapter 11. Configuring the Warehouse Proxy for the Tivoli Data Warehouse 157
158 IBM Tivoli Monitoring: Installation and Setup Guide
Chapter 12. Configuring IBM Tivoli Monitoring Web Services
(SOAP Server) on Windows
By default, all monitoring servers are enabled for Web Services. Use the following
sections to configure IBM Tivoli Monitoring Web Services (SOAP Server) on
Windows XP Professional Edition or Windows 2000 computers.

Note: You cannot make SOAP requests from IBM Tivoli Monitoring to earlier
SOAP servers (such as those in OMEGAMON V350).

The instructions in this chapter assume that you have a basic understanding of
SOAP, XML and XML Namespaces, and the Web Services Description Language
(WSDL).

For complete information about customizing the SOAP interface for your site, refer
to the IBM Tivoli Monitoring Administrator’s Guide.

The following table outlines the steps required to configure SOAP:

Table 41. Overview of SOAP Server configuration steps
Task Where to find information
Define the hubs with which your SOAP “Defining hubs”
Server communicates.
Create users and grant them access. “Adding users” on page 160
Verify that you have successfully configured “Verifying the configuration” on page 160
SOAP.

Defining hubs
In this step you use the Manage Tivoli Enterprise Monitoring Services to activate
the SOAP server and define hubs with which the SOAP server communicates.

Use the following steps to define SOAP hubs:

1. Open Manage Tivoli Enterprise Monitoring Services.
2. Right-click Tivoli Enterprise Monitoring Server.
3. Click Advanced → Configure SOAP Server Hubs.
4. Click Add Hub. The Hub Specification window is displayed:
5. Select the communications protocol from the Protocol menu.
6. Specify an alias name in the Alias field (For example: HUB2). Alias names
cannot be longer than 8 characters.
7. Do one of the following:
v If you are using TCP/IP or TCP/IP Pipe communications, complete the
following fields:
Table 42. TCP/IP Fields in Hub Specification Dialog
Field Description
Hostname or IP Address The host name or TCP/IP address of the
host computer.

© Copyright IBM Corp. 2005 159

 Table 42. TCP/IP Fields in Hub Specification Dialog (continued)
Field Description
Port The TCP/IP listening port for the host
computer.

v If you are using SNA communications, complete the following fields:

Table 43. SNA Fields in Hub Specification Dialog
Field Description
Network Name Your site SNA network identifier.
LU Name The LU name for the monitoring server. This
LU name corresponds to the Local LU Alias
in your SNA communications software.
LU6.2 LOGMODE The name of the LU6.2 logmode. Default:
CANCTDCS.
TP Name The Transaction Program name for the
monitoring server.

Note: If you are connecting to a remote monitoring server, the protocol

information must be identical to that used for the hub monitoring server.
8. Click OK. The server tree is displayed.

Adding users
In this step you define users on each hub and specify the access rights for each
user (query or update).

Use the following steps:

1. Select the server (click anywhere within the server tree displayed), if necessary.
2. Under Add User Data, type the user name. User IDs must be identical to those
specified for monitoring server logon validation. Access is restricted to only
that monitoring server to which a user has access.

Note: If you do not supply a user ID, all users are given permission to update
data.
3. Click the type of user access: Query or Update.
4. Click Add User. The server tree is updated, showing the user and type of
access.
5. To delete a user: Select the user name from the tree and click Delete Item.
6. To delete a hub: Click anywhere within the hub’s tree and click Clear Tree.

Verifying the configuration

In this step you verify that SOAP has been properly configured by starting the
SOAP client and making a request using the command line utility kshsoap.

Use the following steps:

1. Open a DOS window.
2. Change to the <install_dir>\cms directory.
3. In the current directory, create an ASCII text file named SOAPREQ.txt that
contains the following SOAP request:

160 IBM Tivoli Monitoring: Installation and Setup Guide

 <CT_Get><object>ManagedSystem</object></CT_Get>

Or if security has been enabled:

<CT_Get><userid>logonid</userid><password>password</password> \
<object>ManagedSystem</object></CT_Get>
4. Create another ASCII text file named URLS.txt that contains URLs that will
receive the SOAP request. For example: http://hostname:1920///cms/soap
5. Run the following command:
kshsoap SOAPREQ.txt URLS.txt

SOAPREQ.txt is the name of the file that contains the SOAP request and
URLS.txt is the name of the file that contains the URLs.
The kshsoap utility processes the SOAPREQ.txt file and displays the output of the
SOAP request in the DOS window. The SOAP request is sent to each URL listed in
URLS.txt, and the SOAP response from each URL displays in the DOS window.

For complete information about using the SOAP interface, refer to the IBM Tivoli
Monitoring Administrator’s Guide.

Chapter 12. Configuring IBM Tivoli Monitoring Web Services (SOAP Server) on Windows 161
162 IBM Tivoli Monitoring: Installation and Setup Guide
Appendix A. Installation worksheets
Use the following worksheets to gather information you need during the
installation of the IBM Tivoli Monitoring components:
v “Windows hub monitoring server worksheet” on page 164
v “Linux or UNIX hub monitoring server installation worksheet” on page 165
v “Windows remote monitoring server worksheet” on page 166
v “Linux or UNIX remote monitoring server installation worksheet” on page 167
v “Windows portal server worksheet” on page 168
v “Linux portal server worksheet” on page 169
v “Generic Windows monitoring agent worksheet” on page 170
v “Generic Linux or UNIX monitoring agent worksheet” on page 171
v “Windows portal desktop client worksheet” on page 172
v “Linux portal desktop client worksheet” on page 173
v “Monitoring server communications protocol details worksheet” on page 174

© Copyright IBM Corp. 2005 163

Windows hub monitoring server worksheet
Use the following worksheet to gather information for your installation of the hub
monitoring server on a Windows computer.
Table 44. Windows hub monitoring server installation worksheet
Host name of computer
IP address
IBM Tivoli Monitoring installation directory
Encryption key
Agents to install on this computer
Agents to add to the deployment depot

Program folder name

Monitoring server name
Communications protocol details See Monitoring server communications
protocol details worksheet.
Agents for which to add application support
data

164 IBM Tivoli Monitoring: Installation and Setup Guide

Linux or UNIX hub monitoring server installation worksheet
Use the following worksheet to gather information for the installation of the hub
monitoring server on a Linux or UNIX computer.
Table 45. Linux or UNIX hub monitoring server installation worksheet
Host name of computer
IP address
IBM Tivoli Monitoring installation directory
Encryption key
Monitoring server name
Communications protocol details See Monitoring server communications
protocol details worksheet.
KDC_PARTITION
NIC interface name ("Optional Primary
Network Name")
Agents to install on this computer
Agents for which to add application support
data

Agents to add to the deployment depot

Appendix A. Installation worksheets 165

Windows remote monitoring server worksheet
Use the following worksheet to gather information for the installation of the
remote monitoring server on a Windows computer.
Table 46. Windows remote monitoring server installation worksheet
Host name of computer
IP address
IBM Tivoli Monitoring installation directory
Encryption key
Agents to install on this computer

Agents to add to the deployment depot

Program folder name

Monitoring server name
Agents for which to add application support
data

Hub monitoring server name

Hub monitoring server host name
Hub monitoring server communications See Monitoring server communications
protocol details protocol details worksheet.

166 IBM Tivoli Monitoring: Installation and Setup Guide

Linux or UNIX remote monitoring server installation worksheet
Use the following worksheet to gather information for the installation of the
remote monitoring server on a Linux or UNIX computer.
Table 47. Linux or UNIX remote monitoring server installation worksheet
Host name of computer
IP address
IBM Tivoli Monitoring installation directory
Encryption key
Monitoring server name
KDC_PARTITION
NIC interface name ("Optional Primary
Network Name")
Agents for which to add application support
data

Hub monitoring server host name

Hub monitoring server communications See Monitoring server communications
protocol details protocol details worksheet.
Agents to add to the deployment depot

Appendix A. Installation worksheets 167

Windows portal server worksheet
Use the following worksheet to gather information for the installation of the portal
server on a Windows computer.
Table 48. Windows portal server worksheet
Installation location
Encryption key used on the hub monitoring
server
Program folder
Host name of the computer where you are
installing the portal server
Portal server database administrator ID
Portal server database administrator
password
Portal server database user ID (default =
TEPS)
Portal server database user password
Warehouse database administrator ID
Warehouse database administrator password
Warehouse database user ID (default =
ITMUser)
Warehouse database user password
Warehouse data source name (default = ITM
Warehouse)
Warehouse database name
Hub monitoring server host name
Hub monitoring server communications See Monitoring server communications
protocol details protocol details worksheet.

168 IBM Tivoli Monitoring: Installation and Setup Guide

Linux portal server worksheet
Use the following worksheet to gather information for the installation of the portal
server on a Linux computer.
Table 49. Linux portal server worksheet
Installation location
Encryption key for the hub monitoring
server
Host name for the hub monitoring server
Hub monitoring server communications See Monitoring server communications
protocol details protocol details worksheet.
NIC interface name (Primary Optional
Network Name)
DB2 instance name (default = db2inst1)
DB2 administrator ID (default = db2inst1)
DB2 administrator password
Portal server database name (default =
TEPS)
Portal server database user (default =
itmuser)
Portal server database user password
Warehouse database name (default =
WAREHOUS)
Warehouse database user (default = itmuser)
Warehouse database user password

Appendix A. Installation worksheets 169

Generic Windows monitoring agent worksheet
Use the following worksheet to gather information for the installation of a
monitoring agent on a Windows computer. Depending on the agent you are
installing, you might need additional information to configure the agent. See the
agent user's guide for more information.
Table 50. Generic Windows monitoring agent worksheet
Installation directory
Encryption key for the hub monitoring
server
Agents to install

Program folder name

Monitoring server host name
Monitoring server communications protocol See Monitoring server communications
details protocol details worksheet.

170 IBM Tivoli Monitoring: Installation and Setup Guide

Generic Linux or UNIX monitoring agent worksheet
Use the following worksheet to gather information for the installation of a
monitoring agent on a Linux or UNIX computer. Depending on the agent you are
installing, you might need additional information to configure the agent. See the
agent user's guide for more information.
Table 51. Generic monitoring agent for a Linux or UNIX computer worksheet
Installation directory
Encryption key for the hub monitoring
server
Agents to install

Agent product code or codes

Monitoring server host name
Monitoring server communications protocol See Monitoring server communications
details protocol details worksheet.
KDC_PARTITION
NIC interface name (Optional Primary
Network Name)
root user password
User group name
Optional user name

Appendix A. Installation worksheets 171

Windows portal desktop client worksheet
Use the following worksheet to gather information for the installation of a the
portal desktop client on a Windows computer.
Table 52. Windows portal desktop client worksheet
Installation directory
Encryption key for the monitoring server
Program folder name
Portal server host name
Monitoring server host name
Monitoring server communications protocol See Monitoring server communications
details protocol details worksheet.

172 IBM Tivoli Monitoring: Installation and Setup Guide

Linux portal desktop client worksheet
Use the following worksheet to gather information for the installation of a the
portal desktop client on a Windows computer.
Table 53. Linux portal desktop client worksheet
Installation directory
Encryption key for the monitoring server
Instance name for the portal server
Portal server host name

Appendix A. Installation worksheets 173

Monitoring server communications protocol details worksheet
Use the following worksheet to gather the communications protocol details for
your hub and remote monitoring servers.
Table 54. Monitoring server communications protocol details worksheet
IP.UDP Settings
Host name or IP address
Port number or port pools
IP.PIPE Settings
Host name or IP address
Port number
IP.SPIPE Settings
Host name or IP address
Port number
SNA Settings
Network name
LU name
LU 6.2 LOGMODE
TP name
Local LU alias

174 IBM Tivoli Monitoring: Installation and Setup Guide

Appendix B. Performing a silent installation of IBM Tivoli
Monitoring
This appendix provides information about installing IBM Tivoli Monitoring using
the silent installation method. This method of installation is useful for advanced
users who prefer to input installation information once through a response file
instead of repeatedly through an installation wizard.

You might run through the installation wizard one time to determine the values
that you need to set for your monitoring needs and then use silent installation to
install the rest of your environment. For more information about installing through
the installation wizard, see Chapter 5, “Installing IBM Tivoli Monitoring,” on page
47.

The following table outlines the steps for performing a silent installation of IBM
Tivoli Monitoring.
Table 55. Installation and configuration steps
Step Where to find detailed information
Assess your monitoring needs to determine Chapter 3, “Planning the installation of your
the best deployment of IBM Tivoli environment,” on page 21
Monitoring components.
Ensure you have the required hardware and “Hardware and software requirements” on
software. page 24
Gather any information required for “Specific information to have ready” on
successful installation (such as DB2 user page 21
information and security specifications).
Run the silent installation. “Creating and using a Windows response
file”

“Performing a silent installation on a Linux

or UNIX computer” on page 177
Install application support files on the “Installing support for agents on the
monitoring server, portal server, and portal monitoring server, portal server, and
desktop client. desktop client” on page 73
Start the portal client to verify that you can “Starting the Tivoli Enterprise Portal client”
view the monitoring data. on page 82

Creating and using a Windows response file

A sample Windows silent installation response file is provided on the product CD.
Use the following steps to edit that response file as appropriate for your
environment:
1. Locate the silent.txt file on the product installation CD. Copy this file to a
temporary directory on your system.
2. Open your copy of the silent.txt file in a text editor.
3. Change the parameters as appropriate for your environment. The silent.txt file
contains descriptions of all the parameters, including directions on how to use
them.

© Copyright IBM Corp. 2005 175

 Complete all of the steps listed in the file. Each line of the file must be either a
comment (containing a semi-colon in column one) or a meaningful statement
that starts in column one.

Note: If you want to use the TCP/IP protocol, make sure to specify ″IP.UDP.″ If
you specify ″TCP/IP,″ IP.PIPE is used by default.

Attention: Do not modify any other files that come with the installation (for
example, the SETUP.ISS file).
4. Save the file and close the editor.
5. Run the silent installation using one of the following methods:
v “Running the silent install from the command line with parameters”
v “Using SMS”

Note: If the installation fails for any reason, a log file, ″Abort IBM Tivoli
Monitoring <date> <time>.log,″ is created to document the problem. If the
installation fails before reading in the installation location, the log file is
written to Windows BOOT drive, normally the C:\ drive. If the installation
fails after reading the installation location, the log file is written to an
\install subdirectory in the installation directory. For example, if you use the
default installation directory, the log file is written to C:\ibm\itm\install.

Running the silent install from the command line with

parameters
Use the following steps to run the installation from the command line:
1. Start a DOS Command Shell.
2. From the shell, cd to the directory containing this installation (where setup.exe
and setup.ins reside).
3. Run setup as follows. You must specify the parameters in the same order as
listed below.
start /wait setup /z"/sfC:\temp\SILENT.TXT" /s /f2"C:\temp\silent_setup.log"
where:
/z″/sf″
Specifies the name of the installation driver you customized for your site.
This is a required parameter. This file must exist.
/s Specifies that this is a silent install. This causes nothing to be displayed
during installation.
/f2 Specifies the name of the InstallShield log file. If you do not specify this
parameter, the default is to create Setup.log in the same location as the
setup.iss file. In either case, the Setup program must be able to create and
write to this file.

Using SMS
Use the following steps:
1. Copy the all the installation files to a LAN-based disk that SMS will mount on
the desired computers. (Copy all files in the directory with setup.exe and
setup.ins.)
2. Replace the original SILENT.TXT file on the LAN disk with your modified
version.

176 IBM Tivoli Monitoring: Installation and Setup Guide

 3. Edit the PDF file located with setup.exe and change the Setup invocation as
follows:
Setup /z"/sfC:\temp\SILENT.TXT" /s /f2"C:\temp\silent_setup.log"

Performing a silent installation on a Linux or UNIX computer

Just as the interactive installation on Linux and UNIX requires both an installation
of code and then a separate configuration, so does the silent installation method.
Both the installation and configuration use parameter files to define what you are
installing or configuring. Sample installation and configuration parameter files are
shipped with IBM Tivoli Monitoring and with monitoring agents. The files are
located in the following locations:
v Silent installation files:
– On the product installation CD (both base IBM Tivoli Monitoring and agent
installation CDs)
– After installation, a sample file is located in the <install_dir>/samples
directory
v Silent configuration files: After you install the product, a configuration file for
each component that requires configuration is located in the
<install_dir>/samples directory. There is also a sample configuration file that you
can use to configure any component.

Before editing any of the response files, note the following syntax rules:
v Comment lines begin with a pound sign (#).
v Blank lines are ignored.
v Parameter lines are PARAMETER=value. Do not use a space before the
parameter; you can use a space before or after an equal sign (=).
v Do not use any of the following characters in any parameter value:
– Dollar sign ($)
– Equal sign (=)
– Pipe sign (|)

Use the following procedures to perform silent installations:

v “Installing components with a response file”
v “Configuring components with a response file” on page 179

Installing components with a response file

The silent_install.txt response file specifies the installation parameters for IBM
Tivoli Monitoring components. To use this file to perform a silent installation, edit
the file to identify what you want to install and then run the following command:
./install.sh -q -h <install_dir> -p <response_file>

where:
install_dir
Identifies the installation location for the IBM Tivoli Monitoring
component. The default installation location is /opt/IBM/ITM.
response_file
Identifies the response file that you edited to specify installation
parameters. Specify the absolute path to this file.

Appendix B. Performing a silent installation of IBM Tivoli Monitoring 177

 The parameters that you can configure in the silent_install.txt file vary depending
on the component that you are installing. Each of the files contains comments that
explain the options. The following procedure is an example of installing all
available components on one computer. Use this to get an idea of what type of
information you need to gather when you are setting up your own silent
installation.

Use the following steps to perform a silent installation on a UNIX computer:

1. Edit the silent_install.txt file.
2. Set the following parameters as appropriate for your environment:
Table 56. Silent installation parameters for UNIX
Parameter Definition
INSTALL_ENCRYPTION_KEY REQUIRED. The data encryption key used
to encrypt data sent between systems. This
key must be the same for all components in
your IBM Tivoli Monitoring environment.

Do not use the following characters in the

key:
v $
v =
v |
INSTALL_FOR_PLATFORM The operating system for which to install the
components. You can specify an architecture
code. If you do not specify an architecture
code, the operating system for the current
computer is used.
INSTALL_PRODUCT The product code for the components (or
"products") that you want to install. See
Appendix D, “IBM Tivoli Product Codes,”
on page 185 for a list of these codes.

You can specify "all" to install all available

components.

To install multiple components (but not all),

repeat this parameter for each component
that you want to install. For example:
INSTALL_PRODUCT=ms
INSTALL_PRODUCT=cj
INSTALL_PRODUCT=cq

This example installs the monitoring server,

portal server, and portal desktop client on a
Linux computer.
MS_CMS_NAME= If you are installing a monitoring server, use
this parameter to specify the name for the
monitoring server, such as HUB_hostname.
Do not specify an IP address or fully
qualified host name.

3. Save and close the file.

4. Run the following command to install IBM Tivoli Monitoring in the
/opt/IBM/ITM directory:
./install.sh -q -h /opt/ibm/itm -p /tmp/silent_install.txt

178 IBM Tivoli Monitoring: Installation and Setup Guide

Configuring components with a response file
You can use the itmcmd config command with the -p <filename> parameter to
configure IBM Tivoli Monitoring components silently.

The following sample configuration response files are provided with IBM Tivoli
Monitoring:
v ms_silent_config.txt: Used to configure the monitoring server
v cq_silent_config.txt: Used to configure the portal server
v cj_silent_config.txt: Used to configure the portal desktop client
v silent_config.txt: A generic configuration file used to configure agents that do not
require unique configuration parameters
v pc_silent_config.txt: A unique configuration file delivered with any agents that
require unique configuration parameters, for example, the database agents.

Use the following steps to configure a component using the silent method:
1. Edit the configuration file for the component that you want to configure.
2. Complete the parameters identified in the file. Each file contains comments that
define the available parameters and the values to specify.
3. Save the file and exit.
4. Run one of the following commands.
To configure the monitoring server:
./itmcmd config -S -p <response_file> -t <ms_name>
To configure the portal server, desktop client, or an agent:
./itmcdm config -A -p <response_file> pc

where:
<response_file>
The name of the configuration response file. Use an absolute path to
this file.
<ms_name>
The name of the monitoring server that you want to configure.
pc The product code for the component or agent that you want to
configure. See Appendix D, “IBM Tivoli Product Codes,” on page 185
for the list of product codes.

Appendix B. Performing a silent installation of IBM Tivoli Monitoring 179

180 IBM Tivoli Monitoring: Installation and Setup Guide
Appendix C. Firewalls
This appendix provides an overview of IBM’s implementation of firewall support.
It explains basic concepts and gives sample scenarios of various configurations.
This section does not include specific steps for configuring IBM Tivoli Monitoring
across a firewall; those steps can be found in the installation chapter of this guide.

Basic implementation
IBM Tivoli Monitoring supports most common firewall configurations, including
those that use address translation (application proxy firewall is a notable
exception). To enable this support, IBM Tivoli Monitoring uses the IP.PIPE socket
address family, a TCP-based protocol that opens a single port on the firewall for
communication by IBM Tivoli Monitoring components. If your target environment
includes a firewall between any IBM Tivoli Monitoring components, you must
specify IP.PIPE as your communication protocol during configuration. No other
special configuration is needed unless your firewall also uses address translation.

Implementation with address translation

Address translation is an enhanced security feature of some firewall configurations.
With this feature, components that must be reached across the firewall have two
unique, but corresponding addresses: the external address (valid for components
outside the firewall) and the internal address (valid for components inside the
firewall).

In IBM Tivoli Monitoring, the component that typically must be reached for
connection is the monitoring server; however, the Warehouse Proxy, which runs on
Windows as a server-type application, must also be accessible to clients and also
requires an external and internal address. A component on either side of the
firewall only knows about the address that is valid for its side (its “partition”).

To accommodate sites with address translation, IBM Tivoli Monitoring uses a

partition-naming strategy. This strategy requires two steps:
v The creation of a text file, called a partition file, as part of the configuration of a
hub or remote monitoring server (or Warehouse Proxy). The partition file
contains an entry that defines that component’s address in the other partition.
v The specification of a partition name (any alphanumeric string up to 32
characters) as part of the configuration of any agent, a hub or remote monitoring
server, or Warehouse Proxy. A partition name must be specified for each
component regardless of which side of the firewall it resides in.

Sample scenarios
In the sample scenarios, your site has one firewall that contains two partitions,
which are named OUTSIDE and INSIDE.

© Copyright IBM Corp. 2005 181

 Scenario 1: Hub monitoring server INSIDE and monitoring
agents OUTSIDE
The hub monitoring server is contained within the firewall in a partition named
INSIDE. A partition file named parthub.txt is included in this partition and
contains the following entry:
OUTSIDE ip.pipe: hub’s_external_address

OUTSIDE is the partition name outside the firewall and hub’s_external_address is

the address of the hub monitoring server that is valid for the agents.

As part of the configuration of each agent, specify the name of the partition that
each resides in OUTSIDE.

When an agent starts, parthub.txt is searched for an entry that matches the
partition name OUTSIDE and sees the monitoring server address that is valid for
the agents (the external address).

Scenario 2: Hub and remote monitoring servers INSIDE and

monitoring agents OUTSIDE
Note: In Scenarios 2 and 3, all agents report to the remote monitoring server.

As part of the configuration of the hub monitoring server, specify the name of the
partition that it resides in INSIDE. No partition file is needed because the only
component that reports to it (the remote monitoring server) is also inside the
firewall.

As part of the configuration of the remote monitoring server, specify the name of
the partition that it resides in INSIDE. A partition file, partremote.txt, must also be
created at the remote monitoring server. It contains the following entries:
OUTSIDE ip.pipe: remote’s_external_address

When configuring the agents (all of which are outside the firewall, reporting to the
remote monitoring server), specify the name of the partition that they reside in
OUTSIDE. When the agents start, partremote.txt is searched for an entry that
matches the partition name OUTSIDE and sees the remote monitoring server
address that is valid for them (the external address).

Scenario 3: Hub monitoring server INSIDE, remote monitoring

server and agents OUTSIDE
As part of the configuration of the hub monitoring server, specify the name of the
partition that it resides in INSIDE. Create a partition file, parthub.txt, containing
the following entry:
OUTSIDE ip.pipe: hub’s_external_address

OUTSIDE is the partition name outside the firewall and hub’s_external_address is

the address of the hub monitoring server that is valid for the remote monitoring
server.

As part of the configuration of both the agents and the remote monitoring server,
specify the name of the partition they reside in OUTSIDE.

182 IBM Tivoli Monitoring: Installation and Setup Guide

A partition file partremote.txt also must be created at the remote monitoring server.
It contains the following entry:
INSIDE ip.pipe: remote’s_internal_address

If the hub monitoring server needs to communicate with the remote monitoring
server (for example, to issue a report request from an agent that is connected to the
remote monitoring server), partremote.txt is searched for an entry that matches the
partition name INSIDE and sees the remote monitoring server address that is valid
for it (the internal address).

Appendix C. Firewalls 183

184 IBM Tivoli Monitoring: Installation and Setup Guide
Appendix D. IBM Tivoli Product Codes
The following table lists the product codes that identify the different IBM Tivoli
Monitoring components and agents. Use these codes when running commands.
Table 57. Component product codes
Component Product code
Active Directory monitoring agent 3z
DB2 monitoring agent ud
Endpoint monitoring agent tm
i5/OS monitoring agent a4
Linux OS monitoring agent lz
Microsoft Exchange Server monitoring agent ex
Microsoft SQL Server monitoring agent oq
Oracle monitoring agent or
Sybase Server monitoring agent oy
Tivoli Enterprise Monitoring Server ms
Tivoli Enterprise Portal browser client cw
Tivoli Enterprise Portal desktop client cj
Tivoli Enterprise Portal Server cq
Universal Agent um
UNIX Log Alert monitoring agent ul
UNIX OS monitoring agent ux
Warehouse Proxy hd
Warehouse Summarization and Pruning agent sy
Windows OS monitoring agent nt

© Copyright IBM Corp. 2005 185

186 IBM Tivoli Monitoring: Installation and Setup Guide
Appendix E. Command reference
There are three types of commands available in IBM Tivoli Monitoring:
v tacmd commands that are available on both Windows and UNIX computers
v UNIX-only commands (itmcmd commands, cinfo, SetPerm) that are available
only on UNIX computers
v IBM Tivoli Enterprise Console commands that you run on the event server to
configure the event synchronization between IBM Tivoli Monitoring and IBM
Tivoli Enterprise Console

tacmd CLI commands

This section provides reference information about the following commands:
v “tacmd addBundles” on page 188
v “tacmd addSystem” on page 190
v “tacmd configurePortalServer” on page 192
v “tacmd configureSystem” on page 194
v “tacmd createNode” on page 196
v “tacmd describeSystemType” on page 201
v “tacmd help” on page 202
v “tacmd listBundles” on page 203
v “tacmd listSystems” on page 204
v “tacmd login” on page 205
v “tacmd logout” on page 206
v “tacmd removeBundles” on page 207
v “tacmd restartAgent” on page 208
v “tacmd startAgent” on page 210
v “tacmd stopAgent” on page 212
v “tacmd updateAgent” on page 214
v “tacmd viewAgent” on page 215
v “tacmd viewDepot” on page 216
v “tacmd viewNode” on page 217

© Copyright IBM Corp. 2005 187

 tacmd addBundles
Description
Use the tacmd addBundles command to add one or more deployment bundles to
the local agent deployment depot. By default, this command also adds all
deployment bundles that are prerequisites of the deployment bundle being added,
if the prerequisite bundles do not already exist in the depot.

If you do not already have an agent depot, the bundles are added to the location
defined by the DEPOTHOME environment variable in the KBBENV environment
file.

This command must be run locally on a monitoring server containing a depot.

CLI syntax
tacmd addBundles {-i|--imagePath} IMAGEPATH [{-t|--product|--products}
PRODUCT ...] [{-p|--platform|--platforms} PLATFORM ...] [{-v|--version|--
versions} VERSION ...] [{-n|--noPrereq|--noPrerequisites }] [{-f|--force }]

where:
-i|--imagePath
The directory that contains the deployment bundles to be added to the
depot.
-t|--product|--products
The product code or codes of the agents to add. This value corresponds to
the value that is displayed in the Product Code field that is displayed by the
viewDepot or listBundles command.
-p|--platform|--platforms
The platform code or codes of the agents to add. This value corresponds to
the value that is displayed in the Host Type field that is displayed by the
viewDepot or listBundles command.
-v|--version|--versions
The version or versions of the agents to add. This value corresponds to the
value that is displayed in the Version field that is displayed by the
viewDepot command.
-n|--noPrereq|--noPrerequisites
Indicates that prerequisite bundles are not automatically added.
-f|--force
Installs any matching deployment bundles to the depot without prompting
for confirmation first.

CLI example
The following example copies every agent bundle, including its prerequisites into
the agent depot on a UNIX from the installation media (cd image) located at
/mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix

The following example copies all agent bundles for the Oracle agent into the agent
depot on a UNIX computer from the installation media (cd image) located at
/mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t or

188 IBM Tivoli Monitoring: Installation and Setup Guide

The following example copies all agent bundles for the Oracle agent into the agent
depot on a Windows computer from the installation media (cd image) located at
D:\WINDOWS\Deploy:
tacmd addbundles -i D:\WINDOWS\Deploy -t or

The following example copies the agent bundle for the Oracle agent that runs on
the AIX version 5.1.3 operating system into the agent depot on a UNIX computer
from the installation media (cd image) located at /mnt/cdrom/:
tacmd addbundles -i /mnt/cdrom/unix -t or -p aix513

Return values
See Table 58 on page 218.

Related commands
“tacmd listBundles” on page 203

“tacmd removeBundles” on page 207

“tacmd viewDepot” on page 216

Appendix E. Command reference 189

 tacmd addSystem
Description
Use the tacmd addSystem command to deploy a monitoring agent to a computer
in your IBM Tivoli Monitoring environment. The tacmd addSystem command
deploys an agent and other required components if they are not already installed
on the node.

Any computer to which you want to deploy an agent must already have an OS
agent installed. You can either install the OS agent using the installation wizard or
with the “tacmd createNode” on page 196 command.

Note: You cannot use this command to add a non-default Universal Agent
instance that you created manually. You must use the itmcmd config
command with the -o parameter to create additional Universal Agent
instances.

CLI syntax
tacmd addSystem {-t|--type} pc {-n|--node} MANAGED-OS {-p|--property}
NAME=VALUE ...

where:
-t|--type
Specifies the type of agent to add to the monitoring system. See
Appendix D, “IBM Tivoli Product Codes,” on page 185 for a listing of
agent product codes.
-n|--node
Identifies the node, the directory on monitoring system where the OS agent
is installed, to which you want to add the agent. The name of a node
includes the computer where the OS agent is installed and the product
code for the OS agent. For example, stone.ibm.com:LZ is the name of the
node on computer stone.ibm.com, which has a Linux OS agent installed.
-p|--property
Specifies SECTION.NAME=VALUE pairs that identify agent configuration
properties and their values, where SECTION specifies the name of the
section containing the key value pair, KEY specifies the name of the
configuration property, and VALUE specifies the property value.
See the agent user's guide for the agent that you are configuring for a list
of available configuration properties.
In addition to the agent-specific configuration properties, you can also
configure the Run-as settings, specifying the user ID under which an agent
runs. Use the following parameters:
_UNIX_STARTUP_.Username=<user>
On UNIX, the user name under which to run the agent. Note that
you can only use this option if the OS agent running on the UNIX
computer is started as the root user (or another user with
privileges to su). You cannot change the run-as setting if your OS
agent runs as a non-root user.
If you have already configured the run as user (for example,
through the Manage Tivoli Enterprise Monitoring Services utility),
this value defaults to what you have already set. If you have not

190 IBM Tivoli Monitoring: Installation and Setup Guide

 configured the run as user previously, the default user is the user
that is running the OS agent on the computer.
_WIN32_STARTUP_.Username=<user>
On Windows, the user name under which to run the agent.
If you have already configured the run as user (for example,
through the Manage Tivoli Enterprise Monitoring Services utility),
this value defaults to what you have already set. If you have not
configured the run as user previously, the default user is
LocalSystem (InteractWithDesktop=0).
_WIN32_STARTUP_.Password=<pwd>
The password for the run as user that you specified with
_WIN32_STARTUP_Username.
_WIN32_STARTUP_.LocalSystem={0|1}
Indicates whether you want to use the LocalSystem user to start
the agent. Use 1 to specify to use the user and 0 to specify not to
use the user.
You must also specify the
_WIN32_STARTUP_.InteractWithDesktop={0|1} parameter.
_WIN32_STARTUP_.InteractWithDesktop={0|1}
Indicates whether the LocalSystem can interact with the computer
desktop. Use 1 to specify that it can and 0 to specify that it cannot.

CLI example
tacmd addsystem -t um -n stone.ibm.com:LZ -p UA.CONFIG="file_unix.mdl"

This command deploys universal agent (type UA) to the monitoring system named
stone with the file_unix.mdl MDL file.

Return values
See Table 58 on page 218.

Related commands
“tacmd createNode” on page 196

“tacmd describeSystemType” on page 201 (to view configuration properties for an

installed agent)

“cinfo” on page 219 (to return the list of product codes installed on the computer)

Appendix E. Command reference 191

 tacmd configurePortalServer
Description
Use the tacmd configurePortalServer command to configure a user-defined portal
server data source. If the data source already exists, use this command to change
the configuration. If the data source does not exist, it is created by this command.
You can also use this command to remove a data source.

CLI syntax
tacmd configurePortalServer {-s|--dataSource} datasource {-p|--property|--
properties} name=value ... [{-d|--directory} install_dir] [{-f|--force}]

tacmd configurePortalServer {-s|--dataSource} datasource {-r|--remove}

[{-d|--directory} install_dir] [{-f|--force}]

tacmd configurePortalServer {-s|--dataSource} datasource {-v|--view}

[{-d|--directory} install_dir] [{-f|--force}]

where:
-s|--dataSource
The name of a new or existing data source.
-r|--remove
Removes the named data source.
-v|--view
Displays the configuration parameters for an existing data source. Run the
command against an existing data source to identify configuration
parameters that you can edit or to determine the configuration parameters
for a new data source of the same type.
Passwords displayed by this parameter are encrypted.
-p|--property|--properties
A list of property names and values required to configure the data source.
The list can be different for each data source type but usually includes at
least user ID (key name UID) and password (key name PWD). Property
values are encrypted before being stored to the configuration file or the
Windows Registry.
-d|--directory
The directory where the portal server is installed.
-f|--force
Performs actions without asking confirmation.

CLI example
The following example modifies the TEPS2 data source with user ID db2user and
password db2password. The TEPS2 data source is created if it does not already exist.
tacmd configureportalserver -s TEPS2 -p UID=db2user PWD=db2password

The following example displays the configuration settings for the TEPS2 data
source:
tacmd configureportalserver -s TEPS2 -v

The following output is displayed:

192 IBM Tivoli Monitoring: Installation and Setup Guide

DSN=TEPS2
UID=TEPS
PWD={AES256:keyfile:a}HW0LxUxCJ5tj9biXUWhCIQ==
CONNECTION_LIMIT=32

Return values
See Table 58 on page 218.

Appendix E. Command reference 193

 tacmd configureSystem
Description
Use the tacmd configureSystem command to edit configuration options of an
existing agent. The agent is restarted so the new configuration parameters can take
effect. Specify the configuration data through the parameter pair
SECTION.NAME=VALUE. If a parameter is specified with an equal sign but
without a value, the specified parameter is removed from the agent configuration.

You must specify at least one configuration parameter when you configure the
agent. If the agent requires no configuration parameters, use the -p parameter to
set the Run-as setting for the agent.

Note: You cannot use this command to configure a non-default Universal Agent
instance that you created manually. Use the itmcmd config command with
the -o parameter instead to configure a non-default Universal Agent
instance.

CLI syntax
tacmd configureSystem {-m|--system} SYSTEM {-p|--property} NAME=VALUE ...

where:
-m|--system
Identifies the agent (managed system) that you want to configure.
-p|--property
Specifies one or more SECTION.NAME=VALUE pairs that identify
configuration properties to update, where SECTION specifies the name of
the section containing the key value pair, KEY specifies the name of the
configuration property, and VALUE specifies the property value.
You must specify at least one property when you configure an agent. If you
don't have any agent-specific configuration properties, set the run as user,
as described below.
See the agent user's guide for the agent that you are configuring for a list
of available configuration properties.
In addition to the agent-specific configuration properties, you can also
configure the Run-as settings, specifying the user ID under which an agent
runs. Use the following parameters:
_UNIX_STARTUP_.Username=<user>
On UNIX, the user name under which to run the agent. Note that
you can only use this option if the OS agent running on the UNIX
computer is started as the root user (or another user with
privileges to su). You cannot change the run-as setting if your OS
agent runs as a non-root user.
If you have already configured the run as user (for example,
through the Manage Tivoli Enterprise Monitoring Services utility),
this value defaults to what you have already set. If you have not
configured the run as user previously, the default user is the user
that is running the OS agent on the computer.
_WIN32_STARTUP_.Username=<user>
On Windows, the user name under which to run the agent.

194 IBM Tivoli Monitoring: Installation and Setup Guide

 If you have already configured the run as user (for example,
through the Manage Tivoli Enterprise Monitoring Services utility),
this value defaults to what you have already set. If you have not
configured the run as user previously, the default user is
LocalSystem (InteractWithDesktop=0).
_WIN32_STARTUP_.Password=<pwd>
The password for the run as user that you specified with
_WIN32_STARTUP_Username.
_WIN32_STARTUP_.LocalSystem={0|1}
Indicates whether you want to use the LocalSystem user to start
the agent. Use 1 to specify to use the user and 0 to specify not to
use the user.
You must also specify the
_WIN32_STARTUP_.InteractWithDesktop={0|1} parameter.
_WIN32_STARTUP_.InteractWithDesktop={0|1}
Indicates whether the LocalSystem can interact with the computer
desktop. Use 1 to specify that it can and 0 to specify that it cannot.

CLI example
tacmd configureSystem -m stone:UA -p UA.CONFIG="file_unix.mdl"

This command reconfigures the universal agent on stone with the file_unix.mdl
MDL file.

Return values
See Table 58 on page 218.

Related commands
“tacmd addSystem” on page 190

Appendix E. Command reference 195

 tacmd createNode
Description
Use the tacmd createNode command to deploy an OS agent to a remote computer.
This command also creates a node, the directory into which not only the OS agent
is installed, but where any non-OS agents are deployed. The node is created on the
local computer if no host is specified.
Notes:
1. On UNIX computers, you must run the tacmd createNode command as a root
user.
2. After you run the tacmd createNode command, you must close and reopen any
open command line windows before you can run any tacmd commands. If you
are running this command remotely, you must also log out and log back into
IBM Tivoli Monitoring.

CLI syntax
tacmd createNode [{-h|--host} [{smb|ssh|rexec|rsh}://]HOST[:PORT]]
[{-u|--username} USERNAME [{-w|--password} PASSWORD]]
[{-o|--option|--options} NAME=VALUE ...] [{-d|--dir|--directory} NODEDIR]
[{-i|--imagePath} IMAGEPATH] [{-p|--property|--properties} NAME=VALUE ...]
[{-f|--force}]

where:
-h|--host
Identifies the computer on which to create a node. Optionally, a specific
connection protocol and a port can be specified. By default, all supported
protocols are attempted until a connection is successfully established on
one of them.
u|--username
A valid user ID on the specified computer.
-w|--password
The password for the specified user ID. You can specify a file that contains
multiple passwords, one per line. Each password is tried, in the order
specified, until a connection is successfully established.
-o|--option|--options
One or more configuration parameters that can be used to customize the
operation of this command. You can use the following options:
KEYFILE
The full path to an SSH private key file that, when specified, is
used to authenticate with the specified remote computer (which
must already have been configured to accept the private key). Use
KEYFILE when the SSH protocol is, or might be, in use, and you
want to use non-login based authentication.
PASSPHRASE
Use this option in conjunction with the KEYFILE option to enable
the specification of the passphrase (if any) that was used to encrypt
the private key file.
If you use the actual passphrase in this command, that passphrase
is visible in the process table for the current computer, where
anyone on can access it. If access to the computer is restricted to
only trusted personnel, this is not an issue.

196 IBM Tivoli Monitoring: Installation and Setup Guide

 However, if you need to provide the passphrase but do not want
to publish the passphrase, instead of using the passphrase as the
option value, specify the path to a secured local file that contains
the passphrase.
TIMEOUT
A positive integer that indicates the maximum amount of time, in
seconds, to wait for the current node creation to complete. If the
node creation exceeds this time limit, then the node creation
operation ends, and an error message is displayed. The default
value is 1800 seconds (30 minutes).

Note: In the event that a timeout is triggered, the node creation on

the remote host might continue and complete successfully.
However, if the timeout is exceeded, createNode does not
wait for results to be returned from the remote host and
reports a failure.
CONNECT_TIMEOUT
A positive integer that indicates the maximum amount of time, in
seconds, to wait for a successful connection through each
communications protocol being used to connect to the specified
remote computer. The default value is 60 seconds.
TEMP=temp_dir
Defines a temporary directory to use during the deployment of the
agent. By default, the itmcmd createNode command uses the /tmp
directory. Use the TEMP=temp_dir option if your /tmp directory
does not have enough space to accommodate the temporary files
needed for agent deployment.
-d|--dir|--directory
The location on the remote computer where you want to create the node.
This location must be specified as a directory, in absolute path format.
-i|--imagepath
The location on the local monitoring server in which to look for the
installation image for this OS agent.
-p|--property|--properties
A list of property names and values needed to configure the new OS agent.
Values can differ per operating system.
You can use the following properties for all operating systems:
ENCRYPT={NO|YES}
A Boolean flag that indicates whether or not to use SSL encryption
for node communication with the monitoring server. By default,
encryption is enabled for all communications. Accepted values are
NO and YES.
KEY=encryptionkey
The text to be used to encrypt the SSL communications. This value
must match the same value that was specified for the monitoring
server encryption.
IP.PIPE.PARTITION=path
The full path to a file that provides network name/address
translation that is valid for the current computer.

Appendix E. Command reference 197

 IP.SPIPE.PARTITION=path
The full path to a file that provides network name/address
translation that is valid for the current computer.
PROTOCOL|PROTOCOL1=protocol
Specifies the primary communications protocol used between the
node and the monitoring server. Accepted values are IP.UDP,
IP.PIPE, IP.SPIPE, SNA.
PROTOCOL2=protocol
Specifies a secondary communications protocol to use between the
node and the monitoring server. Accepted values are IP.UDP,
IP.PIPE, IP.SPIPE, SNA.
PROTOCOL3=protocol
Specifies a third communications protocol to use between the node
and the monitoring server. Accepted values are IP.UDP, IP.PIPE,
IP.SPIPE, SNA.
PORT=port_number
The port number to use for the current monitoring server
communications protocol. The defaults are the following:
v IP.UDP = 1918
v IP.PIPE = 1918
v IP.SPIPE = 3660
v SNA = n/a

Note: The specified port number must match the port number
being used by the monitoring server.
SERVER=tems_name
Enables you to specify a specific monitoring server. The default
value is the monitoring server from which you are running
createNode. This property accepts an option URL-style format,
which enables you to specify the primary communication protocol
and port number:
[{IP.UDP|IP.PIPE|IP.SPIPE|SNA}://][HOSTNAME][:PORT]
SNA_NETNAME=net_name
The Systems Network Architecture primary network name.
SNA_LOGMODE=logmode_name
The Systems Network Architecture one to eight character log mode
name.
SNA_LUNAME=lu_name
The Systems Network Architecture primary logical unit name.
SNA_TPNAME=tp_name
The Systems Network Architecture transaction program
specification. Accepted values are SNASOCKETS (default),
KDCLLBD, KDTMSNAP.QAUTOMON.
BACKUP={NO|YES}
A Boolean flag used to indicate whether or not to use a secondary
(back up) monitoring server for this node. By default, no backup is
specified. Accepted values are NO and YES.
BSERVER =backup_msname
Specifies a backup monitoring server.

198 IBM Tivoli Monitoring: Installation and Setup Guide

 BPROTOCOL|BPROTOCOL1=protocol
Specifies the primary communications protocol used between the
node and the secondary monitoring server. Accepted values are
IP.UDP, IP.PIPE, IP.SPIPE, SNA.
BPROTOCOL2=protocol
Specifies a secondary communications protocol to use between the
node and the secondary monitoring server. Accepted values are
IP.UDP, IP.PIPE, IP.SPIPE, SNA.
BPROTOCOL3=protocol
Specifies a third communications protocol to use between the node
and the secondary monitoring server. Accepted values are IP.UDP,
IP.PIPE, IP.SPIPE, SNA.
PORT=port_number
The port number to use for the secondary monitoring server
communications protocol. The defaults are the following:
v IP.UDP = 1918
v IP.PIPE = 1918
v IP.SPIPE = 3660
v SNA = n/a

Note: The specified port number must match the port number
being used by the monitoring server.
BSNA_NETNAME=net_name
The Systems Network Architecture primary network name for the
secondary monitoring server.
BSNA_LOGMODE=logmode_name
The Systems Network Architecture one to eight character log mode
name for the secondary monitoring server.
BSNA_LUNAME=lu_name
The Systems Network Architecture primary logical unit name for
the secondary monitoring server.
BSNA_TPNAME=tp_name
The Systems Network Architecture transaction program
specification for the secondary monitoring server. Accepted values
are SNASOCKETS (default), KDCLLBD,
KDTMSNAP.QAUTOMON.

The following parameter applies only to Windows computers:

FOLDER
The name of the folder under which to place the node components.
This is the folder name that is displayed in the Start menu.

The following parameter applies only to Linux and UNIX computers:

BIND.TO.NIC
Indicates a specific IP address for the node to bind to on
multi-homed computers.
-f|--force
Eliminates any interactive prompting.

Appendix E. Command reference 199

 CLI example
tacmd createnode -h stone.ibm.com -d /opt/IBM/ITM -u root

This example installs the OS agent in the /opt/IBM/ITM directory on

stone.ibm.com. The installation is performed as root.

Return values
See Table 58 on page 218.

Related commands
“tacmd addSystem” on page 190

200 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd describeSystemType
Description
Use the tacmd describeSystem command to display the configuration options that
are required for an agent type. If no version is supplied, configuration options for
the latest version are displayed.

This command can only be run from a Tivoli Enterprise Monitoring Server
containing a depot.

CLI syntax
tacmd describeSystemType {-t|--type} pc {-p|--platform} platform [{-v|--version}
VERSION]

where :
-t|--type
The product code for the agent that you want to describe.
-p|--platform
The operating system type of the managed system to describe.
-v|--version
The version of the agent to describe.

CLI example
tacmd describeSystemType –t UM –h WINNT -v 060100000

This command displays the configuration options that are available to use with the
configureSystem or addSystem commands for the Universal Agent (type UM) for
the Windows NT® platform WINNT, version 060100000.
tacmd describeSystemType –t UM –h WINNT

This command displays the configuration options that are available to use with the
configureSystem or addSystem commands for the latest version of the Universal
Agent (type UM) for the Windows NT platform WINNT.

Return values
See Table 58 on page 218.

Related commands
“tacmd configureSystem” on page 194

“tacmd addSystem” on page 190

Appendix E. Command reference 201

 tacmd help
Description
Use the tacmd help command to display the name of all the available CLI
commands, along with a short description of each command.

CLI syntax
tacmd help or tacmd ?

CLI example
tacmd help addSystem

or
tacmd ? addSystem

This command displays the help for the addSystem command.

Return values
See Table 58 on page 218.

202 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd listBundles
Description
Use the listBundles command to display the details of one or more deployment
bundles that are available for deployment to the local deployment depot.

This command must be run locally on a server containing a depot.

CLI syntax
tacmd listBundles {-i|--imagePath} IMAGEPATH [{-t|--product|--products}
PRODUCT ...] [{-p|--platform|--platforms} PLATFORM ...] [{-v|--version|--
versions} VERSION ...]

where:
-i|--imagePath
The directory that contains the deployment bundles to be listed.
-t|--product|--products
The product code or codes of the agents to list bundles for. This value
corresponds to the value that is displayed in the Product Code field that is
displayed by the viewDepot or listBundles command.
-p|--platform|--platforms
The platform code or codes of the products to list bundles for. This value
corresponds to the value that is displayed in the Host Type field that is
displayed by the viewDepot or listBundles command.
-v|--version|--versions
The version or versions of the products to list bundles for. This value
corresponds to the value that is displayed in the Version field that is
displayed by the viewDepot command

CLI example
tacmd listBundles –i D:\cdimage\bundles

This command displays details for all the deployment bundles in the
D:\cdimage\bundles directory.
tacmd listBundles –i /mnt/bundles –t ux –p aix513 –v 060100000

This command displays details for all the deployment bundles in the /mnt/bundles
directory where the bundle product type is ux, the bundle platform is aix513, and
the bundle version is 060100000.

Return values
See Table 58 on page 218.

Related commands
“tacmd addBundles” on page 188

“tacmd removeBundles” on page 207

“tacmd viewDepot” on page 216

Appendix E. Command reference 203

 tacmd listSystems
Description
Use the tacmd listSystems command to display a list of agents, optionally filtering
for only those on a given managed system or one or more product codes, or both.
The managed system name, product code, version, and status is displayed for each
agent.

CLI syntax
tacmd listSystems [{-n|--node} MANAGED-OS] [{-t|--type} pc ...]

where:
-n|--node
Identifies the node, the directory on monitoring system where the OS agent
is installed, for which you want to list the agents. The name of a node
includes the computer where the OS agent is installed and the product
code for the OS agent. For example, stone.ibm.com:LZ is the name of the
node on computer stone.ibm.com, which has a Linux OS agent installed.
-t|--type
Identifies one or more product type codes for which to filter. TYPE is scoped
to NODE level.

CLI example
tacmd listSystems

This command lists all of the systems in your enterprise.

tacmd listSystems –t UM

This command lists all of the systems in your enterprise with the product code UM
(universal agent systems).
tacmd listSystems –t NT

This command lists all of the systems in your enterprise with the product code NT
(NT nodes, or operating system agents). This command is effective for listing all of
the NT nodes in your enterprise.
tacmd listSystems –t NT UX LZ

This command lists all of the systems in your enterprise with product codes NT,
LZ, or UX (NT operating system agents). This command is effective for listing all
of the nodes in your enterprise.
tacmd listSystems –n Primary:STONE:NT –t UM

This command lists all of the systems on node Primary:STONE:NT with the
product code UM (universal agent).

Return values
See Table 58 on page 218.

204 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd login
Description
Use the tacmd login command to log into a monitoring server and create a
security token used by subsequent tacmd commands.

CLI syntax
tacmd login {-s|--server} {[PROTOCOL://]HOST[:PORT]} [{-u|--username}
USERNAME] [{-p|--password} PASSWORD] [{-t|--timeout} TIMEOUT]

where:
-s|--server
Specifies the host name of the Tivoli Enterprise Monitoring Server to log
into.
-u|--username
Specifies the user to authenticate.
-p|--password
Specifies the password of the user to authenticate.
-t|--timeout
Specifies the maximum number of minutes that can elapse between
invocations of tacmd before the user is denied access. The default timeout
is 15 minutes. The maximum timeout is 1440 minutes (24 hours).
If a user name and password are not specified, you are prompted for them.

CLI example
tacmd login –s pebble.ibm.com –u administrator –p mypassword –t 1440

This command logs into the Tivoli Enterprise Monitoring Server on pebble.ibm.com
with the user ID, administrator, the password, mypassword, and a login expiration
time of 1440 minutes.

Return values
See Table 58 on page 218.

Related commands
“tacmd logout” on page 206

Appendix E. Command reference 205

 tacmd logout
Description
Use the tacmd Logout command to log out of the monitoring server and disable
the security token created by the tacmd login command.

CLI syntax
tacmd Logout

CLI example
tacmd logout

Return values
See Table 58 on page 218.

Related commands
“tacmd login” on page 205

206 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd removeBundles
Description
Use the removeBundles command to remove one or more deployment bundles
from the local deployment depot.

This command must be run locally on a monitoring server containing a depot.

CLI syntax
tacmd removeBundles {-i|--imagePath} IMAGEPATH [{-t|--product|--products}
PRODUCT ...] [{-p|--platform|--platforms} PLATFORM ...] [{-v|--version|--
versions} VERSION ...] [{-f|--force }]

where:
-i|--imagePath
The directory to the depot that contains the deployment bundles to be
removed.
-t|--product|--products
The product code or codes of the agents to remove. This value corresponds
to the value that is displayed in the Product Code field that is displayed by
the viewDepot or listBundles command.
-p|--platform|--platforms
The platform code or codes of the agents to remove. This value
corresponds to the value that is displayed in the Host Type field that is
displayed by the viewDepot or listBundles command.
-v|--version|--versions
The version or versions of the agents to remove. This value corresponds to
the value that is displayed in the Version field that is displayed by the
viewDepot command.
-f|--force
Removes any matching deployment bundles from the depot without
prompting for confirmation first.

CLI example
tacmd removeBundles –i D:\cdimage\bundles

This command removes all of the deployment bundles in the D:\cdimage\bundles

directory from the local deployment depot.
tacmd removeBundles –i /mnt/bundles –t ux –p aix513 –v 060100000

This command removes all of the deployment bundles in the /mnt/bundles directory
from the local deployment depot where the bundle product type is ux, the bundle
platform is aix513, and the bundle version is 060100000.

Return values
See Table 58 on page 218.

Related commands
“tacmd addBundles” on page 188

“tacmd listBundles” on page 203

“tacmd viewDepot” on page 216

Appendix E. Command reference 207

 tacmd restartAgent
Description
Use the tacmd restartAgent command to start or restart the given agents or the
agents for the given managed systems.

If you have the authority to restart agents and you specify only the agent type,
you do not need to log in to restart an agent on a local computer.

When you specify only an agent type, all agents of that type are restarted on the
local computer.

You can only use the tacmd restartAgent command to restart OS agents locally.

Note: You cannot use this command to restart a non-default Universal Agent
instance that you created manually. Use the itmcmd agent command with
the -p parameter instead to restart a non-default Universal Agent instance.

CLI syntax
tacmd restartAgent {-m|--system} SYSTEM ... [{-f|--force}]

tacmd restartAgent {-n|--node} MANAGED-OS {-t|--type} TYPE ... [{-f|--force}]

tacmd restartAgent {-t|--type} TYPE ... [{-f|--force}]

where::
-m|--system
Specifies a managed system on which to restart the agents.
-f|--force
Restarts the specified agents without confirmation.
-t|--type
Specifies one or more agents or agent instances to restart. TYPE is scoped
to NODE level.
-n|--node
Identifies the node on the computer where you want to restart an agent.
The node is the installation directory for all agents. The name of a node
includes the computer where the OS agent is installed and the product
code for the OS agent. For example, stone.ibm.com:LZ is the name of the
node on computer stone.ibm.com, which has a Linux OS agent installed.

CLI example
tacmd restartagent -m stone:UA

This command stops the Universal Agent agent with name stone:UA.
tacmd restartAgent –n Primary:STONE:NT –t UM

This command restarts all UM agents on the node Primary:STONE:NT.

tacmd restartAgent –t NT

This command restarts all NT agents on the local system.

Return values
See Table 58 on page 218.

208 IBM Tivoli Monitoring: Installation and Setup Guide

Related commands
“tacmd stopAgent” on page 212

“tacmd startAgent” on page 210

Appendix E. Command reference 209

 tacmd startAgent
Description
Use the tacmd startAgent command to start the given agents or the agents for the
given managed systems.

If you have the authority to start agents and you specify only the agent type, you
do not need to log in to start an agent on a local computer.

When you specify only an agent type, all agents of that type are started on the
local computer.

This command does not work on OS agents, unless used locally.

Notes:
1. If you have made changes to the agent configuration file on a UNIX computer,
use the itmcmd agent command with the -c parameter to start the agent
instead of this command. Using the -c parameter with itmcmd agent preserves
any changes that you have made to the configuration. The tacmd startAgent
command does not preserve the changes.
2. You cannot use this command to start a non-default Universal Agent instance
that you created manually. Use the itmcmd agent command with the -p
parameter instead to start a non-default Universal Agent instance.

CLI syntax
tacmd startAgent {-m|--system} SYSTEM ... [{-f|--force}]

tacmd startAgent {-n|--node} MANAGED-OS {-t|--type} TYPE ... [{-f|--force}]

tacmd startAgent {-t|--type} TYPE ... [{-f|--force}]

where:
-m|--system SYSTEM
Identifies a managed system to perform the action on.
-f|--force
Performs actions without asking confirmation.
-t|--type
The identifiers of one or more agents or agent instances to start. TYPE is
scoped to NODE level.
-n|--node
Identifies the node on the computer where you want to start an agent. The
node is the installation directory for all agents. The name of a node
includes the computer where the OS agent is installed and the product
code for the OS agent. For example, stone.ibm.com:LZ is the name of the
node on computer stone.ibm.com, which has a Linux OS agent installed.

CLI example
This command starts the Universal Agent agent with the name stone:UA.
tacmd startAgent –m stone:UA

This command starts all UM agents on the node Primary:STONE:NT.

tacmd startAgent –n Primary:STONE:NT –t UM

The following command starts all NT agents on the local system:

210 IBM Tivoli Monitoring: Installation and Setup Guide
tacmd startAgent –t NT

Return values
See Table 58 on page 218.

Related commands
“tacmd stopAgent” on page 212

“tacmd restartAgent” on page 208

Appendix E. Command reference 211

 tacmd stopAgent
Description
Use the tacmd stopAgent command to stop the given agents or the agents for the
given managed systems.

If you have the authority to start agents and you specify only the agent type, you
do not need to log in to stop an agent on a local computer.

When you specify only an agent type, all agents of that type are stopped on the
local computer.

This command does not work on OS agents, unless used locally.

Note: You cannot use this command to stop a non-default Universal Agent
instance that you created manually. Use the itmcmd agent command with
the -p parameter instead to stop a non-default Universal Agent instance.

CLI syntax
tacmd stopAgent {-m|--system} SYSTEM ...] [{-f|--force}]

tacmd stopAgent {-n|--node} MANAGED-OS {-t|--type} TYPE ... [{-f|--force}]

tacmd stopAgent {-t|--type} TYPE ... [{-f|--force}]

where:
-m|--system SYSTEM
Identifies a managed system to perform the action on.
-f|--force
Performs actions without asking for confirmation.
-t|--type
The identifiers of one or more agents or agent instances to stop. TYPE is
scoped to NODE level.
-n|--node
Identifies the node on the computer where you want the agent to be
stopped. The node is the installation directory for all agents. The name of a
node includes the computer where the OS agent is installed and the
product code for the OS agent. For example, stone.ibm.com:LZ is the name
of the node on computer stone.ibm.com, which has a Linux OS agent
installed.

CLI example
The following command stops the Universal Agent agent with the name stone:UA:
tacmd stopAgent –m stone:UA

The following command stops all UM agents on the node Primary:STONE:NT:

tacmd stopAgent –n Primary:STONE:NT –t UM

The following command stops all NT agents on the local system:

tacmd stopAgent –t NT

Return values
See Table 58 on page 218.

212 IBM Tivoli Monitoring: Installation and Setup Guide

Related commands
“tacmd restartAgent” on page 208

“tacmd startAgent” on page 210

Appendix E. Command reference 213

 tacmd updateAgent
Description
Use the tacmd updateAgent command to install an agent update on a specified
managed system. Updating agents involves stopping any that are running,
applying the changes, and restarting them. If a version is not specified, the agent is
updated to the latest version.

CLI syntax
tacmd updateAgent {-t|--type} TYPE {-n|--node} MANAGED-OS [{-v|--version}
VERSION] [{-f|--force}]

where:
-t|--type
The type of agent to update.
-n|--node
Identifies the node on the computer that has the agent that you want to
update. The node is the installation directory for all agents. The name of a
node includes the computer where the OS agent is installed and the
product code for the OS agent. For example, stone.ibm.com:LZ is the name
of the node on computer stone.ibm.com, which has a Linux OS agent
installed.
-v|--version
Specifies the version of the agent to switch to. You cannot use this
command to revert an agent to a previous version of that agent.
-f|--force
Performs actions without asking confirmation.

CLI example
The following command updates a UNIX agent (type UX) on vision84:
tacmd updateagent -t UX -n vision84.tivlab.austin.ibm.com:K -v 6111

Return values
See Table 58 on page 218.

214 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd viewAgent
Description
Use the tacmd viewAgent command to display the details of the given agent or
the agent for a given managed system. Details include whether the agent is
running or not, the agent version, and all of the configuration data for the agent.
Configuration data is not displayed for universal agents or OS agents.

CLI syntax
tacmd viewAgent [{-m|--system} SYSTEM ...]

tacmd viewAgent [{-n|--node} MANAGED-OS] [{-t|--type} pc ...]

-m|--system SYSTEM
Identifies a managed system to view agent status for.
-t|--type
The identifiers of one or more agents to view. TYPE is scoped to NODE
level.
-n|--node
Identifies the node on the computer where you want to view an agent. The
node is the installation directory for all agents. The name of a node
includes the computer where the OS agent is installed and the product
code for the OS agent. For example, stone.ibm.com:LZ is the name of the
node on computer stone.ibm.com, which has a Linux OS agent installed.

CLI example
The following command displays the details for the UM agent with the name
stone:UA:
tacmd viewAgent –m stone:UA

The following command displays the details for all UM agents on the node
Primary:STONE:NT:
tacmd stopAgent –n Primary:STONE:NT –t UM

Return values
See Table 58 on page 218.

Appendix E. Command reference 215

 tacmd viewDepot
Description
Use the tacmd viewDepot command to display the types of agents you can install
from the deployment depot on the server which you are logged into or the
specified remote server.

CLI syntax
tacmd viewDepot [{{-j|--depot} DEPOT}]
-j|--depot
Specifies the name of the remote server that hosts the depot when you are
logged into the hub monitoring server.

CLI example
The following command displays the contents of the deployment depot on the
Tivoli Enterprise Monitoring Server you logged into using the tacmd login
command:
tacmd viewDepot

The following command displays the contents of the deployment depot on the
remote monitoring server, REMOTE_ROCK, which connects to the hub monitoring
server. You must log into the hub monitoring server before running this command:
tacmd viewdepot -j REMOTE_ROCK

Return values
See Table 58 on page 218.

Related commands
“tacmd listBundles” on page 203

“tacmd addBundles” on page 188

“tacmd removeBundles” on page 207

216 IBM Tivoli Monitoring: Installation and Setup Guide

tacmd viewNode
Description
Use the tacmd viewNode command to display the details of a node, including the
installed components.

You do not need to log in to view a local node if you have permission to view the
node.

CLI syntax
tacmd viewNode [{{-n|--node} MANAGED-OS} {{-d|--directory} install_dir}]

where:
-n|--node
Specifies the node to display. The node is the installation directory for all
agents. The name of a node includes the computer where the OS agent is
installed and the product code for the OS agent. For example,
stone.ibm.com:LZ is the name of the node on computer stone.ibm.com,
which has a Linux OS agent installed.
-d|--directory
Specifies the base installation directory for IBM Tivoli Monitoring for the
node to display. The directory can be a either a relative path or a fully
qualified path.

CLI example
The following command displays the components installed on the managed system
named icarus.austin.ibm.com.
tacmd viewnode -n icarus.austin.ibm.com

Return values
See Table 58 on page 218.

Appendix E. Command reference 217

 Return codes
The following table lists the return codes for the tacmd commands.
Table 58. Return Codes for tacmd CLI commands
Code Category Description
0 Success Indicates that the command was successful.
1 Syntax Error or Indicates either that the help command was given or that the
Help syntax used was incorrect.
2 No Permission Indicates that the user does not have permission to issue the
command.
3 Version Mismatch Indicates that the version of the server is not what was
expected.
4 Communication Indicates that an error occurred in the communications with
Error the server.
5 Timeout Indicates that an operation waiting for data did not receive it
within the time it was expected.
6 Input Error Indicates that the input to the command was not what was
expected.
7 Server Exception Indicates that an error occurred on the server that caused the
command to fail.
8 Command Error Indicates that an internal error occurred while executing the
command.
9 Invalid Object Indicates that a specified object does not exist.

itmcmd commands
The following commands are available only on UNIX monitoring servers.

218 IBM Tivoli Monitoring: Installation and Setup Guide

cinfo
Description
Use the cinfo command to view the following information for your monitoring
server:
v An inventory of installed IBM Tivoli products
v The configuration settings for products
v The installed CD versions in the current install_dir directory
v The configuration settings for products in the context of the actual variables
used by the installation program
v A list of running IBM Tivoli processes (such as agents or monitoring server)
v An validated list of running IBM Tivoli processes, after first performing an
update on the tracking database, to remove stale PIDs (processes logged as
″running″ but not found when attempting to verify using the ps command).

The command can be run in several ways.

Simply typing cinfo gets this menu:

-- CINFO Menu --
1) Show products installed in this CandleHome
2) Show which products are currently running
3) Show configuration settings
4) Show installed CD release versions
X) Exit CINFO

The command can also be run without a menu, so the four numbered options
above can be invoked as:
cinfo -i
cinfo -r
cinfo -c <pc>
cinfo -v

Typing cinfo -? displays this help:

cinfo -?
cinfo [-h candle_directory] [-c product] [-i] [-r] [-s product] [-R]
[-v]
-c <product> Displays configuration prompts and values
-i Displays an inventory of installed products
-r Shows running processes
-s <product> Displays configuration parameters and settings
-R Shows running processes, after updating a tracking database
-v Shows the installed CD versions in this CandleHome

CLI syntax
cinfo [-h install_dir [-c pc] [-i] [-r] [-s pc | all] [-R]

where:
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-c [pc] (Optional) Lists configuration prompts and values for all components (by
default) or for a specific component (identified by product code). If you
use the product code, you can only enter one code.

Appendix E. Command reference 219

 -i Shows an inventory of installed components.
-s [pc|all]
Shows the configuration parameters and settings for either a single
component (identified using the product code) or for all installed
components.
-r Shows the running processes
-R Shows the running processes, after updating a tracking database.
All started processes started and stopped by IBM Tivoli Monitoring
commands are logged in a tracking database that does not automatically
update itself if the process abnormally ends or is stopped without using an
IBM Tivoli Monitoring command (for example, using the UNIX kill
command directly on the process). The -r parameter shows even these
defunct processes in its report. In contrast, the -R parameter updates the
tracking database before reporting the results. This results in a cleaner
report, but permanently erases the history of processes normally kept in
the tracking database.
The output of the -R option looks the same as the -r option, but any
″process not running″ messages are absent.
-v Shows the installed CD versions in the installation directory.

CLI example
The following example shows all installed products:
./cinfo -i

The following is the output of this example:

...Product inventory
ax Candle Shared Libraries
aix513 Version: 350 Rel: 240
cf ms Configurator
aix513 Version: 300 Rel: 122
ms Candle Management Server
aix513 Version: 350 Rel: 242
hp11 Version: 350 Rel: 219
sa R/3 Monitoring Agent
aix513 Version: 300 Rel: 210

The following example shows the running processes:

./cinfo -r

The following is the output of this example:

Host Prod PID Owner Start ID ..Status
manta mq 104254 longl 07:48:13 larry ..running
manta mq 44270 longl 07:48:13 moe ** process not
running **
manta mq 79456 longl 07:48:27 curley ..running

The following example shows the configuration settings for the Universal Agent:
./cinfo -c um

The following is the output of this command:

Configuration Setting
um aix513 "IP Port Number " = 3141
um aix513 "Data Provider" = ASFS
um aix513 "Network Protocol [ip, sna, or ip.pipe] " = ip
um aix513 "Net Name " = CANDLE

220 IBM Tivoli Monitoring: Installation and Setup Guide

um aix513 "LU Name " = LUNAME
um aix513 "Log Mode " = LOGMODE
um aix513 "CMS Host Name " = manta
um aix513 "Enter Optional Primary Network Name or "none" " = none
um aix513 "IP.PIPE Port Number " = 1918
um aix513 "Secondary CMS Net Name " = CANDLE
um aix513 "Secondary CMS LU Name " = LUNAME
um aix513 "Secondary CMS Log Mode " = LOGMODE
um aix513 "Secondary CMS IP Port Number " = 1918
um aix513 "Secondary CMS IP.PIPE Port Number " = 1918
um aix513 "Network Protocol 2 " = none
um aix513 "Network Protocol 3 " = none
um aix513 "Secondary CMS Protocol 2 " = none
um aix513 "Secondary CMS Protocol 3 " = none
um aix513 "Will this agent connect to a CMS? [YES or NO] " = YES
um aix513 "Will the agent connect through a firewall? [YES or NO] "
= NO
um aix513 "Configure connection for a secondary CMS? [YES or NO] " =
NO

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

Appendix E. Command reference 221

 itmcmd agent
Description
Use the itmcmd agent command to start and stop most agents. You can start or
stop one agent, all agents, or multiple agents. You can also start the portal server
and portal desktop client using this command.

You must run the itmcmd agent command on the architecture for which the agent
is installed.

To start or stop agents for distributed database agent, see “itmcmd dbagent” on
page 226. However, the itmcmd agent command can start and stop agents for
distributed databases, it just cannot select monitors for individual database servers
or activate debugging options.

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

where:
-l Deletes the log file associated with the monitoring agent that is being
stopped. By default, the log file is saved when the monitoring agent is
stopped.
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-o instance
Identifies a database instance to start or stop. You must use this option if
you are starting or stopping a DB2 agent.
-p option
Identifies a Universal Agent instance to start or stop. Use this option when
you are starting or stopping a non-default instance of the Universal Agent.
-c (Optional) Indicates that the configuration file used on agent startup
should not be updated. By default, this file is updated each time the agent
is started.
-s (optional) Option to specify safe mode operation.
Safe mode invokes the JRE with the -nojit option (no just-in-time
compiler). If you encounter a Java failure error, try running the command
as before, but also specifying the -s option.
start | stop {pc|all}
Indicates to start or stop the monitoring agent. You can start or stop one or
more agents by using the product codes (for example, specifying lz um
starts the Linux monitoring agent and the Universal Agent). To start or
stop all agents on the computer, use the all option.
See “cinfo” on page 219 to identify the product code for an agent or
component.

222 IBM Tivoli Monitoring: Installation and Setup Guide

CLI example
The following example starts the Universal Agent:
./itmcmd agent start um

The following example stops a non-default instance (inst1) of the Universal Agent:
./itmcmd agent -p INST1 stop um

The following example starts the portal server:

./itmcmd agent start cq

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

Note: The log file for the agent session is always saved, regardless of whether the
agent was stopped using the itmcmd agent command or any other means,
unless you use the -l parameter when you run the itmcmd agent command.
Additionally, when the agent is stopped using the itmcmd agent command,
the log file for that session ends with the following message:
"** Process terminated by user **"

Related commands
“itmcmd server” on page 231

“cinfo” on page 219 (to determine the product codes for agents and components)

Appendix E. Command reference 223

 itmcmd config
Description
Use the itmcmd config command to configure or reconfigure the following items
for IBM Tivoli Monitoring on UNIX:
v The IP port that the hub monitoring server uses to listen for requests
v The hosts that can run a product
v The location of the hub monitoring server in the network
v The monitoring server an agent connects to
v Whether a monitoring server is a hub or remote server

You can only configure one product at a time. If you reconfigure a monitoring
server, you must stop and restart that monitoring server before the changes take
effect.

The itmcmd config command prompts for input for the required parameters.
Scripts are located in the install_dir/bin directory where install_dir is the directory
into which you installed IBM Tivoli Monitoring.

CLI syntax
Use the following syntax to configure a monitoring server:

itmcmd config -S [ -h install_dir ] [ -a arch ] -t tems_name

itmcmd config -S [ -h install_dir ] -u -t tems_name pc

itmcmd config -S [ -h install_dir ] [-g] [-t tems_name]

Use the following syntax to configure a monitoring agent:

itmcmd config -A [ -h install_dir ] [ -a arch ] [ -t agent_host_name ] pc

itmcmd config -A [ -h install_dir ] [ -a arch ] [ -o domain_name ] pc

itmcmd config -A [ -h install_dir ] [-g] pc

Use the following syntax to configure an Oracle agent:

itmcmd config -A [ -h install_dir ] [ -o "servername,userid,pwd" ] or

where:
-S Indicates that you are configuring a monitoring server.
-A pc Indicates that you are configuring a monitoring agent. pc is the product
code for the agent that you want to configure.
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-s (optional) Option to specify safe mode operation.

224 IBM Tivoli Monitoring: Installation and Setup Guide

 Safe mode invokes the JRE with the -nojit option (no just-in-time
compiler). If you encounter a Java failure error, try running the command
as before, but also specifying the -s option.
-a arch Optional parameter to specify the architecture where arch is one of the
abbreviations used to indicate architecture.
This parameter enables you to configure an agent and a monitoring server
for an architecture other than the one that you are on. For example, if you
are on AIX and want to configure for Solaris computer, then this option is
required. Otherwise the default is the computer you are on.
-u Adds application support (catalog and attribute files) to a monitoring
server for agents that were not installed or for non-UNIX-based agents. If
you specify the -u parameter, you must also specify the product code (pc)
for the agent or agents. Only used with the -S parameter.
-t tems_name
Required parameter that identifies the name of the monitoring server.
-o instance_name
The instance name for the agent that you want to start.

CLI example
The following example configures the monitoring server ms1:
itmcmd config -S -t hub_ms1

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

Appendix E. Command reference 225

 itmcmd dbagent
Description
Use the itmcmd dbagent command to start the IBM Tivoli Monitoring for Sybase
and IBM Tivoli Monitoring for Oracle monitoring agents.

To start other monitoring agents, see “itmcmd agent” on page 222.

CLI syntax
./itmcmd dbagent [-d trace_option] [-h install_dir] [-s server,...] start | stop [pc]

where:
-d trace_option
Enables diagnostic reporting for one or all monitored database tables.
Enables debug tracing for the following items:
Table Turns on KBB_RAS1 tracing for table (korxxxx, kraxxxx). Table
names are case-insensitive. You can use ksh wildcards (but not
regexp).
debug Turns on collector and agent internal tracing through -dddd.
d Fine tunes internal tracing level: -d, -dd, -ddd, -dddd, -ddddd
(debug or ddd’s also change col.out to wrap after 100000 lines, and
keep col.ou[1-9])
all *,debug
ALL ddddd + all possible agent KBB_RAS1: (UNIT:K ALL)

Note: Any form of tracing also turns on KBB_RAS1 (UNIT:KDD ALL).

-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-s server
Starts monitoring only for the specified servers.

Note: This is not the same as the Safe Mode -s parameter available on
some commands.
start | stop
Starts or stops the specified agent.
pc Specifies the agent you want to take action on. If you have installed agents
for more than one kind of database, Oracle and Sybase for example, you
can specify the product code for the database type whose agent you want
action taken upon. The default is that itmcmd dbagent applies to all.
You can specify multiple arguments separated by commas.

CLI example
The following example starts all database monitoring agents on the computer:
./itmcmd dbagent start

226 IBM Tivoli Monitoring: Installation and Setup Guide

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

Related commands
“itmcmd agent” on page 222

“cinfo” on page 219 (to determine product codes)

Appendix E. Command reference 227

 itmcmd manage
Description
Use the itmcmd manage command to start Manage Tivoli Enterprise Monitoring
Services on a UNIX or Linux computer. You can start, stop, and configure
monitoring components in Manage Tivoli Enterprise Monitoring Services.

CLI syntax
./itmcmd manage [-h install_dir]

where:
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on a an IBM Tivoli Monitoring
installation directory other than the one in the current system.

CLI example
The following example starts Manage Tivoli Enterprise Monitoring Services:
./itmcmd manage

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

228 IBM Tivoli Monitoring: Installation and Setup Guide

itmcmd support
Description
Use the itmcmd support command to add agent-specific information to the
monitoring server.

You need to run this command once during the initial installation of the
monitoring server to add data for the components installed from the same
installation CD. Whenever you add a new monitoring agent type to your
monitoring environment, run the itmcmd support command again on the
monitoring server to add the new agent information to the monitoring server.
Notes:
1. Before you can run the itmcmd support command, you must start the
monitoring server. See “itmcmd server” on page 231 for details.
2. Add application support only for agent components, not for other installed
components such as the portal desktop client.
3. After you add the application support to the monitoring server, stop it and
restart it.
4. If you are installing a backup monitoring server, see “Adding application
support on the backup hub monitoring server” on page 110 for information
about adding application support.

CLI syntax
./itmcmd support [-h install_dir] [-m] -t tems_name pc pc pc

where:
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-m Copies application support files to a backup monitoring server without
adding them. Use this option only when you are configuring a backup
monitoring server.
-t tems_name
Identifies the monitoring server. This parameter is required.
pc pc pc
The product codes for the components for which you want to add
application support. To display the product codes for agents installed on
this computer, run the cinfo command. See “cinfo” on page 219 for more
information.

CLI example
The following example adds application support to the hub_ms1 monitoring server
for the agents installed from the IBM Tivoli Monitoring installation CD:
./itmcmd support -t hub_ms1 a4 lz nt sy tm ul um ux

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

Appendix E. Command reference 229

 Related commands
“itmcmd server” on page 231

“cinfo” on page 219 (to determine the product codes for agents)

230 IBM Tivoli Monitoring: Installation and Setup Guide

itmcmd server
Description
Use the itmcmd server command to start and stop monitoring servers that are
defined in directories under the install_dir/tables subdirectory. You must run the
itmcmd server command from the host computer.

CLI syntax
./itmcmd server [-h install_dir] [-l] [-s] start | stop tems_name

where:
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-l Deletes the log file associated with the monitoring server that is being
stopped. By default, the log files is saved when the monitoring server
stops.
-s (optional) Option to specify safe mode operation.
Safe mode invokes the JRE with the -nojit option (no just-in-time
compiler). If you encounter a Java failure error, try running the command
as before, but also specifying the -s option.
start tems_name
Starts the specified monitoring server.
stop tems_name
Stops the specified monitoring server.

CLI example
The following command stops the hub_ms1 monitoring server:
./itmcmd server stop hub_ms1

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

The monitoring server stop message might be displayed before the processes have
completely stopped. It might take a minute for the processes to completely
disappear, based on the system load.

Note: When the monitoring server stops normally, the log file for that session is
saved. Use the -l parameter to delete the log files.

Related commands
“itmcmd agent” on page 222

Appendix E. Command reference 231

 SetPerm
Description
Use the SetPerm command to set file permissions to ensure that the permissions
were set properly during the installation procedure. To run this command, you
must logged into the UNIX computer as root.

When you run the SetPerm command, a product selection list is displayed. This
list is sorted and contains the run architectures within each product description.
From the list of installed products, enter a valid number or numbers separated by
commas or spaces.

CLI syntax
./SetPerm [-h install_dir] -s

where:
-h install_dir
(Optional) Identifies the installation directory if it is not the one in which
the script is located.
Also use this option to take action on an IBM Tivoli Monitoring installation
directory other than the one in the current system.
-s Used to set security validation on selected monitoring servers.

CLI example
The following example starts the SetPerm utility:
./SetPerm -s

Return values
An exit status of 0 indicates that the command ran successfully. An exit status
greater than 0 indicates that there was a failure in the process.

232 IBM Tivoli Monitoring: Installation and Setup Guide

IBM Tivoli Enterprise Console commands
You can run the following commands on the IBM Tivoli Enterprise Console event
server to configure the event synchronization between IBM Tivoli Monitoring and
IBM Tivoli Enterprise Console:
v “sitconfig.sh” on page 234
v “sitconfsvruser.sh” on page 236
v “upg_sentry_baroc.pl” on page 237
v “upg_tec_baroc.pl” on page 238

Run these commands from the $BINDIR/TME/TEC/OM_TEC/bin directory

(where $BINDIR is the location of the Tivoli Management Framework installation).

When running these commands, if you are specifying fully qualified paths, use a
forward slash (/) for all operating systems, including Windows.

Appendix E. Command reference 233

 sitconfig.sh
Description
Use the sitconfig.sh command to set or change the configuration of the event
synchronization. You can use this command to initially create the configuration
settings or to update existing settings.

After you change the configuration of the event synchronization, you must
manually stop and restart the Situation Update Forwarder process. See “Starting
and stopping the Situation Update Forwarder process” on page 103 for
information.

CLI syntax
sitconfig.sh add fileName=<config_filename>
fileSize=<size>
fileNumber=<number>
fileLocation=<path>
pollingInterval=<seconds>
crcBytecount=<count>
cmsSoapUrl=<url>
bufferFlushRate=<rate>
logLevel=<level>

sitconfig.sh update fileName=<config_filename>

[fileSize=<size>]
[fileNumber=<number>]
[fileLocation=<path>]
[pollingInterval=<seconds>]
[crcBytecount=<count>]
[cmsSoapUrl=<url>]
[bufferFlushRate=<rate>]
[logLevel=<level>]

where:
add Create the configuration file. The default name is situpdate.conf.
update
Updates the existing specified configuration file.
fileName=<config_filename>
The name of the configuration file for event synchronization. situpdate.conf
is the default file name.
fileSize=<size>
Specify this parameter to set and change the maximum size, in bytes, for
any one event cache file. The minimum (and default) value is 50000. Do
not use commas when specifying this value (50,000 instead of 50000).
fileNumber=<number>
Specify this parameter to set and change the maximum number of event
caches files permitted at any given time. The minimum value is 2, while
the default value is 10. When this value is reached, the oldest file is deleted
to make room for a new file.
fileLocation=<path>
Specify this parameter if you want to set and change the location on the
event server where event cache files are located. The default locations are
as follows:

234 IBM Tivoli Monitoring: Installation and Setup Guide

 v On Windows: C:\tmp\TME\TEC\OM_TEC\persistence.
v On UNIX: /var/TME/TEC/OM_TEC/persistence
pollingInterval=<seconds>
Specify this parameter to set and change the polling interval, in seconds.
The minimum value is 1, while the default value is 3. This is the number
of seconds that the Situation Update Forwarder process sleeps when there
are no updates to process.
crcBytecount=<count>
Specify this parameter to set and change the number of bytes that the long
running process will use when it saves the location of the last event it
processes. This value must be an integer. The minimum (and default) is 50.
cmsSoapUrl=<url>
Specify this parameter to set and change the URL for the SOAP Server
configured on the computer where the monitoring server is running. The
default value is cms/soap. This value is used to create the URL to which
IBM Tivoli Enterprise Console sends event information. For example,
http://hostname:port///cms/soap, where hostname is the host name of the
monitoring server and port is the port.
bufferFlushRate=<rate>
Specify this parameter to set and change the maximum number of event
updates sent to the monitoring server at one time. The minimum (and
default) value is 100 events.
logLevel=<level>
Specify this parameter to set and change the level of information for event
synchronization that is logged. You have the following choices:
v low (default)
v med
v verbose

CLI example
The following example changes the trace level for the event synchronization to
medium:
sitconfig.sh update fileName=situpdate.conf logLevel=med

Appendix E. Command reference 235

 sitconfsvruser.sh
Description
Use the sitconfsvruser.sh command to add, update, or delete monitoring server
information for event synchronization.

After you change the configuration of the event synchronization, you must
manually stop and restart the Situation Update Forwarder process. See “Starting
and stopping the Situation Update Forwarder process” on page 103 for
information.

CLI syntax
sitconfsvruser.sh add serverid=<server> userid=<user> password=<password>

sitconfsvruser.sh update serverid=<server> userid=<user> password=<password>

sitconfsvruser.sh delete serverid=<server>

where:
add Adds a new monitoring server to the list of monitoring servers that
forward events to IBM Tivoli Enterprise Console.
update
Modifies the user ID or password for an existing monitoring server.
delete Removes a monitoring server from the list of monitoring servers that
forward events to IBM Tivoli Enterprise Console.
serverid=server
The fully qualified host name of the monitoring server.
userid=user
The user ID to access the computer where the monitoring server is
running.
password=password
The password to access the computer.

CLI example
The following example adds the itm17 monitoring server:
sitconfsvruser.sh add serverid=itm17.ibm.com userid=admin password=acc3ssing

236 IBM Tivoli Monitoring: Installation and Setup Guide

upg_sentry_baroc.pl
Description
Use the upg_sentry_baroc.pl script to update the Sentry2_0_Base class file with
additional integration attributes for the situation events received from IBM Tivoli
Monitoring.

If you specify a rule base that does not contain the Sentry2_0_Base class, no
changes are made.

Use this script only when you are manually upgrading your rule base after
installing the event synchronization.

CLI syntax
upg_sentry_baroc.pl [<rb_name> [<rb_path>]]

where:
rb_name
Specifies the rule base that you want to update. If you do not specify a
rule base, all existing rule bases are updated.
rb_path
The path to the rule base specified with the rb_name parameter. This path
is optional.

CLI example
The following example updates the Sentry2_0_Base class in the Sentry.baroc file of
the itmsynch_rb rule base:
upg_sentry_baroc.pl itmsynch_rb

Appendix E. Command reference 237

 upg_tec_baroc.pl
Description
Use the upg_tec_baroc.pl script to add the TEC_Generic class to the tec.baroc file
in the specified rule base. This class is required for event synchronization.

If the rule base already contains the TEC_Generic class in the tec.baroc file, no
changes are made.

Use this script only when you are manually upgrading a rule base after installing
the event synchronization.

CLI syntax
upg_tec_baroc.pl rb_name

where rb_name is the name of the rule base to upgrade. This name is required.

CLI example
The following example adds the TEC_Generic class to the tec.baroc file of the
itmsynch_rb rule base:
upg_tec_baroc.pl itmsynch_rb

238 IBM Tivoli Monitoring: Installation and Setup Guide

Appendix F. Maintaining the EIB on Linux or UNIX
To ensure the effective operation of your monitoring server, you should back up
your EIB tables as part of your routine maintenance. The EIB contains the
attributes and other data that define the agents to the server. The following files,
which are stored in the <install_dir>/tables/eib directory, comprise the EIB.
Table 59. EIB Files
*.db Files *.idx Files
qa1cacts.db qa1daggr.db qa1cacts.idx qa1daggr.idx
qa1cckpt.db qa1dcct.db qa1cckpt.idx qa1dcct.idx
qa1ccobj.db qa1dcct2.db qa1ccobj.idx qa1dcct2.idx
qa1ccomm.db qa1dmobj.db qa1ccomm.idx qa1dmobj.idx
qa1ceibl.db qa1dmtmp.db qa1ceibl.idx qa1dmtmp.idx
qa1chost.db qa1dobja.db qa1chost.idx qa1dobja.idx
qa1ciobj.db qa1dpcyf.db qa1ciobj.idx qa1dpcyf.idx
qa1cmcfg.db qa1drnke.db qa1cmcfg.idx qa1drnke.idx
qa1cnodl.db qa1drnkg.db qa1cnodl.idx qa1drnkg.idx
qa1cplat.db qa1dsnos.db qa1cplat.idx qa1dsnos.idx
qa1cpset.db qa1dspst.db qa1cpset.idx qa1dspst.idx
qa1cruld.db qa1dstms.db qa1cruld.idx qa1dstms.idx
qa1csitf.db qa1dstsa.db qa1csitf.idx qa1dstsa.idx
qa1csmni.db qa1dstua.db qa1csmni.idx qa1dstua.idx
qa1cstsc.db qa1dswrs.db qa1cstsc.idx qa1dswrs.idx
qa1cstsh.db qa1dswus.db qa1cstsh.idx qa1dswus.idx
qa1cthre.db qa1dwgrp.db qa1cthre.idx qa1dwgrp.idx
qa1dactp.db qa1dwork.db qa1dactp.idx qa1dwork.idx

© Copyright IBM Corp. 2005 239

240 IBM Tivoli Monitoring: Installation and Setup Guide
Appendix G. 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
244
v “Uninstalling the IBM Tivoli Enterprise Console event synchronization” on page
248

Uninstalling the entire IBM Tivoli Monitoring environment

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

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

Note: If you plan to reinstall IBM Tivoli Monitoring into a different directory than
the one used for this installation, you must stop and restart this computer
before reinstalling IBM Tivoli Monitoring.

Uninstalling the environment on 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. The following
window is displayed.

Figure 19. Uninstalling IBM Tivoli Monitoring

4. Select Remove and click Next.

© Copyright IBM Corp. 2005 241

 The following window is displayed.

Figure 20. Confirming the uninstallation

5. Click OK.
The following progress window is displayed.

Figure 21. Stopping Tivoli components prior to uninstallation

After Tivoli Enterprise services have stopped, you are asked if you want to
remove the Tivoli Enterprise Portal database.

Figure 22. Removing the portal database

6. Click Yes.
The following window is displayed, requesting information required to remove
the database:

Figure 23. Database information

7. Type the password for the database administrator in the Admin Password field
and click OK.

242 IBM Tivoli Monitoring: Installation and Setup Guide

 The following progress window is displayed.

Figure 24. Uninstallation progress window

A pop-up window, indicating that GSKit is being uninstalled, is displayed.

Figure 25. GSKit uninstallation

After GSKit is uninstalled, the following window is displayed:

Figure 26. Successful uninstallation

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 install_dir/bin

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

Appendix G. Uninstalling IBM Tivoli Monitoring 243

 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.
4. After you have removed all installed components, you are asked if you want to
remove the installation directory. Type y and press Enter.

You can also run the following command to remove all installed components from
the command line:
./uninstall.sh REMOVE EVERYTHING

After the command completes, you can manually remove the IBM Tivoli
Monitoring installation directory.

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

This uninstallation program does not delete the database created for Tivoli
Enterprise Portal on a Linux portal server. If you want to delete that database, you
must remove it manually. See the documentation for your database software for
information about deleting a database.

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 245
v “Uninstalling OMEGAMON agents” on page 245
v “Removing an agent through the Tivoli Enterprise Portal” on page 247

Note: If you plan to reinstall a IBM Tivoli Monitoring component into a different
directory than the one used for this installation, you must stop and restart
this computer before reinstalling the IBM Tivoli Monitoring component.

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.

244 IBM Tivoli Monitoring: Installation and Setup Guide

 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:
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 install_dir/bin

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

Uninstalling OMEGAMON agents

Use the following steps to remove OMEGAMON agents from a computer. Table 60
on page 246 and Table 61 on page 246 list the agents by internal code, release, and
descriptive name.
1. Launch Manage Candle Services (350 or 360) or Manage Tivoli Enterprise
Monitoring Services.
2. Use the Description and Release columns to locate the agent service name.
3. Stop the service by right-clicking the name and clicking Stop.
4. Take note of any task or subsystem names that are listed in the column for
your agent. Usually this column lists Primary unless your agent supports
instances. If your agent supports instances, record these names for later use.
5. Unconfigure the agent by right-clicking the name and clicking Advanced →
Unconfigure. The Configured column changes from Yes to No. Continue to
unconfigure all instances found in step 4.
6. Open the Windows Explorer and navigate to the installation directory for
OMEGAMON 350 or 360 products and IBM Tivoli Monitoring. The default
directories are C:\Candle Candle OMEGAMON and C:\IBM\ITM for IBM
Tivoli Monitoring. Then navigate to the CMA directory.

Appendix G. Uninstalling IBM Tivoli Monitoring 245

 7. Delete files K??ENV (Task/SubSystem name Primary) and any instances shown
as K??ENV_INSTANCENAME (Task/SubSystem name from step 4 on page
245).
8. Delete any PC*.EXE or PC*.DLL files for the product. PC is the product internal
identifier three-character code from the tables.
9. Exit Manage Candle Services or Manage Tivoli Enterprise Monitoring Services
and launch it again. The agent and all instances should not be shown under the
Service/Application column.

Note: You can also use this procedure to remove IBM Tivoli Monitoring agents if
you use the TMAITM6 directory instead of the CMA directory in step 6 on
page 245. All of the other steps do not change.
Table 60. Candle OMEGAMON Release 04R1
Internal
Identifier Release Description
®
K3Z 400 Windows Server Active Directories Monitoring Agent
KA2 120 Alert Adapter for AF/Remote
KA4 300 Monitoring Agent for OS/400
KBL 320 CASP Directory Server Monitoring Agent
KBR 320 CASP Exchange Connector Monitoring Agent
KEZ 251 eBA® Solutions Monitoring Agent
KIC 100 WebSphere InterChange Server Monitoring Agent
KIE 100 WebSphere InterChange Server Data Source
KMA 201 Alert Adapter for Remedy ARS
KMC 360 WebSphere MQ Configuration Agent
KMQ 360 WebSphere MQ Monitoring Agent
KNW 300 NetWare Monitoring Agent
KOQ 301 Microsoft SQL Server Monitoring Agent
KOR 301 Oracle Monitoring Agent
KOY 300 Sybase Monitoring Agent
KPT 201 Alert Adapter for Peregrine Service Center
KQI 120 WebSphere Integration Brokers Monitoring Agent
KSA 301 R/3 Monitoring Agent
KTX 300 Tuxedo Monitoring Agent
KUD 400 DB2 Universal Database Monitoring Agent
KWE 130 WebSphere Application Server Monitoring Agent
KWL 100 BEA WebLogic Server Monitoring Agent
KWN 100 Windows Management Web Service

Table 61. Candle OMEGAMON Release BIV110

Internal
Identifier Release Description
KIC 110 WebSphere InterChange Server Monitoring Agent
KIE 110 WebSphere InterChange Server Data Source
KMC 370 WebSphere MQ Configuration Agent

246 IBM Tivoli Monitoring: Installation and Setup Guide

 Table 61. Candle OMEGAMON Release BIV110 (continued)
Internal
Identifier Release Description
KMQ 370 WebSphere MQ Agent
KQI 130 WebSphere Integration Brokers Monitoring Agent

Removing an agent through the Tivoli Enterprise Portal

You can also uninstall non-OS monitoring agents from the Tivoli Enterprise Portal
by stopping the agent and removing its configuration settings. After you have
removed the agent from the enterprise, you can completely uninstall the agent
from the managed system. When you remove an agent, it is removed from any
managed system lists to which it is assigned, any situation or policy distribution
lists it was on, and any custom Navigator view items to which it was assigned.

Note: You cannot use the Tivoli Enterprise Portal to remove or uninstall OS
agents.

Note: If the Manage Tivoli Enterprise Monitoring Services utility is running when
you uninstall the agent, it is shut down automatically by the uninstallation
process.

Use the following steps to remove and optionally uninstall an agent:

1. In the Tivoli Enterprise Portal, right-click the agent Navigator item and click
Remove.
2. Click Yes when you are asked to confirm the removal of the agent.
3. When you are asked to confirm that you want to permanently uninstall the
agent, click Yes to uninstall or No to leave the agent installed on the computer.

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 G. Uninstalling IBM Tivoli Monitoring 247

 If you are using a Microsoft SQL or Oracle database, use the Windows ODBC Data
Source Administrator utility to remove the ODBC data source.

Uninstalling the IBM Tivoli Enterprise Console event synchronization

Use the following steps to uninstall the event synchronization from your event
server:
1. Run the following uninstallation program:
v On Windows: %BINDIR%\TME\TEC\OM_TEC\_uninst\uninstaller.exe
v On UNIX: $BINDIR/TME/TEC/OM_TEC/_uninst/uninstaller.bin
2. Follow the prompts in the uninstallation program.

You can also run this uninstallation program in silent mode (by running the
program from the command line with the -silent parameter) or in console mode
(by using the -console parameter).

You must stop and restart the event server for these changes to take effect.

If your event server is running on an HP-UX computer, ensure that the _uninst
and _jvm directories are successfully removed by the uninstallation program. If
they are not, manually delete these directories.

248 IBM Tivoli Monitoring: Installation and Setup Guide

Appendix H. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This
section describes the following options for obtaining support for IBM software
products:
v “Searching knowledge bases”
v “Obtaining fixes”
v “Receiving weekly support updates” on page 250
v “Contacting IBM Software Support” on page 250

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

IBM provides extensive documentation that can be installed on your local
computer or on an intranet server. You can use the search function of this
information center to query conceptual information, instructions for completing
tasks, and reference information.

Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

To search multiple Internet resources for your product, use the Web search topic in
your information center. In the navigation frame, click Troubleshooting and
support  Searching knowledge bases and select Web search. From this topic, you
can search a variety of resources, including the following:
v IBM technotes
v IBM downloads
v IBM Redbooks™
v IBM developerWorks®
v Forums and newsgroups
v Google

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click Downloads and drivers in the Support topics section.
3. Select the Software category.
4. Select a product in the Sub-category list.
5. In the Find downloads and drivers by product section, select one software
category from the Category list.

© Copyright IBM Corp. 2005 249

 6. Select one product from the Sub-category list.
7. Type more search terms in the Search within results if you want to refine your
search.
8. Click Search.
9. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click My support in the upper right corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Application servers.
A third list is displayed.
7. In the third list, select a product sub-segment, for example, Distributed
Application & Web Servers. A list of applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
HTTP Server and WebSphere Application Server.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email
on the Edit profile tab.
11. Select Please send these documents by weekly email.
12. Update your e-mail address as needed.
13. In the Documents list, select Software.
14. Select the types of documents that you want to receive information about.
15. Click Update.

If you experience problems with the My support feature, you can obtain help in
one of the following ways:
Online
Send an e-mail message to [email protected], describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

250 IBM Tivoli Monitoring: Installation and Setup Guide

 Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2 and WebSphere products that
run on Windows, or UNIX operating systems), enroll in Passport Advantage® in
one of the following ways:
Online
Go to the Passport Advantage Web site at
http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink™, CATIA, Linux, OS/390, iSeries™, pSeries®,
zSeries®, and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries, pSeries, and iSeries environments), you
can purchase a software maintenance agreement by working directly with an
IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact”
2. “Describing problems and gathering information” on page 252
3. “Submitting problems” on page 252

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.

Appendix H. Support information 251

 Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Describing problems and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you recreate the problem? If so, what steps were performed to recreate the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site
athttp://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

252 IBM Tivoli Monitoring: Installation and Setup Guide

Appendix I. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on 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 may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
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 may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send 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 will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) 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 253

 IBM may 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 which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may 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.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

Trademarks
IBM, the IBM logo, AIX, Candle, Candle Management Server, CICS, DB2, DB2
Universal Database, developerWorks, eBA, eServer, i5/OS, IBMLink, iSeries, Lotus,
OMEGAMON, OMEGAMON Monitoring Agent, OS/390, OS/400, Passport
Advantage, RACF, Rational, Redbooks, Tivoli, the Tivoli logo, Tivoli Enterprise,
Tivoli Enterprise Console, TME 10, WebSphere, z/OS, and zSeries are trademarks
or registered trademarks of International Business Machines Corporation in the
United States, other countries, or both.

Intel and Pentium® are trademarks 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 NT are registered 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 may be trademarks or service marks
of others.

254 IBM Tivoli Monitoring: Installation and Setup Guide

Index
A assessing the existing environment
(continued)
commands (continued)
tacmd 187
accessibility xiii organizational perspective 11 tacmd addBundles 138, 188
adding application support 73 physical perspective 10 tacmd addSystem 190
backup monitoring server 110 asymmetric cryptography 119 tacmd configurePortalServer 192
from command line 113 asymmetric encryption tacmd configureSystem 194
itmcmd support command 54 CA certificate request, creating 121 tacmd createNode 140, 196
Linux desktop client 80 CA certificate, receiving 122 tacmd help 202
Linux monitoring server 54, 76 key database, creating 121 tacmd listBundles 203
Linux portal server 78 password, saving to stash file 123 tacmd listSystems 204
monitoring server 112 public-private key pair, creating 121 tacmd login 205
through Manage Tivoli Enterprise self-signed certificate, using 122 tacmd logout 206
Monitoring Services 112 setting up 120 tacmd removeBundles 207
UNIX monitoring server 54, 76 stash file 123 tacmd restartAgent 208
Windows desktop client 80 attribute group tacmd startAgent 108, 210
Windows monitoring server 74 aggregate data, amount of 31 tacmd stopAgent 108, 212
Windows portal server 77 detailed data, amount of 31 tacmd updateAgent 214
with itmcmd support command 113 detailed records per day, number tacmd viewAgent 215
agent 6 of 30 tacmd viewDepot 216
configuring 107 hard disk drive footprint 31 tacmd viewNode 217
removing through the portal 247 upg_sentry_baroc.pl 237
starting 108 upg_tec_baroc.pl 238
stopping 108
uninstalling on Linux 245 B component
browser client 5
uninstalling on UNIX 245 backup monitoring server
desktop client 5
uninstalling on Windows 244 adding application support 110
portal client 5
agent deploy configuring 110
portal server 5
Universal Agent 143 books
components 3
agent deployment 135 feedback on xi
IBM Tivoli Enterprise Console
deploying OS agents 140 online xi
integration 6
determining when to use 14 ordering xi
monitoring agent 6
managing agent depot 139 see publications xii
monitoring server 4
OS agents, deploying 140 browser client 5
portal client 5
populating agent depot 135 starting 82
portal server 5
sharing an agent depot 139 Tivoli Data Warehouse 6
tacmd createNode command 140 Tivoli Enterprise Portal 5
agent depot 135 C Tivoli Enterprise Portal Server 5
DEPOTHOME environment CA certificate Universal Agent 6
variable 138 receiving 122 Warehouse Proxy 6
location 138 requesting 121 Warehouse Summarization and
managing 139 Candle Management Workstation Pruning agent 6
populating through install 136 coexistence 41 configuring
populating with tacmd addBundles CandleNet Portal database, agents 107
command 138 upgrading 42 hub monitoring server, UNIX 52
sharing 139 certificate Linux, silent 179
agents creating a CA certificate request 121 monitoring agents 107
deploying 135 receiving a CA certificate 122 monitoring agents on Linux 68
deploying OS agents 140 requesting a CA certificate 121 monitoring agents on UNIX 68
failover support 112 self-signed certificate, using 122 monitoring server 106
product codes 185 commands monitoring server, Linux 52, 57
Secondary TEMS configuration 112 describeSystemType 201 portal server 119
uninstalling OMEGAMON 245 for tacmd 187 portal server on Linux 62
aggregate data, amount of 31 itmcmd agent 70, 108 remote monitoring server, UNIX 57
application support 73 itmcmd config 179 response file, using 179
backup monitoring server, adding itmcmd manage 106 Tivoli Data Warehouse 145
to 110 itmcmd server 54, 108 UNIX, silent 179
from command line 113 itmcmd support 54, 113 user security 109
monitoring server, adding to 112 sitconfig.sh 103, 234 Warehouse Proxy 145
through Manage Tivoli Enterprise sitconfsvruser.sh 104, 236 conventions
Monitoring Services 112 special characters xiv typeface xiii
with itmcmd support command 113 syntax xiv
assessing the existing environment 10

© Copyright IBM Corp. 2005 255

customer support event synchronization 85 heartbeat interval 114
See Software Support changing the configuration 103 CTIRA_HEARTBEAT environment
changing the TCP/IP timeout variable 115
setting 104 performance issues 116
D defining additional monitoring
servers 104
setting the interval 115
heartbeat monitoring 114
data warehouse
importing agent class files and rule CTIRA_HEARTBEAT environment
supported databases 146
set 101 variable 115
database size, estimating 32
importing class files and rule set 99 performance issues 116
DB2
installation planning 89 setting the interval 115
creating a tablespace 36
installing 89 hot standby 110
IBMDEFAULTGROUP 36
installing from the command line 93 application support for backup
increasing the size 36
installing using silent install 95 monitoring server 110
DB2 database
installing with the wizard 90 configuring monitoring servers 110
local connection 149
overview 6 configuring on monitoring
DB2 database, configuring for
removing 248 servers 111
warehouse 148
sitconfig.sh command 103 verifying 112
deployment planning 9
sitconfsvruser.sh command 104 HTTPS 119
DEPOTHOME environment variable 138
Situation Update Forwarder hub monitoring server 5
design process overview 9
process 103 adding application support on
desktop client 5
uninstalling 248 Linux 54
adding application support on
event synchronization with Tivoli adding application support on
Linux 80
Enterprise Console 6 UNIX 54
adding application support on
events, forwarding to Tivoli Enterprise configuring on Linux 52
Windows 80
Console 102 configuring on UNIX 52
configuring on Linux 73
example environments 14 enabling user security 109
connecting to an external Web
external Web server failover support 110
server 126
desktop client connection 126 hot standby 110
external Web server, connecting
portal client connection 126 installing 48
to 126
portal server configuration 123 installing on Linux 51
installing 70
installing on UNIX 51
installing on Linux 72
installing on Windows 48
installing on Windows 70
Interoperable Object Reference (IOR) F planning worksheet, Linux or
UNIX 165
on Linux, updating 126 failover support 110
planning worksheet, Windows 164
Interoperable Object Reference (IOR) application support for backup
on Windows, updating 126 monitoring server 110
IOR for Linux, updating 126 configuring monitoring servers 110
IOR for Windows, updating 126 configuring on agents 112 I
planning worksheet, Linux 173 configuring on monitoring IBM HTTP Server on Linux,
planning worksheet, Windows 172 servers 111 configuring 125
starting 82 verifying 112 IBM Tivoli Enterprise Console
detailed data, amount of 31 file descriptors limit 24 integration 6
detailed records per day, number of 30 firewall support 117 IBM Tivoli Monitoring
determining what to monitor 10 editing the partition file 118 agent deployment 135
managed systems 11 sample partition file 118 assessing your needs 10
organizational perspective 11 firewalls component status, monitoring 114
physical perspective 10 multiple network interface cards 127 components 3
digital certificates 119 NAT 127 configuring components 105
disk requirements for Tivoli Data NIC 127 design process 9
Warehouse 35 portal server interface, defining 127 heartbeat monitoring 114
scenarios 128 Manage Tivoli Enterprise Monitoring
fixes, obtaining 249 Services 105
E forwarding events to Tivoli Enterprise
Console 102
overview 1
planning 9
education
fully qualified path names, using 23 remote deployment 135
see Tivoli technical training xiii
removing 241
EIB tables 239
uninstalling 241
enterprise monitoring environment
example 17 G upgrading to 3
what's new 1
estimating warehouse database size 30 Global Sign-On Kit (GSKit) 119
IBM Tivoli Monitoring V5.x
aggregate data, amount of 31 globalization, installing support 81
interoperability 3
amount of detailed data 31 GSKit 119
IBM Tivoli Monitoring Web Services 159
detailed records per day, number
adding users 160
of 30
defining hubs 159
determining the size 32
hard disk drive footprint 31
H verifying configuration 160
hard disk drive footprint 31 iKeyman 119
worksheet 33
hardware requirements 26

256 IBM Tivoli Monitoring: Installation and Setup Guide

information centers, searching for Linux manuals (continued)
problem resolution 249 /etc/hosts file 23 ordering xi
information to gather before adding application support on see publications xii
installing 21 monitoring server 54 maxfiles 24
installation configuring 179 medium monitoring environment
hardware requirements 26 configuring desktop client 73 example 16
information to gather 21 configuring monitoring agents 68 Microsoft SQL database
Linux considerations 22 configuring portal desktop client 73 local connection 150
monitoring server name configuring portal server 62 Microsoft SQL database, configuring for
guidelines 22 EIB tables 239 warehouse 148
operating systems, supported 24 file descriptors limit 24 monitoring agent
order of install 22 file permissions for monitoring configuring 107
overview of the process 21 agents 69 definition 6
required information 21 fully qualified path names 23 planning worksheet, Linux or
requirements 24 host names, setting 23 UNIX 171
software requirements 28 hub monitoring server 51, 52 planning worksheet, Windows 170
UNIX considerations 22 installation considerations 22 removing through the portal 247
Windows consideration 22 installation user account 22 starting 108
installing 47 installing as root 22 stopping 108
application support 73 installing desktop client 72 uninstalling on Linux 245
desktop client 70 installing monitoring agents 67 uninstalling on UNIX 245
globalization support 81 installing portal desktop client 72 uninstalling on Windows 244
hub monitoring server 48 installing portal server 61 monitoring agents
language packs 81 maxfiles 24 configuring on Linux 68
Linux monitoring server 51, 57 monitoring agents 67 configuring on UNIX 68
monitoring agents 64 Network Interface Cards 23 deploying 135
monitoring agents on Linux 67 NFS environment 23 deploying OS agents 140
monitoring agents on UNIX 67 planning 22 failover support 112
monitoring agents on Windows 65 portal server 61 file permissions, changing 69
planning worksheets 163 remote monitoring server 57 installing 64
portal desktop client 70 response file configuration 179 installing on Linux 67
portal server 59 response file installation 177 installing on UNIX 67
remote monitoring server 54 silent configuration 179 installing on Windows 65
silent 175 silent installation 177 monitoring agents on Linux 67
UNIX monitoring server 51, 57 starting monitoring agents 70 product codes 185
Windows monitoring server 48, 54 starting portal server 64 Secondary TEMS configuration 112
Internet TCP/IP network services 23 monitoring environment
searching for problem resolution 249 Linux monitoring server agent deployment 14
Internet Information Server V5.0, advanced configuration 117 assessing needs 10
configuring 123 firewall support 117 design process 9
Internet Information Server V6.0, KDC_PARTITION 117 determining what you need 10
configuring 124 NAT 117 environment examples 14
Interoperable Object Reference (IOR) network address translation monitoring servers, number 12
updating on Linux 126 (NAT) 117 network diagram 11
updating on Windows 126 planning 9
itmcmd agent command 70, 108 planning steps 9
itmcmd config command 179
itmcmd manage command 106
M planning the design 12
remote deployment 14
Manage Tivoli Enterprise Monitoring
itmcmd server command 54, 108 sample deployments 14
Services 105
itmcmd startAgent command 108 security considerations 13
adding application support 112
itmcmd stopAgent command 108 server placement 12
agents, configuring 107
itmcmd support command 54, 113 Tivoli Enterprise Console 13
application support, adding 112
monitoring server
defining SOAP hubs 159
adding application support 112
editing the partition file 118
K itmcmd manage command 106
adding application support on
Linux 54, 76
KDC_PARTITION environment monitoring agents, configuring 107
adding application support on
variable 117 monitoring server, configuring 106
UNIX 54
key database, creating 121 starting components 108
adding application support on
knowledge bases, searching for problem starting on Linux 106
Windows 74
resolution 249 starting on UNIX 106
agent depot, location 138
starting on Windows 105
agent depot, populating 135
stopping components 108
communications protocol planning
L user security, configuring 109
managed system factors 11
worksheet 174
language packs, installing 81 configuring 106
manuals
large monitoring environment configuring failover support 111
feedback on xi
example 17 configuring hot standby 111
online xi

Index 257
monitoring server (continued) OMEGAMON V350 and V360 (continued) portal server (continued)
configuring on Linux 52, 57 planning 40 adding application support on
configuring on UNIX 52, 57 terminology 40 Linux 78
definition 4 unsupported functions 41 adding application support on
DEPOTHOME environment upgrading 39 Windows 77
variable 138 using existing agents 45 configuring 119
determining the number needed 12 when to run the upgrade 40 configuring on Linux 62
EIB tables 239 OMEGAMON XE for CICS 41 configuring SSL 119
enabling user security 109 online publications creating a user 109
failover support 110 accessing xii enabling SSL 120
file descriptor limit on UNIX 24 operating systems, supported 24 external Web server 123
forwarding events to Tivoli Enterprise Optional Primary Network Name 23 firewall scenarios 128
Console 102 Oracle database IBM HTTP Server on Linux 125
heartbeat interval, configuring 114 local connection 150 installing 59
hot standby 110 ordering publications xi, xiii installing on Linux 61
hub definition 5 organizational planning perspective 11 installing on Windows 59
installing on Linux 51, 57 overview 1 interface, defining 127
installing on UNIX 51, 57 Internet Information Server V5.0,
installing on Windows 48, 54 configuring 123
naming 22
remote definition 5
P Internet Information Server V6.0,
configuring 124
partition file
starting 54, 108 planning worksheet, Linux 169
editing 118
stopping 54, 108 planning worksheet, Windows 168
sample 118
TEC Event Integration Facility 102 reconfiguring on Linux 62
password, saving to stash file 123
user security, configuring 109 Secure Socket Layer (SSL) 119
physical planning perspective 10
multiple network interface cards 127 SSL, configuring 119
managed systems factors 11
portal server interface, defining 127 starting 108
network factors 11
starting on Linux 64
planning 9, 12
stopping 108
hardware requirements 26
N installation 21
user security, configuring 109
user, creating 109
naming the monitoring server 22 Linux considerations 22
portal server interface 127
NAT 117, 127 managed system factors 11
problem determination
network address translation (NAT) 117, monitoring servers, number 12
describing problems 252
127 network diagram 11
determining business impact 251
portal server interface, defining 127 operating systems, supported 24
submitting problems 252
network diagram 11 remote deployment 14
product codes 185
network factors 11 requirements 24
product overview 1
Network Interface Cards 23 sample deployments 14
public-private key pair 119
new in this release 1 security considerations 13
creating 121
NFS environment, installing into 23 server placement 12
publications
NIC 127 software requirements 28
accessing online xii
portal server interface, defining 127 Tivoli Data Warehouse 30
feedback on xi
non-NIS Solaris monitoring server, Tivoli Enterprise Console 13
online xi
configuring permissions for 117 UNIX considerations 22
ordering xi, xiii
where to put your servers 12
Windows consideration 22
O worksheets 163
portal browser client R
ODBC connection 148
starting 82 reconfiguring Linux portal server 62
local database connection 149
portal client 5 remote deploy
local DB2 database connection 149
connecting to an external Web Universal Agent 143
local Microsoft SQL database
server 126 remote deployment 135
connection 150
external Web server, connecting deploying OS agents 140
local Oracle database connection 150
to 126 determining when to use 14
remote database connection 150
portal desktop client managing agent depot 139
OMEGAMON
adding application support on OS agents, deploying 140
uninstalling agents 245
Linux 80 populating agent depot 135
OMEGAMON V350 and V360 3
adding application support on sharing an agent depot 139
agents, configuration settings 41
Windows 80 tacmd createNode command 140
Candle Management Workstation
configuring on Linux 73 remote monitoring server 5
coexistence 41
installing 70 configuring on Linux 57
CandleNet Portal database 42
installing on Linux 61, 72 configuring on UNIX 57
installation directory 40
installing on Windows 70 installing 54
Java level, required 42
planning worksheet, Linux 173 installing on Linux 57
migrated information 42
planning worksheet, Windows 172 installing on UNIX 57
migrating Warehouse Proxy data 42
starting 82 installing on Windows 54
OMEGAMON XE for CICS 41
portal server 5

258 IBM Tivoli Monitoring: Installation and Setup Guide

remote monitoring server (continued) software requirements 28 tacmd commands (continued)
planning worksheet, Linux or Software Support tacmd viewDepot 216
UNIX 167 contacting 250 tacmd viewNode 217
planning worksheet, Windows 166 describing problems 252 tacmd configurePortalServer 192
removing 241 determining business impact 251 tacmd configureSystem 194
agent 247 receiving weekly updates 250 tacmd createNode 196
component 244 submitting problems 252 tacmd createNode command 140
Linux 245 SSL 119 requirements 140
UNIX 245 asymmetric cryptography 119 tacmd describeSystemType 201
Warehouse Proxy 247 CA certificate request, creating 121 tacmd help 202
Windows 244 CA certificate, receiving 122 tacmd listBundles 203
event synchronization 248 digital certificates 119 tacmd listSystems 204
from the portal 247 enabling 120 tacmd login 205
monitoring component 244 Global Sign-On Kit (GSKit) 119 tacmd logout 206
Linux 245 iKeyman 119 tacmd removeBundles 207
UNIX 245 key database, creating 121 tacmd restartAgent 208
Warehouse Proxy 247 password, saving to stash file 123 tacmd startAgent 210
Windows 244 public-private key pair 119 tacmd stopAgent 212
monitoring environment 241 public-private key pair, creating 121 tacmd updateAgent 214
Linux 243 self-signed certificate, using 122 tacmd viewAgent 215
UNIX 243 setting up asymmetric tacmd viewDepot 216
Windows 241 encryption 120 tacmd viewNode 217
OMEGAMON agents 245 stash file 123 TCP/IP timeout setting, changing on
required hardware 26 starting Manage Tivoli Enterprise event server 104
required information for installation 21 Monitoring Services TEC Event Integration Facility 102
required software 28 itmcmd manage command 106 Tivoli Data Warehouse 6, 145
return codes for tacmd CLI on Linux 106 configuration steps 145
commands 218 on UNIX 106 configuring Warehouse Proxy 151
on Windows 105 creating the database 147
starting monitoring agents database, creating 147
S itmcmd agent command 70
starting the monitoring server
DB2 database configuration 148
DB2 database, increasing 36
sample deployment scenarios 14
itmcmd server command 54 disk requirements, understanding 35
enterprise environment 17
starting the portal server 64 estimating database size 30
large environment 17
stash file 123 local database, connecting to 149
medium environment 16
status tables for warehouse migration 44 local ODBC connection 149
small environment 14
stopping the monitoring server Microsoft SQL database
scale planning 9
itmcmd server command 54 configuration 148
Secondary TEMS configuration 112
supported operating systems 24 ODBC connection 148
Secure Hypertext Transport Protocol
planning 30
(HTTPS) 119
remote database, connecting to 150
Secure Socket Layer (SSL) 119
security T remote ODBC connection 150
supported databases 146
firewall scenarios 128 tacmd
uninstalling the Warehouse
HTTPS 119 cli 187
Proxy 247
Secure Hypertext Transport Protocol commands 187
Warehouse Summarization and
(HTTPS) 119 tacmd addBundles 188
Pruning agent 145
SSL 119 tacmd addBundles command 138
worksheet 33
user security, configuring 109 tacmd addSystem 190
Tivoli Distributed Monitoring, upgrading
security considerations 13 tacmd commands
from 3
self-signed certificate 122 return codes 218
Tivoli Enterprise Console
silent installation 175 tacmd addBundles 188
changing the TCP/IP timeout
Linux 177 tacmd addSystem 190
setting 104
UNIX 177 tacmd configurePortalServer 192
determining when to use 13
Windows 175 tacmd configureSystem 194
event synchronization 6, 85, 89
from command line 176 tacmd createNode 196
forwarding events to 102
using SMS 176 tacmd describeSystemType 201
integration 6, 85, 86
single-computer installation tacmd help 202
planning 86
order 22 tacmd listBundles 203
TEC Event Integration Facility 102
sitconfig.sh command 103 tacmd listSystems 204
Tivoli Enterprise Monitoring Agent 6
sitconfsvruser.sh command 104 tacmd login 205
Tivoli Enterprise Monitoring Server 4
Situation Update Forwarder process 103 tacmd logout 206
Tivoli Enterprise Portal 5
small monitoring environment tacmd removeBundles 207
browser client 5
example 14 tacmd restartAgent 208
desktop client 5
SOAP server 159 tacmd startAgent 210
Tivoli Enterprise Portal client 5
adding users 160 tacmd stopAgent 212
Tivoli Enterprise Portal Server 5
defining hubs 159 tacmd updateAgent 214
Tivoli software information center xii
verifying configuration 160 tacmd viewAgent 215

Index 259
Tivoli technical training xiii UNIX monitoring server (continued) Windows (continued)
training, Tivoli technical xiii network address translation hub monitoring server 48
type 185 (NAT) 117 monitoring agents 65
typeface conventions xiii non-NIS Solaris monitoring portal desktop client 70
server 117 portal server 59
upgrade remote monitoring server 54
U OMEGAMON V350 and V360 3
order 22
required authority for installation 22
response file 175
uninstallation 241
Tivoli Distributed Monitoring 3 silent installation 175
agent 247
upgrading 39 worksheets 163
component 244
agents, configuration settings 41 communications protocol 174
Linux 245
Candle Management Workstation desktop client on Linux 173
UNIX 245
coexistence 41 desktop client on Windows 172
Warehouse Proxy 247
CandleNet Portal database 42 Linux or UNIX hub monitoring
Windows 244
installation directory 40 server 165
from the portal 247
Java level, required 42 Linux or UNIX remote monitoring
monitoring component 244
migrated information 42 server 167
Linux 245
order 22 Linux portal server 169
UNIX 245
planning 40 monitoring agent on Linux or
Warehouse Proxy 247
terminology 40 UNIX 171
Windows 244
unsupported OMEGAMON monitoring agent on Windows 170
monitoring environment 241
functions 41 monitoring server communications
Linux 243
Warehouse Proxy database 42 protocol 174
UNIX 243
when to run 40 portal desktop client on Linux 173
Windows 241
upgrading to IBM Tivoli Monitoring 3 portal desktop client on
Warehouse Proxy 247
user authority when installing on Linux Windows 172
uninstalling
or UNIX 22 Windows hub monitoring server 164
event synchronization 248
user security 109 Windows portal server 168
OMEGAMON agents 245
creating a portal user 109 Windows remote monitoring
Universal Agent 6
enabling on hub monitoring server 166
Universal Agent, deploying 143
server 109
UNIX
/etc/hosts file 23
adding application support on
monitoring server 54 W
configuring 179 warehouse migration tool 42
configuring monitoring agents 68 configuring 43
EIB tables 239 planning 42
file descriptors limit 24 running 44
file permissions for configuring status tables 44
monitoring agents 69 Warehouse Proxy 6, 145
fully qualified path names 23 configuration steps 145
host names, setting 23 configuring 151, 153
hub monitoring server 51, 52 creating a Windows user 147
installation considerations 22 creating the database 147
installation user account 22 database, creating 147
installing as root 22 DB2 database configuration 148
installing monitoring agents 67 default user ID 147
maxfiles 24 deploying 146
monitoring agents 67 environment variables 153
Network Interface Cards 23 local database, connecting to 149
NFS environment 23 local ODBC connection 149
planning 22 Microsoft SQL database
remote monitoring server 57 configuration 148
response file configuration 179 migrating OMEGAMON database 42
response file installation 177 ODBC connection, setting up 148
silent configuration 179 planning 146
silent installation 177 registering 151
starting monitoring agents 70 remote database, connecting to 150
TCP/IP network services 23 remote ODBC connection 150
UNIX monitoring server removing 247
advanced configuration 117 supported databases 146
configuring permissions for non-NIS uninstalling 247
Solaris 117 Windows user, creating 147
firewall support 117 Warehouse Summarization and Pruning
KDC_PARTITION 117 agent 6, 145
NAT 117 Windows
desktop client 70

260 IBM Tivoli Monitoring: Installation and Setup Guide




Printed in USA

GC32-9407-00