itm622fp2 admin

8/15/2019 Itm622fp2 Admin

1/425


2/425


3/425


4/425

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

June 2010

This edition applies to version 6, release 2, modification 2, fix pack 2 of IBM Tivoli Monitoring (product number5724-C04 ) and to all subsequent releases and modifications until otherwise indicated in new editions.

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


5/425

Contents

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

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

About this guide . . . . . . . . . . . xi

Chapter 1. Introduction . . . . . . . . 1New in this release . . . . . . . . . . . . 1

New in Version 6.2.2 Fix Pack 2 . . . . . . . 1New in Version 6.2.2 Fix Pack 1 . . . . . . . 4New in Version 6.2.2. . . . . . . . . . . 5New in Version 6.2.1. . . . . . . . . . . 9New in Version 6.2.0 . . . . . . . . . . 11

IBM Tivoli Monitoring family of products . . . . 15Tivoli Management Services components . . . . 15

Tivoli Enterprise Portal client . . . . . . . . 16Desktop, Browser, and Java Web Start clients . . 17Historical data collection . . . . . . . . . 18System administrator tasks . . . . . . . . 18

Chapter 2. Preparing your TivoliEnterprise Portal environment . . . . 19Browser client . . . . . . . . . . . . . 19

Java runtime environment (JRE) versions . . . 19Allocating additional memory for the applet . . 19First time logon . . . . . . . . . . . . 21Internet Explorer security settings . . . . . . 21Windows write and delete privileges . . . . . 22Adding your company logo and URL . . . . 22

Starting the Tivoli Enterprise Portal client . . . . 23Using Web Start to download and run the desktopclient . . . . . . . . . . . . . . . . 23

Installing the IBM JRE . . . . . . . . . . 24Enabling tracing for the JRE . . . . . . . . 25Downloading and running the desktop client . . 26Manually creating a shortcut for the Web Startclient . . . . . . . . . . . . . . . 27

Starting the desktop client on another portal server 28Starting the browser client on another portal server 28Specifying the browser used for Launch Applicationand for online help . . . . . . . . . . . . 30Add operating platforms to the Navigator view . . 31Secure Socket Layer transmissions. . . . . . . 32Enabling TIP Web Service for Tivoli IntegratedPortal charts . . . . . . . . . . . . . . 32

Chapter 3. Editing the portalconfiguration settings . . . . . . . . 35Tivoli Enterprise Portal client configuration settings 35

Editing the client parameters . . . . . . . 35Portal client parameter list . . . . . . . . 36Enabling the HTTP proxy server . . . . . . 41Setting application properties for Linux andUNIX systems . . . . . . . . . . . . 42

Setting the environment variable when the hub ison a z/OS system . . . . . . . . . . . 43

Tivoli Enterprise Portal Server configuration settings 44Editing the portal server environment file . . . 44Portal server environment variables . . . . . 45Pruning events on the portal server database . . 46Controlling the size of event attachments . . . 47Controlling the number of logon attempts . . . 48Duper process for optimizing situations . . . . 49Enabling FIPS for the Tivoli Enterprise PortalServer . . . . . . . . . . . . . . . 50

Chapter 4. Setting up asymmetricencryption . . . . . . . . . . . . . 53Setting the JRE for GSKit and starting Key Manager 53Creating a new key database . . . . . . . . 54

Creating a new public-private key pair andcertificate request . . . . . . . . . . . . 54Using a temporary self-signed certificate. . . . . 55Receiving the CA-signed certificate . . . . . . 55Saving the password to a stash file . . . . . . 56

Chapter 5. Enabling user authentication 57User authentication through the hub monitoringserver . . . . . . . . . . . . . . . . 58

Prerequisites for configuring authentication onthe hub monitoring server . . . . . . . . 58Configuration procedure . . . . . . . . . 60Ldapsearch for LDAP information . . . . . . 62

User authentication through the portal server . . . 64Prerequisites for configuring authentication onthe portal server . . . . . . . . . . . . 64About single sign-on . . . . . . . . . . 66Using Manage Tivoli Monitoring Services toconfigure the portal server for LDAPauthentication . . . . . . . . . . . . 68Using the Linux or UNIX command line toconfigure the portal server for LDAPauthentication . . . . . . . . . . . . 71TEPS/e administration console . . . . . . . 72Mapping Tivoli Enterprise Portal user IDs toLDAP distinguished names . . . . . . . . 75Importing and exporting LTPA keys . . . . . 76

Reconfiguring the browser client for SSO . . . 77Tivoli Enterprise Portal distinguished names . . . 77Migrating authentication from the monitoring serverto the portal server . . . . . . . . . . . . 78

Chapter 6. User administration . . . . 81Administer Users . . . . . . . . . . . . 81

Users and User Groups . . . . . . . . . 82Permissions . . . . . . . . . . . . . 82Applications . . . . . . . . . . . . . 85Navigator views . . . . . . . . . . . . 86Member Of and Members . . . . . . . . 86

© Copyright IBM Corp. 2005, 2010 iii


6/425

Managing user IDs . . . . . . . . . . . . 86Adding a user ID . . . . . . . . . . . 86Viewing and editing a user ID . . . . . . . 88Removing a user ID . . . . . . . . . . 89Default user . . . . . . . . . . . . . 89

Managing user groups. . . . . . . . . . . 90Viewing user group memberships . . . . . . 90Adding a user group . . . . . . . . . . 90Reviewing and editing a user group . . . . . 91Removing a user group . . . . . . . . . 92

Notes on user administration . . . . . . . . 93Troubleshooting logon error messages . . . . . 95

Chapter 7. Situation event integrationwith Tivoli Enterprise Console . . . . 99Default mapping of situation events to TivoliEnterprise Console events . . . . . . . . . 99

Expanding a generic event message situationdescription . . . . . . . . . . . . . 101Generic mapping for agent specific slots . . . 101Assigning severity for Tivoli Enterprise Console

events . . . . . . . . . . . . . . . 103Localizing message slots . . . . . . . . . 103Situation event statuses and Tivoli EnterpriseConsole event generation . . . . . . . . 104

Synchronizing situation events . . . . . . . 106Checking the Tivoli Enterprise Console eventcache . . . . . . . . . . . . . . . 106Changing the configuration of the eventsynchronization on the event server . . . . . 107Defining additional monitoring servers for theevent synchronization on the event server. . . 107Closing sampled events . . . . . . . . . 108

Changing rule set parameters for the omegamon.rlsrule set file . . . . . . . . . . . . . . 108

Tuning considerations . . . . . . . . . 110Using the Rules Check utility . . . . . . . . 110Editing the Event Integration Facility configuration 111Specifying EIF forwarding for a situation event . . 113Customizing the event message . . . . . . . 115Updating the XML used by the MCS AttributeService . . . . . . . . . . . . . . . 115Displaying events from the Universal Agent on theTivoli Enterprise Console . . . . . . . . . 117Using the NetView console through the TivoliEnterprise Console event viewer . . . . . . . 118

Chapter 8. Situation event integrationwith Tivoli Netcool/OMNIbus . . . . . 121Default mapping of situation events to OMNIbusalerts . . . . . . . . . . . . . . . . 121

Expanding the description of a generic eventmessage situation . . . . . . . . . . . 124Generic mapping for agent specific slots . . . 125Localizing alert summaries . . . . . . . . 126

Synchronizing situation events . . . . . . . 126Changing the configuration of the eventsynchronization on the event server . . . . . 126Defining additional monitoring servers for theevent synchronization on the ObjectServer. . . 127

Deleted or cleared sampled situation events . . 127Customizing the OMNIbus configuration . . . . 128Editing the Event Integration Facility configuration 129Specifying situation events that send an OMNIbusevent . . . . . . . . . . . . . . . . 131Customizing the event message . . . . . . . 131

Chapter 9. Configuring connectors forthe common event console . . . . . 133Common Event Console Configuration window 133

ITM Connector tab . . . . . . . . . . 134TEC Connector tab . . . . . . . . . . 134OMNIbus Connector tab . . . . . . . . 136Names of Extra Columns tab . . . . . . . 137

Best practices for using event synchronization . . 139Troubleshooting problems with connection to TivoliEnterprise Console server on Linux systems . . . 139

Chapter 10. Maintaining monitoringagents . . . . . . . . . . . . . . 141Adding an agent through the Tivoli EnterprisePortal . . . . . . . . . . . . . . . . 141Configuring an agent through the Tivoli EnterprisePortal . . . . . . . . . . . . . . . . 142Starting, stopping, and recycling an agent throughthe Tivoli Enterprise Portal . . . . . . . . . 143Updating agents . . . . . . . . . . . . 144

Updating an agent through the Tivoli EnterprisePortal . . . . . . . . . . . . . . . 144Updating an agent through the command-lineinterface . . . . . . . . . . . . . . 145

Removing an agent through the Tivoli EnterprisePortal . . . . . . . . . . . . . . . . 146Changing the monitoring server an agent connectsto . . . . . . . . . . . . . . . . . 146

Chapter 11. Agent ManagementServices . . . . . . . . . . . . . 149Features of the Tivoli Agent Management Services 149Tivoli Agent Management Services installation andconfiguration . . . . . . . . . . . . . 151Monitoring the availability of agents . . . . . 155Managing the agent manually . . . . . . . . 155

Chapter 12. Agent autonomy . . . . . 157Autonomous capabilities . . . . . . . . . 157Environment variables for autonomous behavior 160Situation limitations . . . . . . . . . . . 167

UTF-8 encoded XML files . . . . . . . . . 170Configuring Agent Management Services on TivoliSystem Monitor Agents . . . . . . . . . . 171Private situations . . . . . . . . . . . . 172

Private situation operation . . . . . . . . 172Private situation XML specification . . . . . 175Exported enterprise situation XML specification 180Private situation examples . . . . . . . . 185

Private history . . . . . . . . . . . . . 190Situation override XML specification . . . . . 192SNMP alerts . . . . . . . . . . . . . . 197

iv IBM Tivoli Monitoring: Administrator's Guide


7/425

SNMP alert configuration . . . . . . . . 197Trap configuration XML specification . . . . 199MIB for SNMP alerts and agent emits . . . . 207OMNIbus configuration for SNMP . . . . . 208

EIF events . . . . . . . . . . . . . . 213EIF event configuration . . . . . . . . . 213EIF event mapping XML specification . . . . 216EIF event destination configuration XMLspecification . . . . . . . . . . . . . 221Common slots for EIF emitted events . . . . 223EIF life cycle event . . . . . . . . . . 224EIF heartbeat event . . . . . . . . . . 225Master reset event . . . . . . . . . . . 226

Agent Service Interface . . . . . . . . . . 227Starting the Agent Service Interface . . . . . 227Access Authorization Group Profile . . . . . 228Agent Service Interface - Agent Information . . 232Agent Service Interface - Situations . . . . . 233Agent Service Interface - History . . . . . . 234Agent Service Interface - Queries. . . . . . 235Agent Service Interface - Service InterfaceRequest . . . . . . . . . . . . . . 236

Chapter 13. Centralized Configuration 255Centralized Configuration overview. . . . . . 255Centralized Configuration design. . . . . . . 257Configuration load list XML specification . . . . 261

Configuration load list keyword substitution 267Environment variables in the configuration loadlist . . . . . . . . . . . . . . . . 268Bootstrap configuration load list . . . . . . 269

Environment variables for CentralizedConfiguration . . . . . . . . . . . . . 270Enable password encryption in configuration fileson z/OS . . . . . . . . . . . . . . . 273

Centralized Configuration sample setup . . . . 274Centralized Configuration startup . . . . . . 278

Initiating Centralized Configuration with agentenvironment variables . . . . . . . . . 278Initiating Centralized Configuration with a loadlist file. . . . . . . . . . . . . . . 280Initiating Centralized Configuration with aservice interface request . . . . . . . . . 283

Agent autonomy on z/OS . . . . . . . . . 285

Chapter 14. Managing historical data 287About historical data collection . . . . . . . 287Historical data collection configuration . . . . . 289Changing the directory for short-term history files 293

Performance impact of historical data requests . . 293Impact of large amounts of historical data onthe monitoring server or agent . . . . . . 294Requests for historical data from large tables 295Scheduling the warehousing of historical data 295Using a data mart to improve long or complexqueries . . . . . . . . . . . . . . 295

Conversion process for using delimited flat files 298Estimating space required to hold historical datatables . . . . . . . . . . . . . . . 299Limiting the growth of short-term history files 299

What to do when the short-term history filedirectory size reaches its limit . . . . . . . 300

Tivoli Data Warehouse and short-term historyconfiguration . . . . . . . . . . . . . 301Summarization and pruning configuration . . . 303

About the summarization and pruning agent 303Best practices for summarization and pruning 306Summarized and pruned data availability . . . 307Configuring summarization and pruning forattribute groups . . . . . . . . . . . 308Changing global configuration settings . . . . 309How to disable the Summarization and Pruningagent . . . . . . . . . . . . . . . 312

Error logging for stored data . . . . . . . . 312Collecting Agent Operations Log history . . . . 313Converting short-term history files to delimited flatfiles . . . . . . . . . . . . . . . . 314

Converting history files to delimited flat files onWindows systems . . . . . . . . . . . 315Converting history files to delimited flat files onan i5/OS system . . . . . . . . . . . 317Converting history files to delimited flat files onUNIX Systems . . . . . . . . . . . . 318Converting history files to delimited flat files onHP NonStop Kernel Systems . . . . . . . 320Converting history files to delimited flat files onz/OS systems . . . . . . . . . . . . 321

Chapter 15. Tivoli Common Reporting 327Tivoli Common Reporting overview. . . . . . 327Prerequisites for Tivoli Common Reporting . . . 328Upgrading from a previous version . . . . . . 329Limitations . . . . . . . . . . . . . . 330Importing and running Cognos reports. . . . . 330

Creating shared dimensions tables and

populating the time dimensions table . . . . 330Creating and populating the resource dimensiontable . . . . . . . . . . . . . . . 333Connecting to the Tivoli Data Warehouse usingthe database client over ODBC . . . . . . 335Installing and running IBM Cognos reports . . 336

Importing and running BIRT reports . . . . . 337Ensure that historical reporting is enabled . . . 337Import a BIRT report package . . . . . . . 338Configure the data source . . . . . . . . 339Generate a sample BIRT report . . . . . . 340

Chapter 16. Replicating the TivoliEnterprise Portal Server database . . 343Understanding the Tivoli Enterprise Portal Serverdatabase . . . . . . . . . . . . . . . 343Running the migrate-export script . . . . . . 344Running the migrate-import script . . . . . . 345

Running migrate-import from source Windowsto target Windows. . . . . . . . . . . 345Running migrate-import from source Windowsto target Linux or UNIX . . . . . . . . . 346Running migrate-import from source Linux orUNIX to target Windows . . . . . . . . 347

Contents v


8/425

Running migrate-import from source Linux orUNIX to target Linux or UNIX . . . . . . 348

Appendix A. Tivoli EnterpriseMonitoring Web Services . . . . . . 349Configuring Tivoli Monitoring Web Services (SOAPServer) . . . . . . . . . . . . . . . 349

Defining hubs . . . . . . . . . . . . 349Adding users . . . . . . . . . . . . 351Configuring IBM Tivoli Monitoring WebServices (SOAP Server) on UNIX and Linuxsystems . . . . . . . . . . . . . . 351Tuning SOAP transaction performance on AIXsystems . . . . . . . . . . . . . . 352

About the SOAP client . . . . . . . . . . 352Using IBM Tivoli Monitoring Web services . . . 353

User IDs . . . . . . . . . . . . . . 353Starting the SOAP client and making a request . . 353

Using your browser . . . . . . . . . . 354Using the SOAP client command-line utility(kshsoap) . . . . . . . . . . . . . . 354

Issuing SOAP requests as system commands 355SOAP methods . . . . . . . . . . . . . 356

Issuing second-level SOAP requests . . . . . 364Sample CT_Get SOAP request. . . . . . . 365

IBM Tivoli Monitoring Web services scenarios . . 366Generating daily logical operation summariesand charts . . . . . . . . . . . . . 366Obtaining data snapshots and offline table andcharts . . . . . . . . . . . . . . . 367Sending alerts into an IBM Tivoli Monitoringplatform . . . . . . . . . . . . . . 368

Creating collaborative automation using SAIOM . . . . . . . . . . . . . . . 368Acknowledging an event within an IBM TivoliMonitoring platform . . . . . . . . . . 369Report contents. . . . . . . . . . . . 369

Appendix B. Using the Tivoli

Management Services DiscoveryLibrary Adapter . . . . . . . . . . 371

Appendix C. MIB SNMP agent eventdescriptions . . . . . . . . . . . . 373

Appendix D. Agent operation log . . . 379

Documentation library . . . . . . . 381IBM Tivoli Monitoring library . . . . . . . . 381

Documentation for the base agents . . . . . 382Related publications . . . . . . . . . . . 383Other sources of documentation . . . . . . . 383

Support information . . . . . . . . 385

Notices . . . . . . . . . . . . . . 389

Glossary . . . . . . . . . . . . . 393

Index . . . . . . . . . . . . . . . 403

vi IBM Tivoli Monitoring: Administrator's Guide


9/425


10/425


11/425

Tables

1. File locations for changing applicationproperties for UNIX and Linux systems . . . 42

2. Tasks to complete before configuringauthentication. . . . . . . . . . . . 583. LDAP configuration parameters. . . . . . 594. SSL parameters for communication between

hub and LDAP server . . . . . . . . . 605. ldapsearch command line options and

corresponding monitoring server configurationparameters . . . . . . . . . . . . . 63

6. LDAP configuration parameters. . . . . . 657. SSO parameters . . . . . . . . . . . 668. Tivoli Enterprise Console event class

attributes . . . . . . . . . . . . . 1009. Special characters for attribute groups and

names in Tivoli Enterprise Console events

generated from forwarded situation events. . 10210. Situation name suffix mapping to Tivoli

Enterprise Console event severity. . . . . 10311. Tivoli Netcool/OMNIbus ObjectServer

attributes . . . . . . . . . . . . . 12212. Mapping of situation attributes to OMNIbus

attributes . . . . . . . . . . . . . 12313. Special characters for attribute groups and

names in EIF events generated fromforwarded situation events . . . . . . . 125

14. Availability of situation formula functionswhen an enterprise agent is connected ordisconnected, or when the situation is private. 167

15. TrapDest element XML specification . . . . 200

16. TrapAttrGroup element XML specification 20217. Situation element XML specification . . . . 20318. Agent life cycle status traps. . . . . . . 20519. StatTrap element XML specification . . . . 20620. Set of common slots for emitted EIF events. 22321. EIF life cycle events. . . . . . . . . . 22422. EIF life cycle event ITM_StatEvent class slot

values. . . . . . . . . . . . . . . 22523. Master reset event content. . . . . . . . 22624. Access Authorization Group permissions for

Service Interface commands. . . . . . . 22925. Agent Service Interface - Queries sample

attribute listing . . . . . . . . . . . 23626. Agent Service Interface - Queries sample

report . . . . . . . . . . . . . . 23627. Agent Service Interface

request. . . . . . . . . . . . . . 23628. Agent Service Interface

request output. . . . . . . . . . . . 237

29. Agent Service Interface request. . . . . . . . . . . . . . 238

30. Agent Service Interface request output. . . . . . . . . . . . 23831. Agent Service Interface request. 23832. Agent Service Interface request

output.. . . . . . . . . . . . . . 23933. Agent Service Interface


request output. . . . . . . . . . . . 23935. Agent Service Interface request 24136. Agent Service Interface request

output.. . . . . . . . . . . . . . 24237. Agent Service Interface request 24538. Agent Service Interface request

output.. . . . . . . . . . . . . . 24539. Agent Service Interface


request output. . . . . . . . . . . . 24641. Agent Service Interface





request. . . . . . . . . . . . . . 25046. Agent Service Interface request

output.. . . . . . . . . . . . . . 25147. Configuration load list element

and the Activate options available for theDisp type.. . . . . . . . . . . . . 266

48. Keywords for the configuration load list. 26749. Summarization functions. . . . . . . . 30450. Parameters for the krarloff rolloff program 31751. DD names required . . . . . . . . . 32352. KPDXTRA parameters . . . . . . . . 32353. TCP/IP Fields in Hub Specification Dialog 35054. SNA Fields in Hub Specification Dialog 35055. SNMP trap variables for agentStatusEvent 373

56. SNMP trap variables foragentSitSampledEvent . . . . . . . . 374

57. SNMP trap variables for agentSitPureEvent 376

© Copyright IBM Corp. 2005, 2010 ix


12/425

x IBM Tivoli Monitoring: Administrator's Guide


13/425

About this guide

This guide describes the administration of your IBM® Tivoli® Monitoringinfrastructure, Tivoli Management Services.

The chapter topics cover the following tasks:

v Configuring, customizing, and maintaining the Tivoli Enterprise Portal clientsand server

v Setting up asymmetric encryption using public-private key files

v Enabling user authentication on the hub Tivoli Enterprise Monitoring Serversystem registry or an external LDAP registry

v Maintaining user IDs and user groups on the Tivoli Enterprise Portal

v Integrating the situation event activities between the Tivoli Enterprise Consoleevent server or the Netcool/OMNIbus Probe for Tivoli EIF and the hubmonitoring server

v Configuring connectors for the event systems that send event information to theTivoli Enterprise Portal

v Using the Tivoli Enterprise Portal to maintain agents that support the remoteagent deployment feature

v Configuring Tivoli Enterprise Monitoring Agents for autonomous operation

v Setting up and enabling Centralized Configuration

v Managing historical data collection and the Tivoli Data Warehouse

v Importing reports for Tivoli Common Reporting that are unique to products thatrun on the Tivoli Enterprise Portal and use the Tivoli Data Warehouse as thesource of historical data for generating reports. This information is intended forthe administrator who sets up Tivoli Common Reporting and installs reportpackages

v Replicating the Tivoli Enterprise Portal Server database to another computer orto keep as a backup

v Using IBM Tivoli Monitoring Web Services SOAP methods to query and controlyour monitored environment

Users of this book should be familiar with performance monitoring concepts andadministration. If you use the IBM Tivoli Data Warehouse, you must be familiarwith the operating system that hosts the warehouse. To learn more about thisfamily of products, see http://www-306.ibm.com/software/tivoli/solutions/availability/products.html.

© Copyright IBM Corp. 2005, 2010 xi

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


14/425

xii IBM Tivoli Monitoring: Administrator's Guide


15/425

Chapter 1. Introduction

This chapter reviews the new features and enhancements to the Tivoli EnterprisePortal interface and Tivoli Management Services administrative features, followed

by a list of the administrative tasks you can expect to perform.

For information on how to use the Version 6.2.2 Tivoli Enterprise Portal features,please consult the integrated help (Help → Contents and Index) or the IBM Tivoli

Monitoring Tivoli Enterprise Portal User's Guide.

New in this release

Review the latest enhancements to the Tivoli Enterprise Portal and to the TivoliManagement Services components that are relevant to the Administrator's Guide.

New in Version 6.2.2 Fix Pack 2This topic describes enhancements to the Tivoli Management Services componentsthat affect the system administrator since the release of Version 6.2.2 Fix Pack 1.

Centralized Configuration to maintain local configuration files from a centrallocation

You can implement a configuration load list XML file to pull localconfiguration file updates from one or more central locations that serveagents throughout the monitored enterprise. Using the repository, you caninstall or maintain monitoring agents (or both) and download all requiredfiles to become fully operational. See Chapter 13, “CentralizedConfiguration,” on page 255.

The new tacmd getfile and tacmd putfile CLI commands are useful for

implementing Centralized Configuration and agent autonomy. See IBMTivoli Monitoring Command Reference for details.

Send agent heartbeat as an EIF event or SNMP alert to a receiverYou can now monitor the online status of a monitoring agent byconfiguring the heartbeat interval that sends a heartbeat event to a receiverafter each interval. See “EIF heartbeat event” on page 225

Agent Management Services enables instance-specific CAP filesIn previous releases only one executable or 'family' of executable files wassupported per CAP (common agent package) file, thus multi-instancemonitoring agent instances were governed by the same CAP file. Now youhave the ability to configure CAP files for specific instances of monitoringagents.

Agent Management Services disabled on zLinux OS agentIn previous versions Agent Management Services was enabled on thezLinux OS agent. Now it is disabled, even if it was enabled beforeupgrading to V6.2.2 Fix Pack 2. The watchdog must be enabled manually.See “Tivoli Agent Management Services installation and configuration” onpage 151.

Autonomous operation of the Tivoli Data Warehouse agentsTo enable autonomous agents to write out their accumulated historical datato the Tivoli Data Warehouse without the intervention of the Tivoli

© Copyright IBM Corp. 2005, 2010 1

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htm


16/425

Enterprise Monitoring Server and thereby prevent loss of such data, thewarehouse agents have been enhanced to allow them to run autonomously.

Run Warehouse Proxy agent without requiring registration with theTivoli Enterprise Monitoring ServerThe Warehouse Proxy can be configured to run with no connection to thehub monitoring server.

Monitoring agents can be configured to specify the location of theirWarehouse Proxy agent instance, bypassing any other methods of obtaining its address. See the KHD-prefixed environment variables in“Control autonomy in Tivoli Enterprise Monitoring Agents” on page 161.

Run Summarization and Pruning agent without requiring connection tothe Tivoli Enterprise Portal ServerIn previous releases the summarization and pruning configuration settingsfor attribute groups that have been configured for historical data collectionwere stored on the Tivoli Enterprise Portal Server database in a tablenamed KDWHISTDATA. The summarization and pruning configurationhas been moved from the portal server to the Tivoli Data Warehousedatabase in a table named WAREHOUSESUMPRUNE. After the portal

server and summarization and pruning agent have been upgraded toTivoli Monitoring V6.2.2 Fix Pack 2, the next time summarization andpruning takes place and the portal server is restarted, the migration of thesummarization and pruning configuration occurs automatically.

See “Configuring a Summarization and Pruning agent to runautonomously” in IBM Tivoli Monitoring Installation and Setup for acomplete description.

Tivoli Common Reporting V1.3The current version of Tivoli Common Reporting is Version 1.3, whichintroduces IBM Cognos Business Intelligence and Reporting Version 8.4reports for the Tivoli Monitoring OS Agents and other monitoringproducts. A set of predefined reports is provided on a separate eAssembly

media package for monitoring individual, multiple, and enterpriseresources. See Chapter 15, “Tivoli Common Reporting,” on page 327 andthe user's guide for your Tivoli Enterprise Monitoring Agent.

Filtered historical data collectionThe Tivoli Monitoring Version 6.2.2 release included the added capabilityof configuring multiple data collections for the same attribute groups withdifferent settings and managed system distributions. Also added was theability to create historical groups of historical collections that share thesame managed system distribution.

Now you can write filter criteria to specify the data to collect. The newFilter tab in the Historical Collection Configuration editor has a formulaeditor much like what you have in the Situation editor. Historical collectionof a data sample occurs only if the values in the data row fulfill the filtercriteria. For example, if the data sample has % Disk Write Time greaterthan 50%, it is saved to short-term history; otherwise the sample is notsaved. See step 9 of “Creating a historical collection” in the Tivoli EnterprisePortal User's Guide.

The command-line interface tacmd histcreatecollection and tacmdhisteditcollection commands have been updated to include the filteroption for adding a filter formula; the tacmd histviewcollection and tacmdhistlistcollections commands display any defined filter for a historicalcollection; and tacmd histviewattributegroup has been updated to add the

2 IBM Tivoli Monitoring: Administrator's Guide

http://idd.tivlab.austin.ibm.com:8228/help/topic/com.ibm.itm.doc_6.2.2fp2/cfg_spa_auto.htmhttp://idd.tivlab.austin.ibm.com:8228/help/topic/com.ibm.itm.doc_6.2.2fp2/cfg_spa_auto.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/history_configurecollection_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm622fp2_tepuser.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm622fp2_tepuser.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm622fp2_tepuser.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm622fp2_tepuser.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm622fp2_tepuser.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/history_configurecollection_tep.htmhttp://idd.tivlab.austin.ibm.com:8228/help/topic/com.ibm.itm.doc_6.2.2fp2/cfg_spa_auto.htmhttp://idd.tivlab.austin.ibm.com:8228/help/topic/com.ibm.itm.doc_6.2.2fp2/cfg_spa_auto.htm


17/425

-v verbose option to include the table name and attribute names in thedisplay. See IBM Tivoli Monitoring Command Reference.

Dynamic items for custom Navigator viewsThe Navigator Physical view is a discovered view and the NavigatorLogical view is a predefined, customizable view. You can also createcustom Navigator views for different logical hierarchies. Because custom

Navigator views are user-defined, these views are not updated in the TivoliEnterprise Portal when new managed systems come online. You mustmanually add them using Navigator editor.

Now you can assign managed system groups to Navigator items asdynamic members in the new Dynamic items tab of the Navigator itemproperties editor. As managed systems are added or removed from thegroup, the constituent members change dynamically within this branch of the Navigator. New managed systems that fit the filter criteria of themanaged system group are added automatically.

See “Navigator item properties”.

Define schedules for running situation overridesIn previous releases you could apply a predefined schedule, such asWeekend, to specify when the situation expression override is run. You cannow create your own calendar-based schedule or hourly schedule for eachexpression override that you create for a situation.

Also in previous releases, the only way to define a schedule for a situationexpression override was through the command-line interface tacmdaddCalendarEntry. As well as shared calendar-based schedules in theSituation editor, you can define repeating hourly schedules that apply tospecific hourly time ranges.

See “Creating a situation override”.

The CLI tacmd setOverride, tacmd deleteOverride, tacmdsuggestBaseline, and tacmd acceptBaseline commands have been updated

to include the inlinecal option for specifying the inline (hourly) calendarschedule. See IBM Tivoli Monitoring Command Reference.

Model Expression dialog for testing situation override scenariosTivoli Monitoring V6.2.2 introduced the expression modeling feature tovisually assist the situation author in establishing proper threshold values

based on historical data and statistical analysis (see “Model Situation”).That same capability has now been added for situation expressionoverrides.

This new visual modeling capability also integrates the ability todynamically build and associate daily schedules to expression overridesusing drag-and-drop gesturing. See “Model Expression”.

Monitored baselining for charts indicate situation override expressionsThe Add Monitored Baseline tool was added to the chart views inTivoli Monitoring V6.2.2 for you to visualize the attribute threshold valuesfrom associated situations alongside the historical or real-time informationdisplayed. If expression overrides are associated with the situation, youcan now visualize them in the chart as well. You can optionally filter outsituation and expression overrides that are inactive based on the datasample and time span being rendered in the view.

See “Adding monitored baselines to a chart”.

Chapter 1. Introduction 3

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_navitemprops.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/situation_overridecreate_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_establishbaseline.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_sited_overridemodel.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/chart_baselinemonitored_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/chart_baselinemonitored_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_sited_overridemodel.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_establishbaseline.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/situation_overridecreate_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/dlg_navitemprops.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htm


18/425

New and enhanced CLI tacmdsNew tacmd getfile and tacmd putfile commands are available fortransferring files between remote managed systems and a local computer.

New tacmd commands are available for replicating Navigator view orNavigator item managed system assignments:

listSysAssignments to list all managed systems and managed system

groups that are assigned to a Navigator item.exportSysAssignments to export all managed system assignments forthe specified Navigator item or the entire Navigator view..

importSysAssignments to import all managed system assignments fora Navigator item or Navigator view.

deleteSysAssignments to delete the specified situation association forthe given navigator item

The tacmd listworkspaces has been enhanced to include the TivoliEnterprise Portal objectid in the workspace listing. By using the new tacmddeleteWorkspace command, you can indicate the workspace to delete byits objectid name.

New tacmd commands are available for changing situation associationswith Navigator items:

listSitAssociations to list all situation associations defined for anavigator item

createSitAssociation to create a situation association for the givennavigator item

exportSitAssociations to export all situation associations on the server

importSitAssociations to import all situation associations specified in afile

deleteSitAssociation to delete the specified situation association for thegiven navigator item

These commands have a new inlinecal option for specifying an inline(hourly schedule) calendar entry for situation overridses: tacmdsetOverride, tacmd suggestBaseline, tacmd acceptBaseline, and tacmddeleteOverride.

These commands have a new filter option for adding a formula forpre-filtering data collection: tacmd histcreatecollection and tacmdhisteditcollection. The tacmd histviewattributegroup command has a newverbose option for displaying the table name and attributes names definedfor an attribute group.

See IBM Tivoli Monitoring Command Reference

New in Version 6.2.2 Fix Pack 1This topic describes enhancements to the Tivoli Management Servicesadministration since the release of Version 6.2.2.

TEDGEN can be run from the hub monitoring server or portal serverThe TEDGEN tool provides an alternate method for generating a new XMLfile for EIF Slot Customization. There are now three places where you canrun the TEDGEN tool if the necessary baroc files are on the samecomputer:

1. On the computer where the Tivoli Enterprise Console event server isinstalled.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.2fp2/itm_cmdref.htm


19/425

2. On the computer where the hub Tivoli Enterprise Monitoring Server isinstalled.

3. On the computer where the Tivoli Enterprise Portal Server is installed.

See “Updating the XML used by the MCS Attribute Service” on page 115.

Send EIF events for private situationsYou can configure a monitoring agent and an EIF event configuration fileto emit life cycle events or private situation events, or both, directly to anEIF receiver such as the Tivoli Enterprise Console event server orNetcool/OMNIbus Probe for Tivoli EIF, with no connection to the TivoliEnterprise Monitoring Server. See “EIF event configuration” on page 213.

Agent Management Services expanded supportSupport has been added for these products:

v IBM Tivoli Monitoring for Databases: Oracle Agent

v IBM Tivoli Monitoring for Databases: Sybase Agent

v IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoAgent (including 64-bit)

v IBM Tivoli OMEGAMON XE for Messaging

Also, Windows OS agents and Lotus Domino agents on 64-bit systemshave Common Agent Package XML files installed in the TMAITM6_x64\CAPdirectory rather than TMAITM\CAP. See Chapter 11, “Agent ManagementServices,” on page 149.

New in Version 6.2.2This topic describes enhancements to the Tivoli Management Services that arerelevant to this guide since the release of Version 6.2.1. Many of the changes areobvious as soon as you log on, such as the new toolbar icons. Others are changesin behavior or changes that are not apparent until you open workspaces or one of the editors.

The Tivoli Enterprise Portal client features are described in the online help andIBM Tivoli Monitoring Tivoli Enterprise Portal User's Guide.

User interface updatesThe toolbar buttons and graphic icons have been updated and consolidatedto further align the Tivoli user interfaces. Move the mouse pointer over atool in the Tivoli Enterprise Portal to see its identity.

Tivoli Enterprise Portal Version 6.2.1Desktop mode:

Browser mode:

Tivoli Enterprise Portal toolbar for Version 6.2.2Some of the icons have been regrouped to align them with theirfunction: Switch to Home Workspace has moved to the firstposition in the toolbar, next to Back in the desktop modetoolbar, and Save in the browser mode toolbar; and theSituation Event Console, Common Event Console, andTivoli Enterprise Console views are grouped near the end of thetoolbar.Desktop mode:



20/425


21/425

Baseline tool for selecting a situation to compare with the currentsampling and anticipated values. The plot chart and area chart also have anew Add Statistical Baseline tool with statistical functions. In addition,the plot chart has a new Add Historical Baseline tool for comparingcurrent samplings with a historical period. See Chart baselines.

Situation overrides can be assigned to subnodes

Situation overrides for dynamic thresholding has been extended to includesubnodes. For situations that are distributed to managed systems that aresubnodes of other managed systems, you can now apply expressionoverrides to the managed system subnodes. See Situation overrides fordynamic thresholding.

Tivoli System Monitor AgentThe Tivoli System Monitor Agent is a new category of monitoring agent. Itis an OS agent that is installed and configured to have no dependency onnor any connection to a monitoring server. It must be installed on acomputer where no other Tivoli Monitoring products or TivoliManagement Services components are installed, with the exception of agents created with Agent Builder.

The system monitor agent can run private situations that are defined in asituation configuration XML file; collect historical data, also defined in thesituation configuration XML file, and send SNMP alerts that are defined ina trap destination XML file to an event receiver such as theNetcool/OMNIbus SNMP Probe. See Chapter 12, “Agent autonomy,” onpage 157

Agent autonomy

Agent autonomy is the ability of a monitoring agent to performindependently of the Tivoli Enterprise Monitoring Server. Withenvironment variables introduced in IBM Tivoli Monitoring V6.2.1, theTivoli Enterprise Monitoring Agent can retain event information whencommunications with its monitoring server are interrupted. Now it is the

default behavior that agent startup is independent of the monitoring serverand information is collected at the agent and maintained even if the agentis stopped and started again, ready for transfer to the monitoring serverwhen a connection is made.

Features introduced in this release that can be used by agents without amonitoring server connection are private situations, private history, SNMPalerts, and the Agent Service Interface. See Chapter 12, “Agent autonomy,”on page 157.

Create private situations that run locally, independent of the monitoring serverPrivate situations are created in a local private situation configuration XMLfile for a monitoring agent. Situation definitions that were exported fromthe monitored enterprise can also be added to the file to create situations.The events generated by private situations remain local to yourworkstation or can be sent as SNMP alerts to a receiver such as theNetcool/OMNIbus SNMP Probe.

Private situations have the same capability as enterprise situations, withsome limitations. For example, only the Value of expression andCheck for Missing Items formula functions can be used. See “Situationlimitations” on page 167.

Create private history collections that run locally, independent of the monitoringserver Private history is the collection and short-term storage of data from a local


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/chart_baselineintro_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/situation_overrideintro_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/situation_overrideintro_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/situation_overrideintro_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/situation_overrideintro_tep.htmhttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?topic=/com.ibm.itm.doc_6.2.2fp1/chart_baselineintro_tep.htm


22/425

monitoring agent. Define historical collection for each attribute group in aprivate situation configuration file for an agent, then use the Agent ServiceInterface to view the short-term history.

Private history is local only; there is no interaction with a warehouse proxyfor long-term storage on the Tivoli Data Warehouse. However, whendefining the private history, you can change the default 24-hour limit for

historical data storage to as many hours as you like, limited only by thestorage space on the computer. See “Private history” on page 190

Send SNMP trapsSend SNMP alerts from the local Tivoli Enterprise Monitoring Agent orTivoli System Monitor Agent directly to a receiver, without ever connectingto a monitoring server. You create a trapcnfg.xml file and reference thesituations and attribute information to send when the situation becomestrue. When the agent is started, it sends any alerts for the situationsdefined in the file as SNMPv1/v2 traps or SNMPv3 informs to a receiversuch as the Netcool/OMNIbus SNMP Probe. See “SNMP alerts” on page197.

Create situation overrides in a local XML configuration file

As an alternative to creating expression overrides for enterprise situationsin the Tivoli Enterprise Portal, you can define them in an XMLconfiguration file. See Situation override XML specification.

Agent Service InterfaceThe IBM Tivoli Monitoring Service Index has links to service consoles forthe components installed on the computers. Now, when you go to theService Index, you will also see links to the Agent Service Interface. Usethe Agent Service Interface to get reports for an installed agent, whether itis a Tivoli Enterprise Monitoring Agent or Tivoli System Monitor Agent.After logging into the local operating system, you can choose reports of agent information, private situations, private history, and attributedescriptions and current values. You can also make a service interface

request using provided XML elements. See “Agent Service Interface” onpage 227.

Proxy Agent Services renamed to Agent Management ServicesThe Proxy Agent Services have been renamed to Agent ManagementServices to better describe their function. More base agents are supportedand there are new capabilities to report and manage agent instances. SeeChapter 11, “Agent Management Services,” on page 149.

TIP Web Service for Tivoli Integrated Portal chartsIn the previous release, users who wanted to see query-based views in theTivoli Integrated Portal administrative console needed to have workspaceadministrator authority. This is no longer a requirement. Users can nowview through the administrative console any Tivoli Enterprise Portal

workspaces that their user ID has permission to view. For example, if theallowed applications for your user ID include Linux OS application but notDB2, then any Linux OS workspaces are available from the administrativeconsole but not the DB2 workspaces. See “Enabling TIP Web Service forTivoli Integrated Portal charts” on page 32.

Optional agent restartAfter reconfiguring an agent, you can now choose whether to restart theagent immediately for the changes to take effect or to leave the agentrunning and restart it at a later time. The Tivoli Service Manager (ManageTivoli Monitoring Services window) has a new column named



23/425

Configuration to show this status: out-of-sync for configuration changesthat have not been implemented; or up-to-date for configuration changesthat have been implemented by restarting the agent.

Client environment variablescnp.browser.installdir to specify a different path for the browser viewfiles, required if users will be running multiple instances of the portal

client and possibly logging on to different versions of the portal server. See“Portal client parameter list” on page 36.

New in Version 6.2.1This topic describes enhancements to the Tivoli Enterprise Portal and to the othercomponents of Tivoli Management Services that are relevant to this guide since therelease of Version 6.2.0.

The Tivoli Enterprise Portal client features are described in the online help andIBM Tivoli Monitoring Tivoli Enterprise Portal User's Guide.

Dynamic thresholding with situation overrideDynamic thresholding for situations means that you can override the

expression values of a situation formula for a specific managed system (orgroup of managed systems) or for a specific time period or both. Thiscapability enables you to adjust situations for conditions that are specific toa particular managed system or managed system group or to a particulartime period.

Long situation namesSituation names can now be as long as 256 bytes and are no longerrestricted to only letters, numbers, and underscores.

Organize situations and managed systems into named groupsThe Object Group editor is a general, consistent mechanism for creatingnamed groups of objects. The object types that can be grouped aresituations and managed systems. The managed system group is being

retired in this release and all the functions of the managed system groupeditor are now provided by the new object group editor.

Customize the EIF slots in the Situation editor for events that get forwarded toan EIF receiver

Through the EIF (Enterprise Integration Facility) tab of the Situation editor,you can now map situation events to the EIF receiver and customize theforward events.

Area chartThe new area chart view is similar to the plot chart. The difference is thatthe area from the X-axis and Y-axis to the plot point for each data series isfilled with a pattern or color or both.

Chart area thresholds and markers, collapsible legendVisual indicators for value ranges (chart thresholds) and for specific values(chart markers) can be added to the bar, plot, and area charts. Chartlegends can be kept in a collapsible panel and expanded and hidden asneeded to give maximum viewing space to the plot area. As well ascolored labels for the attributes, you can specify a fill pattern.

Zooming in on chart areasOn bar charts, plot charts, and area charts, you can click and drag over anarea of the chart that you would like to zoom into for closer scrutiny, thenpress Esc to return to the previous size.



24/425

Historical navigation mode to synchronize workspacesWhen you open a workspace, the query-based views retrieve the latestvalues. Then, as you open or link to other workspaces, their assignedqueries also retrieve the latest values. However, you might be performinganalysis over multiple workspaces that requires review of a fixed time ortime range. You can turn on Historical navigation mode with a time span thatyou specify. Then, all workspaces you open will align to that time period

until you turn it off.

Options for more frequent warehouse intervalsWhen configuring attribute groups for historical data collection, you havemore choices for the data rolloff from the history files to the Tivoli DataWarehouse. As well as 1 hour and 1 day, you now can select 15 minutes,30 minutes, or 12 hours.

Find Navigator itemsThe Find feature for Navigator items enables you to search for and locateitems by criteria such as product code or associated situation, and usingformula functions. .

Terminal view links

You can now build contextual links from the table and chart views on anOMEGAMON XE workspace to a terminal view in another workspace.

Tabbed workspacesWhen using the Tivoli Enterprise Portal browser client, you can openworkspaces in new tabs if your browser enables them.

Agent deployment status workspacesNew workspaces have been added to the Enterprise Navigator item forshowing deploy depot information and the status of the past, current, andscheduled agent deployments.

Single sign-on support with Java Web Start clientAs well as the browser client, you can now use the Java Web Start client to

launch into the Tivoli Enterprise Portal and out to other Tivoli web-basedand web-enabled solutions without needing to re-enter your authenticationcredentials.

Tivoli Proxy Agent ServicesNew services can monitor the availability of agents and respondautomatically (such as with a restart) if the agent operates abnormally orexits unexpectedly.

Configuring an HTTP proxy server for the browser viewThe procedure for setting up an HTTP proxy server for portal browserview has been simplified and is the same for all Tivoli Enterprise Portalclients.

Enabling FIPS

The Tivoli Enterprise Portal Server has a new environment variable thatcan be enabled for conformance to the Federal Information ProcessingStandard (FIPS) 140–2 specification.

64-bit integers are now supportedSupport for 64–bit integers has been added. Many of the Version 6.2.1products have new attribute groups, attributes, situations, and workspacesthat use the new 64–bit integer values. For example, there are workspaceswith a superseded version that displays queries with a signed 32-bitmaximum value (2,147,483,647) and a version with the same name (minus‘superseded') with queries that support values up to signed 64-bit max



25/425

(9,223,372,036,854,775,807). You will also see similar ‘superseded' notationsfor attribute groups, attributes, and situations that have a 64–bitcounterpart. See your product user's guide for details.

New schema publication tool simplifies generation of SQL statements forcreating the Tivoli Data Warehouse

With the new schema publication tool, you can now generate the SQL

statements needed to create the database objects (data warehouse tables,indexes, functions, views, and ID table inserts) required for initial setup of the Tivoli Data Warehouse. For details, see “Generating SQL statements forthe Tivoli Data Warehouse: the schema publication tool” in the IBM Tivoli

Monitoring Installation and Setup Guide.

Tivoli Data Warehouse now supports DB2 on z/OSYou can now create your Tivoli Data Warehouse repository using DB2running on z/OS. Although the Warehouse Proxy agent still runs only onWindows, Linux, or UNIX, the data warehouse itself is stored in DB2 onz/OS databases. Data communication is supported using either an ODBCor a JDBC connection. See “Tivoli Data Warehouse solution using DB2 onz/OS” in the IBM Tivoli Monitoring Installation and Setup Guide forinstructions on setting up your Tivoli Data Warehouse environment to runwith a DB2 on z/OS repository.

Command Line Interface tacmds for new featuresThe CLI has dozens of new tacmds for many of the new Tivoli EnterprisePortal features and for features that are exclusive to the CLI, such as forexporting queries and custom Navigator views and their associatedsituations. See the IBM Tivoli Monitoring Command Reference for details.

Setting tracesOn Linux and UNIX, the file that contains the KBB_RAS1 parameter forsetting a trace has moved from the .config file in the Install_dir/configdirectory to ms.ini. On distributed operating platforms the value is nolonger enclosed in single quotes. See the IBM Tivoli Monitoring

Troubleshooting Guide for information on setting traces.

New in Version 6.2.0This topic describes enhancements to the Tivoli Enterprise Portal and to the othercomponents of Tivoli Management Services that are relevant to this guide in thisrelease.

Event type tag for SOAP methodsThe CT_Alert, CT_Acknowledge, CT_Reset, and CT_Resurface methodswere modified to support the tag, which specifies the event type.

User groupsThe Administer Users window has been significantly enhanced to enablethe creation of user groups, including assigned permissions.

Lockout and lockout overrideLogon Permitted is a new permission that enables the administrator tolock out a user ID, preventing the user from logging on to the portal serveror to override an automatic lock out, which occurs after a set number of invalid logon attempts.

User authenticationSupport has been added to enable external authentication of TivoliEnterprise Portal users with standards-based Lightweight Directory AccessProtocol (LDAP) to shared registries. The hub monitoring server can be



26/425

configured to validate user IDs and passwords using either the localsystem registry or a central LDAP authentication and authorization system.

Flexible scheduling of summarization and pruningThe Summarization and Pruning agent configuration window has beenenhanced to allow for flexible scheduling and to have the data warehouseand warehouse aggregation logs trimmed automatically after a specified

number of days, months, or years.The Defaults tab has been removed. Now, when you use the HistoryCollection Configuration window to configure historical data collection foran attribute group, no summarization and pruning check boxes are selectedfor you by default.

Null values in summarized historical dataYou now see null in a table cell or chart point when values that wereidentified as invalid were reported from a monitoring agent for a givensummarization period.

More frequent intervals for historical data collectionOne-minute and five-minute intervals have been added to the CollectionInterval options, enabling you to save more frequently to the short-termhistory files at the monitoring agent or monitoring server.

There are no longer pre-selected check boxes for summarization andpruning when you configure historical data collection for an attributegroup.

Common and Tivoli Enterprise Monitoring Server attributesThe common attribute groups, Local Time and Universal Time, have a newTime attribute for the time of the data sampling corrected for local timezone and daylight saving time.

Two of the Tivoli Enterprise Monitoring Server attribute groups also havenew attributes: The Managed System Status attribute group adds a Reasonattribute for the two-character reason code, if one exists, for the managed

system status. The Situation Definition attribute group adds a new LastRelease attribute to identify the release of the product to associate with thesituation.

If your product was updated for this release of IBM Tivoli Monitoring,check the New in this release section of the product user's guide for a listof the new and updated attribute groups.

Some distributed products might require that you create new queries before you can see the new attributes in the query or queries for thatattribute group or see no query for a new attribute group.

Seven event severitiesThe state of an event that opens for a true situation can be set to

informational, warning, or critical. Now you have four additional states tochoose from for associated situations, table view thresholds, and forfiltering an event console view: Unknown, Harmless, Minor, and

Fatal.

Table view threshold iconsThe table view has a feature that highlights the background of any cellwhose value exceeds a given threshold. Before this release, thresholdingwas limited to three background colors to indicate an informational,



27/425

warning, or critical severity. Now, as well as having four more severitiesavailable, you can choose to display either an icon in the cell ( ) or a

background color ( ).

Table view style propertiesA new option on the Style tab and in the workspace presentation cascadingstyle sheet enables you to control the default font styling of table view

header and footer text.Common event console view

The common event console enables you to view and manage events fromthe Tivoli Enterprise Monitoring Server in the same way as the situationevent console, plus it incorporates events from the Tivoli EnterpriseConsole event server and the Tivoli Netcool/OMNIbus ObjectServer if your managed environment is configured for those servers.

Situation editor EIF tabThe new EIF (event integration facility) tab has options for forwardingevents that open for the situation to one or more EIF receivers and tospecify the severity. The tecserver.txt mapping file that was used in version6.1 is no longer needed.

Refresh Tivoli Enterprise Console informationA new CLI (Command Line Interface) tacmd refreshTECInfo commandenables you to have the Tivoli Enterprise Console Event Forwarderreprocess updated event definitions, EIF configuration, and custom eventmapping files without requiring a hub monitoring server recycle.

Situation event acknowledgementEvent acknowledgement has several new enhancements to facilitate quickacknowledgements, writing and reviewing notes, and attaching files to theacknowledgement.

Enterprise Status workspaceThe first indication of the acknowledgement enhancements is in the

Enterprise Status workspace, which adds a new view called MyAcknowledged Events, as well as a new Owner column in the situationevent console view that shows the ID of the user who acknowledged thesituation event.

Home workspaceInitially, Enterprise Status is the first workspace to be displayed when youlog on to the portal server. This is your home workspace. With the Assignas Home Workspace option, you can now establish another workspace,whether at this Navigator level or another and whether on this Navigatorview or another, as your home workspace. The Home tool opens thehome workspace.

Topology view

Topology view is a new type of query-based view that enables you tocreate views from relational data sources. Attributes from the query arerendered as objects and connected to related objects.

Another topology view that is available at the Enterprise level of theNavigator is the TMS (Tivoli Management Services infrastructure view,which visually expresses the relationships and linking of monitoring agentsand other components to the hub monitoring server.

Self-Monitoring Topology workspaceThe Enterprise Navigator item has a new Self-Monitoring Topology



28/425

predefined workspace. The purpose of this workspace is to introduce theself-monitoring capabilities that are available through the Tivoli EnterprisePortal.

Dynamic linkingA new link type has been added to the workspace link feature that enablesthe link author to identify the target workspace by the host identifier. The

dynamic link type adds more opportunities for workspace linking, such asto provide links to workspaces of other types of monitoring agents.

Navigator view icon in the status barWhen the Navigator view has been collapsed, you can now restore it oropen to another Navigator view by a click or right-click of in the Tivoli Enterprise Portal tatus bar.

Bar chart overlayA new overlay feature has been introduced that allows one or more relatedattributes to be plotted against the bar chart. This can highlight therelationship of related values, and is useful for visualizing trends fromhistorical data.

Plot chart overlay

In earlier releases the plot chart view was able to show data only from thefirst row of a data sampling. The plot chart properties have been enhancedfor plotting multiple-row attribute groups (or historical data from asingle-row attribute group) and multiple managed systems, and forcontrolling the refresh rate independent from the workspace as a whole.

The plot chart also has a new overlay feature that can be used to establisha secondary value axis.

Workflow editorYou can now launch the Situation editor from an activity in the Workfloweditor to edit the situation that it references.

Application window

The banner artwork in the browser client has changed, the Navigator tabshave been modernized, as have the view title bars, which also have twonew buttons for hiding or showing the view toolbar and for opening theProperties editor.

Creating a new viewAfter you click a view tool to create a new view, the mouse pointer adoptsthe view icon (instead of the hand icon) on Windows® systems. Andyou can now press Escape or click somewhere in the toolbar if you thendecide not to add the view.

Moving a viewYou can now drag a view by its title bar to a new location in theworkspace.

Searching in a viewThe view toolbar for the table, notepad, and browser views has a new

Find tool for quickly searching through text in the view.Cell function

The See if Null (no value) has been detected function can be used inthe Filters and Thresholds formula editors to locate attributes for which novalue has been retrieved.



29/425

operatorThe Value of expression function has a new comparison operator thatcan be used in situations and in table view Filters and Thresholds tohighlight specific text values.

Browser viewThe browser view now supports most types of web content, such as

JavaScript™

, Applets, and PDF files.

IBM Tivoli Monitoring family of products

The following information provides a brief overview of the applications of the IBMTivoli Monitoring family of products.

IBM Tivoli Monitoring products help you manage the performance and availabilityof distributed operating systems and applications. These products are based on aset of common service components, referred to collectively as Tivoli ManagementServices. Tivoli Management Services provides security, data transfer and storage,notification mechanisms, user interface presentation, and communication servicesin an agent-server-client architecture. These services are common to many product

suites such as IBM Tivoli OMEGAMON XE mainframe monitoring, IBM TivoliComposite Application Manager, and IBM Tivoli Performance Analytics for TivoliEnterprise Portal.

After you have installed and initially configured Tivoli Management Services andthe products that rely on them, consult this guide to apply further customization ina distributed environment. (Configuring the Tivoli Enterprise Monitoring Server on

z/OS® is provided in the guide of the same name.) It also has generaladministrative information for the managed systems that share these commonservices. Product-specific administrative information is given in the guides for theindividual products.

Tivoli Management Services componentsThe following Tivoli Management Services components provide the infrastructurefor your Tivoli Enterprise Monitoring Agents.

Client The IBM Tivoli Monitoring client, Tivoli Enterprise Portal is a Java-baseduser interface for viewing and monitoring your enterprise network.Depending on how it was installed, you can start Tivoli Enterprise Portalas a desktop application or through your browser as a Web application.

Presentation serverThe Tivoli Enterprise Portal client connects to the Tivoli Enterprise PortalServer. The Tivoli Enterprise Portal Server is a collection of softwareservices for the client that enables retrieval, manipulation and analysis of

data from the monitoring agents on your enterprise.Management server

The Tivoli Enterprise Portal Server connects to the main, or hub, TivoliEnterprise Monitoring Server. The monitoring server acts as a collectionand control point for alerts received from the enterprise monitoring agents,and collects performance and availability data from them. The hubmonitoring server correlates the monitoring data collected by monitoringagents and any remote monitoring servers and passes it to the portalserver for presentation in the portal console.

Agents



30/425

Tivoli Enterprise Monitoring Agents are installed on the systems orsubsystems whose applications and resources you want to monitor. Anagent collects monitoring data from the managed system and passes it to themonitoring server to which it is connected. The client gathers the currentvalues of the attributes and produces reports formatted into tables, charts,and relational table-based topology views. It can also test the valuesagainst a threshold and display an alert icon when that threshold is

exceeded or a value is matched. These tests are called situations.OS agentscan be installed outside the enterprise as Tivoli System Monitor Agents. Theydo not connect to nor have any reliance on the Tivoli EnterpriseMonitoring Server. They can run private situations, which are independentof the monitoring server, save data samples for attribute groups as privatehistory, and can send SNMP alerts to an Netcool/OMNIbus SNMP Probe.

Help serverThe IBM User Interface Help System built on Eclipse is installed with theportal serverportal serverand provides presentation and search features forthe integrated help system.

Data warehouseThe Tivoli Data Warehouse is an optional component for storing historicaldata collected from agents in your environment. The data warehouse islocated on a supported database (such as DB2®, Oracle, or Microsoft®®

SQL).

Event synchronizationThe event synchronization component is optional. It is configured to sendsituation event updates that were forwarded to a Tivoli Enterprise ConsoleEvent Server or a Tivoli Netcool/OMNIbus ObjectServer back to themonitoring server.

Tivoli Enterprise Portal client

Tivoli Enterprise Portal is the interface for your IBM Tivoli Monitoring products. In

the same way you use your browser's home page as a starting point for navigatingthe Internet, you use Tivoli Enterprise Portal to get a high level overview of yournetwork environment.

One section of the window displays the Navigator, a tree-like view of yourmonitored network, from the top level down to individual groupings of information collected by monitoring agents. The rest of the window is filled withviews pertinent to the chosen item in the Navigator tree. From the top level orfrom your home workspace, you can navigate to specific locations to check activityand investigate problems.

This workspace was customized for the select item in the tree. This workspace wasdesigned with a bar chart, two plot charts, and a table that displays a backgroundcolor for cell values that exceed a certain threshold. You can create and customizeadditional workspaces for every item in the tree.

The event indicators that display in the tree, or Navigator, are the results of tests,called situations, that run on your monitored systems. When the conditiondescribed in the situation is true, a colored icon overlays the affected items in thetree. Use the Situation editor to set up conditional alerts that monitor yourenvironment automatically. Use the Workflow editor to set up policies to automateyour environment.



31/425

Desktop, Browser, and Java Web Start clientsThe Tivoli Enterprise Portal client can be deployed in three ways, as described

briefly here and in more detail in the IBM Tivoli Monitoring Installation and SetupGuide:

DesktopThe desktop client requires that you load and run the installation softwareon each computer where the desktop client will be run. Users start TivoliEnterprise Portal the same way they do their other locally installedapplications. With the desktop client, you can also create multiple instancesfor connecting to different portal servers.

BrowserThe browser client installation software resides on the Tivoli EnterprisePortal Server. The client software is downloaded from there to yourcomputer the first time you log on to the portal server from your browser,

and thereafter only when there are software updates.You can start the browser client from any browser-enabled computer byentering the URL for the portal server. In this mode of operation, eachportal workspace has a URL, so you can save a workspace to yourFavorites list.

With the browser client you can launch from the Tivoli Enterprise Portal toother Tivoli Web-based and Web-enabled applications, and from thoseapplications into the portal without re-entering your log-on credentials.This single sign-on solution uses a central LDAP-based user registry toauthenticate sign-on credentials.

Java™ Web StartWith Java Web Start, like the browser client, the client software is accessedthrough a URL and downloaded from the portal server. Unlike the browserclient, which is always run inside the browser, the Web Start client is runas a desktop application. Whenever updates to the client software areavailable, they are downloaded from the portal server automatically.References to desktop client behavior in this guide also assumes the JavaWeb Start client unless otherwise stated. Single sign-on is an example: Aswell as the browser client, you can use single sign-on with the Web Startclient



32/425

Historical data collectionIn addition to the real-time reports offered by Tivoli Enterprise Portal workspaces,you can configure historical data collection to store the data being collected byyour monitoring agents for historical reports and situations. You can specify thefollowing:

v Attribute groups for historical data collection

v Data collection interval.v Data warehousing intervals if you choose to write data to the Tivoli Data

Warehouse

v How data samples are grouped for pruning from the Tivoli Data Warehouse

v Pruning schedule of warehoused data.

v Storage location for the short-term history files before they are sent to the datawarehouse. Data samples can be stored at the monitoring agent or on the TivoliEnterprise Monitoring Server.

To ensure that data samplings are saved to populate your predefined historicalworkspaces, you must first configure and start historical data collection. Real-timeworkspaces are available whether you start historical collection or not.

System administrator tasksA system administrator has the highest level of authority and can access all IBMTivoli Monitoring features.

This list represents the types of tasks a system administrator might perform:

v Establishes user IDs and user groups with the appropriate permissions for their jobs.

v Designs workspaces for Navigator items and makes these workspaces availableto users based on their established permissions.

v Defines queries that can be applied to table and chart views to specify the

attributes and attribute value ranges to retrieve from the monitoring serverv Writes definitions for launching applications and makes them available to users

based on their established permissions.

v Creates command line actions that can run at the specified managed systemfrom the portal client, and makes them available to users who have beengranted authority.

v Creates situations using the visual programming facilities

v Sets the severity of a situation for a particular Navigator item and what, if any,sound plays when the situation is true and an event opens

v Decides which situations apply to which managed systems, a process calleddistribution

v

Provides expert advice to display when certain situations evaluate truev Creates policy workflows, which are actions to take when situations evaluate

true

v Creates, installs, upgrades, distributes and configures agents on remote hostsfrom a central location

v Starts, stops, and recycles agent processes



33/425

Chapter 2. Preparing your Tivoli Enterprise Portalenvironment

Review these topics for additional configuration of the Tivoli Enterprise Portalclient environment.

Browser client

Users start the browser client by entering the URL for the integral HTTP server onthe Tivoli Enterprise Portal Server.

The advantages of the browser client are:

v Easy deployment. The browser client is installed the first time users log on tothe URL for the Tivoli Enterprise Portal integral HTTP server.

v Software upgrades are automatic. When users log on, their browser client ischecked against the one at the Tivoli Enterprise Portal Server; if a newer versionis detected, it is downloaded from the server.

v Global parameter settings are set for all users connected to the same TivoliEnterprise Portal Server.

v Workspaces have identifying URLs that can be referenced in Web pages andwhen launching from another Web-enabled application.

v Includes a banner that can be customized with your company logo and URL.

Java runtime environment (JRE) versionsThe Tivoli Enterprise Portal Server and client run Java-based software. When youinstall the portal server, a check is done for IBM Java 1.5 on your system and, if not found, is installed automatically. This check also takes place when you install

the desktop client, Java WebStart client, or log on from a browser with thisdifference: Sun Java 1.5.0_xx through 1.6.0_xx is also recognized as a valid JRE forthe client (but not 1.6.0_xx for Firefox on Linux).

If you have different versions of the Java Runtime Environment installed locally,they can coexist. Tivoli Enterprise Portal V6.2.1 and V6.2.2 require IBM Java V1.5or Sun Java V1.5. The desktop client must be at the same version as the portalserver it connects to. This is also true for the browser client, but Java versioning iscontrolled at the portal server and upgraded automatically when you connect to anewer portal server.

Running IBM Tivoli Monitoring V6.1 agents and IBM Tivoli Monitoring V6.2agents on the same computer requires Java 1.4.2 and 1.5 on that computer.

Allocating additional memory for the appletWhen the browser client connects to the Tivoli Enterprise Portal Server, itdownloads a Java applet. Before starting the browser client, allocate enoughmemory for the applet to avoid out-of-memory problems.

Before you begin

Specify the runtime parameters for the Java applet using the control panel for theappropriate JRE. Use the same user ID from where the browser client will be

© Copyright IBM Corp. 2005, 2010 19


34/425

launched to open the control panel and specify these parameters. Otherwise, theuser-level deployment.properties file for the correct user ID will not be updated.

About this task

Take these steps to increase the memory allocated for the Tivoli Enterprise Portal Java applet.

Procedure

1. Open the Java control panel:

v Launch the IBM Control Panel for Java or the Java Control Panel.

v Find the Java ControlPanel executable under your jre_install_dir andlaunch it. Example: /opt/IBM/ibm-java2-i386-50/jre/bin/ControlPanel.

2. Click the Java tab.

3. In the Java Applet Runtime Settings area, click View.

4. If you have multiple Java versions, verify that you have the correct controlpanel open by reading the Location column to confirm the Java Runtime andthat the JRE is in the correct path. For example, C:\Program

Files\IBM\Java50\jre\bin for IBM Java on Windows.5. Click in the Java Runtime Parameters field and set the parameters:

-Xms128m -Xmx256m -Xverify:none

The -Xms128m specifies the starting size of the Java heap (128 MB) and-Xmx256m specifies the maximum size. The -Xverify:none parameter disables

Java class verification, which can improve the startup time.If you are using the IBM JRE on Linux, add the –Djava.protocol.handler.pkgsoption:

-Xms128m -Xmx256m -Xverify:none-Djava.protocol.handler.pkgs=sun.plugin.net.protocol

This option is required for the IBM JRE on Linux due to a problem with theplug-in not caching jar files. If the parameter is left off, the Tivoli EnterprisePortal applet jar files will not be cached, making subsequent start ups of theapplet slow.

6. Confirm that the Temporary Files settings are set to Unlimited:

a. Click the General tab.

b. Click Settings.

c. Select the maximum amount of disk space for storing temporary files: 1000MB.

7. Clear the browser cache:

a. In the General tab, click Delete Files.

b. In the window that opens, select Downloaded Applets .

What to do next

You can now start the browser client and connect to the portal server.

Note: The Sun JRE does not always support the same maximum heap values asthe IBM JRE. The true maximum is calculated based on the resources available onthe particular computer being configured, and the algorithm that is involved isdifferent between the two JREs. The symptom of a memory problem is that theapplet fails to load in the browser and you receive an error message. To resolve



35/425

this problem, reduce the value of the maximum heap setting in the Java Controlpanel in 32m or 64m increments until the error g

itm622fp2 admin

Documents