tivoli manager for websphere application server -...

Tivoli® Manager for WebSphere®Application ServerUser’s Guide Version 1.1

Tivoli Manager for WebSphere Application Server User’s Guide

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems SoftwareLicense Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer orLicense Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic,optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporationgrants you limited permission to make hardcopy or other reproductions of any machine-readable documentation foryour own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No otherrights under copyright are granted without prior written permission of IBM Corporation. The document is notintended for production and is furnished “as is” without warranty of any kind. All warranties on this document arehereby disclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, Tivoli Enterprise, and Tivoli Enterprise Console are trademarks orregistered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States,other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

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

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries,or both.

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

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they willbe available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used.Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionallyequivalent product, program, or service can be used instead of the referenced product, program, or service. Theevaluation and verification of operation in conjunction with other products, except those expressly designated byTivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation,North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho Should Read This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

What This Document Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Conventions Used In This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Accessing Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Accessing the Files on the Product CD . . . . . . . . . . . . . . . . . . . . . . . . . x

Accessing the Files on the Tivoli Web Site . . . . . . . . . . . . . . . . . . . . . . x

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introducing Tivoli Manager for WebSphereApplication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Operations Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Integration with Tivoli Management Framework . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Installing Tivoli Manager for WebSphereApplication Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Where to Install Tivoli Manager for WebSphere Application Server . . . . . . . . 6

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Installing Tivoli Manager for WebSphere Application Server . . . . . . . . . . . . . 7

Installing From the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Using the winstall Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

iiiTivoli Manager for WebSphere Application Server

Uninstalling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3. Getting Started with Tivoli Manager forWebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Assigning Tivoli Manager for WebSphere Application Server Authorization 14

Assigning Tivoli Management Region Roles to a Tivoli Administrator 14

Assigning Resource Roles to a Tivoli Administrator . . . . . . . . . . . . . . . 15

Configuring Tivoli Enterprise Console Event Handling. . . . . . . . . . . . . . . . . 16

Configuring the Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Managing WebSphere Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Subscribing Servers to a Profile Manager. . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4. Managing WebSphere Application ServerEvents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring the Event Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring an Event Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Filtering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter 5. Monitoring WebSphere Application ServerResources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Enabling Performance Monitoring in WebSphere . . . . . . . . . . . . . . . . . . . . . 25

Understanding the Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Monitors Configured at Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Status Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Administration Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Integration Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Application Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Performance Counter Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

EJB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

iv User’s Guide Version 1.1

HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Thread Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Adding Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 6. Tasks for Managing Tivoli Manager forWebSphere Application Server Resources . . . . . . . . . . . . . 37

WAS Server Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Server Information Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Administration Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

List Application Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Application Server Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Server Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Start Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Stop Administration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Start Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Stop Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Start Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Stop Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

WAS Utility Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Start Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Stop Debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Start Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Stop Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Configure WAS Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Delete Endpoint Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

List Endpoint Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Delete Endpoint Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Display WAS Endpoint Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 50

vTivoli Manager for WebSphere Application Server

Displaying Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Running Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Appendix A. Event Classes and Rules . . . . . . . . . . . . . . . . . . 55Tivoli Manager for WebSphere Application Server Event Classes . . . . . . . . . 55

Distributed Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

WebSphere Application Server Events . . . . . . . . . . . . . . . . . . . . . . . . . 56

Rules for Tivoli Manager for WebSphere Application Server Events . . . . . . . 57

Distributed Monitoring Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

WebSphere Application Server Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Appendix B. Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Appendix C. Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Installation Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Questions on Running Tasks from the Desktop . . . . . . . . . . . . . . . . . . . . . . 87

Questions on Using Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Questions on Using the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . 89

Helpful Debugging Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Appendix D. Performance Monitoring InstrumentationLevels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Changing the Instrumentation Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

vi User’s Guide Version 1.1

Preface

This document provides information about planning for, installing,and using Tivoli Manager for WebSphere Application Server.

Tivoli Manager for WebSphere Application Server enables you tomonitor the performance and status of WebSphere ApplicationServer. In addition, Tivoli Manager for WebSphere ApplicationServer management tasks enable you to stop and start a WebSphereApplication Server and display information on each endpoint.

Note: The Tivoli Enterprise Console™ and Tivoli AdapterConfiguration Facility (ACF) products must be installed foryou to take advantage of event management functions. Theremainder of this document treats event management topicswith the assumption that Tivoli Enterprise Console and TivoliACF are installed where required.

This document describes how to use the tasks and monitors that areprovided with Tivoli Manager for WebSphere Application Server.

Who Should Read This DocumentThis guide is for system administrators who monitor and manageWebSphere Application Servers. This guide requires knowledge ofTivoli management software, Tivoli products (such as DistributedMonitoring and Tivoli Enterprise Console), and WebSphereApplication Server products.

Prerequisite and Related DocumentsFor hardware and software requirements, and other releaseinformation, see the Tivoli Manager for WebSphere ApplicationServer Release Notes.

Related documents include:

¶ Tivoli Management Framework Planning and Installation Guide

¶ Tivoli Management Framework User’s Guide

viiTivoli Manager for WebSphere Application Server

¶ Tivoli Management Framework Reference Manual

¶ Tivoli Distributed Monitoring User’s Guide

¶ Tivoli Enterprise Console User’s Guide

¶ Tivoli Enterprise Console Rule Builder’s Guide

¶ Tivoli Software Installation Service User’s Guide

What This Document ContainsThe Tivoli Manager for WebSphere Application Server User’s Guidecontains the following sections:

¶ “Introducing Tivoli Manager for WebSphere Application Server”on page 1

Introduces the features and functions of Tivoli Manager forWebSphere Application Server.

¶ “Installing Tivoli Manager for WebSphere Application Server” onpage 5

Describes how to plan for and install Tivoli Manager forWebSphere Application Server.

¶ “Getting Started with Tivoli Manager for WebSphere ApplicationServer” on page 13

Describes how to configure Tivoli Manager for WebSphereApplication Server.

¶ “Managing WebSphere Application Server Events” on page 19

Describes how to manage WebSphere Application Server eventsusing tasks that are contained in the WAS Event Tasks library.

¶ “Monitoring WebSphere Application Server Resources” onpage 25

Contains information on how to use the performance monitorsthat Tivoli Manager for WebSphere Application Server provides.

¶ “Tasks for Managing Tivoli Manager for WebSphere ApplicationServer Resources” on page 37

Contains information on how to locate and use tasks that TivoliManager for WebSphere Application Server provides.

viii User’s Guide Version 1.1

¶ “Event Classes and Rules” on page 55

Contains a list of the event classes and rules that the TivoliManager for WebSphere Application Server defines.

¶ “Messages” on page 61

Describes the messages that Tivoli Manager for WebSphereApplication Server generates.

¶ “Troubleshooting” on page 85

Provides installation tips, help on debugging problems, andtypical symptoms and solutions.

¶ “Performance Monitoring Instrumentation Levels” on page 97

Provides information on the WebSphere Application Servermonitor collection.

Conventions Used In This DocumentThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, flags, and other information that youmust use literally appear in bold.

Italics Variables and new terms appear in italics. Words and phrasesthat are emphasized also appear in italics.

MonospaceCode examples, output, and system messages appear in amonospace font.

Accessing Online DocumentationThe Tivoli Customer Support Web site(http://www.tivoli.com/support/) offers a guide to support services(the Customer Support Handbook); frequently asked questions(FAQs); and technical information, including release notes, user’sguides, redbooks, and white papers.

ixTivoli Manager for WebSphere Application Server

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

Tivoli Manager for WebSphere Application Server documentation isavailable in the following online formats on both the Tivoli Managerfor WebSphere Application Server CD and the Tivoli Web site:

¶ Portable Document Format (.pdf, which you can view or printusing the Adobe Acrobat Reader). If you do not already haveAdobe Acrobat Reader, you can obtain it for free by clicking theGet Acrobat Reader icon at the Adobe Web site,http://www.adobe.com, and following the steps that are provided.

¶ Hypertext Markup Language (.htm), which you can view usingyour default Web browser.

Accessing the Files on the Product CDThe .pdf and the .htm files for the Tivoli Manager for WebSphereApplication Server User’s Guide (w11u.pdf and w11u.htm) areavailable on the Tivoli Tivoli Manager for WebSphere ApplicationServer CD and, after installation, in the following directory:

¶ for UNIX™: $BINDIR/../generic_unix/TME/WASAV/doc

¶ for Windows NT™:%BINDIR%\..\generic_unix\TME\WASAV\doc

Use Adobe Acrobat to view or print the w11u.pdf located in the\DOC directory on the product CD. Use your browser to view thew11u.htm file located in the \DOC directory on the product CD.

Note: The Tivoli Manager for WebSphere Application ServerRelease Notes document is not provided on the TivoliManager for WebSphere Application Server CD.

Accessing the Files on the Tivoli Web SiteThe Tivoli Manager for WebSphere Application Server User’s Guideand the Tivoli Manager for WebSphere Application Server ReleaseNotes are available at http://www.tivoli.com/support/documents/ .

You must be a registered user to access this Web site. If you havenot registered, when the Username and Password Required prompt isdisplayed, click Cancel and follow the registration directions.

x User’s Guide Version 1.1

http://www.adobe.com

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

TerminologyFor a complete glossary of Tivoli terms, refer to the glossary at thefollowing Web site:http://www.tivoli.com/support/documents/glossary

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or bycalling one of the following telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey athttp://www.tivoli.com/support/survey/

Contacting Customer SupportThe Tivoli Customer Support Handbook athttp://www.tivoli.com/support/handbook/ provides information aboutall aspects of Tivoli Customer Support, including the following:

¶ Registration and eligibility.

¶ How to contact support, depending on the severity of yourproblem.

¶ Telephone numbers and e-mail addresses, depending on thecountry you are in.

¶ What information you should gather before contacting support.

xiTivoli Manager for WebSphere Application Server

http://www.tivoli.com/support/documents/glossary

http://www.tivoli.com/support/Prodman/html/pub_order.html

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

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

xii User’s Guide Version 1.1

Introducing Tivoli Manager forWebSphere Application Server

Tivoli Manager for WebSphere Application Server provides acentralized system management tool for IBM’s™ WebSphereApplication Server Advanced Edition (WebSphere ApplicationServer) processes on the Tivoli platform. Tivoli Manager forWebSphere Application Server facilitates the management ofWebSphere application servers on Tivoli Management Frameworkendpoints.

WebSphere Application Server provides the following functions:

¶ Tools for developing active web sites through the use of Java™

servlets and Java Server Pages (JSP).

¶ Tools for developing and deploying enterprise beans written tothe Enterprise JavaBeans™ (EJB) specification. Enterprise beanscan act as a bridge between your Web site and your non-webcomputer systems.

¶ A graphical user interface (GUI), the WebSphere AdministrativeConsole, for administering the components of the TivoliManager for WebSphere Application Server.

¶ A set of application programming interfaces (APIs) forgenerating, validating, and presenting extensible markuplanguage (XML) documents.

1

1Tivoli Manager for WebSphere Application Server

1.In

trod

uctio

n

Tivoli Manager for WebSphere Application Server can be used withTivoli Enterprise Console, although it is not a required product. TheTivoli Enterprise Console event server (event server) receives, filters,and processes selected events before displaying them in the TivoliEnterprise Console event console (event console).

Tivoli Manager for WebSphere Application Server provides thefollowing features that enable you to perform system managementfunctions for WebSphere Application Server:

¶ Tasks to perform WebSphere Application Server administrativeactivities on endpoints

¶ Monitors for key performance and availability of applicationservers

¶ WebSphere Application Server events are forwarded to the TivoliEnterprise Console

Operations ManagementTivoli Manager for WebSphere Application Server provides tasks tostart, stop, and obtain status on the servers.

Performance ManagementTivoli Manager for WebSphere Application Server provides theIntegration Server which collects performance data for monitors.

Event ManagementYou can use Tivoli Manager for WebSphere Application Server tomonitor and retrieve events from application servers. These eventsare converted to a Tivoli Enterprise Console event format andforwarded to a centralized event server for display and processing.

The Integration Server is used in event management to capturemessages that WebSphere logs to its database and forwards thesemessages to the event server. In addition, the Integration Serverallows you to specify events that you do not want forwarded to theevent server. With this feature, you can prevent the Tivoli Enterprise

2 User’s Guide Version 1.1

Console from being populated with harmless events, allowing you tofocus on events of interest to your administrators. See “ConfigureWAS Endpoint” on page 44 for more information.

Note: The Tivoli Enterprise Console and Tivoli AdapterConfiguration Facility (ACF) products must be installed foryou to take advantage of event management functions. Theremainder of this document treats event management topicswith the assumption that Tivoli Enterprise Console and TivoliACF are installed where required.

Integration with Tivoli Management FrameworkTivoli Management Framework provides a powerful and flexibleframework for developing a comprehensive management system.Tivoli Manager for WebSphere Application Server integrates yourapplication servers into this system. Integration with the TivoliManagement Framework provides many benefits, including:

AuthorizationsTivoli Manager for WebSphere Application Server resourcesare contained in a Tivoli policy region. Tivoli Manager forWebSphere Application Server creates two new roles,wasav_senior and wasav_admin. To start tasks, one or bothof these roles must be assigned to an administrator.

Event consolesThe event console provides consolidated event displays forWebSphere Application Server events. You can create andconfigure event consoles for a number of WebSphereApplication Server administrators and servers.

Distributed monitoringYou can set up monitors to alert you about eventsconcerning WebSphere Application Server resources.Configurable thresholds and responses enable you to activelymonitor and automatically assign various severity levels forserver events.


1.In

trod

uctio

n

Installing Tivoli Manager forWebSphere Application Server

Before you can install Tivoli Manager for WebSphere ApplicationServer, you must prepare both your Tivoli and WebSphereApplication Server environments. This chapter describes how toinstall Tivoli Manager for WebSphere Application Server anddiscusses the following pre-installation tasks:

1. Ensure that all prerequisite software is installed and that you arerunning on a supported operating system.

Refer to the Tivoli Manager for WebSphere Application ServerRelease Notes for information on supported Tivoli software,prerequisite software and operating systems, and disk spacerequirements.

2. Configure the Tivoli management regions to include WebSphereapplication servers as endpoints before installing Tivoli Managerfor WebSphere Application Server.

Note: Resources may be shared on interconnected Tivolimanagement regions

3. Ensure that Tivoli Management Framework endpoints andgateways are properly configured and functional. For moreinformation on gateways and endpoints, see Chapter 8, ″TivoliEndpoints and Gateways″ in the Tivoli Management FrameworkPlanning and Installation Guide.

2


2.In

stalling

Where to Install Tivoli Manager for WebSphereApplication Server

Install Tivoli Manager for WebSphere Application Server on theTivoli management region server and on all endpoint gateways. Forinterconnected Tivoli management regions, Tivoli Manager forWebSphere Application Server must be installed on all the Tivolimanagement region servers.

Optionally, if Tivoli Enterprise Console is installed, you can installTivoli Manager for WebSphere Application Server on the TivoliEnterprise Console event server (event server). With TivoliEnterprise Console, the Integration Server and the monitors canforward events to the event server.

Notes:

1. Tivoli Manager for WebSphere Application Server supports onlyone installation of WebSphere Application Server on a host.

2. Tivoli Manager for WebSphere Application Server requires aWebSphere administration server to be on the managed endpoint.

Installation OverviewInstall Tivoli Manager for WebSphere Application Server using oneof the following methods:

¶ From the Tivoli desktop as described in “Installing From theTivoli Desktop” on page 8.

¶ From the command line by using the winstall command asdescribed in “Using the winstall Command” on page 9.

The installation facility installs Tivoli Manager for WebSphereApplication Server and creates a Tivoli Manager for WebSphereApplication Server policy region on the desktop. The followingtable shows the location of the installed component:


Installed Component

TivoliManagement

Region Server Event Server Gateway Endpoint

Tivoli Manager forWebSphere ApplicationServer

X X X

To install Tivoli Manager for WebSphere Application Server followthese procedures:

1. Install all prerequisite Tivoli software, gateways and endpoints.Refer to the Tivoli Manager for WebSphere Application ServerRelease Notes for prerequisite information.

2. Ensure that the WebSphere Application Server has been installedon the endpoints that you want to manage.

3. Back up the Tivoli database.

4. Install Tivoli Manager for WebSphere Application Server onTivoli management region servers, the event server in your Tivolimanagement region, and all gateways. See “Installing TivoliManager for WebSphere Application Server” for moreinformation.

Note: You must have at least install_product authority to installTivoli Manager for WebSphere Application Server.

5. Backup the Tivoli database using a different name from theprevious backup.

Installing Tivoli Manager for WebSphere ApplicationServer

You can install Tivoli Manager for WebSphere Application Serverfrom the Tivoli desktop or by using the winstall command. You canalso install Tivoli Manager for WebSphere Application Server usingthe Software Installation Service (SIS). For more information on SIS,refer to the Tivoli Software Installation Service User’s Guide.


2.In

stalling

Installing From the Tivoli DesktopTo install Tivoli Manager for WebSphere Application Server fromthe desktop, follow these steps:

1. From the Desktop menu, select Install —> Install Product todisplay the Install Product dialog.

2. Click Select Media to display the File Browser dialog, fromwhich you can specify the path to the installation media.

3. In the Path Name text field, enter the full path to the TivoliManager for WebSphere Application Server installation files.Usually, it is the path of the CD-ROM drive; however, you canplace the installation files on a network drive.

4. Click Set Path. The File Browser dialog displays the contentsof the specified media in the Files scrolling list.

5. Click Set Media & Close. The File Browser dialog is closed,and the Install Product dialog is displayed.

6. Select Tivoli Manager for WebSphere Application Server 1.1from the Select Product to Install scrolling list.

7. Select the target clients on which to install Tivoli Manager forWebSphere Application Server from the Available Clientsscrolling list and then click the left arrow. The selected clientsare moved to the Clients to Install On scrolling list.

Note: Install Tivoli Manager for WebSphere Application Serveron the Tivoli management region server, the event server,and on all gateways.

8. Click Install & Close. The Product Install window is displayed,listing the actions that will be taken when you continue theinstallation process.

9. Click Continue Install to begin the Tivoli Manager forWebSphere Application Server installation process. The ProductInstall window continues to display messages that show theprogress of the installation. After the Finished productinstallation message is displayed, you must look at the


messages in the task output dialog to determine whether theproduct installation was successful.

10. Click Close to close the Product Install window.

11. Refresh the desktop by selecting Refresh from the View menubar. The desktop displays the Tivoli Manager for WebSphereApplication Server icon.

The following objects are created in the Tivoli Manager forWebSphere Application Server policy region:

¶ WAS Indicators - indicator collection

¶ WAS 3.5 Servers - profile manager

¶ WAS Monitors- profile manager

¶ WAS Event Tasks - task library

¶ WAS Server Tasks - task library

¶ WAS Utility Tasks - task library

Note: When Tivoli Manager for WebSphere Application Server isinstalled, the following three log files are created and placedin the directory returned by the wtemp command:

¶ wasav_init.log

¶ AMS_WASAV_ALIDB_after.error.log

¶ AMS_WASAV_ALIDB_after.output.log

Using the winstall CommandTo install the Tivoli Manager for WebSphere Application Serverusing the winstall command, enter the following command from thecommand prompt:

winstall -c cdrom_path -s tmr_server -i WASAV.INDmanaged_node


2.In

stalling

where:

-c cdrom_pathThe full path name of the CD image.

-s tmr_serverThe name of the Tivoli management region server.

-i The index file, WASAV.IND, from which the Tivoli Managerfor WebSphere Application Server is to be installed.

managed_nodeSpecifies the managed node on which the product is to beinstalled. Multiple managed nodes can be specified. Ifmanaged nodes are not specified, the product will beinstalled on all managed nodes in the Tivoli managementregion.

Refer to the Tivoli Management Framework Reference Manual formore information about the winstall command.

UninstallingUse the wuninst command to remove Tivoli Manager forWebSphere Application Server from all nodes in the Tivolimanagement region.

To uninstall Tivoli Manager for WebSphere Application Server, dothe following:

1. Before removing the product from the Tivoli management region,run the Delete Endpoint Dependencies task to delete product filesfrom the endpoints. Refer to “Delete Endpoint Dependencies” onpage 48 for information on this task.

After you have removed the product from the Tivoli managementregion, you cannot run the Delete Endpoint Dependencies taskagain until you install the product again.

2. Back up the database and the Tivoli management region serverinstall directory before running the wuninst command.


3. Close the Tivoli Manager for WebSphere Application Serverwindows (for example, Add Monitors). If any windows are open,the task generated by the wuninst command will fail withtransaction errors.

4. Enter the following command from the command prompt:

wuninst AMS_WASAV node_name -rmfiles

where:

node_nameThe node from which to remove the product. Ifnode_name is the Tivoli management region server, theproduct is removed from the entire Tivoli managementregion.

-rmfilesIndicates that all product files are to be removed fromthe node specified by node_name.

Refer to the Tivoli Management Framework Reference Manualfor information on the wuninst command. Tivoli Manager forWebSphere Application Server does not require any options.

Note: The log file on the Tivoli management region server is calledwasav_uninstall.log and is written to the directory returnedby the wtemp command.


2.In

stalling

Getting Started with TivoliManager for WebSphereApplication Server

This chapter describes how to configure Tivoli Manager forWebSphere Application Server, which involves the followingprocedures:

1. Assigning the Tivoli Manager for WebSphere Application Serverauthorization to one or more Tivoli administrators as described in“Assigning Tivoli Manager for WebSphere Application ServerAuthorization” on page 14.

2. Configuring Tivoli Enterprise Console event handling, asdescribed in “Configuring Tivoli Enterprise Console EventHandling” on page 16.

3. Configuring the WebSphere Application Server endpoint, asdescribed in “Configure WAS Endpoint” on page 44.

4. Running the List Application Servers task to populate the filethat contains the names of the application servers, as described in“List Application Servers” on page 38.

5. Managing Tivoli Manager for WebSphere Application Server, asdescribed in “Managing WebSphere Application Servers” onpage 16.

3


3.G

etting

Started

Assigning Tivoli Manager for WebSphere ApplicationServer Authorization

When you install Tivoli Manager for WebSphere Application Server,two roles, wasav_senior and wasav_admin, are created.

All tasks require at least one of these roles to be assigned to theTivoli administrator who is running the task. In addition, some tasksrequire Tivoli authority as defined by Tivoli management regionroles. A Tivoli administrator must have the required Tivoli authorityand must have been assigned one of the Tivoli Manager forWebSphere Application Server roles to successfully run these tasksand processes. You can assign Tivoli Manager for WebSphereApplication Server authorization as Tivoli management region rolesor as resource roles, depending on local authorization requirements.

Assigning Tivoli Management Region Roles to a TivoliAdministrator

To assign Tivoli management region wasav_senior andwasav_admin roles to a Tivoli administrator, follow these steps:

1. From the desktop, double-click the Administrators icon todisplay the Administrators window.

2. Right-click the appropriate Administrator icon and select EditTMR Roles from the pop-up menu. The Set TMR Roles dialogis displayed.

3. From the Available Roles scrolling list, do the following:

a. Select either the wasav_senior or wasav_admin role, orboth.

b. Move the selected roles to the Current Roles scrolling listby clicking the left-arrow button.

4. Click Change and Close.

5. Exit the desktop.

6. Start the desktop again for the new roles to take effect.


Assigning Resource Roles to a Tivoli AdministratorTo add resource roles for a specific policy region to a Tivoliadministrator:

1. From the desktop, double-click the Administrators icon todisplay the Administrators window.

2. Right-click the appropriate Administrator icon and select EditResource Roles from the pop-up menu.

3. Select Tivoli Manager for WebSphere Application Server fromthe Resources scrolling list.

4. From the Available Roles scrolling list,

a. Select either the wasav_admin or wasav_senior role, orboth.

b. Move the selected roles to the Current Roles scrolling list byclicking the left arrow button.

5. Click Change and Close.

6. Exit the desktop.

7. Start the desktop again for the new roles to take effect.

8. To use the new roles as resource roles instead of TMR roles, dothe following:

a. Use the following command to add the Endpoint resource tothe current resources in the Tivoli Manager for WebSphereApplication Server policy region:wsetpr Endpoint "Tivoli Manager for WebSphere Application Server"

b. Link the endpoint to the policy region where the roles areassigned using the following command, where endpoint_labelis the name of the endpoint to be linked to the policy region:wln @Endpoint:endpoint_label @PolicyRegion:"Tivoli Manager forWebSphere Application Server"

c. Use the following command to synchronize the endpoint datathat is stored by the endpoint manager, gateways, and theendpoint:wep sync_gateways


3.G

etting

Started

Configuring Tivoli Enterprise Console EventHandling

Configuring Tivoli Enterprise Console event handling involves thefollowing procedures:

1. Use the Configure Event Server task to configure the TivoliEnterprise Console event server (event server) as described in“Configuring the Event Server” on page 20.

2. Use the Configure Event Console task to configure the TivoliEnterprise Console event console (event console) as described in“Configuring an Event Console” on page 23.

Configuring the Integration ServerThe Integration Server is installed and started by the Configure WASEndpoint task. Refer to “Configure WAS Endpoint” on page 44 moreinformation on configuring the Integration Server.

Managing WebSphere Application ServersThe following steps describe the procedures to manage yourWebSphere Application Server environment with Tivoli Manager forWebSphere Application Server:

1. Ensure that the WebSphere Application Server endpoint is asubscriber to the desired profile manager lists as described in“Subscribing Servers to a Profile Manager”.

2. Select and add WebSphere Application Server monitors and thendistribute them to selected endpoints. For more information, see“Monitoring WebSphere Application Server Resources” onpage 25.

3. Run any of the management tasks that are described in “Tasksfor Managing Tivoli Manager for WebSphere Application ServerResources” on page 37.

Subscribing Servers to a Profile ManagerTivoli Manager for WebSphere Application Server automaticallycreates profile managers to help you group servers for management.


Each profile manager has a list of subscribers that enables you to runtasks and monitors against all subscribers. The following profilemanagers are initially created:

¶ WAS 3.5 Servers

¶ WAS Monitors

Follow these steps to subscribe servers to a profile manager:

1. Right-click on one of the profile managers and selectSubscribers from the pop-up menu.

2. Select the desired endpoints from the Available to BecomeSubscribers scrolling list and move them to the CurrentSubscribers list by clicking the left-arrow button.

3. Click Set Subscriptions & Close to subscribe the servers to thelist.


3.G

etting

Started

Managing WebSphereApplication Server Events

This chapter describes how to manage WebSphere ApplicationServer events using tasks that are contained in the WAS EventTasks library. The WebSphere Application Server issues eventnotifications to describe events that affect WebSphere ApplicationServer resources. The Integration Server provided by Tivoli Managerfor WebSphere Application Server handles these events as follows:

¶ Queries WebSphere Application Server for the serious eventsthat are written to the WebSphere database

¶ Formats the events

¶ Maps each event to a Tivoli Enterprise Console severity

¶ Sends the events to the Tivoli Enterprise Console event server(event server) using the wpostemsg command

Tivoli Manager for WebSphere Application Server also provides aset of event classes that are used by the event server to categorizeand interpret events received from both the Integration Server andthe WebSphere Application Server monitors.

The following table lists the required roles and targets for the tasks:

Task Role Target

Configure Event Server senior event server

Configure Event Console senior event console

4


4.M

anag

ing

Even

ts

To work with WebSphere Application Server events at your eventconsole, you must configure both ends of the connection andconfigure the Tivoli Enterprise Console:

1. Configure the event server to recognize WebSphere ApplicationServer events and the process rules concerning those events. Formore information, see “Configuring the Event Server”.

2. Configure an event console to assign the newly created eventgroup to the appropriate event console. For more information, see“Configuring an Event Console” on page 23.

3. Run the Configure WAS Endpoint task to start the IntegrationServer with the desired settings. For more information see“Configure WAS Endpoint” on page 44.

Configuring the Event ServerThe Configure Event Server task configures an event server for theTivoli Manager for WebSphere Application Server. This task alsostops and starts the event server. Run the Configure Event Servertask against the managed node that is the event server. A log file,wasav_config_evtsvr.log, is automatically generated by this task andplaced in the directory returned by the wtemp command.

Note: A Tivoli administrator with at least global senior authority isrequired to run the Configure Event Server task.

The Configure Event Server task performs the following actions:

¶ Imports the Tivoli Manager for WebSphere Application Serverevent classes

¶ Imports the Tivoli Distributed Monitoring event classes if theyare not already present.

¶ Imports the Tivoli Manager for WebSphere Application Serverrule set.

¶ Compiles the rule base to incorporate new classes and rules.


¶ Creates a new event source for Tivoli Distributed Monitoring ifneeded.

¶ Creates an event source that is called WAS Events forWebSphere Application Server events.

¶ Creates a new event group that is called WAS Event Group.

¶ Updates the forwarding server location, if specified.

¶ Loads the new rule base.

¶ Stops and starts the event server to incorporate these changes.

You can configure only one event server for each Tivoli managementregion. When you have interconnected Tivoli management regions,run the Configure Event Server task against each Tivoli managementregion that contains an event server.

The Tivoli Manager for WebSphere Application Server includes a setof event classes and rules specific to WebSphere Application Server.Events forwarded by the Integration Server, as well as monitorevents, are both included in the WAS Event Group.

To set up your event server to process WebSphere Application Serverevents, follow these steps:

1. From the desktop, double-click the Tivoli Manager forWebSphere Application Server policy region to display thePolicy Region: Tivoli Manager for WebSphere Application Serverwindow.

2. Double-click the WAS Event Tasks icon to display the TaskLibrary: WAS Event Tasks window.

3. Double-click the Configure Event Server task icon andcomplete the Execute Task dialog. Set the Timeout Value on theExecute Task dialog to a value greater than the default to allowthe task to complete. For example, a value of 300 equals 5minutes and a value of 0 equals infinity.


4.M

anag

ing

Even

ts

4. Click Execute & Dismiss to display the Configure Event Serverdialog.

5. New (Or Existing) Rule Base Name. Enter the name for thenew or existing rule base in this field. The default name is WAS.Do not modify the Default rule base, which is named Default.The wlsrb command provides a list of all available rule bases.

Note: You should not change the default rule base, therefore donot enter Default in this field.

6. Rule Base to Clone (If New). Enter the rule base to clone inthis field. If you are creating a new rule base, enter the name ofthe rule base you want to clone. If you have not previouslycreated a new rule base, accept the default name, which isDefault.

7. Path for New Rule Base (If New). Enter the path for the newrule base in this field. If you are creating a new rule base, enterthe full path for where you want the new rule base to be created.The default value is ⁄usr⁄tec_rules⁄wasav. If you are not creatinga new rule base, leave this field blank.

8. Click Set and Execute to start the task. The Configure EventServer Output window displays the job status after the task iscompleted.


Configuring an Event ConsoleThe Configure Event Console task assigns the WAS Event Group tothe event console. This event group contains filters to display eventswith a source of WAS or SENTRY. The task must be run against themanaged node on which the event console is installed. The taskprompts you for the name of the event console to be configured andcontains the List Consoles button, which allows you to list the validevent consoles on the local Tivoli management region. The eventconsole name is the same name as the event console that alreadyexists on the administrator’s desktop. Run this task after running theConfigure Event Server task. A log file, wasav_config_console.log,is automatically generated by this task and placed in the directoryreturned by the wtemp command.

After running the Configure Event Console task, open the eventconsole. Windows are displayed showing the newly added eventgroup and event sources.

Filtering EventsWebSphere Application Server events that are forwarded by theIntegration Server and regarded as harmless or unlikely to requireaction can be suppressed from being displayed on the event console.The Tivoli Management Framework provides the following methodsfor you to filter out events that you do not want to see:

¶ You can specify that the event is not to be forwarded from theendpoint to the event server. In this case, you specify filtercriteria in the Configure WAS Endpoint task. Depending on thefrequency of the events, this option can decrease network traffic.Refer to “Configure WAS Endpoint” on page 44 for moreinformation.

¶ You can create new rules to exclude the event. When you dothis, the event will be forwarded to the event server, but will beeliminated by the rules engine. The Tivoli Enterprise ConsoleRule Builder’s Guide describes the steps for building andchanging rules.


4.M

anag

ing

Even

ts

¶ You can exclude classes of events using the event console’s userinterface. Refer to the Tivoli Enterprise Console User’s Guidefor more information.


Monitoring WebSphereApplication Server Resources

This chapter explains how to customize and use WebSphereApplication Server monitors. Tivoli Manager for WebSphereApplication Server provides a monitor collection to enable remotemonitoring of overall WebSphere Application Server performance.

Like any Tivoli Distributed Monitoring monitor, you can customize aWebSphere Application Server monitor. For example, you mightwant to set the severity or threshold of the monitors or you mightwant to add more monitors to the default set. For additionalinformation, see the Tivoli Distributed Monitoring User’s Guide.

Enabling Performance Monitoring in WebSphereTo ensure that the Tivoli Manager for WebSphere Application Servermonitors can monitor performance data, you must have theWebSphere Application Server collect performance data. Data iscollected for performance categories, each of which containscounters. Each performance category has an instrumentation levelwhich determines which counters are being collected for thatperformance category. Each counter has a cost rating (high, medium,low, or none), indicating its impact on an application’s performanceif data is collected for that counter. If a performance category has aninstrumentation level of high, for example, all counters in thatperformance category with a high cost rating and lower arecollected. The following table describes the instrumentation level

5


5.M

on

itorin

gR

esou

rces

required for each performance category:

Performance Category Instrumentation Level

Enterprise beans high

Enterprise bean methods* not applicable

Database connection pools medium

ORB thread pool high

Bean object pool* not applicable

Transactions* not applicable

Servlet engine high

Note: * = Tivoli Manager for WebSphere Application Server does notcurrently support these performance categories.

Refer to “Performance Monitoring Instrumentation Levels” onpage 97 for more details on instrumentation levels and how to setthem using the WebSphere Advanced Administrative Console.

Understanding the MonitorsTivoli Manager for WebSphere Application Server provides thefollowing set of monitors:

¶ Status Monitors

v Administration Server status

v Integration Server status

v Application Server status

¶ Performance Counter Monitors

v Database Connections

v Enterprise JavaBeans (EJB)

v HTTP

v Java Virtual Machine

v Servlets

v Thread Pools


Tivoli Manager for WebSphere Application Server provides theIntegration Server which provides the Tivoli integration with theWebSphere Advanced product. It is the conduit through which theperformance data flows back to the Tivoli Framework. WebSphereperformance data is gathered for each component. The depth towhich object performance data can be obtained is limited to thecontainer level. Thus, performance information for servers andapplication servers will be available, but not for the objects thatreside within application servers.

For performance data to be collected, the administration server,application server, and Integration Server must be running.

Notes:

1. Some monitors require you to enter the application server name.Click Server Name on the Edit Monitor dialog to select from alist of server names. If the list of names is empty, then the$DBDIR/was_servers file (on UNIX) or%DBDIR%\tmp\was_servers file (on Windows NT) is empty.To populate the list, run the List Application Servers task or editthe file directly. For more information on the List ApplicationServers task, refer to “Server Information Tasks” on page 38.

2. Specify parameters exactly as they are defined, includingcapitalization and spacing. If a monitor fails, -1 is returned forthe counter value and a message is displayed.

Monitors Configured at InstallationDuring installation, the Tivoli Manager for WebSphere ApplicationServer configures two monitors in the WebSphere Application Servermonitoring collection and adds them to the WAS MonitorsDistributed Monitoring profile. The two monitors are:

¶ Administration Server status

¶ Integration Server status

The properties of the Administration Server status and IntegrationServer status monitors are described below. Use the values as aguide to setting up the monitors. The monitors are enabled, but mustbe distributed to a valid endpoint before they become active.


5.M

on

itorin

gR

esou

rces

Response Level:/Triggered When Server:

Response Level: Triggered When Server:

warning comes up

critical goes down

critical is down

Default Action:If Tivoli Enterprise Console is installed, then an event isforwarded to the event server. Otherwise, a notice is sent tothe Sentry notice group and summary information is sent tothe WAS Monitors indicator collection.

Frequency:30 minutes

Status MonitorsThis section describes the monitors which check the status of theservers.

Administration Server StatusThe Administration Server status monitor returns the status of theadministration server as follows:

¶ up if the administration server is running

¶ down if the administration server is not running

¶ unknown if there is a problem obtaining the status

Note: This monitor uses the WebSphere wscp command, which canbe resource intensive. Therefore, it is recommended that youdo not run this monitor at small intervals of time.

Integration Server StatusThe Integration Server status monitor returns the status of theIntegration Server, which is monitoring the performance of theapplication server, as follows:

¶ up if the Integration Server is running

¶ down if the Integration Server is stopped



Application Server StatusThe Application Server status monitor returns the status of theapplication server as follows:

¶ up if the application server is running

¶ down if the application server is stopped


Note: This monitor uses the WebSphere wscp command, which canbe resource intensive. Therefore, it is recommended that youdo not run this monitor at small intervals of time.

The argument is:

Application Server NameThe name of the application server for which the status is tobe checked. Specify the application server name in thefollowing format:/Node:node_name/ApplicationServer:application_server_name/

For example:/Node:ramtuff/ApplicationServer:Default Server/

The Application Server Name can also be enclosed in braces({}).

Performance Counter MonitorsThis section describes the monitors that collect information on theperformance counters.

Database ConnectionsThe Database Connections monitor returns information on thedatabase connections.

The counters are:

CreatedReturns the number of connections created.


5.M

on

itorin

gR

esou

rces

Time maxedReturns the average percent of time the number ofconnections in the database pool has reached the maximumnumber.

Average Wait TimeReturns the average wait time needed, in milliseconds, toobtain a database connection.

Threads WaitingReturns the average number of threads waiting for a databaseconnection.

The arguments are:

Application Server NameThe name of the application server for which the status is tobe checked. Specify only the server name. If the name isspecified in the format that includes the node, then the servername is extracted and used.

Data SourceThe name of the Data Source to be checked.

EJBThe EJB monitor returns information on the Enterprise JavaBeans.

The counters are:

Method executionReturns the average response time on all methods of theremote interface for this bean.

Method CallsReturns the total bean method invocations.

Method Calls/MinuteReturns the number of bean method invocations per minute.

Method LoadsReturns the number of times the entity bean data was loaded.

The argument is:



HTTPThe HTTP monitor returns information on the HTTP sessions.

The counters are:

Active sessionsReturns the average number of concurrently active sessions.

Invalid sessionsReturns the number of sessions that are not valid.

The argument is:


JVMThe JVM monitor returns information on the Java Virtual Machinememory size.

The counters are:

Free memoryReturns the Java Virtual Machine free memory size.

Total memoryReturns the Java Virtual Machine total memory size.

The argument is:

Application Server NameThe name of the application server for which the status is to


5.M

on

itorin

gR

esou

rces

be checked. Specify only the server name. If the name isspecified in the format that includes the node, then the servername is extracted and used.

ServletsThe Servlets monitor returns information on the servlets.

The counters are:

Concurrent RequestsReturns the number of concurrent requests for the servlet.

Currently loadedReturns the current number of loaded servlets.

RequestsReturns the total number of requests for the servlet.

Response timeReturns the amount of time in milliseconds taken for theservlet in the Web application to perform a request.

The argument is:


Thread PoolsThe Thread Pools monitor returns information on the thread pools.

The counters are:

CreatedReturns the number of threads created.

Average activeReturns the average number of active threads in the threadpool.


Average totalReturns the average number of threads (active and idle) inthe thread pool.

Percentage maximumReturns the average percent of time that the number ofthreads in the thread pool reached or exceeded the maximumnumber.

The argument is:


Note: Specify parameters exactly as they are defined, includingcapitalization and spacing. If a monitor fails, -1 is returnedfor the counter value and a message is displayed.

For additional information on monitors, refer to the TivoliDistributed Monitoring User’s Guide.

Adding MonitorsTo add a monitor to those already provided by WebSphereApplication Server, do the following:

1. From the Tivoli desktop, double-click the Tivoli Manager forWebSphere Application Server icon. The Policy Region: TivoliManager for WebSphere Application Server window is displayed.

2. Double-click the WAS Monitors icon. The Profile Managerwindow is displayed.

3. From the Profiles group box, double-click the WAS Monitorsicon to display the TME 10 Distributed Monitoring ProfileProperties window.


5.M

on

itorin

gR

esou

rces

4. Click Add Monitor to display the Add Monitor to TME 10Distributed Monitoring Profile dialog.

5. Select a collection name for which you want to display theavailable monitors, such as WebSphere Application Server inthe Monitoring Collections scrolling list. Select the monitor youwant to add, such as Administration Server status monitor, inthe Monitoring Sources scrolling list.

6. When the selected monitor requires an argument, a text fieldbecomes available in the Monitor Arguments area of thewindow. When an argument is required, either enter it directly


into the text field from the keyboard or select it from a list. Todisplay the list, click the button to the right of the text field andselect the argument.

7. Click Add Empty to add the selected monitoring source. TheEdit Monitor dialog is displayed.

8. If you check the Change Icon box, the WAS Indicators icon inthe Tivoli Manager for WebSphere Application Server policyregion will change when the threshold is reached. When themonitor is triggered, the response level determines the new iconimage. Tivoli provides standard icons that correspond to theNormal, Warning, Severe, and Critical response levels. Summaryinformation is logged in the WAS Monitors indicator log.

9. Enter the information in the Edit Monitor dialog and then clickChange & Close. The monitor is added and the TME 10Distributed Monitoring Profile Properties window is displayed.


5.M

on

itorin

gR

esou

rces

10. To add another monitor, repeat steps 4 through 9.

11. When you are done adding monitors, select Save from theProfile menu in the TME 10 Distributed Monitoring ProfileProperties window to save the added monitor information.

12. Select Distribution Defaults from the Profile menu in theTME 10 Distributed Monitoring Profile Properties window andset the following and click Set and Close:

¶ Distribute To: All Levels Of Subscribers

¶ Distribute Will: Make subscribers’ profile an EXACTCOPY of this profile

13. Select Close from the Profile menu in the TME 10 DistributedMonitoring Profile Properties window.

14. The Confirm dialog is displayed. Click Save & Exit.

15. After you have added and edited the appropriate monitors,distribute the profiles to begin monitoring. To distribute themonitor profile:

a. Select the desired profile icon in the Profiles area of theProfile Manager window.

b. Drag the icon to the desired subscriber icon in theSubscribers area.

Note: Arguments are both space and case sensitive. When you enterarguments for monitors manually, it is important that youenter the arguments exactly. If a monitor fails, -1 is returnedfor the counter value and a message is displayed.


Tasks for Managing TivoliManager for WebSphereApplication Server Resources

Tivoli Manager for WebSphere Application Server includes thefollowing task libraries that are used to manage WebSphereApplication Server resources and monitors:

¶ WAS Server Tasks - These tasks control the servers and aredescribed in “WAS Server Tasks” on page 38. These tasks canalso be run using the Execute option on the Task menu on theevent console.

¶ WAS Utility Tasks - These tasks control the endpoints and aredescribed in “WAS Utility Tasks” on page 42.

¶ WAS Event Tasks - These tasks manage the Tivoli EnterpriseConsole and are described in “Managing WebSphere ApplicationServer Events” on page 19.

When you start a task, specify the endpoints on which to run thetask.

If there are task input fields, select Task Description from the taskdialog to view information about the task window’s text fields. Forcomplete instructions on how to use tasks and jobs, refer to theTivoli Management Framework User’s Guide.

6


6.Tasks

WAS Server TasksTivoli Manager for WebSphere Application Server provides thefollowing types of tasks for managing the administration server,application server, and Integration Server:

Type of Task Task Role Target

ServerInformation

Administration Server StatusList Application Servers*Application Server Status *

wasav_admin orwasav_senior

Endpoint

ServerManagement

Start Administration ServerStop Administration Server

wasav_senior Endpoint

Start Application Server *Stop Application Server*Start Integration Server *Stop Integration Server

wasav_admin orwasav_senior

Endpoint

Note: * = These tasks require that the Administration Server is running.

Note: See “Troubleshooting” on page 85 to help solve problemsencountered when running tasks and jobs from the desktop.

Server Information TasksThis section describes the tasks that provide server information.

Administration Server StatusThe Administration Server Status task displays the status of both theadministration server and the Integration Server. For each server, thistask returns the following:

¶ up if the server is running

¶ down if the server is stopped

¶ unknown if there is a problem obtaining status

List Application ServersThe List Application Servers task displays the list of applicationservers currently defined in the WebSphere domain. Run this taskagainst only one node in the domain. Use this list as a source ofinput to several monitors and the Start Application Server, Stop


Application Server, and Application Server Status tasks, by savingthe list to the $DBDIR/was_servers file (on UNIX) or%DBDIR%\tmp\was_servers file (on Windows NT). In these tasksand monitors, when you click the Server Name button, the list ofapplication servers is presented.

When saving data to the was_servers file, remove lines that are notserver names, and ensure that there are no extraneous or controlcharacters at the end of the lines containing server names. If so, editthe file and remove the characters.

Application Server StatusThe Application Server Status task returns the status of theapplication server and can be run against only one application serverat a time. This task returns the following:

¶ up if the application server is running

¶ down if the application server is stopped

¶ unknown if there is a problem obtaining status

The argument is:

Application Server NameThe name of the application server for which the status is tobe checked. Specify the application server name in thefollowing format:/Node:node_name/ApplicationServer:application_server_name/



Server Management TasksThis section describes the tasks that enable you to manageWebSphere servers.


6.Tasks

Note: Some tasks require you to enter the Application Server name.Select the Server Name button to select from a list of servernames. If the list of names is empty, then the$DBDIR/was_servers file (on UNIX) or%DBDIR%\tmp\was_servers file (on Windows NT) isempty. To populate the list, run the List Application Serverstask and place the results in the file or edit the file directly.For more information on the List Application Servers task,refer to “Server Information Tasks” on page 38.

Start Administration ServerThe Start Administration Server task issues the command to start theadministration server. When the administration server is stopped andstarted, you must stop and start the Integration Server to synchronizeit with the administration server.

The administration server can take some time to initialize. Beforerunning tasks and monitors that require the administration server tobe up, run the Administration Server Status task to verify that theadministration server is up.

Stop Administration ServerThe Stop Administration Server task issues the command to stop theadministration server. The Integration Server is stopped when theadministration server is stopped.

Note: If administration server is stopped and the Integration Serverhas been configured to send events to an event server, theIntegration Server detects that the administration server hasstopped and shuts itself down. The monitor_admin_up_wasrule causes the event server to start the Integration Serverwhen an event is received from the Administration Serverstatus monitor indicating that the administration server hasstarted (monitor value has changed to up. In order to use thisrule, the Administration Server status monitor must bedeployed to the endpoint and must be configured to sendevents to the event server. See “Rules for Tivoli Manager forWebSphere Application Server Events” on page 57 for moreinformation.


Start Application ServerThe Start Application Server task starts an application server and canbe run against only one application server at a time.

The argument is:

Application Server NameThe name of the application server to be started. Specify theapplication server name in the following format:/Node:node_name/ApplicationServer:application_server_name/



Stop Application ServerThe Stop Application Server task stops an application server and canbe run against only one application server at a time.

The argument is:

Application Server NameThe name of the application server to be stopped. Specifythe application server name in the following format:/Node:node_name/ApplicationServer:application_server_name/



Start Integration ServerThe Start Integration Server task starts the Integration Server whichis needed for running the performance monitors and forwardingWebSphere events to the event server. An event is then sent to theevent console to inform you that the Integration Server is forwardingevents.


6.Tasks

Note: Before running this task, ensure that the administration serveris running.

Stop Integration ServerThe Stop Integration Server task stops the Integration Server. If theserver is stopped, performance monitors cannot run properly andWebSphere events are not forwarded to the event server. This taskreturns -1 for the counter value and it displays a message.

WAS Utility TasksTivoli Manager for WebSphere Application Server provides utilitytasks to help your endpoints. Start the following tasks from the WASUtility Tasks library in the Tivoli Manager for WebSphereApplication Server policy region on the desktop.

Task Role Target

Start Debugging wasav_admin orwasav_senior

Endpoint

Stop Debugging wasav_admin orwasav_senior

Endpoint

Start Monitors wasav_admin orwasav_senior

Endpoint

Stop Monitors wasav_admin orwasav_senior

Endpoint

Configure WAS Endpoint wasav_admin orwasav_senior

Endpoint

Delete Endpoint Dependencies wasav_admin orwasav_senior

Endpoint

List Endpoint Logs wasav_admin orwasav_senior

Endpoint

Delete Endpoint Logs wasav_admin orwasav_senior

Endpoint

Display WAS Endpoint Configuration wasav_admin orwasav_senior

Endpoint


Start DebuggingThe Start Debugging task turns on debug tracing for all the tasks andmonitors shipped with Tivoli Manager for WebSphere ApplicationServer. Use this task to resolve problems if a task or monitor is notrunning properly. Debug tracing is turned on for the endpoint againstwhich the Start Debugging task is run. A separate log file is writtento a temporary directory for each task or monitor run while debugtracing is on.

The Configure Event Server, Configure Event Console, andConfigure WAS Endpoint tasks write output to a log file regardlessof whether debugging has been enabled with the Start Debuggingtask. All other tasks and monitors write output to a log file only ifthe Start Debugging task has been run.

The Configure Event Server and Configure Event Console tasksautomatically generate a log file and place it in the directoryreturned by the wtemp command. The log files are as follows:

¶ The Configure Event Server task writes output to thewasav_config_evtsvr.log file.

¶ The Configure Event Console task writes output to thewasav_config_console.log file.

All other tasks and monitors write output to separate log files on theendpoint. These files are located in the $LCF_DATDIR/WASAVdirectory (on UNIX endpoints) or %LCF_DATDIR%\WASAVdirectory (on Windows NT endpoints). For example:

¶ The Application Server Status task writes output to thewasav_server_status.log file.

¶ The Configure WAS Endpoint task writes output to thewasav_config_tivwasav.log file.

Stop DebuggingThe Stop Debugging task turns off debug tracing for all the tasksand monitors shipped with Tivoli Manager for WebSphereApplication Server. Debug tracing is turned off on the endpointagainst which the Stop Debugging task is run. The configure tasks


6.Tasks

(Configure Event Server, Configure Event Console, and ConfigureWAS Endpoint) create debug logs regardless of whether the StopDebugging task has been run.

Start MonitorsThe Start Monitors task enables all the monitors from only theWebSphere Application Server collection that have been distributedto the endpoint. Other monitor instances on the endpoint are notenabled. Use this task to quickly enable all of the WebSphereApplication Server monitors after they have been stopped.

Note: This task does not change the status displayed on theDistributed Profile Properties window. The monitors displayedon this window might have been distributed to endpointsagainst which you have run the Start Monitors task.

Stop MonitorsThe Stop Monitors task disables all the monitors from only theWebSphere Application Server collection that have been distributedto the endpoint. Other monitor instances on the server are notdisabled. Use this task to quickly disable all of the WebSphereApplication Server monitors when a server is down.

Note: This task does not change the status displayed on theDistributed Profile Properties window. The monitors displayedon this window might have been distributed to endpointsagainst which you have run the Stop Monitors task.

Configure WAS EndpointThe Configure WAS Endpoint task stores both WebSphereApplication Server and Tivoli Manager for WebSphere ApplicationServer configuration information, and installs and starts theIntegration Server.

When security is enabled for WebSphere Application Server, youmust create a security properties file (for example, sas.wscp.props)for the wscp client so that it can be authenticated by the server. Thisfile is located in the properties subdirectory in the directory inwhich you installed the WebSphere Application Server product.


Refer to the WebSphere product documentation for more informationon the wscp command.

Note: If security is enabled on the WebSphere Application Server,security audit messages will interfere with the wscpcommands that Tivoli Manager for WebSphere ApplicationServer issues. To redirect the security audit messages, add thefollowing lines to the sas.wscp.props file that you created:com.ibm.CORBA.securityTraceOutput=$(WASROOT)/logs/sastrace.log

com.ibm.CORBA.securityOuputMode=file

The audit messages cause the log file to increase in size. Toensure that the log file does not grow too large, you mustmonitor its size. Refer to the Tivoli Manager for WebSphereApplication Server Release Notes for information on how tomanage this problem.

To configure the Integration Server, follow these steps:

1. Ensure that the administration server is running.

2. From the Tivoli desktop, double-click the Tivoli Manager forWebSphere Application Server icon to display the PolicyRegion: Tivoli Manager for WebSphere Application Serverwindow.

3. Double-click the WAS Utility Tasks icon to display the TaskLibrary: WAS Utility Tasks window.

4. Double-click the Configure WAS Endpoint icon and completethe displayed Execute Task dialog.


6.Tasks

5. Click Execute & Dismiss to display the Configure WASEndpoint dialog.

6. Install path of WebSphere Application Server. Enter theinstall path of WebSphere Application Server. This is known asWAS_HOME. It is the directory where the application serversource and binaries are located. If this field is left blank, it isset to the default directory. The default directories are:

¶ For Solaris or HP: /opt/WebSphere/AppServer

¶ For AIX: /usr/WebSphere/AppServer

¶ For Windows NT: c:\WebSphere\AppServer

Note: If the Configure WAS Endpoint task is run againstmultiple endpoints, ensure that WAS_HOME is the sameon all endpoints.

7. Integration Server Port. Enter a port number which theIntegration Server can use for communication. This is the portused for performance monitoring. The default port is 57392.

8. Event Server (name registry format). Enter the name of theevent server that events will be forwarded to. The Integration


Server uses this parameter to specify where to forwardWebSphere events. Enter one of the following:

¶ Event server name in name registry format. To identify theevent server that is part of the same Tivoli managementregion, the value is @EventServer. For an event server in adifferent Tivoli management region, the value is@EventServer#region_name

where region_name is the TMR_Server_Host region.

¶ NOTECSERVER. If you are not using Tivoli EnterpriseConsole and do not want events to be forwarded to theevent server, enter NOTECSERVER. If you enterNOTECSERVER, the Integration Server will not attempt toget serious events from the administration server. If ACF isnot installed, the Configure WAS Endpoints task isconfigured with NOTECSERVER.

¶ Blank. The @EventServer default value is used.

9. Security Properties File.

¶ If security is not enabled, leave this field blank.

¶ If security is enabled, enter the name of the securitiesproperties file without specifying the path.

10. Forward Fatal events. Indicate whether you want theIntegration Server to forward WebSphere fatal events:

¶ If you click Yes, the Integration Server forwards FATALevents to Tivoli Enterprise Console with a severity ofFATAL.

¶ If you click No, FATAL events are not forwarded.

11. Forward Terminate events. Indicate whether you want theIntegration Server to forward WebSphere terminate events:

¶ If you click Yes, the Integration Server forwardsTERMINATE events to Tivoli Enterprise Console with aseverity of CRITICAL.


6.Tasks

¶ If you click No, then TERMINATE events are notforwarded.

12. Forward Error events. Indicate whether you want theIntegration Server to forward WebSphere error events:

¶ If you click Yes the Integration Server forwards ERRORevents to Tivoli Enterprise Console with a severity ofCRITICAL.

¶ If you click No, then ERROR events are not forwarded.

13. Forward Warning events. Indicate whether you want theIntegration Server to forward WebSphere warning events:

¶ If you click Yes, the Integration Server forwardsWARNING events to Tivoli Enterprise Console with aseverity of WARNING.

¶ If you click No, then WARNING events are not forwarded.

14. Forward Audit events. Indicate whether you want theIntegration Server to forward WebSphere audit events:

¶ If you click Yes, the Integration Server forwards AUDITevents to Tivoli Enterprise Console with a severity ofHARMLESS.

¶ If you click No, then AUDIT events are not forwarded.Because there are a large number of AUDIT events, and thenature of these events is not of special interest, the defaultfor the Integration Server at start up is to not send them.

Delete Endpoint DependenciesThe Delete Endpoint Dependencies task deletes all supporting files(such as logs, message catalogs, executables, and so on) that theTivoli Manager for WebSphere Application Server has put on thetargeted endpoints. This task also disables, but does not delete, anyprobes that were distributed from the WebSphere Application Servermonitoring collection to the specified endpoints. The monitordefinitions are not disabled on the Tivoli management region. TheDelete Endpoint Dependencies task also invokes the Stop Integration


Server task. If the Integration Server is not installed or not running,you can ignore the error message that you receive when the StopIntegration Server task is run.

If you run another task against an endpoint from which thedependencies were deleted, the product files from WebSphereApplication Server will be distributed again to the endpoint. Theneither run the Start Monitors task or distribute the monitors again inorder to restart the monitors. If you do not intend to use thisendpoint again, unsubscribe it from any Profile Managers to which itis subscribed and delete the probes using the wdelprb command.Refer to the Tivoli Distributed Monitoring User’s Guide for moreinformation.

If you do not confirm the delete, the files are not deleted and thetask will be reported as successful. If debug is on when you run thistask, the associated log files remain on the endpoint. Rerun this taskto remove the wasav_delete_utils.log and thewasav_stop_tis_server.log files.

List Endpoint LogsThe List Endpoint Logs task returns the list of debug logs, that arecurrently on the endpoint, for Tivoli Manager for WebSphereApplication Server. This task also returns the contents of debug logsif the List Log Contents field is set to Yes.

All Tivoli Manager for WebSphere Application Server tasks andmonitors which are run against an endpoint, write output to separatelog files in the $LCF_DATDIR/WASAV directory (for UNIX) or%LCF_DATDIR%\WASAV directory (for Windows NT) on theendpoint. For example:




6.Tasks

Delete Endpoint LogsThe Delete Endpoint Logs task deletes the debug logs that arecurrently on the endpoint, for Tivoli Manager for WebSphereApplication Server. Since this task deletes all files with the .logextension, it does not return a debug log regardless of whether theStart Debugging task has been run.

Display WAS Endpoint ConfigurationThe Display WAS Endpoint Configuration task displays theconfiguration settings for the WebSphere Application Serverendpoint. You can set these using the Configure WAS Endpoint task.

Displaying TasksTo display the tasks that Tivoli Manager for WebSphere ApplicationServer provides, follow these steps:

1. From the desktop, double-click the Tivoli Manager forWebSphere Application Server icon to display the PolicyRegion: Tivoli Manager for WebSphere Application Serverwindow.

2. To display the available Tivoli Manager for WebSphereApplication Server tasks, double-click the task library icon (WASServer Tasks, WAS Utility Tasks, or WAS Event Tasks) thatcontains the tasks you want to display. For example, if youdouble-click on the WAS Server Tasks icon, the Task Library:WAS Server Tasks window is displayed listing the server tasksprovided by Tivoli Manager for WebSphere Application Server.


Running TasksTo run a task, follow these steps:


6.Tasks

1. Double-click the task icon and complete the fields in the ExecuteTask dialog.

2. Click Execute & Dismiss to start the task. When a dialog ispresented, enter the information and then click Set & Execute tostart the task.


A window showing the output from the task is displayed.


6.Tasks

Event Classes and Rules

This appendix contains a list of the event classes and rules that theTivoli Manager for WebSphere Application Server defines, whichapply to Tivoli Enterprise Console.

Tivoli Manager for WebSphere Application ServerEvent Classes

Events are received from Tivoli Distributed Monitoring monitors andthe WebSphere Application Server. These events are then forwardedto the Tivoli Enterprise Console.

Distributed Monitoring EventsWAS_Monitors is a superclass definition for all WebSphereApplication Server monitor events. The following table lists themonitors that Tivoli Manager for WebSphere Application Serverprovides and their corresponding event class name as defined in thewasav_monitors.baroc file.

Monitor Name Event Class

Administration Server status WAS_adminstat

Integration Server status WAS_tisstat

Application Server status WAS_applstat

Database connections - created WAS_dbcrt

Database connections - time maxed WAS_dbmax

Database connections - average wait time WAS_dbwait

A


A.

Even

tC

lassesan

dR

ules

Monitor Name Event Class

Database connections - threads waiting WAS_dbthrd

EJB - method execution WAS_ejbmeth

EJB - method calls WAS_ejbmethcalls

EJB - method calls/minute WAS_ejbmethrate

EJB - method loads WAS_ejbmethloads

HTTP - active sessions WAS_httpact

HTTP - invalid sessions WAS_httpinv

JVM - free memory WAS_jvmfree

JVM - total memory WAS_jvmtot

Servlets - concurrent requests WAS_servconcurr

Servlets - currently loaded WAS_servload

Servlets - requests WAS_servreq

Servlets - response time WAS_servresp

Thread pools - created WAS_thrdcrt

Thread pools - average active WAS_thrdact

Thread pools - average total WAS_thrdtot

Thread pools - percentage maximum WAS_thrdprcnt

WebSphere Application Server EventsWAS_Event is a superclass definition for all WebSphere ApplicationServer events that are forwarded from the Integration Server on theendpoint.

When the Integration Server receives an event that is generated bythe WebSphere Application Server application, it maps fields in theWebSphere Application Server-generated event to Tivoli EnterpriseConsole event slots.

The following is an example of a WebSphere Application Serverevent. The slots that are shown in bold font contain data that ismapped from the original events in WebSphere.WAS_Event;

server_handle=1;date_reception=940273971;


event_handle=1;source=WAS;sub_source=WAS;origin=146.84.172.85;sub_origin='Default Server';hostname=tjevans;adapter_host=";status=OPEN;administrator='';acl=[ admin];severity=HARMLESS;date='Oct 18 15:12:50 1999';duration=0;msg='Servlet.unload.initiated:. jsp10;msg_catalog=";msg_index=0;num_actions=0;credibility=0;repeat_count=0;cause_date_reception=0;cause_event_handle=0;WAS_id=1466;WAS_time=’10/26/00 11:48 AM’;WAS_node=pinball;WAS_server='Default Server';WAS_threadId=a2671ee9;WAS_source=com.id.servlet.engine.webapp.ServletInstance;

END

Rules for Tivoli Manager for WebSphere ApplicationServer Events

The Tivoli Enterprise Console includes a rules engine that processesevents according to a set of rules that are provided by applications oradded by users. Tivoli Manager for WebSphere Application Serversupplies a rule base, which is a set of rules that provide correlationof related events. You can change these rules and also write rulesthat are tailored for your installation. See the Tivoli EnterpriseConsole Rule Builder’s Guide for more information on how to usethe Tivoli Enterprise Console graphical rule editor.

Distributed Monitoring RulesThe wasav_monitors.rls file contains a set of rules for theWAS_Monitors class of events that are sent from the monitors. Thisrule set uses the classes from the was_monitors.baroc file.


A.

Even

tC

lassesan

dR

ules

The WAS_Monitors class event processing rules that are providedwith the Tivoli Manager for WebSphere Application Server are asfollows:

dup_monitor_wasThis rule removes duplicate WebSphere Application Servermonitor events. A duplicate event is defined as an eventreceived at the event server within 5 minutes of the previousevent that has the slot values for the monitor, probe_arg,collection, sub_source, severity, hostname, value, and info.When a duplicate event occurs, the new event is droppedand the repeat_count is increased by one.

timeharmless_monitor_wasThis rule sets a timer on each harmless event to 15 minutes.A timer rule closes the event when the timer expires.

closeharmless_monitor_wasThis rule closes harmless events after 15 minutes, as set bythe timeharmless_monitor_was rule.

close_status_wasThis rule closes events as follows for the Application Serverstatus, Administration Server status, and Integration Serverstatus monitors:

¶ If an event is received indicating that the server is up,this rule closes out the previous down event for thatserver

¶ If an event is received indicating that the server is down,this rule closes out the previous up event for that server

monitor_events_wasThis rule places the application server name into thesub_origin slot in the event. This allows the applicationserver name to be displayed from the event console windowif the user has specified that the Sub-Origin field is to bedisplayed.

monitor_admin_up_wasThis rule runs the Start Integration Server task when an


event from the Administration Server status task indicatesthat the status of the administration server has changed toup.

WebSphere Application Server RulesThe wasav_events.rls file contains a set of rules for the WAS_Eventclass of events that are sent from the Integration Server. This rule setuses the classes from the wasav_events.baroc file.

The WAS_Event class event processing rules that are provided withthe Tivoli Manager for WebSphere Application Server are as follows:

dup_wasThis rule removes duplicate WebSphere Application Serverevents. A duplicate event is defined as an event received atthe event server within five minutes of the previous eventthat has the same slot values for the hostname, msg,WAS_node, WAS_server, and WAS_source. When a duplicateevent occurs, the new event is dropped and the repeat_countslot on the previous event is increased by one.

timeharmless_wasThis rule sets a timer on each harmless event to 15 minutes.A timer rule will close the event when the timer expires.

closeharmless_wasThis rule closes harmless events after 15 minutes, as set bythe timeharmless_was rule.

The TME 10 Enterprise Console Rule Builder’s Guide describes thesteps for building and changing rules.


A.

Even

tC

lassesan

dR

ules

Messages

This appendix describes the messages that Tivoli Manager forWebSphere Application Server produces.

IZY0001E Task failed

Source: Tasks

Cause: Explained in other messages.

User Response: Check other messages.

IZY0002I Task complete

Source: Tasks

Cause: Informational

User Response: None

IZY0003E This task must be run on an endpoint.

Source: Tasks

Cause: Attempted to execute a task on a managed node.

User Response: Run the task against an endpoint.

IZY0004I Log information is written to: FileName

Source: Tasks that have debugging set on


User Response: None

B


B.

Messag

es

IZY0005I Configure EventConsole Complete.

Source: Configure Event Console task


User Response: None

IZY0006I EventGroupName already assigned to EventConsole.



User Response: None

IZY0007I Assigned EventGroupName to EventConsole.



User Response: None

IZY0008E Failed to assign EventGroupName to EventConsole. Ensurethat task is run against the event server.


Cause: Task run against managed node that is not the TEC server

User Response: Run the task against the event server.

IZY0009E Command Failed...

Source: Configure Event Console, Configure Event Server tasks

Cause: General failure.

User Response: Check log for other messages.

IZY0010I The last few lines of the log file FileName are...

Source: Configure Event Console, Configure Event Server tasks


User Response: None


IZY0011I Rulebase rule base already exists, will update it. Clone rulebase will be ignored.

Source: Configure Event Server task


User Response: None

IZY0012I Clone rule base Rulebaseexists.



User Response: None

IZY0013I Created Rulebase



User Response: None

IZY0014I Sentry classes already installed.



User Response: None

IZY0015I Sentry classes have not been installed, adding them.



User Response: None

IZY0016I Rulebase compiles successfully.



User Response: None


B.

Messag

es

IZY0017I Created Rulebase rule base.



User Response: None

IZY0018I Copied CloneRulebase rule base to Rulebase.



User Response: None

IZY0019I Imported ClassFile to Rulebase rule base.



User Response: None

IZY0020I Stopped event server.



User Response: None

IZY0021I Restarted event server.



User Response: None

IZY0022I Configuring event server...



User Response: None


IZY0023I Rulefile is already in (Rulebase) rule base.



User Response: None

IZY0024I Will delete and import it again to pick up any new rules.



User Response: None

IZY0025I Created EventSource event source.



User Response: None

IZY0026I EventSource event source already exists.



User Response: None

IZY0027I Removed EventSource.



User Response: None

IZY0028I Loaded Rulebase rule base.



User Response: None


B.

Messag

es

IZY0029I Copied rule callback script.



User Response: None

IZY0030I Creating event group.



User Response: None

IZY0031I The WAS Event Group created successfully.



User Response: None

IZY0032I The WAS Event Group already exists.



User Response: None

IZY0033E A rule base must be defined.


Cause: A rule base name was not entered in the Configure Event Serverdialog.

User Response: Run the task again and supply a new or existing rule basename.


IZY0034E Clone rule base must be defined.


Cause: A new rule base was specified on the Configure Event Serverdialog but no Rule Base to Clone was entered.

User Response: Run the task again and supply an existing rule base toclone or specify an existing rule base.

IZY0035E Clone rule base (Rulebase) must already exist.


Cause: A new Rule Base was specified, but the Rule Base to Clone doesnot exist.

User Response: Run the task again and supply an existing rule base toclone.

IZY0036E Cannot create new rule base path.


Cause: Unable to issue mkdir command.

User Response: Check for other diagnostic messages.

IZY0037E Rulebase does not compile.


Cause: One or more rules in the rule base failed to compile.

User Response: Check the log for the rules that did not compile, correctthe rules, and rerun the task.

IZY0038E Failed to create Rulebase rule base.


Cause: The wcrtrb command encountered a problem.

User Response: Check the log for the error, correct it, and run the taskagain.


B.

Messag

es

IZY0039E Failed to copy CloneRulebase rule base to Rulebase.


Cause: The wcprb command encountered a problem.


IZY0040E Failed to import Rulefile to Rulebase rule base.


Cause: The wimprbclass command encountered a problem.


IZY0041E Failed to create EventSource event source.


Cause: The wcrtsrc command encountered a problem.


IZY0042E Failed to delete EventSource event source.


Cause: The wdelsrc command encountered a problem.


IZY0043E Failed to load Rulebase into Event Server


Cause: The wloadrb command encountered a problem.



IZY0044E Failed to create event group.


Cause: The wcrteg command encountered a problem.


IZY0045E Failed to add a filter to the event group.


Cause: The waddegflt command encountered a problem.


IZY0046E Failed to Stop Event Server. Event Server must berestarted before installation is complete.


Cause: The wstopesvr command encountered a problem.

User Response: Stop (wstopesvr) and start (wstartesvr) the event serverfrom the command line.

IZY0047E This host is not an event server.


Cause: The task was not run against the event server.

User Response: Run the task again against the event server.

IZY0048E Error locating Rulebase rule base directory: Directory


Cause: The wlsrb command encountered a problem.



B.

Messag

es

IZY0049E Cannot locate baroc file.


Cause: Cannot find the baroc files. Possible installation error or files mayhave been removed.

User Response: Check the debug log. Check installation log files andrestore files if needed. Run the task again.

IZY0050I The current debug setting for endpoint is: ON.

Source: List Endpoint Logs, Delete Endpoint Logs tasks


User Response: None

IZY0051I The current debug setting for endpoint is: OFF.



User Response: None

IZY0052I There are currently no debug logs for endpoint.



User Response: None

IZY0053I The current debug logs are...



User Response: None

IZY0054E Deleting debug logs failed on endpoint.

Source: Delete Endpoint Logs task

Cause: Remove (rm) command failed for one of the files

User Response: Check the output, correct the error, and run the taskagain.


IZY0055I Deleting debug logs complete on endpoint.



User Response: None

IZY0056I Deleting debug logs....



User Response: None

IZY0057E Error stopping monitors, rc= ReturnCode.

Source: Stop Monitors task

Cause: Check log and return code from the wdisprv command.

User Response: Correct problem and run the task again.

IZY0058I Monitors stopped.

Source: Stop Monitors task


User Response: None

IZY0059I Debugging turned off.

Source: Stop Debugging task


User Response: None

IZY0060I Debugging turned on.

Source: Start Debugging task


User Response: None


B.

Messag

es

IZY0061I Monitors started.

Source: Start Monitors task


User Response: None

IZY0062E Error starting monitors, rc= ReturnCode.

Source: Start Monitors task

Cause: Check log and return code from wenblprb command.

User Response: Correct problem and run the task again.

IZY0063I The values of environment variables are:

Source: Start Debugging task


User Response: None

IZY0064I No monitors currently distributed.

Source: Stop Monitors, Start Monitors tasks


User Response: None

IZY0065I The configuration setting for Endpoint are:

Source: Display WAS Endpoint Configuration task


User Response: None


IZY0066E The java version indicates this is not a supported version ofWebSphere Application Server.

Source: Configure WAS Endpoint task

Cause: The java version on the endpoint was not 1.2 or higher, whichmeans that it is not WebSphere Application Server 3.5. Tivoli Manager forWebSphere Application Server 1.1 supports only WebSphere ApplicationServer 3.5. This is followed by message IZY0067I and the result of thejava version command.

User Response: Run the task against endpoints with the supported versionof WebSphere Application Server.

IZY0067I Tivoli Manager for WebSphere Application Server supportsWebSphere Application Server 3.5.



User Response: This message appears with IZY0066E. Refer to thatmessage.

IZY0069E The security properties file filename was not found.


Cause: The securities properties file specified by the user was not foundin the properties subdirectory in the WebSphere Application Server installdirectory.

User Response: Specify a valid properties file and run the task again.

IZY0070I The Server server has been started.

Source: Start Application Server, Start Integration Server, Configure WASEndpoint tasks


User Response: None


B.

Messag

es

IZY0071E The Integration Server was NOT started; return code =ReturnCode.

Source: Start Integration Server task

Cause: Specified in ReturnCode.

User Response: Correct the error and run the task again.

IZY0072I The Server server has been stopped.

Source: Stop Application Server, Stop Integration Server tasks


User Response: None

IZY0073E A stop was issued for the Integration Server and it failed;return code = ReturnCode.

Source: Stop Integration Server tasks

Cause: Specified in ReturnCode.


IZY0074I To use this list as input to monitors and tasks, save theresults in the file $DBDIR/was_servers (on UNIX) or$DBDIR/tmp/was_servers (on NT) on the TMR Server. You can alsocopy and paste selected lines to the file. After saving the list, edit thefile and remove all lines that are not server names.

Source: List Application Server task


User Response: When saving the output to the file, in particular in NT,ensure that there are no special characters (such as, ^ M) at the end of thelines.


IZY0078E WebSphere Application Server was not found in directory.Please specify correct path and rerun configuration task.


Cause: Invalid WebSphere location specified

User Response: Specify the full path name where WebSphere is installed;rerun Configure WAS Endpoint task.

IZY0079E No server name specified for task.

Source: Application Server Status, Start Application Server, and StopApplication Server tasks

Cause: Application Server name not specified.

User Response: Specify valid Application Server name; run theappropriate task again.

IZY0080I The server ApplicationServer status is: status.

Source: Application Server Status task


User Response: None

IZY0081I The Administration server status is: status.

Source: Administration Server Status task


User Response: None

IZY0082E Error obtaining status for server ApplicationServer: Reason

Source: Application Server Status task and monitors

Cause: Specified in Reason output.

User Response: Run the appropriate task again.


B.

Messag

es

IZY0083E Some files or directories may not have been deleted fromthe endpoint.

Source: Delete Endpoint Dependencies task

Cause: An error occurred when deleting files on the endpoint.

User Response: If the wasav_delete_utils.log exists on the endpoint,check it for errors. On the endpoint, manually delete any files in the$LCFDIR directory that have WASAV in the path.

IZY0084I Using WebSphere’s default install directory:DefaultInstallDirectory.



User Response: None

IZY0085E WebSphere Application Server is not installed.

Source: Administration Server Status, Stop Administration Server, StartAdministration Server tasks

Cause: WebSphere is not installed.

User Response: Install WebSphere Application Server Advanced Edition.Run the appropriate task again.

IZY0087E The Integration Server is not installed. The Configure WASEndpoint task must be run to install it.

Source: Tasks and monitors that are run against an application server

Cause: The Integration Server is not installed.

User Response: Run the Configure WAS Endpoint task. Run theappropriate server task again.


IZY0088E No Application Server Name specified for the monitor.

Source: Monitors

Cause: Application Server Name is not specified.

User Response: Specify the Application Server Name. Edit andredistribute the appropriate monitor.

IZY0089E No Data Source specified for the monitor.

Source: Monitors

Cause: Data Source is not specified.

User Response: Specify the Data Source. Edit and redistribute theappropriate monitor.

IZY0090E Error obtaining data: error.

Source: Tasks and monitors

Cause: Specified in error output.

User Response: Correct the error. Then, run the appropriate task again orredistribute the appropriate monitor.

IZY0092W The Adapter Configuration Facility is not installed. Eventscannot be forwarded to the event server.


Cause: The Adapter Configuration Facility is not installed on both theTivoli management region and the gateway and the Event Server field isnot set to NOTECSERVER.

User Response: If you want events to be forwarded to the event server,install ACF on the Tivoli management region or the gateway. Then run the$BINDIR/../generic_unix/TME/WASAV/wasav_tool_dep.sh script to addwpostemsg to the dependency set. If you do not want events to beforwarded, set the Event Server field (in the Configure WAS Endpointdialog) to NOTECSERVER.


B.

Messag

es

IZY0093I The Administration Server is already running.

Source: Start Administration Server task


User Response: None

IZY0094I The Administration Server has been started.



User Response: None

IZY0095E Error starting the Administration Server: error.


Cause: The wscp command was run and returned an error.


IZY0096I The Administration Server is not running.

Source: Stop Administration Server task


User Response: None

IZY0097I The Administration Server has been stopped.



User Response: None

IZY0098E Error stopping the Administration Server: error.





IZY0099I The Integration Server is not running.

Source: Stop Integration Server task


User Response: None

IZY0100I The Integration Server is already running.



User Response: None

IZY0101E The ApplicationServer server was NOT started: error.

Source: Start Application Server task



IZY0102E The ApplicationServer server was NOT stopped: error.

Source: Stop Application Server task



IZY0103I No servers listed. You can run the List Application Serverstask to retrieve a list of server names which can be presented here byplacing the results in the file $DBDIR/was_servers (on UNIX) or$DBDIR/tmp/was_servers (on NT). You can also edit the file and enterthe Application Server names in the format:/Node:<node_name>/ApplicationServer:<app_svr_name>/

Source: Application Server Status, Start Application Server, StopApplication Server tasks

Cause: The Application Server Name list is blank when you click theServer Name button.

User Response: Run the List Application Server task and save the servernames in the was_servers file. Run the appropriate task again.


B.

Messag

es

IZY0108I No product files were deleted from endpoint.

Source: Delete Endpoint Dependencies task

Cause: Informational; the user did not confirm the deletion of files, thusno files were deleted.

User Response: None

IZY0109I The product files were successfully deleted from endpointand the monitor probes disabled.

Source: Delete Endpoint Dependencies task; uninstall command


User Response: None

IZY0111I The Application Server Application Server is alreadyrunning.



User Response: None

IZY0112I The Application Server ApplicationServer is already stopped.



User Response: None

IZY0113E Error obtaining data: Integration Server is not running.

Source: Monitors

Cause: Integration Server is not running. Integration Server must berunning for performance data to be collected.

User Response: Run the Start Integration Server task to start theIntegration Server.


IZY0114E Error obtaining data: Application Server Server is notrunning.

Source: Monitors

Cause: Application Server is not running. It must be running forperformance data to be collected.

User Response: Run the Start Application Server task to start theapplication server.

IZY0115E Error obtaining data: Unable to communicate with theAdministration Server. Verify security settings.

Source: Tasks and monitors

Cause: Security is enabled on the Administration Server. However, whenthe endpoint was configured using the Configure WAS Endpoint task,either the securities properties file was not supplied or and invalid file wassupplied.

User Response: Run the Configure WAS Endpoint task again and specifya valid value for the security properties file. Then, run the appropriate taskor monitor again.

IZY0116I The command has been issued to start the AdministrationServer. The server can take a while to initialize. It is recommended torun the Administration Server Status task to verify the serverinitialization is complete.

Source: Start Administration Server task (from a UNIX endpoint).


User Response: Run the Administration Server Status task to verify thatthe Administration Server initialization is complete.

IZY0119I The Integration Server status is: status.

Source: Administration Server Status task


User Response: None


B.

Messag

es

IZY0120E Error obtaining data: Administration Server is notrunning.

Source: List Application Servers and Application Server Status tasks

Cause: The administration server is not running.

User Response: Run the Start Administration Server task to start theadministration server. Then, run the appropriate task or monitor again.

IZY0121E Error starting Application Server: Administration Server isnot running.



User Response: Run the Start Administration Server task to start theadministration server. Then, run the Start Application Server task again.

IZY0122E Error stopping Application Server: Administration Serveris not running.



User Response: Run the Start Administration Server task to start theadministration server. Then, run the Stop Application Server task again.

IZY0123I Event Group WAS Event Group not created; command notavailable.


Cause: Tivoli Enterprise Console version 3.7 does not support the wcrtegcommand.

User Response: Create the event group manually from the TivoliEnterprise Console event server desktop.


IZY0124I Event Group WAS Event Group not assigned; command notavailable.


Cause: Tivoli Enterprise Console version 3.7 does not support thewassigneg command.

User Response: Assign the event group to the event console manuallyfrom the Tivoli Enterprise Console event server desktop.

IZY0125E The Integration Server was NOT started; unable tocommunicate with the administration server.


Cause: The administration server is not running, the administration serveris running with security enabled but the endpoint was not configured withsecurity, or an invalid port number was specified when the endpoint wasconfigured.

User Response: Correct the error and rerun the task.

IZY0126E No valid consoles found.


Cause: The List Consoles button was clicked and no event consoles aredefined in the Tivoli management region.

User Response: Create one or more event consoles within the Tivolimanagement region. Then, rerun the task. When you click the ListConsoles button, the event consoles are listed.


B.

Messag

es

Troubleshooting

Problems that you might encounter while using Tivoli Manager forWebSphere Application Server to manage a WebSphere ApplicationServer can have many different causes such as:

¶ Machine or server availability

¶ Operating system environment

¶ WebSphere Application Server installation

¶ Tivoli Manager for WebSphere Application Server configuration

This appendix helps you to resolve these types of problems. It ispresented in a question and answer format.

Refer to the Tivoli Manager for WebSphere Application ServerRelease Notes for information on the prerequisites.

Installation QuestionsWhat should be verified prior to installation to prepare for theTivoli Manager for WebSphere Application Server?

Test Distributed Monitoring and the Tivoli Enterprise Console eventserver (event server) before installing Tivoli Manager for WebSphereApplication Server. This is especially important if you are installingTivoli Manager for WebSphere Application Server in a new Tivolimanagement region. If these core applications are not working,

C


C.

Trou

blesh

oo

ting

Tivoli Manager for WebSphere Application Server will not workeither. At a minimum, you should be able to do the following withthese applications:

¶ Start a simple task. If you have Tivoli Enterprise Console, thenstart one of the tasks in the T/EC Tasks library.

¶ Deploy some distributed monitoring monitors on WebSphereApplication Server machines. Deploy monitors that send apop-up dialog to the administrator. Also send a Tivoli EnterpriseConsole event to ensure that the monitor is running and that theevent console receives distributed monitoring events.

¶ Send events to the event server from the endpoint using thewpostemsg utility provided by Tivoli ACF.

After your basic Tivoli installation, install the Tivoli Manager forWebSphere Application Server as follows:

¶ Back up your database on each machine where Tivoli Managerfor WebSphere Application Server will be installed.

¶ Install Tivoli Manager for WebSphere Application Server.

¶ Back up your database on each machine on which TivoliManager for WebSphere Application Server was installed.

Note: After the files are loaded onto the system from the installationmedia, an installation program is run to create the TivoliManager for WebSphere Application Server policy region.The installation program creates a wasav_init.log file in thedirectory returned by the wtemp command.

If the log file does not exist, correct the problem indicated inthe task output and reinstall the product from the installationmedia.

If the log file exists, review the log file to determine thecause of the problem. Then, correct the problem indicated inthe log file and reinstall the product from the installationmedia.


Questions on Running Tasks from the DesktopThe following information might help you solve problemsencountered using tasks from the desktop:

Why does a task fail with the following permissions error:endpoint_name(Endpoint): The task failed to execute.

endpoint_name(Endpoint): Insufficient roles for executing the task onendpoint_name endpoint.

1. Ensure that you assigned the resource roles wasav_senior orwasav_admin (or both) to the administrator that runs the task.Refer to “Assigning Resource Roles to a Tivoli Administrator” onpage 15 for more information.

2. After the resource roles have been assigned, stop and then startthe desktop again, so that the assigned roles will take effect.

Why are files still on the endpoint after running the DeleteEndpoint Dependencies task?

If debug is on when you run this task, the associated log files remainon the endpoint. To remove the log files, ensure that debug is offwhen you run the Delete Endpoint Dependencies task. Run this taskagain to remove the wasav_delete_utils.log and thewasav_stop_tis_server.log files.

Why are the administration server or application server tasksreturning UNKNOWN?

This can happen as the result of the following:

¶ Security is enabled after the Configure WAS Endpoint task wasrun. Run the Configure WAS Endpoint task again.

¶ The state of the server is in transition. For example, the servermight be starting or stopping. If this is the case, the status willreturn a valid state when the task is run again.

Questions on Using MonitorsWhy are my monitors returning -1?


C.

Trou

blesh

oo

ting

¶ Ensure that the administration server and the Integration Serverare running.

¶ Ensure that all parameters were entered correctly; the applicationserver name must be exact.

¶ Ensure that the application server is running.

¶ Ensure that the performance monitoring setting is correct. Referto “Enabling Performance Monitoring in WebSphere” on page 25for more information.

Why are my monitors not running?

If monitors are not running, do the following:

¶ Ensure that dm_ep_engine has been started on the endpoint.

¶ Ensure that the monitors are defined and enabled within theprofile.

¶ Ensure that you distribute the monitors to the subscriber list byfollowing these steps:

1. Open the WAS Monitors profile manager.

2. Right-click the Sentry profile collection and select EditProperties from the pop-up menu.

3. From the Profile menu, select Distribution Defaults. Ensurethat the ALL Levels of Subscribers and Make subscribers’profile an EXACT COPY of this profile check boxes havebeen selected.

4. Distribute the monitors again.

¶ Restart the Integration Server.

Why are the monitors returning E.EXEC as a result?

Typically monitors return E.EXEC when the monitor times outbefore it can obtain the results. Either the workload on the server istoo high or the administration server is still initializing orexperiencing a change of state. Ensure that the administration serveris fully initialized and operational.


Why are the administration server or application servermonitors returning UNKNOWN?

¶ This can happen as a result of security being enabled after theConfigure WAS Endpoint task was run. Run the Configure WASEndpoint task again.

¶ The state of the server is in transition. For example, the servermight be starting or stopping. If this is the case, the status willreturn a valid state when the monitor is redistributed.

Questions on Using the Tivoli Enterprise ConsoleWhy am I not seeing both WAS_Event events and WAS_Monitorevents on the Tivoli Enterprise Console event console (eventconsole)?

If you do not see both WAS_Event events and WAS_Monitor eventson the event console, check the following:

¶ Ensure that the event server is operational. Refer to the“Configuring the Event Server” on page 20 for more information.

¶ Ensure that the Integration Server is running.

¶ Ensure that Tivoli Manager for WebSphere Application Serverclasses and rules are installed and configured on the eventserver.

1. Enter the wlscurrb command to display the name of theactive rule base.

2. Run the wlsrbclass active_rulebase_name command to listthe defined event classes. Ensure that the WAS_Event andWAS_Monitors classes are defined.

3. Run the wlsrbrules active_rulebase_name command to listthe defined rules. Ensure that the wasav_events.rls and thewasav_monitors.rls rule bases are defined.

4. If the required Tivoli Manager for WebSphere ApplicationServer classes or rules are not defined, run the ConfigureEvent Server task to define the classes and the rules.


C.

Trou

blesh

oo

ting

¶ Check to see if the events are being received at the event server.

v Run the wtdumprl command on the event server to displaythe events in the reception log on the event server.

v If the events are not in the list, see the previous informationfor the WebSphere Application Server endpoint in thissection.

¶ The events are being received, but have a parsing_failedmessage.

v The Configure Event Server task has not been run. This taskloads the definitions for the WebSphere Application Serverevents into the event server.

¶ The events are being received and are processed.

Check the Event Groups that have been assigned to the eventconsole. If the WAS_Event Group is not listed, then the eventconsole has not been set up to display the WebSphereApplication Server events. Run the Configure Event Consoletask to assign the event group to the event console. This can alsobe done manually from the event server desktop.

Why am I not seeing WAS_Event events on the event console?

¶ If Integration Server events are being forwarded to the eventconsole, any of the following messages might be generated:

v The Integration Server has started and is sendingevents to the event server. This message is sent fromthe endpoint to the event console when the Integration Serverstarts.

v The Integration Server is shutting down and is nolonger sending events to the event server. Thismessage is sent from the endpoint to the event console whenthe Integration Server shuts down under normal operatingconditions.

v The Integration Server has lost communication withthe Admin server. Stopping serious events. This


message is sent from the endpoint to the event console whenthe Integration Server loses communication with theadministration server.

If you receive any of the above messages, but are not seeingWAS_Event events on the event console, check the following:

v Is there enough space in your WebSphere Application Serverdatabase to store new messages? (For example, the tablenamed SE_TABLE might contain hundreds of records.)

v Ensure that you have correctly specified which WebSphereevents should be forwarded to the event server. (Make surethat you have checked Yes for at least one message type(Fatal, Warning, Error, Audit, or Critical) and verify that thattype of event has occurred, which would cause it to beforwarded to the event server.) Refer to “Configure WASEndpoint” on page 44 for more information.

v Verify that the administration server is running. If theadministration server is not running, do the following:

– Stop the Integration Server

– Start the administration server

– Start the Integration Server. You should see a IntegrationServer started message in the event console.

¶ If Integration Server events are not being forwarded to the eventserver, do the following:

v Ensure that Tivoli ACF is installed.

v Ensure that the Integration Server is running.

v Verify that the Integration Server is communicating with theendpoint by issuing the following command from a Tivolimanagement region:wadminep endpoint_name view_version

where endpoint_name is the name of the endpoint with whichyou want to communicate.


C.

Trou

blesh

oo

ting

v Ensure that the event server is configured correctly. Refer tothe “Configuring the Event Server” on page 20 for moreinformation.

v Ensure that you have correctly specified which WebSphereevents should be forwarded to the event server. (Make surethat you have checked Yes for at least one message type(Fatal, Warning, Error, Audit, or Critical) and that that type ofevent has occurred, which would cause it to be forwarded tothe event server.) Refer to “Configure WAS Endpoint” onpage 44 for more information.

v Run the Display WAS Endpoint Configuration task. Refer to“Display WAS Endpoint Configuration” on page 50 for moreinformation.

– If the Event Server field is set NOTECSERVER, run theConfigure WAS Endpoint task again. Refer to “ConfigureWAS Endpoint” on page 44 for more information.

– Verify that the wpostemsg command is available on theendpoint and that it is in the $LCF_BINDIR/../toolsdirectory. On the event server, enter the wtdumprlcommand to see if the message was sent. This verifiesthat the communication between the adapter and theserver is operational.

Why am I not seeing WAS_Monitor events on the event console?

Events generated by WebSphere Application Server monitors are sentto the Distributed Monitoring event group on the event console.The class name for each monitor is WAS_monitor_name, wheremonitor_name is a short name for the monitor. If you do not seeWAS_Monitor events in the Distributed Monitoring event group,check the following:

¶ Run the following command to view a list of monitors that havebeen distributed to an endpoint:wlseng -z endpoint_label

Confirm that the Monitoring Probes area lists the monitors thatyou have distributed.


¶ Edit the properties for the WAS_Monitors profile. Verify thatthe monitor is set to forward an event to an event server.

¶ Edit a monitor and check the Trigger When selection. Themonitor will not forward events if the trigger condition has notbeen met.

¶ Run a monitor from another monitoring collection such as theUniversal monitoring collection. If you do not receive an event,refer to the Distributed Monitoring and Tivoli Enterprise Consoledocumentation.

¶ If you still experience problems after doing the above, clear andstop the monitoring engine by running the following commands:1. wclreng -z endpoint_label

2. wstopeng -z endpoint_label

All monitors are removed from the endpoint on which thecommand is run. Verify that the monitors have been removed bylisting the contents of the engine by running the followingcommand:wlseng -z endpoint_label

Distribute the monitors again. Events should appear in theDistributed Monitoring event group

¶ If you did not run the Configure Event Server task afterinstalling Tivoli Manager for WebSphere Application Server, youwill not see WAS_Monitor events on the event console.

What process should I follow if I want to install TivoliEnterprise Console or Tivoli ACF after Tivoli Manager forWebSphere Application Server has been installed?

What to do:

¶ Install the event console, the event server, and the Tivoli ACFutility.

¶ Configure the event server, as described in “Configuring theEvent Server” on page 20 and the event console, as described in“Configuring an Event Console” on page 23.


C.

Trou

blesh

oo

ting

¶ Run the$BINDIR/../generic_unix/TME/WASAV/wasav_tool_dep.shscript on the Tivoli management region.

¶ Run the Configure WAS Endpoint task, as described in“Configure WAS Endpoint” on page 44.

¶ Optionally, edit the default monitors (Integration Server Statusand Administration Server Status to forward events to the eventserver.

Helpful Debugging InformationKnowing file names, their contents, and where to look forinformation, such as task output and log files, can often be the keyto solving a problem.

The Configure Event Server, Configure Event Console, andConfigure WAS Endpoint tasks write output to a log file regardlessof whether debugging has been enabled with the Start Debuggingtask. All other tasks and monitors write output to a log file only ifthe Start Debugging task has been run.

The Configure Event Server and Configure Event Console tasksautomatically generate a log file and place it in the directoryreturned by the wtemp command. The log files are as follows:

¶ The Configure Event Server task writes output to thewasav_config_evtsvr.log file.

¶ The Configure Event Console task writes output to thewasav_config_console.log file.

All other tasks and monitors write output to separate log files on theendpoint. These files are located in the $LCF_DATDIR/WASAVdirectory (on UNIX endpoints) or %LCF_DATDIR%\WASAVdirectory (on Windows NT endpoints). For example:




When Tivoli Manager for WebSphere Application Server is installed,in addition to the log files created by tasks and monitors, thefollowing three log files are created and placed in the directoryreturned by the wtemp command:

¶ wasav_init.log

¶ AMS_WASAV_ALIDB_after.error.log

¶ AMS_WASAV_ALIDB_after.output.log

When the Tivoli Manager for WebSphere Application Server isremoved from the Tivoli management region, thewasav_uninstall.log file is placed in the directory returned by thewtemp command.


C.

Trou

blesh

oo

ting

Performance MonitoringInstrumentation Levels

The following table lists the monitors included in the WebSphereApplication Server monitor collection. Each monitor is listed with itscorresponding counter name.

Monitor Counter

Database connections -created

connectionMgr.data_store.numCreates

Database connections - timemaxed

connectionMgr.data_store.percentMaxed

Database connections -average wait time

connectionMgr.data_store.avgWaitTime

Database connections -threads waiting

connectionMgr.data_store.numWaiters

EJB - method execution beanData.beanMethodRT

EJB - method calls beanData.beanMethodCalls

EJB - calls/minute beanData.beanMethodCalls

EJB - method loads beanData.entityBeanLoads

HTTP - active sessions servletEngine.sessions.activeSessions

HTTP - invalid sessions servletEngine.sessions.invalidatedSessions

JVM - free memory runtime.resources.memFree

JVM - total memory runtime.resources.memTotal

Servlets - concurrent requests servletEngine.numConcurrentRequests

D


D.

Perfo

rman

ceM

on

itorin

gIn

strum

entatio

nL

evels

Monitor Counter

Servlets - currently loaded servletEngine.numLoadedServlets

Servlets - requests servletEngine.totalRequests

Servlets - response time servletEngine.responseTime

Thread pools - created orbThreadPool.threadCreates

Thread pools - average active orbThreadPool.numActiveThreads

Thread pools - average total orbThreadPool.totalNumThreads

Thread pools - percentagemaximum

orbThreadPool.percentTimeMaxed

Changing the Instrumentation LevelsYou can change the instrumentation levels using the Performancedialog box in the WebSphere Advanced Administrative Console. Inthe Performance dialog box, you can set the instrumentation level foreach performance category and for each resource instance. Thecurrent instrumentation level is represented by a small box icon withcolor stripes. The color key is as follows:

¶ Gray - Data is not being collected

¶ Blue - Counters that have a low impact on performance arebeing collected

¶ Yellow - Counters that have a medium impact and lower onperformance are being collected

¶ Red - Counters that have a high impact and lower onperformance are being collected

The color stripes indicate cumulative cost levels. An icon with blueand yellow stripes, for example, indicates that both low-impact andmedium-impact counters are being collected. Similarly, an icon withblue, yellow, and red stripes indicates that all counters (high,medium, and low) for that resource are being collected.

To specify or change the instrumentation level for a resource, do thefollowing:


1. Right-click an application server instance and choosePerformance from the pop-up menu to display the Performancedialog box.

2. In the Performance dialog box, a hierarchy of performancemodules is displayed. Expand the tree to reveal the performancecategory and resource desired. Select a resource.

3. Right-click a resource and choose None, Low, Medium, or Highfrom the pop-up icon. The color associated with the choseninstrumentation level is added to the instrumentation icon.

4. Click Set to apply the chosen setting. Click Reset to undo anychanges and revert the setting to its previous setting.

5. Click Quit to exit from the dialog box.

6. If performance monitoring is changed to a higher level, you mustresynchronize the Integration Server with the application serveras follows. On the WebSphere Advanced Administrative Console,select the application server and click the Refresh icon. Then,restart the Integration Server on the Tivoli desktop.

Note: Choosing an instrumentation level causes the same level to beapplied recursively to all elements beneath the selectedresource. To ensure that an instrumentation level is applied tothe desired resource, expand the node and make sure that onlythe desired resource is selected before setting the level.

Go to the http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/index.htmlWeb site and select Tune and troubleshooting for moreinformation.


D.

Perfo

rman

ceM

on

itorin

gIn

strum

entatio

nL

evels

http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/index.html

http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/index.html

Index

Aadding monitors 33administration server status monitor 27, 28administration server status task 38application server status monitor 29application server status task 39authorization

resource roles 15tivoli management region roles 3Tivoli management region roles 14, 15

Cclose_status_was rule 58closeharmless_monitor_was rule 58closeharmless_was rule 59command line installation 9commands

wdelprb 49winstall 9wlscurrb 89wlsrbclass 89wlsrbrules 89wpostemsg 19, 92wtdumprl 90, 92wtemp 86wuninst 10

components, installed 7configure event console task 23, 90configure event server task 20, 90configure WAS endpoint task 44configuring

event console 23event server 20integration server 16Tivoli Enterprise Console event handling 16WAS endpoint 44

customer support xi

Ddatabase connections monitor 29debugging

helpful information 94log files

location of 94delete endpoint dependencies task 48delete endpoint logs task 50desktop installation 8display WAS endpoint configuration task 50distributed monitoring

events 55rules 57

documentsaccessing files on product CD xaccessing files on Tivoli web site xaccessing online ixconventions ixordering xiproviding feedback xi

dup_monitor_was rule 58dup_was rule 59

EEJB monitor 30enabling performance monitoring 25event

classes 19, 55filtering 23Websphere Application Server event

sample 56


Ind

ex

event console 3, 23event management 2event server 20events

distributed monitoring 55Websphere Application Server 56

Ffiltering events 23

Ggetting started 13

HHTTP monitor 31

Iinstallation

from the command line 9from the desktop 8hints 85log files 9, 95objects created 9overview 6where to install 6

instrumentation levels 98integration server

configuring 16description 2events handled 19

integration server status monitor 27, 28integration with tivoli management

framework 3

interconnected Tivoli management regions 6introduction to tivoli manager for websphere

application server 1

JJVM monitor 31

Llibraries

WAS event tasks 19, 37WAS server tasks 37WAS utility tasks 37

list application servers task 38list endpoint logs task 49log files

configuration tasks 43, 94installation 9, 95location of 43, 95

Mmanagement

event 2operations 2performance 2

messages 61monitor_admin_up_was rule 58monitor_events_was rule 58monitors

adding 33administration server status 27, 28application server status 29database connections 29EJB 30hints on using 87HTTP 31integration server status 27, 28


monitors (continued)JVM 31servlets 32thread pools 32

Oobjects created during installation 9online documentation ixoperations management 2

Pperformance

management 2monitoring 25, 97

performance counter monitorsdatabase connections 29EJB 30HTTP 31JVM 31servlets 32thread pools 32

problems, finding and correcting 85

Rroles

resource roles 15Tivoli management region roles 14wasav_admin 14, 15wasav_senior 14, 15

rulesdistributed monitoring 57Websphere Application Server 59

Ssecurity properties file 47server information tasks 38server management tasks 39servlets monitor 32Software Installation Service 7start administration server tasks 40start application server tasks 41start debugging task 43start integration server task 41start monitors task 44status monitors

administration server status 28application server status 29integration server status 28

stop administration server task 40stop debugging task 43stop integration server task 42stop monitors task 44subscribing servers to a profile manager 16

Ttasks

hints, running from the desktop 87listing 50running 51WAS event tasks

configure event console 23configure event console task 90configure event server 20configure event server task 90

WAS server tasksadministration server status 38application server status 39list application servers 38start administration server 40start application server 41start integration server 41stop administration server 40stop integration server 42

WAS utility tasksconfigure WAS endpoint 44


Ind

ex

tasks (continued)delete endpoint dependencies 48delete endpoint logs 50display WAS endpoint configuration 50list endpoint logs 49start debugging 43start monitors 44stop debugging 43stop monitors 44

terminology xithread pools monitor 32timeharmless_monitor_was rule 58timeharmless_was rule 59Tivoli Enterprise Console, hints on using 89Tivoli Enterprise Console event console

configuring 23Tivoli Enterprise Console event handling 16Tivoli Enterprise Console event server

configuring 20tivoli management framework integration 3Tivoli management region

interconnected 6roles

assigning 14Tivoli management region roles 14, 15troubleshooting

installation 85running tasks and jobs from the desktop 87using monitors 87using the Tivoli Enterprise Console 89

Uuninstalling 10

WWAS event tasks library 19, 37WAS server tasks

administration server status 38application server status 39

WAS server tasks (continued)list application servers 38server information tasks 38server management tasks 39start administration server 40start application server 41start integration server 41stop administration server 40stop integration server 42

WAS server tasks library 37WAS utility tasks

configure WAS endpoint 44delete endpoint dependencies 48delete endpoint logs 50display WAS endpoint configuration 50list endpoint logs 49start debugging 43start monitors 44stop debugging 43stop monitors 44

WAS utility tasks library 37wasav_admin role 14, 15wasav_senior role 14, 15wdelprb command 49Webphere Application Server tivoli enterprise

console event sample 56Websphere Application Server

events 56rules 59subscribing 16

Websphere Application Server advancededition 1

winstall command 9wlscurrb command 89wlsrbclass command 89wlsrbrules command 89wpostemsg command 19, 92wtdumprl command 90, 92wtemp command 86wuninst command 10


Part Number: 5698WAS

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0701-00

(1P)

P/N:

5698

WAS