IBM Tivoli Monitoring for Web Infrastructure: WebSphere...

IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server

User’s GuideVersion 5.1.0

SC23-4705-00

��

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

First Edition (September 2002)

This edition applies to the 5.1.0 version of IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2002. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . ixWho should read this guide . . . . . . . . . ixPublications . . . . . . . . . . . . . . ix

IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server Library . . . . ixPrerequisite publications . . . . . . . . . xAccessing softcopy publications . . . . . . . xTivoli Information Center . . . . . . . . . xOrdering publications . . . . . . . . . . xProviding feedback about publications . . . . xi

Accessibility . . . . . . . . . . . . . . xiContacting Customer Support . . . . . . . . xiConventions used in this book . . . . . . . . xi

Typeface conventions . . . . . . . . . . xi

Chapter 1. Overview of IBM TivoliMonitoring for Web Infrastructure,Version 5.1.0: WebSphere ApplicationServer . . . . . . . . . . . . . . . 1Availability management . . . . . . . . . . 1Performance management . . . . . . . . . . 2Operations management . . . . . . . . . . 2Overview of IBM Tivoli Monitoring . . . . . . 3

Understanding IBM Tivoli Monitoring terminology 3Authorization roles . . . . . . . . . . . . 9Managed resources and endpoints . . . . . . . 10User interface options . . . . . . . . . . . 10

Chapter 2. Setting up IBM TivoliMonitoring for Web Infrastructure:WebSphere Application Server . . . . 11Guidelines for setting up the product . . . . . . 11Setting authorization roles . . . . . . . . . 12Configuring endpoints. . . . . . . . . . . 13

Configure client side WebSphere security . . . 13Enabling IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server tocommunicate with IBM WebSphere ApplicationServer on a non-default port. . . . . . . . 14Enabling performance monitoring . . . . . . 15

Creating IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server objects 16Setting up the IBM Tivoli Monitoring environment 2121Distributing profiles . . . . . . . . . . . 21

Distributing profiles from the Tivoli desktop . . 21Distributing profiles using MDist2 . . . . . . 23

Chapter 3. Setting up the TivoliEnterprise Console for eventcorrelation . . . . . . . . . . . . . 27Overview of the Tivoli Enterprise Console . . . . 27Configuring the Tivoli Enterprise Console eventserver . . . . . . . . . . . . . . . . 28Configuring the Tivoli Enterprise Console adapter 31Filtering events . . . . . . . . . . . . . 33

Chapter 4. Integrating with TivoliBusiness Systems Manager . . . . . 35Understanding Tivoli Business Systems Manager . . 35Prerequisites . . . . . . . . . . . . . . 36Integrating IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server withTivoli Business Systems Manager . . . . . . . 36Configuring the Tivoli Enterprise Console eventserver to work with Tivoli Business SystemsManager . . . . . . . . . . . . . . . 37Discovering resources for Tivoli Business SystemsManager . . . . . . . . . . . . . . . 38Working with Tivoli Business Systems Manager . . 39Uninstalling IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Serverintegration from Tivoli Business Systems Manager . 40

Chapter 5. Working with resourcemodels. . . . . . . . . . . . . . . 41Resource model library . . . . . . . . . . 41Modifying indications . . . . . . . . . . . 42Specifying tasks for an indication . . . . . . . 44Sending a notice to administrators when an eventoccurs . . . . . . . . . . . . . . . . 45Creating scheduling rules. . . . . . . . . . 46Modifying data logging settings . . . . . . . 48Managing profiles and resource models at endpoints 50Managing IBM Tivoli Monitoring gateways. . . . 51Determining which resource models are running onendpoints . . . . . . . . . . . . . . . 52Viewing resource model results with the IBM TivoliWeb Health Console . . . . . . . . . . . 53

Understanding resource health . . . . . . . 53Connecting the IBM Tivoli Monitoring WebHealth Console . . . . . . . . . . . . 54

Chapter 6. Working with IBM TivoliMonitoring for Web Infrastructure:WebSphere Application Serverresources . . . . . . . . . . . . . 55Checking the status of an IBM WebSphereadministration or application server . . . . . . 55Starting or stopping a server . . . . . . . . 57Listing application servers . . . . . . . . . 58

iii

Viewing endpoint or callback log files . . . . . 60

Chapter 7. Working with tasks and jobs 63Running a task . . . . . . . . . . . . . 63Customizing a task . . . . . . . . . . . . 66Creating a job . . . . . . . . . . . . . 67Running a job . . . . . . . . . . . . . 70Scheduling a job . . . . . . . . . . . . . 71

Chapter 8. Enabling Tivoli EnterpriseData Warehouse. . . . . . . . . . . 75Overview . . . . . . . . . . . . . . . 75

Control server . . . . . . . . . . . . 75Central data warehouse . . . . . . . . . 76Data marts . . . . . . . . . . . . . 76Report interface . . . . . . . . . . . . 76

Working with users and user groups . . . . . . 77About users and user groups . . . . . . . 77The Tivoli Enterprise Data Warehouse roles. . . 77

Creating an IBM Console user . . . . . . . . 78Assigning roles to a user . . . . . . . . . . 78Creating a user group . . . . . . . . . . . 79Assigning users to a user group . . . . . . . 79Assigning user groups to a data mart. . . . . . 80Managing Tivoli Enterprise Data Warehouse reports 80

IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server star schemas, datamarts, and reports . . . . . . . . . . . 81Running reports . . . . . . . . . . . . 84Scheduling reports to run automatically . . . . 85Modifying default settings for reports . . . . 86Creating reports . . . . . . . . . . . . 87

Appendix A. Task authorization rolesquick reference . . . . . . . . . . . 89

Appendix B. Task quick reference . . . 91

Appendix C. Setting up IBM TivoliMonitoring . . . . . . . . . . . . . 93Creating profile managers and profiles . . . . . 94

Subscribing resources to profile managers . . . . 96Adding default resource models to profiles . . . . 96Adding customized resource models to profiles . . 97Rerunning failed profile distributions . . . . . . 98

Appendix D. Creating customresource models . . . . . . . . . . 101Creating custom resource models using the IBMTivoli Monitoring Workbench . . . . . . . . 101Enabling JVMPI data reporting . . . . . . . 103

Appendix E. Event classes and rules 105Event classes . . . . . . . . . . . . . 105Rules for resource models . . . . . . . . . 105Rules for events . . . . . . . . . . . . 105

Appendix F. Problem determination 107Possible problems and workarounds . . . . . 107

General problem determination . . . . . . 107Tivoli Enterprise Console problemdetermination . . . . . . . . . . . . 108Tivoli Enterprise Data Warehouse problemdetermination . . . . . . . . . . . . 109Tasks problem determination . . . . . . . 109Resource models problem determination . . . 114

Debugging information . . . . . . . . . . 118Log file information . . . . . . . . . . 118AutoTrace information . . . . . . . . . 119

Appendix G. Accessibility . . . . . . 121Using assistive technologies . . . . . . . . 121Magnifying what is displayed on the screen . . . 121Documentation in accessible formats . . . . . 121Using alternative text. . . . . . . . . . . 121

Appendix H. Notices . . . . . . . . 123Trademarks . . . . . . . . . . . . . . 124

Index . . . . . . . . . . . . . . . 127

iv IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

Figures

1. The Discover_WebSphere_Resources taskexecution window . . . . . . . . . . 20

2. The Configure Event Server task window 303. The Configure WebSphere TEC Adapter task

window. . . . . . . . . . . . . . 324. The Operation menu on a IBM Tivoli

Monitoring for Web Infrastructure: WebSphereApplication Server object . . . . . . . . 56

5. The output window for the Check Statusaction . . . . . . . . . . . . . . 57

6. List of application servers associated with thespecified IBM WebSphere administrationserver. . . . . . . . . . . . . . . 59

7. The list of endpoint logs associated with theIBM WebSphere administration server . . . 61

8. Example of a task argument window . . . . 66

v

vi IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

Tables

1. Counting occurrences . . . . . . . . . 62. Guidelines for setting up the product . . . . 113. Guidelines to configure endpoints . . . . . 134. Minimum performance monitoring levels for

the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Serverresource models . . . . . . . . . . . 16

5. Integrating with Tivoli Business SystemManager . . . . . . . . . . . . . 35

6. IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server resource models 41

7. Health Determination Example . . . . . . 538. Working with tasks and jobs . . . . . . . 639. Guidelines for working with Tivoli Enterprise

Data Warehouse users and user groups . . . 7710. Guidelines for working with Tivoli Enterprise

Data Warehouse reports . . . . . . . . 8111. Default time filter names and values . . . . 86

12. IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server taskauthorization roles . . . . . . . . . . 89

13. IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server task libraries. . 91

14. Monitoring resources and applicationsguidelines . . . . . . . . . . . . . 93

15. Guidelines for creating custom resourcemodels. . . . . . . . . . . . . . 101

16. General problems and solutions . . . . . 10717. Tivoli Enterprise Console problems and

solutions . . . . . . . . . . . . . 10818. Tivoli Enterprise Data Warehouse problems

and solutions . . . . . . . . . . . 10919. Task problems and solutions . . . . . . 11020. Discover_WebSphere_Resources task

problems and solutions . . . . . . . . 11221. Resource model problems and solutions 114

vii

viii IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

About this guide

The IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebSphere ApplicationServer User’s Guide provides information about setting up and using IBM® Tivoli®

Monitoring for Web Infrastructure: WebSphere® Application Server to manage yourIBM WebSphere Application Server resources.

Who should read this guideThis guide is for administrators and system programmers who use IBM TivoliMonitoring for Web Infrastructure to manage IBM WebSphere Application Serverresources.

Readers should be familiar with the following:v The operating systems that the Web servers run on, such as UNIX®, Microsoft®

Windows® 2000, Windows NT®, and Linuxv Web server administrationv The Tivoli management environment

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server library and any other related documents. It alsodescribes how to access Tivoli publications online, how to order Tivolipublications, and how to submit comments on Tivoli publications.

IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server Library

The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverlibrary contains the following publications:v IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guide,

GC23-4719Provides information about installing and setting up IBM Tivoli Monitoring forWeb Infrastructure.

v IBM Tivoli Monitoring for Web Infrastructure Release Notes, GI10-5798Provides a product overview, system requirements, and additional installationinformation.

v IBM Tivoli Monitoring for Web Infrastructure Reference Guide, GC23-4720Provides detailed programming information about the IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server resource models, tasks,commands, and error messages.

v IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application ServerWarehouse Enablement Pack Implementation Guide, SC09-7783Provides information about installing and using the IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server Warehouse Enablement Pack.This document is located on the IBM Tivoli Monitoring for Web Infrastructure,Version 5.1.0: Component Software CD in the \tedw_apps_etl\izy\pkg\v110\docdirectory.

ix

v IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application ServerWorkaround and Limitations Supplement, GI11-0928Provides information about problems that might occur, as well as customerissues that have been resolved.

Prerequisite publicationsTo use the information in this book effectively, you must have some prerequisiteknowledge of IBM Tivoli Monitoring, which you can get from the following books:v IBM Tivoli Monitoring User’s Guide, SC23-4567

Provides an overview of IBM Tivoli Monitoring, especially of resource models. Italso describes how to use the user interface.

v IBM Tivoli Monitoring Workbench User’s Guide, SC23-5678Describes using the IBM Tivoli Monitoring Workbench to create and customizeresource models.

Accessing softcopy publicationsThe publications for this product are available in PDF and HTML formats throughthe following media:

IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: Documentation CD,LK3T-8515–00

The Documentation CD contains all of the English language publications for thisproduct, except for the Web-only Limitations and Workarounds supplements. Toaccess the publications, use a Web browser to open the start.html file, which islocated in the root directory of the CD.

Note: The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application ServerWarehouse Enablement Pack Implementation Guide is located on the productCD, not the documentation CD.

The NLS (national language support) Documentation CD contains both Englishand non-English language publications for this product, except for the Web-onlyLimitations and Workarounds Supplements. To access the publications, use a Webbrowser to open the start.html file, which is located in the root directory of the CD.

Tivoli Information CenterIBM posts all publications for this product, as they become available and wheneverthey are updated, to the Tivoli Information Center Web site. The Tivoli InformationCenter is located at the following Web address:

Click the IBM Tivoli Monitoring for Web Infrastructure link to access the productlibrary.

Ordering publicationsYou can order hardcopy publications online from the IBM Publications Center Website:

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

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

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

x IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

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

v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,complete the customer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface. For more information about the accessibility features of this product, seeAppendix G, “Accessibility” on page 121.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact Customer Support.See the Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv What information you should gather before contacting support

Conventions used in this bookThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface conventionsThe following typeface conventions are used in this book:

Bold Lowercase and mixed-case commands, command options, andflags that appear within text appear like this, in bold type.

Graphical user interface elements and names of keys also appearlike this, in bold type.

Italic Variables, values you must provide, new terms, and words andphrases that are emphasized appear like this, in italic type.

Monospace Commands, command options, and flags that appear on a separateline, code examples, output, and message text appear like this, inmonospace type.

About this guide xi

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

http://www.tivoli.com/support/handbook/

Text strings you must type, when they appear within text, namesof Java™ methods and classes, and HTML and XML tags alsoappear like this, in monospace type.

xii IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

Chapter 1. Overview of IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebSphere Application Server

IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebSphereApplication Server provides a centralized system management tool for IBMWebSphere Application Server Advanced Edition. The IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server enables you to manage IBMWebSphere administration and application servers.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides the ability to manage and monitor IBM WebSphere Application Serverresources by providing extensions to Tivoli Management Framework, IBM TivoliMonitoring, Tivoli Enterprise Console, Tivoli Business Systems Manager, and TivoliEnterprise Data Warehouse.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server usesIBM Tivoli Monitoring resource models to manage distributed IBM WebSphereApplication Server resources effectively.

Use IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverto perform the following tasks:v Monitor and interpret performance and availability data for all IBM WebSphere

Application Server resources across distributed environmentsv Manage performance and availability of IBM WebSphere Application Server

resourcesv Capture and manage historical data that is stored in a central data warehousev Forward IBM WebSphere Application Server events to the Tivoli Enterprise

Consolev Manage event correlation and automation using the Tivoli Business Systems

Manager

Note: Tivoli Enterprise Console, Tivoli Business Systems Manager, and AdapterConfiguration Facility products must be installed for you to take advantageof event management functions. This guide addresses event managementtopics with the assumption that Tivoli Enterprise Console, Tivoli BusinessSystems Manager, and Adapter Configuration Facility products are installedwhere required.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides the following features:v Availability managementv Performance managementv Operations management

Availability managementIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides resource models that periodically check the status of your IBM WebSphereApplication Server components. For example, the resource models monitor theadministration and application servers for the following states:

1

v Upv Down

You can configure the resource models to customize the monitoring cycle and tochange the triggering thresholds.

To ensure that you are managing all available resources, IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server provides theDiscover_WebSphere_Resources task that finds IBM WebSphere administrationservers and application servers. When the Discover_WebSphere_Resources tasklocates new IBM WebSphere Application Server resources, it adds them to yourTivoli configuration.

IBM WebSphere Application Server resources report operational changes in locallogs. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides event adapter functions to extract IBM WebSphere Application Serverevents from these logs. You can view these events on the Tivoli Enterprise Consoleevent console, and you can write rules to automatically take action in response tothese events. You can also forward events from Tivoli Enterprise Console to TivoliBusiness Systems Manager.

Performance managementThe IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverresource models enable you to measure and report the performance of variouscomponents running on your IBM WebSphere Application Server resources, suchas Enterprise JavaBean (EJB) performance or database connection poolperformance, both of which affect the performance of Web applications running onyour servers.

Operations managementIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server tasksenable you to manage your IBM WebSphere Application Server resources on adaily basis. You can use these tasks to do the following:v Start and stop your IBM WebSphere administration and application servers, as

well as the Tivoli Enterprise Console event adapterv Check the status and retrieve information about your IBM WebSphere

Application Server resourcesv Retrieve and delete IBM Tivoli Monitoring for Web Infrastructure: WebSphere

Application Server trace log files

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server eventrules manage the information presented on your event console. These rules removeduplicate and harmless events and correlate events to close events that are nolonger relevant. IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server event reporting functions support standard Tivoli eventfiltering, which you can use to reduce the number of events sent to your eventsserver. In addition to forwarding events to Tivoli Enterprise Console, IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server can also forwardevents to Tivoli Business Systems Manager.

2 IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server: User’s Guide

Overview of IBM Tivoli MonitoringIBM Tivoli Monitoring 5.1.1 enables you to deploy preconfigured best practicesresource models as well as standard and customized resource models to automatethe monitoring of essential resources. In this context, a resource is anything thataffects the operation of a computer system and includes physical and logical disks,CPUs, memory, printers, the processes running, and the services, such as LanMan,Windows event log, UNIX syslogd (logging system daemon) and TCP/IP. Thisenables you to detect bottlenecks and other potential problems and defineautomatic recovery from critical situations. This ability frees system administratorsfrom manually scanning extensive performance data. The monitoring softwareintegrates with other Tivoli Availability solutions, including Tivoli Business SystemManager and Tivoli Enterprise Console.

A resource model captures and returns information, such as database status or serveravailability, about a resource or software application in the Tivoli managementenvironment. To use a resource model, you must define and distribute it to anendpoint.

Tivoli provides tools for organizing system resources on the Tivoli desktop. Serversare subscribed to profile managers. These subscriptions provide the channel throughwhich resource models are distributed to servers. A profile manager also containsprofiles, which are containers for application-specific information about a particulartype of resource. Each profile contains one or more resource models. You cansubscribe resources to a profile manager. You can distribute individual profileswithin the profile manager to subscribers of the profile manager. You can groupprofile managers in a way that meets your needs. Profile managers can reflectfunctional grouping of resources, functional grouping of resource models, or anygrouping at all. Likewise, a profile can contain any combination of resourcemodels. However, you must segregate profiles according to resources: Web serversneed Web server resource models, and database servers need database serverresource models.

You can define each resource model to include information such as how often tocheck resource status and what to do when certain conditions are met. Someresource models provide predefined settings and response actions, which you canadjust. Other resource models require you to define all the settings. See the IBMTivoli Monitoring for Web Infrastructure Reference Guide for a description ofindividual settings.

Before running a resource model, you must subscribe the server resource to theprofile manager that contains the profile in which the resource model is stored.You can then distribute the profile to the resource. By default, resource models areset up to become active when you distribute them to subscribers. You can activateand deactivate resource models after they are distributed.

Understanding IBM Tivoli Monitoring terminologyThis section describes the main concepts required for understanding how to usethe IBM Tivoli Monitoring product.

Note: The definitions below apply to resource models in general. They are notspecific to the resource models provided by IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server. For information about theconfiguration of the IBM Tivoli Monitoring for Web Infrastructure:

Chapter 1. Overview of IBM Tivoli Monitoring for Web Infrastructure, Version 5.1.0: WebSphere Application Server 3

WebSphere Application Server resource models, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

ActionsYou can associate one or more recovery actions with a specific event. Theseactions are automatically triggered when the event occurs and, typically,are used for restoring satisfactory system service level. Each time an eventoccurs, the system provides a notification of the event, triggers a recoveryaction to restore satisfactory conditions and, if the action is successful,provides a notification that the action was performed. Actions areassociated with the execution of a CIM method or the execution of aprogram. Associate actions with indications when modifying an existingresource model using this software, or when creating a new resourcemodel with the IBM Tivoli Monitoring Workbench.

AttributesAttributes can be string or numeric values. When creating a new resourcemodel with the IBM Tivoli Monitoring Workbench, you can qualify anevent by specifying relevant attributes according to the information youwant the resource model to monitor. For example, an event might indicateinsufficient disk space. When you specify attributes, such as disk name, oravailable disk space, the resource model can generate a more preciseindication of the problem. For each resource model, some of the attributesare designated as keys.

Cycles When a resource model is run at an endpoint, it gathers data at regularintervals, called cycles; the duration of a cycle is the cycle time, which isexpressed in seconds. A resource model with a cycle time of 60 secondsgathers data every 60 seconds. Each of the supplied resource models has adefault cycle time, which you can modify when you define the resourcemodel. At each cycle, the resource model collects data, analyzes it,generates the events and triggers specified actions. The data collected are asnapshot of the status of the resources specified in the resource model.

Gathering Historical Data componentThe Gathering Historical Data component enables IBM Tivoli Monitoringto use Tivoli Decision Support for Server Performance Prediction andTivoli Enterprise Data Warehouse.

The Gathering Historical Data component uses data collected by specificIBM Tivoli Monitoring resource models to populate a database on theTivoli server where the Gathering Historical Data component is installed.The collected data is aggregated every 24 hours and added to the IBMTivoli Monitoring database, from where it can be used in analyses thathelp plan network growth using key system metrics.

For more information about Tivoli Enterprise Data Warehouse, see thefollowing publications:v Tivoli Distributed Monitoring Warehouse Enablement Pack: Implementation

Guide

v Enabling an Application for Tivoli Enterprise Data Warehouse

Heartbeat functionIBM Tivoli Monitoring operates a heartbeat function, which monitors thebasic system status at endpoints attached to the gateway at which it isenabled. Events can be sent to the Tivoli Business Systems Manager(provided that the Tivoli Business Systems Manager Adapter component isinstalled at the gateway), the Tivoli Enterprise Console®, and the IBM TivoliMonitoring Notice Group.


Indications and EventsAn indication is generated when the state of a given resource meetsdefined criteria. By itself, an indication does not trigger any specific action.When indications are aggregated, the resource model generates an event.When you define an event, you must specify under what conditions acertain number of indications are aggregated into an event. You alsospecify whether these indications must be consecutive, or whether thesequence may be interrupted by one or more monitoring cycles that do notregister any indication. The cycles during which no indication is generatedare called holes. An event can notify that there is a problem in the resourcestate, trigger an action and, if enabled, send a notification to the TivoliEnterprise Console server or to Tivoli Business Systems Manager.

IndicationsEach resource model generates an indication when thresholds youdefine are exceeded in a given cycle. A single occurrence of anindication does not always represent a problem, however thepersistence of indications might. The resource model measures thepersistence of the indications and aggregates them according toyour specifications, or how you define settings for occurrences andholes. If the persistence of an indication meets the specifiednumber of occurrences, the resource model generates and event.Indications can be generated in any one of the followingcircumstances:v When a single threshold is exceededv When a combination of two or more thresholds are exceededv When a combination of other factors change

Occurrences and holesOccurrences and holes record whether or not an indication occursduring a cycle for a specific resource model. An occurrence is acycle during which at least one threshold is exceeded and anindication occurs for a given resource model. A hole is a cycleduring which an indication does not occur for a given resourcemodel. A hole means none of the conditions that generate anindication were met.

EventsAn event is an aggregation of a defined number of consecutiveoccurrences during which there can be a defined number ofconsecutive holes. An event is generated only when theaggregation algorithm detects the number consecutive occurrencesdefined in the indication with which the event is associated. Anevent verifies the persistence of an indication by eliminatingunrepresentative peaks and troughs over a period of cycles. Anindication that persists over several cycles is more likely to be aproblem. Thus, an event defines that a number of occurrences overa period of cycles has occurred.

When you define an event, you can specify how many consecutiveholes in the sequence of consecutive occurrences are permitted.Specifying how many consecutive holes are permitted during theaccumulation of the consecutive occurrences enables you tocontinue the counting of consecutive occurrences if one or twocycles fall below the threshold.


The following examples illustrate what happens if you define anevent as three occurrences and two holes. 1 represents anoccurrence and 0 represents a hole.v 0 1 0 1 0 0 1

Because fewer than three holes exist between each of the threeoccurrences, the three occurrences are consecutive. Therefore, thesequence represents an event.

v 1 0 0 1 0 0 1If each occurrence is followed by the maximum specified holeswithin seven cycles, an event is triggered.

v 1 0 0 1 0 0 0If the algorithm counts two consecutive occurrences and thenobserves three consecutive holes (more holes than that allowedin the definition of an event for this example) it sets the count ofoccurrences to zero. See Table 1.

Table 1. Counting occurrences

Sequence Count of occurrences

1 0 0 1

1 0 0 1 2

1 0 0 1 0 2

1 0 0 1 0 0 2

1 0 0 1 0 0 0 0

While defining an event, you can also indicate if you want thesystem to notify the Tivoli Enterprise Console server, or the TivoliBusiness Systems Manager, that an event was generated. The TivoliMonitoring operator can change these selections later, when theresource model is included in a Tivoli Monitoring profile. You canalso define the degree of severity and the message that will specifythe notification of the event.

Clearing EventsA clearing event is a resource model function that, ifenabled, allows IBM Tivoli Monitoring to close an eventwhen the circumstances that caused the event are nolonger present. Clearing events can be processed by theTivoli Enterprise Console server and by Tivoli BusinessSystems Manager. Clearing events have a severity ofharmless, regardless of the severity of the original event, buthave the same event ID as the original event.

For example, a service stops and the Tivoli EnterpriseConsole server receives an event notifying it of thisproblem. Until the service restarts, the problem is stillpresent on the endpoint, but IBM Tivoli Monitoring doesnot send any further event notifications to the TivoliEnterprise Console server. If the Clearing Event function isenabled, as soon as the service restarts, Tivoli EnterpriseConsole server, thereby closing the original event. TheClearing Event itself does not normally appear on theserver, because its only function is to clear the originalerror event.


Note: Correlated events cannot be cleared.

Monitoring of events and indicationsEvents can be sent to the Tivoli Enterprise Console server, the WebHealth Console, and Tivoli Business Systems Manager.

Tivoli Enterprise Console serverEvents can be viewed by a Tivoli Enterprise Console serverand contain a set of properties that can help to identifyproblems.

Clearing events can also be processed by the TivoliEnterprise Console server. If the default procedure is usedto enable the monitoring of events, the Tivoli EnterpriseConsole server uses the clearing event to close theassociated error event. However, if you choose not toinstall the clearing events rule incorporated in theabove-mentioned default procedure, the clearing event isdisplayed as a separate entity with the same ID as theoriginal error event.

Web Health ConsoleThe Web Health Console, an optional part of IBM TivoliMonitoring, displays the health of each resource model fora selected endpoint as a numeric value between 100(perfect health) and zero (with zero meaning that an eventhas been triggered). Intermediate values show thepercentage of occurrences currently registered with respectto the total number of occurrences needed to trigger anevent.

Tivoli Business Systems ManagerEvents and clearing events can also be sent to the TivoliBusiness Systems Manager, provided that the TivoliBusiness Systems Manager Adapter component has beeninstalled on the gateways of the endpoints that are to bemonitored. A full description of Tivoli Business SystemsManager can be found in the Tivoli Business SystemsManager documentation.

Clearing events can also be processed by the TivoliBusiness Systems Manager, which uses the clearing eventto close the associated error event.

LoggingFor any endpoint, you can log the data collected by a resource model in alocal database. Then you can view it through the History View of the WebHealth Console. You can choose to store raw or aggregated data. You canalso log data to the Tivoli Enterprise Data Warehouse.

ParametersWhile thresholds can be only numeric values, parameters can be lists ofnumbers or strings. Using parameters enables you to customize yourresource model. You can define different parameters, as required. For eachparameter you can specify a value, which can, for example, represent theinstances you want to monitor, or a limit you do not want your resource toexceed, depending on how you use this setting in your script. The lists willthen be displayed in the IBM Tivoli Monitoring dialogs, and depending onthe type of list you select in the IBM Tivoli Monitoring Workbench, thelists will appear in different forms on IBM Tivoli Monitoring. Within the


IBM Tivoli Monitoring Workbench, you can define default values and thenlet the operator customize the settings in IBM Tivoli Monitoring. You canchoose one among the following kinds of lists when you specify theparameters:v Boolean Listv Choice Listv String Listv Numeric List

Some resource models have one or more parameters.

ProfilesIBM Tivoli Monitoring is a profile-based application that runs in a Tivolienvironment. Different profiles can be defined containing differentselections of resource models. All aspects of existing profiles can bemodified, including the addition, deletion and customization of resourcemodels. You can distribute multiple profiles to each endpoint.

Recovery ActionsFor any event, recovery actions can be run automatically, such as built-inactions (for Windows) or Tivoli Framework tasks. The actions can takepositive steps to remedy the situation, or can ensure that information aboutthe event is distributed to the appropriate authorities or entities.

Built-In ActionsCertain events can have one or more built-in actions predefined forthem. An action can be either the execution of a common informationmodel (CIM) class method or the execution of a program. Both typeof actions can be implemented only through the Workbench. Forexample, an event that detects the failure of a service could havethe restart of that service as its built-in action. Thus, without anyhuman intervention, IBM Tivoli Monitoring detects the failure of aservice and automatically restarts it. Built-in actions are defined bydefault as part of an event, but can be removed. They have thesame event ID as the event that they are designed to correct.

Note: The indications for the IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebSphere Application Serverresource models do not have built-in actions. You can addbuilt-in actions to a custom resource model.

Tivoli Framework tasksFor each event you can select one or more Tivoli Framework tasksto be performed when the event is triggered. The tasks that aretriggered by a IBM Tivoli Monitoring event can access the eventname and event thresholds by accessing the environment variables.

Resource modelsIBM Tivoli Monitoring products provide predefined resource models thataccess specific performance data from the system at runtime. The resourcemodels process the data they collect using an algorithm that determineswhether or not the system is performing to expectations. You can eitheruse a resource model’s default values to collect performance data orcustomize the resource models to match specific requirements in yourenvironment. Distributing resource models using default values enablesyou begin monitoring immediately to obtain useful data concerning your


enterprise. When you become more familiar with the monitoring processand feedback, you may choose to customize the resource modelinformation.

SchedulingIBM Tivoli Monitoring contains a scheduling feature that enables you todetermine a period within which monitoring takes place and specificscheduling rules.

The monitoring period is determined by defining a from and a to date.

The scheduling rules enable you to define time periods on specific daysduring which monitoring takes place. Any number of rules can be defined,allowing you to set up a complex pattern of resource monitoring for aprofile, covering the time periods important to you.

The scheduled times are always interpreted as local times, enabling you toset up a single rule that monitors the same local time period in differenttime zones. For example, if your region covers several time zones, but youwant to monitor morning activities in each time zone, a single ruledefining the monitoring period of between 08:00 and 13:00 is interpretedlocally in each of the time zones, so that you monitor the same relativeperiod.

You should note also that all times of events or activities reported fromendpoints or gateways are logged in the local time of the system fromwhere they originated.

ThresholdsEach resource model defines one or more thresholds. Each threshold has adefault numeric value that you can change when you define the profile.The following are examples of how a resource model can use thresholds:v A threshold value might represent a limit that, if not met, indicates an

unsatisfactory resource state. For example, if you want the system tonotify you when disk space drops under 70%, set the threshold value to70 to generate an indication each time your disk space is less than 70%.

v Some threshold values control the scope of what the resource modelmonitors.

You can add a description for each threshold in the Threshold dialogexplaining what each value measures and how it is used within themonitoring algorithm.

Authorization rolesIBM WebSphere Application Server administrators are known in the Tivolienvironment as Tivoli administrators. Administrators are system or Tivoliadministrators who have the authorization to manage IBM WebSphere ApplicationServer servers. After the product is installed, you can assign authorization roles toadministrators that define the operations they can perform. Each administrator orgroup of administrators is represented by an icon on the Tivoli desktop.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server fullyintegrates into Tivoli security. To perform administration functions, administratorsmust have authorization roles for both IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server and the Tivoli managementenvironment.


IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server usesthe following authorization roles:v websphereappsvr_super

v websphereappsvr_admin

v websphereappsvr_user

Managed resources and endpointsA managed resource is a system or network resource that you manage with TivoliManagement Framework. A managed resource is a specific resource that has adefault policy defined in a policy region. An endpoint is a managed resource thatis the target for distribution of a profile or the resource on which a task or job is tobe run. IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer uses endpoint objects to represent IBM WebSphere administration andapplication servers. To manage IBM WebSphere Application Server resources, theTivoli endpoint must be installed on each IBM WebSphere Application Servernode.

Note: In the Tivoli environment, the term node is used to refer to any managedresource with Tivoli Management Framework installed. In the WebSphereenvironment, the term node is used to refer to the IBM WebSphereadministration server. In this document, unless specifically indicated, theTivoli environment definition of node is used.

User interface optionsYou can use the following user interfaces when working with IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server:v The Tivoli desktop, which is the traditional Tivoli graphical user interface (GUI)v The command line interface (CLI)v IBM Tivoli Monitoring Web Health Console to work with resource modelsv Tivoli Enterprise Console to work with event managementv Tivoli Business Systems Manager to work with event management and to run

some tasksv Tivoli Enterprise Data Warehouse to gather data about your resources


Chapter 2. Setting up IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server

This chapter describes how to configure IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server.

Guidelines for setting up the productThe following table describes the steps required to set up IBM Tivoli Monitoringfor Web Infrastructure: WebSphere Application Server, as well as links to where tofind more information.

Table 2. Guidelines for setting up the product

Goal Where to find information

Assign the IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer authorization to one or more Tivoliadministrators

“Setting authorization roles” on page 12

Configure the endpoints:

1. If WebSphere security is enabled,configure client side security.

2. If you are using a non-default port forWebSphere, enable the endpoint to alsouse the non-default port.

3. Enable performance monitoring.

“Configuring endpoints” on page 13

Create IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer objects to represent your IBMWebSphere Application Server components

“Creating IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer objects” on page 16

Set up the IBM Tivoli Monitoringenvironment so that you can run commands

“Setting up the IBM Tivoli Monitoringenvironment” on page 21

Distribute profiles either from the Tivolidesktop or using MDist2

“Distributing profiles” on page 21

Set up Tivoli Enterprise Console for eventcorrelation (optional)

“Configuring the Tivoli Enterprise Consoleevent server” on page 28

Set up Tivoli Business Systems Manager(optional)

“Integrating IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer with Tivoli Business SystemsManager” on page 36

During installation, IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server performs several tasks that help to set up your IBM TivoliMonitoring environment, including creating profile managers, adding resources tothe profiles, and adding resource models to profiles. The following profilemanagers are created during installation:v WebSphere Administration Serversv WebSphere Application Serversv WebSphere Application Servers with EJBsv WebSphere Application Servers with Servlets

11

If you want to create additional profile managers or customize the subscribers orresource models assigned to your profile manager, the procedures are documentedin Appendix C, “Setting up IBM Tivoli Monitoring” on page 93.

Setting authorization roles

ObjectiveTo assign the IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server authorization roles for managing resources to administratorsand users.

Background informationWhen you install IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server, the following three roles are created:v websphereappsvr_super

v websphereappsvr_admin

v websphereappsvr_user

All tasks require that you assign at least one of these roles to the Tivoliadministrator who is running the task. In addition, some tasks require Tivoliauthorities as defined by Tivoli management region roles. To run tasks andprocesses, the Tivoli administrator must have the required Tivoli authority andmust be assigned one of the IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server authorization roles. You can assign IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server authorization asTivoli management region roles or as resource roles, depending on localauthorization requirements.

Required authorization rolesenior

Before you beginBefore setting authorization roles, you must have installed IBM Tivoli Monitoringfor Web Infrastructure: WebSphere Application Server. See the IBM TivoliMonitoring for Web Infrastructure Installation and Setup Guide for information oninstallation.

When you finishAdd managed resources to a policy region.

ProcedureYou can perform this procedure from the command line or the Tivoli desktop.

Command Line: Use the wsetadmin command to set or change resourceauthorization roles. See the Tivoli Management Framework Reference Manual for moreinformation.

Tivoli desktop: Follow these steps to perform this procedure from the Tivolidesktop:1. Open the Administrators collection to see the icons representing the defined

Tivoli administrators.2. Right-click the existing administrator whose role you want to modify to access

the pop-up menu.3. Select Edit TMR Roles to access the Set TMR Roles window.


4. Select a resource for which you want to set the administrator’s role from theResources scrolling list.

5. Add or remove roles for the selected resources as follows:v To add roles for the selected resources, select one or more roles from those

shown in the Available Roles scrolling list and click the left-arrow button.The selected roles are moved from the Available Roles scrolling list to theCurrent Roles scrolling list. You can also double-click an entry in theAvailable Roles scrolling list to move it automatically to the Current Rolesscrolling list.

v To remove roles for the selected resources, select one or more roles fromthose shown in the Current Roles scrolling list and click the right-arrowbutton. The selected roles are moved from the Current Roles scrolling list tothe Available Roles scrolling list. You can also double-click an entry in theCurrent Roles scrolling list to move it automatically to the Available Rolesscrolling list.

6. You must click Change & Close or Change to add and remove the selectedroles and save your changes.

Note: You must click Change for each resource to which you assign roles.7. (Optional) Repeat Steps 4 through 6 for each resource to which you want to

assign roles.8. Click Change & Close to return to the Administrators window.

The administrator must restart the Tivoli desktop before this change takes effect.

Configuring endpointsBefore you can monitor your resources, you must configure the WebSphere nodesto work with IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server. You only need to configure a node one time. Configuring thenodes includes the following steps:

Table 3. Guidelines to configure endpoints


Link to a JRE for each endpoint IBM Tivoli Monitoring for Web InfrastructureInstallation and Setup Guide

If WebSphere security is enabled, configureclient side security

“Configure client side WebSphere security”

Configuring an endpoint to use anon-default port (Optional)

“Enabling IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer to communicate with IBM WebSphereApplication Server on a non-default port” onpage 14

Enable performance monitoring “Enabling performance monitoring” onpage 15

Enable JVMPI data reporting (optional) “Enabling JVMPI data reporting” onpage 103

Configure client side WebSphere security

ObjectiveTo enable WebSphere security for endpoints.

Chapter 2. Setting up IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server 13

Background informationWhen client side WebSphere security is enabled for IBM WebSphere ApplicationServer, you must perform steps to configure client side WebSphere security.

Required authorization roleNo Tivoli role is required. The procedure below is performed on the endpointsystem, not the Tivoli management region server. Administrator authority isrequired on the IBM WebSphere Application Server system.

Before you beginNone

When you finishIf you are using a non-default port, see “Enabling IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server to communicate with IBMWebSphere Application Server on a non-default port”.

Enable performance monitoring on your IBM WebSphere administration andapplication servers. See “Enabling performance monitoring” on page 15 for moreinformation.

ProcedureUse the following steps to configure client side WebSphere security:1. In the directory where you installed IBM WebSphere Application Server, make

a copy of the sas.client.props file and name it ″sas.wscp.props.″2. Open the new file, sas.wscp.props, and edit the following lines:

com.ibm.CORBA.loginSource=propertiescom.ibm.CORBA.loginUserid=<userid>com.ibm.CORBA.loginPassword=<password>

where <userid> is the user ID for IBM WebSphere Application Server and<password> is the password for the user.

Ensure that the user ID and password are in plain text and not encrypted.3. Save and close the file.

Enabling IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server to communicate with IBMWebSphere Application Server on a non-default port

ObjectiveTo configure endpoints to use a non-default port when IBM WebSphereApplication Server is using a non-default port.

Background informationIf you are using a non-default port for IBM WebSphere Application Server, youneed to change the configuration of the endpoint in order to communicate with theIBM WebSphere Application Server object. You do this by changing the port settingin the sas.wscp.props file. You must do this whether or not WebSphere security isenabled.

Required authorization roleNo Tivoli role is required. The procedure below is performed on the endpointsystem, not the Tivoli management region server. Administrator authority isrequired on the IBM WebSphere Application Server system. Administratorauthority is required on the IBM WebSphere Application Server system.


Before you beginCreate the sas.wscp.props file as described in “Configure client side WebSpheresecurity” on page 13. You must create this file, even if you are not usingWebSphere security. However, you do not need to add the lines in that process thatenable security. Instead, create the file and use it for the procedure listed below.

When you finishNone

ProcedureUse the following steps to change the default port used by endpoints:v Open the sas.wscp.props file in a text editor.

Note: If you have not already created this file, copy the sas.client.props file tosas.wscp.props, as described in “Configure client side WebSpheresecurity” on page 13.

v Add the following line:wscp.hostPort=<port_number>

where <port_number> is the same value specified for propertycom.ibm.ejs.sm.adminServer.bootstrapPort in $WAS_HOME/bin/admin.config.

v Save and close the file.

Enabling performance monitoring

ObjectiveTo enable IBM WebSphere Application Server to collect performance data

Background informationBefore IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer can monitor performance data for your IBM WebSphere administration andapplication servers, you must have the IBM WebSphere Application Server collectperformance data. Data is collected for the performance categories, each of whichcontains counters. Each performance category has an instrumentation level, whichdetermines which counters are collected for the category. Each category has arating (maximum, high, medium, low, or none) that indicates the impact on anapplication’s performance if data is collected for the counters in that category.

For information about WebSphere performance monitoring, see the WebSphereInfocenter.

Required authorization roleNo Tivoli role is required. The procedure below is performed on the endpointsystem, not the Tivoli management region server. Administrator authority isrequired on the IBM WebSphere Application Server system.


When you finishIf you want to gather Java Virtual Machine Profiler Interface (JVMPI) metrics witha custom resource model, enable JVMPI data reporting. See “Enabling JVMPI datareporting” on page 103 for more information. The IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server resource models do not gather thisinformation. You can create other resource models to gather this data. Forinformation, see the IBM Tivoli Monitoring Workbench User’s Guide.


ProcedureTo specify or change the instrumentation level for a resource, do the following:1. Right-click the application server in the hierarchical tree located in the left

panel of the IBM WebSphere Administrator’s console.2. Click Properties in the pop-up menu. The Properties notebook is displayed.3. Click the Services tab.4. From the list of services, select Performance Monitoring Settings and click the

Edit Properties box.The Performance Monitoring Settings panel is now displayed.

5. Select Enable performance counter monitoring.6. Select a resource and choose the appropriate monitoring level. See Table 4 for

the minimum monitoring levels.7. When you are finished, click OK.

You do not need to restart the application server.

Notes:

1. Choosing an instrumentation level causes the same level to be appliedrecursively to all elements beneath the selected resource. To ensure that aninstrumentation level is applied to the desired resource, expand the node andmake sure that only the desired resource is selected before setting the level.

2. If you change a monitoring setting while the related resource model is running,the change is automatically picked up. You do not need to redistribute orrestart the resource model.

The following table lists the minimum monitoring levels for the IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server resource models.

Table 4. Minimum performance monitoring levels for the IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server resource models

Resource model Monitoring setting Minimum monitoring level

Administration Server Status Not applicable Not applicable

Application Server Status Not applicable Not applicable

DB Pools Database Connection Pools High

EJBs Enterprise Beans High

HTTP Sessions Servlet Session Manager High

JVM Runtime JVM Runtime Low

Thread Pools Thread Pools High

Transactions Transaction Manager Medium

Web Applications Web Applications High

Creating IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server objects

ObjectiveTo create IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer objects that represent your IBM WebSphere Application Server components.


Background informationThe first step in managing IBM WebSphere Application Server components(administration server and application servers) is to create IBM Tivoli Monitoringfor Web Infrastructure: WebSphere Application Server objects to represent thecomponents that you want to manage. There are two kinds of IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server objects:v WSAdministrationServers that represent IBM WebSphere Administration serversv WSApplicationServers that represent IBM WebSphere application servers

You can create these objects in one of three ways:v Using the wwebsphere –c commandv Using the Tivoli Framework GUIv Using the Discover_WebSphere_Resources task

Required authorization rolewebsphereappsvr_admin or websphereappsvr_super for the wwebsphere –ccommand and for the Tivoli desktop

websphereappsvr_super for the Discover_WebSphere_Resources task

Before you beginAny systems that you want to manage with IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server must have a supported version ofIBM WebSphere Application Server or higher installed and must be configured asTivoli endpoints. See the Tivoli Management Framework Reference Manual forinformation about configuring Tivoli endpoints.

Ensure that the IBM WebSphere administration server is running.

When you finishSubscribe servers to profile managers, if needed. Distribute resource models to thenew IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverobjects so that you can monitor their status and performance.

ProcedureYou can perform this procedure from the command line, from the Tivoli desktop,or as a task.

Note: If you experience problems performing this procedure, see Appendix F,“Problem determination” on page 107 for information about log files andcommon problems that might occur. You can also see the IBM TivoliMonitoring for Web Infrastructure Reference Guide for information aboutmessages.

Command Line: Use the wwebsphere command with the –c parameter to createobjects. See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for moreinformation.

Tivoli desktop: Follow these steps to create objects from the Tivoli desktop:1. From inside the Monitoring for WebSphere Application Server policy region or

a sub-region, click Create.2. Select the type of object you want to create: WSAdministrationServer or

WSApplicationServer.3. Click Set & Execute.


4. If you selected WSAdministrationServer, complete the following fields on theCreate WSAdministrationServer window:

Node Name (Required)Type the name of the node for the IBM WebSphere administrationserver that this object will represent.

Fully Qualified Host Name (Required)Type the fully qualified host name for the IBM WebSphereadministration server. For example, hpx1.raleigh.tivoli.com is the fullyqualified host name for the hpx1 IBM WebSphere administration server.

Endpoint Name (Required)Select the Tivoli endpoint on which the IBM WebSphere administrationserver is running.

Managed Node Name (Optional)Type the name of the managed node where you want to create theobject.

By default, the object is created on the managed node currently hostingthe gateway that manages the selected endpoint. Type a differentmanaged node name to create the object on a different node.

WebSphere Admin Port (Optional)Type the port number used to open a communication channel with theIBM WebSphere administration server. The default value is 900.

WebSphere Version (Required)Type the version of IBM WebSphere Application Server running on theendpoint. The format must be dot separated For example, if you arerunning IBM WebSphere Application Server version 4.0.2 on theendpoint, type ″4.0.2.″

See the IBM Tivoli Monitoring for Web Infrastructure Release Notes for thesupported versions of IBM WebSphere Application Server.

WebSphere Security Enabled (Optional)Specify whether or not WebSphere security is enabled on the endpoint.If security is enabled, provide the name of the security properties filesin the WebSphere Security Properties File field.

WebSphere Security Properties File (Conditionally required)Type the name of the security properties file. If you enter only the filename, and not the full path, the file is assumed to be in the$WAS_HOME/properties directory on the endpoint.

WebSphere Install Path (Required)Type the full path to the directory on the endpoint where IBMWebSphere Application Server is installed. Use UNIX style slashes forthe directory. For example, use c:/WebSphere/AppServer instead ofc:\WebSphere\AppServer.

WebSphere OS Type (Optional)Type the operating system running on the endpoint, such as ″AIX.″

5. If you selected WSApplicationServer, complete the following fields:

Application Server Name (Required)Type the application server name for this object.

Administration Server Label (Required)Type the Tivoli object label for the existing IBM WebSphere


administration server object with which this application server object isassociated. For example, mysphere_pr@sandhill.

Endpoint Name (Required)Select the Tivoli endpoint on which the IBM WebSphere applicationserver is running.

Has Web Module (Optional)Select this if the IBM WebSphere application server is using the WebModule and is capable of hosting servlets.

Has EJB Module (Optional)Select this if the IBM WebSphere application server is using theEnterprise JavaBeans (EJB) module and is capable of hosting EJBs.

Managed Node Name (Optional)Type the name of the managed node where you want to create theobject.

By default, the object is created on the managed node currently hostingthe gateway that manages the selected endpoint. Type a differentmanaged node name to create the object on a different node.

6. Click Set & Execute.

Task: Follow these steps to perform this procedure using a task:1. From the Tivoli desktop, double-click the Monitoring for WebSphere

Application Server policy region.2. Double-click the WebSphere Application Server Utility Tasks icon.3. Double-click the Discover_WebSphere_Resources task icon and complete the

Execute Task window. Select the managed node on which you want to run theDiscover_WebSphere_Resources task.

4. Select Display on Desktop to display the output of the task on the desktop.5. Increase the timeout value because the Discover_WebSphere_Resources task

takes a considerable amount of time to finish. Allow 300 seconds for eachendpoint on which you are running the Discover_WebSphere_Resources task.

6. Click Execute or Execute and Dismiss to display theDiscover_WebSphere_Resources window.


7. Complete the following fields on the Discover_WebSphere_Resources window:

Policy Region Name (Required)Enter the name of the policy region in which to create the discoveredIBM WebSphere administration server objects. If this policy region doesnot exist, it is created.

Install path of WebSphere Application Server (Conditionally required)The IBM WebSphere Application Server installation path on theendpoint. If you leave this field blank, the default WebSphereApplication Server installation path is used.

Endpoints (Required)The specific endpoints on which to search for objects. Click Choices todisplay all endpoints available to search. See the release notes to knowwhich versions of WebSphere Application Server are supported.

Security Properties File (Conditionally required)If you have security enabled on your IBM WebSphere administrationserver, this task requires a security properties file. Enter the full pathand file name of the security properties file. If you enter only the filename, the file is assumed to be in the $WAS_HOME/propertiesdirectory on the endpoint.

Object destination (Managed Node Name) (Optional)Specifies where to create the objects that correspond to the resourcesdiscovered. The default destination is the managed node that hosts thegateway of the endpoint currently being discovered.

WebSphere Node name if different than host name (Optional)If the endpoint host name is not the same as the IBM WebSphere nodename, enter the IBM WebSphere node name for the endpoint you areselecting.

8. Click Set & Execute to run the Discover_WebSphere_Resources task.

For more information on the Discover_WebSphere_Resources task, see the IBMTivoli Monitoring for Web Infrastructure Reference Guide.

Figure 1. The Discover_WebSphere_Resources task execution window


Setting up the IBM Tivoli Monitoring environment

ObjectiveTo set up the environment required to run IBM Tivoli Monitoring commands.

Background informationIn order to issue IBM Tivoli Monitoring commands such as wdmcmd andwdmlseng in a command window, you first need to source in the Tivolienvironment.

Required authorization roleOn UNIX, the user must have root privileges; on Windows, the user must havemembership in the Administrators group.


When you finishNone

ProcedureYou can perform this procedure from the command line.

To set up the environment, enter one of the following commands at the commandprompt:v On a UNIX managed node, enter one of the following commands:

– For non-C shells:. /etc/Tivoli/setup_env.sh

– For C shell:source /etc/Tivoli/setup_env.csh

v On a UNIX endpoint, enter one of the following commands:– For non-C shells:

. /etc/Tivoli/lcf/x/lcf_env.sh

– For C shell:source /etc/Tivoli/lcf/x/lcf_env.csh

where x is the number of the endpoint installed on the machine.v On a Windows managed node, enter:

%SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd

v On a Windows endpoint, enter:%SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd

where x is the number of the endpoint installed on the machine.

Distributing profilesYou can distribute profiles from either the Tivoli desktop or by using MDist2.

Distributing profiles from the Tivoli desktop

ObjectiveTo distribute profiles to specified subscribers.


Background informationYou can distribute profiles to the following groups:

All levels of subscribersDistributes the profile to all subscribers in the hierarchy.

Next level of subscribersDistributes the profile only to the subscribers named in the Distribute toThese Subscribers: scrolling list of the Distribute Profile window. Thisoption does not distribute to subscribers at lower levels of the hierarchy.Perform the distribution process from profile managers at more than onelevel to reach all the profile endpoints if a profile manager with subscribersresides at the next lower level.

Consider the following example. You have a profile in which a dataless profilemanager is subscribed to a profile manager, and the dataless profile manager has asubscribed endpoint. If you distribute to the next level of subscribers, the profilemanager distributes the profile only to the dataless profile manager. If youdistribute to all levels of subscribers, the profile manager distributes the profile tothe dataless profile manager and to the endpoint.

Required authorization roleadmin

Before you beginv Create a profile manager and profile. See “Creating profile managers and

profiles” on page 94 for information.v Add subscribers to a profile manager. See “Subscribing resources to profile

managers” on page 96 for information.v Add a resource model to a profile. See “Adding default resource models to

profiles” on page 96 and“Adding customized resource models to profiles” onpage 97 for information.

You can also use the predefined profile managers and profiles created duringinstallation.

See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailedinformation about each resource model.

When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the Monitoring for WebSphere Application Server policy region

icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Click Profile → Distribute. The Distribute Profile window opens.3. Select one of the Distribute To options. These options are explained in the

Background information section. You have the following choices:


v Next level of subscribers

v All levels of subscribers

These options are explained in “Background information” on page 22.4. Select one of the Distribute Will options based on the following descriptions:

v Preserve modifications in subscribers’ copy of the profile retains changes toexisting resource models in each copy of the profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed. If youedit the configuration of a resource model in the subscriber’s copy, thosechanges are written to every copy of that profile.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profilewindow, saves the settings you made, and returns to the IBM TivoliMonitoring Profile window.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile window open.

ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide. You can also see “Scheduling a job” on page 71for more information.

7. Click Profile → Close to close the IBM Tivoli Monitoring Profile window.

Distributing profiles using MDist2

ObjectiveTo circulate copies of the monitoring profile to subscribers while using MDist2 sothat administrators and users can activate the monitoring process.

Background informationIBM Tivoli Monitoring uses Multiplexed Distribution (MDist2) to performasynchronous profile data transfers through a hierarchy of repeaters. MDist2returns a sequence of responses containing the distribution status from eachendpoint to the application initiating the distribution. These responses are sentback to IBM Tivoli Monitoring in a log file, on the MDist2 command line, orthrough the MDist2 GUI.

IBM Tivoli Monitoring uses the following MDist2 functions:


Asynchronous deliveryIBM Tivoli Monitoring submits a distribution request and immediatelyreceives a distribution identifier and confirmation that the distribution is inprogress. MDist2 uses the callback function to send the final distributionstatus for each endpoint when it completes each endpoint distributioninstead of waiting until all endpoints are distributed.

Assured deliveryAssures that distributed profiles are delivered to the endpoints when thereare network interruptions, computer shutdowns, or disconnectedendpoints. Assured delivery tries to reestablish the connections until it iseither successful or the distribution time expires.

Check-point and restartAssures that an interrupted data stream resumes from the last successfulcheckpoint. You do not have to resend all the IBM Tivoli MonitoringProfile data when the distribution resumes, but only the data that was notsent when the interruption occurred.

Data depotingStores segments of the profile at a depot close to the endpoint so theendpoints can retrieve the data from the depot instead of from the sourcehost. This reduces network traffic and speeds up the distribution.





profiles” on page 96 and“Adding customized resource models to profiles” onpage 97 for information.


See the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for detailedinformation about each resource model.

When you finishNone

ProcedureYou can perform this procedure from the command line or from the Tivoli desktop.

Command Line: Use the wdistrib command to distribute the profile to thesubscribers of the profile manager. This command updates subscriber databasesand configuration files. If no subscriber is specified, wdistrib updates allsubscribers. Refer to the Tivoli Management Framework Reference Manual for moreinformation about the wdistrib command.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.


b. Double-click the Monitoring for WebSphere Application Server policy regionicon to display the policy region.

c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Click Profile → Distribute to display the Distribute Profile window.3. Select one of the Distribute To options. These options are explained in the

Background information section. You have the following choices:v Next level of subscribers

v All levels of subscribers

These options are explained in “Background information” on page 22.4. Select one of the Distribute Will options based on the following descriptions:

v Preserve modifications in subscribers’ copy of the profile retains changes toexisting resource models in each copy of the profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed. If youedit the configuration of a resource model in the subscriber’s copy, thosechanges are written to every copy of that profile.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profilewindow, saves the settings you made, and returns to the IBM TivoliMonitoring Profile window.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile window open.

ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide. You can also see “Scheduling a job” on page 71for more information.

7. Click Profile → Close to close the IBM Tivoli Monitoring Profile window.


Chapter 3. Setting up the Tivoli Enterprise Console for eventcorrelation

This chapter provides information on setting up the Tivoli Enterprise Console forevent correlation. Setting up event correlation requires the following tasks:1. “Configuring the Tivoli Enterprise Console event server” on page 282. “Configuring the Tivoli Enterprise Console adapter” on page 31

Note: Before you can configure the event adapter, you must create Tivoliobjects for your IBM WebSphere Application Server resources asdescribed in “Creating IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server objects” on page 16.

3. “Filtering events” on page 33

For information about the event classes and rules included with IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server, see Appendix E,“Event classes and rules” on page 105.

For information about using Tivoli Enterprise Console, see the Tivoli EnterpriseConsole User’s Guide.

If you experience problem using the procedures in this chapter, see Appendix F,“Problem determination” on page 107. You can also see the IBM Tivoli Monitoringfor Web Infrastructure Reference Manual for information about any messages that youreceive.

Overview of the Tivoli Enterprise ConsoleThe Tivoli Enterprise Console provides the following functions:v Receiving events from various sourcesv Processing events using rulesv Grouping events and delegating the groups selectively to administratorsv Responding to events automaticallyv Viewing events at a console

In the Tivoli Enterprise Console, rules (.rls) files contain the logic for correlation ofevents. BAROC (.baroc, Basic Recorder of Objects in C) files contain the definedevent classes.

The following list explains basic concepts of event management. For moreinformation about the Tivoli Enterprise Console, refer to the Tivoli EnterpriseConsole User’s Guide.

EventsAn event is a structured piece of information. It carries information aboutitself, including the event class, event identity, severity, location (hostwhere the event originated), and description. IBM Tivoli Monitoring usesevents with resource models to verify the persistence of an indication overa period of cycles.

27

Sources of EventsThe Tivoli Enterprise Console accepts events from many sources. Forexample, you can configure resource models to send events. Typically,Tivoli software is set up so that events are sent in response to changes inan application or system resource.

Event ProcessingThe Tivoli Enterprise Console uses rules to process events. A rule is madeup of a set of logic statements. The rule determines what to do with theevent based on information provided in the event, such as the event class,event name, severity, location, and description.

A rule’s logic provides one or more responses to the event: it can dropinsignificant events, escalate important events, create new events, orrespond to defined relationships of multiple events (event correlation). Itcan also close an old event when a new event indicates that the originalcondition is resolved.

Event Grouping

The Tivoli Enterprise Console can filter events into event groups. Theseevent groups are typically organized by function but can also be organizedby other criteria, such as location or organizational jurisdiction.

Event groups are especially useful for subdividing all Tivoli EnterpriseConsole events into manageable chunks. Administrators can be assigned toone or more event groups.

Viewing EventsThe Tivoli Enterprise Console includes a console where administrators canwatch for incoming events and respond to them. The Tivoli EnterpriseConsole can filter out normal events, respond automatically to anticipatedproblems, and forward only those events that require human intervention.

Responses to EventsThe Tivoli Enterprise Console normally provides automatic responses tomany common events, either by executing response programs or byexecuting Tivoli tasks. For example, you can set up a response to the eventthat is received when a server becomes unavailable. The specific responsecan inform an administrator or attempt automatic restarts of the server, ora combination of both.

You cannot use the Tivoli Enterprise Console automatic responsemechanism with this product. However, you can write Tivoli EnterpriseConsole rules that accomplish the same thing.

Configuring the Tivoli Enterprise Console event server

ObjectiveTo set up your Tivoli Enterprise Console event server to process IBM WebSphereApplication Server events.

Background informationYou must set up the event server before events can be sent to Tivoli EnterpriseConsole. Use the Configure Event Server task to set up the Tivoli EnterpriseConsole event server.

The Configure_Event_Server task performs the following actions:v Imports the IBM Tivoli Monitoring for Web Infrastructure: WebSphere

Application Server event classes and rule set


v Imports the IBM Tivoli Monitoring event classes (if they are not already present)v Imports the Tivoli Business Systems Manager rule set, if appropriatev Compiles the rule base to incorporate new classes and rulesv Loads the new rule base (optional)v Optionally stops and restarts the event server

You can configure only one Tivoli Enterprise Console event server for each Tivolimanagement region. When you have interconnected Tivoli management regions,run the Configure Event Server task against each Tivoli management region thatcontains a Tivoli Enterprise Console event server.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverincludes the following sets of event classes and rules specific to IBM WebSphereApplication Server:v ITMWAS_Eventsv ITMWAS_TEC_Adapter_Eventv Events for each resource model, such as the WebSphereAS_AdminServer_Down

event



When you finishConfigure the Tivoli Enterprise Console event adapter. For more information, see“Configuring the Tivoli Enterprise Console adapter” on page 31.

Configure Tivoli Business Systems Manager to receive events. See Chapter 4,“Integrating with Tivoli Business Systems Manager” on page 35 for moreinformation.

ProcedureYou can run this procedure from the command line or the Tivoli desktop.

Command line: Use the wruntask command to run the Configure_Event_Servertask. For the CLI syntax for this task, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Tivoli desktop: Follow these steps to perform this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the Monitoring for WebSphere

Application Server policy region.2. Double-click the WebSphere Event Tasks icon.3. Double-click the Configure_Event_Server task icon and complete the Execute

Task window. Select the managed node on which you want configure the eventserver.

4. Select Display on Desktop to display the output of the task on the desktop.5. Increase the timeout value because the Configure_Event_Server task can take a

considerable amount of time to finish.6. Click Execute & Dismiss to display the Configure Event Server window.

Chapter 3. Setting up the Tivoli Enterprise Console for event correlation 29

Complete the following fields:

Rule Base ConfigurationSpecify the way that the rule base is created:

Update Current Rule BaseSelect this to update your existing rule base.

Create New Rule Base From ExistingIf you are creating a new rule base, select the name of anexisting rule base, if you have one available. If you have notpreviously created a rule base, accept the default, ″Default.″

If you select this option, you must type the name of the newrule base in the New Rule Base Name field and the path to thenew rule base in the New Rule Base Path field.

Create New Rule BaseSelect this to create a new rule base that is not initialized withan existing rule base.

If you select this option, you must type the name of the newrule base in the New Rule Base Name field and the path to thenew rule base in the New Rule Base Path field. You cannotselect a rule base from the Rule Bases list.

New Rule Base NameEnter the name for the new or existing rule base. The default name is″ITMWAS.″

Note: Do not change the Default rule base. Do not enter ″Default″ inthis field.

Figure 2. The Configure Event Server task window


New Rule Base PathEnter the full path for the new rule base. The default path is″$BINDIR/TME/TEC.″

Rule Base Activation RulesSelect one of the following:

Compile rule base onlyCreates or updates the rule base, but does not upload the rulebase into the event server. Use this option if you want toreview rule base changes before you activate them.

Compile and load rule baseCreates or updates the rule base and loads it into the eventserver. The new rule base is active when the event server isrestarted.

Compile and load rule base and restart systemCreates or updates the rule base, loads it into the event server,and restarts the event server.

7. Click Set and Execute to start the task. The Configure Event Server Outputwindow displays the job status after the task is completed.

Configuring the Tivoli Enterprise Console adapter

ObjectiveTo configure, deploy, and start the Tivoli Enterprise console adapter.

Background informationThe Tivoli Enterprise Console adapter is used to ensure that IBM WebSphereFATAL, ERROR, AUDIT, WARNING, and TERMINATE messages (SeriousEvents)are forwarded to the Tivoli Enterprise Console. The Tivoli Enterprise Consoleadapter is also self-reporting; you can see the adapter status events in yourconsole.

Required authorization rolewebsphereappsvr_admin, websphereappsvr_super

Before you beginConfigure the Tivoli Enterprise Console event server. See “Configuring the TivoliEnterprise Console event server” on page 28 for more information.

Before you can configure the event adapter, you must create Tivoli objects for yourIBM WebSphere Application Server resources as described in “Creating IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server objects” onpage 16.

Ensure that the Tivoli Adapter Configuration Facility is installed. The TivoliAdapter Configuration Facility is required to use event adapters. For information,see the Tivoli Enterprise Console documentation.

Ensure that the IBM WebSphere administration server is running.

When you finishView events in the event console.

ProcedureYou can perform this procedure from either the command line or the Tivolidesktop.


Command line: Use the wruntask command to run theConfigure_WebSphere_TEC_Adapter task. For the CLI syntax for this task, see theIBM Tivoli Monitoring for Web Infrastructure Reference Guide.

Tivoli desktop:

1. From the Tivoli desktop, double-click the Monitoring for WebSphereApplication Server policy region.

2. Double-click the WebSphere Event Tasks icon.3. Double-click the Configure_WebSphere_TEC_Adapter task icon and complete

the Execute Task window.4. Select Display on Desktop to display the output of the task on the desktop.5. Increase the timeout value if you selected more than one IBM WebSphere

administration server because this can causes the task to take longer to displayoutput.

6. Click Execute & Dismiss to display the Configure WebSphere TEC Adapterwindow.Complete the following fields:

Event Adapter PortThe port number that the Tivoli Enterprise Console adapter uses forcommunication. The default port is 42146.

Event Server (name registry format)The name of the event server to which events are forwarded. Enter oneof the three following values:

Event server name in registry formatTo identify an event server that is part of the samemanagement region, type ″@EventServer.″ For an event serverin a different management region, the value is@EventServer#<tmr>, where <tmr> is the name of a Tivolimanagement region.

Figure 3. The Configure WebSphere TEC Adapter task window


NOTECSERVERIf you are not using Tivoli Enterprise Console or do not wantevents to be forwarded to the event server, enterNOTECSERVER.

Blank The default value, @EventServer, is used.

Forward Fatal EventsIndicates whether or not you want fatal events forwarded to the TivoliEnterprise Console with a severity of FATAL. The default value is ″yes.″

Forward Terminate EventsIndicates whether or not you want terminate events forwarded to theTivoli Enterprise Console with a severity of CRITICAL. The defaultvalue is ″yes.″

Forward Error eventsIndicates whether or not you want error events forwarded to the TivoliEnterprise Console with a severity of CRITICAL. The default value is″yes.″

Forward Warning eventsIndicates whether or not you want warning events forwarded to theTivoli Enterprise Console with a severity of WARNING. The defaultvalue is ″yes.″

Forward Audit eventsIndicates whether or not you want audit events forwarded to the TivoliEnterprise Console with a severity of HARMLESS. The default value is″no.″

7. Click Set and Execute to start the task. TheConfigure_WebSphere_TEC_Adapter Output window displays the job statusafter the task is completed.

Filtering eventsEvents that are forwarded by the WebSphere TEC adapter and regarded asharmless or unlikely to require action can be suppressed from displaying on theevent console. The Tivoli Management Framework provides the following methodsfor you to filter out events that you do not want to see:v You can specify that the event is not to be forwarded from the endpoint to the

event server. In this case, you specify filter criteria with theConfigure_WebSphere_TEC_Adapter task. Depending on the frequency of theevents, this option can decrease network traffic. See “Configuring the TivoliEnterprise Console adapter” on page 31 for more information.

v You can create new rules to exclude the event. When you do this, the event willbe forwarded to the event server, but will be eliminated by the rules engine. TheTivoli Enterprise Console Rule Builder’s Guide describes the steps for building andchanging rules.

v You can exclude classes of events using the event console’s user interface. Referto the Tivoli Enterprise Console User’s Guide for more information.


Chapter 4. Integrating with Tivoli Business Systems Manager

This chapter provides information on using Tivoli Business Systems Manager tomanage IBM WebSphere Application Server resources and events.

Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer into Tivoli Business Systems Manager includes the following steps:

Table 5. Integrating with Tivoli Business System Manager

Goal Refer to

1. Install the IBM Tivoli Monitoring forWeb Infrastructure: WebSphereApplication Server integrationprogram on the Tivoli BusinessSystems Manager server

“Integrating IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer with Tivoli Business SystemsManager” on page 36

2. Configure your Tivoli EnterpriseConsole event server to forward eventsto Tivoli Business Systems Manager

“Configuring the Tivoli Enterprise Consoleevent server to work with Tivoli BusinessSystems Manager” on page 37

3. Define the specific IBM TivoliMonitoring for Web Infrastructure:WebSphere Application Server objectsfor Tivoli Business Systems Managerusing a discovery task.

“Discovering resources for Tivoli BusinessSystems Manager” on page 38

This chapter also provides a list of the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server tasks that you can run from TivoliBusiness Systems Manager and information about uninstalling the IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server integration fromTivoli Business Systems Manager.

Understanding Tivoli Business Systems ManagerTivoli Business Systems Manager is a business systems management tool thatenables you to graphically monitor and control interconnected businesscomponents and operating system resources. A business component and itsresources are referred to as a Line of Business (LOB).

Tivoli Business Systems Manager consists of the following components:

Tivoli Business Systems Manager management serverThe Tivoli Business Systems Manager management server processes all theavailability data that is collected from various sources. Availability data isinserted in the Tivoli Business Systems Manager database, where intelligentagents provide alerts on monitored objects and then broadcast those alertsto Tivoli Business Systems Manager workstations. The management serverprocesses all user requests that originate from the workstations andincludes a database server that is built around a Microsoft SQL Serverdatabase.

Tivoli Business Systems Manager workstationThe Tivoli Business Systems Manager workstation displays objects incustomized views, called Line of Business Views. Objects are presented in a

35

hierarchical TreeView so that users can see the relationship betweenobjects. Alerts are overlaid on the objects when the availability of the objectis threatened.

Tivoli Event EnablementTivoli Event Enablement is installed on the Tivoli Enterprise Console eventserver and enables the event server to forward events to Tivoli BusinessSystems Manager. Tivoli Event Enablement defines event classes and rulesfor handling events related to Tivoli Business Systems Manager.

For more information about Tivoli Business System Manager, see the TivoliBusiness System Manager documentation.

PrerequisitesBefore you integrate IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server into Tivoli Business Systems Manager, perform the followingprerequisite steps:v Install Tivoli Business Systems Manager, as described in the Tivoli Business

Systems Manager Installation and Configuration Guide. You must install TivoliBusiness Systems Manager Version 1.5 with patch 35.

v Install and configure the Tivoli Event Enablement (with patch 38) on all TivoliEnterprise Console event servers that receive events that you want to forward toTivoli Business Systems Manager. See the Tivoli Business Systems ManagerInstallation and Configuration Guide for more information.

v Configure Tivoli Business Systems Manager to communicate with each TivoliEvent Enablement installed in the previous step. See the Tivoli Business SystemsManager Installation and Configuration Guide for more information.

Integrating IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server with Tivoli Business Systems Manager

ObjectiveTo integrate IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer with Tivoli Business Systems Manager so you can receive IBM WebSphereApplication Server events on the Tivoli Business Systems Manager.

Background informationTo enable Tivoli Business Systems Manager to manage IBM WebSphere ApplicationServer events, you must install an IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server integration program on the Tivoli Business SystemsManager server. This integration program performs the following steps:v Defines the IBM WebSphere Application Server objects in Tivoli Business

Systems Managerv Adds IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application

Server tasks to the object types in Tivoli Business Systems Managerv Defines a line of business for IBM WebSphere Application Server resources

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.

Before you beginMake sure that your Tivoli Business Systems Manager environment is configuredcorrectly and that you have Tivoli Event Enablement installed on each Tivoli


Enterprise Console event server that you want to forward events. For moreinformation, see the Tivoli Business Systems Manager Installation and ConfigurationGuide.

When you finishConfigure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager. See “Configuring the Tivoli Enterprise Console eventserver to work with Tivoli Business Systems Manager” for more information.

ProcedureUse the following steps to install the IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server integration program:1. On the Tivoli Business Systems Manager server, insert the IBM Tivoli Monitoring

for Web Infrastructure: WebSphere Application Server CD and, from a commandprompt, navigate to the \TBSM directory.

2. Type install to start the installation wizard.3. Click Next on the welcome screen.4. Specify an installation location for the Tivoli Business Systems Manager

integration program. The default location is C:\tivoli\itmwas. Click Browse toselect a different installation location.Click Next to continue.

5. Provide the following Microsoft SQL Server information and click Next to startthe installation.

SQL ServerThe name of the SQL server with which this Tivoli Business SystemsManager server is associated

SQL UseridThe SQL user ID

SQL PasswordThe password for the user ID defined above

A progress bar is displayed to show the progress of the installation. Wheninstallation is complete, a message appears.

6. Click Finish to exit the installation wizard.

Configuring the Tivoli Enterprise Console event server to work withTivoli Business Systems Manager

ObjectiveTo configure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager.

Background informationBefore Tivoli Enterprise Console event servers can forward events to TivoliBusiness Systems Manager, you must configure them to use a rule base to forwardthe events.


Chapter 4. Integrating with Tivoli Business Systems Manager 37

Before you beginInstall the Tivoli Event Enablement on each Tivoli Enterprise Console event serverthat you want to forward events to Tivoli Business Systems Manager. For moreinformation, see the Tivoli Business Systems Manager Installation and ConfigurationGuide for more information.

When you finishDefine your IBM WebSphere Application Server objects for Tivoli Business SystemsManager with the Send_WebSphere_Discovery_Events_to_TBSM task, as describedin “Discovering resources for Tivoli Business Systems Manager”.

ProcedureUse the Configure Event Server task to configure (or reconfigure) each eventserver. If you installed the Tivoli Event Enablement on the event server, this taskrecognizes that and compiles the rule base that forwards events to Tivoli BusinessSystems Manager. For information on running this task, see “Configuring theTivoli Enterprise Console event server” on page 28.

Discovering resources for Tivoli Business Systems Manager

ObjectiveTo define the specific IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server objects for Tivoli Business Systems Manager.

Background informationThe IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverintegration program that you installed in “Integrating IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server with Tivoli Business SystemsManager” on page 36 defined the types of objects that you want Tivoli BusinessSystems Manager to manage. After you define the object types, you must definethe specific objects. You can do this with theSend_WebSphere_Discovery_Events_to_TBSM task. This task searches a managednode for objects and sends a DISCOVER event to Tivoli Business Systems Managerfor each object. The Send_WebSphere_Discovery_Events_to_TBSM task alsomaintains a list of the objects that have been discovered and alerts Tivoli BusinessSystems Manager when they have been deleted by sending Tivoli Business SystemsManager a GONE event for each object that no longer exists on the managed node.


Before you beginConfigure your Tivoli Enterprise Console event server, as described in“Configuring the Tivoli Enterprise Console event server to work with TivoliBusiness Systems Manager” on page 37.

When you finishUse Tivoli Business Systems Manager to view and manage your IBM WebSphereApplication Server objects. For information on using Tivoli Business SystemsManager, see the Tivoli Business Systems Manager User’s Guide. For information onthe IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Servertasks that you can run from Tivoli Business Systems Manager, see “Working withTivoli Business Systems Manager” on page 39.



Command line: Use the wruntask command to run theSend_WebSphere_Discovery_Events_to_TBSM task from the command line. Forinformation on the CLI syntax for this task, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Tivoli desktop: Use the following steps to run this procedure as a task:1. Open the task library window by performing the following steps:

a. Open the Tivoli desktop.b. Double-click the Monitoring for WebSphere Application Server policy

region icon to display the policy region.c. Double-click the WebSphere Application Server Utility Tasks icon to open

the task library window.2. In the WebSphere Application Server Utility Tasks task library, double-click the

Send_WebSphere_Discovery_Events_to_TBSM task.3. Select the managed node on which you want to search for objects.4. Select Display on Desktop to display the output on the desktop.5. Increase the timeout vaue if you selected more than one managed node because

this can cause the task to take longer to display output.6. Click Execute.

If the task completes successfully, you receive a list of the DISCOVER and GONEevents that were sent to Tivoli Business Systems Manager.

Working with Tivoli Business Systems ManagerIn addition to using Tivoli Business Systems Manager to monitor the state of yourresources, you can also run tasks on the objects. IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server tasks are loaded into Tivoli BusinessSystems Manager when you install the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server integration program. These tasksappear on the Operation Tasks menus for the different object types(WSAdministrationServer and WSApplicationServer). This Operation Tasks menuis displayed when you right-click an object.

You can perform the following IBM WebSphere administration server tasks fromTivoli Business Systems Manager:v Check_Administration_Server_Statusv List_Application_Serversv Start_Administration_Serverv Stop_Administration_Server

You can perform the following application server tasks from Tivoli BusinessSystems Manager:v Check_Application_Server_Statusv Start_Application_Serverv Stop_Application_Server

Tivoli Business Systems Manager also monitors the status of resource models.Events generated by the Tivoli Enterprise Console adapter or resource models areforwarded from Tivoli Enterprise Console to Tivoli Business Systems Manager.

Chapter 4. Integrating with Tivoli Business Systems Manager 39

For more information about these tasks and resource models, see the IBM TivoliMonitoring for Web Infrastructure Reference Guide.

Uninstalling IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server integration from Tivoli Business Systems Manager

ObjectiveTo remove the IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server integration program from Tivoli Business Systems Manager.

Background informationUninstalling the IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server integration program removes the IBM WebSphere ApplicationServer object definitions and objects from Tivoli Business Systems Manager.

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.


When you finishNone

ProcedureUse the following steps to perform this procedure:1. From a command prompt on the Tivoli Business Systems Manager server,

navigate to the directory where you installed the IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server integration program. Thedefault directory is C:\tivoli\itmwas.

2. Type uninstall to start the uninstallation wizard.3. Click Next on the welcome screen.4. The installation location for the Tivoli Business Systems Manager integration

program is displayed. Click Next to continue.5. Provide the following Microsoft SQL Server information and click Next to start

the uninstallation:

SQL ServerThe name of the SQL server with which this Tivoli Business SystemsManager server is associated

SQL UseridThe SQL user ID

SQL PasswordThe password for the user ID defined above

6. Click Finish to exit the installation wizard.


Chapter 5. Working with resource models

This chapter provides information about using the resource models that areincluded in IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer. You can customize various management aspects of the resource models sothat they have the appropriate settings for your monitoring environment.Customizing a resource model involves the following steps:v “Modifying indications” on page 42v “Specifying tasks for an indication” on page 44v “Sending a notice to administrators when an event occurs” on page 45v “Creating scheduling rules” on page 46v “Modifying data logging settings” on page 48v “Managing profiles and resource models at endpoints” on page 50v “Managing IBM Tivoli Monitoring gateways” on page 51v “Determining which resource models are running on endpoints” on page 52v “Viewing resource model results with the IBM Tivoli Web Health Console” on

page 53

Resource model libraryIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides the following resource models.

Table 6. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverresource models

Resource model Description

WebSphereAS Administration Server Status Monitors the state of the administrationserver.

WebSphereAS Application Server Status Monitors the state of the application server.

WebSphereAS DB Pools Monitors the WebSphere databaseconnection pool at the data source level.

WebSphereAS EJBs Monitors Enterprise JavaBeans (EJBs),including performance and exceptions.

WebSphereAS HTTP Sessions Monitors HTTP sessions.

WebSphereAS JVM Monitors the performance of the Java VirtualMachine (JVM) runtime memory.

WebSphereAS Thread Pools Monitors the object request broker (ORB)and Web container pools.

WebSphereAS Transactions Monitors the application server transactions.

WebSphereAS Web Applications Monitors information about theservlets/Java server pages (JSPs) and Webapplications.

Note: ″WebSphereAS″ is the abbreviated name of the IBM Tivoli Monitoringcategory of IBM WebSphere Application Server resource models. It is usedas an identifying prefix.

41

For information about the default configuration of these resource models, see theIBM Tivoli Monitoring for Web Infrastructure Reference Guide.

Modifying indications

ObjectiveTo modify indication rules so that resources are monitored and events aregenerated relevant to your environment.

Background informationEach resource model triggers an indication if certain conditions defined by theresource model’s thresholds are not satisfied during the monitoring cycle.





profiles” on page 96 for information.


When you finishDistribute the profile to which the resource model belongs. See “Distributingprofiles from the Tivoli desktop” on page 21.

– OR –

Optional: Continue customizing the resource model:v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 44v Specify if you want to receive information on a specific event through a notice.

See “Sending a notice to administrators when an event occurs” on page 45v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules” on page 46v Specify if you want the log data collected by a resource model written to a local

database. See “Modifying data logging settings” on page 48


Command Line: Use the wdmeditprf command to customize a resource modelfor a profile. See the IBM Tivoli Monitoring Reference Guide for more information.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.


b. Double-click the Monitoring for WebSphere Application Server policyregion icon to display the policy region.

c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize from the IBM Tivoli

Monitoring Profile window.3. Click Edit to open the Edit Resource Model dialog.4. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.5. Select the indication that contains the values you want to modify.6. Apply the changes to the values that are appropriate to your requirements. See

the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for the defaultresource model settings.You can customize the following fields. For more information about thesefields, see the IBM Tivoli Monitoring documentation.

Number of occurrencesSpecifies the number of consecutive times the problem occurs beforethe software generates an indication. You can change this value tospecify the number of times a problem occurs before an indication isgenerated.

Number of holesDetermines how many cycles that do not produce an indication canoccur between cycles that do produce an indication.

Use the value for the Number of Holes in conjunction with theNumber of Occurrences parameter and the Cycle Time to define atime window for the generation of an event.

Send TEC EventsSelect this check box to send an event to the Tivoli Enterprise Console.You must have Tivoli Enterprise Console installed and configured.

Send to TBSMSends events to Tivoli Business Systems Manager. You do not need toselect this box. If you have Tivoli Business Systems Manager installedand configured, Tivoli Enterprise Console automatically forwardsevents to Tivoli Business Systems Manager.

7. Specify the serverity of the indication in the Severity pull-down list. You havethe following options:v FATALv CRITICALv WARNINGv HARMLESSv MINOR

8. Click one of the following buttons:

Apply ChangesSaves the changes and leaves the Indications and Actions windowopen.

Apply Changes and CloseCloses the Indications and Actions window and saves the changes.

Chapter 5. Working with resource models 43

Specifying tasks for an indication

ObjectiveTo specify a task so administrators and users can determine corrective or reportingtasks for an event.

Background informationYou can select one or more task to run automatically when an event occurs. Thesetasks can access the IBM Tivoli Monitoring event name and thresholds byaccessing the environment variables.





profiles” on page 96 and for information.



– OR –

Optional: Continue customizing the resource model:v Specify if you want to customize your thresholds and events to optimize the

monitoring process. See “Modifying indications” on page 42v Specify if you want to receive information on a specific event through a notice.


time periods of selected days. See “Creating scheduling rules” on page 46v Specify if you want the log data collected by a resource model written to a local

database. See “Modifying data logging settings” on page 48



Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the Monitoring for WebSphere Application Server policy

region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.


d. Double-click the profile icon in which you want to customize a resourcemodel.

2. Select a resource model from the IBM Tivoli Monitoring Profile window andclick Edit to open the Edit Resource Model window.

3. Click Indications. The Indications and Actions window opens and displays theindications appropriate to the selected resource model.

4. Select the indication for which you want to specify a task.5. Click Tasks in the Action List window. The Tasks window opens.6. Double-click the appropriate task library from the scroll list of the Libraries

panel. The tasks contained in the library are displayed in the Tasks panel.7. Double-click the appropriate task in the Tasks panel. You can also click Select

Task.8. Specify the appropriate parameters in the Configure Task window.

Additional information: This only applies to tasks that require input parameters.9. Click Change & Close to add the task to the Action List panel in the

Indications and Actions window.

Repeat these steps for each task you want to add.

Sending a notice to administrators when an event occurs

ObjectiveTo send a notice in response to an event so administrators can take the appropriateactions or responses.

Background informationYou can select the IBM Tivoli Monitoring Utility task to send notices in response toan event.







You must create an administrator before you can subscribe the administrator to anotice group. For information about creating administrators, see the TivoliManagement Framework, Version 3.7.1: Reference Manual.


– OR –

Optional: Continue customizing the resource model:


v Specify if you want to customize your thresholds and events to optimize themonitoring process. See “Modifying indications” on page 42

v Specify if you want corrective or reporting tasks for an event. See “Specifyingtasks for an indication” on page 44

v Specify if you want the monitoring of resource models to take place on specifictime periods of selected days. See “Creating scheduling rules”

v Specify if you want the log data collected by a resource model written to a localdatabase. See “Modifying data logging settings” on page 48



Tivoli desktop:


region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select a resource model from the IBM Tivoli Monitoring Profile window and

click Edit to open the Edit Resource Model window.3. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.4. Select the indication for which you want to generate notices.5. Click Tasks in the Action List window. The Tasks window opens.6. Double-click the IBM Tivoli Monitoring Utility Tasks library in the scroll list

of the Libraries panel. The tasks contained in the IBM Tivoli Monitoring UtilityTasks library are displayed in the Tasks panel.

7. Double-click dm_mn_send_notice in the Tasks panel. The Configure Taskwindow opens.

8. Specify the appropriate parameters in the Configure Task window.Additional information: Run the wlsnotif -g command to see the available NoticeGroups. See the IBM Tivoli Monitoring Reference Guide for more information.

9. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.

Creating scheduling rules

ObjectiveTo create schedule rules so administrators and users can determine the timeperiods on selected days when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to createspecific scheduling rules that determine a period when monitoring takes place. Youcan divide the overall collection period into active and inactive intervals byapplying one or more schedule rules.


The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules whichallows you set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If the profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that monitors the same local time period in different time zones. Alltimes of events or activities reported from endpoints or gateways are also loggedin the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesContains a list of the defined scheduling rules, which manage the timeintervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.








– OR –


monitoring process. See “Modifying indications” on page 42v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 44


v Specify if you want to receive information on a specific event through a notice.See “Sending a notice to administrators when an event occurs” on page 45

v Specify if you want the log data collected by a resource model written to a localdatabase. See “Modifying data logging settings”



Tivoli desktop:




click Edit to open the Edit Resource Model window.3. Click Schedule to open the Scheduling window.4. To use the default monitoring period, select Always in the Schedule panel.5. To customize the monitoring period, perform the following steps:

a. Set a Start Date and Stop Date to customize the monitoring period.b. Click New Rule in the Schedule Rules panel.c. Type a name for the rule in the Rule Name text box of the Rule Editor

panel.d. Select one or more items in the weekday list to specify the day or days on

which you want the collections active during the collection period.Additional information: Use the Shift or Ctrl key as necessary to select morethan one day from the list.

e. Set the Start Time and Stop Time for the collection activity or select the AllDay check box.Additional information: Times are always interpreted as local time where theendpoint engine runs. Setting a time interval of 08:00 to 13:00 ensures thatmonitoring takes place between those times in all time zones to which youdistribute the profile.

f. Click Set Rule. Your new rule appears in the Schedule Rules list.Additional information: To display the details of any rule, select the rule in theSchedule Rules list. Its settings are displayed in the Rule Editor group box.

6. Click Modify & Close to save your rule and close the Scheduling window.

Repeat these steps for each scheduling rule that you want to create.

Modifying data logging settings

ObjectiveTo modify data logging information so administrators and users can log datacollected by a resource model and write it in a local database.


Background informationYou can view the log data through the IBM Tivoli Monitoring Web Health Consoleafter you write it in a local database. You can store one of the following types ofdata in the database:

Raw dataData written exactly as the resource model collects it. All the monitoredvalues are collected and copied in the database.

Aggregated dataData collected and aggregated at fixed intervals that you define(Aggregation Period). Only the aggregated values are written in thedatabase. The aggregated data is calculated on the basis of one or more ofthe following options:v Maximumv Minimumv Average

Tivoli Enterprise Data Warehouse data loggingData collected is logged to the Tivoli Enterprise Data Warehouse.

Note: To enable Tivoli Enterprise Data Warehouse data logging, you mustdisable aggregated data logging.








– OR –


monitoring process. See “Modifying indications” on page 42v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an indication” on page 44v Specify if you want to receive information on a specific event through a notice.


time periods of selected days. See “Creating scheduling rules” on page 46




Tivoli desktop:




click Edit to open the Edit Resource Model window.3. Click Logging to open the Logging window.4. Select Enable Data Logging in the Data Logging Settings panel. To enable raw

data logging, select Raw Data.5. To enable logging aggregated data, perform the following steps to specify the

aggregation rule applied to the data before it is written to the database:a. Set Hours and Minutes of the Aggregation Period to the required values.b. Select one or more of the following functions to perform on the numerical

data collected during the aggregation period before it is written to thedatabase:

MaximumCalculates and logs the peak value in each aggregation period.

MinimumCalculates and logs the lowest value in each aggregation period.

AverageCalculates and logs the average of all values in each aggregationperiod.

6. To enable Tivoli Enterprise Data Warehouse data logging, clear Aggregateddata and select TEDW data.

7. Set Hours and Minutes of the Historical Period to the required values.8. Click Apply Changes and Close to save your changes and close the Logging

window.

Managing profiles and resource models at endpoints

ObjectiveTo manage profiles and resource models after they are distributed to endpoints soadministrators and users can maintain monitoring processes on those endpoints.

Background informationNone






profiles” on page 96 for information.v Distribute the profile. See “Distributing profiles from the Tivoli desktop” on

page 21 for information.


When you finishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command Line: Use the wdmcmd command to stop or restart IBM TivoliMonitoring on one or more endpoints from a gateway or server.

Use the wdmdistrib command to distribute a profile to one or more subscribers.

Use the wdmeng command to stop or start profiles or resource models atendpoints or to delete profiles at endpoints.

Use the wdmlseng command to return a list and the status of all resource modelsthat have been distributed on a specified endpoint.

Use the wdmtrceng command to set the trace parameters of the IBM TivoliMonitoring engine at the endpoint.

See the IBM Tivoli Monitoring Reference Guide for information about the syntax ofthese commands.

Managing IBM Tivoli Monitoring gateways

ObjectiveTo manage IBM Tivoli Monitoring on gateways so administrators and users canrun monitoring processes on those gateways.








v Distribute the profile. See “Distributing profiles from the Tivoli desktop” onpage 21 for information.


When you finishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command Line: Use the wdmmn command to stop or start selected IBM TivoliMonitoring processes on one or all gateways. See the IBM Tivoli MonitoringReference Guide for more information.

Determining which resource models are running on endpoints

ObjectiveTo determine which resource models are running on an endpoint.






profiles” on page 96 for information.v Distribute the profile. See “Distributing profiles from the Tivoli desktop” on

page 21 for information.


When you finishNone

ProcedureYou can perform this procedure from the command line.

You can also view the resource models distributed to endpoints with the WebHealth Console, as described in “Viewing resource model results with the IBMTivoli Web Health Console” on page 53.

Command Line: Use the wdmlseng command to determine which resourcemodels are running on an endpoint:wdmlseng -e <endpoint>

where endpoint> is the Tivoli endpoint label.


Refer to the IBM Tivoli Monitoring User’s Guide for more information.

Viewing resource model results with the IBM Tivoli Web HealthConsole

This section provides an overview of the Web Health Console. For completeinformation on installing and working with the Web Health Console see the latestversion of the IBM Tivoli Monitoring User’s Guide. The Web Health Console runs onNetscape 6.x and Internet Explorer 6.x. You can use the Web Health Console forthe following purposes:v Checking, displaying, and analyzing the status and health of endpoints that

have distributed resource resource modelsv Displaying an endpoint’s real-time and historical data logged to the IBM Tivoli

Monitoring databasev Viewing online and historical data on endpoints as a follow-up to specific

problemsv Starting and stopping the IBM Tivoli Monitoring engine and individual resource

models on selected endpointv Removing a profile from the selected endpoint

You can use the Web Health Console to check, display, and analyze the status andhealth of any endpoint with profiles and resource models. Status reflects the stateof the endpoint, such as running or stopped. Health is a numeric value determinedby resource model settings. You can also use the Web Health Console to work withreal-time or historical data from an endpoint that is logged to the IBM TivoliMonitoring database.

You can use the diagnostic and monitoring capabilities of the Web Health Consoleto perform targeted analysis of problems associated with individual endpointswhen an event is sent to the Tivoli Enterprise Console. Use the online andhistorical data to follow up specific problems with single endpoints.

Understanding resource healthThe Web Health Console obtains events and indications from endpoints. The WebHealth Console displays the health of each potential problem as a numeric valuebetween 100 (perfect health) and zero (with zero meaning that the conditions forthe corresponding event are met). Intermediate values show the percentage ofoccurrences currently registered with respect to the total number of occurrencesneeded to trigger an event. See Table 7

Table 7. Health Determination Example

Cycle 1 2 3 4 5

CPU% 55 73 54 63 68

Occurrences or Holes H O H O O

Occurrence Count 0 1 1 2 3

Health % 100 75 75 50 25

Table 7 displays the health percentage changes in steps of 25% because 4occurrences were required to trigger an event; if the indication required 5occurrences, the health percentage would have changed by steps of 20%. Resourcehealth is determined at the indication level and passed up to the endpoint. Thelowest health of any indication in a resource model is shown as the health of thatresource model and the lowest health of any resource model installed on an


endpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is installed on an endpoint has a health of zero, the healthof the endpoint is shown as zero.

The required occurrences, cycle times, thresholds, and parameters for indicationsare defined when the resource model is created in the IBM Tivoli MonitoringWorkbench. If you use the default profile managers created during the installationof IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server,the occurrences, cycle times, thresholds, and parameters are already defined.

Connecting the IBM Tivoli Monitoring Web Health ConsoleYou can connect the IBM Tivoli Monitoring Web Health Console to any Tivolimanagement region server, managed node, or endpoint, and configure it tomonitor any or all of the endpoints that are found in that region. The IBM TivoliMonitoring Web Health Console does not have to be within the region itself,although it could be. To connect to the IBM Tivoli Monitoring Web Health Consoleyou need access to the server on which the IBM Tivoli Monitoring Web HealthConsole server is installed and the IBM Tivoli Managed Region on which you wantto monitor health. All user management and security is handled through the IBMTivoli management environment. This includes creating users and passwords aswell as assigning authority.

For more information, see the Web Health Console documentation in the IBMTivoli Monitoring publications library.


Chapter 6. Working with IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server resources

This chapter provides information about working with IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server resources. The following tableprovides an overview of the topics covered in this chapter.


Check the status of an object “Checking the status of an IBM WebSphereadministration or application server”

Start or stop a server “Starting or stopping a server” on page 57

List application servers “Listing application servers” on page 58

View endpoint or callback log files “Viewing endpoint or callback log files” onpage 60

Note: The procedures in this chapter are performed from the Tivoli desktop. Youcan also perform the procedures from the command line or using theassociated tasks. For information about running tasks and jobs, seeChapter 7, “Working with tasks and jobs” on page 63. For specificinformation about tasks, see the IBM Tivoli Monitoring for Web InfrastructureReference Guide.

Checking the status of an IBM WebSphere administration orapplication server

ObjectiveTo check the status of an IBM WebSphere administration or application server.

Background informationIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverdisplays the status of the IBM WebSphere administration or application server.

Required authorization rolewebsphereappsvr_user, websphereappsvr_admin, websphereappsvr_super

Before you beginCreate IBM WebSphere Application Server objects. See “Creating IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server objects” onpage 16 for more information.

When you finishStart or stop the server, depending on the status returned. See “Starting orstopping a server” on page 57 for more information.

ProcedureYou can perform this procedure from the command line, as a task, or from theTivoli desktop.

You can also check the status of a server with a resource model. See Chapter 5,“Working with resource models” on page 41 for information about using resourcemodels.

55

Command line: Use the wruntask command to run either theCheck_Administration_Server_Status or Check_Application_Server_Status task. Forthe CLI syntax for these tasks, see the IBM Tivoli Monitoring for Web InfrastructureReference Guide.

Task: Use the Check_Administration_Server_Status task to check the status of theIBM WebSphere administration server. Use the Check_Application_Server_Statustask to check the status of an application server. See Chapter 7, “Working withtasks and jobs” on page 63 for information about running tasks.

Tivoli desktop: Use the following steps to run this procedure from the Tivolidesktop:1. From the Tivoli desktop, double-click the policy region that contains the

administration or application server objects to display the Policy Regionwindow.The default policy region is Monitoring for WebSphere Application Server. Ifyou created additional policy regions, open the one that contains the objectsyou want to work with.

2. Right-click an IBM WebSphere administration or application server and selectOperation to display the Operation pop-up menu.

3. Select Check Status to display the status of the server.

Figure 4. The Operation menu on a IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server object


The status of the server is one of the following:v Initializingv Upv Terminatingv Downv Unknown – the status of the server cannot be determined. Check the

communication to the server and try again.

Starting or stopping a server

ObjectiveTo start or stop an IBM WebSphere administration or application server.

Background informationIf an IBM WebSphere administration server is down, any IBM WebSphereapplication servers associated with that administration server are unavailable. If anapplication server is down, any applications running on that application server arealso down.


Before you beginCheck the status of your IBM WebSphere administration and application servers.See “Checking the status of an IBM WebSphere administration or applicationserver” on page 55 for more information.

When you finishNone


Figure 5. The output window for the Check Status action

Chapter 6. Working with IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server resources 57

Command line: Use the wruntask command to run either theStart_Administration_Server or Stop_Administration_Server to start or stop an IBMWebSphere administration server. Use the wruntask command to run either theStart_Application_Server task or Stop_Application_Server task to start or stop anapplication server. For the CLI syntax for these tasks, see the IBM Tivoli Monitoringfor Web Infrastructure Reference Guide.

Task: Use the Start_Administration_Server task or Stop_Administration_Servertask to start or stop an IBM WebSphere administration server. Use theStart_Application_Server task or Stop_Application_Server task to start or stop anapplication server. See Chapter 7, “Working with tasks and jobs” on page 63 forinformation about running tasks.


administration or application server objects to display the Policy Regionwindow.The default policy region is Monitoring for WebSphere Application Server. Ifyou created additional policy regions, open the one that contains the objectsyou want to work with.

2. Right-click an IBM WebSphere administration or application server and selectOperation to display the Operation pop-up menu.

3. Click Start Server or Stop Server to start or stop the server.4. If you clicked Stop Server, a confirmation window is displayed. Click Yes to

stop the server or No to cancel the action.

Listing application servers

ObjectiveTo list the application servers associated with an IBM WebSphere administrationserver.

Background informationIBM WebSphere administration servers have associated application servers. Youcan list these servers before running the Discover_WebSphere_Resources task todetermine which application servers need to have objects created for them beforethey can be monitored with IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server. When you have this list, run theDiscover_WebSphere_Resources task against the administration servers to createapplication server objects for them.

You can also use this list to determine which tasks to run on your applicationservers.


Before you beginEnsure that your IBM WebSphere administration server is running. See “Checkingthe status of an IBM WebSphere administration or application server” on page 55for more information.


When you finishIf your list of application servers includes any that do not have IBM TivoliMonitoring for Web Infrastructure: WebSphere Application Server objects, createobjects for them. See “Creating IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server objects” on page 16 for more information.


Command line: Use the wruntask command to run the List_Application_Serverstask. For the CLI syntax for this tasks, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Task: Use the List_Application_Servers task to list the application serversassociated with an IBM WebSphere administration server. See Chapter 7, “Workingwith tasks and jobs” on page 63 for information about running tasks.


application server objects to display the Policy Region window.The default policy region is Monitoring for WebSphere Application Server. Ifyou created additional policy regions, open the one that contains the objectsyou want to work with.

2. Right-click the IBM WebSphere administration server for which you want to listthe application servers and select Operation to display the Operation pop-upmenu.

3. Select List Application Servers to display a list of the application serversassociated with this administration server.

You can also double-click an IBM WebSphere administration server to view a list ofthe associated application servers. Double-clicking the IBM WebSphere

Figure 6. List of application servers associated with the specified IBM WebSphere administration server.


administration server object displays only the application servers that have beendiscovered by IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server; using the procedure above displays all application serversassociated with the IBM WebSphere administration server.

Viewing endpoint or callback log files

ObjectiveTo list or display all IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server endpoint or callback logs for an IBM WebSphere administrationor application server.

Background informationYou can use the endpoint or callback logs if you encounter any problems whilerunning IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer.



When you finishNone


Command line: Use the wruntask command to run the List_Trace_Logs task. Forthe CLI syntax for this task, see the IBM Tivoli Monitoring for Web InfrastructureReference Guide.

Task: Use the List_Trace_Logs task to list the callback and endpoint logs. SeeChapter 7, “Working with tasks and jobs” on page 63 for information aboutrunning tasks.


administration server objects to display the Policy Region window.The default policy region is Monitoring for WebSphere Application Server. Ifyou created additional policy regions, open the one that contains the objectsyou want to work with.

2. Right-click an IBM WebSphere administration or application server and selectDiagnostics to display the Diagnostics pop-up menu.

3. Select Tivoli Logs.4. Select the type of log you want to list, either Endpoint or Callback. A list of

logs is displayed.


From the Log Files window, you can select individual callback logs to display ordelete. For endpoint logs, you can only select to display or delete all logs.

You can refresh this list to display any logs created after you generated the list.

Figure 7. The list of endpoint logs associated with the IBM WebSphere administration server


Chapter 7. Working with tasks and jobs

This chapter provides information about using tasks and jobs to manage your IBMWebSphere Application Server resources.

Table 8 shows the options to manage tasks and jobs.

Table 8. Working with tasks and jobs

Goal Refer to

Run a task to perform a specific operation. “Running a task” on page 63

Define a standard task with specific arguments to customize thetask.

“Customizing a task” on page 66

Create a job from a task so that it can be scheduled to run. “Creating a job” on page 67

Run a job with predefined arguments. “Running a job” on page 70

Schedule jobs to run at specified times. “Scheduling a job” on page 71

The installation process installs the task library in the product policy region. Werecommend that you do not remove the task library from this policy region. Thetask library contains default policies that affect how the task library works.

The policy region containing the task library defines task and job policies. Defaultpolicies set profile manager options and endpoints for tasks. Validation policiescontrol the creation and execution of tasks.

Running a task

ObjectiveTo run one of the standard tasks in the task library.

Background informationA task is an action that must be routinely performed on selected endpoints ormanaged nodes throughout the network. A task defines the executables to be run,the authorization role required to execute the task, and the user or group nameunder which the task is run. IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server provides standard tasks in a task library. Standardtasks run on any system without consideration of platform type.

Required authorization rolesSee the IBM Tivoli Monitoring for Web Infrastructure Reference Guide for theauthorization role required for each task.


When you finishNone


63

Command Line: Use the wruntask command to run a task. See the IBM TivoliMonitoring for Web Infrastructure Reference Guide for information about runningtasks from the command line.

For more information about the wruntask command, see the Tivoli FrameworkReference Manual.

Tivoli desktop:

1. Open the task library window by performing the following steps:a. Open the Tivoli desktop.b. Double-click the Monitoring for WebSphere Application Server policy

region icon to display the policy region.c. Double-click the product task icon to open the product task library

window.2. Double-click the task icon that you want to run to open the Execute Task

window.Additional information: The Execute Task window is a generic window thatcontains execution parameters for all tasks.

3. Select one of the following check boxes in the Execution Mode group box:

ParallelRuns the task simultaneously on all targets. Parallel is typically thefastest method of execution.

Serial Runs the task sequentially on all targets in alphabetical order.

StagedRuns the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you are running thetask on a large number of endpoints. Complete Step 5 to specify theStaging Count (number of targets to run against per stage) and theStaging Interval (number of seconds between each set).

4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional information: The Timeout value does not stop the task. This valuespecifies the number of seconds the Tivoli desktop waits for the task tocomplete before it issues an error. The task continues to execute on theendpoint without displaying the output results. Setting an early timeoutenables your Tivoli desktop to become available again if the task takes a longtime to execute. The default is 60 seconds. If the task takes longer to completethan the specified Timeout and is running in Serial or Staged mode, theproduct moves on to other endpoints after this time expires.

5. Optional: If you selected Staged in Step 3, specify the number of endpoints toinclude in each staged set in the Staging Count text box and the number ofseconds between each set’s startup time in the Staging Interval text box.

6. Select one or more of the following check boxes in the Output Format dialogto choose the output returned upon task completion:

HeaderIncludes a descriptive header for each record, such as the task nameand target.

Return CodeIncludes the programming codes produced when the task executes.

Standard ErrorIncludes all error messages encountered when the task executes.


Standard OutputIncludes all information that results from the task execution.

7. Select one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Tivoli desktop to display the task output on the Tivoli

desktop.Additional information: If you choose Display on Desktop, you have theoption, inside the output display window, of saving the information to afile.

v Click Save to File to save the output to a file.a. Type the name of the endpoint on which to save the output in the On

Host text box.Additional information: The endpoint must be a Tivoli client.

b. Type the absolute path name for the output file in the Output File textbox.Additional information: Example: /tmp/mytask.out

c. Click Set & Close to set your choices and return to the Execute Taskwindow.

8. Choose the endpoints on which you want to run the task by doing one of thefollowing:v Run the task on specific endpoints by doing the following:

a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the

Selected Task Endpoints list.

—OR—v Run the task on all subscribers of the specified profile managers by doing

the following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.9. Click Execute or Execute and Dismiss. If the task requires additional input

parameters, the task argument window is displayed. Otherwise, the taskexecutes.

Chapter 7. Working with tasks and jobs 65

Additional information: For information about how to fill in the task argumentdialog, refer to the task description in the IBM Tivoli Monitoring for WebInfrastructure Reference Guide or click Task Description to display the onlinehelp.

10. Click Set & Execute to run the task.

Customizing a task

ObjectiveTo customize one of the standard tasks in the task library so you can save definedarguments for future use.

Note: You can only customize tasks that use additional arguments.

Background informationA customized task is a standard task with defined arguments saved in the tasklibrary with a unique name. For example, you can customize a task to save taskoutput results to a file after each execution. Because you can customize taskarguments, the Tivoli environment does not display argument dialogs when yourun the task from the Tivoli desktop. However, if you run a customized task fromthe command line, you still must specify the task arguments. Running acustomized task requires additional information before it runs, such as the target ofthe task.

Required authorization roleswebsphereappsvr_admin


Figure 8. Example of a task argument window


When you finishYou can run the task by following the procedure in “Running a task” on page 63.When you run a customized task, the Tivoli desktop does not display the taskargument dialog.

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Open the task library window by performing the following steps:

a. Open the Tivoli desktop.b. Double-click the Monitoring for WebSphere Application Server policy


window.2. Double-click a task icon to open the Execute Task window for that task.3. Click Execute to open the task argument window.4. Enter the appropriate values for this customized task.

Additional information: For information about each field in these windows, seethe task description in the IBM Tivoli Monitoring for Web Infrastructure ReferenceGuide or click Task Description to display the online help.

5. Click Save to open the Save Argument window.6. Type the following information to define the customized task:

a. Type a name for the task in the Name text box.Additional information: This name will appear in the Library Contents fieldso you can view the customized tasks that are based on the parent task.

b. Type an identifier for this task.Additional information: An identifier is the name of the task icon that willappear in the Task Library window. A customized task identifier has twoparts. The first part should be the standard task name. The second partshould be descriptive information that makes sense to you.The software generates a unique default name if no identifier is entered.To enable filtering for an identifier without the standard task name, editthe tl_def_man_nodes policy method in the task library policy object. Seethe Tivoli Framework Reference Manual for more information.

c. Type a description of this task in the Description text box.Additional information: This description will appear when you click TaskDescription in the task argument window for this customized task.

d. Optional: Select Show by Identifier to change the Library Contents list touse the task identifier instead of the task name.

e. Click Save & Close to return to the task argument window.7. Click Cancel in the task argument window.8. Click Close in the Execute Task window to return to the Task Library window.9. Click View to display the View drop-down menu.

10. Click Refresh from the View drop-down menu to display the new customizedtask.

Creating a job

ObjectiveTo create a job by defining execution parameters so you can specify a targetenabling you to schedule it to run at certain times in the Scheduler.


Background informationA job is a task with defined and saved arguments that can be executed many timeson specific managed resources. You can create jobs from both standard andcustomized tasks in the product task library. Like tasks, you store jobs in tasklibraries so you can reuse them.



When you finishAfter you create a job, you can run it immediately using the procedure describedin “Running a job” on page 70. You also can schedule jobs to run at certain timesin the Scheduler, as described in “Scheduling a job” on page 71.


Command Line: Use the wcrtjob command to create jobs from the command line.See the Tivoli Management Framework Reference Manual for information about thewcrtjob command.

Tivoli desktop:



window.2. Click Create to display the Create drop-down menu.3. Select Job from the Create drop-down menu to open the Create Job window.4. Type a descriptive job name in the Job Name text box.

Additional information: The job name identifies the icon on the Tivoli desktop.The name can include any alphanumeric character, an underscore (_), dash (–),period (.), or a blank space.

5. Select the task on which the job is based from the Task Name list.6. In the Execution Mode group box, select one of the following check boxes:

ParallelRuns the task simultaneously on all targets. Parallel is typically thefastest method of execution.

Serial Runs the task sequentially on all targets in alphabetical order.

StagedRuns the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you are running thetask on a large number of endpoints. Complete Step 5 to specify theStaging Count (number of targets to run against per stage) and theStaging Interval (number of seconds between each set).

7. In the Execution Parameters group box, type the timeout value (in seconds)for the task in the Timeout text box.


Additional information: This value specifies the number of seconds the productwaits for the task or job to complete before it issues an error. The default is 60seconds. If the task takes longer to complete than the specified Timeout and isrunning in Serial or Staged mode, the product moves on to other endpointsafter this time expires. The task continues to execute on the endpoint, eventhough the product stopped waiting for it to end.

8. Optional: If you selected Staged in Step 6, specify the number of endpoints toinclude in each staged set in the Staging Count text box and the number ofseconds between each set’s startup time in the Staging Interval text box.

9. Select one or more of the following check boxes to choose the output type inthe Output Format group box:

HeaderIncludes a descriptive header for each record.

Return CodeIncludes the programming codes produced when the job executes.

Standard ErrorIncludes all error messages encountered when the job executes.

Standard OutputIncludes all information that results from the job execution.

10. Do one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Tivoli desktop to display the job output on the Tivoli

desktop. Go to Step 12.Additional information: If you choose Display to Desktop, you have anoption, inside the output display window, to save the information to a file.—OR—

v Click Save to File to save the output to a file and open the Destination forTask Output window. Go to Step 11.

11. Do the following in the Destination for Task Output window to save the joboutput to a file:a. Type a Tivoli client endpoint name on which to save the output in the On

Host text box.b. Type the absolute path name for the output file in the Output File text

box.Additional information: Example: /tmp/myjob.out

c. Click Set & Close to set your choices and return to the Create Job window.12. Do one of the following to choose the endpoints on which to run the job:

v Run the job on specific endpoints by doing the following:a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the

Selected Task Endpoints list.–OR–

v Run the job on all subscribers of the specified profile managers by doingthe following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.13. Click Create & Close to create the job and return to the Task Library window.


Additional information: The new job icon appears in the Task Library window.

Running a job

ObjectiveTo execute a job on specific endpoints immediately so you can perform amanagement operation.

Background informationIf you created a job from a standard task, the Tivoli desktop displays the taskargument dialog so that you can fill in any required information.

Jobs created from customized tasks run without further input because all requiredinformation is specified. (See “Customizing a task” on page 66 for informationabout how to create a customized task.)


Before you beginBefore you can run a job, you must create it, as described in “Creating a job” onpage 67.

When you finishAfter you create a job, you can set it up to run on a regular schedule as describedin “Scheduling a job” on page 71.


Command Line: Use the wrunjob command to run jobs from the command line.For more information about this command, see the Tivoli Framework ReferenceManual.

Tivoli desktop:


region icon to display the policy region.c. Double-click the product task icon to open the product task library window.

2. Do one of the following:v Double-click the job icon created from a customized task to begin executing

the job.–OR–

v Double-click the job icon created from a standard task. Go to Step 3.3. Type the values in the task window.

Additional information: For information about specific fields, see the taskdescription in the IBM Tivoli Monitoring for Web Infrastructure Reference Guide orclick Task Description to display the online help. The job runs and displays theoutput on the Tivoli desktop or sends it to a file in accordance with the jobspecification.


Scheduling a job

ObjectiveTo schedule jobs to occur regularly so you can routinely perform managementoperations.

Background informationThe product uses Scheduler to schedule jobs. Scheduler is a service that enablesyou to run jobs unattended. You can schedule a job to run one time or multipletimes. Scheduler notifies you by the manner you select when a job is complete.


Before you beginTo schedule a job, the job must exist in the task library. You create a job byfollowing the procedure described in “Creating a job” on page 67.

When you finishNone


Command Line: Use the wschedjob command to schedule a job in the TaskLibrary from the command line. From the command line, you can only schedulejobs that already exist in the task library. For more information, see the TivoliFramework Reference Manual.

Tivoli desktop:



window.2. Drag the job icon that you want to schedule onto the Scheduler icon located

in the TME Desktop for Administrator <root_admin_name> window on theTivoli desktop.

3. Optional: Do the following if a task argument window opens:a. Type the appropriate information for each field in the dialog.

Additional information: Refer to the task description in the IBM TivoliMonitoring for Web Infrastructure Reference Guide or click Task Descriptionto display the online help for this task.

b. Click Set & Execute to set the task arguments and open the AddScheduled Job window.

4. Type a label for the job icon in the Job Label text box of the Add ScheduledJob window.Additional information: The label identifies the icon on the Tivoli desktop. Thejob label can include alphanumeric character, underscores (_), dashes (–),periods (.), and blanks. If you do not specify a label, the job name is used.

5. Do one of the following:v Select Disable the Job to stop a scheduled job from running.


—OR—v Clear Disable the Job to continue running a scheduled job.

Additional information: For more information on job disabling, see the TivoliManagement Framework User’s Guide.

6. Optional: Type a job description to uniquely identify the job in the Descriptionfield.

7. Set the date and time to begin scheduling in the Schedule Job For group box:a. Type a date in the Month, Day, and Year text boxes.b. Enter the time using the Hour and Minute drop-down lists and the AM

and PM radio buttons.8. Optional: Repeat the job by doing the following in the Repeat the Job group

box:a. Do one of the following:

v Select Repeat the job indefinitely to repeat the job indefinitely.–OR–

v Repeat the job a finite number of times by doing the following:1) Select Repeat the job.2) Type the number of times you want the job to run.

b. Set the interval between start times for the job in the The job should startevery field.

9. Select any of the following check boxes in the When Job Completes groupbox to send job completion notification:v Send a notice to a specific group by doing the following:

a. Select Post Tivoli Notice.b. Click Available Groups to open the Available Groups window.c. Select a group from the list of notice groups.d. Click Set to set your group and return to the Add Scheduled Job

window.

Additional information: You can read notices from the Tivoli desktop byclicking the Notices icon.

v Send a notice to your Tivoli desktop by doing the following:a. Select Post Status Dialog on Tivoli desktop.b. Type the message you want displayed in the text box next to the check

box.v Send an e-mail to a specified user by doing the following:

a. Select the Send e-mail to.b. Type the complete e-mail address in the text box next to the check box.

v Log the job completion status to a file by doing the following:a. Select Log to File.b. Enter the file destination by doing one of the following:

– Type the file destination in the Host and File text boxes. The hostmust be a Tivoli client endpoint and the file must be a fully qualifiedpath name. For example: /tmp/mytask.out–OR–

– Browse for the file destination by doing the following:1) Click File Browser to open the File Browser window.


2) Double-click on a host name to display the directories and filesfor that host.

3) Select a directory and file from the Directories and Files lists.4) Click Set File & Close to return to the Add Scheduled Job

window.10. Optional: Set retry, cancel, or restriction options by doing the following:

a. Click Set Retry/Cancel/Restriction Options to open the Set Retry/CancelRestrictions Options window.

b. Choose one of the following cancel job options:v Clear Cancel job to have the Scheduler continue trying the job

indefinitely.—OR—

v Set the Scheduler to cancel a job in a specified time frame by doing thefollowing:1) Select Cancel job.2) Type the time frame for the Scheduler to wait before canceling a job

that has not started.c. Click one of the following retry options:

v Click Retry the job until success to retry the job until it runssuccessfully.—OR—

v Specify the number of times a job attempts to run by doing thefollowing:1) Select Retry the job.2) Type the number of attempts to start the job in the text box.3) Type the amount of time the Scheduler waits before retrying in the

The job should retry every field.d. Select any of the following check boxes in the Restrictions group box to

specify the job run times:

During the daySet the beginning and ending hour of the day for the job to run.

At nightSet the beginning and ending hour of the night for the job to run.

During the weekSet the beginning and ending day of the week for the job to run.

On weekendsSet the beginning and ending day of the weekend for the job torun.

e. Click Set to set the options and return to the Add Scheduled Job window.11. Click Schedule Job & Close to schedule the job and return to the Tivoli

desktop.


Chapter 8. Enabling Tivoli Enterprise Data Warehouse

This chapter provides information on enabling IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server for Tivoli Enterprise Data Warehouse.

OverviewTivoli Enterprise Data Warehouse enables you to access application reports fromvarious Tivoli and customer applications. The infrastructure provides a set ofextract, transform and load (ETL) utilities that you use to extract and move datafrom Tivoli application data stores to a central data warehouse database.

Tivoli Enterprise Data Warehouse provides the following capabilities:v An open architecture for storing, aggregating, and correlating historical data. In

addition to the data collected by IBM Tivoli software, Tivoli Enterprise DataWarehouse has the flexibility and extensibility to enable you to integrate yourown application data.

v Database optimizations for the efficient storage of large amounts of historicaldata and for fast access to data for analysis and report generation.

v The infrastructure and tools necessary for maintaining and viewing the collecteddata. These include the Tivoli Enterprise Data Warehouse application, IBM DB2Universal Database™ Enterprise Edition, the Data Warehouse Center, DB2Warehouse Manager, and a user interface for creating and viewing reports.

v The ability to use your choice of data analysis tools to examine your historicaldata. In addition to the report interface, you can analyze your data using otherproducts such as online analytical processing (OLAP), planning, trending,analysis, accounting, and data mining tools.

v The ability to control access to your historical data. You can keep data aboutmultiple customers and data centers in one central data warehouse, but restrictaccess so that customers can see and work with data and reports based only ontheir data and not any other customer’s data. You can also restrict an individualuser’s ability to access data.

v A zero-footprint client. Users can access Tivoli Enterprise Data Warehousereports from any system by using a Web browser. No special software isrequired on the user’s system.

v Internationalization support. Not only is the report interface localized,application programmers can localize the data stored in the central datawarehouse.

Tivoli Enterprise Data Warehouse consists of the following components:v Control serverv Central data warehousev Data martsv Report interface

Control serverThe control server contains the control database for Tivoli Enterprise DataWarehouse from which you manage your data warehouse.

75

The control server has these subcomponents:v A server program that controls communication between the control server, the

central data warehouse server, the data mart server, and the report server.v The control database, which contains metadata for Tivoli Enterprise Data

Warehouse.

The control server uses the following parts of the IBM DB2 product, which youmust install manually before installing the control server. These parts are allautomatically installed when you install IBM DB2 Universal Database EnterpriseEdition on a Microsoft Windows system.v DB2 Serverv The Data Warehouse Center, a component that automates data warehouse

processing. You can use the Data Warehouse Center to define the ETL processesthat move and transform data into the central data warehouse and the starschemas used by the data marts. Then, you can use the Data Warehouse Centerto schedule, maintain, and monitor these processes.

v The warehouse agent, part of DB2 Warehouse Manager.

Central data warehouseThe central data warehouse is a DB2 database that contains the historical data foryour enterprise. The system that hosts the central data warehouse is called thecentral data warehouse server. The central data warehouse component uses IBM DB2Universal Database Enterprise Edition, which you must install manually beforeinstalling the control server.

Data martsA separate DB2 database contains the data marts for your enterprise. Each datamart contains a subset of the historical data from the central data warehouse tosatisfy the analysis and reporting needs of a specific department, team, customer,or application. The system that hosts this DB2 database is called the data martserver. Although you can have many data marts, you can have only one data martserver.

The data mart component requires IBM DB2 Universal Database EnterpriseEdition, which you must install manually before installing the control server.

The warehouse pack for IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server creates data marts whose structure is suitable for the reportinterface. They do this by providing an extract, transform, and load (ETL) process,called a data mart ETL, that creates the data mart and loads it with data from thecentral data warehouse.

You can modify an existing data mart, or create new data marts that containslightly different data, to address a reporting need specific to your situation. Tomodify or create a data mart, you must be familiar with database ETL processesand with the internal representation of a data mart as star schemas in the TivoliEnterprise Data Warehouse databases. For information about this, see Enabling anApplication for Tivoli Enterprise Data Warehouse.

Report interfaceThe Tivoli Enterprise Data Warehouse report interface (RPI) provides tools and agraphical user interface that other Tivoli software products use to create anddisplay reports. You can use Tivoli Enterprise Data Warehouse to customize reports


provided with other Tivoli software and to create new reports. You also use thereport interface to control access to data marts and to the reports associated with adata mart. The system on which you install the report interface is called the reportserver.

Use the Work with Reports task group in the report interface to manage users,groups, and data marts for Tivoli Enterprise Data Warehouse or to run, create, andview Tivoli Enterprise Data Warehouse reports.

Working with users and user groupsThis section describes tasks associated with managing user groups for TivoliEnterprise Data Warehouse. It includes the following topics:

Table 9. Guidelines for working with Tivoli Enterprise Data Warehouse users and usergroups


Understand users and user groups “About users and user groups”

Understand Tivoli Enterprise DataWarehouse roles

“The Tivoli Enterprise Data Warehouseroles”

Create an IBM Console user “Creating an IBM Console user” on page 78

Assign roles to a user “Assigning roles to a user” on page 78

Create a user group “Creating a user group” on page 79

Assign users to a user group “Assigning users to a user group” onpage 79

Assign a user group to a data mart “Assigning user groups to a data mart” onpage 80

About users and user groupsYou control access to data in Tivoli Enterprise Data Warehouse data marts byspecifying which user groups (collections of users) can run the reports that accessthe data in each data mart. Each user in a user group is given access to the reportsthe user group can access.

By default, Tivoli Enterprise Data Warehouse provides the TWHAdmin user group,which contains a single user: superadmin. You can customize the TWHAdmin usergroup for the needs of your enterprise.

A user can be assigned to more than one user group.

The Tivoli Enterprise Data Warehouse rolesThe following Tivoli Enterprise Data Warehouse roles control access to tasks andactivities:v Warehouse Security Administrator

With this role, a user can create and manage groups and data marts. A user withthis role controls access to data marts by assigning users to groups and bygiving groups access to specific data marts. In effect, this role controls access tothe Tivoli Enterprise Data Warehouse data using user groups and data marts.

v Report roles control a user’s ability to create and modify reports for the datamarts his user groups can access. Assign only one of the following roles to eachuser:

Chapter 8. Enabling Tivoli Enterprise Data Warehouse 77

– Advanced Report AuthorWith this role, a user can create, modify, run, and delete public and their ownpersonal reports, and save the output of reports, both public and personal.

– Report AuthorWith this role, a user can run and save the output of public and privatereports and create, modify, and delete their own personal reports.

– Report ReaderWith this role, a user can run public reports and view the saved output ofpublic reports.

Creating an IBM Console user

ObjectiveTo create an IBM Console user.

Background informationTivoli Enterprise Data Warehouse is displayed using the IBM Console, which isalso used by other Tivoli software products. A user is given access to tasks in theIBM Console based on the roles that are assigned to that user. One user can haveroles for diverse tasks including administering IBM Console users, managing TivoliEnterprise Data Warehouse user groups and data marts, running and viewing theoutput of Tivoli Enterprise Data Warehouse reports, and performing tasksassociated with other Tivoli software products.

Required authorization rolesuperadmin

Before you beginNone.

When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.

ProcedureTo create an IBM Console user, complete the following steps:1. From the IBM Console, select Administer Users and then Create a User.2. Open the Task Assistant and follow the instructions provided in the online help

to create a user.

Assigning roles to a user

ObjectiveTo assign roles to a user.

Background informationNone.

Required authorization rolesuperuser



When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.

ProcedureTo assign a role to a user, complete the following steps:1. From the IBM Console, select Administer Users and Roles and then Manage

Users.2. From the table of users, click the context menu icon of a user and select

Properties.3. Follow the instructions in the Task Assistant about assigning roles to the user.

Creating a user group

ObjectiveTo create a user group.


Required authorization roleAdministration Authorizations


When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding users to a user group, and deleting a usergroup.

ProcedureTo create a user group, complete the following steps:1. From the IBM console, select Work with Reports and then Manage User

Groups.2. In the Manage User Groups window, click the context menu of Root and select

Create.3. Follow the instructions in the Task Assistant about creating user groups.

Assigning users to a user group

ObjectiveTo assign users to user groups.





When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding or removing users from a user group, anddeleting a user group.

ProcedureTo assign one or more users to a user group, perform the following steps:1. From the IBM Console, select Work with Reports and then Manage User

Groups.2. In the Manage User Groups window, click the context menu icon of a group

and select Properties.3. Follow the instructions in the Task Assistant about assigning users to user

groups.

Assigning user groups to a data mart

ObjectiveTo assign user groups to a data mart.

Background informationGrant access to only those user groups whose users need the data mart to performtasks.



When you finishThe Tivoli Enterprise Data Warehouse online help can guide you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, removing users from a user group, and removing datamart access from a user group.

ProcedureTo assign user groups to a data mart, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Data

Marts.2. In the Manage Data Marts window, in the Data Mart view, click the context

menu icon for the data mart that you want to change and click Properties.3. Select the User Groups tab.4. Open the Task Assistant and follow the instructions provided in the online help

to assign a user group to a data mart.

Managing Tivoli Enterprise Data Warehouse reportsTivoli Enterprise Data Warehouse reports display a static view of the data in a datamart. Reports are provided by the warehouse pack for IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server, along with the data martsrequired to collect the data used in the report.

Tivoli Enterprise Data Warehouse provides three types of reports, which contain astatic view of your data:


Extreme caseAn extreme case report is a ″one measurement versus many components orgroups of components″ report that displays the worst or best n cases. Thisreport displays a maximum of 25 cases.

Health checkA health check report displays status and performance for a specifiedmeasurement over a period of time. The data in a health check report isaggregated at the application server level.

SummaryA summary report displays the overall status of the resource models. Thedata in a summary report is aggregated at the application server level andis grouped by operating system, node, and application server.

This section describes the following tasks:

Table 10. Guidelines for working with Tivoli Enterprise Data Warehouse reports


Run a report “Running reports” on page 84

Schedule a report to run automatically “Scheduling reports to run automatically” onpage 85

Modify the default settings of a report “Modifying default settings for reports” onpage 86

Create a custom report “Creating reports” on page 87

For more information about working with reports, see the Tivoli Enterprise DataWarehouse online help.

Tivoli software products using the Tivoli Enterprise Data Warehouse can provideprepackaged reports that enable you to access specific information about yourbusiness environment. All of these reports are listed in the Manage Reports andReport Output task of the Work with Reports task group in the IBM Console. Thisincludes reports from all Tivoli software products that use the Tivoli EnterpriseData Warehouse report interface. Tivoli software products can also provide adifferent reporting interface.

A Tivoli Enterprise Data Warehouse report uses data from a single data mart.

If you have the appropriate role, you can also create additional reports or modifyexisting reports. Before you can create a new report or modify an existing report,you must understand the structure of the underlying warehouse data and of theoperational data that is the source of that data. For information about the structureof data in the data mart and in the central data warehouse, see Enabling anApplication for Tivoli Enterprise Data Warehouse.

For information about any problems that might occur, see the ″Troubleshooting″chapter in the Installing and Configuring Tivoli Enterprise Data Warehouse, Version 1,Release 1.

IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server star schemas, data marts, and reports

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Servercontains the following Tivoli Enterprise Data Warehouse star schemas, data marts,and reports.


For detailed information on the specific data mart, star schema, and reportmapping of IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer, see the IBM Tivoli Monitoring for Web Infrastructure: WebSphere ApplicationServer Warehouse Enablement Pack Implementation Guide located in the doc directoryof IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application ServerInstallation CD.

Star schemasstar schema is a set of three or more data tables.

IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides the following star schemas:

IZY Hourly Administration Server Star SchemaStar schema with dimension tables associated with the hourly fact table forthe IBM WebSphere Administration server components.

IZY Daily Administration Server Star SchemaStar schema with dimension tables associated with the daily fact table forthe IBM WebSphere Administration server components.

IZY Weekly Administration Server Star SchemaStar schema with dimension tables associated with the weekly fact table forthe IBM WebSphere Administration server components.

IZY Monthly Administration Server Star SchemaStar schema with dimension tables associated with the monthly fact tablefor the IBM WebSphere Administration server components.

IZY Hourly Application Server Star SchemaStar schema with dimension tables associated with the hourly fact table forthe IBM WebSphere application servers.

IZY Daily Application Server Star SchemaStar schema with dimension tables associated with the daily fact table forthe IBM WebSphere application servers.

IZY Weekly Application Server Star SchemaStar schema with dimension tables associated with the weekly fact table forthe IBM WebSphere application servers.

IZY Monthly Application Server Star SchemaStar schema with dimension tables associated with the monthly fact tablefor the IBM WebSphere application servers.

IZY Hourly Application Server Component Star SchemaStar schema with dimension tables associated with the hourly fact table forthe IBM WebSphere application server components, such as data sources,EJBs, JVMs, web applications, thread pools, servlet sessions, andtransaction managers.

IZY Daily Application Server Component Star SchemaStar schema with dimension tables associated with the daily fact table forthe IBM WebSphere application server components, such as data sources,EJBs, JVMs, web applications, thread pools, servlet sessions, andtransaction managers.

IZY Weekly Application Server Component Star SchemaStar schema with dimension tables associated with the weekly fact table forthe IBM WebSphere application server components, such as data sources,EJBs, JVMs, web applications, thread pools, servlet sessions, andtransaction managers.


IZY Monthly Application Server Component Star SchemaStar schema with dimension tables associated with the monthly fact tablefor the IBM WebSphere application server components, such as datasources, EJBs, JVMs, web applications, thread pools, servlet sessions, andtransaction managers.

IZY Hourly Application Server Subcomponent SchemaStar schema with dimension tables associated with the hourly fact table forthe IBM WebSphere application server subcomponents, such as connectionpools and servlets.

IZY Daily Application Server Subcomponent SchemaStar schema with dimension tables associated with the daily fact table forthe IBM WebSphere application server subcomponents, such as connectionpools and servlets.

IZY Weekly Application Server Subcomponent SchemaStar schema with dimension tables associated with the weekly fact table forthe IBM WebSphere application server subcomponents, such as connectionpools and servlets.

IZY Monthly Application Server Subcomponent SchemaStar schema with dimension tables associated with the monthly fact tablefor the IBM WebSphere application server subcomponents, such asconnection pools and servlets.

Data marts and reportsThis warehouse pack provides one data mart: IZY Monitoring for WebSphereApplication Server.

This data mart uses the following star schemas:v IZY Hourly Administration Server Schemav IZY Daily Administration Server Schemav IZY Weekly Administration Server Schemav IZY Monthly Administration Server Schemav IZY Hourly Application Server Schemav IZY Daily Application Server Schemav IZY Weekly Application Server Schemav IZY Monthly Application Server Schemav IZY Hourly Application Server Component Schemav IZY Daily Application Server Component Schemav IZY Weekly Application Server Component Schemav IZY Monthly Application Server Component Schemav IZY Hourly Application Server Subcomponent Schemav IZY Daily Application Server Subcomponent Schemav IZY Weekly Application Server Subcomponent Schemav IZY Monthly Application Server Subcomponent Schema

IZY Monitoring for WebSphere Application Server provides the followingprepackaged reports:

IZY EJBs with the Most HitsThis extreme case shows the top 25 EJBs with the highest weekly averagetotal requests.


IZY Servlets with the Highest Response TimeThis extreme report shows the top 25 servlets with the highest weeklyaverage response time.

IZY Servlets with the Most HitsThis extreme report show the top 25 servlets with the highest weeklyaverage total requests.

IZY EJB Performance HealthThis health check report compares the performance (Method ResponseTime), load (Concurrent Active) and throughput (Total Requests),aggregated for the application server.

IZY Servlet Performance HealthThis health check report compares the performance (Servlet ResponseTime), load (Concurrent Requests), and throughput (Servlet Requests),aggregated for the application server.

IZY Enterprise JavaBean Resource Model SummaryThis summary report examines the minimum, maximum, average and totalvalues, as applicable, for Enterprise JavaBean resource modelmeasurements grouped by operating system, node and application server.

IZY JVM Runtime Resource Model SummaryThis summary examines the minimum, maximum, average and totalvalues, as applicable, for all JVM Runtime resource model measurementsgrouped by operating system, node and application server.

IZY Transaction Manager Resource Model SummaryThis summary examines the minimum, maximum, average and totalvalues, as applicable, for transaction manager resource modelmeasurements grouped by operating system, node and application server.

IZY Web Application Resource Model SummaryThis summary examines the minimum, maximum, average and totalvalues, as applicable, for Web Application resource model measurementsgrouped by operating system, node and application server.

IZY Servlet Session Resource Model SummaryThis summary examines the minimum, maximum, average and totalvalues, as applicable, for servlet session resource model measurementsgrouped by operating system, node and application server.

Running reports

ObjectiveTo run a report using the report interface.


Required authorization roleAdvRepAuthRole, RepAuthRole, or RepReaderRole


When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as displaying the properties of a report,


modifying the settings, and deleting a report. Also see “Modifying default settingsfor reports” on page 86 for information about customizing the reports.

ProcedureTo run a report using the report interface, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Reports

and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

the context menu icon of a report and select Run.3. For more information about running reports, see the online help in the Task

Assistant. The online help can also help guide you through additional tasks forreports, such as displaying the properties of a report and deleting a report.

Scheduling reports to run automatically

ObjectiveTo automatically run reports.

Background informationUsing the Tivoli Enterprise Data Warehouse report interface, you can schedule areport to run automatically when the associated data mart is updated. This ensuresthat when you examine the output of the report, it displays the most recent data inthe warehouse.

Required authorization roleAdvRepAuthRole


When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureTo schedule a report to run automatically when the associated data mart isupdated, complete the following steps:1. From the IBM Console, select Work with Reports and then Manage Reports

and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

Reports.3. Click the context menu icon of a report and select Properties.4. Select the Schedule tab.5. In the Schedule window, select Run the report when the data mart is built.6. Click OK.

For more information about automatically running reports, see the online help inthe Task Assistant. The online help can also guide you through additional tasksfor reports, such as modifying or displaying the properties of a report and deletinga report.


Modifying default settings for reports

ObjectiveTo modify default settings for report creation.

Background informationWhen you create or modify a report, you select predetermined values for the timeframe of the report. The predetermined values of Peak Hours and Weekdaysspecified under Filtering in the Time page of report properties can be modified. Dothis by modifying the information in the control database on the control server.

The default value for Peak Hours is 9:00 am through 5:00 PM, or 0900 to 1700. Thisvalue can be modified to reflect different peak hours if necessary.

The default value for Weekdays is Monday through Friday. This value can also bemodified.

The RPI.TimeFilters table contains the following filters and default filter values.

Table 11. Default time filter names and values

TIME_FILTER_NAME TIME_FILTER_VALUES

Peak hours hour(meas_hour) in (9,10,11,12,13,14,15,16,17)

Weekdays dayofweek(meas_date) between 2 and 6

Required authorization roleAdvRepAuthRole


When you finishFor additional information on the properties of the RPI.TimeFilters table, seeEnabling an Application for Tivoli Enterprise Data Warehouse.

ProcedureTo change the values displayed in the report interface, perform the following steps:1. Connect to the control database (TWH_MD).2. Use an SQL statement similar to the following to modify the values for Peak

Hours or Weekdays in the RPI.TimeFilters table. The following example sets theWeekdays filter to represent Sunday through Thursday:

Update RPI.TimeFilters set TIME_FILTER_VALUES =dayofweek(meas_date) between 1 and 5where TIME_FILTER_NAME =Weekdays

After doing this, when a user selects a Weekdays filter for a report in the reportinterface, the data returned is for Sunday through Thursday.

Note: There is no error-checking for the values inserted into the tables for PeakHours and Weekdays. Therefore, ensure that the information you insert intothe tables is correct. You can save a report that contains incorrect values forthese parameters without receiving an error message. The message is notgenerated until the report is run.


Creating reports

ObjectiveTo create a report.


Required authorization roleAdvRepAuthRole or RepAuthRole

Before you beginEnsure that you use descriptive and meaningful names for the reports you create.Report names are unique across all users of Tivoli Enterprise Data Warehouse.

When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureYou can perform this procedure from the IBM Console.1. Click Work with Reports and select Create a Report.2. Select one of the following type of reports to create: Extreme Case, Health

Check, and Summary.3. Select the data mart that contains the information from which to create the

report.4. Click OK.5. Click the General tab and enter the Name and Description for the report.6. Click the Metrics tab, and select Add to add a new metric to graph and

display the Add Metrics screen.7. Select the star schema containing the metric that you would like to graph and

to display a list of available metrics for the star schema.8. Check one or more of the metrics that you would like to graph.9. Click Next.

10. Select the aggregation type that you would like for each metric.11. Click Next.12. Specify the attributes to filter by, group by, or order by.13. Click the Time tab, and specify the Time frame for which you would like to

run the report.Additional information: You can either specify a General Time Frame, such asthe Last 7 days, or a Specific Time Interval, such as January 1, 2002 throughJanuary 31, 2002.

14. Click the Schedule tab, and select whether the report should be run when thedata mart is built.

15. Click OK.


Appendix A. Task authorization roles quick reference

Table 12 lists the minimum required authorization roles for the tasks. Forinformation about these IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server authorization roles, see “Setting authorization roles” on page 12.

Table 12. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server taskauthorization roles

Task name Minimum authorization role

Event tasks

Configure_Event_Server super

Configure_WebSphere_TEC_Adapter websphereappsvr_admin

Display_WebSphere_TEC_Adapter_Configuration websphereappsvr_user

Start_WebSphere_TEC_Adapter websphereappsvr_admin

Stop_WebSphere_TEC_Adapter websphereappsvr_admin

Administrative server tasks

Check_Administration_Server_Status websphereappsvr_user

List_Application_Servers websphereappsvr_user

Start_Administration_Server websphereappsvr_admin

Stop_Administration_Server websphereappsvr_admin

Application server tasks

Check_Application_Server_Status websphereappsvr_user

Start_Application_Server websphereappsvr_admin

Stop_Application_Server websphereappsvr_admin

Utility tasks

Delete_Trace_Logs websphereappsvr_admin

Discover_WebSphere_Resources websphereappsvr_super

List_Trace_Logs websphereappsvr_user

Send_WebSphere_Discovery_Events_to_TBSM websphereappsvr_admin

89

Appendix B. Task quick reference

A task is an operation or set of operations that is performed routinely. Thefollowing table lists the IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server tasks alphabetically. For more information about this tasks, seethe IBM Tivoli Monitoring for Web Infrastructure Reference Guide.

The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Servertasks are grouped into the following task libraries:

Table 13. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server task libraries

Task name Description

WebSphere Event Tasks

Configure_Event_Server Configures an event server for IBM TivoliMonitoring for Web Infrastructure: WebSphereApplication Server and imports the TivoliBusiness Systems Manager rules, if appropriate.

Configure_WebSphere_TEC_Adapter Configures and starts the IBM WebSphereApplication Server Tivoli Enterprise Consoleadapter. The adapter is used to forward IBMWebSphere FATAL, ERROR, AUDIT, WARNING,and TERMINATE messages (SeriousEvents) to theTivoli Enterprise Console.

Display_WebSphere_TEC_Adapter_Configuration Displays the configuration settings for the IBMWebSphere Application Server Tivoli EnterpriseConsole adapter.

Start_WebSphere_TEC_Adapter Starts the IBM WebSphere Application ServerTivoli Enterprise Console adapter, which isneeded to forward IBM WebSphere ApplicationServer events and Tivoli Enterprise Consoleadapter events to the Tivoli Enterprise Consoleand Tivoli Business Systems Manager.

Stop_WebSphere_TEC_Adapter Stops the IBM WebSphere Application ServerTivoli Enterprise Console adapter.

WebSphere Administration Server Tasks

Check_Administration_Server_Status Displays the status of the IBM WebSphereadministration server.

List_Application_Servers Lists the IBM WebSphere application serverscurrently defined for an IBM WebSphereadministration server.

Start_Administration_Server Starts the IBM WebSphere administration server.

Stop_Administration_Server Stops the IBM WebSphere administration server.

WebSphere Application Server Tasks

Check_Application_Server_Status Displays the status of the IBM WebSphereapplication server.

Start_Application_Server Starts a IBM WebSphere application server.

Stop_Application_Server Stops a IBM WebSphere application server.

WebSphere Utility Tasks

91

Table 13. IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server task libraries (continued)

Task name Description

Delete_Trace_Logs Deletes all IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server tracelogs on the selected endpoint or managed node.

Discover_WebSphere_Resources Discovers the IBM WebSphere administration andapplication server resources that can be managedusing IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server.

List_Trace_Logs Returns a list of IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server tracelogs on the specified endpoint or managed node.

Send_WebSphere_Discovery_Events_to_TBSM Sends a DISCOVER event to Tivoli BusinessSystems Manager for each IBM WebSphereadministration server and application server thatIBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server is currentlymanaging. For any resources that have beenremoved since the last time this task was run, thistask sends a GONE event to Tivoli BusinessSystems Manager.


Appendix C. Setting up IBM Tivoli Monitoring

During installation, IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server performs several tasks that help to set up your IBM TivoliMonitoring environment, including creating profile managers, adding resources tothe profiles, and adding resource models to profiles. The following profilemanagers are created during installation:v WebSphere Administration Serversv WebSphere Application Serversv WebSphere Application Servers with EJBsv WebSphere Application Servers with Servlets

This appendix provides procedures to create additional profile managers orcustomize the resources or resource models assigned to your profile manager.

Table 14 provides guidelines for the order in which you set up monitoringinformation and the required procedures for setting up IBM Tivoli Monitoring.

Note: For additional or advanced information on IBM Tivoli Monitoring in theTivoli environment, see the IBM Tivoli Monitoring User’s Guide.

Table 14. Monitoring resources and applications guidelines

Goal See

1. Set up profile managers and profiles toorganize your resource models. This makesthe distribution of resource models moreefficient. You might need to set up multipleprofile managers and profiles within theprofile managers to meet the needs of yourenvironment.

“Creating profile managers andprofiles” on page 94

2. Subscribe endpoints to the profile manager.This determines which resources receive aprofile when the profile is distributed.Profiles contain resource models to runagainst the endpoints (see Step 3).

“Subscribing resources to profilemanagers” on page 96

3. Populate each profile manager/profile withresource models for the resource that youwant to monitor. Include resource modelswith the default values or customize thedefault values to meet the needs of yourenvironment.

“Adding default resource modelsto profiles” on page 96

“Adding customized resourcemodels to profiles” on page 97

93

Table 14. Monitoring resources and applications guidelines (continued)

Goal See

4. For each resource model in your profile, dothe following:

v Determine how the resource modelgenerates an event by specifyingthresholds, occurrences, and holes for eachindication for that resource model.

v Specify if you want corrective or reportingtasks for an event.

v Specify if you want to receive informationon a specific event through a notice.

v Specify when the monitoring occurs.

v Specify if you want the collected log datawritten to a local database.

“Modifying indications” on page42

“Specifying tasks for an indication”on page 44

“Sending a notice to administratorswhen an event occurs” on page 45

“Creating scheduling rules” onpage 46

“Modifying data logging settings”on page 48

5. For each profile in your profile manager, dothe following:

v Specify the subscribers that you want todistribute the monitoring profile to anddistribute the profile.

v Specify the subscribers that you want todistribute the monitoring profile to whileusing MDist2.

“Distributing profiles from theTivoli desktop” on page 21

“Distributing profiles usingMDist2” on page 23

Creating profile managers and profiles

ObjectiveTo create profile managers and profiles so you can organize and distribute yourresource models more efficiently.

Background informationA monitoring profile is a group of defined resource models that you can distribute toa subscribed managed resource in a profile manager.

In addition to activating default resource models, profile managers and profiles cangroup resources to enable simultaneous monitoring of multiple resources. You canhierarchically organize the profile managers. The profile manager is the top level ofthe organization and contains specific profiles that contain specific resourcemodels. Instances are then subscribed to the profile managers, which enable themonitoring information to be channeled to those resources.

You can create an unlimited number of profile managers, but it is recommendedthat they reflect some logical or functional grouping of resources or the business’sorganizational structure. For example, profile managers could be labeled Sales andMarketing, Administration and Finance, and Operations to reflect a businessorganization.

For more information about profile managers, including the different types (suchas dataless), see the Tivoli Management Framework documentation.



Before you beginSet up the Tmw2kProfile managed resource types. Refer to the IBM TivoliMonitoring User’s Guide for information.

When you finishAdd resource models to the profile. See “Adding default resource models toprofiles” on page 96 or “Adding customized resource models to profiles” onpage 97.


Command Line:

1. Use the wcrtprfmgr command to create a profile manager. For example, tocreate a profile manager called ″ProfMgr2″ in the TestRegion policy region,enter the following command:wcrtprfmgr @PolicyRegion:TestRegion ProfMgr2

2. Optional: Use the wsetpm command to make the policy manager operate indataless mode. For example, to make the profile manager ProfMgr2 dataless,enter the following command:wsetpm -d @ProfileManager:ProfMgr2

where:

-d Specifies that the profile manager operates in a dataless mode.3. Use the wcrtprf command to create a profile. For example, to create a profile

called ″MarketingProf2″ in the ProfMgr2 profile manager, enter the followingcommand:wcrtprf @ProfileManager:ProfMgr2 MarketingProfile MarketingProf2

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual.

Tivoli desktop:

1. Open the Policy Region window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.

2. Select Create → Profile Manager to open the Create Profile Manager window.3. Type a unique name in the Name/Icon Label text box.4. Click Create & Close.5. Double-click the profile manager icon to open the Profile Manager window.6. Select Create → Profile to open the Create Profile window.7. Type a unique name for the profile in the Name/Icon text box.8. Select the Tmw2kProfile resource from the Type list.9. Click Create & Close. An icon for the new profile is displayed in the Profiles

area of the Profile Manager window.

Appendix C. Setting up IBM Tivoli Monitoring 95

Subscribing resources to profile managers

ObjectiveTo add managed resources to a monitoring profile so administrators can definewhich resource to monitor.

Background informationSubscribing resources to a profile manager determines which resources receive aprofile when the profile is distributed. IBM Tivoli Monitoring uses the list ofsubscribers to determine which systems are monitored. To add a subscriber to adistributed monitoring profile, you must add the subscriber to the profile manager.

Note: Resources can also be subscribed to profiles from the IBM Tivoli MonitoringProfile window. See “Distributing profiles from the Tivoli desktop” onpage 21.


Before you beginCreate a monitoring profile with monitoring sources. See “Creating profilemanagers and profiles” on page 94 for information.

When you finishDistribute the monitoring profile to the subscribed resource. See “Distributingprofiles from the Tivoli desktop” on page 21 for information.


Command Line: Use the wsub command to add subscribers to the profilemanager. For example, to add a database called ″Sample@bburns″ as a subscriberto the profile manager DatabaseMonitors, enter the following command:wsub @ProfileManager:DatabaseMonitors @PolicyRegionName:Sample@bburns

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual.

Tivoli desktop:

1. Open the Policy Region window.2. Double-click a profile manager icon to open the Profile Manager window.3. Select Profile Manager → Subscribers.4. Select the subscribers to receive the profile distribution from the Available to

become Subscribers scrolling list.5. Click the left-arrow button to move the selected subscribers to the Current

Subscribers scrolling list.6. Click Set Subscriptions & Close to add the subscribers. Subscribers are

displayed in the Subscribers field of the Profile Manager window.

Adding default resource models to profiles

ObjectiveTo add a resource model to a profile using its default values so you can run theresource model immediately.


Background informationA resource model captures and returns information about a resource or application.You set up resource models and distribute them to endpoints. Each resource modelmonitors multiple resources. Choose the resource models to add to a profile basedon the resources you want to monitor. Adding one or more of these resourcemodels to a profile enables you to begin monitoring resources immediately.

Put all of the resource models that you are going to distribute to the sameendpoint in a single profile because the distribution occurs on a per-profile basis.




managers” on page 96 for information.

When you finishDistribute the profile. See “Distributing profiles from the Tivoli desktop” onpage 21.


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile. For more information, see the IBM Tivoli Monitoring for WebInfrastructure, Version 5.1.0: WebSphere Application Server Reference Guide.

Desktop:

1. Open the IBM Tivoli Monitoring Profile window.2. Click Add With Defaults to open the Add Resource Models to Profile

window.3. Select the resource model category from the Category drop-down list.4. Select the resource model you want from the Resource Model drop-down list.5. Click Add & Close. The resource model is added to the IBM Tivoli Monitoring

Profile.

Adding customized resource models to profiles

ObjectiveTo add a resource model with customized settings so that admins and users canspecify the relevant type of platform, cycle time, and threshold values that meetthe needs of your environment and add the resource model to a profile.

Background informationResource models are set up and distributed to IBM WebSphere Application Serverobjects. In addition to using the predefined resource models that are installed withthe product, you can customize the predefined resource models. Each resourcemodel monitors a different resource. Choose the resource models that you want tocustomize and the setting you want to use to monitor those resources.





managers” on page 96 for information.

When you finishDistribute the profile. See “Distributing profiles from the Tivoli desktop” onpage 21.


Command Line: Use the wdmeditprf command to add a customized resourcemodel to a profile. For more information, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile window.2. Click Add to open the Add Resource Models to Profile window.3. Select the resource model category from the Category drop-down list.4. Select the desired resource model from the Resource Model drop-down list.5. Set the frequency with which the resource model monitors the data in the

Cycle Time text box. Enter a time in seconds.6. Use the following steps to change any of the threshold values:

a. Select the Threshold Name that you want to change.Additional Information: The description box displays a description of thethreshold that you selected. A dialog box above the description displays thecurrently assigned threshold value. For the default threshold values, see theIBM Tivoli Monitoring for Web Infrastructure Reference Guide.

b. Change the currently assigned threshold value to a value appropriate toyour requirements.

c. Click Apply to set and display the new value in the Threshold Valuewindow.

7. Optional: Click Indications or Parameters to make required modifications toindications and parameters and click Schedule to add schedule information.Additional information: If you do not perform this step, the indications andparameters use the default values shipped with the resource models. See“Modifying indications” on page 42 and “Creating scheduling rules” on page 46for information.

8. Click Add & Close to save your changes. The IBM Tivoli Monitoring Profilewindow now shows the customized resource model.

Rerunning failed profile distributions

ObjectiveTo verify that the distribution to an endpoint failed so that you can rerun thedistribution for the failed endpoint.


Background informationWhen a distribution fails, IBM Tivoli Monitoring creates a profile manager thatcontains the endpoint subscribers that failed.

When you successfully redistribute profiles, the software deletes the profilemanager that it created for the failed distribution. A wholly or partiallyunsuccessful redistribution retains the profile manager containing only thesubscribers that were unsuccessful in the redistribution. Continue the process ofcorrecting the errors and retrying the distribution until the profile is successfullydistrubted to all endpoints.



When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.

Tivoli desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following::a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.

2. Select View → Refresh from the Policy Region dialog box to see the new profilemanagers.

3. Review the new profile manager names to determine and correct the cause ofthe failure. The following profile manager names are derived from a faileddistribution:v The failed distribution creates the following profile manager name due to a

Bad_Interpreter error:OriginalProfileName_Push_Failed_Bad_Interpreter

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

The AMW089E error message is displayed at this point, indicatingthat the resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX-T endpoint.

v The failed distribution creates the following profile manager name due toany other error:OriginalProfileName_Distribution_Failed

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.


4. Subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile.

Note: This can be done only if the profile manager used for the originaldistribution was not a dataless endpoint.

5. Distribute the original profile to the failed endpoints by selecting these profilemanagers as the target for the distribution. You can also edit the profilemanagers to delete an endpoint from a group of failed endpoints beforeretrying the distribution.


Appendix D. Creating custom resource models

This section briefly describes how you can use the Resource Model Wizard tocreate your own resource models using the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server common information model (CIM)classes. Refer to the IBM Tivoli Monitoring Workbench documentation for moreinformation on how to create resource models.

For information about the IBM Tivoli Monitoring for Web Infrastructure:WebSphere Application Server CIM classes, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

The following topics are discussed in this section:

Table 15. Guidelines for creating custom resource models


Create a custom resource model that usesthe IBM Tivoli Monitoring for WebInfrastructure: WebSphere ApplicationServer CIM classes.

“Creating custom resource models using theIBM Tivoli Monitoring Workbench”

Enable Java Virtual Machine ProfilerInterface (JVMPI) data reporting to collectperformance data

“Enabling JVMPI data reporting” onpage 103

Creating custom resource models using the IBM Tivoli MonitoringWorkbench

ObjectiveTo create customized resource models in the IBM Tivoli Monitoring Workbenchusing IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application ServerCIM classes and use the Resource Model Wizard to guide you through the process.

Background informationThe IBM Tivoli Monitoring Workbench is a programming tool for creating,modifying, debugging, and packaging resource models for use with IBM TivoliMonitoring products. Samples of the ″best practice″ resource models have beenprovided for you to use within the IBM Tivoli Monitoring Workbench. The sampleresource models are intended to be used as working examples for creating newresource models. Also, you can use the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server ″best practice″ resource models asexamples.

The Tivoli Maintenance and Support Contract covers assistance with problemsrelating to the operation of the IBM Tivoli Monitoring Workbench, but does notcover assistance for new or modified resource models other than the ones that areincluded in the IBM Tivoli Monitoring Workbench.

The Resource Model Wizard guides you through the process of creating resourcemodels using IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server CIM classes. For information about the IBM Tivoli Monitoring

101

for Web Infrastructure: WebSphere Application Server CIM classes, see the IBMTivoli Monitoring for Web Infrastructure Reference Guide.

Refer to the IBM Tivoli Monitoring Workbench documentation for moreinformation on how to create resource models.


Before you beginBefore you begin, you must perform the following steps:1. Install and configure Windows Management Instrumentation.

Additional Information: You can download Windows ManagementInstrumentation (WMI) from http://msdn.microsoft.com/downloads/. WMI isalready installed on Windows 2000 systems.

2. Install and configure IBM Tivoli Monitoring Workbench.3. Load each CIM class you want to use.

Additional Information: Load the classes by running the mofcomp commandfrom the Workbench/w32–ix86 directory on the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server installation CD. For moreinformation about the mofcomp command, refer to the Windows ManagementInstrumentation documentation.See the IBM Tivoli Monitoring for Web Infrastructure Installation and Setup Guidefor more information on loading these files.

When you finishRefer to IBM Tivoli Monitoring Workbench documentation for instructions on howto build and deploy your new resource model. Resource models created to use theIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server CIMclasses need to be distributed to the WSAdministrationServer orWSApplicationServer objects.

Procedure1. From the IBM Tivoli Monitoring Workbench, click File → New.2. Select Java Script Resource Model and click OK.3. Select Resource Model Wizard and click OK.4. Select the CIM/WMI data source type.5. Select all of the available operating systems on which you want the resource

model to run.6. Click Next.7. Type ″root\Cimv2″ in the Connect to namespace field.

Additional Information: ″\root\Cimv2″ refers to the namespace in the classrepository that includes resource model information.

8. Optional: Type your password.9. Click OK to display the Select a Class window.

Additional Information: The Selected Class field displays all available CIMclasses for use in your custom resource models.

10. Select the CIM class properties to monitor from the Available Propertiesgroup box.

11. Select one or more CIM classes.


http://msdn.microsoft.com/downloads/

Additional information: For information about the IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server CIM classes, see the IBMTivoli Monitoring for Web Infrastructure Reference Guide.

12. Click Next.13. Follow the Resource Model Wizard instructions to complete your resource

model. See the IBM Tivoli Monitoring Workbench documentation for detailedinstructions.

14. After the wizard is complete, add the CIM classes as platform-specificdependencies to the resource model by doing the following:a. Open the IBM Tivoli Monitoring Workbench dialog box containing the

decision tree SCRIPT.b. In the tree on the left side of the window, click ″+″ to expand the tree list

for the newly created resource model.c. Click ″+″ to the left of Dependencies to expand the Dependencies tree.d. Right-click on a platform-specific dependency element to display the Add

pop-up menu.e. Click Add to display the Open dialog box.f. For the Look in field, scroll to select the IBM Tivoli Monitoring for Web

Infrastructure installation CD.g. Click one of the following directories for the operating system on which

the resource models will run:v Windows: Workbench/w32–ix86.

—OR—v UNIX (including Linux-ix86, aix4–r1, HP–UX10, solaris2):

Workbench/UNIX.h. Select the appropriate .mof file and then click Open to add the classes to

the Dependencies folder.i. Repeat steps 14d to 14h for the All dependency element. Click the

following directory to select the data provider code that whill be used bythe resource model: WORKBENCH|ALL. Both of the .jar files in thisdirectory should be added as dependencies to all IBM Tivoli Monitoring forWeb Infrastructure: WebSphere Application Server resource models.

Enabling JVMPI data reporting

ObjectiveTo enable the Java Virtual Machine Profiler Interface (JVMPI) to improveperformance analysis.

Background informationIBM WebSphere Application Server includes a Resource Analyzer that retrievesperformance data by periodically polling the administrative server. The ResourceAnalyzer provides a range of performance data for two kinds of resources:WebSphere resources, such as enterprise beans and servlets, and runtime resources,such as Java Virtual Machine (JVM) memory application server thread pools anddatabase connection pools.

You do not need to enable JVMPI data reporting to use the resource modelsincluded with IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server. However, you can use the CIM classes to create customresource models to collect this information. See “Creating custom resource modelsusing the IBM Tivoli Monitoring Workbench” on page 101 for more information.

Appendix D. Creating custom resource models 103

The Resource Analyzer uses a Java Virtual Machine Profiler Interface (JVMPI) toretrieve information, such as garbage collection, about the JVMs that run on theapplication server. JVMPI is a two-way function call interface between the JVMand an in-process profiler agent. The JVM notifies the profiler agent of variousevents, such as heap allocations and thread starts. The profiler agent can activateor inactivate specific event notifications based on the needs of the profiler.

The JVMPI is available on the Windows, AIX, and Solaris platforms.

Required authorization roleNo Tivoli role is required.

Before you beginEnable performance monitoring on your systems. See “Enabling performancemonitoring” on page 15 for more information.

When you finishCreate a custom resource model to collect this information. See “Creating customresource models using the IBM Tivoli Monitoring Workbench” on page 101 formore information.

ProcedureDo the following on the IBM WebSphere Application Server AdministrativeConsole to enable JVMPI data reporting:1. Right-click the application server in the hierarchical tree located in the left pane

of the Administrative Console.2. Click Properties in the pop-up menu. The Properties notebook is displayed.3. Click the JVM Settings tab.4. Click Advanced JVM Settings on the bottom left of the JVM Settings page. The

Advanced JVM Settings page is displayed.5. Type the following case-sensitive command in the Command line arguments

field:-XrunpmiJvmpiProfiler

6. Click OK.7. Start or restart the application server.


Appendix E. Event classes and rules

This appendix contains information about the Tivoli Enterprise Console eventclasses and rules that IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server provides. The following topics are discussed in this appendix:v “Event classes”v “Rules for resource models”v “Rules for events”

Event classesIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides a set of Tivoli Enterprise Console event classes.v WebSphereAS_Monitor_Event

Events for these classes are generated by the resource models.v ITMWAS_Eventv ITMWAS_TEC_Adapter_Event

These event classes are generated by the WebSphere TEC adapter.

Rules for resource modelsIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverprovides rules for events generated by resource models. The rules are contained inthe itmwas_monitors.rls file. The rules and their functions are as follows:

dup_monitor_wasSearches for and closes duplicate events generated by the resource models.

timeharmless_monitor_wasSets a 15 minute timer for each Harmless event.

closeharmless_monitor_wasCloses the Harmless event when the 15 minute timer has expired.

waspac_tmw_clearingCorrelates and closes the original status change event associated with thisclearing event.

Rules for eventsIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serversupplies a set of rules that provide correlation of related events. Theitmwas_forward_tbsm.rls and itmwas_events.rls files contain the set of rules. Theserule sets use the classes from the itmwas_dm_events.baroc anditmwas_events.baroc files.

The rules and their functions are as follows:

forward_itmwas_event_to_tbsm:Forwards events to Tivoli Business Systems Manager.

forward_itmwas_clearing_event_to_tbsmForwards clearing events to Tivoli Business Systems Manager.

105

dup_wasSearches for and closes duplicate events generated by IBM WebSphereApplication Server.

dup_tec_adapter_wasSearches for and closes duplicate events generated by the Tivoli EnterpriseConsole adapter.

timeharmless_wasSets a 15 minute timer for each Harmless event.

closeharmless_wasCloses the Harmless event when the 15 minute timer has expired.

status_change_wasCloses previous status change events generated by the Tivoli EnterpriseConsole adapter.


Appendix F. Problem determination

This appendix provides information about resolving problems that might occurwhen you run IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server. Problems can be caused by the following things:v Machine or server availabilityv Operating system environmentv IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Server

configuration

Possible problems and workaroundsThe following sections describe problems that might occur and providesworkarounds or fixes for those problems.

General problem determinationTable 16. General problems and solutions

Problem Solution

You might see messages related to missingdependencies, such as patches, even though youhave all the required dependencies installed. Themessage also might state that a required filecannot be found.

This can occur if you install required dependencies (such asTivoli Enterprise Console) or patches to the requireddependencies after installing IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server. To fix this, run thefollowing script:

$BINDIR/../generic_unix/TME/WSAPPSVR/itmwas_tool_dep.sh

Note: On Windows systems, you must run this script from thebash shell.

107

Tivoli Enterprise Console problem determinationTable 17. Tivoli Enterprise Console problems and solutions

Problem Solution

Events are not displayed in the event console. Check the following:

v Ensure that the event server is operational.

v Ensure that the event adapter is running.

v Ensure that the IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server classesand rules are installed and configured on the eventserver.

1. Run the wlscurrb command to display the name ofthe active rule base.

2. Run the wlsrbclass active_rule_base_name commandto list the defined event classes. Ensure that theITMWAS_Event, ITMWAS_TEC_Adapter_Event,and WebSphereAS_Monitor_Event classes aredefined.

3. Run the wlsrbrules active_rule_base_name commandto list the defined rules. Ensure that theitmwas_events.rls and itmwas_monitor.rls rule setfiles are defined.

4. If the required classes or rules are not defined, runthe Configure Event Server task to define theclasses and rules.

v Ensure that events are being received at the eventserver. To do this, run the wtdumprl command on theevent server to display the events in the reception logon the event server.

v The events are being received at the event server buthave a parsing_failed message. This occurs if youhave not run the Configure Event Server task. Run thetask to load the definitions for the IBM WebSphereApplication Server events into the event server.

v Ensure that the IBM Tivoli Monitoring profile wasenabled to forward events.

See the Tivoli Management Framework Reference Manual forinformation about the commands mentioned above.

You receive the following message:

IZY1125E The event adapter was notstarted because the IBM WebSphereadministration server is not running.

The Tivoli Enterprise Console adapter might have startedbut didn’t start within the 40 second limit the StartWebSphere TEC Adapter task waits. Check the TivoliEnterprise Console to see if the TEC Adapter Startedevent was sent.


Tivoli Enterprise Data Warehouse problem determinationTable 18. Tivoli Enterprise Data Warehouse problems and solutions

Problem Solution

No data in the reports.

In the case of summary reports, the report is empty oryou receive the following message:

DWRB0022E No records were found for this report.

This can be caused in the following situations.

v Resource model logging is not enabled. See“Modifying data logging settings” on page 48 forinformation.

v You have not installed the IBM Tivoli Monitoring,Warehouse Enabling component and have notsuccessfully uploaded data to the middle layerdatabase. See the IBM Tivoli Monitoringdocumentation.

v You have not installed and run the IBM TivoliMonitoring Tivoli Enterprise Data Warehouse supporton the Tivoli management region server. See the IBMTivoli Monitoring for Web Infrastructure Installation andSetup Guide.

v You have not installed and run the IBM TivoliMonitoring for Web Infrastructure: WebSphereApplication Server Warehouse Enablement Packprocesses. See IBM Tivoli Monitoring for WebInfrastructure Installation and Setup Guide.

You see the following error in the TWHApp.log file:

(F) CDWIC0022E Failure detected duringSQL script executionfor Database(TWH_MART).Return code was (4)Check messages in DB2 log (twh_ibm_db2_runlog.log),Removing TMP script.Exiting...

And the following error in the twh_ibm_db2_runlog.logfile:

DECLARE global temporary TABLEPrune_Mart_Control( Table_Name VARCHAR(120) NOTDB21034E THe command was processed as anSQL statement because it was not a validCommand Line Processor command.During SQL processing it returned:SQL0286N A default table space could notbe found with a page size of at least "4096"that authorization ID "DB2" is authorizedto use. SQLSTATE=42727

If you install the Tivoli Enterprise Data Warehouse Packwith one user ID (such as ″db2admin″) and the IBMTivoli Monitoring 5.1.1 Warehouse Enablement or thiswarehouse enablement pack with another user ID (suchas ″db2″), you must create a temporary tablespace for thewarehouse enablement pack installation user.

To create a temporary tablespace, on the system that isthe Tivoli Enterprise Data Warehouse Control Server,open a DB2 command window and issue the followingcommands:

db2 connect to TWH_CDW user <userID> \using <password>

db2 create user temporary tablespace usertmp2 \managed by system using (’usertmp2’)db2 connect to TWH_MART user <userID> \using <password>db2 create user temporary tablespace usertmp3 \managed by system using (’usertmp3’)

where <userID> is the warehouse enablement pack installuser and <password> is the password of that user.

General errors occur while using Tivoli Enterprise DataWarehouse

See the ″Troubleshooting″ chapter in the Installing andConfiguring Tivoli Enterprise Data Warehouse, Version 1,Release 1 guide for more information.

Tasks problem determinationThe following table lists general task problems that might occur.

Appendix F. Problem determination 109

Table 19. Task problems and solutions

Problem Solution

When a task fails, you might receive the following error:

endpoint_name(Endpoint): The task failedto execute.endpoint_name(Endpoint): Insufficient rolesfor executing the task onendpoint_name endpoint.

You might also receive a message that states that youhave no permission. The following message is anexample of the message received if you try to run theDiscover_WebSphere_Resources task without sufficientpermission:

bn3c4(ManagedNode): The task failed to execute.bn3c4(ManagedNode): no permission for’WebSphere Application Server UtilityTasks/Discover WebSphereResources’ for operation of ’run_task’

Ensure that you assigned the resource roles to theadministrator running the task. See “Settingauthorization roles” on page 12 for more information.After you assign the resource roles, immediately stopand start the Tivoi desktop so the assigned roles takeeffect.

The Administration server does not stop after runningthe Stop_Administration_Server task immediately afterstarting the server.

IBM WebSphere Application Server uses a nanny processto ensure that the Administration server successfullystarts. If you start the Administration server and thenstop it using a task, the Administration server might notstop. To stop the Administration server soon afterstarting it, you must wait several minutes to ensure thatthe nanny process completes. Then you can stop theAdministration server.

If you have a Windows Tivoli management region serverand HP-UX or Solaris endpoints, when you runadministration tasks from the GUI, you might see anerror ″Could not set locale correctly″ in the stderr sectionof the output.

Set the following environment variable on your WindowsTivoli management region server: LANG=C. After youset the environment variable, stop and restart your Tivolidesktop.

The ″C″ is for English. If you have a different localesetting, this might not fix the problem. See the TivoliManagement Framework documentation for moreinformation.

When running application server tasks, you receive amessage saying the IBM WebSphere administrationserver isn’t running even though it is.

This problem might occur if you are using a non-defaultport, with or without WebSphere security enabled. Checkthe sas.wscp.props file and ensure that the line thatchanges the port is in there. See “Enabling IBM TivoliMonitoring for Web Infrastructure: WebSphereApplication Server to communicate with IBM WebSphereApplication Server on a non-default port” on page 14 formore information.


Table 19. Task problems and solutions (continued)

Problem Solution

You might see a file sharing violation when trying todelete the trace_WebSphereAS_Iltx.log files in the$LCF_DATDIR/LCFNEW/IZY/LOGS directory.

This occurs if the IBM Tivoli Monitoring engine is stillrunning while you try to delete the files. You must stopor kill the engine before deleting the log files.

On Windows:

1. From the Tivoli management region server, issue thefollowing command:

wdmcmd -stop e endpoint_name

where endpoint_name is the name of the endpointwhere you are trying delete log files.

2. On the endpoint, open an MS-DOS prompt and issuethe following command:

net stop winmgmt

3. On the endpoint, open the Task Manager. If you stillsee the m12javaprovider process running in the TaskManager, then end the process manually.

On Unix:

1. Issue the following command:

wdmcmd -stop -e endpoint_name

where endpoint_name is the name of the endpointwhere you want to delete log files.

2. Run the following command to see if the IBM TivoliMonitoring engine is still running:

ps -ef | grep dmunix

3. If the engine is still running, stop it manually.

Once the IBM Tivoli Monitoring engine is stopped, youcan delete the trace_WebSphereAS_Iltx.log files. Then,restart the IBM Tivoli Monitoring engine.

You might see a file sharing violation when trying todelete the trace_WebSphereAS_tecAdapter.log file in the$LCF_DATDIR/LCFNEW/IZY/logs directory.

This occurs if the IBM WebSphere Application ServerTivoli Enterprise Console adapter is running whilemessages are being sent to the file. You must stop theIBM WebSphere Application Server Tivoli EnterpriseConsole adapter before deleting the file.

Run the Stop_WebSphere_TEC_Adapter task against theadministration server machine that contains the log file.Delete the log file. Restart the adapter by running theStart_WebSphere_TEC_Adapter task.

You receive the following error when running a task:

ctv07067 (ManagedNode): The task failed to execute.ctv07067 (ManagedNode): FRWTD0026E The task failedto complete execution before the timeoutperiod expired.

The task might have completed successfully, but thetimeout value was insufficient. To see the output of thetask displayed upon task completion, increase thetimeout value for the task and run the task again.

Discover_WebSphere_Resources task problem determinationThe following table lists problems that might occur when you run theDiscover_WebSphere_Resources task.


Table 20. Discover_WebSphere_Resources task problems and solutions

Point ofFailure

Problem Solution

Managed node The Discover_WebSphere_Resources task failswith the following message:

IZY1143I The Discover WebSphere Resourcestask will stop because noendpoints were selected.

You must specify endpoints on which to run theDiscover_WebSphere_Resources task. See“Creating IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Serverobjects” on page 16 for more information.

Running the Discover_WebSphere_Resourcestask from the command line fails with thefollowing message:

IZY1143I The Discover WebSphere Resourcestask will stop because noendpoints were selected.

even though you specified endpoints for thetask.

Ensure that the path names you supply areUNIX-style names, such asc:/WebSphere/AppServer instead ofc:\WebSphere\AppServer.

OSERV error Run the following command to determinewhether or not you can communicate with theendpoint:

wadminep <endpoint_name>

where <endpoint_name> is the name of theendpoint.

Check the Tivoli Management Frameworkendpoint and gateway logs for moreinformation. See the Tivoli ManagementFramework Reference Manual for informationabout these logs.

You might receive the following error whenrunning the WebSphere_Discover_Resourcestask if the administration server object is alreadycreated either from a priorWebSphere_Discover_Resources task executionor manual creation:

Exception: StExcepMsg:0006System Exception: invalid objectreference: completion status: NO

o_errs:0008 object identifier not valid

This is caused by nslookup not being found onthe managed node where theDiscover_WebSphere_Resources task is run. Thiscan be solved by creating a link to nslookup in/usr/bin, or on w32 interps, making sure thatthe system path points to the directory where/usr/bin is located.


Table 20. Discover_WebSphere_Resources task problems and solutions (continued)

Point ofFailure

Problem Solution

Endpoint You receive the following message:

IZY1159E Endpoint <endpoint> willnot be discovered due tofailure calling dependency init.

Ensure that your gateway is running.

Run the following command to determinewhether or not you can communicate with theendpoint:



You receive the following exception:

EXCEPTION FRWSL0005E A communicationsfailure occurred: FRWOG0014Edestination dispatcher unavailable

Run the following command to determinewhether or not you can communicate with theendpoint:



Authorization or authentication failed When discovering an endpoint, be sure to putthe sas properties file in the Security PropertiesFile field of the Configure Task Parameterswindow.

Ensure that the IBM WebSphere administrationserver is running.

Verify that you have correctly entered the username, password, and login source (properties)in the sas.wscp.props file.

Verify that the password in your sas.wscp.propsfile is plain text, not encrypted.

See “Configure client side WebSphere security”on page 13 for more information about the

sas.wscp.props file.

You receive the following message:

/tmp/aaaeUoaMa[##]:./XMLConfigItmwas.sh: not found.

or

IZY1164E Error creating WebSphere XMLoutput. See log file for details.

Check the installation path that you specified forthe IBM WebSphere Application Server. Itshould be $WAS_HOME. You might haveentered a valid path, but it is not the$WAS_HOME path.


Table 20. Discover_WebSphere_Resources task problems and solutions (continued)

Point ofFailure

Problem Solution

Endpoint(cont.)

Discover_WebSphere_Resources worked but theport number on objects is not correct.

If your system PATH is set with $WAS_HOME,the Discover_WebSphere_Resources task willwork if you entered a path that exists on theendpoint but is not $WAS_HOME. However, theobjects created might not be configuredcorrectly.

You can validate the WSAdministrationServerand WSApplicationServer objects created for theendpoint using the wwebsphere -g command.Review the/trace_itmwas_discover_endpoint.log file in the$LCF_DATDIR/LCFNEW/IZY/logs directory tobe sure there are no errors. You can also deletethe created objects for the endpoint and rerunthe Discover_WebSphere_Resources task.

Data was not received because the connectiontimed out.

net_recv: timeout (NNN seconds)waiting to receive from<ip_address>+<port>

Increase the gateway timeout:

1. Run the following command to see thecurrent setting:

wgateway <gateway_name>

2. Run the following command to increase thegateway session timeout:

wgateway <gateway_name>set_session_timeout nn

The task processing on the endpoint is takinglonger to complete than the gateway timeout.The task will complete, but you will not see theresults in the output window.

You can check each created object manuallywith the wwebsphere –g command. Review the/trace_itmwas_discover_endpoint.log file in the$LCF_DATDIR/LCFNEW/IZY/logs directoryfor errors, or delete the created objects for theendpoint and rerun theDiscover_WebSphere_Resources task.

Resource models problem determinationTable 21. Resource model problems and solutions

Problem Solution

A resource model fails to start but no event isreported to Tivoli Enterprise Console.

Tivoli Enterprise Console events are not generated when aresource model fails to start; they are generated when there is aproblem or change in a resource being monitored. Problems thatoccur with the resource model itself are reported in the IBMTivoli Monitoring Web Health Console.


Table 21. Resource model problems and solutions (continued)

Problem Solution

You receive the ″Failing 54″ error code in theWeb Health Console.

An error occurred collecting metrics from the application server;the IBM WebSphere administration server or application servermight be down, performance monitoring is not enabled for thisresource, or there are no instances of this resource on thisapplication server.

Check the status of the administration and application serversand restart if necessary. Activate performance monitoring. Ifthere are no instances of this resource on the server, eitherremove the resource model from the profile or unsubscribe theobject from the profile manager.

The IBM Tivoli Monitoring engine is notavailable.

Refer to the IBM Tivoli Monitoring documentation for additionalassistance.

For Windows endpoints:

1. Open the Task Manager to see if the m12javaprovider.exeprocess is running.

2. If it is not running:

a. From a command window on the Tivoli managementregion server, source the Tivoli environment, as describedin “Setting up the IBM Tivoli Monitoring environment” onpage 21.

b. Restart the engine by executing the following command:

wdmcmd -restart -e endpoint_name

where endpoint_name is the name of the endpoint.

3. If it is running, use the Task Manager to end them12javaprovider.exe manually and then restart the engine asdescribed above.

For UNIX endpoints:

1. Execute the wdmlseng command to determine if the engineis running

2. If it is not running:

From a command window on the Tivoli management regionserver, source the Tivoli environment, as described in “Settingup the IBM Tivoli Monitoring environment” on page 21.

Restart the engine by executing the following command:

wdmcmd -restart -e endpoint_name

where endpoint_name is the name of the endpoint.

3. If it is running:

a. Stop the engine by executing the following command:

wdmcmd -stop endpoint_name

b. Restart the engine as described above.



Problem Solution

You distribute a monitoring profile and it is notshowing up on the Web Health Console.

Refer to the IBM Tivoli Monitoring documentation for additionalassistance.

Determine if the distribution was interrupted by running thefollowing command:

wmdist -I repeatername

If the output shows that the distribution was interrupted, youcan clear the distribution in the following ways:

1. Stop the gateway on which the repeater resides by runningthe following command:

wgateway gateway_name stop

where gateway_name is the name of the gateway.

2. Clear the repeater by running the following command:

wmdist -B repeatername

If this is not successful, use the following commands to deletetemporary files:

cd ’/wtemp’rm ./states/*rm ./depot/*

3. Restart the gateway/repeater by running the followingcommand:

wgateway gateway_name start

where gateway_name is the name of the gateway.

4. Redistribute the profile.

If this does not work, use the List Trace Logs task to determine ifthe trace_WebSphereAS_Ilt.log exists.

If the log file does not exist, stop the IBM Tivoli Monitoringengine and run the IBM Tivoli Monitoring task DMLinkJRE asspecified in the IBM Tivoli Monitoring for Web InfrastructureInstallation and Setup Guide. Restart the engine

If the trace_WebSphereAS_Ilt.log file exists, view the contents tosee if it is using the IBM WebSphere Application Server JRE.

If it is not using the IBM WebSphere Application Server JRE, stopthe IBM Tivoli Monitoring engine and run the IBM TivoliMonitoring task DMLinkJRE, specifying the IBM WebSphereApplication Server JRE and restart the engine. See the IBM TivoliMonitoring for Web Infrastructure Installation and Setup Guide formore information.

You see a ″Not Compiled″ status for a resourcemodel on the Web health Console.

On a Windows endpoint, this occurs when you do not haveWindows Script Host, Version 5.6, installed. Run the cscriptcommand from the command prompt to verify the version ofWindows Script Host. If it is not Version 5.6, you can downloadit from the Microsoft Web site.



Problem Solution

You see a ″Missed PreReq″ status for a resourcemodel on the Web health Console

You probably have not run the DMLinkJRE command. Run theDMLinkJRE command as specified in the IBM Tivoli Monitoringfor Web Infrastructure Installation and Setup Guide.

If this problem occurs after the resource model has already runsuccessfully, restart the IBM Tivoli Monitoring engine on theendpoint. You can restart the engine from the Web HealthConsole or from the command line (with the wdmcdmcommand).

A resource model fails. Restart the IBM Tivoli Monitoring engine on the endpoint. Youcan restart the engine from the Web Health Console or from thecommand line (with the wdmcdm command).

The resource models write trace messages in one of the followingfiles on the endpoint:

v For UNIX:$LCF_DATDIR/LCFNEW/AMW/log/trace_dmxengine.log

v For Windows:%LCF_DATDIR%\LCFNEW\Tmw2k\Tmw2k.log

The statements preceding the resource model aborting messagein the trace file should contain information about why theresource model failed.

For more information, refer to the IBM Tivoli Monitoring User’sGuide.

The resource model status alternates between″Failing 54″ and ″Running.″

When the IBM WebSphere administration server or applicationserver is down, no performance information can be retrieved forthat resource, so the resource models that report performanceinformation report ″Failing 54.″ The IBM Tivoli Monitoringengine will automatically retry the resource model every threeminutes. After reporting the failure, the engine returns the statusto ″Running″ on the Windows platform. The status will alternatebetween ″Running″ and ″Failing 54″ until the problem isresolved.

See the solution to the ″You receive the ″Failing 54″ error code inthe Web Health Console″ problem.

Non-key attributes in the events sent to TivoliEnterprise Console do not reflect the currentvalues as displayed in the IBM Tivoli MonitoringWeb Health Console.

Because the Web Health Console displays real-time data andTivoli Enterprise Console provides a snapshot of the data at thetime the event was generated, it is possible for the information inthe events to be out of sync with the information displayed onthe Web Health Console.



Problem Solution

The IBM WebSphere administration server isrunning but the resource model says it is down.

Either the wrong JRE was specified when the DMLinkJRE taskwas run or WebSphere security is enabled but no properties filewas specified when the WSAdministrationServer object wascreated.

Check the$LCF_DATDIR/LCFNEW/IZY/logs/trace_WebSphereAS_Ilt.logon the endpoint. If you see AbstractMethodError andConnectionLost exceptions, the IBM WebSphere ApplicationServer JRE is not being used. If tracing is set to ALL in theitmcsLog.Properties file on the endpoint, the ″Java home″ valuewill be logged. This value should be the location of the IBMWebSphere Application Server JRE. On Unix, the JRE version isidentified in$LCF_DATDIR/LCFNEW/Tmw2k/Unix/data/dmxout.log

To link the ILT to the correct JRE, first stop the engine on theendpoint. On Windows NT, make sure the m12javaprovider.exeis also stopped. Then run the DMLinkJRE task as specified in theIBM Tivoli Monitoring For Web Infrastructure Installation and SetupGuide. Specify the location of the IBM WebSphere ApplicationServer JRE. Then restart the engine.

If you see ConnectionLost exceptions and WebSphere security isenabled, execute the wwebsphere -g command to determine ifWebSphere Security Enabled is TRUE and the WebSphereSecurity Properties File is correctly identified. If this is wrong,you must unsubscribe the objects, delete them and recreate themwith the correct information.

For information about the resource model error codes reported in the IBM TivoliMonitoring Web Health Console, see the IBM Tivoli Monitoring for WebInfrastructure Reference Guide.

Debugging informationThe following sections provide information that might be helfpul for debuggingany problems that occur.

The following topics are discussed:v “Log file information”v “AutoTrace information” on page 119

Log file informationKnowing file names, file contents, and where to look for information, such as taskoutput and log files, can often be the key to solving a problem. The followingsections provide information about the logfiles created by IBM Tivoli Monitoringfor Web Infrastructure: WebSphere Application Server.

General log filesIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverwrites log files to endpoints and Tivoli management region servers or gateways.


The location of the log files on the endpoint is $LCFDAT_DIR/LCFNEW/IZY/logsThe location of the log files on the Tivoli management region server or gateway is$DBDIR/IZY/logs.

For information about viewing these log files from the Tivoli desktop, see“Viewing endpoint or callback log files” on page 60.

Task log filesThe IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Servertasks write logs to the $LCF_DATDIR/LCFNEW/IZY/logs directory. For thenames of the log files created by the tasks, see the task descriptions in the IBMTivoli Monitoring for Web Infrastructure Reference Guide.

For information about viewing these log files from the Tivoli desktop, see“Viewing endpoint or callback log files” on page 60.

Tivoli Enterprise Data Warehouse log filesTivoli Enterprise Data Warehouse log files are written to the Tivoli Enterprise DataWarehouse server machine in the DB2 logging directory. On Windows, the defaultdirectory is SQLLIB\logging. The log file names start with IZY and match theTivoli Enterprise Data Warehouse process step.

Resource model log filesIBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Serverresource models log information to the IBM Tivoli Monitoring logs, which are inlocated in the $LCF_DATDIR/LCFNEW/AMW/logs/trace_dmxengine.log onUNIX and in the $LCF_DATDIR/LCFNEW/Tmw2k/tmw2k.log on Windows.

The IBM Tivoli Monitoring for Web Infrastructure: WebSphere Application Servertasks do not control these logs. You can use the IBM Tivoli Monitoring wdmtrcengcommand to set the level of tracing for IBM Tivoli Monitoring. See the IBM TivoliMonitoring documentation for more information.

The code that retrieves the performance information for the resource models, theILT, creates log files on the endpoint in the $LCF_DATDIR/LCFNEW/IZY/logs.They are named trace_WebSphereAS_ILT.log, trace_WebSphereAS_ILT1.log,, andtrace_WebSphereAS_ILT2.log. The most current trace log file istrace_WebSphereAS_ILT.log; the other two files are used for cycling the mostcurrent log. The level of logging is determined by the itmcsLogger.trc.levelproperty in the $LCF_DATDIR/LCFNEW/ITM/PACS/itmcsLog.Properties file onthe endpoint. The default setting is ERROR, only error conditions will be logged. Ifthere is a problem, Customer Support might ask you to change this to ALL. Forexample: itmcsLogger.trc.level=ALL

Gathering log files for Customer SupportIn certain situations, Customer Support might request that you send log files withyour problem report. Use the IBM Tivoli Monitoring Component Serviceswitmcollectsupportdata command to gather the log files into an XML file that youcan send to Customer Support.

AutoTrace informationAutoTrace is installed by IBM Tivoli Monitoring and is initialized to collect traceinformation for IBM Tivoli Monitoring Web Infrastructure: WebSphere ApplicationServer on each managed node when the product is installed. IBM TivoliMonitoring Web Infrastructure: WebSphere Application Server generates AutoTraceinformation only on the managed nodes on which the product is installed. No


AutoTrace information for IBM Tivoli Monitoring Web Infrastructure: WebSphereApplication Server is generated on the endpoints.

The following sections provide information about AutoTrace. The following topicsare discussed:v Initializing autotracev Gathering information to send to Customer Support

Initializing autotraceTo verify that AutoTrace is initialized and enabled for IBM Tivoli Monitoring WebInfrastructure: WebSphere Application Server, execute the following command at aTivoli sourced prompt on the Tivoli management region server or managed nodewhere you want to capture AutoTrace information″$ atctl product

When AutoTrace is initialized and tracing, you see output similar to the following:# prod name home49420013 TMWAS /tivoli/<hostname>.db/IZY/logs

Gathering AutoTrace informationTo capture a snapshot of the Autotrace channel information to a file for IBM TivoliMonitoring Web Infrastructure: WebSphere Application Server, execute thefollowing command at a Tivoli sourced prompt on the relevant Tivoli managementregion server or managed node.$ atctl snap 13

The number 13 stands for the default AutoTrace channel in use by IBM TivoliMonitoring Web Infrastructure: WebSphere Application Server.

A 1 MB file named snap13_0.at is created as the output of the previous command.You can submit this file to Customer Support if requested.

Additional snapshots taken in the same directory using the above command createfiles named snap13_x, where x is a unique number. Each snap resets the tracechannel to zero to allow for the accumulation of more trace information.


Appendix G. Accessibility

Accessibility features help users who have a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server enable you to:v Use assistive technologies such as screen-reader software and a digital speech

synthesizer to hear what is displayed on the screenv Operate specific or equivalent features using only the keyboardv Magnify what is displayed on the screen

In addition, the product documentation includes the following features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for you to apply screen-reader software.v All images are provided with alternative text so that users of the documentation

with vision impairments can understand the contents of the images.

Using assistive technologiesAssistive technology products such as screen-readers function with both thetext-based and graphical user interfaces found in IBM Tivoli Monitoring for WebInfrastructure: WebSphere Application Server. Consult the assistive technologyproduct documentation for specific information about using it to accesscommand-line or graphical interfaces.

Magnifying what is displayed on the screenIn all components of IBM Tivoli Monitoring for Web Infrastructure: WebSphereApplication Server other than the Web Health Console, you can magnify thescreens of the product user interfaces using facilities provided by the operatingsystems on which the product is run. For example, in a Windows environment youcan change the screen settings to a lower resolution to enlarge the font sizes of thetext on the screen. Information about these facilities is provided in the relevantoperating system documentation.

Documentation in accessible formatsAll user documentation is provided in HTML format, which can be read directlyby assistive tools such as screen readers, or in convertible PDF format. ConvertiblePDF files are those that can be converted from PDF to HTML by the Adobe PDF toHTML converter. For information about converting PDF documents to HTML, referto the Adobe book Optimizing Adobe PDF Files for Accessibility

Using alternative textAll documentation images are provided with an alternative text that can be readby assistive tools such as screen readers.

121

Appendix H. 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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents.You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:li

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

123

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, 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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksDB2, IBM, the IBM logo, Tivoli, the Tivoli logo, Tivoli Enterprise Console, andWebSphere are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Microsoft and Windows are registered trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks 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 othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Appendix H. Notices 125

Index

Aaccessibility xi, 121actions (recovery), concept 8administration servers, checking the

status of 55administrators, Tivoli 9application servers

checking the status of 55listing 58

assigning user groups in Tivoli EnterpriseData Warehouse 80

authorization roles 89assigning 12defined 9

AutoTrace 119gathering information for Customer

Support 120initializing 120

availability management 1

Bbooks

feedback ixonline ixordering ix

built-in actionsconcept 8

Ccallback log files, viewing 60CIM class, definition 8clearing events, concept 6commands

wcrtjob 68wcrtprf 95wcrtprfmgr 95wdistrib 24wdmcmd 51wdmdistrib 51wdmeditprf 42, 44, 46, 48, 50, 97, 98wdmeng 51wdmlseng 51, 52wdmmn 52wdmtrceng 51wrunjob 70wruntask for any task 64wruntask, Check Administration

Server Status task 56wruntask, Check Application Server

Status task 56wruntask, List Application Servers

task 59wruntask, List WebSphere Trace Logs

task 60wruntask, Start Administration Server

task 58wruntask, Start Application Server

task 58

commands (continued)wruntask, Stop Administration Server

task 58wruntask, Stop Application Server

task 58wschedjob 71wsetadmin 12wsetpm 95wsub 96wwebsphere 17

conceptsactions (recovery) 8built-in actions 8clearing events 6data logging 7event monitors 7events 5events (clearing) 6Gathering Historical Data

Warehouse 4heartbeat function 4logging (data) 7monitors 7profiles 8recovery actions 8scheduling 9tasks (Tivoli Management

Framework) 8Tivoli Management Framework

tasks 8configure event server task 31Configure WebSphere TEC Adapter

task 28configuring

endpoints 13Tivoli Enterprise Console event

server 28, 37conventions xicreating security properties file 13Customer Support xicycles

definition 4

Ddata logging

concept 7customizing 48

data marts 80dataless profile managers, subscribers

example 95debugging

log files 118distributed systems

defined 3

Ee-mail contact xiendpoint log files, viewing 60

endpointsconfiguration 14configuring 13dataless 95defined 10subscribing 96which resource models are

running 52ETL utilities 75event

classescategories 105

event classes and rules 105event monitors

concept 7Health Console 7Tivoli Business Systems Manager 7Tivoli Enterprise Console server 7

event server 31Tivoli Enterprise Console,

configuring 28events

concept 5filtering 33rules for 105

events (clearing), concept 6events, Tivoli Enterprise Console

defined 27groups 28processing 28responding to 28sources 28viewing 28

Ffailed profile distributions 98feedback about publications xifiles

callback log 60endpoint log 60sas.client.props 14sas.wscp.props 15security properties 14

filtering events 33

Ggateways

IBM Tivoli Monitoring, managing 51Gathering Historical Data Warehouse

concept 4groups, subscribers 22

Hhealth

example of health determination 53understanding resource 53

127

Health Consoleas monitor, concept 7

heartbeat functionconcept 4

HelpSee Customer Support

holesdefined 5example 43

IIBM Tivoli Monitoring

about 3gateways, managing 51logging, customizing 48notices, sending 45overview 3profiles, managing 50resource model results 53scheduling rules, creating 46setting up 93setting up the environment 21tasks, specifying 44thresholds 42Web Health Console 53, 54which resource models are

running 52IBM Tivoli Monitoring for Web

Infrastructure, Version 5.1.0: WebSphereApplication Server

event rules 105indications

defined 5installation

task library 63tasks performed automatically 11Tivoli Business Systems Manager 37

interfaces, user 10

Jjobs

creating 67running 70scheduling 71

JVMPI data reporting, enabling 103

Llibrary, task 63Line of Business 35log files 118

callback, viewing 60endpoint, viewing 60gathering for Customer Support 119resource models 119tasks 119Tivoli Enterprise Data

Warehouse 119logging

customizing 48logging (data)

concept 7

logsSee also log fileslist of endpoint or callback 60

Mmanaged resources

defined 3managed resources, defined 10management, availability 1management, operations 2management, performance 2manuals

feedback ixonline ixordering ix

MDist2distributing profiles using 23functions used by IBM Tivoli

Monitoring 23monitoring profiles, defined 94monitoring, enabling performance 15monitors

concepts 7Health Console 7Tivoli Business Systems Manager 7Tivoli Enterprise Console server 7

Nnotices

sending 45

Ooccurrences

defined 5operations management 2ordering publications xoverview

IBM Tivoli Monitoring 3IBM Tivoli Monitoring for Web

Infrastructure: WebSphereApplication Server 1

Pparameters

defined 7performance management 2performance monitoring, enabling 15problem determination

AutoTrace 119dependencies issues 107failed task 110log files 118permissions errors 110resource model log files 119task log files 119Tivoli Enterprise Console events not

displayed 108Tivoli Enterprise Data

Warehouse 119profile managers

created during installation 11

profile managers (continued)creating 94dataless 95setting up 94subscribing endpoints 96

profilesconcept 8creating 94distributing from the Tivoli

desktop 21distributing using MDist2 23managing at endpoints 50monitoring 94rerunning failed distributions 98subscribers of 22

publicationsfeedback ixonline ixordering ix

Qquick reference, task 91

Rrecovery actions, concept 8reports

Tivoli Enterprise Data Warehouse,creating 87

Tivoli Enterprise Data Warehouse,modifying default settings 86

Tivoli Enterprise Data Warehouse,modifying settings 86

Tivoli Enterprise Data Warehouse,running 84

Tivoli Enterprise Data Warehouse,scheduling to run 85

resource health, understanding 53resource model log files 119resource models

adding customized 97adding default 96created during installation 11definition 8log files 119managing at endpoints 50organizing 97results, viewing 53running on endpoints 52scheduling rules, creating 46tasks, specifying 44thresholds, customizing 42

resourcesadded during installation 11discovering for Tivoli Business

Systems Manager 38endpoints 10managed 10

resources, manageddefined 3

results, resource models, viewing 53roles

authorization, assigning 12Tivoli Enterprise Data Warehouse 77


roles (continued)Tivoli Enterprise Data Warehouse,

assigning 78Tivoli Enterprise Data Warehouse,

IBM Console user 78roles, authorization 9rules 105rules, Tivoli Enterprise Console

about 28

Sscheduling

concept 9for monitoring 46resource models 46

scheduling rules, example 47security properties file, creating 13server objects

configuring 16creating in the Tivoli environment 16locating 16

serversSee also server objectsapplication, listing 58IBM WebSphere, checking status 55starting 57stopping 57

softcopy publications xsubscribers 22subscribing endpoints 96Support, Customer xi

Ttask argument window, example 66task library 63task log files 119tasks

Administration Server Status 56Application Server Status 56authorization roles 89command names 91Configure WebSphere TEC Adapter

task 28customizing 66descriptions 91ITMWAS event tasks configure event

server 31library 63List Application Servers 59List Trace Logs 60log files 119quick reference 91running 63specifying for an event 44standard 63Start Administration Server 58Start Application Server 58Stop Administration Server 58Stop Application Server 58Tivoli Business Systems Manager,

WebSphere_TBSM_Discovery_Eventstask 39

tasks (continued)working with IBM Tivoli Monitoring

for Web Infrastructure: WebSphereApplication Server resources 55

tasks (Tivoli Management Framework)concept 8

thresholdscustomizing resource models 42defined 9

Tivoli administrators 9Tivoli Business Systems Manager

as monitor, concept 7configuring Tivoli Enterprise Console

to forward events 37discovering resources 38IBM WebSphere administration server

tasks 39IBM WebSphere application server

tasks 39installing 37integrating with IBM Tivoli

Monitoring for Web Infrastructure:WebSphere Application Server 36

prerequisites for integrating 36task,

WebSphere_TBSM_Discovery_Eventstask 39

understanding 35uninstalling 40WebSphere_TBSM_Discovery_Events

task 39Tivoli Enterprise Console

Configure Event Server window 29Configure WebSphere TEC Adapter

window 32console 28event classes 105event groups, definition 28event rules 105event server, configuring 28, 31, 37events not displayed 108events, defined 27events, processing 28events, responding to 28events, sources 28events, viewing 28overview 27rules, overview 28

Tivoli Enterprise Console serveras monitor, concept 7

Tivoli Enterprise Data Warehouseassigning user groups to a data

mart 80assigning users to user group 79capabilities 75central data warehouse 76components 75control server 75creating IBM Console user 78creating reports 87creating user groups 79data marts 76log files 119logging 49modifying report settings 86modifying report settings

example 86

Tivoli Enterprise Data Warehouse(continued)

problem determination 109report interface 76roles 77running reports 84scheduling reports to run

automatically 85user roles, assigning 78users and user groups 77

Tivoli Management Frameworktasks, concept 8

troubleshootingSee problem determination

Uuser groups

Tivoli Enterprise Data Warehouse,assigning 80

Tivoli Enterprise Data Warehouse,assigning users 79

Tivoli Enterprise Data Warehouse,creating 79

usersroles, assigning in Tivoli Enterprise

Data Warehouse 78users. creating for IBM Console 78utilities, ETL 75

Wwcrtjob command 68wcrtprf command 95wcrtprfmgr command 95wdistrib command 24wdmcmd command 51wdmdistirb command 51wdmeditprf command 42, 44, 46, 48, 50,

97, 98wdmeng command 51wdmlseng command 51, 52wdmmn command 52wdmtrceng command 51Web Health Console 53

IBM Tivoli Monitoring 54WebSphere security 13WebSphere TEC adapter

filtering events 33wrunjob command 70wruntask command

Check Administration Server Statustask 56

Check Application Server Statustask 56

for any task 64List Application Servers task 59List WebSphere Trace Logs task 60Start Administration Server task 58Start Application Server task 58Stop Administration Server task 58Stop Application Server task 58

wschedjob command 71wsetadmin command 12wsetpm command 95wsub command 96

Index 129

wwebsphere command 17


��

Printed in U.S.A.

SC23-4705-00

IBM Tivoli Monitoring for Web Infrastructure: WebSphere...

Documents

Transcript of IBM Tivoli Monitoring for Web Infrastructure: WebSphere...