Websphere KM

PATROL for WebSphere Application Server
User Guide
Supporting
PATROL for WebSphere Application Server 2.4.00
June 9, 2006
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000
Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000
Copyright 2006 BMC Software, Inc., as an unpublished work. All rights reserved. BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc. IBM is a registered trademark of International Business Machines Corporation. DB2 is a registered trademark of International Business Machines Corporation. Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation. All other trademarks belong to their respective companies. BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.
Customer support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see Before Contacting BMC Software.
Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this website, you can
I I I I I I I
read overviews about support services and programs that BMC Software offers find the most current information about BMC Software products search a database for problems similar to yours and possible solutions order or download product documentation report a problem or ask a question subscribe to receive e-mail notices when new product versions are released find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 or send an e-mail message to support@bmc.com. Outside the United States and Canada, contact your local support center for assistance.
Before contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:
I
product information product name product version (release number) license number and password (trial or permanent)
operating system and environment information machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or maintenance level
I I I
sequence of events leading to the problem commands and options that you used messages received (and the time and date that you received them) product error messages messages from the operating system, such as file system full messages from related software
PATROL for WebSphere Application Server User Guide
Contents
Chapter 1 Product Components and Capabilities 17 18 18 18 19 20 21 21 21 22 22 23 23 23 26 29 33 45 45 46 46 47 49 49 51 52 52 52 53 54 61 61 63 64 66 67 68
5
PATROL for WebSphere Application Server Features. . . . . . . . . . . . . . . . . . . . . . . . . . Application-Centric Transaction Monitoring and End-to-End Response Time. . Support for WebSphere 6.0.02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Monitoring and Management . . . . . . . . . . . . . . . . . . . . . . . . . . Cell-Based Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Availability of Full Range of PMI-Provided Metrics . . . . . . . . . . . . . . . . . . . . . . . . Fine Grained Control of the Monitoring Environment . . . . . . . . . . . . . . . . . . . . . . Enterprise Java Bean Monitoring and Management . . . . . . . . . . . . . . . . . . . . . . . . J2EE Bytecode Instrumentation and JVM Profiling . . . . . . . . . . . . . . . . . . . . . . . . . Application Monitoring and Management with JMX . . . . . . . . . . . . . . . . . . . . . . . Database Connection Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebSphere Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL in a Cell-Based Management Environment . . . . . . . . . . . . . . . . . . . . . . . Application Classes and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Instance Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Product Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where to Go from Here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2 Installing and Migrating PATROL for WebSphere Application Server
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual Machine Support Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance and Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Installation Package of the Merged PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Removing Files from the PATROL_CACHE Directories. . . . . . . . . . . . . . . . . . . . . 69 Importing into a Distribution Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Importing a CD or Customized Installation Package into the Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Installing PATROL for WebSphere Application Server by Using the Distribution Server (Overview of Process). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Browser Version Required for Viewing PATROL Console for Unix Help . . . . . . 73 Additional Considerations for Using Online Help for Unix . . . . . . . . . . . . . . . . . . 73 Uninstalling PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . 76 Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 76 Other Information to Know Before Uninstalling PATROL for WebSphere Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Uninstalling PATROL for WebSphere Application Server on Unix . . . . . . . . . . . 77 Uninstalling PATROL for WebSphere Application Server on Windows . . . . . . . 81 Where to Go from Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Chapter 3 Configuration 87
Loading PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Initial KM Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Registering the WebSphere Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Configuring the Local Node Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Configuring the Local Deployment Manager Environment . . . . . . . . . . . . . . . . . . 94 Configuring the Remote Deployment Manager Environment . . . . . . . . . . . . . . . . 96 Configuring the Remote Application Server Environment . . . . . . . . . . . . . . . . . . . 97 Verifying the Runtime Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 KM Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Adding and Removing Monitored Nodes in Your Environment. . . . . . . . . . . . . 101 Setting the Monitoring Mode of Application Servers. . . . . . . . . . . . . . . . . . . . . . . 103 Setting Specific Monitoring Options for Application Servers . . . . . . . . . . . . . . . . 105 Scheduling Blackouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Creating or Adding to a Blackout Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Listing Blacked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Manually Stopping a Blackout Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Verifying Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Where to Go from Here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Setting Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Setting KM Debug Trace Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Chapter 4 Security 121
WebSphere Application Server Security and the KM . . . . . . . . . . . . . . . . . . . . . . . . . . 122 WebSphere Global Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Local WebSphere Administrator OS Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 WebSphere Global Security and the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 KM Command Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 KM Command Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
6 PATROL for WebSphere Application Server User Guide
Chapter 5
Tuning the KM
133 134 134 135 135 137 138 138 139 139 140 145 146 146 147 148 149 151 152 153 153 154 154 155 155 155 156 156 156 157 158 158 162 163 165 167 168 169 169 170 170 172 173
General Tuning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Application Servers Only as Needed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limiting the Number of Available Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters Affected by IBM Performance Data Monitoring Levels . . . . . . . . . . Parameters Affected by Profiling and Instrumentation Overhead . . . . . . . . . . . Tuning Collection Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limiting Log Monitoring Scan Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Profiling and Instrumentation Judiciously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Blackouts Effectively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Tuning for Large Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6 Working with Datasource Connections
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering the WebSphere Data Source Connection Account . . . . . . . . . . . . . . Checking the JDBC Connection Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating DataSource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling JDBC Connection Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 7 Working with Application Servers and Server Resources
Managing and Monitoring Cells, Nodes, and Servers in a Network Environment. Managing Mixed-Version WebSphere Environments . . . . . . . . . . . . . . . . . . . . . . Managing Cells and Deployment Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping a Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server and Resource Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Application Server Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Application Server Information and Controls . . . . . . . . . . . . . . . . . . . . . . . Checking Manually for Application Server Availability. . . . . . . . . . . . . . . . . . . . Stopping an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the HTTPTransport Connection State . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Monitoring of Application Servers and their Resources. . . . . . . . . . . . . . Enabling JVM Profiling on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Advanced JVM Runtime Resource Information . . . . . . . . . . . . . . . . . . . Generating an Application Server JVM Performance Report . . . . . . . . . . . . . . . . Configuring Java Classes for Method Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Method Profiling on Java Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Blackouts by Menu Command . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspending Monitoring for All Servers on a WebSphere Instance . . . . . . . . . . . Listing Blacked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resuming Monitoring of Blacked Out Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Blackouts by Command Line Interface . . . . . . . . . . . . . . . . . . . . Managing JMS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 8 Working with Web Applications, Servlets, and EJBs
Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Contents 7
Determining the Availability of Virtual Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Instrumented Web Application and Servlet Performance . . . . . . . . . . . . . . . . . . . . . . 177 Generating a Web Application Performance Report . . . . . . . . . . . . . . . . . . . . . . . 177 Generating a Servlet Performance ReportAll Applications. . . . . . . . . . . . . . . . 179 Generating a Servlet Performance ReportSpecific Application . . . . . . . . . . . . 180 Viewing Servlet Method Performance Information . . . . . . . . . . . . . . . . . . . . . . . . 182 Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Working with EJBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 EJB Management Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 BEANS and EJB_SUMMARY Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 EJB_TRANSACTION Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 EJB Method Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Generating a Performance Collector Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Chapter 9 Application Performance and Transaction Monitoring 187
Monitoring Transactions and Enterprise Web Applications . . . . . . . . . . . . . . . . . . . . 188 Activating and Deactivating Transaction Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . 189 Enabling ByteCode instrumentation with Java2 Security enabled. . . . . . . . . . . . 193 Adding and Removing Objects in the Monitoring Environment . . . . . . . . . . . . . . . . 193 Thresholds and Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Chapter 10 Instrumenting and Profiling J2EE Components 197
Instrumentation and Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Using Instrumentation to Identify and Monitor Most Critical SQL Objects . . . . . . . 198 Running the SQL Performance Report on All DBURLs . . . . . . . . . . . . . . . . . . . . . 199 Running the SQL Performance Report to Monitor SQL Objects. . . . . . . . . . . . . . 201 Monitoring Individual SQL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Monitoring Web Applications and Servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Profiling the Java Virtual Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Deleting Profiling and Instrumentation Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . 205 Chapter 11 Managing JMX-Instrumented Applications 209
Monitoring JMX MBeans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Instrumenting Your Application with JMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 The KM MBean Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Activating JMX Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Setting Default E-mail Address for Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Defining Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Adding Automatic Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Adding E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Deleting JMX files from Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Advanced Features for JMX Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Manually Registering an MBean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Defining Conditions for an Unregistered MBean . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Setting JMX Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Understanding Condition Settings and the ConditionDef Configuration Variable. 224
Chapter 12 Log File Monitoring Log Monitoring Benefits and Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Log Monitoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Files Monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Monitoring Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Monitoring Parameters and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activate or Deactivate Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting Log Monitor Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Log File Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rewind Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A Accessing Menu Commands, InfoBoxes, and Online Help
229 230 230 231 231 232 232 233 233 235 235 236 236 237 238 239
Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Appendix B Parameter Reference Column Headings Defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abbreviations Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Core Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consumer-Collector Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predominance of PerfCollector2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependencies for JVM Bytecode Instrumentation Parameters . . . . . . . . . . . . . . Appendix C Menu Summary 243 244 245 245 383 386 386 388 393
Core Product Application Class Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Application Menus for JMX Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Appendix D Agent Configuration Variables 419
Application Performance Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 Appendix E Product InfoBoxes Standard InfoBox Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Core Product Application Class InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_APPSERVER InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CELL InfoBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DATASOURCE InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBURL InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_LOG InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_NODE InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 428 428 428 429 429 430 430 430
Contents
PMW_MAIN InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 PMW_SERVER_RESOURCES InfoBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 PMW_SETUP InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 JMX InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 JMX_CONDITION InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 JMX_SERVER InfoBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 Appendix F Installed Files, Directories, and System Changes 435
Main File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Product Objects and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 Processes and Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 Microsoft Windows Registry Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Product and Process Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 Index 445
10
Figures
Application Class Hierarchy in PATROL for WebSphere . . . . . . . . . . . . . . . . . . . . . . 24 Application Class Hierarchy for Monitored WebSphere Components . . . . . . . . . . . 25 JMX Component Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Architecture of PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . 27 Managing Cell-Based Environments with PATROL . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Local Node Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Local Deployment Manager Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Remote Deployment Manager Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Remote Application Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 PATROL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Select Products to Installusing Typical Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Setup dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Register WebSphere Environment dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Register Local Node dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Register Local Deployment Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Register Remote Deployment Manager dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Register Remote Application Server dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Application Server Monitoring Modes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Monitoring Options for Application Servers Dialog Box . . . . . . . . . . . . . . . . . . . . . . 106 Performance Data Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Parameter Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Performance Data Level Dialog for WebSphere 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Initial Blackout Schedule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Add Blackout Period Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Initial Blackout Schedule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 WebSphere Icons in PATROL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Desktop view of a monitored WebSphere network environment . . . . . . . . . . . . . . . 152 Set Profiling Level dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Application Server Resource Report display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Configure Java Class for Method Profiling Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 166 Organization of web applications and servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Ping Virtual Host Aliases Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Servlet Performance Report for Specific Web App . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Application-centric monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 SQL Performance Report for All DBURLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 SQL Statement Stack Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 SQL Performance Report for a Specific DBURL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Define Condition dialog for ExtremeTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figures
11
12
Tables
Application Class Icons and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Instance Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 PATROL for WebSphere Application Server Installation Requirements . . . . . . . . . . 50 Mount commands by platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 NFS mount commands by platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Default Values for PATROL Location Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Runtime Environment Verification Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Application Server Monitoring Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Tuning Site/Size Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Parameters Affected by WAS Performance Data Levels . . . . . . . . . . . . . . . . . . . . . . 136 Parameters Affected by Profiling and Instrumentations . . . . . . . . . . . . . . . . . . . . . . 137 Parameters Activated When JVM Profiling Is Enabled . . . . . . . . . . . . . . . . . . . . . . . . 159 JVM Memory Allocation and Management Parameters . . . . . . . . . . . . . . . . . . . . . . . 162 Application Server Resource Report Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Transaction Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Profiling and Instrumentation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Setup e-mail dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 MBean Management dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Attributes of a JMX Condition Definition for ExtremeWeather . . . . . . . . . . . . . . . . . 225 Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 PATROL for WebSphere Application Server Core Parameters . . . . . . . . . . . . . . . . . 246 JMX Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 PMW_SERVER_RESOURCES Parameters Populated by JVMCollector . . . . . . . . . 388 PMW_DBURL Parameters Populated by DbUrlCollector . . . . . . . . . . . . . . . . . . . . . 389 PMW_SQL Parameters Populated by SQLCollector . . . . . . . . . . . . . . . . . . . . . . . . . . 389 PMW_SERVLET_GROUP Parameters Populated by PjsWebAppTopNCol . . . . . . 389 PMW_SERVLET_METHOD Parameters Populated by PjsServletClassCol . . . . . . 389 Dependencies for Availability Consumer Parameters . . . . . . . . . . . . . . . . . . . . . . . . 390 Dependencies for Log Consumer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 PMW Standard Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 PMW_ALARM_MANAGER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 PMW_ALARMMGR_GRP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 PMW_ALARM_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 PMW_APPSERVER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 PMW_BEANS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 PMW_CACHE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 PMW_CACH_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 PMW_CACH_TEMPLATE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 PMW_CELL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Tables 13
PMW_CLUSTER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 PMW_DATASOURCE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 PMW_DBPOOLS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 PMW_DBPOOLS_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 PMW_DBURL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 PMW_DBURLS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 PMW_DCS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 PMW_DCS_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 PMW_DCS_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 PMW_EJB_CONTAINER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 PMW_EJB_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 PMW_EJB_METHOD commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 PMW_EJB_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 PMW_EJB_TRANSACTION commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 PMW_HA_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 PMW_HA_MANAGER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 PMW_HA_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 PMW_J2C commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 PMW_J2C_FACTORY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 PMW_J2C_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 PMW_J2EE_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 PMW_J2EE_OBJ commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 PMW_LOG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 PMW_MAIN commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 PMW_NODE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 PMW_OBJECT_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 PMW_OBJECT_POOL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_OBJECT_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_ORB commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_ORB_INTERCEPTOR commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_ORB_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_PROF_CLASS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_SCHEDULER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_SCHEDULER_SERVICES commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 PMW_SCHEDULER_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 PMW_SERVER_RESOURCES commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 PMW_SERVLET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 PMW_SERVLET_ENGINE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SERVLET_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SERVLET_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SESSIONS commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SETUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 PMW_SIB_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SIB_SERVICE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SIB_SUMMARY commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SQL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_THREADPOOL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 PMW_THREADPOOL_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 PMW_THREADPOOL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
14
PMW_WEBSERVICE commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_WEBSERVICE_GROUP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_THREADPOOL commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_WLM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_WLM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_CONDITION commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_DOMAIN commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_SERVER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Agent Variables Used by PATROL for WebSphere Application Server . . . . . . . . . PATROL for WebSphere Application Server Standard InfoBox Fields . . . . . . . . . . PMW_APPSERVER Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . PMW_CELL Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DATASOURCE Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . PMW_DBURL Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_LOG Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_NODE Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_MAIN InfoBox Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_SERVER_RESOURCES Application Class InfoBox Items . . . . . . . . . . . . . . . . PMW_SETUP Application Class InfoBox Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_CONDITION InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_SERVER InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Types By File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directories and Files Installed on a PATROL Agent Computer . . . . . . . . . . . . . . . . Directories and Files Installed on a PATROL Console Server Computer . . . . . . . . Directories and Files Installed on a PATROL 3.x Console Computer . . . . . . . . . . . . Common Directories and Files Installed Regardless of Computer Role . . . . . . . . . Processes Run by PATROL for WebSphere Application Server . . . . . . . . . . . . . . . .
415 416 416 416 416 417 417 418 420 428 428 429 429 430 430 430 431 431 432 432 433 436 438 439 440 441 443
Tables
15
16
Chapter
1
18 18 19 20 21 21 21 22 22 23 23 23 26 29 33 45 45 46
Product Components and Capabilities

1
This chapter provides a brief overview of the PATROL for WebSphere Application Server product. The chapter contains the following sections: PATROL for WebSphere Application Server Features. . . . . . . . . . . . . . . . . . . . . . . . . . Application-Centric Transaction Monitoring and End-to-End Response Time. . Application Server Monitoring and Management . . . . . . . . . . . . . . . . . . . . . . . . . . Cell-Based Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Availability of Full Range of PMI-Provided Metrics . . . . . . . . . . . . . . . . . . . . . . . . Fine Grained Control of the Monitoring Environment . . . . . . . . . . . . . . . . . . . . . . Enterprise Java Bean Monitoring and Management . . . . . . . . . . . . . . . . . . . . . . . . J2EE Bytecode Instrumentation and JVM Profiling . . . . . . . . . . . . . . . . . . . . . . . . . Application Monitoring and Management with JMX . . . . . . . . . . . . . . . . . . . . . . . Database Connection Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Class Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebSphere Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL in a Cell-Based Management Environment . . . . . . . . . . . . . . . . . . . . . . . Application Classes and Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Instance Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing Product Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
PATROL for WebSphere Application Server Features

The PATROL for WebSphere Application Server product provides a monitoring and management capability for reliable, predictable performance of an IBM WebSphere Application Server environment. This section introduces the major product features that deliver this capability.
Application-Centric Transaction Monitoring and End-to-End Response Time

PATROL for WebSphere Application Server provides the ability to identify long-running transactions and to see component calls made within a transaction in order to identify bottlenecks. In this context, a transaction is the flow of work from the point a request enters the application server through the point it exits as a response. Performance and request rate information can be aggregated and monitored for J2EE components across multiple servers in a WebSphere cluster. By default, data will be aggregated at the enterprise application level. You can also aggregate data by specific J2EE components (servlets, EJBs, or JSPs). If bytecode instrumentation or request metrics is enabled, you can generate detailed transaction reports for enterprise application or transactions using a J2EE component that exceed threshold levels that you define. These transaction reports contain detailed information about JSPs, EJBs, and JDBC (SQL statements) used by the application, along with response timing metrics.
Support for WebSphere 6.0.02

PATROL for WebSphere Application Server can monitor and manage a WebSphere 6.0.02 environment. PATROL can also monitor and manage a mixed environment that includes servers running WebSphere 6 and other servers running WebSphere 5.
18
The WebSphere features that are fully monitored by PATROL for WebSphere Application Server are as follows:
I I
I I
Distribution and Consistency Services that handle inbound messages. The High Availability Manager (HA Manager) that controls key services in a distributed environment rather than the central server used in previous WebSphere versions. The HA Manager provides fault tolerance and failover capability for critical services, improving overall application server availability. The Scheduler Manager providing timing control services that run business logic. An Object Pool managing the creation and reuse of Java objects used in enterprise applications. A Service Integration Bus (SIBus) is a communication framework that provides synchronous and asynchronous messaging used to manage services in a distributed environment. SIBus supports the Service Oriented Architecture (SOA) and provides interoperability with WebSphere MQ.
Application Server Monitoring and Management

The heart of the PATROL for WebSphere Application Server product is centered on the health and activities of the application server. Core monitoring capabilities provided with the product allow you to
I I
monitor runtime application server availability monitor availability and performance of WebSphere resources, such as database connection pools, thread pools, overall memory utilization, and web services monitor performance of servlets, Java Server Pages (JSPs), and Enterprise Java Beans (EJBs)
Depending on the configuration options you select, the product can provide you with information about the following resources:
I I I I I I I I I I I I
application server runtime resources database connection pooling performance of SQL statements Enterprise Java Beans and methods client sessions virtual hosts Web applications servlets/JSPs Java 2 connections Object Request Broker (ORB) web services workload manager
Chapter 1 Product Components and Capabilities 19
You can also view data and generate reports with statistics concerning up to 30 of the most resource intensive of each of the following categories:
I I I
Web applications in the application server servlets in the entire application server servlets within a single Web application
Menu commands included with the product also give you the ability within PATROL for WebSphere Application Server to ping (manually verify availability of resources) and to stop and start certain resources:
Resources you can ping for availability through menu commands

I I I I I I
application servers Web server connection JDBC data source connection Deployment Manager Node agents JMS servers
Resources you can stop and start through menu commands

I I I I I
application servers Enterprise applications Deployment Manager Node agents JMS server
Cell-Based Management
PATROL for WebSphere Application Server fully supports the cell-based, network-oriented management approach that was first introduced in WebSphere 5.0. The cell-based approach provides some advantages for the WebSphere administrator in that it allows more flexible approaches to load balancing and a centralized management solution for WebSphere nodes dispersed throughout a network. When used to monitor a WebSphere network environment, PATROL for WebSphere Application Server provides an object hierarchy that aligns with IBMs management structure. For more information about cell-based management, see PATROL in a Cell-Based Management Environment on page 29.
20
Availability of Full Range of PMI-Provided Metrics

WebSpheres Performance Monitoring Infrastructure (PMI) provides a framework for monitoring a wide range of usage statistics and performance metrics. With PATROL for WebSphere Application Server, these values are represented as parameters, and the full range of PATROL tools can be leveraged to monitor EJBs, web applications, dynamic cache, J2C connection pools, JDBC connection pools, the Object Request Broker, the Workload Manager, thread pools, web services, and more.
Fine Grained Control of the Monitoring Environment

With PATROL for WebSphere Application Server you can specify which product services you currently need and which you want to hold in reserve for possible future use. This gives you the flexibility to tailor your PATROL for WebSphere Application Server environment for optimal performance, while maintaining all the functionality you require. You can choose the services you want to use, and exclude those that for which you dont have a current need. Beyond that, you can also specify which parameters in a service you want to be active. As you make these choices, PATROL for WebSphere Application Server automatically sets the performance monitoring level required by IBM WebSphere Application Server to accommodate your choices. The PATROL for WebSphere Application Server gives you the option of raising the performance monitoring level to meet that need, leaving the level as it is currently set, or setting a lower performance monitoring level.
Enterprise Java Bean Monitoring and Management

PATROL for WebSphere Application Server provides a great deal of information about the performance of Enterprise Java Beans (EJBs) in your IBM WebSphere Application Server environment. Depending on the configuration options you elect, you can
I I I
monitor EJBs for load values, response times, and life cycle activities monitor real-time performance of EJB transactions monitor performance of EJB methods
Chapter 1
21
J2EE Bytecode Instrumentation and JVM Profiling

The PATROL for WebSphere Application Server product includes instrumentation technology that allows you to monitor J2EE component performance at a fine-grained component level and to identify potential performance bottlenecks that may be associated with a single Web application, database URL, SQL statement, or Web application servlet. Using this technology, you can identify critical components that are most often invoked in your own environment, and you can identify components with slow response times. Using the full capabilities of the products J2EE bytecode instrumentation you can
I I
I I I
view details of transactions that exceed a response time threshold monitor and generate reports about SQL statements in all DBURLs or in a specific DBURL monitor and view statistics about any specific SQL statement monitor and generate reports about Web applications monitor and generate reports about servlet performance for all applications or for a specified application monitor servlet methods
PATROL for WebSphere Application Server also provides the ability to monitor performance of the Java Virtual Machine. Controls allow you to monitor selected Java classes and to profile performance. Available data includes JVM memory statistics, garbage collection metrics, method-level data, and thread data.
NOTE
Profiling with PATROL for WebSphere Application Server employs Java Virtual Machine Profiling Interface (JVMPI) technology. Because of the overhead inherent in the use of JVMPI, BMC recommends that profiling not be used with the KM on production machines, but be used only in development and testing environments.
Application Monitoring and Management with JMX

PATROL for WebSphere Application Server provides tools that let you monitor and manage MBean enabled applications used in a JMX-managed IBM WebSphere Application Server. You can select which MBeans you want to monitor and you can define attributes that determine which MBeans are monitored, that trigger automatic alerts (including events that can be managed in the PATROL Event Manager), and that can take automatic actions based on your monitoring criteria.
22
Product Architecture
Database Connection Monitoring

Because connections to an associated database are an integral part of many PATROL for WebSphere Application Server sites, the product gives you the capability of monitoring database connection pool performance. Included is an advanced feature to define database attributes for a very few sites whose high level of customization makes it impossible for the PATROL discovery process to detect those attributes automatically.
This section contains information about the hierarchy of information displayed on the PATROL Console and about the general architecture of PATROL for WebSphere Application Server in the IBM WebSphere Application Server environment. It also includes information about possible approaches to organizing a WebSphere environment under IBMs cell-based management approach, and shows where PATROL product components reside and operate in these environments.
Application Class Hierarchy

Figure 1 shows the organization of application classes in PATROL for WebSphere Application Server. Most application classes that represent WebSphere objects can have multiple instances and are organized into groups called containers. The containers have a class called SUMMARY that presents statistics and metrics spanning all instances. Figure 2 shows the relationship between containers, instances, and summary classes. The classes for JMX management are organized in a similar way, as shown in Figure 3. Information about how these instances are named is on page 45. For more information about each application class, see Application Classes and Icons on page 33.
Chapter 1
23
Figure 1
Application Class Hierarchy in PATROL for WebSphere

Application Performance
console SETUP MAIN CELL-BASED MANAGEMENT ENVIRONMENT (J2EE_GROUP)
J2EE_OBJ CELL (0 or more) CLUSTER (0 or more) SERVER LOG
NODE (0 or more)
LOG
servers
APPSERVER classes and containers
DBURLS*
JAVA CLASSES DB POOLS* ENTERPRISE BEANS* WEB MODULES JMX SERVER CACHE* ORB*
DBURL
JAVA METHODS ALARM MANAGER* DCS* THREADPOOLS* WORKLOAD MANAGER* WEBSERVICES* SESSIONS
SQL
SIBus
RESOURCES J2C
HIGH AVAILABILITY*
Object Pool*
* See Figure 2
24
Figure 2
Application Class Hierarchy for Monitored WebSphere Components

Contains 1 or more instances of monitored objects Statistics on instances are summarized in parameters under a SUMMARY class Containers may have subcomponents
GENERAL CONTAINER ORGANIZATION CONTAINER
INSTANCE1
INSTANCE2 Number varies
SUMMARY
COMPONENT
ORGANIZATION OF SOME SPECIFIC CONTAINERS Database Pools

APPSERVER DB POOLS SERVLET_CONTAINER corresponds to Enterprise application
Servlets
DATASOURCE
DB POOLS SUMMARY
SERVLET GROUP corresponds to Web application
SERVLET SUMMARY
EJBs
EJB_CONTAINER corresponds to Enterprise application
SERVLET SUMMARY SESSIONS SERVLET
SERVLET METHOD
EJB_JAR
BEANS TRANSACTION SUMMARY SUMMARY
BEANS
METHODS
Chapter 1
25
Figure 3
JMX Component Class Hierarchy
JMX SERVER
JMX CONDITION JMX DOMAIN
JMX CONDITION
If a condition applies to multiple domains, it is a child of the JMX_SERVER class. If it applies to only one domain, it is a child of the JMX_DOMAIN class.
WebSphere Data Collection

Figure 4 shows how the PATROL Console interacts with the PATROL Agent on an IBM WebSphere application server. A Java client collects performance data from the application server via a SOAP or RMI connection. PATROL obtains the performance data from the WebSphere Administration server or the application server via API calls. The PATROL Agent periodically collects these metrics using a Java client, then passes information to the Console or Console Server.
26
Figure 4
PATROL Consoles PATROL Console Servers
Architecture of PATROL for WebSphere Application Server

Host with IBM WebSphere Application Server
PATROL Components PATROL Agent PATROL for WebSphere Application Server Other PATROL KM products WebSphere Servers Bytecode Instrumentation JVM Profiling JMX Java Clients PMI
PATROL for WebSphere Application Server Other PATROL KM products
Deployment Manager
Data sources
Base App Server
Web Server
An explanation of the diagram components follows:
PATROL Consoles, PATROL Console Servers

These provide the ability to interact with one or more PATROL agents to setup and configure PATROL for WebSphere Application Server, and to manage WebSphere. You must install PATROL for WebSphere Application Server on at least one PATROL console for Windows or Unix, or on a PATROL console server providing PATROL common services. Installing on a console server allows you to use PATROL Central for Windows or PATROL Central for Web as your console.
PATROL Agent
For WebSphere version 5.x and later, an agent can be used to manage multiple WebSphere nodes in the Deployment Manager environment, or multiple base application servers throughout your network.
WebSphere Servers
These are the processes targeted for management. These include deployment managers, node agents, and application servers.
Chapter 1
27
Java Clients
BMC provides clients that interact with various WebSphere components and external components to gather information such as performance statistics, process status, and resource availability. They communicate with deployment managers, node agents, and application servers. These clients are designed to be launched once and reused via PSL global channels for maximum efficiency.
Bytecode Instrumentation
If activated, this instrumentation provides data such as SQL statement performance and servlet method performance. Data is collected in the WebSphere application server processes and is sent directly to the PATROL agent.
JVM Profiling
Recommended for a development environment only, JVM profiling can provide detailed information about Java class and method performance and about memory utilization. Data is collected in the WebSphere application server processes and is sent directly to the PATROL agent.
JMX
Java Management Extensions (JMX) provides the management infrastructure for WebSphere version 5.x and later. PATROL for WebSphere takes advantage of this by using JMX to invoke certain management functions. In addition, you can use JMX to build management into your application, and the JMX component of PATROL for WebSphere can be activated to interact with that management and monitor application-specific conditions.
PMI
This is an interface through which WebSphere provides performance statistics. PATROL for WebSphere requires that the service underlying this interface be active and uses it to discover and monitor most J2EE components in the WebSphere servers.
Admin Services
These are services in WebSphere allowing for configuration and control of the application servers. They reside in application servers or the deployment manager for WebSphere 5.x and later. Your configuration of PATROL for WebSphere drives the use of these services to achieve the corresponding configuration of WebSphere itself, including the optional BMC JMX service for application management.
28
Data Sources
Data sources provide the relational data needed for J2EE applications. PATROL for WebSphere clients can test the availability of these data sources, which can reside on the local host with WebSphere or remotely on another machine.
Deployment Manager
In a WebSphere Network Deployment environment, this process hosts the admin services described previously. It may reside on a remote host. PATROL for WebSphere clients interact with the deployment manager to configure WebSphere, and also check Deployment Manager availability.
Web Server
This process, which may reside on a remote host, receives Web user requests and drives servlets in WebSphere. WebSphere clients test the availability of the web server.
PATROL in a Cell-Based Management Environment

WebSphere version 5 introduced a new concept in managing a WebSphere environment that spanned across a network. Key to this new organization was the concept of the cell, which comprises multiple nodes throughout a network with management concentrated in an Administrative console and a Deployment Manager. PATROL for WebSphere Application Server provides a flexible management approach that can reflect the approach used in a given WebSphere environment, with PATROL management supporting either multiple remote agents, or a single centralized PATROL Agent. For optimal performance, BMC Software recommends that a PATROL Agent be limited to managing a single WebSphere cell.
NOTE
Monitoring a WebSphere cell is possible only if the cell is not empty, which requires that the cell includes an application server (excluding the deployment manager) at the first level of the list.
Chapter 1
29
The PATROL management approach to a cell-based environment relies on three key components:
I
Java client: Gathers most performance data and communicates with deployment managers, node agents, and application servers. JMX listener: Handles notifications from custom MBeans, messages using the Jras Logging Service, and asynchronous discovery information from Java collector clients. XPC: Handles data for the bytecode instrumentation and JVM profiling features.
Figure 5 shows PATROL managing supported cell-based management environments, while Figure 6 through Figure 9 show details of specific environment types. Figure 5 Host 1
Local Deployment Manager
Managing Cell-Based Environments with PATROL Host 2

Remote Deployment Manager
PATROL Java Client Java Client PATROL Agent JMX Listener Java Client Java Client
Host 3
Local Node Remote Application Server
30
Figure 6 Host 1
PATROL PATROL Agent
Local Node Environment
WebSphere Node 1 XPC Application Server Node Agent Application Server Application Server
JMX Listener
Java Client WebSphere Node 2 Java Client Application Server Application Server Application Server
Figure 7 Host 1
PATROL PATROL Agent
Local Deployment Manager Environment Host 2

WebSphere Cell 1 Node 1 XPC Application Server Node Agent Application Server
JMX Listener
Java Client
WebSphere Cell 1 Deployment Manager
Host 3
WebSphere Cell 1 Node 2 Node Agent Application Server Application Server
Chapter 1
31
Figure 8 Host 1
PATROL PATROL Agent
Remote Deployment Manager Environment Host 3

WebSphere Cell 1 Node 1 XPC Application Server Node Agent Application Server
JMX Listener
Java Client
Host 2
WebSphere Cell 1 Deployment Manager
Host 4
WebSphere Cell 1 Node 2 Node Agent Application Server Application Server
Figure 9 Host 1
PATROL PATROL Agent
Remote Application Server Environment
XPC
Host 2
Base Application Server
JMX Listener
Java Client
32
Application Classes and Icons

PATROL for WebSphere Application Server contains several applications and application containers. Application containers group together multiple instances of a managed resource. The MAIN application container represents the IBM WebSphere Application Server environment, and might contain a single node or multiple nodes. It is labeled WebSphere. The WebSphere Setup icon and the WebSphere icon are displayed in the computer window along with the WebSphere Setup and various other product icons. See Figure 10. Figure 10 PATROL Console
setup icon for PATROL for WebSphere Application Server
icon for monitoring and managing IBM WebSphere
Chapter 1
33
Table 1 shows the icon for each application class, the application class name, and a brief description of its function. Table 1 Icon Application Class Icons and Functions (Part 1 of 11) Application Class File Name Function Parent-Child Relationships
Administrative icons that appear in main PATROL Console

Setup Application Class
PMW_SETUP.km Configures PATROLs monitoring environment for IBM WebSphere Parent of: PMW_ENVIRONMENT
WebSphere Application Class

PMW_WEBSPHERE.km Provides supporting functionality for PMW_MAIN. Default discovery cycle is 1 hour.
Main Application Class

PMW_MAIN.km Serves as a container representing the entire Parent of: PMW_APPSERVER and IBM WebSphere Application Server PMW_NODE environment. Default discovery cycle is 1 hour.
Environment Application Class

PMW_ENVIRONMENT.km Represents a registered WebSphere 5.x environment and reports configuration problems. Child of: PMW_SETUP
Top-level icons that can represent a registered WebSphere environment

Node Application Class
PMW_NODE.km Represents an IBM WebSphere Application Server node in Network Deployment installations of version 5.x. Instances are discovered by the APPSERVER class. Instance labels take the form <environment>(Node_<name>) when representing the top level, or Node_<name> if the environment name is the same as the instance name. Parent of: PMW_CLUSTER
34
Table 1 Icon
Application Class Icons and Functions (Part 2 of 11) Application Class File Name
PMW_CELL.km
Function
Represents a single WebSphere cell in a management environment. A cell is a grouping of nodes. Instance labels take the form <environment>(Cell_<name>) when representing the top level, or Cell_<name> if environment name equals instance name.
Parent-Child Relationships
Child of: PMW_MAIN Parent of: PMW_NODE, PMW_CLUSTER, and PMW_APPSERVER
Cell Application Class
Application Server Application Class

PMW_APPSERVER.km Represents an instance of the IBM WebSphere Application Server application running on a given host (node). Child of: PMW_MAIN, PMW_NODE, PMW_CLUSTER
Parent of: many container and The instance label is AppServer_<server object classes, see classes below. name> if clusters are not used, or <node name>_ <server name> if it is under a cluster.
Icons that represent container classes and monitored WebSphere components

Cluster Application Class
PMW_CLUSTER.km Represents a WebSphere cluster. A cluster is a logical grouping of servers. This class is not relevant when monitoring a single Managed Server. Child of: PMW_CELL Parent of: PMW_APPSERVER
Blackout Application Class

Operates in background. No icon.
PMW_BLACKOUT.km Provides the functionality for blackout operations available through the PMW_SETUP and PMW_MAIN classes.
Alarm Manager Application Class

PMW_ALARM_MANAGER.km Represents an instance of the Alarm Manager running on the server. Child of: PMW_ALARMMGR_GRP Parent to: none
Alarm Manager Group Application Class

PMW_ALARMMGR_GRP.km Container for all Alarm Manager instances on the server. Child of: PMW_APPSERVER Parent to: PMW_ALARM_MANAGER
Alarm Manager Summary Application Class

PMW_ALARM_SUMMARY.km Provides aggregate summary statistics of all Child of: monitored Alarm Manager instances. PMW_ALARMMGR_GRP Parent to: none
Chapter 1
35
Table 1 Icon
PMW_CACHE.km
Function
Container class for dynamic cache metrics.
Child of: PMW_APPSERVER
Cache Application Class
Cache Summary Application Class

PMW_CACHE_SUMMARY.km Summary statistics for all dynamic caches. Child of: PMW_CACHE
Cache Template Application Class

PMW_CACHE_TEMPLATE.km Represents dynamic cache information. There will be one instance of this class per cache template. Child of: PMW_CACHE
Channel Application Class

PMW_CHANNEL.km Provides administrative functions supporting PMI clients.
Data Source Application Class

PMW_DATASOURCE.km Represents a connection pool to a database. Child of: PMW_DBPROVIDER
Database Pools Application Class

PMW_DBPOOLS.km Container for all datasource instances and datasource performance summary information. Default discovery cycle is 1 hour. Child of: PMW_APPSERVER Parent to: PMW_DBPROVIDER and PMW_DBPOOLS_SUMMARY
Database Summary Application Class

PMW_DBPOOLS_SUMMARY. km Contains summary performance data on all Child of: PMW_DBPOOLS database pools and datasources.
Database Provider Application Class

PMW_DBPROVIDER.km Performance metrics on the database driver Child of: PMW_DBPOOLS used for a database connection pool. Parent of PMW_DATASOURCE and PMW_DBPOOLS_SUMMARY
36
Table 1 Icon
PMW_DBURLS.km
Function
Represents all of the DBURLs in a WebSphere node. This class requires J2EE bytecode instrumentation.
Child of: PMW_APPSERVER Parent to: PMW_DBURL
DBURLS Application Class
DBURL Application Class

PMW_DBURL.km Represents a single DBURL. This class requires J2EE bytecode instrumentation. Child of: PMW_DBURLS Parent to: PMW_SQL
DCS Application Class

PMW_DCS.km Represents and instance of the Distribution and Consistency Service. Child of: PMW_DCS_GROUP Parent to: none
DCS_GROUP Application Class

PMW_DCS_GROUP.km Container class for data about the Distribution and Consistency Services. Child of: PMW_APPSERVER Parent to: PMW_DCS, PMW_DCS_SUMMARY
DCS_SUMMARY Application Class

PMW_DCS_SUMMARY.km Container class for aggregated data for all Distribution and Consistency Service instances. Child of: PMW_DCS_GROUP Parent to: none
Enterprise Java Bean Group Container Application Class

PMW_EJB_GROUP.km Serves as a container for all Enterprise Java Bean (EJB) information. This contains summary information across the server, and containers for beans. Default discovery cycle is 1 hour. Child of: PMW_APPSERVER Parent of: PMW_EJB_SUMMARY and PMW_EJB_CONTAINER
EJB_JAR Application Class

PMW_EJB_JAR.km Container for all beans in a JAR file and summary information for each type of bean (entity, message driven, stateful, or stateless). Child of: PMW_EJB_CONTAINER Parent to: PMW_BEANS
Enterprise Java Bean Summary Application Class

PMW_EJB_SUMMARY.km Presents summary performance data on EJBs across the entire application server. There will be one instance of this class for each type of bean in the JAR file. Child of: PMW_EJB_JAR
Chapter 1
37
Table 1 Icon
PMW_EJB_TRANSACTION.km
Function
Represents EJB transaction parameters within a Java virtual machine; data from this class spans all applications.
Child of: PMW_EJB_GROUP
Enterprise Java Bean Transaction Application Class
Enterprise Java Bean Container Application Class

PMW_EJB_CONTAINER.km Represents an enterprise application containing EJBs. Child of: PMW_EJB_GROUP Parent of: PMW_EJB_SUMMARY and PMW_BEANS
Beans Application Class

PMW_BEANS.km Represents an EJB instance; the label is the name of the EJB. Child of: PMW_EJB_JAR
Method Application Class

PMW_EJB_METHOD.km Represents a method called by an Enterprise Java Bean, including the following metrics: Total number of invocations of each method I Rate of invocation for each method I Total number of method invocations per bean
I
Child of: PMW_BEANS
High Availability Group Application Class

PMW_HA_GROUP.km Container for all High Availability Managers on a server. Child of: PMW_APPSERVER Parent to: PMW_HA_MANAGER
High Availability Application Class

PMW_HA_MANAGER.km Represents an instance of the High Availability Manager on a server. Child of: PMW_HA_GROUP Parent to: none
High Availability Summary Application Class

PMW_HA_SUMMARY.km Contains aggregate statistics for all High Availability Managers. Child of: PMW_HA_GROUP Parent to: none
38
Table 1 Icon
PMW_J2C.km
Function
Container class for J2EE Connector Architecture connection pools.
Child of: PMW_APPSERVER Parent to: PMW_J2C_FACTORY and PMW_J2C_SUMMARY
J2C Application Class
J2C Factory Application Class

PMW_J2C_FACTORY.km Performance data for a J2C connection pool. Child of: PMW_J2C
J2C Summary Application Class

PMW_J2C_SUMMARY.km Summary statistics across all J2C connection pools. Child of: PMW_J2C
J2EE Group Application Class

PMW_J2EE_GROUP.km Container for tracking response times and transaction activity at the enterprise application level, the EJB level, and the servlet level. Child of: PMW_APPSERVER Parent to: PMW_J2EE_OBJ
J2EE Object Application Class

PMW_J2EE_OBJ.km Represents an enterprise application, servlet, or EJB for response time and transaction tracking. Child of: PMW_J2EE_GROUP Parent to: none
Log Group Application Class

PMW_LOG_GROUP.km Represents a subset collection of error log Child of: PMW_SERVER_LOG files within the server logs being monitored by the KM. This application class is available only for IBM WebSphere version 5.x.
Log Application Class

PMW_LOG.km Represents an individual log file being monitored by the KM. Child of: PMW_SERVER_LOG and PMW_LOG_GROUP
Object Group Application Class

PMW_OBJECT_GROUP.km Container class for all Object Pools under the server. Child of: PMW_APPSERVER Parent to: PMW_OBJECT_POOL
Chapter 1
39
Table 1 Icon
PMW_OBJECT_POOL.km
Function
Represents an object pool on the server.
Child of: PMW_OBJECT_GROUP Parent to: none
Object Pool Application Class
Object Summary Application Class

PMW_OBJECT_SUMMARY.km Container for aggregate statistics spanning all object pool instances. Child of: PMW_OBJECT_GROUP Parent to: none
Object Request Broker Application Class

PMW_ORB.km Container class representing object request broker data. Child of: PMW_APPSERVER Parent to: PMW_ORB_INTERCEPTOR and PMW_ORB_SUMMARY
ORB Interceptor Application Class

PMW_ORB_INTERCEPTOR.km Performance and usage data for the ORB intereceptor on one application server. Child of: PMW_ORB
ORB Summary Application Class

PMW_ORB_SUMMARY.km Summary statistics for all ORB interceptors. Child of: PMW_ORB
RAS Messages Application Class

PMW_RAS_MESSAGES.km Monitors Java reliability and serviceability (JRAS) trace and debug messages. Child of: PMW_APPSERVER, PMW_NODE, PMW_CELL
Scheduler Application Class

PMW_SCHEDULER.km Represents a Scheduler service running on the server. Child of: PMW_SCHEDULER_SERVICES Parent to: none
Scheduler Services Application Class

PMW_SCHEDULER_SERVICES.km Container for all Schedulers under a server; each Scheduler will be represented by an instance of the PMW_SCHEDULER application class. Child of: PMW_APPSERVER Parent to: PMW_SCHEDULER
40
Table 1 Icon
PMW_SCHEDULER_SUMMARY. km
Function
Contains aggregate statistical parameters for all Scheduler instances.
Child of: PMW_SCHEDULER_ SERVICES Parent to: none
Scheduler Summary Application Class
Server Logs Application Class

PMW_SERVER_LOGS.km Represents the collection of server logs being monitored by the KM. Child of: PMW_MAIN
Sessions Application Class

PMW_SESSIONS.km Represents HTTP session metrics from the SessionManager. Child of: PMW_APPSERVER, PMW_SERVLET_GROUP
Server Resources Application Class

PMW_SERVER_RESOURCES. km Monitors server resources, including Java Virtual Memory and thread pools. Default discovery cycle is 1 hour. Child of: PMW_APPSERVER
Servlet Application Class

PMW_SERVLET.km Represents a servlet instance. Child of: PMW_SERVLET_GROUP
Servlet Container Application Class

PMW_SERVLET_CONTAINER. km Represents web applications containing servlets for a given enterprise application. Child of: PMW_SERVLET_ENGINE Parent to: PMW_SERVLET_GROUP
Servlet Engine Application Class

PMW_SERVLET_ENGINE.km Provides summary and instance information about servlet engines in the application server. Default discovery cycle is 1 hour. Child of: PMW_APPSERVER Parent to: PMW_SERVLET_CONTAINER PMW_SERVLET_SUMMARY
Servlet Group Application Class

PMW_SERVLET_GROUP.km Represents web applications containing servlets on the application server. Child of: PMW_SERVLET_CONTAINER Parent to: PMW_SERVLET_SUMMARY PMW_SERVLET
Chapter 1
41
Table 1 Icon
PMW_SERVLET_SUMMARY. km
Function
Provides servlet performance summary information. If the summary instance appears under the Servlet Group, then it summarizes all servlets comprising the web application. If the summary instance appears under the HTTP host, then it summarizes all web application statistics for the servlet engine on its parent host or node.
Child of: PMW_SERVLET_ENGINE PMW_SERVLET_GROUP
Servlet Summary Application Class
Servlet Method Application Class

PMW_SERVLET_METHOD.km Represents a servlet method instance. This class is generated only if EJB method data was selected for PMI collection during configuration and if J2EE bytecode instrumentation is active. Child of: PMW_SERVLET
SIBus Group Application Class

PMW_SIB_GROUP.km Container class for all instances of the SIB_SERVICE and SIB_SUMMARY classes. Provides statistics and performance metrics monitoring the service integration bus (SIBus). SIBus supports messaging in WebSphere version 6, which can be used to support Web Services applications and to interoperate with WebSphere MQ. SIB_GROUP and its children classes are not available to monitor versions of WebSphere prior to WebSphere 6.0. Child of: PMW_APPSERVER Parent of PMW_SIB_SERVICE
SIBus Service Application Class

PMW_SIB_SERVICE.km Performance metrics for SIBus services. This class is available only for WebSphere 6 or later. Child of: PMW_SIB_GROUP Parent of PMW_SIB_SUMMARY
SIBus Summary Application Class

PMW_SIB_SUMMARY.km Summary statistics spanning all SIB_SERVICE instances. This class is available only for WebSphere 6 or later. Child of: PMW_SIB_SERVICE
SQL Application Class

PMW_SQL.km Represents an SQL statement in a DBURL. This class requires J2EE bytecode instrumentation. Child of: PMW_DBURL Parent to: none
42
Table 1 Icon
PMW_THREADPOOL.km
Function
Represents performance information for a given threadpool.
Child of: PMW_THREADPOOL_GROUP
Thread Pool Application Class
Thread Pool Group Application Class

PMW_THREADPOOL_GROUP. km Container class representing threadpool information. Child of: PMW_APPSERVER Parent to: PMW_THREADPOOL and PMW_THREADPOOL_ SUMMARY
Thread Pool Summary Application Class

PMW_THREADPOOL_ SUMMARY.km Summary statistics for all threadpools. Child of: PMW_THREADPOOL_GROUP Parent to:
Web Services Application Class

PMW_WEBSERVICE. km Represents web services information on a server. Child of: PMW_WEBSERVICE_GROUP
Web Services Group Application Class

PMW_WEBSERVICE_GROUP. km Container for web services information. Child of: PMW_APPSERVER Parent to: PMW_WEBSERVICE PMW_WEBSERVICE_ SUMMARY
Web Services Summary Application Class

PMW_WEBSERVICE_ SUMMARY.km Container for summary information on all webservices in a group. Child of: PMW_WEBSERVICE_GROUP Parent to:
Workload Manager Application Class

PMW_WLM.km Performance information on the workload manager. Child of: PMW_WLM
Chapter 1
43
Table 1 Icon
PMW_WLM_GROUP.km
Function
Container class for a group of workload managers.
Child of: PMW_APPSERVER Parent to: PMW_WLM, PMW_WLM_SUMMARY
Workload Manager Group Application Class
Workload Manager Summary Application Class

PMW_WLM_SUMMARY.km Contains aggregate statistical parameters for all Workload Manager instances. Child of: PMW_WLM_GROUP
JMX_MAIN Application Class

JMX_MAIN.km Provides administrative functions for the JMX component JMX applies only to IBM WebSphere Application Server 5.x environments
JMX_DOMAIN Application Class

JMX_DOMAIN.km Provides administrative functions for the JMX component Child of: JMX_SERVER JMX applies only to IBM WebSphere Application Server 5.x environments
JMX_SERVER Application Class

JMX_SERVER.km Each instance represents an MBean server. JMX applies only to IBM WebSphere Application Server 5.x environments Child of: JMX_MAIN
JMX_CONDITION Application Class

JMX_CONDITION.km Each instance represents a monitored condition that you have previously defined; the condition includes definitions of attribute value thresholds and notifications. JMX applies only to IBM WebSphere Application Server 5.x environments If a condition applies to a single JMX domain, the icon is a child of JMX_DOMAIN, if it applies to multiple domains, it is a child of JMX_SERVER
44
Accessing Product Help
Application Instance Naming Conventions

Many application classes in PATROL for WebSphere Application Server can have multiple instances, each with a unique name. The name is used to label icons in the PATROL Console. Application class instances are named using the conventions shown in Table 2. Table 2 Instance Naming Conventions Instance Naming Convention name of the application server name of the EJB name of the cell name of the cluster name of the database connection pool name of the database provider ENTERPRISE_BEANS name of the jar file name of the node name of the servlet instance cart-ejb.jar Node_MyNode Snoop name of the enterprise application petstore Example SalesServer2, AppServer_SalesSrv LocalTaxBean Cell_Cell2 Cluster_Clus1 custdb4 DB2 JDBC Provider
Application PMW_APPSERVER PMW_BEANS PMW_CELL PMW_CLUSTER PMW_DATASOURCE PMW_DBPROVIDER PMW_EJB_CONTAINER PMW_EJB_GROUP PMW_EJB_JAR PMW_J2EE_OBJ PMW_NODE PMW_SERVLET PMW_SERVLET_ CONTAINER PMW_SERVLET_GROUP
name of the enterprise application petstore
name of the enterprise application petstore containing servlets name of the war file app1.war
PMW_SERVLET_ENGINE WEB_APPLICATIONS
Accessing Product Help

PATROL provides Help topics for the currently displayed window or dialog box. You can also start the Help system for the KM, and get help for application classes and parameters. How you get the product Help depends on the type of PATROL Console you are using. For specific instructions about accessing Help in each Console type, please refer to Accessing Online Help on page 241 in Appendix A, Accessing Menu Commands, InfoBoxes, and Online Help.
Chapter 1
45
Additional Information
A core set of PATROL manuals is provided on the documentation CD included with major releases of the PATROL Console and Agent. You can also view manuals in electronic format or order additional printed copies from the Web:
http://www.bmc.com/support_home.
For the latest updates to product information, refer to the release notes, which are also available at http://www.bmc.com/support_home.
Where to Go from Here

If you are ready to install and configure the PATROL for WebSphere Application Server product, see Chapter 2, Installing and Migrating PATROL for WebSphere Application Server.
46
Chapter
Installing and Migrating PATROL for WebSphere Application Server

2
This chapter describes how to install PATROL for WebSphere Application Server or upgrade from a previous version. Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Virtual Machine Support Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Performance and Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Installation Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Preparing to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Determine the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Target Computers and Their Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Determining Where to Install KMs Based on Architecture. . . . . . . . . . . . . . . . . . . 57 Typical and Custom Installation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Installing for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Typical New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Upgrading from an Earlier Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Removing Previous Profiling and Instrumentation Libraries . . . . . . . . . . . . . . . . 63 Determining the Location of PATROL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Upgrading Without Saving KM Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Preparing to Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Creating an Installation Package of the Merged PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Removing Files from the PATROL_CACHE Directories . . . . . . . . . . . . . . . . . . . . 69 Importing into a Distribution Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Distribution Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Importing a CD or Customized Installation Package into the Distribution Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Installing PATROL for WebSphere Application Server by Using the Distribution Server (Overview of Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Considerations for Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 2 Installing and Migrating PATROL for WebSphere Application Server 47
Browser Version Required for Viewing PATROL Console for Unix Help . . . . . . 73 Additional Considerations for Using Online Help for Unix . . . . . . . . . . . . . . . . . . 73 Uninstalling PATROL for WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . 76 Determining the Version of the Installation Utility . . . . . . . . . . . . . . . . . . . . . . . . . 76 Other Information to Know Before Uninstalling PATROL for WebSphere Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Uninstalling PATROL for WebSphere Application Server on Unix . . . . . . . . . . . 77 Uninstalling PATROL for WebSphere Application Server on Windows . . . . . . . 81
48
Installation Requirements
Before installing PATROL for WebSphere Application Server, verify that your system is supported for this product and that you have a valid license from BMC Software and an appropriate account from which to install the product. If you will be using the JVM Profiling and Instrumentation features, verify that your Java environment is supported for this product.
NOTE
Any information for Unix, unless otherwise specified, applies to any supported versions of Linux.
System
Before installing PATROL for WebSphere Application Server, verify that the target computer meets the installation requirements listed in Table 3.
49
Table 3 Resource
PATROL for WebSphere Application Server Installation Requirements (Part 1 of 2) Minimum Requirements
I I
Comments
operating system (supported with 32-bit WebSphere AS)
I I
I I I
IBM AIX 4.3.3 and later none HP-UX 11i with September 2004 Quality Pack and the required HP-UX patches for Java Solaris 8 and later Windows 2000 Advanced Server (SP 4), Windows 2000 Server (SP 4), Windows 2000 Professional (SP 4), Windows 2003 Server (SP 1), Windows XP Professional (SP 1a or SP 2) SUSE Linux SLES 8 (SP 4) or 9 (SP 1) (Intel) SUSE Enterprise Server 7 or 8 (zSeries) Red Hat Enterprise Linux AS/ES for Intel 2.1 (2.4 kernel) or 3.0 (Update 2, 3, or 4) Red Hat Enterprise Linux AS for zSeries 3.0 (Update 2, 3, or 4) or 4.0 Red Hat Enterprise Linux WS for Intel 3.0 (Update 2, 3 or 4) or 4.0 HP-UX 11iv2 Update 2 none Red Hat Enterprise Linux AS/ES for Intel 3.0 (Update 3 or 4) or 4.0 SUSE Linux Enterprise Server 9 (SP 1) Windows Server 2003 Enterprise (SP 1) Windows Server 2003 x64 Editions 5.0 or 5.1 Base or Network Deployment 6.0 Base, Express, or Network 6.0.02 Base, Express, or Network
I
operating system (supported with 64-bit WebSphere AS) IBM WebSphere Application Server
I I
I I I I I I
WebSphere Application Server - Express version 5.x or earlier is not supported by PATROL. WebSphere 5.0 (not 5.1) is required for AIX 4.3.3 and SLES 7.
Java Development Kit (JDK) PATROL products
I I I I I I
WebSphere 5.0.02: IBM JDK 1.3.1 WebSphere 5.1.0.x: IBM JDK 1.4.1 WebSphere 5.1.1: IBM JDK 1.4.2 WebSphere 6.0: IBM JDK 1.4.2
none
I I
PATROL Agent 3.5.30, 3.6.00.5i none PATROL Central Operator Windows Edition or Web Edition or PATROL Classic Console for Unix or Windows PATROL for Unix PATROL for Microsoft Windows Servers On a Unix console: 51 MB On a Windows console: 51 MB On a PATROL Central console: 43 MB Much of the disk space requirement is used for code that is shared with the installer.
disk space
I I I
50
Table 3 Resource memory
PATROL for WebSphere Application Server Installation Requirements (Part 2 of 2) Minimum Requirements varies greatly, depending on the number of objects in the monitored environment Comments Memory use is typically
I
minimally increased with standard monitoring increased slightly more when instrumentation is enabled significantly to drastically increased with the use of JVMPI for profiling, especially method-level profiling
BMC Software recommends that profiling be limited to test and development environments. port
I I I
Port 3604 is required. Port 4560 is used by xmlMsgClient. Port 49002 and 52000 are used by BMCProfiler.
Port 3604 is used by the JMX MBean interface; if 3604 is blocked, the JMX listener will not function. If profiling features are enabled, performance will be significantly degraded on processors slower than 1 GHz.
processor speed depends on the number of objects in the monitored environment
Virtual Machine Support Limitation

VMWare provides technology that creates virtual infrastructures by providing a layer of abstraction between the computing, storage, and networking hardware, and the software that runs on it. This technology enables customers to run additional operating systems in multiple windows called virtual machines. BMC Software does not anticipate problems with the PATROL and SmartDBA product families in virtual infrastructure implementations, but products within these families have not been specifically tested in this scenario. Therefore, BMC Software will only provide support for problems that are reproducible without these complementary technologies.
51
Performance and Scalability

BMC Software tested PATROL for WebSphere Application Server to assess its performance in typical IBM WebSphere Application Server environments in different configurations. Generally, we found that:
I
In a basic out-of-the-box configuration, monitoring an active IBM WebSphere Application Server environment, PATROL for WebSphere Application Server used negligible resources. Turning on Instrumentation features slightly increased the load on the PATROL Agent. Due to inherent overhead of the JVMPI, turning on Profiling features significantly increased the CPU load and caused extended load times for the PATROL Agent and for the WebSphere Application Server. As a result, BMC Software recommends using Profiling features only as a development and test tool outside the production environment.
License
Verify that you have a a permanent license to run your PATROL product or a valid demonstration license. If you have not yet installed a permanent license, contact your BMC Software sales representative or BMCs Contract Administration department for licensing information.
Installation Account
Install PATROL for WebSphere Application Server on each machine using the dedicated PATROL OS account under which you installed the PATROL Console or Agent. If you do not already have a dedicated PATROL account, this section describes how to set up a PATROL installation account for Windows and Unix platforms.
Windows Environment
PATROL requires a dedicated user account in the Windows environment known as the PATROL default account. The PATROL default account must be created before you install PATROL. The PATROL default account can be either a local or a domain account.
52
Preparing to Install
Stand-alone workgroup servers must use a local user account as a PATROL default account. Servers that are trusted members of a domain may use either a local or domain account. In each case, the PATROL default account must be a member of the local administrators group of the computer where the agent will reside. PATROL default accounts on domain controllers should be only domain accounts. The account on a domain controller must be a member of the domain administrators group. Although you can use an existing Windows user account, BMC Software recommends that you create a separate Windows user account for PATROL.
WARNING
Do not use a domain or local Administrator account as the PATROL default account. Such account usage causes files created by PATROL to be owned by the Administrator, which could result in security or file access problems.
Unix Environments
BMC Software recommends that the Unix account that you create meets the following conditions:
I
The account .login, .profile, .cshrc, and .kshrc files should contain as little user customization as possible. Specifically, there should be no aliases, the prompt should be set to the default, and there should be no command in these files to change the umask setting. The recommended umask setting for the installation account is 022. Do not use root to install PATROL products as this may create security risks. Be sure the account has permission to create directories in the directory where you will install PATROL products.
The account that you use to install PATROL must have permission to write the installation logs to the $HOME and /tmp directories on the computer where you are installing products.
BMC Software recommends that you install the product on a limited number of development or test machines first, configure and test the product, and then install it onto production machines.
53
Installation Prerequisites
Before you install, you must
I
ensure you are using the appropriate version of the installation utility (see page 54) understand target machines and their roles (see page 55) understand PATROL security options (see page 59)
Checking for Product Patches or Fixes Before Installing

Product fixes or patches are often available through the BMC Software Web site. Patches correct problems that are found after a product is released. BMC Software recommends that you check the product page for version 2.4.00 of PATROL for WebSphere Application Server on the BMC Software Customer Support Web page to determine whether a patch is available before you begin installing a product.
Remote Installation
If you create an installable image, the product configuration information that you enter, such as the BMC Software products installation directory, account names, passwords, PATROL Agent port number, and security options, must be the same for all computers on which the image is to be installed. If you want to specify different settings for different computers, you must either create a separate image for each set of values that you want to implement or edit the variables in the images control file by using the ctltool. For more information about creating, distributing, and installing installable images, and about using the ctltool, see the PATROL Installation Reference Manual.
Determine the Version of the Installation Utility

The installation instructions contained in this version of the PATROL for WebSphere Application Server User Guide pertain to version 7.4.60 of the PATROL Installation Utility. This version of the installation utility might be different from the version included on another product CD or from a version that you downloaded from the BMC Software Electronic Product Download (EPD) site. If you use a version of the PATROL Installation Utility other than version 7.4.60, the instructions in this manual may not precisely match what you see on your screen.
54
To determine the version of an installation utility, perform the following steps:
1 Open a command prompt. 2 Navigate to the directory where the installation utility is located. 3 Enter one of the following commands:
I I
Windows: setup.exe -v Unix: setup.sh -v
A message box displays the version of the installation utility.
Target Computers and Their Roles

The installation utility prompts you to select the roles performed by the computer on which you are installing BMC Software products (the target computer). Before beginning the installation process, review the following definitions of the roles that are presented in the installation utility and decide which of these roles is performed by each computer in your environment.
Roles Performed by Computers in the PATROL Architecture

The roles performed by computers in the PATROL Architecture are
I
Console Systems (also referred to as console computers) host user desktop
applications such as consoles, user interfaces, viewers, and browsers. Select this option if the computer to which you are installing will perform any of the following roles: monitor and manage on Windows by using a PATROL Central Operator Microsoft Windows Edition console (PATROL 7.x architecture) monitor, manage, and develop KMs on Unix by using a PATROL Console for Unix (PATROL 3.x architecture) monitor, manage, and develop KMs on Windows by using a PATROL Console for Windows (PATROL 3.x architecture)
55
Managed Systems (also referred to as agent computers) host software that manages
the resources on the computer, such as a PATROL Agent, PATROL Knowledge Modules, and Service Reporting Retrievers. Select this option if the computer to which you are installing will perform any of the following roles: host a PATROL Agent 3.5 or 3.6 (works with both the PATROL 3.x and PATROL 7.x architecture) host KMs and components that contain the knowledge that PATROL uses to monitor the resources on this computer
NOTE
If you are installing PATROL for WebSphere Application Server into an IBM WebSphere Application Server 5.0 or later environment in the Network Deployment configuration, do not install the KM onto a machine that has only the Deployment Manager piece installed. A Common Services (PATROL 7.x architecture) computer hosts services that are shared among managed systems and console systems. You can install each of these common services on any computer in the network. Select this option if the computer to which you are installing will perform any of the following roles: host the PATROL Central Operator Web Edition (PATROL 7.x architecture) Web server host the PATROL Console Servers host the RTservers
For more information about the PATROL consoles and PATROL Console Server or RTserver, see the products respective online help systems and the following documents:
I
PATROL Central Operator - Web Edition Getting Started PATROL Central Operator - Microsoft Windows Edition Getting Started PATROL Console Server and RTserver Getting Started PATROL Configuration Manager User Guide PATROL Console for Microsoft Windows User Guide - Understanding the Basics of PATROL, Volume 1 PATROL Console for Unix User Guide
56
Determining Where to Install KMs Based on Architecture

PATROL 3.x and PATROL 7.x architectures differ as to which target computers store Knowledge Modules and how much KM information is required by each type of system. During installation, ensure that you select the appropriate types of systems according to the following information:
PATROL 3.x
Install KM packages to Managed Systems and Console Systems. A PATROL 3.x environment includes the following components:
I I
PATROL Agent 3.5 or 3.6 runs on Managed Systems. PATROL Console for Windows or PATROL Console for Unix 3.5 runs on Console Systems.
PATROL 7.x
For PATROL Central Operator Microsoft Windows Edition, install KM packages to Console Systems, Common Services Systems, and Managed Systems. For PATROL Central Operator Web Edition, install KM packages to Common Services Systems and Managed Systems. A PATROL 7.x environment includes the following components:
I I I I
PATROL Agent 3.5 or 3.6 runs on Managed Systems. RTserver runs on Commons Services Systems. PATROL Console Server runs on Common Services Systems. PATROL Central Operator Microsoft Windows Edition, PATROL Central Operator Web Edition, or both run on Console Systems.
For more information about the PATROL 7.x architecture, see the PATROL Infrastructure Planning Guide.
Mixed PATROL 3.x and 7.x Environment

A mixed PATROL 3.x and 7.x environment includes the components from both a PATROL 3.x environment and a PATROL 7.x environment.
57
Typical and Custom Installation Types

The installation utility prompts you to select one of the following installation types:
I
In general, use the Typical installation type if you are installing PATROL for WebSphere Application Server for the first time or if you are upgrading from a previous installation and you wish to use standard default settings for directories and port numbers. In general, use the Custom installation type if you want to install only individual components, or if you are upgrading from a previous version of PATROL for WebSphere Application Server and have a PATROL environment that may be configured with non-standard settings.
NOTE
If you are installing PATROL for WebSphere Application Server to an existing PATROL Agent or Console environment that is not in the default installation directory, use Custom. Do not use Typical. Typical will automatically install the agent or console with PATROL for WebSphere Application Server and overwrite your existing installation. If you do not want to overwrite your existing installation, use Custom so that you can clear the selection of the agent or console product.
58
PATROL Security
You can secure the data passed between PATROL components and restrict unauthorized users from accessing your data by implementing PATROL security. PATROL security is installed as part of the agent, console server, and consoles. KMs inherit the security policy from the agent, console server, and console on which they are installed. For more information about implementing and using PATROL security, see the following documentation:
I I
PATROL Security User Guide PATROL Security Release Notes
Default Login Shell

BMC Software recommends that you define the default login shell as part of preparation to install, if you are installing into a Unix environment. Although setting a default login shell is not specifically a requirement for installation, starting the KM without having defined the correct login shell could result in unpredictable behavior. Both the WebSphere Administration Account and the PATROL Default User Account must be set to use one of the following the default login shells:
I I
the Bourne shell (sh) the Korn shell (ksh)
Mounting a CD on Unix
The following sections provide information about the mount commands you must use to mount the PATROL product CDs on your Unix system.
Mounting the CD Drive

In this procedure, the root directory for the CD drive is called /cdrom. This directory might be different for your computer, depending on how your system administrator has configured the device. If a problem occurs, consult your system administrator or read the man page for mount.
1 Log on as root. 2 Insert the CD into the CD drive.
59
3 Use the mount command appropriate to your platform to mount the CD.
Table 4 Platform AIX HP-UX Linux Solaris Mount commands by platform Mount Command mount -r -v cdrfs /dev/cd0 /cdrom mount -F cdfs -o ro /dev/dsk/drive_for_cdrom/cdrom mount /dev/cdrom /path_to_target _mount_point Volume Manager (/usr/sbin/vold) automatically mounts. Otherwise, mount -r -F hsfs /dev/sr0 /cdrom
4 Log off.
Mounting the CD drive for an NFS Client

Before you can mount the CD on an Network File System (NFS) device, you must export the CD file system so that it can be mounted by NFS clients. Most platforms use the exportfs command to export a local file system, including a CD file system. However, Solaris platforms use the share command. To mount the CD on an NFS client, follow these steps:
1 Log on as root. 2 Create a directory on your local computer (for example, /mnt/cdrom or
/mnt/cdrom/cdrom0 for Solaris) as the mount point for the CD on the remote host
computer.
3 Use the mount command appropriate to your platform to mount the CD.
Table 5 Platform Linux Solaris NFS mount commands by platform Mount Command mount host:/path_to_file_system_to_be_exported / path_to_target_mount_point mount host:/cdrom/cdrom0 /mnt/cdrom/cdrom0 If a problem occurs, consult your system administrator or read the man page for mount.
AIX, HPUX-PA1.0 mount host:/cdrom /mnt/cdrom
4 Log off.
60
Installing for the First Time

This section describes how to do a new install of PATROL for WebSphere Application Server. You can optionally perform remote or multiple installations using the Distribution Server (see Distribution Server on page 70). You should first install on a limited number of machines in a test environment, test the installation thoroughly, and then install in your production environment.
NOTE
By default, the Typical installation configures the PATROL Agent to connect through port 3181. If you want to use a different port, you must use the Custom installation, see Upgrading from an Earlier Version on page 63.
Typical New Installation

To do a Typical first time install:
1 Insert the PATROL for WebSphere Application Server product CD in the

CD-ROM. If you are using a Unix system, mount the CD.
2 If the installation program did not automatically start, or if you are installing from
an electronically downloaded install image, then start the installer. From the installation CD, run Windows: setup.exe Unix: setup.sh If you are in a Unix environment with no web browser, or are in a Windows 2000 environment with Citrix Metaframe, perform the following steps to launch the installation program:
A From a command line prompt, change to the directory in which the installation
utility is located.
B Start the installation utility using one of the following commands:

Unix: ./setup.sh -serveronly Windows: setup.exe -serveronly
C On another computer with a browser, start the web browser. D Direct the browser to the URL displayed in the message box (enter the URL in
your browsers Address or Go To field).
61
3 In the Welcome to the Installation Utility window, click Next to begin your
installation.
4 Accept Licence Agreement, select Accept then click Next to continue. 5 From the Select Installation Option window, select I want to install products on this
computer now, then click Next.
6 From the Select Type of Installation window, select the Typical installation method
and click Next.
7 In the Specify Installation Directory window, enter a directory path if you do not
wish to accept the default directory. Click Next to continue.
8 In the Select System Roles window, select whether the machine to which you are
installing is used as a monitoring console or as a target managed system (or both). Select the appropriate role, then click Next.
I
Select Console System if you are installing to computer that will host the PATROL Classic Console. Select Managed System if you are installing to a computer that will host a PATROL Agent. (This is a computer on which you run IBM WebSphere Application Server). Select Common Services if you are installing to a computer that will host the PATROL Central Operator - Web Edition (PATROL 7.x architecture) web server, the PATROL Console Servers, or the RTservers. If you are not sure which option to choose, select both Console System and Managed System.
9 From the Select Products and Components to Install window (see Figure 11), click
+ to expand the PATROL Solutions branch, select BMC PM for WebSphere AS version 2.4.00 Maintenance Release, then click Next.
Figure 11
Select Products to Installusing Typical Install
10 Review the setup information on the Review Selections and Install (or Review
Selections and Create Installable Image) window. If you want to change settings, click Back to go back to previous windows. Click Start Install to complete the installation.
62
Upgrading from an Earlier Version
11 When the status window reports that installation is 100% complete, click Next to
see the results window. (Next does not appear until installation is complete.)
12 You can click View Log to review details of the installation, or click Exit to close the
installation utility.

If you have a previous version of PATROL for WebSphere Application Server installed on the target computer, you have the following options for upgrading to the new version of PATROL for WebSphere Application Server:
I
Upgrading Without Saving KM Customizations on page 66
Removing Previous Profiling and Instrumentation Libraries

The J2EE bytecode instrumentation and Advanced JVM monitoring features of PATROL for WebSphere Application Server deploy files to the JAVA_HOME directory used by WebSphere. Typically this directory is located at java/jre relative to the WebSphere installation directory. If you previously activated these features using PATROL for WebSphere 2.1.00 or later, you should remove these files. To remove the files that support advanced monitoring features:
1 Stop the PATROL Agent, all application servers, and any other JVMs that are using
the JAVA_HOME directory.
2 Remove the directory JAVA_HOME/lib/patrol. 3 Remove all files matching the pattern BMC*.jar under the directory
JAVA_HOME/lib/ext.
4 Remove any of the following platform-dependent advanced profiling files that

may exist on your system. Platform Windows AIX or Linux Solaris HP Location %JAVA_HOME%\jre\bin $JAVA_HOME/jre/bin $JAVA_HOME/jre/lib/sparc $JAVA_HOME/jre/lib/PA_RISC2 libBMCprofiler.sl File BMCProfiler.dll libBMCprofiler.so
Once you have completed your upgrade of PATROL for WebSphere, updated files be deployed if these features are active.
Installing and Migrating PATROL for WebSphere Application Server 63
Determining the Location of PATROL

During the installation process, the PATROL Installation Utility records where it installs PATROL components in environment variables. To function properly, various components of the PATROL product, such as the migration tools, require the information stored in these variables. Two important variables are PATROL_HOME and PATROL_CACHE. Throughout this section, all references to PATROL_HOME represent %PATROL_HOME% if you are using Windows and $PATROL_HOME if you are using Unix. All references to PATROL_CACHE represent %PATROL_CACHE% if you are using Windows and $HOME/patrol if you are using Unix.
Default Values for PATROL Location Variables

If you do not specify a location for the PATROL installation, the installer uses the following preprogrammed default locations and stores these locations in environment variables. Table 6 Variable PATROL_HOME Default Values for PATROL Location Variables Windows Default Value C:\Program Files\BMC Software\PATROL3 Unix Default Value /opt/bmc/PATROL3
PATROL_CACHE %HOMEDRIVE%\%HOMEPATH%\ $HOME/PATROL3 PATROL3
64
Viewing Environment Variables Set by PATROL

To view the value of PATROL_HOME, PATROL_CACHE and other environment variables, perform the appropriate procedure for your operating system: Operating System Procedure
Microsoft Windows NT 4.x Using the Control Panel tools 1. From the Start Menu, select Start => Settings => Control Panel. 2. Open the System application. 3. Select the Environment tab. 4. Scroll through the System Variable list box to view the variables. Note: The System application displays PATROL_CACHE only if it is set to a value other than its default value. Using the PATROL Environment Probe 1. From the Start Menu, select Start => Programs => BMC PATROL => PATROL Environment Probe. 2. Scroll to the variables that you want to view.
65
Operating System Microsoft Windows 2000
Procedure Using the Control Panel tools 1. From the Start Menu, select Start => Settings => Control Panel. 2. Open the System application. 3. Select the Environment tab. 4. Scroll through the System Variable list box to view the variables. Note: The System application displays PATROL_CACHE only if it is set to a value other than its default value. Using the PATROL Environment Probe 1. From the Start Menu, select Start => Programs => BMC PATROL => PATROL Environment Probe. 2. Scroll to the variables that you want to view.
Unix using Bourne or Korn At the shell command prompt, type export and press Shell ENTER. The shell displays a list of environment variables and their values. Note: If PATROL_HOME is not set, run patrolrc.sh. Unix using C Shell At the shell command prompt, type setenv and press ENTER. The shell displays a list of environment variables and their values. Note: If PATROL_HOME is not set, run patrolrc.sh.
Upgrading Without Saving KM Customizations

If you do not want to save any customizations of .km files, PSL code, alarm thresholds, or events, you can simply install the new version of PATROL for WebSphere Application Server over your previous version after moving or deleting PATROL for WebSphere Application Server files from the PATROL_CACHE. See Installing for the First Time on page 61 for instructions.
66
You might also want to remove the directory PATROL_HOME/websphere because version 2.4.00 uses a directory called PATROL_HOME/pmw_websphere.
NOTE
Customizations applied using PATROL Configuration Manager or operator overrides are automatically saved in the agent configuration database. They will take effect automatically unless the parameter name or application name has changed. In either of those cases, you must reapply the customizations.
Preparing to Upgrade
Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If the .kml file or any of the .km files for the new version of PATROL for WebSphere Application Server has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.
Before You Begin

I
If you plan to migrate your customizations, determine whether you can migrate from a previous version of PATROL for WebSphere Application Server. If you are upgrading from version 2.1.00 or later of PATROL for WebSphere Application Server, you must remove the advanced Java monitoring components before upgrading. See Removing Previous Profiling and Instrumentation Libraries on page 63.
To Back Up the Current Installation

Back up your customizations so that you can restore the current installation if you want to roll back your upgrade.
1 Shut down any PATROL Agents, consoles, and related services that are currently
running.
2 Remove the following obsolete or changed .km files from the list of preloaded KMs
on each PATROL Agent:
I I I
PMW_SERVLET_WAR.km PMW_PROF_CLASS.km PMW_PROF_METHOD.km
3 Ensure that no one is accessing any PATROL files or directories.

4 Perform a full backup of the directories where PATROL files are typically stored.
These directories are listed in the following tables:
Windows
File Type executables and data console customizations Directory PATROL_HOME for agent and console installation directories PATROL_CACHE for the console working cache
Unix and Linux

File Type executables and data console customizations Directory PATROL_HOME/.. for agent and console installation directories PATROL_CACHE for the console working cache
Creating an Installation Package of the Merged PATROL for WebSphere Application Server
After you have migrated and merged your customizations, you must create an installation package that can be used with the installation utility to install locally on one computer or with Distribution Server, to install remotely on multiple computers.
1 Copy the entire contents of the PATROL for WebSphere Application Server CD to
a temporary directory on a hard drive on a server. You can delete this temporary directory after you have successfully created an installable image.
2 Navigate to the packaged_results directory for the merged package and open the
.ppf file with a text editor. Write down the file name in the first line of the .ppf file. This file name is the name of the directory that you will look for in the Products
directory of the CD image.
3 Rename the packaged_results directory with the file name that you found in the .ppf
file in the previous step.
EXAMPLE
If pokckm/8.5.00/030107-233044 was listed in the first line of the .ppf file, you would use pokckm as the directory name.
68
Importing into a Distribution Tool
4 Copy the renamed directory to the Products directory of the temporary directory
that you used in Step 1. You will be replacing the files there with the merged files that contain your customizations.
5 Copy the PATROL for WebSphere Application Server CD image to the server that
you will use to install PATROL for WebSphere Application Server.

I
Remove the files in the PATROL_CACHE directory by following the instructions in Removing Files from the PATROL_CACHE Directories on page 69. Install PATROL for WebSphere Application Server from the target server by following the instructions in Installing for the First Time on page 61. Import the customized version of PATROL for WebSphere Application Server into the Distribution Server by following the instructions in Importing a CD or Customized Installation Package into the Distribution Server on page 70.
Removing Files from the PATROL_CACHE Directories

Before you install, you must remove the current PATROL for WebSphere Application Server files from the PATROL_CACHE directory for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the newly installed files from PATROL_HOME. You may wish to create a backup copy of the files elsewhere on your system before deleting the files. Delete files with the following naming patterns from PATROL_CACHE\knowledge and PATROL_CACHE\psl:
I I
PMW* JMX*

The PATROL for WebSphere Application Server can be installed locally to a single computer or remotely to multiple computers using BMC Softwares Distribution Server.
69
The details of how to install a product across an enterprise to multiple machines by using Distribution Server is beyond the scope of this book. However, this section does describe how to import the PATROL for WebSphere Application Server product into the tool. It also provides a high-level overview of the enterprise installation process that uses this product.
Distribution Server
You use the Distribution Server to perform remote installations or uninstallations of BMC Software distributed systems products across multiple systems from a central location. With the Distribution Server you can
I
Install, uninstall, upgrade, and reinstall products on remote systems from one central location. Create collections of products and system groups to distribute multiple products to multiple systems in one distribution. Schedule a distribution for a specific date and time. Maintain multiple product versions to be distributed. View reports to check distribution status, gather distribution data, and diagnosis problems.
Importing a CD or Customized Installation Package into the Distribution Server

This task describes how to import components into the Distribution Server for deployment to multiple locations.
Before You Begin

I
The customized installation packages that resulted from Creating an Installation Package of the Merged PATROL for WebSphere Application Server on page 68 must be accessible to the Distribution Server. Ensure that you use the Distribution Server version 7.1.15 and apply any available patches.
70
To Import Components in to the Distribution Server 1 Using the Distribution Server Manager, start the Distribution Server and connect
to it.
2 In the Distribution Server tab area, click the Components tab. 3 In the list area, click the Import button. 4 Navigate to the location where the components are located and click Next. 5 Select the directory that contains the Products directory (do not select the Products
directory itself). If the components are not accessible on a local drive, you can specify them by using the NFS name and path.
EXAMPLE
Assuming that you copied the CD image into a directory called merged_CD and then, after migrating your customizations and creating a customized installation package, you copied the updated package to the directory containing the CD image, the resultant directory structure would resemble: (Windows Only) merged_CD\Products\pokchm (Unix Only) merged_CD/Products/pukchm You would select the directory merged_CD.
6 Select the check boxes for the components that you want to import and click OK. 7 Click Import to import the selected components.
Installing PATROL for WebSphere Application Server by Using the Distribution Server (Overview of Process)
Once you have imported the PATROL for WebSphere Application Server into the Distribution Server, you must perform the following tasks within the tool. The tasks can be grouped into three stages.
71
Considerations for Using Online Help
To Set Up Products 1 Import components into the Distribution Server repository on the Components tab
of the Distribution Manager.
2 Arrange components in collections on the Collections tab of the Distribution

Manager.
3 Configure the collections on the Configurations tab of the Distribution Manager. To Set Up Systems 1 Create accounts in the operating system of the computers to which you want to
distribute PATROL for WebSphere Application Server.
2 Add accounts and create profiles for the systems on the Systems tab of the
Distribution Manager.
3 Add the systems and install the Distribution Client on the Systems tab of the
Distribution Manager.
4 Arrange systems in system groups on the Systems tab of the Distribution Manager. To Distribute Products 1 Distribute configurations of collections to system groups on the Distributions tab of
the Distribution Manager.
2 Run reports to review distributions on the Reports tab of the Distribution Manager.
For detailed instructions about how to perform remote installations with the Distribution Server, see the Distribution Server Getting Started Guide.

If you plan to install the Unix version of PATROL for WebSphere Application Server on a PATROL Console for Unix, you must install the supported version of the Help browser separately if it is not already installed.
72
Browser Version Required for Viewing PATROL Console for Unix Help
The appropriate one of the following browsers is required to view PATROL Help in PATROL version 3.x:
I
Unix: Netscape Navigator version 3.01 through 4.78 Red Hat Linux: Netscape Navigator version 4.x
PATROL Help does not support Netscape Navigator 6.0.
Installation Requirement
You must install Netscape Navigator on the computer where the PATROL console resides. You can install Netscape anywhere on your Unix computer as long as the binary is in the path.
Download Location
Netscape Navigator is supplied by Netscape Communications Corp. You can locate the browser at http://home.netscape.com/download.
Additional Considerations for Using Online Help for Unix

When you select Help from the PATROL Console for Unix, it may take a few seconds for the Help browser to launch. Two windows will be displayed. First, the Netscape Navigator window is displayed as an icon, and then a browser window that contains the Help is displayed. In addition, you must be aware of the following restrictions:
I
Netscape Navigator displays warning messages when it is invoked multiple times within the same user account because of its file-locking mechanism. It will, however, continue functioning. By default, when Netscape Navigator starts, it uses a private color map. As a result, you might experience color flashing on your workstation. If so, you can set the value of PATROL_BROWSER so that the colormap option is not specified. However, some subsequent color requests might fail and the online Help will be improperly displayed.
73
The Exceed for Windows NT X Window Server product by Hummingbird Communication Ltd. may not always display the Help files properly.
Consult your Netscape Navigator documentation for specific platform requirements and restrictions.
Required Environment Variables Settings for the Browser

The LANG, PATH, and PATROL_BROWSER environment variables must be set for the Help browser to run properly. The following sections describe these variables.
LANG Variable
The Unix LANG environment variable must be set to C so that Netscape Navigator will work properly. Otherwise, you might experience product failures. Type of Shell Bourne Korn C Export Command for LANG Variable LANG=C export LANG export LANG=C setenv LANG=C
PATH Variable
The PATROL user account PATH variable must contain the location of the directory containing the Netscape files. If the directory containing the Netscape files is not in the path, add the directory to the PATROL user account path. This requirement applies only to the PATROL user account on the PATROL console computer. Type of Shell Bourne Korn C Export Command for PATH Variable PATH=$PATH:/netscape_location export PATH export PATH=$PATH:/netscape_location setenv PATH=$PATH:/netscape_location
PATROL_BROWSER Variable
When PATROL starts the Help browser, it uses the command in the PATROL_BROWSER environment variable. As a default, the PATROL_BROWSER environment variable contains the following command:
74
Type of Shell Bourne
Export Command for PATROL_BROWSER Variable PATROL_BROWSER=netscape -display $DISPLAY -install -iconic export LANG export PATROL_BROWSER=netscape -display $DISPLAY -install -iconic setenv PATROL_BROWSER=netscape -display $DISPLAY -install -iconic
Korn C
To use different arguments, set the value of PATROL_BROWSER to the appropriate string.
EXAMPLE
For a Korn shell:
export PATROL_BROWSER=/usr/local/bin/netscape -raise
75
Uninstalling PATROL for WebSphere Application Server

To uninstall PATROL for WebSphere Application Server you must use the same version of the installation utility that you used to install the product. Run the installation utility in uninstall mode to uninstall PATROL for WebSphere Application Server from your system.
WARNING
If you use a different version of the installation program to uninstall, you might remove files needed to perform uninstallation of other BMC Software products.
Determining the Version of the Installation Utility

To determine the version of the installer, perform the following procedure.
1 Access a command prompt and navigate to the appropriate location:

(Windows) <BMC_ROOT>\Uninstall (Unix) <BMC_ROOT>/Uninstall
2 Type the following command and press ENTER.

(Windows) uninstall.exe -v (Unix) ./uninstall.sh -v
Other Information to Know Before Uninstalling PATROL for WebSphere Application Server
NOTE
If you used the advanced profiling and instrumentation features of PATROL for WebSphere Application Server, you may need to uninstall Java components. See Removing Previous Profiling and Instrumentation Libraries on page 63.
76
Uninstalling PATROL for WebSphere Application Server on Unix

The following procedure describes how to uninstall PATROL for WebSphere Application Server from a Unix environment with or without a browser installed.
To Uninstall Individual Products Using the Installation Utility 1 Change to the Uninstall directory in your BMC Software product installation
directory and enter the following command to launch the installation utility in uninstall mode:
./uninstall.sh
2 The Welcome window is displayed, and click Next. 3 Select the installation directory from which you want to remove a product, and
click Next.
4 Select the product or products that you want to uninstall, and click Next. 5 Review your selections and click Uninstall.
After the uninstallation is complete, a window is displayed that tells you whether the uninstallation was successful.
To Uninstall Individual Products in a Unix Environment without a Browser 1 If you are uninstalling from a Unix environment without a browser perform the
following steps to launch the installation utility:
A From a command line, change to the Uninstall directory and enter the following
command to start the installation Web server:
./uninstall.sh -serveronly
A A message box is displayed that shows the URL to use to connect to the
installation Web server.
B On another machine with a browser, start the browser. C Connect to the installation Web server from the browser to start the installation
utility by using the URL that is displayed in the message box.
2 The Welcome window is displayed, and click Next.

3 Select the installation directory from which you want to remove a product, and
click Next.
Uninstalling All Products but Leaving Log Files and Configuration Files
This task describes how to uninstall the PATROL product but retain log files, which contain history for future analysis, and configuration files for redeployment.
1 Uninstall all products as described in To Uninstall Individual Products Using the

Installation Utility on page 77.
2 Locate the uninstall.ctl file in the following directory.

(Unix only) BMC_Products_Installation_directory/Uninstall/Install/instdata
3 Open the uninstall.ctl file in a text editor, and edit the /BMC/Base variable to specify
the name of the directory from which you removed the products in step 1.
4 Open a command line prompt. 5 Change to the following directory.

(Unix only) BMC_Products_Installation_directory/Uninstall/Install/ instbin
6 Enter the following commands:

(Unix only) thorinst.sh -uninstall path_to_control_file -log path_to_log_file -output
path_to_output_log_file
Use the following table to help determine the log file and output log file locations:
78
Option -log
Description sends the log information to a standard log file This file contains all installation status information.
Value path to log file; any valid path and file name (with a .txt extension) If a space exists in the path, the entire path must be enclosed in quotation marks.
-output
path to output log file; any valid path and file name (with a .txt This file contains all messages about extension) the progress of the installation that If a space exists in the path, are normally sent to standard the entire path must be output. enclosed in quotation marks. sends the log information to an output log file
Example (Unix only)

If /opt/bmc is your product installation directory, you would change to /opt/bmc/Uninstall/Install/instbin directory and enter the following command: thorinst.sh -uninstall /opt/bmc/Uninstall/Install/instdata/uninstall.ctl -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out This action would remove all installation files and directories except those that are used by the utility at the time the uninstallation is performed. Log files, configuration files, and user-modified files would also be retained.
Uninstalling All Products, Associated Log Files, and Configuration Files

This task describes how to remove all PATROL products and related log files and configuration files from your Unix computer. Once these files have been removed, you cannot recover them unless you have made a back-up copy of the installation.
1 Uninstall all products as described in To Uninstall Individual Products Using the

Installation Utility on page 77.
2 Locate the uninstall-all.ctl file in the following directory.

(Unix only) BMC_Products_Installation_directory/Uninstall/Install/instdata
3 Open the uninstall-all.ctl file in a text editor, and edit the /BMC/Base variable to
specify the name of the directory from which you removed the products in step 1.

(Unix only) BMC_Products_Installation_directory/Uninstall/Install/instbin
6 Enter the following command.

(Unix only) thorinst.sh -uninstall path_to_control_file -log path_to_log_file -output
path_to_output_log_file
Use the following table to help determine the log file and output log file locations: Option -log Description sends the log information to a standard log file Value path to log file; any valid path and file name (with a .txt extension) If a space exists in the path, the entire path must be enclosed in quotation marks. path to log file; any valid path and file name (with a .txt extension)
This file contains all installation status information.
-output
sends the log information to an output log file
This file contains all messages about the progress of the installation that If a space exists in the path, the entire path must be are normally sent to standard enclosed in quotation output. marks.
Example (Unix only)

If /opt/bmc is your product installation directory, you would change to /opt/bmc/Uninstall/Install/instbin directory and enter the following command:
80
thorinst.sh -uninstall /opt/bmc/Uninstall/Install/instdata/uninstall-all.ctl -log /var/logs/NetworkLogs/MyLogs.txt -output /var/adm/NetworkLogs/MyLogs.out This action would remove all installation files and directories. The files that were used to perform the uninstallation will be marked for deletion and will be removed when the computer on which the products were uninstalled is rebooted.
Uninstalling PATROL for WebSphere Application Server on Windows

You can use the option that is appropriate for what you want to uninstall to uninstall PATROL for WebSphere Application Server. The following procedures describe how to uninstall products from a Windows environment and all related log files.
To Uninstall Individual Products 1 From the Uninstall directory in your BMC Software product installation directory,
double-click uninstall.exe to launch the installation utility in uninstall mode.
NOTE
As an option, you can launch the installation utility in uninstall mode by choosing Start => Settings => Control Panel => Add/Remove Programs and double-clicking BMC Software Tools in the Add/Remove Programs Properties dialog box. If you are uninstalling from a Windows 2000 with Citrix Metaframe environment, perform the following steps to launch the installation utility in uninstall mode:
A From a command line, change to the Uninstall directory and enter the following
command to start the installation Web server:
setup.exe -serveronly
A message box is displayed that shows the URL to use to connect to the installation Web server.
B On another machine with a browser, start the browser. C Connect to the installation Web server from the browser to start the installation
utility by using the URL that is displayed in the message box. The Welcome window is displayed. Click Next.
2 Select the installation directory from which you want to remove a product, and
click Next.
Uninstalling All Products but Leaving Log Files and Configuration Files
This task describes how to uninstall the PATROL product but retain log files, which contain history for future analysis, and configuration files for redeployment.
1 Uninstall all products as described in To Uninstall Individual Products on

page 81.
2 Locate the uninstall.ctl file in the following directory.

(Windows only) BMC_Products_Installation_directory\Uninstall\Install\instdata
3 Open the uninstall.ctl file in a text editor, and edit the /BMC/Base variable to specify
the name of the directory from which you removed the products in step 1.

(Windows only) BMC_Products_Installation_directory\Uninstall\Install\ instbin

(Windows only) thorinst.exe -uninstall path_to_control_file -log path_to_log_file
-output path_to_output_log_file
82
Use the following table to help determine the log file and output log file locations: Option -log Description sends the log information to a standard log file This file contains all installation status information. Value path to log file; any valid path and file name (with a .txt extension) If a space exists in the path, the entire path must be enclosed in quotation marks. -output path to output log file; any valid path and file name (with a .txt This file contains all messages about extension) the progress of the installation that If a space exists in the path, are normally sent to standard the entire path must be output. enclosed in quotation marks. sends the log information to an output log file
Example (Windows only)

If C:\Program Files\BMC Software is your product installation directory, you would change to the C:\Program Files\BMC Software\Uninstall\ Install\instbin directory and enter the following command: thorinst.exe -uninstall C:\Program Files\BMC Software\Uninstall\Install\instdata\uninstall.ctl -log Z:\NetworkLogs\MyLogs.txt -output Z:\NetworkLogs\MyLogs.out This action would remove all installation files and directories except those that are used by the utility at the time the uninstallation was performed. Log files, configuration files, and user-modified files would also be retained.
Uninstalling All Products, Associated Log Files, and Configuration Files

This task describes how to remove all PATROL products and related log files and configuration files from your Unix computer. Once these files have been removed, you cannot recover them unless you have made a back-up copy of the installation.
83
1 Uninstall all products as described in To Uninstall Individual Products on

page 81.
2 Locate the uninstall-all.ctl file in the following directory.

(Windows only) BMC_Products_Installation_directory\Uninstall\Install\instdata
3 Open the uninstall-all.ctl file in a text editor, and edit the /BMC/Base variable to
specify the name of the directory from which you removed the products in step 1.

(Windows only) BMC_Products_Installation_directory\Uninstall\Install\instbin

(Windows only) thorinst.exe -uninstall path_to_control_file -log path_to_log_file -output path_to_output_log_file Use the following table to help determine the log file and output log file locations: Option -log Description sends the log information to a standard log file Value path to log file; any valid path and file name (with a .txt extension) If a space exists in the path, the entire path must be enclosed in quotation marks. path to log file; any valid path and file name (with a .txt extension)
This file contains all installation status information.
-output
sends the log information to an output log file
This file contains all messages about the progress of the installation that If a space exists in the path, the entire path must be are normally sent to standard enclosed in quotation output. marks.
84
Example (Windows only)

If C:\Program Files\BMC Software is your product installation directory, you would change to the C:\Program Files\BMC Software\Uninstall\ Install\instbin directory and enter the following command: thorinst.exe -uninstall C:\Program Files\BMC Software\Uninstall\Install\instdata\uninstall-all.ctl -log Z:\NetworkLogs\MyLogs.txt -output Z:\NetworkLogs\MyLogs.out This action would remove all installation files and directories. The files that were used to perform the uninstallation will be marked for deletion and will be removed when the computer on which the products were uninstalled is rebooted.

After installation is complete, turn to Chapter 3 for information about configuring PATROL for WebSphere Application Server.
85
86
Chapter
Configuration
After you install PATROL for WebSphere Application Server, you need to load the Knowledge Modules into the PATROL Console and configure the product. This chapter contains the following topics: Loading PATROL for WebSphere Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . 88 Initial KM Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Registering the WebSphere Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Configuring the Local Node Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Configuring the Local Deployment Manager Environment . . . . . . . . . . . . . . . . . . 94 Configuring the Remote Deployment Manager Environment . . . . . . . . . . . . . . . . 96 Configuring the Remote Application Server Environment . . . . . . . . . . . . . . . . . . 97 Verifying the Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 KM Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Adding and Removing Monitored Nodes in Your Environment . . . . . . . . . . . . 101 Setting the Monitoring Mode of Application Servers . . . . . . . . . . . . . . . . . . . . . . 103 Setting Specific Monitoring Options for Application Servers . . . . . . . . . . . . . . . 105 Scheduling Blackouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Creating or Adding to a Blackout Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Listing Blacked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Manually Stopping a Blackout Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Verifying Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Setting Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Configuration
87
Loading PATROL for WebSphere Application Server
Loading PATROL for WebSphere Application Server

After you install PATROL for WebSphere Application Server, you must load the product KM into the PATROL Console.
NOTE
Before the KM can successfully operate with IBM WebSphere Application Server, a default login shell must be defined that is valid for both the WebSphere Administration Account and the PATROL Default User Account, as explained in Default Login Shell on page 59. Before loading the product:
I I
start a PATROL Console start a PATROL Agent on each machine that you want to monitor
NOTE
PATROL for WebSphere Application Server can start even if no IBM WebSphere Application Server is running. However, in that case only the highest level icons will be generated.
To Load PATROL for WebSphere Application Server

1. Add to the PATROL Console those hosts on which PATROL for WebSphere Application Server is running. From the PATROL Console menu, choose Hosts => Add. 2. Load the product knowledge files. From the PATROL Console menu, choose File
=> Load KM...
3. Select PMW.kml, then click Open. 4. Save your console configuration so that PATROL automatically loads the selected KMs the next time you start the PATROL Console. From the PATROL Console menu, choose File => Save Configuration. After PATROL for WebSphere Application Server is loaded into the PATROL Console, you can configure the product using the WebSphere setup application class.

After you load the KM files, proceed with Initial KM Setup on page 89.
88
Initial KM Setup
Initial KM Setup
Initial KM setup consists of providing configuration information that defines your IBM WebSphere Application Server environment to the PATROL monitoring environment. The typical setup process is shown below.
KM Setup Process
Configure local node environment. See page 93.
Register the WebSphere Admin OS Account See page 90.
Configure local deployment manager environment. See page 94.
Verify runtime environment. See page 99.
Configure remote deployment manager environment. See page 96.
Configure remote application server environment. See page 97.
Chapter 3 Configuration
89
Initial KM Setup
Registering the WebSphere Account

Follow these steps to monitor a WebSphere environment.
1 Access the WebSphere Setup icon and choose KM Commands => KM Setup =>
Initial Setup.
The Setup Dialog screen is displayed. Figure 12 Setup dialog
90
Initial KM Setup
2 Fill in the WebSphere Node information: A In the WebSphere Home Directory box, type the full directory path (not a relative
path) in which IBM WebSphere Application Server is installed. This path is the value of the WAS_HOME environment variable, for example, d:\Program Files\WebSphere\AppServer on Windows NT/Windows 2000, or /usr/WebSphere/AppServer in AIX systems.
NOTE
For IBM WebSphere Application Server version 5, specify the path the directory at which the application server is installed. If you have an environment with only a Deployment Manager, enter the deployment manager path, for example: C:\ProgramFiles\Websphere\DeploymentManager
3 Fill in the WebSphere Admin OS Account information: A In the User ID box, type the username of the WebSphere Admin account (for
further information about this account, refer to on page 123).
B In the Password box, type the password for the WebSphere Admin account
specified in the User ID box. The password is case sensitive.
C Re-type the password in the Confirm Password box. 4 Check the box if you want to globally allow PATROL to set the PMI level. The
default is to allow PATROL to set the PMI level, and this is the recommended setting.
NOTE
If you uncheck this box, you may have conflicts or unexpected results when you try to set the PMI at a server level, as shown in Figure 22 on page 110.
NOTE
Checking the Allow PATROL to set PMI level in WebSphere only prevents the WebSphere KM from automatically changing the PMI level without the users knowledge. It does not prevent the PATROL user from manually changing the PMI level (i.e., WebSphere Performance Data Level Setting).
5 Click OK.
The Register WebSphere Environment dialog is displayed.
91
Initial KM Setup
NOTE
If the Registered Environment Selection is displayed, and not the Register WebSphere Environment dialog, it means that this is not your initial installation. Information about adding environments and modifying configurations is in KM Customization on page 101. Figure 13 Register WebSphere Environment dialog
6 Type a name for the environment. This will be used as an instance name. 7 Choose the type of WebSphere environment that you will be monitoring, then click
OK. Based on the environment type that you selected, a dialog will be displayed requiring you to define various configuration information.
I I
Local Node, see Configuring the Local Node Environment. Local Deployment Manager. Configuring the Local Deployment Manager Environment on page 94 Remote Deployment Manager. Configuring the Remote Deployment Manager Environment on page 96 Remote Application Server. Configuring the Remote Application Server Environment on page 97
92
Initial KM Setup
Configuring the Local Node Environment

To configure the local node environment, you will need to provide the instance configuration directory (defaults to the WebSphere install directory), local OS account (if needed to override default), and global security status and credentials if WebSphere global security is enabled for the cell to which this node belongs. Figure 14 Register Local Node dialog
1 In the Configuration Directory box, type the full directory path (not a relative path)
to the location of your configuration information.
2 Fill in the Java client connectivity information.
93
Initial KM Setup
A Use the pull-down menu to select the type of protocol used by your Java clients. NOTE
If you choose RMI, ensure that the version of WebSphere local to the machine running the PATROL Agent is that same as that of the WebSphere installation being registered by the KM. Connections from dissimilar versions may not work well due to differences in the underlying Java virtual machine implementation.
B If you want clients that connect to WebSphere to establish an environment

under the control of the setupCmdLine script, set the Invoke setupCmdLine script pull-down menu to Yes, otherwise, set it to No.
C If you have also defined an override script, type or copy the full path to that
script in the User setup script box.
D Enter the user name and password for the account used by Java clients, or
accept the default using local WebSphere Administrator.
E If global security is disabled, leave the WebSphere global security ID box

blank, otherwise, provide a user name and password as credentials, depending on the global security environment.
3 Click OK.
The next dialog that appears is the screen for setting PMI performance settings. Continue the setup process as described in Setting Specific Monitoring Options for Application Servers on page 105.
Configuring the Local Deployment Manager Environment

To configure the local deployment manager environment, you will need to provide the instance configuration directory (defaults to the WebSphere install directory), local OS account (if needed to override default), and global security status and credentials, if WebSphere global security is enabled for the cell to which this node belongs.
94
Initial KM Setup
Figure 15
Register Local Deployment Manager dialog
1 Fill in the Local Deployment Manager information. A In the Cell name field, enter the cell name as defined in your environment. B In the Configuration Directory box, type the full directory path (not a relative
path) to the location of your configuration information.
2 Fill in the Java client environment information. A If you want clients that connect to WebSphere to establish an environment
B If you have also defined an override script, type or copy the full path to that
C Enter the user name and password for the account under which Java clients are
to run, or accept the default using local WebSphere Administrator credentials.
95
Initial KM Setup
D If global security is disabled, leave the WebSphere global security ID box

blank, otherwise, provide a user name and password as credentials to be used by the KM, depending on the global security environment.
3 Click OK.
Configuring the Remote Deployment Manager Environment

To configure the remote deployment manager environment, you will need to provide the host name with SOAP or RMI port for contacting the deployment manager, WebSphere installation and instance configuration directories on the remote host, and global security status and credentials, if WebSphere global security is enabled for the cell to which this node belongs. Figure 16 Register Remote Deployment Manager dialog
96
Initial KM Setup
1 Fill in the Remote Deployment Manager information. A In the Remote Host box, enter the cell name as defined in your environment. B In the Port box, use the pull-down list to select the protocol type used for your
deployment manager and the port number on which it listens. This is, by default, 8879 for SOAP or 9809 for RMI.
NOTE
If you choose RMI, ensure that the version of WebSphere local to the computer that is running the PATROL Agent is the same as the version of the WebSphere installation being registered by the KM. Connections from dissimilar versions might not work well due to differences in the underlying Java virtual machine implementation. If the local installation of WebSphere (on the same host as the PATROL Agent) is 6.0.x and the managed system is running WebSphere 5.1.x, monitoring is possible only if the managed WebSphere Application Server installation is version 5.1.1.7 or later and the local WebSphere version is 6.0.2 or later.
2 Fill in the Java Client Connectivity information. A Select the connection protocol for the Java clients from the Protocol menu. B If you want clients that connect to WebSphere to establish an environment
under the control of the setupCmdLine script, set the Invoke setupCmdLine script menu to Yes; otherwise, set it to No.
D If global security is disabled, leave the WebSphere Global Security ID box

blank; otherwise, provide a user name and password as credentials to be used by the KM.
3 Click OK.
Configuring the Remote Application Server Environment

To configure the remote application server, you will need to provide basic configuration information, such as node name and host name with SOAP or RMI port, as well as WebSphere administrator and global security status and credentials.
97
Initial KM Setup
Figure 17
Register Remote Application Server dialog
1 Fill in the Remote Server information. A In the Remote Host field, enter the address of the server to be monitored. B In the Port box, specify the communication port number for the protocol you
use. By default, this will be 8880 if you use SOAP or 2809 if you use RMI.
2 Fill in the Java client environment information.
98
Initial KM Setup
A Use the pull down menu to select either SOAP or RMI as your protocl. NOTE
If you choose RMI, ensure that the version of WebSphere local to the computer that is running the PATROL Agent is the same as the version of the WebSphere installation being registered by the KM. Connections from dissimilar versions might not work well due to differences in the underlying Java virtual machine implementation. If the local installation of WebSphere (on the same host as the PATROL Agent) is 6.0.x and the managed system is running WebSphere 5.1.x, monitoring is possible only if the managed WebSphere Application Server installation is version 5.1.1.7 or later and the local WebSphere version is 6.0.2 or later.
B If you want clients that connect to WebSphere to establish an environment

D Enter the user name and password for the account under which Java clients are
to run.
E If global security is disabled, leave the WebSphere global security ID box

blank, otherwise, provide a user name and password as credentials to be used by the KM.
3 Click OK.
Verifying the Runtime Environment

As needed, display details of the runtime environment as it was set up and discovered. This information is displayed automatically at the end of the initial setup process, and can be displayed again on demand at any time.
1 Access the WebSphere Setup icon. 2 Access the KM Commands => KM Setup => Post-Install Runtime Verification ...
command. An information window opens displaying configuration information for each WebSphere environment that you defined during setup. There may be many sections in this window, each section corresponding to setup information for a particular server. Table 7 explains information that you should expect to see in the display.
99
Initial KM Setup
3 Click OK. If any information needs to be changed, access the Setup icon and
choose KM Commands => KM Setup => Initial Setup.
Table 7 Field
Runtime Environment Verification Fields Explanation JVM version located under the $WAS_HOME directory local to the PATROL Agent logical name of the registered environment type of environment, such as local node, local deployment manager, remote deployment manager, or remote application server communication protocol used by your deployment protocol (SOAP or RMI) name of the cell to be monitored name of the node to be monitored path where configuration information can be found; same as $WAS_HOME or %WAS_HOME% environment variable username for the WebSphere Adminstrator OS Account, explained in Local WebSphere Administrator OS Account on page 123 yes or no flag indicating whether clients that connect to WebSphere establish an environment under the control of the setupCmdLine script path and name of any locally defined override script type of WebSphere global security, such as none, LDAP/LTPA, or OS level authentication if global security is enabled, the ID used as credentials by the PATROL KM WebSphere server instance
Java full version Registered Environment Name Environment Type
Protocol Cell Name Node Name Configuration Directory WebSphere OS Account
Invoke setupCmdLineScript
Optional Setup Script WebSphere Global Security WebSphere Global Security ID Application Server
Where to go from here

After you have completed initial setup, you can specify preferences for your monitored IBM WebSphere Application Server environments. These preferences include the alarm status of application servers, the services that you choose to activate, and the parameters you choose to make available. To make those selections, go on to the next sections starting with Setting the Monitoring Mode of Application Servers on page 103, which explain how to customize the KM to your specific needs.
100
KM Customization
KM Customization
After you have registered the WebSphere Admin account, registered the WebSphere Administration DB account, and registered the WebSphere LTPA account (if needed), you are ready to begin customizing the monitoring features of the KM. This section explains how to complete initial customization.
NOTE
Customization is a central part of preparing the product for initial monitoring, reporting, and management, but is also an ongoing part of using the product capabilities you need, but using only what is necessary for the needs of your environment at any given time. For this reason, you will perform some of the tasks described in this section repeatedly as your needs require.
Adding and Removing Monitored Nodes in Your Environment

After a WebSphere environment is configured and monitored, you may want to add additional environments for monitoring, make changes to your existing configuration, or remove WebSphere environments from your previous PATROL configuration. All of these functions are done using the same setup process as the Initial Setup, but with an additional screen that allows you to select environments and make changes to a configuration.
To Change an Environment Configuration 1 Access the WebSphere Setup icon and choose KM Commands => KM Setup =>
Initial Setup.
The Setup Dialog screen is displayed.
2 Click OK.
Chapter 3
Configuration
101
KM Customization
The Registered Environment Selection dialog is displayed.
3 If you want to stop monitoring an environment or you want to change

configuration information about an environment, click the environment name from the list of currently registered and monitored environments to select it. If you want to add a new environment, do not select an environment name.
4 Click the radio button to select the type of change you want made.
I
Modify selected environment will allow you to change configuration information about the selected environment. After you click OK, you will go through the
same set of screens as you did for the initial setup process, the only difference will be that fields will be populated with settings for the selected environment and changes you make will affect the existing environment settings. See Initial KM Setup on page 89. Register a new environment goes through the initial setup process so that you can configure additional environments for monitoring. See Initial KM Setup on page 89. Remove selected environment deletes your environment configuration. This will remove the instance from the PATROL tree and will clean pconfig variables.
5 Click OK to perform the selected action.
102
KM Customization
Setting the Monitoring Mode of Application Servers

In this task, you will specify whether to monitor an application server and specify what each server is to do when an alarm is issued.
NOTE
The dialog used to perform this task launches automatically during initial setup, can be manually launched later.
1 Access the WebSphereSetup icon. 2 Choose KM Commands => Customization=>Monitor Options ....
A dialog box such as the following will open: Figure 18 Application Server Monitoring Modes Dialog Box
3 Highlight one or more discovered servers so you can set the monitoring mode. A Click once on each server you want to highlight. B Click again on any highlighted server you want to deselect.
Chapter 3
Configuration
103
KM Customization
4 For the highlighted servers, select a monitoring mode:

Table 8 Application Server Monitoring Modes Effect Monitoring is active for the highlighted application servers. The alarm events for the associated AppServerAvailability parameter are issued as defined. Monitoring is active for the highlighted application servers. The alarm events for the associated AppServerAvailability parameter are suppressed. Monitoring is disabled for the highlighted servers. The associated instance icons are in the offline state and all alarm events are suppressed. Set the monitoring and alarm behavior to the value selected for the Default Setting. (See section text below).
Monitoring Mode Enable Alarms
Disable Alarms
Do Not Monitor
Use Default Setting
5 In the box next to Default Setting is, specify a default setting.

For all servers with a monitoring mode of Use Default Setting, you can changes the monitoring mode without highlighting servers another time, simply by changing the default monitoring setting. Possible default settings include Enable Alarms, Disable Alarms, and Do Not Monitor, as explained in Table 8.
6 Click OK.
The Monitoring and Alarm Setting columns will reflect the settings you have just specified.
7 Repeat Steps 2 and 3 until you have set or changed all monitoring modes you want
to put into place.
8 Click Exit. A confirmation box appears:
104
KM Customization
A Click Yes to commit the monitoring options you have set or changed (to apply
the changes to the operations of the application servers) and to go on to the next task.
B Click No to discard the changes to monitoring options you have just made, but
to go on to the next task.
9 Go on to the next task: Setting Specific Monitoring Options for Application

Servers.
Setting Specific Monitoring Options for Application Servers

In this task, you will specify which monitoring and management services to activate for each application server. The dialog box in Step 2 is automatically displayed when you configure some types of WebSphere environments.
NOTE
In this task, you will make choices that could significantly affect the level of performance monitoring at which your application server is set. More information about performance levels is available from IBM at the IBM WebSphere InfoCenter (http://www-306.ibm.com/software/webservers/appserv/infocenter.html)
1 Access the WebSphere Setup icon. 2 Choose the Customization=>Performance Data Selection .... command
A dialog box illustrated in Figure 19 opens:
Chapter 3
Configuration
105
KM Customization
Figure 19
Monitoring Options for Application Servers Dialog Box
3 Select the server for which to set options. A If the server name is listed, click the server, click to highlight the Modify
operation, then click OK.
B If you wish to clear all options and have a server use the default settings, click
the server name, click the Restore Default Settings operation, then click OK.
NOTE
If you modify the Default Server, further selections you make in this task, if committed, will apply to all application servers, regardless what options might previously have been activated.
4 Click OK.
A Performance Data Selection dialog box, illustrated in Figure 20, opens:
106
KM Customization
Figure 20
Performance Data Selection Dialog Box
PMI data
bytecode instrumentation data
5 Select the Performance Data Selection services you need for your environment.
Performance Data Selection are divided into two groups: First Group This group uses PMI monitoring that is a part of IBM WebSphere Application Server. This group also uses log monitoring developed by BMC Software. The effect on performance of each selection varies by the resources required for the related collection and display of monitored data. Second Group The second group enables J2EE bytecode instrumentation for
I I I
SQL Performance Web Applications Servlet method performance
Chapter 3
Configuration
107
KM Customization
You can also enable transaction monitoring as a part of this procedure. See Activating and Deactivating Transaction Monitoring on page 189 for more information.
NOTE
Enabling any of these three services requires a restart of the application server. However, after the application server is restarted to enable any service in this group, the other services can be enabled by use of this dialog box without an additional application server restart.
6 Click OK.
For each Performance Data option selected, a Parameter Selection Dialog box will open. Figure 21 Parameter Selection Dialog Box
7 Specify which parameters to activate for collection and display:

I
To select parameters to be activated, perform the following steps: 1. In the Available Parameters list, select each parameter to be activated. 2. Select the Select parameters option.
108
KM Customization
3. Click OK.
I
To select parameters to be deactivated, perform the following steps: 1. In the Selected Parameters list, select each parameter to be deactivated. 2. Select the Deselect parameters option. 3. Click OK.
When you have made all of the necessary changes in parameter activation for this service, perform the following steps: 1. Select the Done option. 2. Click OK.
8 If no changes are required for a particular selected monitoring option, click Cancel
to move on to the next selected monitoring option.
9 Repeat steps 6 or 7 for each selected monitoring option.

When you have selected parameters for activation or cancelled from each selected monitoring option, the Performance Data Selection dialog box reappears.
10 Click Exit.
A confirmation box appears:
11 Click Yes to activate the selected parameters for each selected monitoring option
and to go on to the next task. (Click No to discard the changes to monitoring options you have just made.) If the parameter activation changes you selected require a different performance data monitoring level, a Performance Data Level dialog box appears.
Chapter 3
Configuration
109
KM Customization
This dialog box varies, depending on the WebSphere version. With WebSphere 6, IBM introduced a new way of organizing PMI metrics, based on categories called Basic, Extended, All, or Custom (which gives you very fine-grained control over which metrics are collected, building your own set of metrics that spans the pre-defined categories). Figure 22 shows the categories for WebSphere 6. Figure 22 Performance Data Level Dialog for WebSphere 6
this option can be either None or Disabled
NOTE
If this dialog is brought up for a server on which PMI is disabled, the None option will instead be labelled Disabled. If PMI was disabled on a server, and you click a performance level setting on this dialog, a message will be displayed asking if you want to enable PMI for the server. Click Yes to change the setting and enable PMI on the server, effective when the server restarts. If you are using the Custom setting with WebSphere 6 or later, the KM will not automatically try to change the setting even if the Allow PATROL to Set PMI level in WebSphere option was enabled during Setup (see Figure 12 on page 90), but the level can still be reset from this dialog.
12 To set the performance data level to the requirement for the parameters you have
chosen to activate, select the option that is no lower than that specified in the Required Setting: field, and then click OK. Use the Inherit WebSphere PMI Setting when you want PATROL to use the level set from within WebSphere. The performance data levels that are actually set and used by PATROL are set from this dialog, but can be affected by the global setting that allows PATROL to set the PMI level (see Registering the WebSphere Account on page 90).
110
KM Customization
If the global setting is to not allow PATROL to set the PMI level, you can change the PMI level in this step, but no further PMI level change is done. Only if the global setting allows PATROL to set the PMI level will your changes from this dialog be reliably used.
13 Should you select a lower performance level than is required, a warning similar to
the following appears:
14 If this dialog appears, do one of the following:

I
Click Yes to commit the performance level you selected. Some of the parameters you selected for activation will not be generated. Click No to return to the Performance Data Level Dialog, where you can specify a performance data level at least as high is required for the parameters you selected. Perform step 12 on page 110 again.
15 Restart the server.

An application server must be restarted if either of the following changes are made in parameter selection: Any parameter requiring J2EE bytecode instrumentation or JVM profiling is selected if profiling and instrumentation are not already active If either of these conditions applies, a dialog will appear that offers to restart the servers involved.
I
To let the KM restart the servers, click Yes. At the next collection cycle, the application servers will be restarted, and the parameter changes you select will go into effect. To keep the KM from restarted the servers, click No. The application servers will not be restarted, and the changes you selected will not be put into effect.
Chapter 3
Configuration
111
Scheduling Blackouts
The blackout mechanism provides a way to suspend collection and display operations temporarily in PATROL for WebSphere Application Server without shutting the product down. This mechanism can be useful when it becomes necessary to shut down one or more application servers, and when alarms and associated recovery actions such as e-mails and pages are not needed. On example might be during routine backup operations. The following task, on page 112, explains how to set one or more blackouts to occur routinely by a schedule you specify. (You can also create an on-demand blackout by suspending collection and display for a specified application server or for all application servers in your environment. See on page 168 for more information.)
Creating or Adding to a Blackout Schedule

This task explains how to create a blackout schedule or to modify a blackout schedule that was previously created.
1 Access the Setup icon and choose the KM Setup=>Blackout=>Setup Blackout

Schedule command. A dialog box similar to the following appears:
Figure 23
Initial Blackout Schedule Dialog Box
2 Select Add. (If this is the first blackout period you are scheduling, Add is the only
option that appears.)
3 Click OK.
A dialog box similar to the following appears: Figure 24 Add Blackout Period Dialog Box
4 Define the specifics for the blackout period: A In the Blackout Name box, type a name that represents the blackout period for
you. This can be any combination of letter and numbers you choose.
B In the Server Name box, select <All> to blackout all application servers on the
host, or click the down arrow on the right side of the box, and choose one of the discovered application servers in the list.
C In the Start Time area, specify days of the week on which the blackout to occur
and the time of each scheduled day at which the blackout is to begin:
Chapter 3
Configuration
113
1. Click once in the square by each day on which you want to schedule the blackout. Click again to remove a day from the schedule. 2. Using the up and down arrows on the right side of the Hour and Minute boxes, select the time at which the blackout is to begin, based on a 24-hour clock. For example, if you want the blackout to start at 10:35 P. M., set the Hour box to 22 and the Minute box to 35.
NOTE
Blackout schedules are based on the time zone in which IBM WebSphere Application Server and the PATROL Agent are located. If the Console is in a different time zone, take that difference into account as you set blackout schedules.
D Using the up and down arrows on the right side of the Days, Hours, and Minutes
boxes in the Duration section, specify how long the blackout is to last.
E Click OK.
The Setup Blackout Schedule dialog box re-appears, with the information you specified now in place, similar to the following: Figure 25 Initial Blackout Schedule Dialog Box
5 If you want to schedule another blackout, select Add, click OK, and complete
another blackout period definition as explained in the previous steps.
6 When you have added the blackout periods needed at your site, and the Setup
Blackout Schedule dialog reflects your desired blackout schedule, click Done.
114

When a blackout occurs, you can verify that the objects you specified for blackout are in fact blacked out. Listing Blacked Out Objects on page 115 explains how to perform this verification.
Listing Blacked Out Objects

This task explains how to use menu commands to list the objects suspended in a blackout. This task is a follow-up for Creating or Adding to a Blackout Schedule on page 112 and is specific to that task. However, this task uses the same principles that are used to verify blackouts that begin with an invocation of the Suspend Monitoring command of the PMW_MAIN application class (for all application servers in the environment).
1 Schedule one or more blackouts as explained in Creating or Adding to a Blackout

Schedule on page 112.
2 When the scheduled day and time has elapsed for a blackout to occur, access the
WebSphere Setup icon, and choose the KM Setup=>Initial Setup=>Blackout=>List Blackout Objects command. A report appears that lists objects that are blacked out at the time the List Blackout Objects command is executed.
3 Scroll down the list of objects that have been blacked out and verify that all the
objects you expected to be suspended by the blackout are on the list.
4 When you have finished inspecting the report, close the window by clicking on the
X in the upper-right corner.
Manually Stopping a Blackout Period

A blackout period can be stopped manually before it expires, regardless of how the blackout was started.
1 Access the WEBSPHERE, or the WebSphere icon.

I
Access the top-level WebSphere icon to stop a blackout and resume monitoring for all servers in an environment.
2 Choose the Blackout=>Resume Monitoring KM Command.
Chapter 3
Configuration
115
Verifying Discovery
At the beginning of the next collection cycle (within 60 seconds by default), collection and display operations will resume according to their respective schedules.
Verifying Discovery
After you have set up your IBM WebSphere Application Server, verify that the WEBSPHERE icon appears in the PATROL Console and that all servers, containers, and instances that you expect to see are discovered and are displaying appropriate performance data. 1. From the PatrolMainMap, open the computer window and verify that the WebSphere icon is present, as shown in Figure 26. This icon is a container that represents the environment under a WebSphere administration server for the given host or node. Figure 26 WebSphere Icons in PATROL Console
Icon representing IBM WebSphere environment
2. Double-click the WebSphere icon to see which application servers are being monitored. There will be as many application server instances at this level as you registered. If you went through the configuration process only one time for a single server, you will see one server instance icon. To add more servers, repeat the setup process described on page 89. 3. Double-click a server instance icon.
116
Verifying Discovery
You should see several icons in the PATROL window, corresponding to the container application classes described in Chapter 1.
4. Double-click one of the container icons. You should see subservices or parameters you selected for activation. If you do not see the parameters or subservices you expected, you may have missed a step in setting up performance monitoring, including setting the application server to the required performance monitoring level. 5. Continue double-clicking container icons and reviewing parameters until you are satisfied that the system is being correctly monitored.
Chapter 3
Configuration
117
Verifying Discovery
Identifying Potential Setup Problems

If your WebSphere environment is not fully discovered or performance parameters are missing or incorrect, it may indicate one of the following configuration problems:
I
I I
Discovery not completing: If discovery fails, consult the operating system vendor to find out how to set user limits. The limits for the following should be unlimited I File size I Max memory size I CPU time I Virtual memory Incorrect Information in Setup Parameters: Open the PATROL Console system output window and read the status messages. Look for messages that might indicate a specific problem, such as a user authentication failure, or incorrect WebSphere home directory path. Correct any setup problems as described in Initial KM Setup on page 89. XMLConfig.sh: Verify that the XMLConfig.sh file has execute permission enabled. DLL Conflict in Windows NT: Check to see if the NTRegistry.dll file exists in both the PATROL KM for Windows NT and in the WebSphere Application Server. If it does, apply PATROL KM for Windows NT patch 3.6.07, available from BMC Software. PATROL Agent-E-EUSER: Invalid username/password for the command of type 'OS' for instance 'PMW_MAIN.WebSphere' -command not executed. and PMW_SETUP.PMW_SETUP Command, Line# 6136: execute: couldn't execute OS command. This error is most generally the result of an issue with the users permission to read or execute files. Ensure that the following directories (and relevant subdirectories and files) have the appropriate permissions for the PATROL user (read and execute): I $PATROL_HOME/pmw_WebSphere I $WAS_HOME/java/bin
NOTE
This list of directories is not exhaustive and will vary depending on factors such as WebSphere Application Server version, type (base or network deployment), and global security activation.

You are now ready to monitor and manage your IBM WebSphere Application Server environment. However, the KM can interact successfully with IBM WebSphere Application Server, the right accounts must be in place and must have the access they require.
118
Setting Debug Flags
To review security, including its relationship to WebSphere Application Server and the KM, refer to Chapter 4, Security. For more information about parameters, menu commands, or detailed information about using features of PATROL for WebSphere Application Server, see the other chapters in this User Guide, or see the Help.
Setting Debug Flags

Two levels of debug information can be generated by PATROL for WebSphere Application Server:
I
KM debug information: provides diagnostic information about the status of the PATROL for WebSphere Application Server JMX debug information: provides diagnostic information about only the parts of the KM that monitor JMX Mbeans
BMC Software recommends turning on debug features only under the advice of BMC Software support staff. To turn on KM debug information, see Setting KM Debug Trace Flags on page 119. To turn on JMX debug information, see Setting JMX Debug Flags on page 223.
Setting KM Debug Trace Flags

You can turn on flags that save trace data to a file. This data file is useful to BMC Software support personnel in troubleshooting KM problems.
NOTE
The debug options set in PATROL for IBM WebSphere ASAE are used to save KM trace data only. This is not a general tool for debugging problems in the WebSphere environment.
To set KM debug flags 1 Right-click the WebSphere Setup icon. 2 From the KM Commands menu, choose Debug Options.
Chapter 3
Configuration
119
Setting Debug Flags
The Debug Option dialog is displayed.
3 Select one or more types of trace data that you want saved, or check the All
Components checkbox to save all trace data.
4 Click OK.
120
Chapter
4
122 122 123 130 131 131 132
Security
This chapter explains security matters that relate to PATROL for WebSphere Application Server. The chapter contains the following sections: WebSphere Application Server Security and the KM . . . . . . . . . . . . . . . . . . . . . . . . . WebSphere Global Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local WebSphere Administrator OS Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebSphere Global Security and the KM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KM Command Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . KM Command Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATROL Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security
121
WebSphere Application Server Security and the KM

This section briefly reviews IBM WebSphere Application Server security and explains the relationship between WebSphere security and the successful operation of the KM. The section concentrates mostly on the characteristics and requirements of the WebSphere Administrative OS Account (WebSphere Admin) because that account is central to the monitoring and management services that the KM offers. In addition explains the requirements for successful KM operation when WebSphere (global) security of any kind is enabled.
WebSphere Global Security Overview

PATROL for WebSphere Application Server supports all types of security levels provided within IBM WebSphere Application Server. IBM WebSphere Application Server provides mechanisms to establish security policies for all servers, applications, and resources that make up the WebSphere environment. You can apply security settings via the WebSphere Administrative Console. These policies are then enforced by a Security Plugin on the web server and the Security Collaborator on the application server. Permissions can be established on components at various levels with the Security Application authenticating users and controlling access. If you are using WebSphere security for the first time, read the security information provided in the IBM WebSphere Application Server documentation and on IBMs web site (www.ibm.com). This documentation explains how the various components of the WebSphere security model work together and how security is implemented. WebSphere global security is used to prevent access to the Administrative Server, Administrative Console, or configuration utilities such as wscp, XMLConfig, or wsadmin. Implement security using WebSpheres Administrative Console. If you decide to use LDAP authentication, you must also configure an LDAP directory server, such as IBM SecureWay Directory. PATROL for WebSphere Application Server will work with any LDAP server that is supported by IBM WebSphere Application Server.
122
The following general authentication methods apply to an IBM WebSphere Application Server environment:
I
None: security is not managed from within WebSphere, but rather from the
operating system, Java environment, or web server. Local OS: access is monitored and controlled by WebSphere via user names and passwords verified using native operating system services. LTPA: Lightweight Third Party Authentication (LTPA) is done by searching a Lightweight Directory Access Protocol (LDAP) server. LDAP/LTPA works in conjunction with user registry information stored in a database (such as DB2). Custom: Custom security levels for access to WebSphere are applicable.
PATROL for WebSphere Application Server will support security at any of the above levels. A full discussion of configuring and managing security with LDAP/LTPA is beyond the scope of this document. See the IBM documentation that applies the versions you have installed at your site for full details about installing and implementing LDAP/LTPA security for your site.
Local WebSphere Administrator OS Account

The WebSphere Administrator Account is a crucial piece in the successful operation of the KM to monitor and manage in an IBM WebSphere Application Server environment. This account is used to launch Java clients that read files in the local WebSphere environment and connect to local and remote WebSphere servers, and in certain circumstances write files to the WebSphere environment. This section provides the characteristics and requirements of the WebSphere Administrator OS account. The Local WebSphere Administrator OS account is specified at two levels:
I
through the initial setup dialog, which is used for accessing WebSphere files for initial discovery and to start Java clients for Remote Deployment Manager and Remote Application Server environments when registering a Local Node or Local Deployment Manager environment, which is used to access files specific to that environment and to start Java clients to connect to servers in that environment.
Usually, you can use the same account for all cases.
Chapter 4
Security
123
Characteristics of the WebSphere Administrator OS Account

The WebSphere Admin account does not have to be called WebSphere Admin, but will be referred to by that name for the sake of this discussion. Whether it is the WebSphere OS account or another account created specifically for interaction with PATROL for WebSphere Application Server, the account must
I
be an authorized WebSphere user account with the ability to invoke WebSphere utilities such as setupCmdLine, and wsadmin. As explained in Default Login Shell on page 59, this requires that the default login shell be set to the Bourne shell (/bin/sh) or the Korn shell (/bin/ksh). have read and write access to the pmw_WebSphere and j2ee subdirectories or folders in the PATROL installation directory meet requirements defined in Unix Requirements on page 124 or Windows Requirements on page 128. have the appropriate permissions (read and execute) for the PATROL user on the following directories (and relevant subdirectories and files):
I I
$PATROL_HOME/pmw_WebSphere $WAS_HOME/java/bin
NOTE
This list of directories is not exhaustive and will vary depending on factors such as WebSphere Application Server version, type (base or network deployment), and global security activation.
NOTE
There may be occasions (particularly during initial installation and configuration) when the PATROL account must be able to access the WAS_HOME directories ($WAS_HOME in Unix or %WAS_HOME% in Windows). If you experience access problems, add the PATROL account to the same group as the WebSphere Admin account so that PATROL can access the WebSphere configuration directories.
Unix Requirements
On Unix systems, the WebSphere Admin account must fill the following specific requirements:
124
1. WebSphere Admin account must be a member of the PATROL primary group.
NOTE
Before a WebSphere Administrator with a non-root account on a Unix system can use PATROL for WebSphere Application Server for the first time, the WebSphere Admin OS Unix ID must added to the PATROL Unix group, and the PATROL Agent must be restarted. 2. The WebSphere Admin account must have certain privileges relative to $WAS_HOME, $JAVA_HOME, and $USER_INSTALL_ROOT. For Unix,
I
$WAS_HOME is typically /opt/WebSphere/AppServer for WebSphere 5 or for /opt/IBM/WebSphere/Appserver for WebSphere 6 $JAVA_HOME is where the JDK or JRE resides. It is usually $WAS_HOME/java , but could be a path oustide $WAS_HOME. For WebSphere 5, $USER_INSTALL_ROOT is usually the same as $WAS_HOME. An exception to this would be a WebSphere node created using the wsinstance utility, in which case $USER_INSTALL_ROOT is defined when you execute wsinstance. For WebSphere version 6, $USER_INSTALL_ROOT is established by defining a profile, and is usually $WAS_HOME/profiles/<profile_name>.
NOTE
$JAVA_HOME must be the location of the JVM used by IBM WebSphere Application Server.
Chapter 4
Security
125
3. The WebSphere Admin account must have recursive READ privileges:

I
READ requirements with all versions (unless noted): I $WAS_HOME (Top Level) I $WAS_HOME/properties/sas.server.props I $WAS_HOME/properties/sas.client.props I $WAS_HOME/etc/wsserver.key I $WAS_HOME/properties/wsserver.key I Any additional files required to resolve WebSphere Global Security authentication I $JAVA_HOME (recursive READ access) I $WAS_HOME/bin/*.jar I $WAS_HOME/lib/* I $USER_INSTALL_ROOT/config/cells/<cell_name>/security.xml I $USER_INSTALL_ROOT/properties/soap.client.prop I $USER_INSTALL_ROOT/properties/version/BASE.product I $USER_INSTALL_ROOT/config/cells/<cell-name>/ virtualhosts.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/serverindex.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/variables.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/servers/<server-name>/server.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/servers/<server-name>/variables.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/resources.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/resources.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/<node-na me>/servers/<server-name>/resources.xml
126
additional READ requirements only with WebSphere 5.0 or later if the wsinstance tool is used to define additional nodes: I $WAS_HOME/properties/wsinstance.config I $USER_INSTALL_ROOT/config/cells/<cell-name>/ virtualhosts.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/ <node-name>/serverindex.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/ <node-name>/variables.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/ <node-name>/servers/<server-name>/server.xml I $USER_INSTALL_ROOT/config/cells/<cell-name>/nodes/ <node-name>/servers/<server-name>/variables.xml
4. WebSphere Admin must have recursive READ/EXECUTE privileges to the following:

I
READ/EXECUTE requirements: I $WAS_HOME/bin/startServer.sh I $WAS_HOME/bin/stopServer.sh I $WAS_HOME/bin/setupCmdLine.sh I $WAS_HOME/bin/wsadmin.sh
5. If you are going to use profiling, WebSphere Admin must have recursive READ/WRITE/EXECUTE privileges for the owner and group, and READ/WRITE privileges for the bin and lib directories, for example:
I I
AIX: $JAVA_HOME/jre/bin Solaris: $JAVA_HOME/jre/lib/sparc
6. If you are going to use bytecode instrumentation, WebSphere Admin must have recursive READ/WRITE/EXECUTE privileges for the owner and group, and READ/WRITE privileges for the world for the shared library directories:
I
$JAVA_HOME/jre/lib/ext
Also, WebSphere Admin must be able to create the directory $JAVA_HOME/BMCSoftware 7. If you are going to activate JMX Management, WebSphere Admin must have recursive READ/WRITE privileges to the following:
I
$WAS_HOME/config/temp
Also, WebSphere Admin must be able to create the directory $JAVA_HOME/BMCSoftware
Chapter 4
Security
127
Windows Requirements
On Microsoft Windows systems, the WebSphere Admin account must fill the following specific requirements: 1. Have recursive READ access to the PATROL installation directory, and WRITE access to the \WebSphere subdirectory under the PATROL installation directory. 2. If you are using the PATROL Agent 3.5.30 or later, the PATROL Agent account must also have the following rights:
I I I
Act as part of the operating system Logon as a service Replace a process level token
3. The WebSphere Admin account must have certain privileges relative to %WAS_HOME% or %JAVA_HOME%. Typically,
I I I
%WAS_HOME% is C:\Program Files\WebSphere\AppServer %JAVA_HOME% is where the JDK resides. It could be %WAS_HOME%\java For WebSphere 5, %USER_INSTALL_ROOT% is usually the same as %WAS_HOME%. An exception to this would be a WebSphere node created using the wsinstance utility, in which case %USER_INSTALL_ROOT% is defined when you execute wsinstance. For WebSphere version 6, %USER_INSTALL_ROOT% is established by defining a profile, and is usually %WAS_HOME%\profiles\<profile_name>.
NOTE
%JAVA_HOME% must be the location of the JVM used by IBM WebSphere Application Server.
128
4. The WebSphere Admin account must have recursive READ privileges: With all versions of WebSphere: I %WAS_HOME% (Top Level) I %WAS_HOME%\properties\sas.server.props I %WAS_HOME%\properties\sas.client.props I %WAS_HOME%\etc\wsserver.key I %WAS_HOME%\properties\wsserver.key I Any additional files required to resolve WebSphere Global Security authentication I %JAVA_HOME% (recursive READ access) I %WAS_HOME%\bin\*.jar I %USER_INSTALL_ROOT%\config\plugin-cfg.xml I %WAS_HOME%\lib\* I %WAS_HOME%\properties\com\ibm\websphere\product.xml I %USER_INSTALL_ROOT%\config\cells\<cell_name>\security.xml I %WAS_HOME%\properties\soap.client.prop I %WAS_HOME%\properties\version\BASE.product I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\serverindex.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\variables.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\servers/<server-name>\server.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\servers\<server-name>\variables.xml additional READ requirements only if the wsinstance tool is used to define additional nodes: I %WAS_HOME%\properties\wsinstance.config I %USER_INSTALL_ROOT%\config\cells\<cell-name>\ virtualhosts.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\serverindex.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\variables.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\servers\<server-name>\server.xml I %USER_INSTALL_ROOT%\config\cells\<cell-name>\nodes\ <node-name>\servers\<server-name>\variables.xml
I
Chapter 4
Security
129
5. WebSphere Admin must have recursive READ\EXECUTE privileges to the following:

I
READ/EXECUTE requirements: I %WAS_HOME%\bin\startServer.bat I %WAS_HOME%\bin\stopServer.bat I %WAS_HOME%\bin\setupCmdLine.bat I %WAS_HOME%\bin\wsadmin.bat
6. If you are going to use profiling and bytecode instrumentation, WebSphere Admin must have recursive READ/WRITE privileges to the following:
I I
%JAVA_HOME%\jre\bin %JAVA_HOME%\jre\lib
Also, WebSphere Admin must be able to create the directory $JAVA_HOME/BMCSoftware 7. If you are going to activate JMX Management, WebSphere Admin must have recursive READ/WRITE privileges to the following:
I
%WAS_HOME%\lib
Also, WebSphere Admin must be able to create the directory $JAVA_HOME/BMCSoftware
WebSphere Global Security and the KM

If IBM WebSphere Application Server global security is enabled, the KM can monitor and manage only if you have registered the appropriate account with the KM so that the KM can authenticate with the security. Typically global security deployed with IBM WebSphere Application Server is either a form of LTPA security or the security in place with the operating system (Local OS security). In either case, you can register the KM with the global security by supplying the KM with the username and password of the global security account for each registered environment. After you have completed this registration once, it is not necessary to supply the information again unless a global security setting changes. The KM retains the username and password you supplied and authenticates each time that sort of security is enabled when the KM starts.
130
KM Command Security
In a typical IBM WebSphere Application Server installation, global security is implemented in a choice to use either OS local security or LTPA security. As you evaluate these two techniques at your site, you may change your WebSphere configuration to use one or the other. Bear in mind that anytime you change the global security account, you must register this change in the KM. Specify a global security username and password for each environment registered, or none for environments in which global security is not enabled.
Registering After Initial Setup

If global security is not enabled when the KM is being set up but becomes enabled later, it is necessary to re-run the KM Setup, as described in Chapter 3.
1 Access the WebSphere Setup icon. 2 Access the KM Setup=>Inital Setup... command. 3 Click OK to view the list of registered environments. 4 Modify the appropriate environment(s) with the global security ID and password.
KM Command Security
The object of KM command security is to ensure that only authorized users are able to use the KM to perform critical management operations.
KM Command Security
This section explains KM security when the KM is used to monitor and manage IBM WebSphere Application Server.
Operations Affected by the Security Policy

When the KM is used to monitor and manage IBM WebSphere Application Server, KM security is invoked every time a stop or restart operation is invoked by KM command. That policy involves the following operations:
I
Stopping application servers, node agents, deployment managers, and clusters
Chapter 4
Security
131
PATROL Security
Security Mechanism
Every time a user attempts one of the operations in the list above, before the operation executes, a dialog box is displayed that requires a username and password. However, the username and password required are sometimes different from those required when the KM is managing earlier versions of IBM WebSphere Application Server:
I
If WebSphere security is not enabled, the WebSphere Admin username and password satisfy the requirement. If WebSphere security is enabled, username and password of the account controlling the security is required. This is typically the LTPA security account or the Local OS security account.
This KM command mechanism is used purely by the KM. Although it uses information from WebSphere global security if the KM is monitoring IBM WebSphere Application Server with global security enabled, the KM command security does not alter WebSphere global security.
PATROL Security
If you are using PATROL 3.5 or later, you can secure data passed between PATROL components and can restrict unauthorized access to data by setting security levels. Five security levels, or policies, are defined. The lowest level (0) is a minimal level of security and has no configuration requirements. The highest security policy (4) requires authentication between all communicating components and validation of connection requests to key databases. High security requires significant configuration of communicating components (such as the agent and console) and is more difficult to use than lower levels. You can select the security level that best balances the ease of use with your need for security. All components in a system, including agents and consoles, must operate at the same level of security in order to communicate with each other. This requirement is ensured when you install PATROL with basic security (the default level of 0).
NOTE
Review security level definitions in the PATROL Security User Guide before installing PATROL products or implementing security levels. All components in a system, including agents, consoles and KMs, must use the same security level.
132
Chapter
5
134 134 135 138 138 139 139 140
Tuning the KM
The chapter presents the following topics: General Tuning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Application Servers Only as Needed . . . . . . . . . . . . . . . . . . . . . . . . . Limiting the Number of Available Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . Tuning Collection Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limiting Log Monitoring Scan Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Profiling and Instrumentation Judiciously. . . . . . . . . . . . . . . . . . . . . . . . . . Using Blackouts Effectively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Tuning for Large Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tuning the KM
133
General Tuning Considerations
General Tuning Considerations

For many sites, PATROL for WebSphere Application Server will satisfy the needs for which it was purchased exactly as it is installed. However, PATROL for WebSphere Application Server has the flexibility to be adapted to a wide variety of IBM WebSphere Application Server configurations. This chapter helps you decide whether tuning is likely an issue at your site. It also contains information that is valuable to keep in mind at any site. Whether or not tuning is necessary is often directly correlated to the size and complexity of a sites IBM WebSphere Application Server environment. For a smaller site with a relatively small number of defined objects, PATROL for WebSphere Application Server is likely to fit a companys needs completely, just as it is installed. The larger the site grows and the more complex The following matrix provides some guidance about whether to think of your site as small, medium, or large. There is no hard and fast rule about who will need to do extra tuningthis information is provided simply to help anticipate the probability of whether tuning might be in order at your site. Table 9 Site Size Small Medium Large Tuning Site/Size Matrix Data Sources 14 58 >8 EJBs <20 20 50 >50 JSPs/ Servlets <100 100 300 >300
Generally, the larger the site, the more likely that specific tuning would be a performance advantage.
Monitoring Application Servers Only as Needed

As you consider your use of the PATROL for WebSphere Application Server product, one of the first things BMC Software suggests is that you consider which of your application servers need to be monitored. If you have 40 application servers in your IBM WebSphere Application Server environment, but you really need to monitor only 7 of them, you use only a fraction of the resources it would take to monitor all 40.
134
Limiting the Number of Available Parameters
This is also a question that would be worth keeping open over time. As problems arise in the performance of an application server, you might want to add it to the list of monitored application servers. Likewise, as a non production application server demonstrates over time that it is stable and efficient in its responses, assigning it a monitoring status of Do Not Monitor will save the resources your system is taking to monitor and display information. For a reminder about how to change the monitoring mode for discovered application servers, see Setting the Monitoring Mode of Application Servers on page 103.

In versions of PATROL for WebSphere Application Server earlier than 2.1.00, most of the parameters available with the product were active by default. Starting with release 2.1.00, the default for nearly all parameters other than collectors is to be inactive. To review how to make specific parameters available for display, see Setting Specific Monitoring Options for Application Servers on page 105. In general, the fewer parameters you have displayed, the fewer resources are needed to display them and populate their values. The three parameters of the EJB_METHOD application class require a performance data monitoring level of MAXIMUM and are an exception to this generality. One way of considering which of the parameters you want to make available is to review the purpose of each parameter and determine whether you really need that information. Parameters Affected by IBM Performance Data Monitoring Levels on page 135 and Parameters Affected by Profiling and Instrumentation Overhead on page 137 list which of the KM application classes is associated with each monitoring service you can select for activation, explained in Setting Specific Monitoring Options for Application Servers on page 105. The page numbers in the tables identify the page in Appendix B, Parameter Referenceon which you can find documentation about parameters of the application class.
Parameters Affected by IBM Performance Data Monitoring Levels

Most of the parameters referred to in Table 10 are directly associated with IBM WebSphere Application Server performance data monitoring levels, populated with data collected by the PerfCollector2 parameter. Collectors, parameters showing resource availability, and log monitoring parameters are not populated by PerfCollector2.
Chapter 5 Tuning the KM 135
Table 10 Service
Parameters Affected by WAS Performance Data Levels (Part 1 of 2) KM App Classes PMW_APPSERVER PMW_SERVER_RESOURCES (only those populated by the PerfCollector2 parameter) PMW_DATASOURCE PMW_DBPOOL_SUMMARY PMW_BEANS PMW_EJB_SUMMARY PMW_EJB_TRANSACTIONS PMW_SERVLET PMW_SERVLET_SUMMARY PMW_SESSIONS PMW_EJB_METHODS PMW_LOG PMW_CACHE_SUMMARY PMW_CACHE_TEMPLATE PMW_ORB_SUMMARY PMW_ORB_INTERCEPTOR PMW_THREADPOOL_ SUMMARY PMW_THREADPOOL PMW_J2C_SUMMARY PMW_J2C_FACTORY PMW_WLM PMW_WLM_SUMMARY PMW_WEBSERVICE PMW_ALARM_MANAGER PMW_ALARM_SUMMARY PMW_DCS PMW_DCS_SUMMARY PMW_HA_MANAGER PMW_HA_SUMMARY Appendix Page page 248 page 331
Availability of WebSphere Components Basic Application Server Runtime Resources
Database Connection Pools Enterprise Java Beans EJB Container Transactions Servlets and JSPs Servlet Sessions EJB Method Performance Log Monitor Dynamic Cache Object Request Broker (ORB) pools Thread Pools
page 274 page 279 page 249 page 293 page 302 page 338 page 343 page 345 page 292 page 321 page 259 page 266 page 325 page 325 page 363 page 361 page 315 page 311 page 373 page 378 page 365 page 246 page 247 page 286 page 289 page 308 page 309
Java 2 Connector Workload Manager Web Services Alarm Manager Distribution and Consistency Services High Availability Manager
PMW_WEBSERVICE_ SUMMARY page 369
136
Table 10 Service
Parameters Affected by WAS Performance Data Levels (Part 2 of 2) KM App Classes PMW_J2EE_OBJ PMW_OBJECT_POOL PMW_OBJECT_SUMMARY PMW_SCHEDULER PMW_SCHEDULER_SUMMARY PMW_SIB_SERVICE PMW_SIB_SUMMARY Appendix Page page 318 page 323 page 324 page 328 page 329 page 351 page 355
J2EE Enterprise Applications and Transactions Object Pools Scheduler Service Integration Bus
NOTE
The performance data monitoring level required for parameters depends on the underlying IBM functionality. More information about PMI performance levels and the WebSphere Performance Viewer tool is available from IBM at the IBM WebSphere InfoCenter (http://www-306.ibm.com/software/webservers/appserv/infocenter.html). EJB method performance requires the highest performance setting (Maximum in WebSphere 5 or All in WebSphere 6).
Parameters Affected by Profiling and Instrumentation Overhead

The parameters referred to on Table 11 are all associated with JVM profiling or J2EE bytecode instrumentation. All profiling and instrumentation involves resource overhead that ranges from a minimal amount to substantial overhead, therefore, it should only be part of a development or test environment. Table 11 Service Profiling Comprehensive Application Server Runtime Resources Instrumentation SQL Performance PMW_DBURLS PMW_DBURL PMW_SQL page 286 page 284 page 360 PMW_SERVER_RESOURCES (only those populated by the JVMCollector parameter) page 331 Parameters Affected by Profiling and Instrumentations KM App Classes Appendix Page
Chapter 5
Tuning the KM
137
Tuning Collection Intervals
Table 11 Service
Parameters Affected by Profiling and Instrumentations KM App Classes PMW_SERVLET_GROUP PMW_SERVLET_METHOD Appendix Page page 341 page 343
Web Applications Servlet Method Performance
Tuning Collection Intervals

For the majority of businesses using PATROL for WebSphere Application Server, the overhead resulting from default collection intervals is an acceptable cost for the benefits provided by associated consumer parameters and by the products reporting capabilities. Under certain circumstances, it might become useful to experiment a longer or shorter collection interval. This is possible especially at sites with a large number of applications running on one application server, with many application servers that need to be monitored, or with both.
NOTE
Graph data points might be delayed as a result of reduction in the resource consumption by the PATROL Agent.
BMC Software suggests, however, that collection intervals be changed only on the advice of experienced PATROL administrators who understand the implications of such changes or on the advice of BMC Software Support.
Limiting Log Monitoring Scan Patterns

The PATROL for WebSphere Application Server product always monitors certain log files (see Log Files Monitored on page 231 for a list of files that the KM scans). Simply monitoring the log files for size and growth involves little overhead and can yield useful information. The major overhead associated with log monitoring results from having to scan for particular patterns. By default, no scan patterns are defined for log monitoring. Adding scan patterns increases overhead, and that overhead grows geometrically as the number of scan patterns is increased.
138
Using Profiling and Instrumentation Judiciously
For this reason, one of the most effective ways of assuring efficient KM operation is to limit the number and complexity of text patterns for which the log files must be parsed as they are scanned. This is especially true of very large log files. See Chapter 12, Log File Monitoring, for more detailed information.
Using Profiling and Instrumentation Judiciously

NOTE
Because of the resources required for the Java Virtual Machine Profiling Interface (JVMPI), BMC Software strongly recommends that profiling be restricted to development and testing environments and not be enabled on production systems. This is especially relevant to Java method-level profiling. JVM profiling and J2EE bytecode instrumentation provide certain kinds of runtime information that cannot be provided in any other way. These tools can be especially valuable in the diagnosis and debugging of applications under development and in the evaluation of software being considered for deployment. The greatest single factor affecting the amount of resources required to support either profiling or instrumentation is the number of objects being monitored. If only a few methods are being invoked, the overhead from Java method profiling is not nearly as severe as if there are thousands or even millions of method invocations being profiled.
Using Blackouts Effectively

If an application server goes down because of a known or scheduled shutdown, the KM still recognizes the application server as being down. If an alarm is set for that circumstance, operations personnel could see the console alarm and incorrectly identify the situation as an application server failure. The blackout functionality gives a WebSphere administrator a means for avoiding the waste of resources and personnel time that a false alarm of this sort could occasion.
Chapter 5
Tuning the KM
139
Advanced Tuning for Large Sites
Blackout functionality should be use during a time when the WebSphere environment is expected to be unavailable or during a time when one or more application servers are known already to be down. Typically this kind of known unavailability occurs during a maintenance window when backups are being performed, when operating system maintenance requires a partial system shutdown, or when new deployments of WebSphere applications require a WebSphere to be unavailable. However, exercise care when you are using this feature. If the scheduled time is changed or eliminated, you must change the blackout schedule or remove the blackout from the KM. Otherwise, one of two outcomes could occur:
I
The server could go into blackout at the wrong time, and the KM could fail to detect a real problem. The server could be brought down for routine maintenance, and the KM could falsely report the event as a failure.
For more information about blackouts, please refer to the following other sections:
I I I
Scheduling Blackouts on page 112 Application Server Blackouts by Menu Command on page 168 Application Server Blackouts by Command Line Interface on page 170

For many companies, PATROL for WebSphere Application Server will satisfy needs completely with a default configuration. However, for sites that have especially large or complex WebSphere installations, PATROL for WebSphere Application Server includes control variables that can fine tune performance.
WARNING
Inappropriate or invalid values for configuration variables could result in unpredictable behavior and potentially serious damage to your environment. BMC Software recommends that the variables described in this section be adjusted only by advanced PATROL administrators. Questions about these variables should be directed to BMC Support.
NOTE
After altering the value of a Pconfig variable, select the WebSphere icon and choose the Refresh Discovery command to make the change effective. Variables affecting log file scans will take effect on the next subsequent collection cycle.
140
The following variables can be used to tune performance:

I I I I
/WEBSPHERE/expireInactivityCollCycles on page 141 /WEBSPHERE/LogReadDefer on page 141 /WEBSPHERE/logScanMaxSize on page 142 /WEBSPHERE/<application server>.monitorAppServerObjects on page 143
/WEBSPHERE/expireInactivityCollCycles
Purpose Specifies the number of collector cycles with no activity, after which number a persistent Java client is terminated. Default Value 3
Explanation: The expireInactivityCollCycles limits the number of successive, collections cycles during which a persistent Java client persists with no activity (by default 3). After a Java client has had no activity successively for the number of collection cycles specified, it is terminated. This variable is not applicable for WebSphere version 5.
/WEBSPHERE/LogReadDefer
Purpose Specifies whether to scan only a specified number of bytes during a collection cycle, and defer scanning the remainder of the file until the subsequent collection cycle(s). Possible values are Y or N. Default Value Y
Explanation: The /WEBSPHERE/LogReadDefer variable specifies whether to scan only a limited number of bytes during a collection cycle and defer scanning the remainder of the file until subsequent collection cycles, or to scan the entire log file. Valid values are Y for Yesdefer, and N for Nodo not defer, but scan the entire file. (The default value is Y). The parameter value also determines the type of text patterns for which the log file is to be scanned.
If Y is specified, in the first collection cycle the collector scans only n bytes of newly written log message, where n is the number of bytes specified by the /WEBSPHERE/LogScanMaxSize Pconfig variable. In each subsequent collection cycle, the collector begins scanning where it left off in the previous cycle, and scans n more bytes. Through all scans, the collector scans for all specified text messages, whether the messages are associated with INFORMATION events, WARNING events, or ALARM events.
Chapter 5
Tuning the KM
141
If N is specified, the collector scans all newly written log messages, but behaves in two ways. While scanning the first n bytes (also specified by /WEBSPHERE/LogScanMaxSize), the collector scans for all specified text messages. While scanning the remainder of the log messages, the collector scans only for specified text messages associated with an ALARM event. In that part of the scan, messages associated with the INFORMATION event or the WARNING event are ignored.
NOTE
Whether the value of this parameter is Y or N, the time required for a scan increases in proportion to the number of text strings specified. Injudiciously increasing the number of scan patterns can have a severe impact on a system with high volume log traffic. Effective with this release, the KM by default has no active scan patterns.
/WEBSPHERE/logScanMaxSize
Purpose Specifies the maximum number of bytes for the collector to scan, in conjunction with /WEBSPHERE/logReadDefer.
Explanation:
Default Value 100,000
If /WEBSPHERE/logReadDefer is set to Y, this variable specifies the maximum number of bytes in the log file that will be scanned during a collection cycle. If /WEBSPHERE/logReadDefer is set to N, this variable specifies the number of bytes in the log file that will be scanned for specified text messages associated with any event (INFORMATION, WARNING, or ALARM), after which the remainder of the file will be scanned only specified text messages associated with the ALARM event. The default value is 100,000 bytes.
142
/WEBSPHERE/<application server>.monitorAppServerObjects
Purpose Controls the monitoring of WebSphere objects Variables and Default Values
I I I I I I I I I I I I I I I I I I I I I I I I
Purpose (type of metrics)

I I I I I I I I I I I I I I I I I I I I I I I I
alarm=Y availStatus=Y cache=Y dbPools=Y dcs=Y ejbBean=Y ejbMethods=N ejbTrans=Y ham=Y j2c=Y jvmRuntime=Y logMonitor=Y objectPool=Y orb=Y scheduler=Y servletJsp=Y servletMethods=N sessions=Y sib=Y sqlPerf=N threadPools=Y webApp=N webService=Y wlm=Y
alarm manager performance availability status (up or down) dynamic cache performance database connection pool distribution and consistency service EJB performance metrics method-level servlet performance EJB transaction performance high availability manager J2C connection factory Java Virtual Machine runtime metrics log monitoring object pool performance object request broker performance scheduler service servlet and JSP performance method-level servlet performance session performance service integration bus performance SQL performance thread pool performance web application performance web services performance workload manager performance
Explanation:
This variable allows you to turn off generation of various types of performance metrics. This capability can save significant CPU if a summary is sufficient for your needs. Regardless of the settings, monitoring of these types of objects continues. Each variable can take a value of Y to generate and display the metrics, or N to suppress the metrics.
Chapter 5
Tuning the KM
143
144
Chapter
6
146 146 147 148 149
Working with Datasource Connections

6
This chapter provides the information to understand and work with the monitoring of datasource connections and includes the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Registering the WebSphere Data Source Connection Account . . . . . . . . . . . . . . Checking the JDBC Connection Directly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating DataSource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Controlling JDBC Connection Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
145
Overview
Overview
PATROL for WebSphere Application Server provides functionality to view information about JDBC connections to datasources and provides certain controls on how that information is collected. The tasks that follow provide the controls to manage how datasource connections are monitored:
I
on page 146 explains how to provide the KM with the username and password necessary so that you can use the other command options. on page 147 explains how to find out whether the JDBC connection is active when the connection state is not displayed on the console screen because the JDBCConnectState parameter is not active. on page 148 explains how to force the collection of information about the datasource connection and have centrally important characteristics of the connection displayed in a screen message. on page 149 explains how to deactivate the JDBCConnectState parameter to save the overhead associated with its collection function, and how to reactivate the parameter if the constant display of the connection state becomes worth the overhead.
Registering the WebSphere Data Source Connection Account

PATROL for WebSphere Application Server uses the WebSphere data source connection account to verify the availability of the JDBC connection. The location at which this account is created varies with database vendor. For example, DB2 uses an OS account but Oracle uses accounts internal to itself. To specify the location of the WebSphere data source accounts, do the following:
1 Expand the DB_POOLS application class.
2 Access one of the icons representing a data source.
146
Overview
3 Select the Setup DataSource Login KM command. The Data Source DB Account
Information dialog will be displayed.
4 In the User Name field, type in the name of the database connection account for
the data source. It is case sensitive for Unix, and may be case sensitive for NT.
5 In the Password field, type the password for the database connection account. The
password and its confirmation are case sensitive.
6 In the Confirm Password field, retype the password for the database connection
account for confirmation.
7 Click OK.
Checking the JDBC Connection Directly

If the JDBCConnectState parameter is not active, you cannot tell at a glance whether the JDBC connection itself is active. By using this task, you can find out the state of the JDBC connection without making the JDBCConnectState parameter active and incurring the associated collection overhead.
Chapter 6
147
Overview
1 To check the state of the JDBC connection directly, access the datasource icon, and
choose the Ping JDBC Connection command. One of the following will occur:
I
A message will indicate that the command is being processed, followed by another message indicating that the ping succeeded or that it failed. A message will indicate that the DB Login Account information is required.
2 Take further action based on the message that returned from the Ping command:
I
If the Ping succeeded, you know the connection is active. No further action is needed. If the Ping failed, the connection is not active. Take the appropriate action to restore the connection, based on the characteristics of the datasource you are using. If the message from step 1 indicated that DB Login Account information was required, then supply the required DB Login Account information as explained in Registering the WebSphere Data Source Connection Account on page 146. Then invoke the Ping JDBC Connection command again.
Updating DataSource Information

With this command, you can force an update of datasource information before the next collection cycle starts. Access the datasource icon and choose the Update DataSource Info command. A message will display to explain that the operation might take several minutes to complete. When the update operation has completed, the collection of information about the datasource will have been forced, and another message will display the current characteristics of the connection (on your console screen, you will see the implementation class name, driver jar file path, JNDI name, and database name and node):
148
Overview
Controlling JDBC Connection Monitoring

Using the two KM commands associated with datasources, you can specify whether the standard parameter JDBCConnectState is active for collection and display. Leaving it inactive can save some system resources and increase overall product performance levels. To stop collection activities for the JDBCConnectState parameter Access the icon of the datasource instance and choose the JDBC Connection Configuration => Stop JDBC Conn Monitoring command. At the start of the next collection cycle, the JDBCConnectState parameter will become inactive, and the state of the JDBC connection will no longer be displayed. To resume collection activities for the JDBCConnectState parameter Access the icon of the datasource instance and choose the JDBC Connection Configuration => Resume JDBC Conn Monitoring command. At the start of the next collection cycle, the JDBCConnectState parameter will become active, and the state of the JDBC connection will be displayed.
NOTE
The Stop JDBC Conn Monitoring command and Resume JDBC Conn Monitoring command affect only the JDBCConnectState parameter. Neither of these commands affects the PerfCollector2 parameter or any of the other parameters in the PMW_DATASOURCE application class that display information about the allocation and performance of datasource connection. (For details about the parameters in this application class, see on page 274.)
Chapter 6
149
Overview
You can ascertain the status of the JDBC connection from the JDBCConnectState parameter by invoking the Ping JDBC Connection as explained above in Checking the JDBC Connection Directly on page 147.
150
Chapter
Working with Application Servers and Server Resources

7
The PATROL for WebSphere Application Server provides a range of control and monitoring capabilities for managing application servers and the resources associated with them. The KM also can provide extensive information about EJBs and the ability to start and stop EJB containers. This chapter explains those capabilities in the following sections and tasks: Managing and Monitoring Cells, Nodes, and Servers in a Network Environment. Managing Mixed-Version WebSphere Environments . . . . . . . . . . . . . . . . . . . . . . Managing Cells and Deployment Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting and Stopping a Node Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting a Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server and Resource Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Application Server Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Application Server Information and Controls . . . . . . . . . . . . . . . . . . . . . . . Checking Manually for Application Server Availability. . . . . . . . . . . . . . . . . . . . Stopping an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring the HTTPTransport Connection State . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Monitoring of Application Servers and their Resources. . . . . . . . . . . . . . Enabling JVM Profiling on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Viewing Advanced JVM Runtime Resource Information . . . . . . . . . . . . . . . . . . . Generating an Application Server JVM Performance Report . . . . . . . . . . . . . . . . Configuring Java Classes for Method Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Method Profiling on Java Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Blackouts by Menu Command . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspending Monitoring for All Servers on a WebSphere Instance . . . . . . . . . . . Listing Blacked Out Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resuming Monitoring of Blacked Out Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Server Blackouts by Command Line Interface . . . . . . . . . . . . . . . . . . . . 152 153 153 154 154 155 155 155 156 156 156 157 158 158 162 163 165 167 168 169 169 170 170
151
Managing and Monitoring Cells, Nodes, and Servers in a Network Environment

PATROL for WebSphere Application Server provides a monitoring and management environment that mirrors the cell-based, network approach used in WebSphere 5.0 and later. In this type of environment, some product functions will apply to only certain configurations, depending on whether PATROL is monitoring a server on a local host or a remote host, whether the Deployment Manager is local or remote, and whether a Node Agent is present on the monitored server. Conceptual diagrams that show how components of a networked environment can be organized are provided in Chapter 1. See PATROL in a Cell-Based Management Environment on page 29. In the PATROL monitoring environment, a networked WebSphere environment might look like Figure 27. Figure 27 Desktop view of a monitored WebSphere network environment
top-level servers these can be a Deployment Manager, Node with or without a Node Agent, or an Application Server
NOTE
When monitoring remote servers, some features are not supported. The following are limitations of remote servers:
I I
No JVMPI (BMC profiling) Start commands for remote node agents or deployment managers are not supported Start command for remote app server is supported only for a Network Deployment environment, and a Node Agent must be running No log scanning (although RAS message reporting will provide some of the same functionality)
152
Managing Mixed-Version WebSphere Environments

You can use PATROL for WebSphere Application Server to monitor environments that include servers running both WebSphere 5 and WebSphere 6 (including standalone servers or cells). If you do so, BMC Software recommends using the WebSphere 6 installation to monitor and manage any mixed-version environments, and use a WebSphere 5 installation only when monitoring and managing environments that do not include WebSphere 6 servers. If you monitor a mixed-version environment from WebSphere 5, the jar file that handles WebSphere 6 PMI data will not be available and you will not have access to some performance data.
NOTE
The RMI protocol is not supported for mixed-version environments. Use the SOAP protocol if your environment includes servers running both WebSphere 5 and 6.
Managing Cells and Deployment Managers

A cell can comprise multiple nodes throughout a network with management concentrated in an Administrative console and a Deployment Manager. At the cell level, PATROL allows you to verify that a Deployment Manager is responding, view messages about the cell, or start and stop Deployment Managers.
To verify that the Deployment Manager is responding 1 Access the instance icon of the cell you want to check. 2 From the KM Commands menu choose Ping Deployment Manager.
A message dialog box will show you whether the Deployment Manager is running, and if so, its process ID (pid).
To stop the Deployment Manager 1 Access the instance icon of the cell on which you want to stop the Deployment
Manager.
2 From the KM Commands menu choose Stop Deployment Manager.
Chapter 7
153
To start the Deployment Manager 1 Access the instance icon of the cell on which you want to start the Deployment
Manager.
2 From the KM Commands menu choose Start Deployment Manager.
Starting and Stopping a Node Agent

This task explains how to start or stop a Node Agent on a node in a network environment.
To start a Node Agent 1 Access the instance icon of the node on which you want to start a Node Agent. 2 From the KM Commands menu choose Start Node Agent.
The Node Agent will be started if the node instance is a local node or a local Deployment Manager with a Node Agent running on the same host.
NOTE
A Node Agent cannot be started for a node with a remote Deployment Manager or a node on a remote server.
To stop a Node Agent 1 Access the instance icon of the node on which the Node Agent you want stopped is
running.
2 From the KM Commands menu choose Stop Node Agent.

The Node Agent will be stopped.
Starting a Deployment Manager

This task explains how to start a Deployment Manager on a cell in a network environment.
154
Application Server and Resource Monitoring
To start a Deployment Manager 1 Access the instance icon of the cell on which you want a local Deployment
Manager started.
2 From the KM Commands menu choose Start Deployment Manager.

The Deployment Manager will be started.
NOTE
A Deployment Manager cannot be started on a local node or remote server, nor can this command be used to start a Remote Deployment Manager.

Basic control of application servers and information about the resources they consume is an important feature of the PATROL for WebSphere Application Server product. Additional fine-grained information about application objects is provided through J2EE bytecode instrumentation.
Basic Application Server Resource Information

Information about server resources is available through the parameter selection process explained in Setting Specific Monitoring Options for Application Servers on page 105. Default parameters include Active Threads, FreeMemory, PercentMemoryUsed, ThreadPercentMaxed, ThreadPoolSize, and UsedMemory. For a full list of server resource parameters providing basic resource information, see PMW_SERVER_RESOURCES application class on page 331.
Basic Application Server Information and Controls

Although the only basic information available about application servers is provided by the AppServerAvailability parameter, some basic controls are available through menu commands for managing application servers. The task topics below explain how to use these controls.
Chapter 7
155
Checking Manually for Application Server Availability

Use this task to manually check the availability of the application server.
To check Application Server availability

Access the server instance icon (APPSERVER), and from the KM Commands menu choose Ping Application Server. A message is returned telling you whether the server is running or stopped.
Stopping an Application Server

This task explains how to stop a running application server through the use of KM commands.
To stop a server 1 Access the instance icon of the server you want to stop, and from the KM
Commands menu choose Stop Application Server.
2 Complete the KM security authorization dialog box (see KM Command Security

on page 131). When the operation has completed, a message is displayed. The format will vary, depending on the server type.
3 Click the Acknowledge button, and proceed with operations.

If the server was not running when you completed this task, a message box will indicate that the server was stopped, but will not indicate that the operation succeeded.
Starting an Application Server

Use this task to start an application server that has previously been stopped by use of the Stop Application Server command.
156
NOTE
Application servers can be started on remote nodes only if the Node Agent for that node is running. The Start Application Server command can not be issued for a remote server without an active Node Agent.
1 Access the instance icon of the stopped server that you want started, and from the
KM Commands menu choose Start Application Server.
2 When the message window is displayed, confirming that the application server is
started, click Acknowledge.
3 Proceed with other KM operations.
Monitoring the HTTPTransport Connection State

You can monitor the availability of the HTTP Transport connection using the HTTPTransportConnState parameter, which is inactive by default. To use this parameter, you must configure the connection information. You can configure multiple separate URIs for multiple ports on the server. Once configured, the parameter will alarm if any configured URI path fails.
1 Access the instance icon of the application server on which you want to monitor
the HTTP Transport connection.
2 From the KM Commands menu, choose Configure HTTPTranport Connection Info.

The Configure HTTP Transport Connection Info dialog is displayed.
3 Click the Activate button if you want to ping every default connection and create
the HTTPTransportConnState parameter.
4 Select an available transport connection. 5 In the URI Path field, type the URI address of the HTTP connection to be tested.
For example, /servlet/snoop or /snoop.
6 Click Update and then click OK. Repeat the process for any other ports for which
you want to configure a URI.
7 When you are finished, click Done, then click OK.
Chapter 7
157
Advanced Monitoring of Application Servers and their Resources

PATROL for WebSphere Application Server provides fine-grained information about Java Virtual Machine (JVM) configuration, resource usage, and performance. This information is provided through profiling components that can add substantial overhead when enabled.
NOTE
Use of JVMPI profiling has the potential to consume a tremendous amount of resources. For this reason, BMC Software strongly recommends that profiling be enabled only in test and development environments.
Enabling JVM Profiling on a Server

Some of the advanced method-level profiling features of PATROL for WebSphere Application Server can be used only if they are first enabled. This task explains the differences between Standard WebSphere Profiling and Advanced JVMPI Profiling, and explains how to enable the profiling features of PATROL for WebSphere Application Server.
NOTE
You need to restart the server after enabling JVM profiling on the monitored system.
Standard WebSphere vs. Advanced JVMPI Profiling

When you enable Standard WebSphere profiling, you are starting the JVM profiler that is provided by IBM as part of the WebSphere Application Server. When you enable Advanced JVMPI, you are starting the JVM profiler provided by BMC Software. The BMC profiler also captures information about garbage collection, lock activity, thread activity, object allocation, and Java method invocation. Both profilers capture information about various JVM metrics, including garbage collection, object allocation, locks, and threads, but the BMC profiler also captures method-level invocation data and provides memory usage information.
158
Table 12 shows which parameters are activated with each option. See Appendix B, Parameter Reference for complete parameter descriptions. Table 12 Parameters Activated When JVM Profiling Is Enabled Advanced JVMPI Parameters AllocatedHeaps CpuPercent CpuUtilization GarbageCollectionDuration GarbageCollectionObjectsInUsed GarbageCollections HighestCpuThread HeapsInUse PeakNTRealMemory PeakNTVirtualMemory VirtualMemory ActiveThreads
Standard WebSphere Parameters GarbageCollections GarbageCollectionRate GarbageCollectionInterval GarbageCollectionDuration LockWaits LockWaitRate LockWaitTime ObjectsAllocated ObjectsAllocatedRate ObjectsInUse ObjectsFreed ObjectsFreedRate ObjectsMoved ObjectsMovedRate ThreadCreates ThreadCreateRate ThreadDestroys ThreadDestroyRate Threads
To enable profiling 1 Load the PMW_JVM_PROFILER.kml file. 1 Access the instance icon of the application server on which you want profiling
enabled.
2 From the KM Commands menu, choose the Advanced Monitoring => Profiling =>
Set Profiling Level menu command.
The Set Profiling Level dialog (Figure 28) is displayed.
Chapter 7
159
Figure 28
Set Profiling Level dialog
3 Select the profiling level that you need. Unless you are an advanced user doing
testing on a limited basis, you probably want Standard WebSphere. This will enable the extended set of SERVER_RESOURCE parameters.
NOTE
Selecting Advanced JVMPI on the Set Profiling Level dialog does not, by default, enable collection of thread object data. Reports that contain thread information will always display 0 for HighestCpuThread and ThreadsObjects metrics unless thread collection is enabled.
4 Click Accept. NOTE

Restart the server after enabling JVM profiling.
Activating and Deactivating Collection of Thread Objects

Thread data collection has a high resource impact on system performance. The following section provides information about activating and deactivating thread object collection.
160
To activate collection of thread objects 1 In the Set Profiling dialog box, select Advanced JVMPI as the profiling level. 2 Restart the server. 3 From the KM Commands menu, choose Advanced Monitoring => Profiling =>
Activate JVM Thread Object Collection.
The updating object profiling dialog box is displayed. After the thread object collection is activated on the managed system, the message Setup succeeded is displayed in the dialog box.
NOTE
If the thread object collection fails, the message Setup Failed and the cause of the failure is displayed in the dialog box.
To deactivate thread object collection 1 Access the application server icon. 2 From the KM Commands menu, choose Advanced Monitoring => Profiling =>
Deactivate JVM Thread Object Collection.
After the thread object collection is deactivated from the managed system, the message Setup succeeded is displayed in the dialog box.
NOTE
If the thread object collection cannot be deactivated, the message Setup failed and the cause of the failure is displayed in the dialog box.
Where to Go From Here

You may want to verify your configuration settings for performance level data collection to ensure that you have activated everything that you want monitored. See Setting Specific Monitoring Options for Application Servers on page 105. When you are finished using the advanced monitoring features, you will want to remove them before monitoring a production environment. See Removing Previous Profiling and Instrumentation Libraries on page 63 and Deleting Profiling and Instrumentation Libraries on page 205.
Chapter 7
161
Viewing Advanced JVM Runtime Resource Information

Use parameters populated by the JVM Collector and the PMW_SERVER_RESOURCES InfoBox to see information about JVM memory use and memory management.
1 Access the SERVER_RESOURCES icon. TIP

If profiling is activated, after discovery has completed, you will see the AllocatedHeaps parameter, among others.
2 Check parameter values and adjust threshold and alarm values as needed for your
site: Table 13 JVM Memory Allocation and Management Parameters For Information about ... Check This Parameter Heap memory allocation and use Garbage collection AllocatedHeaps HeapsInUse GarbageCollectionDuration GarbageCollectionObjectsInUsed GarbageCollections CPU usage CpuUtilization CpuPercent HighestCpuThread Windows memory (applicable to Windows only) real memory threads using memory PeakNTRealMemory PeakNTVirtualMemory VirtualMemory HighestCpuThread ThreadsObjects Active Threads
3 For information about starting and ending times of the most recent garbage
collection, check the InfoBoxes associated with PMW_SERVER_RESOURCES:
I I
Last Garbage Collection Start Last Garbage Collection End
162
Generating an Application Server JVM Performance Report

This task explains how to generate a report that displays information about the performance of application resources in the JVM. An application server JVM performance report provides detailed information about resource and activities on the JVM. Using this report, you can identify problems that might lead you to further investigation, including Java class method profiling.
Before You Begin

Before you can complete this task, it is necessary to activate the service.
NOTE
JVM profiling uses the JVMPI, an industry-standard interface that inherently results in significant increases in server resource consumption, including both CPU cycles and memory. For this reason, BMC Software strongly recommends that JVM profiling be restricted to test and development application servers and NOT be activated in a production environment.
Generating the Report

1 Access the SERVER_RESOURCES icon. 2 Select the AppServer JVM Performance KM command.
A report window, part of which is illustrated in Figure 29, is displayed.
Chapter 7
163
Figure 29
Application Server Resource Report display
The report lists the date and time at which the information for the report was collected, and contains the additional following kinds of information: Table 14 Column Application Server Resource Report Information Explanation date and time at which the thread was started name of the JVM thread name of the thread group of which the JVM thread is member name of the parent thread from which the JVM thread was spawned thread ID of the OS thread that corresponds to the JVM thread thread ID of the JVM thread number of times the thread was loaded amount of CPU time in seconds that the JVM thread has used as of the report number of objects using the JVM thread amount of memory in KB being consumed by the objects using the JVM thread
Start Date and Time Thread Name Thread Group Thread Parent OS TId JVM TId Loaded CPU Time Obj-in-Use Memory Used (KB)
3 To refresh the information in the report A Select Refresh View at the top of the report B Click Take Selected Action
164
4 To print the report to the system output window, A Select Print to system output window at the top of the report B Click Take Selected Action 5 To close the report, click Exit.
Configuring Java Classes for Method Profiling

Use this procedure to start Java class method profiling, to modify the list of classes that are profiled, or to stop Java class method profiling. These actions require that profiling features are enabled on the server. See Enabling JVM Profiling on a Server on page 158.
WARNING
Java class method profiling is a dynamic operation. Each time you restart the application server, you must complete the procedure if you want to enable Java class method profiling. Consider that Java class method profiling typically uses more resources than any other KM operation. BMC Software suggests that you profile Java classes only in test and development environments. Additionally, method profiling can be configured only on cell, node, or server names that do not contain white spaces. Class method profiling is disabled for the core JRE classes, such as java.lang.String, javax.swing, and java.lang.System, for the purpose of improving resource usage when Advanced Profiling is activated.
1 Access the application server icon. 2 From the KM Commands menu, choose the Advanced Monitoring => Profiling =>
Configure Method Profiling Class.
A dialog box is displayed as illustrated in Figure 30 on page 166.
Chapter 7
165
Figure 30
Configure Java Class for Method Profiling Dialog Box
NOTE
The Configure Java Class for Method Profiling dialog box lists the classes automatically only if BCI is active. This feature is disabled by default to improve performance.
3 Take one of the following actions:

I
After an application server restart, if you are enabling Java class method profiling of classes that you have previously selected for profiling, skip to step 4. If you are starting Java class method profiling for the first time or modifying the list of classes, complete the following steps:
166
1. Using one of the two following actions, select a Java class for profiling: 1. Type the full name of the Java class in the input space marked Type Java class name. 2. Select one or more Java class names from the list of discovered Java classes. 2. Select the Add option toward the bottom of the dialog box. 3. Click OK. 4. Repeat step 3 until each class you want to have profiled is listed in the area marked List of typed or selected java class names for method profiling.
NOTE
If the area marked List of the selected java class names for method profiling is empty, method profiling events are disabled on the managed system.
4 Select Done. 5 Click OK. NOTE

If you click Exit, the dialog box closes without saving the changes that you have specified.
The Activating Method Profiling dialog box, which contains a list of classes for which method profiling has been activated, is displayed. This dialog box also lists the classes for which the activation of method profiling failed. An icon will be created for each of the methods that you have chosen for profiling.
Stopping Method Profiling on Java Classes

You can stop profiling for one or more Java classes whose methods have been profiled, or you can stop Java class method profiling entirely.
Chapter 7
167
Application Server Blackouts by Menu Command
To Stop Profiling Methods of Specific Java Classes 1 Access the application server icon. 2 From the KM Commands menu, choose the Advanced Monitoring => Profiling =>
Configure Method Profiling Class.
3 Select one or more Java classes that you no longer want to profile by clicking once
on each class in the area marked List of typed or selected java class names for method
profiling.
4 Select Delete. 5 Click OK.

The Configure Java Class for Method Profiling dialog box is again displayed.
6 Click Done. 7 Click OK.

The Activating Method Profiling dialog box, which contains a list of classes for which method profiling has been deactivated successfully, is displayed. This dialog box also lists the classes for which the deactivation failed.
To Stop Profiling Java Class Methods 1 Access the server instance icon. 2 From the KM Commands menu, choose Advanced Monitoring => Remove
Instrumentation and Profiling.

The blackout mechanism provides a way to suspend collection and display operations temporarily in PATROL for WebSphere Application Server without shutting the product down. This mechanism can be useful when it becomes necessary to shut down one or more application servers and when alarms and associated recovery mechanisms such as e-mails and pages are not needed.
168
Suspending Monitoring for All Servers on a WebSphere Instance on page 169 and Listing Blacked Out Objects on page 169, explain how to create an on-demand blackout by suspending collection and display for a specified application server or for all application servers in your environment. Blackouts can be initiated or terminated in two other waysscheduling in advance and initiating by command line invocation of a script. See Scheduling Blackouts on page 112 for information about scheduling blackouts in advance and Application Server Blackouts by Command Line Interface on page 170 for information about invoking custom scripts by command line directive.
Suspending Monitoring for All Servers on a WebSphere Instance

This task explains how to suspend monitoring of all application servers that appear in a WebSphere environment.
1 Access the WebSphere icon. 2 Choose the KM Command Blackout=>Suspend Monitoring.

At the next discovery cycle, monitoring of all application servers monitored under that PMW_MAIN instance ceases, and remains blacked out until the Blackout => Resume Monitoring command is invoked or until a scheduled blackout period expires.

When a blackout occurs, you can verify that the objects you specified for blackout are in fact blacked out. Listing Blacked Out Objects on page 169 explains how to perform this verification.
Listing Blacked Out Objects

This task explains how to verify quickly that the objects you intended to be suspended in a blackout are in fact suspended.
1 Access the top level WebSphere icon. 2 Choose the Blackout=>List Blackout Objects KM command.
Chapter 7
169
Application Server Blackouts by Command Line Interface
3 Scroll down the list of objects that have been blacked out and verify that all the
objects you expected to be suspended by the blackout are on the list.
Resuming Monitoring of Blacked Out Servers

This task explains how to stop a blackout period and resume monitoring the application servers that were suspended during the blackout.
1 Access the application class that corresponds to the application servers you want
to resume monitoring:
I
To resume monitoring all application servers in an environment, access the top-level WebSphere icon. To resume monitoring a specific application server, access its instance icon.
2 Choose the Blackout=>Resume monitoring KM command.

At the beginning of the next blackout collection cycle, collection and display will begin again for the application server or servers you accessed, according to the collection schedules in effect on the application servers involved.

Application servers can be blacked out according to a preset schedule (see Scheduling Blackouts on page 112) or by immediate menu command (see Application Server Blackouts by Menu Command on page 168). However, the most convenient, responsive, and consistent method of managing the suspension and resumption of monitoring activities is to use the PatrolCli tool, which is installed with each PATROL installation. This tool permits the user to send an event into PATROL that initiates an action in the KM.
170
To use the PatrolCli tool for suspending and resuming application servers, you must obtain the following information about the host on which PATROL for WebSphere Application Server is running and the connection:
I I I I I
username password host name port number transport protocol
Using this information, you can construct a script to perform the target action, then pipe the script into the PatrolCli tool by including a command line entry such as the following, where websphereSuspend.txt represents the file that triggers the desired blackout action (this command is most commonly submitted as part of an automated script): PatrolCli < websphereSuspend.txt Here are some samples you could modify for your environment to direct various blackout actions. In each of these samples,
I I I I
username = lpatrol password = secure host = websphere-hou-80 port = 3181 via TCP
To suspend monitoring for all monitored application servers

Create a text file with the following lines:
user lpatrol secure connect websphere-hou-80 3181 TCP event send PMW_BLACKOUT Blackout INFORMATION 3 <ALL>+SUSPEND
To resume monitoring all discovered application servers

user lpatrol secure connect websphere-hou-80 3181 TCP event send PMW_BLACKOUT Blackout INFORMATION 3 <ALL>+RESUME
Chapter 7
171
Managing JMS Servers
To suspend monitoring one server

user lpatrol secure connect websphere-hou-80 3181 TCP event send PMW_BLACKOUT Blackout INFORMATION 3 Cell1/websphere-hou-80/server1+SUSPEND
To suspend monitoring multiple servers

Create a text file with the following lines (distinguish servers to be suspended by separating server names with commas):
user lpatrol secure connect websphere-hou-80 3181 TCP event send PMW_BLACKOUT Blackout INFORMATION 3 Cell1/websphere-hou-80/server1,Cell1/websphere-hou-80/server2+SUSPEND
Managing JMS Servers

During the discovery process, PATROL for WebSphere Application Server will retrieve information about the JMS Server configuration for the cell or node and, if the JMS Server is configured, will check the state and set the availability parameter JMSServerAvailability (PMW_NODE). If the JMS Server is configured, menu commands will be available to verify the availability of the JMS Server (ping server), and to start or stop the JMS Server.
To stop a JMS Server 1 Right-click a node instance to access the menu commands. 2 From the KM Commands, choose Stop JMS Server.
The command is only available if a JMS Server is running on the node or cell.
To start a stopped JMS Server 1 Right-click a node instance to access the menu commands. 2 From the KM Commands, choose Start JMS Server.
172
Chapter
8
174 175 177 177 179 180 182 182 183 183 183 184 185 186
Working with Web Applications, Servlets, and EJBs

8
This chapter explains how to identify, monitor, and work with Web applications. The chapter contains the following sections: Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determining the Availability of Virtual Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . Instrumented Web Application and Servlet Performance. . . . . . . . . . . . . . . . . . . . . . Generating a Web Application Performance Report . . . . . . . . . . . . . . . . . . . . . . . Generating a Servlet Performance ReportAll Applications . . . . . . . . . . . . . . . Generating a Servlet Performance ReportSpecific Application . . . . . . . . . . . . Viewing Servlet Method Performance Information . . . . . . . . . . . . . . . . . . . . . . . . Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with EJBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EJB Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BEANS and EJB_SUMMARY Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EJB_TRANSACTION Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EJB Method Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generating a Performance Collector Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Working with Web Applications, Servlets, and EJBs
173
Web Applications
Web Applications
Icons for Web applications are created on the PATROL Console under the WEB_APPLICATIONS container (which is the PMW_SERVLET_ENGINE application class). Levels of containers below WEB_APPLICATIONS show web applications, groups of servlets, and then individual servlets. The organization Figure 31 Organization of web applications and servlets
PMW_SERVLET_ENGINE.km
PMW_SERVLET_CONTAINER.km
PMW_SERVLET_GROUP.km
PMW_SERVLET.km
In the PATROL for WebSphere Application Server environment, a Web application is represented by an instance of the SERVLET_CONTAINER application class. Each application is named according to the functionality provided by the servlets that the application contains. The name can be something simple such as Sales, or something more complex and abstract, such as ITSOAppServerWebApp. Each web application may contain servlets from several archive files (war). Each war file is represented in PATROL by an instance of the SERVLET_GROUP class, and each servlet in the group is represented by an instance of the SERVLET class. Parameters that can be made available for servlet monitoring provide information about the number and frequency of servlet requests, response time statistics, and servlet errors. Aggregate summary statistics are available in the SUMMARY class.
174
Web Applications
Determining the Availability of Virtual Hosts

Using this task, you configure one or more virtual host aliases and then use a ping command to determine whether the connection to the aliases is up or down. In addition, a parameter can be created that displays the ongoing status (on-line/off-line) of virtual host aliases you select.
NOTE
If an HTTP server is outside a firewall that disallows HTTP server requests across a standard port, Ping Virtual Host Aliases will fail to validate the status of that HTTP server.
To configure the virtual host alias

Before you can ping the virtual host, you must define one or more virtual host aliases.
1 Expand the application class representing the applications in your environment.

This class is labeled WEB_APPLICATIONS, and then expand the appropriate CONTAINER instance.
2 Select the Web application (SERVLET_GROUP) whose connections to the Virtual

Host Aliases (HTTP server connections) you want to ascertain.
3 Choose the Configure VHost Alias Ping List command. A dialog box like Figure 32
appears.
Chapter 8 Working with Web Applications, Servlets, and EJBs
175
Web Applications
Figure 32
Ping Virtual Host Aliases Dialog Box
4 Select one or more virtual host aliases to ping:

I
If the virtual host alias you want to ping is displayed by name, click once on the name to select that alias. To select a virtual host alias represented by and asterisk, type the name of the HTTP server you want to ping, followed by a colon and the correct port number, in the space marked HTTP Server Name. The input is case sensitive, and the spelling must be exact. You can type in multiple entries for the HTTP Server Name, so that connectivity to more than one HTTP server is verified with a single ping. Separate each HTTP server name a comma.
5 If you want the ping results to continue being collected and to be displayed
through a parameter, select the option labeled Configure ping results as
SelectedAliasesActive parameter.
176
Instrumented Web Application and Servlet Performance
6 If you also want to be warned by alarm when none of the of active virtual hosts
you selected for pinging remains active, also select Alarm when ports available
reaches zero.
NOTE
Select the option to be warned when no ports are available only if you also selected the option to have the SelectedAliasesActive parameter be generated.
7 When you have made your choices, click OK. To ping the virtual host alias 1 Expand the application class representing the applications in your environment.
This class is labeled WEB_APPLICATIONS, and then expand the CONTAINER instances to locate the specific application (SERVLET_GROUP) that you want to test.
2 Choose the Ping Virtual Host Aliases command.

You can generate reports that display statistics about the performance of Web applications and servlets, both on the WEB_APPLICATION and on the servlet group (Web application) level, as explained in the sections that follow.
Generating a Web Application Performance Report

Run a report to identify which web applications are used most often and have the longest response rates on your application servers. You can use this information to decide which web applications should be watched more closely, and you can identify servlets for deeper investigation.
To run the WebApp Performance report: 1 Access the WEB_APPLICATION menu. 2 From the KM Commands, choose WebApp Performance Report.
Chapter 8 Working with Web Applications, Servlets, and EJBs 177
The Configure dialog is displayed.
3 Select the checkbox for the criterion you want used to determine top Web
applications, then slide the control to indicate the number of results you want.
4 Click OK.
The report is displayed.
The report includes the following statistics that pertain to the Web application during the collection cycle:
I I I I I I I
total number calls to the same uri path average number of calls per second total cumulative response time over all calls average response time per call the name of the Web application the internal (uri) path to the servlets in the application the specific query (if there is one) for the request
178
Using the information from this report, you can start monitoring selected servlets, and can define alarm thresholds or alerts to be generated if performance degrades to unacceptable levels.
Generating a Servlet Performance ReportAll Applications

Run a report to identify which of all servlets running in monitored application servers are used most often and have the longest response rates on your application servers. You can use this information to decide which servlets should be selected for monitoring.
To run the Servlet Performance report: 1 Access the WEB_APPLICATIONS icon. 2 From the KM Commands, choose Servlet Performance Report.
3 Select the checkbox for the criterion you want used to determine top (worst
performing) servlets, then slide the control to indicate the number of results you want.
4 Click OK.
The report is displayed:
179
This report shows which servlets respond slowest or are most often called. The information is organized by Web application. Using the information from this report, you can select a web application on which to run a servlet performance report and focus on the performance of the servlets and JSPs that are specific to that Web application. Generating a Servlet Performance ReportSpecific Application on page 180 explains how this is done.
Generating a Servlet Performance ReportSpecific Application

Run a report to identify which servlets within an application are used most often and have the longest response rates on your application servers. You can use this information to decide which servlets should be selected for monitoring.
To run the Servlet Performance report: 1 Access the Web application instance icon (SERVLET_GROUP). 2 From the KM Commands, choose Servlet Performance Report.
180
3 Select the checkbox for the criterion you want used to determine top (worst
performing) servlets, then slide the control to indicate the number of results you want.
4 Click OK.
The report is displayed: Figure 33 Servlet Performance Report for Specific Web App
This report shows which servlets respond slowest or are most often called. Using the information from this report, you can start identify which servlets and JSPs you want to look at more closely, and can you can define alarm thresholds or alerts to be generated if performance degrades to unacceptable levels.
181
Sessions
Viewing Servlet Method Performance Information

Use this task to generate parameters that display statistics about performance of servlet methods, or to update servlet method performance parameters if they have been previously created but then disabled.
To create or enable servlet method parameters

Follow the procedure explained in Setting Specific Monitoring Options for Application Servers on page 105, and select Servlet Method Performance. If Servlet Method Performance has not be previously enabled, parameters will be generated and datapoints will be create at each collection cycle. If Servlet Method Performance has previously been enabled, creation of new datapoints will resume in parameters that already exist.
To disable servlet method parameters

Follow the procedure explained in on page 105, and deselect Servlet Method Performance. Parameters that have been created to display servlet method performance will remain, but no further data points will be created.
Sessions
The PATROL for WebSphere Application Server product provides a variety of information about servlet session creation, completion, availability, and activity during a collection cycle. You can choose to have any of this information at your disposal by activating the relevant parameters through the process explained in Setting Specific Monitoring Options for Application Servers on page 105. You can also review information about session parameters that can be made available. PMW_SESSIONS application class on page 345
182
Working with EJBs
The parameters you can choose to render active can supply you with the following kinds of information:
I
session creation number of sessions created rate at which sessions were created (creates per second) session availability and activity number of sessions live (available for use) number of session active (actually being used) session invalidation number of sessions invalidated rate of invalidation (invalidates per second) average time it took to invalidate a session number of sessions finalized average session lifetime
Working with EJBs

The PATROL for WebSphere Application Server product provides the means to start and stop EJB containers and to view a wide range of information about EJB operations in your IBM WebSphere Application Server environment. This section contains information about the KMs EJB capabilities.
EJB Management Commands

The PATROL for WebSphere Application Server product can display a great deal of information about the use of EJBs in an IBM WebSphere Application Server environment. The service also provides the capability to start and stop discovered EJB.
BEANS and EJB_SUMMARY Monitoring

Using PATROL for WebSphere Application Server you can view a variety of kinds of information about EJBs and EJB pools:
183
Working with EJBs
Status information during a collection interval:

number of beans that are active number of beans that are live (active or available to become active)
Bean operations during a collection interval:

number beans created create time beans destroyed beans instantiated beans activated beans passivated beans removed remove timE
EJB pool information during a collection interval:

bean pool size number of times a bean was found with the get method a bean was taken from the pool with the get method a bean was returned to the pool a bean was discarded after being returned to the pool number of times the bean pool was found idle, and an attempt was made to drain unneeded connections from the pool average number of objects drained in each drain operation
Bean method information during a collection interval:

number of active methods number of times any method was loaded number of method invocations rate of method invocation (calls per second) average method response time
EJB_TRANSACTION Monitoring
The PATROL for WebSphere Application Server product provides information about EJB transactions.
184
Working with EJBs
Parameters can be activated that display the following kinds of information for local transactions, as well as for global transactions:
I I I I I I I I I
duration before completion commit duration prepare duration transactions begun transactions committed transaction duration transactions involved transactions rolled back transactions timed out
In addition, a parameter displays information about the number of transaction optimizations.
EJB Method Monitoring

PATROL for WebSphere Application Server provides the capability to track EJB method activity, using basic services rather than JVM profiling or J2EE bytecode instrumentation, as are required for Java class method-level profiling or servlet method-level profiling.
NOTE
EJB method monitoring is the only service that requires a performance data level of MAXIMUM, and consumes the most resources of any basic monitoring service. BMC Software suggests that you activate EJB method monitoring only for the diagnosis and resolution of EJB method performance problems. Measurements that can be selected for monitoring EJB method execution include
I
the number of EJB method invocations during a collection cycle the rate at which EJB methods are invoked EJB method response time
To review the parameters involved, see PMW_EJB_METHOD application class on page 292.
185
Generating a Performance Collector Report
Generating a Performance Collector Report

Most of the application classes in PATROL for WebSphere Application Server contain a menu command to generate a Performance Collector Report. (See Appendix C on page 393). The generated report contains a snapshot of parameter information from the most recent collection cycle. It shows details about high, low, and recent parameter values, as well as sources from which the metrics were obtained or how they were calculated. The Timer Counter column is used only for timer type parameters: when it is populated, it shows the number of events over which the current value (total time) was accumulated, so that to generate an average value, the current value is divided by the timer counter. Running this command on a high-level object can produce too much information, but the command can be very useful when run at the servlet level or for a class like those monitoring the service integration bus (PMW_SIB_SERVICE), which contain many parameters.
To generate the performance collector report 1 Right-click the instance icon for the type of parameter data for which you want to
see detailed collection information.
2 From the KM Commands menu, choose Performance Collector Report.

The report is displayed in an output window.
186
Chapter
9
188 189 193 193 194
Application Performance and Transaction Monitoring

9
This chapter explains how to monitor and optimize J2EE application performance and to monitor transaction performance down to the component level. The chapter contains the following sections: Monitoring Transactions and Enterprise Web Applications . . . . . . . . . . . . . . . . . . . . Activating and Deactivating Transaction Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . Enabling ByteCode instrumentation with Java2 Security enabled . . . . . . . . . . . Adding and Removing Objects in the Monitoring Environment . . . . . . . . . . . . . . . . Thresholds and Performance Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
187
Monitoring Transactions and Enterprise Web Applications
Monitoring Transactions and Enterprise Web Applications

PATROL for WebSphere Application Server provides the ability to monitor transactions and application components on an enterprise-level, across a networked environment in which the application may use components running on multiple application servers of different types. Application components (such as servlets, SQL commands, or EJBs) are aggregated using the container classes J2EE_GROUP and J2EE_OBJ. Using the enterprise-wide, application-centric monitoring approach, you can define performance threshold levels for application components and you can monitor end-to-end response time of distributed applications, with response time information that spans across multiple servers in a WebSphere node, cell, or cluster. In the PATROL Console, these features will appear under the Application Performance icon, as shown in Figure 34. Figure 34 Application-centric monitoring
Transaction information is captured from one of two sources: IBMs Request Metrics (WebSphere 5.1.1 or higher recommended) which you activate from within the WebSphere administrative console, or from BMCs Bytecode Instrumentation, which you activate through the PATROL configuration dialogs, as explained in To activate transaction monitoring with BMC Bytecode Instrumentation on page 190. Although applications and objects are automatically discovered, you can add servlets, JSPs, or EJBs for monitoring, you can set threshold levels to reflect your own definitions of acceptable or problematic (long-running) transactions, you can customize the view to remove objects from monitoring, and you can produce reports to identify long-running transactions.
188
Activating and Deactivating Transaction Monitoring

PATROL for WebSphere Application Server can use transaction performance data from either of two sources: IBM Request Metrics, or BMC Software Bytecode Instrumentation (BCI). SQL response data will not be available if you use only IBM Request Metrics. If you want to use IBMs Request Metrics, activate the feature using the IBM WebSphere Administrative Console. You can activate the feature at different levels, and can filter details by J2EE object or incoming IP address. For best results, use WebSphere 5.1.1 when capturing data with Request Metrics. When PATROL for WebSphere Application Server uses IBMs Request Metrics, thresholds and transaction data will be contained in the ReqMetrics instance of the PMW_J2EE_OBJ class. There are several differences between using the IBM Request Metrics and using the BMC Bytecode Instrumentation. The parameters displayed with each option differ. Table 15 lists parameters for transaction monitoring and the source of metrics (see Appendix B for parameter details). The Request Metrics data cannot be broken down to the application level (use the WebSphere Administrative Console to set up filters and monitoring components). You can tune the threshold levels used by BMC Bytecode Instrumentation using the bcithresh configuration variable (see Appendix D). Table 15 Transaction Parametersa Parameters Under the ReqMetrics Icon, Generated by IBM Request Metrics TransactionLongCount TransactionMaximum TransactionReport
Parameters Under the Application Performance Icon Generated by BMC Bytecode Instrumentation SQLDeleteRespTime SQLDeleteReqRate SQLUpdateRespTime SQLUpdateReqRate SQLSelectRespTime SQLSelectReqRate SQLInsertRespTime SQLInsertReqRate TransactionLongCount TransactionMaximum
a
Generated by WebSphere PMI EJBResponseReport ServletResponseReport EJBResponseTime EJBRequestRate ServletResponseTime ServletRequestRate
Parameter data may be obtained from more than one source.
Chapter 9
189
You can use the following methods to activate transaction monitoring:

I
using the Activate ByteCode Instrumentation dialog box using the Performance Data Selection dialog box
To activate transaction monitoring with BMC Bytecode Instrumentation 1 Right-click the Application Performance icon to access the J2EE_GROUP menu. 2 From the KM Commands, choose Monitor Transactions => Activate.
A message dialog explains the difference between IBM Request Metrics and BMC Bytecode Instrumentation.
3 Click Accept.
The Activate Bytecode Instrumentation dialog box is displayed.
4 Select the All servers option if you want the settings to apply to all servers in the
environment, or select Selected servers only and choose the specific servers on which you want the settings applied.
5 (optional) Set a threshold value for filtering short transactions.

Although this step is optional, and you could set a very low threshold, a higher (and more reasonable) threshold will produce more relevant results and will improve your overall PATROL performance. The ByteCode Instrumentation (BCI) generates transaction data for transactions that exceed the specified threshold period.
6 Click Accept. 7 Click Yes on the Activate Bytecode Instrumentation confirmation message dialog
box. Activating bytecode instrumentation accomplishes the following tasks:
I
Installs BMCBCI Custom Service in WebSphere: This service dynamically controls bytecode instrumentation. Installation requires that either the Application Server be active or that, in the Network Deployment environment, the Deployment Manager and Node Agent are active. You will need to restart the Application Server.
190
Installs bytecode instrumentation files in PATROL: If the current version on a server is lower than the installed version, or if no current version of bytecode instrumentation is detected on the server, then files are moved from the PATROL_HOME directory to the Java environment under which the Application Server is running. If the server is remote to the PATROL Agent, additional commands are run on the remote host to install files in the correct directories. In some cases, you may need to stop Application Servers or other Java processes in order to replace files. Deployment takes effect when the Application Server is restarted. Activates dynamic controls: If the BMCBCI Custom Service and bytecode instrumentation files did not need to be installed, then the following dynamic controls are modified: InstrumentationEnabled is set to true MessageThreadElapsedFilter is set to the threshold value specified in the Activate Bytecode Instrumentation dialog. These controls do not require a server restart.
NOTE
If the managed system is a remote computer for the PATROL Agent, a jar file is created in the pmw_WebSphere directory that should be manually deployed on the remote computer. Perform the steps that appear in the GUI of the product when the target is a remote computer. If any of these installation steps fails, a message will be displayed and the activation will be re-attempted by the application server discovery process.
To activate transaction monitoring using the Performance Data Selection dialog box 1 Right-click the WebSphere Setup icon. 2 Choose the Customization=>Performance Data Selection command.
Transaction monitoring is activated because of the activation of the following categories:
I I I
SQL Performance Web Applications Servlet Method Performance
For more information, see Setting Specific Monitoring Options for Application Servers on page 105.
Chapter 9
191
To deactivate bytecode instrumentation 1 Right-click the Application Performance icon to access the J2EE_GROUP menu. 2 From the KM Commands, choose Monitor Transactions => Deactivate.
The Deactivate Bytecode Instrumentation dialog is displayed.
3 Click the button next to All servers if you want to deactivate BMC bytecode
instrumentation on all servers in the environment, or click Selected servers only and choose the specific servers on which you want to deactivate bytecode instrumentation.
4 Click Accept. 5 Click Yes on the Deactivate Bytecode Instrumentation confirmation message dialog
box. Deactivating bytecode instrumentation does not require a restart; it is done using dynamic controls. This process does not actually remove the BMCBCI Custom Service nor the installed Java files. See Deleting Profiling and Instrumentation Libraries on page 205.
NOTE
If the managed system is a remote computer for the PATROL Agent, perform the steps that appears in the GUI of the product to completely deactivate BCI.
192
Adding and Removing Objects in the Monitoring Environment
Enabling ByteCode instrumentation with Java2 Security enabled

If Java 2 security is enabled , BCI will not work correctly. In order to activate BCI, update the server.policy file to provide access to the BCI component.
To enable BCI with Java2 security 1 Locate the security policy file, which for WebSphere is typically
<WebSphere_Install_Directory>/properties/server.policy.
2 Add the following entries:

grant codeBase "file:${was.install.root}/java/jre/lib/ext/BMCJ2eeExt.jar" { //BMC BCI permissions permission java.security.AllPermission; }; grant codeBase "file:${was.install.root}/java/jre/lib/ext/BMCSvrExt.jar" { //BMC BCI permissions permission java.security.AllPermission; };
Adding and Removing Objects in the Monitoring Environment

You can add servlets, JSPs, or EJBs for monitoring, and you can stop monitoring any J2EE object that is discovered but that you do not want monitored.
To add a servlet or JSP for monitoring 1 Right-click the Application Performance icon to access the J2EE_GROUP menu. 2 From the KM Commands, choose Monitor Servlet/JSP.
The Select servlet/JSP for monitoring dialog appears.
3 Enter the application name, jar file, and servlet name if you want to specify the
information, or leave it blank and you can select from a list of discovered instances.
Chapter 9
193
Thresholds and Performance Reports
4 Set a threshold level and number of transactions. The threshold value should
reflect the maximum time (in milliseconds) that you consider to be reasonable performance in your environment. This threshold is also used when setting the value of the TransactionCount (J2EE_OBJ) parameter.
5 Click Accept. 6 If you left the top section of the previous screen blank, then a list of servlets will be
displayed. Click the servlet you want monitored then click Accept.
7 When you are prompted for a label, enter a unique name that is meaningful to you.
This will be used in PATROL as an instance name to identify the object.
To add an EJB for monitoring: 1 Right-click the Application Performance icon to access the J2EE_GROUP menu. 2 From the KM Commands, choose Monitor EJB. 3 Enter the requested information about the EJB you want monitored (this dialog is
almost identical to the one for selecting servlets or JSPs).
4 Set the threshold and number of transactions. The threshold should reflect
maximum acceptable completion times.
5 Click Accept. To stop monitoring any servlet, JSP, or EJB: 1 Right-click the instance icon of the object that you want to stop monitoring. This
will access the J2EE_OBJ menu.
2 From the KM Commands, choose Remove Monitoring. 3 On the confirmation dialog, click OK.

J2EE objects monitored by PATROL for WebSphere have a threshold level associated with them. This threshold level defines the maximum acceptable performance level. When the objects response time exceeds the threshold level that you define, it may trigger alarms and it will be included in performance reports that you view. You can also set the number of transactions that you want to see in generated reports.
194
To set a threshold level or number of transactions for reports 1 Right-click the instance icon of the object that you are monitoring. 2 From the KM Commands menu, choose Modify Monitoring.
The Modify Monitoring dialog box appears.
3 Enter the threshold level for identifying the longer running transactions on the
monitored system. The threshold value should reflect the maximum time (in milliseconds) that you consider to be reasonable performance in your environment. This filtering applies on data already delivered by the BCI from the monitored system.
4 Enter the number of long running transactions to be monitored for reporting

purposes.
5 To import the details of the monitored transactions automatically into PATROL,

select Collect transaction information automatically. If this option is selected, the PATROL Agent uses more system resources.
6 To track the SQL performance of applications running on the monitored system,

select Track SQL statement rate and response. This option will add parameters for each application in order to track the SQL performance.
NOTE
This feature is available for enterprise applications only and not for Servlets, JSP, EJB, and IBM ReqMetrics. The SQL tracking feature affects the performance of the PATROL Agent. Hence, BMC recommends the use of this feature only when needed.
7 Click Accept. To generate a performance report for an object: 1 Right-click the instance icon of the object that you are monitoring to access the
J2EE_OBJ menu.
2 From the KM Commands menu, choose View Transactions if you want to see a list
of those transactions that take the longest time to complete (includes the start and stop time stamps and the transactions details).
Chapter 9
195
A list of servers and high-level information is shown in a report output window.
Object details are shown in the report output window.
3 You can delve deeper into the performance information by choosing another object
and clicking Select. Multiple levels of reports can exist, depending on how deeply component object calls continue.
4 When you are done viewing transaction timing details, click Back until you reach
the server level, and then click Exit.
196
Chapter
10
Instrumenting and Profiling J2EE Components

10
This chapter explains how to use PATROL for WebSphere Application Server to monitor performance of Web applications and the application server JVM, of Web applications running on the application server, and of low-level objects, such as individual SQL statements, servlet methods, and Java class methods.
NOTE
The features described in this chapter become available only when JVM profiling and J2EE bytecode instrumentation are activated. (See Setting Specific Monitoring Options for Application Servers on page 105.) Instrumentation and Profiling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the SQL Performance Report on All DBURLs . . . . . . . . . . . . . . . . . . . . Running the SQL Performance Report to Monitor SQL Objects . . . . . . . . . . . . . Monitoring Individual SQL Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitoring Web Applications and Servlets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Profiling the Java Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting Profiling and Instrumentation Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 199 201 203 203 204 205
Instrumenting and Profiling J2EE Components
197
Instrumentation and Profiling
Instrumentation and Profiling

PATROL for WebSphere Application Server contains features that can let you discover detailed performance metrics and monitor your IBM WebSphere Application Server components to a very granular level. Using tools provided in the product, you can find which SQL statements and web application servlets are the most resource intensive in your environment, and you can monitor the performance of these components to proactively isolate potential service problems before they become noticeable to end users. You can also use these features together to characterize performance of J2EE components and to use this information to modify your Java code so as to optimize performance as you develop and roll out new web applications. To do this, you would iteratively use most of the instrumentation and method-level profiling features described or referenced in this chapter.
NOTE
When you activate BCI and restart the PATROL Agent, certain BCI parameters do not appear in the tree and some parameters cease the monitoring process until the monitored application becomes active again. Advanced profiling features are available in the product only after they are specifically enabled; to enable the features, see Enabling JVM Profiling on a Server on page 158. Some of the features described in this chapter may also be available only if enabled through selections you make as described in Setting Specific Monitoring Options for Application Servers on page 105.
Using Instrumentation to Identify and Monitor Most Critical SQL Objects

By using the instrumentation features of PATROL for WebSphere Application Server, you can generate a report showing which SQL objects are most expensive in your environment and you can monitor their performance. Once you know which SQL objects are most critical, and you identify their associated DBURLs, you can also make modifications to your PATROL for WebSphere Application Server configuration to optimize performance. For example, if you notice a pattern of slow performance from a particular DBURL, you may want to look at components that could affect its performance, such as the number of connections in its associated JDBC pool, and perhaps increase the maximum pool size to reduce the likelihood of waiters.
198
Running the SQL Performance Report on All DBURLs

Run a report to identify which SQL statements might present performance problems on your WebSphere application servers, and run a stack tracing report. You can use this information to decide which SQL objects should be watched more closely, and you can identify web applications, servlets, and methods that call your most used or most resource-intensive SQL. You can run the report for one specific database URL or for all database URLs on the server.
To run the SQL Performance Report: 1 Access the SQL_STATS icon: 2 From the KM Commands menu, choose SQL Performance Report.
The SQL Performance Report dialog is displayed.
3 Select the checkbox for the criterion you want used to determine top SQL, then
slide the control to indicate the number of results you want.
4 Click OK.
The report is displayed in a report dialog box.
Chapter 10 Instrumenting and Profiling J2EE Components
199
Figure 35
SQL Performance Report for All DBURLs
are response times too slow?
This report shows various kinds of information about the worst performing SQL statements:
I I I I I
Total number of invocations Rate of invocations Total cumulative response time Average response time Text identifying the SQL statement
Using information from the report, you can start monitoring selected SQL, and can define alarm thresholds or alerts to be generated if performance degrades to unacceptable levels. The most useful information is the SQL call tracing. This information shows what objects (web applications, servlets, methods, or EJBs) are calling the SQL (stack trace).
5 To get a stack tracing report, do the following: A Select an SQL statement by clicking once anywhere on the line. B Choose the Select SQL for Stacks Tracing option. C Click Take Selected Action.
A report dialog appears that traces the calling stack of the selected SQL statement:
200
Figure 36
SQL Statement Stack Trace
Information contains the calling sequence of an SQL statement executed from the web application to the JSP or servlet to EJB. While you may want to monitor the SQL itself, you may also want to look more closely at objects identified in the stack trace to determine how well they are performing, and possibly monitor them as well.

You can select SQL objects for monitoring (page 201), and you can further investigate and monitor methods and servlets related to your top SQL.
Running the SQL Performance Report to Monitor SQL Objects

See performance statistics about SQL statements in a single DBURL and monitor individual SQL statements you select. SQL objects are not monitored by default because there are far too many of them and the objects of critical importance are specific to your own environment. To determine which SQL statements you want to monitor, run the SQL Performance Report on a specific DBURL instance. Then, based on the displayed performance statistics, set up monitoring instances for the SQL statement or statements that seem to warrant individual observation.
To run the SQL performance report on a DBURL: 1 Access a DBURL instance icon. 2 From the KM Commands menu, choose SQL Performance Report.
201
The SQL Performance Report criteria dialog box appears,.
3 Click the box next to the criteria you want to use for determining top SQL, then
slide the bar to the number of responses you want.
4 Click OK.
The SQL Performance Report dialog appears Figure 37 SQL Performance Report for a Specific DBURL.
5 To monitor a specific SQL statement, do the following: A Select the SQL you want monitored from the list of SQL statements by clicking
once on the line containing information about the SQL statement.
B In the space labeled Label for Selected SQL Monitoring, type a label for the SQL
statement. This label is used to create an instance icon in the PATROL Console.
C Choose the Select SQL for Monitor option at the top of the dialog box. D Click Take Selected Action. E If desired, repeat step A through step D for each SQL statement you want to
monitor.
6 When you have completed all desired actions, click Exit.

You can now monitor your selected SQL and can set alarm thresholds if you wish to be alerted to significant performance changes in this SQL. Monitoring Individual SQL Statements on page 203
202
Monitoring Web Applications and Servlets
Monitoring Individual SQL Statements

For individual SQL statements selected for monitoring, view the full SQL name, and stop monitoring the SQL statement. You can also adjust alarm ranges as with other PATROL parameters.
To view the full SQL name: 1 Access the icon for an SQL statement icon. 2 Access the View SQL Name command.
The text of the full SQL statement is displayed on a text box.
3 Click Acknowledge. To stop monitoring an SQL statement 1 Access the icon for an SQL statement icon. 2 Access the Stop Monitoring command.
The instance icon for the SQL statement is deleted.
Monitoring Web Applications and Servlets

Using J2EE bytecode instrumentation technology provided with PATROL for WebSphere Application Server, you can run reports on the performance of Web applications and on servlets. Information about generating and using these reports is available at the following locations: For Information About ... generating Web application reports generate a report about servlets in all monitored Web applications in which instrumentation is enabled Refer to .... Generating a Web Application Performance Report on page 177 Generating a Servlet Performance ReportAll Applications on page 179
203
Profiling the Java Virtual Machine
For Information About ... generate a report about servlets in a specific monitored Web application in which instrumentation is enabled generate or update parameters that display information about servlet method performance
Refer to .... Generating a Servlet Performance ReportSpecific Application on page 180 Viewing Servlet Method Performance Information on page 182

The PMW_SERVER_RESOURCES and PMW_APPSERVER application classes provide ways for system administrators to look inside the Java Virtual Machine to see how system resources are being used. Parameters and reports provide various statistics on memory usage, CPU usage, and processes and threads, as well as timing details on garbage collection cycles.
NOTE
Occasionally, reports and parameters provide information about the same types of JVM resources, but may sometimes reflect different values for similar parameters because of differences in the collector polling cycles. Because the profiling information that the KM provides is tied directly to the performance of JVM resources within a specific application server, that information is contained in the chapter dealing with those resources. To view all information available through profiling, you may need to activate performance data categories, as explained in Setting Specific Monitoring Options for Application Servers on page 105. Please see the following topics for more information: For Information About ... Refer to ....
use of JVM memory, CPU, garbage collection, Viewing Advanced JVM Runtime Resource and thread resources Information on page 162 performance specifically of JVM threads profiling Java class methods Generating an Application Server JVM Performance Report on page 163 Configuring Java Classes for Method Profiling on page 165
204
Deleting Profiling and Instrumentation Libraries

This task explains how manually to clear JVM profiling and J2EE bytecode instrumentation code from an application servers startup libraries. When any service is activated in the last section of the Performance Data Selection dialog box, the KM inserts three libraries into the application server startup process. (See Setting Specific Monitoring Options for Application Servers on page 105 for details about activating instrumentation and profiling services.) If it becomes necessary to remove the profiling and instrumentation libraries, you can use the following steps to accomplish that:
1 Deselect all advanced monitoring anywhere you have enabled it in your

monitored environment:
A For each application server on which profiling, instrumentation, or both have

been activated, access the Performance Data Selection dialog box as explained in Setting Specific Monitoring Options for Application Servers on page 105.
B Ensure that the following services within the last two sections of the Performance
Data Selection dialog box are deselected:
I I I
SQL Performance Web Applications Servlet Method Performance
C Complete the performance selection process and click Yes on the confirmation
dialog box to commit the choices.
D Set the profiling level to None. See To enable profiling on page 159 for more
information about profiling levels.
E Ensure that the transaction monitoring feature is deactivated. (See

To deactivate bytecode instrumentation on page 192 for information about deactivating transaction monitoring.)
WARNING
If the transaction monitoring feature is not deactivated, the BCI files are redeployed when the PATROL Agent is restarted.
2 Stop each of the application servers on which profiling or instrumentation has

been activated.
3 Invoke the clearing of the profiling and instrumentation code:
205
A Access the icon of an application server on which profiling or instrumentation

has been activated.
B From the KM Commands menu, choose Advanced Monitoring => Remove

Instrumentation and Profiling.
C Select the Remove J2EE Bytecode Instrumentation and Profiling from JRE option. D Click Accept. E Repeat steps A through D for each of the remaining application servers on
which profiling or instrumentation has been activated.
NOTE
Although a message is displayed indicating that the command succeeded, the removal of the libraries in the WebSphere JRE is a Java process is only scheduled, not actually accomplished.
4 Terminate all Java processes that reference the WebSphere JRE.

I
If possible, locate and terminate each process that references the WebSphere JRE. If you cannot identify which JRE a running process, it might be necessary to terminate all running Java processes.
WARNING
Some Unix systems allow files to be deleted even if they are still being referenced, but doing so could produce unexpected results. Window NT and Windows 2000 require that files no longer be in use before they can be deleted.
5 Verify that the following files are cleared from the WebSphere JRE:
206
Table 16 Profiling and Instrumentation Files Operating System Path All OSs WAS_HOME/java/jre/lib/ext/ WAS_HOME/java/jre/lib/patrol/bin/
File BMCJ2eeExt.jar BMCSvrExt.jar BMCJ2eeCP.jar BMCJ2eeExt.jar BMCJ2eeRef.jar BMCJ2eeCtrl.jar
WAS_HOME/java/jre/lib/patrol/server/ <server instance name> Windows 2000 or Windows NT Server AIX or Linux Solaris HP-UX %JAVA_HOME%\jre\bin $JAVA_HOME/jre/bin $JAVA_HOME/jre/lib/sparc $JAVA_HOME/jre/lib/PA_RISC2.0
BMCJ2eeCP.jar BMCJ2eeRef.jar BMCJ2eeSvrExt.jar BMCProfiler.dll libBMCProfiler.so libBMCProfiler.sl
NOTE
The BMCProfiler.dll, libBMCProfiler.so, and libBMCProfiler.sl files exist only after the activation of JVMPI. These files do not appear if only BCI is activated. The jar files in the WAS_HOME/java/jre/lib/patrol directory do not affect WebSphere. These files are created during the deployment of profiling or BCI . These files are used as backup for easier deployment of files upon re-activation of profiling or BCI.
6 If any of the files still exist in the location identified in Table 16, delete the file or
files manually. If you get an error and cannot delete a file, it is probably still being referenced by a Java process. Terminate the process and try deleting again until all of the files identified in the table have been deleted.
7 Remove the BMCBCI custom service from the WebSphere administrative console.
207
208
Chapter
11
210 210 211 211 212 213 217 218 220 220 221 221 223 224
Managing JMX-Instrumented Applications

11
This chapter explains how to effectively monitor and manage applications that are instrumented with Java Management Extensions (JMX). The following topics are discussed: Monitoring JMX MBeans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Instrumenting Your Application with JMX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The KM MBean Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activating JMX Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Default E-mail Address for Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding Automatic Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding E-mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting JMX files from Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Advanced Features for JMX Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually Registering an MBean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Conditions for an Unregistered MBean. . . . . . . . . . . . . . . . . . . . . . . . . . Setting JMX Debug Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Understanding Condition Settings and the ConditionDef Configuration Variable
209
Monitoring JMX MBeans

PATROL for WebSphere Application Server provides tools that let you monitor Java MBeans used in a JMX-managed IBM WebSphere Application Server. You can select which MBeans you want to monitor and you can define attributes that determine which MBeans are monitored, that trigger automatic alerts, and that can take automatic actions based on your monitoring criteria. In any IBM WebSphere Application Server environment, thousands of MBeans may exist, and any of them could be monitored by this product, but in most environments, only a small number of those MBeans will be important for monitoring purposes. To effectively use this product, you will need to set up some configuration options and to identify those MBeans that you want monitored. PATROL calls this process of identifying and specifying MBeans for monitoring as defining a condition. After a condition is defined, you can implement automatic recovery actions that will take place whenever a condition occurs. Each condition can also automatically send e-mail notifications and can generate PATROL events that you can monitor with the PATROL Event Manager or other tools. The following diagram shows the sequence of steps for successfully implementing JMX MBean monitoring in a typical IBM WebSphere Application Server environment. Additional information is in the online Help.
setup default e-mail notification define conditions add automatic actions add e-mail notifications
Instrumenting Your Application with JMX

JMX is a universal open technology for management and monitoring of Java applications and systems. Information about the JMX specification, including how to instrument your application with JMX, is at http://java.sun.com/products/JavaManagement.
210
The KM MBean Interface

Using PATROL for WebSphere Application Server to manage IBM WebSphere Application Server version 5.0 or later, you can view MBeans with their components, set MBean attribute values, invoke MBean operations, and monitor MBean attributes and notifications. These capabilities are available from the instance icon for the JMX_SERVER class (the icon labeled MBEANS) or from instances of JMX_DOMAIN that appear under the server instance. The WebSphere domain is recognized as being provided and controlled by IBM for the purpose of managing IBM WebSphere Application Server. For MBeans in this domain, you will not be able to change attribute values or invoke operations. You will, however, be able to view MBeans, attributes, operations, notifications, and constructors, and you will be able to monitor attributes and notifications for these MBeans. You can begin the process of using this technology by activating JMX management, as explained below.
Activating JMX Management

JMX management is optional and requires that a custom service called BMCJMX vrmmnn, where vrmmnn identifies the version of the JMX component of PATROL for WebSphere, be installed on your WebSphere servers. Follow the steps in this task to activate JMX Management.
1 If Java 2 security is enabled, update the server.policy file to provide access to the
JMX component, as described in online help for message BMCJMX533E.
A Locate the security policy file, which for WebSphere is typically

<WebSphere_Install_Directory>/properties/server.policy.
B Add the following entry:

grant codeBase "file:${was.install.root}/BMCSoftware/-" { //BMC JMX permissions permission java.security.AllPermission; };
211
NOTE
On WebSphere 6.x, the ${was.install.root} parameter should be replaced with ${user.install.root}. An example of the grant command is given in the server_bmc.policy file, which is deployed to the WAS_HOME/properties directory after JMX is deployed.
2 Access the WebSphere setup icon. 3 From the KM commands menu, choose JMX=> Activate JMX Management.
An output window displays the results of JMX activation.
4 In certain cases, you would be prompted to copy the bmc-jmxbundle<version>.jar

from $PATROL_HOME/JMX/ to $WAS_HOME/config/temp.
5 Restart each server for which either of the following is true:

I I
you updated the application servers server.policy file as described in step 1 the output window displaying JMX activation results directs that the server be restarted
6 Restart the PATROL Agent and the deployment manager.
Setting Default E-mail Address for Notifications

Perform these steps to define one or more default e-mail addresses that will receive notifications whenever a defined condition is met. The default e-mail addresses can receive notifications for all defined conditions. Individual conditions can also have additional e-mail notifications (see Adding E-mail Notifications on page 218).
To set a default e-mail address for notifications: 1 Access the WebSphere Setup icon. 2 From the KM Commands menu, choose JMX => Setup E-mail.
The Setup e-mail dialog box appears.
3 Enter the requested configuration information, described in Table 17.
212
Table 17 Setup e-mail dialog box Field Name Action SMTP e-mail server Internet address of e-mail sender JMX recipients Location of JavaMail classes type the name of your e-mail server, for example, mail.mycompany.com type the name of the account from which notification e-mail will be sent, for example, patrol@myhost.com type the e-mail address(es) that are to receive notifications whenever a condition occurs; separate multiple addresses with semicolons type the full directory path and file name to the .jar file that contains the JavaMail classes. This field is optional, and generally IBM WebSphere Application Server requires no value.
4 Click OK.

Define the criteria for monitoring JMX MBeans. See Defining Conditions on page 213.
Defining Conditions
Perform these steps to define conditions for monitoring JMX MBeans. When you define conditions, you establish the criteria for PATROL to monitor one or more MBeans, create icons in the console, and establish thresholds that will be used to set the status of the instance, execute actions in the JMX server, generate PATROL events, and generate e-mail notifications.
To define conditions: 1 Right-click a JMX server icon or a

JMX domain icon under which the MBean is registered.
2 From the KM Commands menu, choose Manage MBeans => All MBeans to bring up
a list of all MBeans in the server or domain, or Manage MBeans => Select MBeans to select a subset of MBeans based on object name. Using Select MBeans will make it easier to locate the MBean you are interested in when performing the next step.
213
The MBean Management dialog box is displayed.

click Manage MBeans
click an MBean to select, click again to deselect
click Select when finished, or click Exit to cancel all changes
3 Click on an MBean to select it. Optionally, you can filter the list of MBeans by
completing the fields shown in Table 18. For example, if you wanted to find all MBeans whose type is not Runtime or Config, you would:
I I I
enter the word Type in the Attribute field use the pull-down list to select does not end with enter the string &Config;Runtime in the Value field
214
Table 18 MBean Management dialog box Field Name Action Domain enter a pattern to match for the domain portion of the object name; the domain name can include the ? character to match any single character, or the * character to match 0 or more characters enter a pattern to match for the key property list portion of the object name; a key property list consists of one or more property-value pairs in the form property=value; the * character can be used to match one or more key properties, for example, *,Type=WebModule this can be an explicit list without wildcards; wildcards cannot be embedded within property names or values Attribute (optionally) enter the name of a numeric or string MBean attribute that will be used to filter the MBean list, based on a conditional expression; this is used in conjunction with the Value field; leave these fields blank if you do not want to filter the list (optionally) specify a numeric or string value that will be used to filter the MBean list; you may specify multiple criteria (separated with a semicolon) and you may precede the values with boolean operators & (and) and | (or) to specify complex criteria
Keys
Value
4 Click Select. The MBean Information dialog box is displayed. 5 Specify the target attribute or exception on which the condition will be based: A Click a numeric, string, or boolean attribute in the top pane, or a notification in
the third pane.
B Click the Define Conditions button. C Click Select. (If you clicked on a condition in the third pane, you will be
prompted for a notification type.)
215
The Define Conditions dialog box is displayed. The contents of this dialog vary depending on the type of data contained in the object (string, boolean, numeric).
set scope to Servers managed by this PATROL agent if you plan to export the definition
6 Complete the condition definition: A Type a name for the condition. This name will be used as an instance name for
icons created in the PATROL Console, and it will be used to refer to this condition if you need to perform future updates.
B You can change the object name to monitor a different object, or you can
optionally use wildcard characters (? or *) to monitor multiple MBeans for the same condition.
216
C If you wish to apply this definition to other servers and PATROL Agents, set
Scope of definition to servers managed by this PATROL agent. (See below.)
D Complete the remaining fields, which vary depending on the type of element
you selected. Click the Help button at the bottom of the dialog for information about the fields on this dialog.
7 Click OK.
Defining conditions that apply to multiple servers

When you define a condition, you can specify that it apply to all servers managed by the PATROL Agent by setting the Scope of Definition. If you do so, you can also use the PATROL Configuration Manager to copy the key /JMX/ConditionDef/ALLSERVERS to other PATROL agents. If you copy a condition definition to all servers across all agents, monitoring will occur only for servers on which the target MBean exists. You can limit instance creation to applicable servers by setting the Create PATROL object field in the condition definition to a value other than Always.

You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page 217. You can change the list of recipients to be notified whenever a condition is met. See Adding E-mail Notifications on page 218.
Adding Automatic Actions

Perform these steps to add or change automatic actions that occur when a defined condition is met. This process assumes that you have already defined conditions. See Defining Conditions on page 213. Automatic actions can be specified while you define a new condition, or you can define the condition, and then add the action later. Actions can include setting MBean attributes, invoking MBean operations, or generating PATROL events.
To add automatic actions to a defined condition: 1 Right-click the JMX server instance icon. 2 From the KM Commands menu, choose Define Condition.
217
The Defined Conditions dialog box appears.
3 Click the name of the condition to which you want to add notifications. 4 Click the Modify button. 5 Click Select.
The Define Condition dialog box appears.
automatic actions are set from this pane
6 In the list of actions, click the action you want to modify. 7 Click the Modify/Enable button to set an automatic action. If you want to remove
an automatic action, click the Disable button.
8 Click OK.
A series of dialog boxes will allow you to define how the automatic action is to take place. These dialog boxes vary considerably, depending on the type of data being used by your MBean. Click the Help buttons on each screen if you are unsure about how to use the dialog or what information is expected in the different fields.

You can change the list of recipients to be notified whenever a condition is met. See Adding E-mail Notifications on page 218.
Adding E-mail Notifications

You can add e-mail addresses for notifications to any defined condition. This process assumes that you have already defined conditions. See Defining Conditions on page 213.
218
To add automatic actions to a defined condition: 1 Right-click the JMX server instance icon. 2 From the KM Commands menu, choose Define Condition.
The Defined Conditions dialog box appears.
3 Click the name of the condition to which you want to add notifications. 4 Click the Modify button. 5 Click Select.
The Define Condition dialog box appears.
E-mail notifications are set from this pane
6 If you want the default e-mail address(es) to receive the notification, click the check
box. This can be either in addition to or in place of any other e-mail addresses you specify.
7 Type additional e-mail addresses in the specified field. Multiple addresses must be
separated by a semicolon.
8 Click OK.

You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page 217.
219
Advanced Features for JMX Monitoring
Deleting JMX files from Servers

Several JMX files are created while activating JMX management. These files are not needed when JMX management is not enabled for the application server. Perform the following steps to delete these JMX files.
To delete JMX files 1 In the WebSphere administrative console, verify that the custom service
BMCJMX<version> is not running on the application server.
2 Stop the application server. 3 Delete the $WAS_HOME/BMCSoftware directory. 4 Delete the file $WAS_HOME/config/temp/bmc-jmxbundle<version>.jar file. 5 Delete the $WAS_HOME/com/bmc directory. 6 Start the application server.

Several JMX features in PATROL for WebSphere Application Server are provided for advanced users or for troubleshooting purposes only. These features are unlikely to be needed for routine setup and monitoring. Advanced features include:
I
Manually registering an MBean. Typically, you will use your application to programmatically register MBeans that manage it. You may occasionally want to register an MBean for testing purposes. Defining conditions for MBeans that are not registered. This may be useful, for example, for defining conditions on MBeans that are in development or that support currently uninstalled applications. This requires a deep knowledge of the MBean and how it will be implemented. Setting debug flags. Debugging information is not generally useful except when troubleshooting specific problems.
220
Manually Registering an MBean

You can register and monitor any Java object that complies with JMX MBean specifications, including those that are not automatically registered as part of the applications they manage. Perform these steps to register an object.
NOTE
This process requires knowledge of object and class information. You do not need to use this process to monitor MBeans that are part of most Java applications because they are automatically registered for you.
To manually register an MBean: 1 Right-click a JMX server instance

icon (represented by the application name).
2 From the KM Commands menu, choose Register MBean.

The Create New MBean dialog appears.
3 Enter the required object and class information. Click the Help button if you need
more information.
4 Click OK.

You can define conditions to monitor your newly registered MBean. See Defining Conditions on page 213.
Defining Conditions for an Unregistered MBean

Perform these steps to define conditions for monitoring a JMX MBean that is not yet registered. This feature may be useful for web application developers who would like to roll out the ability to monitor MBeans before the managed applications are registered.
221
NOTE
This feature requires detailed information about object names and attributes. This capability is intended for advanced users. BMC Software does not recommend this process for most users. Instead, roll out the web application, register the MBeans, and follow the process described in Defining Conditions on page 213.
To define conditions for an MBean that is not registered: 1 Right-click a JMX server instance
icon (represented by the application name).
2 From the KM Commands menu, choose Define Conditions.

If at least one other condition is defined, the Defined Conditions dialog is displayed, otherwise, the Define Conditions dialog is displayed. If the Defined Conditions dialog is displayed, click the Add button, then click Select. This will display the Defined Conditions dialog.
3 Start defining the condition: A Type a name for the condition. This name will be used as an instance label on
the icon that appears in your console window. It will also be used to identify the condition if you make future updates.
B Type the object name. You can use wildcards (? or *) to specify multiple MBeans
to be monitored for the condition.
C Click a button to indicate the type of attribute (numeric, string, boolean). D Type the name of the notification or attribute on which the monitoring will be
based.
E Click Next.
The Define Condition dialog is displayed.
4 Complete the condition definition: A Change the condition name, object name, or element name, if desired. B Complete the remaining fields. These fields vary depending on the element type
you selected. Click the Help button if you need more information.
C Click OK.
222

You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page 217. You can change the list of recipients to be notified whenever a condition is met. See Adding E-mail Notifications on page 218.
Setting JMX Debug Flags

Although BMC Software makes every effort to ensure that products run reliably, problems do occasionally occur. BMC Software technical support staff sometimes ask customers to turn on debugging features if a problem source is difficult to pinpoint. Follow these steps to turn on or turn off debugging flags for the JMX component.
NOTE
The debugging feature is not intended for routine use. BMC Software recommends that it be turned on only under the direction of BMC support personnel.
To set debug flags: 1 Right-click the WebSphere Setup icon. 2 From the KM Commands menu, choose JMX => Set Debug Flags.
The JMX Debug Flag Settings dialog is displayed.
each line is a flag click to toggle on or off
file location to save debug data
223
Understanding Condition Settings and the ConditionDef Configuration Variable
3 Click a line to turn a flag on. Click it again to turn it off. NOTE
Usually, JMX_Debug will be the only flag you need to turn on. If you are generating debug information, set only JMX_Debug, unless you are specifically requested to provide another type of debug information.
4 Click the File button and enter a file name and directory path in which to save
debugging information.
5 Click Select.

JMX conditions are defined using dialogs (see Defining Conditions on page 213). When you create a condition definition, the attributes and values that you define are stored in a PATROL configuration (pconfig) variable that could be used with the PATROL Configuration Manager. The pconfig variable is: /JMX/ConditionDef/ALL^SERVERS/<ConditionName> or /JMX/ConditionDef/<ServerName>/<ConditionName>, depending on the scope of the definition. Figure 38 shows an example of creating a condition definition called ExtremeWeather. Table 19 explains the attributes comprising the ExtremeWeather ConditionDef variable.
224
Figure 38
Define Condition dialog for ExtremeTemperature
Each element on this dialog is an attribute stored in the ConditionDef variable
Table 19
Attributes of a JMX Condition Definition for ExtremeWeather (Part 1 of 3) Explanation

This is the name of the defined condition. This indicates where the definition applies: is set to either global (ALL^SERVERS) or local. This is an arbitrary ID number used to synchronize definitions between the PATROL Configuration and the live process. This indicates the type of condition definition. A value of 0 indicates that the condition definition is based on a JMX notification; 1 indicates that it is based on a numeric attribute; 2 indicates that it is based on a boolean attribute; and 3 indicates that it is based on a string attribute. This identifies the attribute or notification on which the condition is based. This identifies the MBean(s) for which the attribute or notification is being monitored. This controls when a PATROL object corresponding to the condition is created. A value of 0 indicates always; 1 indicates only if MBeans matching the defined pattern exist; 2 indicates only if alarms are issued and not relieved; and 3 applies to numeric attribute-based conditions only and indicates only if the numeric attribute value crosses a threshold.
Keyword and Value

name=ExtremeTemperature scope=global id=1045580897 type=1
element=LatestReportedValue objectname=Weather:* instantiation=2
225
Table 19
sendemail=

A list of email recipients delimited by semicolons. If the value LOCALONLY is included as an e-mail recipient, e-mail is not sent the the users on the JMX recipient list, as contained in PATROL configuration variable /JMX/EMailRecipients. Otherwise these users do receive an e-mail, in addition to any users identified in this field. The e-mail is sent whenever condition status changes. In order for email to work, PATROL configuration variables /JMX/SMTPServer must also be set. For attribute-based conditions, establishes how frequently (in seconds) the attribute value will be checked. For all condition types except numeric attribute-based, this controls the severity of the alarm condition. A value of 1 indicates a warning, 2 indicates a critical alarm. For a notification-based condition, this indicates how an alarm based on notification will be reset. A value of 0 indicates it can only be reset by console command; a value of 1 indicates it can be relieved by subsequent notification; a value of 2 indicates it can be relieved based on attribute value. For a notification-based condition, resetelement identifies the notification or attribute that will reset the condition that is in alarm status. If resetobjectspecified is 1, the notification or attribute that causes an alarm to be relieved must come from a specific MBean indicated by resetobject; otherwise, the notification or attribute must come from the same MBean that generated the alarm. For a numeric attribute-based condition, these fields identify thresholds that determine the condition status based on the current value of the attribute. For warncompare and alarmcompare, a value of 0 indicates less than; 1 indicates greater than or equal to. For a boolean attribute-based condition, a value of 0 means the condition is in alarm if the attribute is false; a value of 1 causes the alarm to occur if the attribute is true. For a string attribute-based condition, stringmatch=0 indicates that if the attribute is equal to value, an alarm results. stringmatch=1 indicates that if the attribute is not equal to value, an alarm results.
Keyword and Value
frequency=3 status=1 resettype=1
resetobjectspecified=0; resetelement=weather.not.raining
warnthresh=90; alarmthres=32; warncompare=1; alarmcompare=0 value=0 stringmatch=0; value=xxx
Note: The keywords below control the ability to set JMX attributes, invoke JMX operations, and issue PATROL events based on a change in state of the condition. Conditions that are based on JMX notifications, boolean attributes, and string attributes can be in one of two states: OK or alarm. Conditions that are based on numeric attributes can be in one of three states: OK, warning, or critical. Each keyword described below is presented in the form that would be used to control actions for the critical state (numeric attribute-based condition) or the alarm state (other types of conditions). It is also possile to prefix each keyword below with OK to indicate an action that will be taken for the OK state (any condition) or with WARN to indicate an action that will be taken for the warning state (numeric attribute-based condition only). setattribute=0 setattribute=1; setattributename=ChanceOfRain; setattributevalue=0; setattributeobjectspecified=0; setattributeobject=; setattributeurls=; A value of 0 sets no alarm. A value of 1 for setattribute indicates that an MBean attribute will be set when the critical alarm condition occurs. The attribute name and value are provided. If setattributeobjectspecified is 0, the attribute that has been defined will be set on the same MBean that originated the alarm. If setattributeobjectspecified is 1, the attribute that has been defined will be set on the MBean indicated by invokeoperationobject. setattributeurls allows you to specify values for attributes of non-standard type (e.g., not Integer, String, etc.). A value of 1 for issueevent indicates that a PATROL event will be issued when the critical alarm condition occurs. The event definition indicates the KM containing a message catalog with the event, and the name of the defined event. JMX_REPORT is an event defined in the event catalog for JMX_MAIN.
issueevent=1 eventdefinition= JMX_MAIN.JMX_REPORT
226
Table 19

A value of 1 for invokeoperation indicates that an operation will be invoked when the critical alarm condition occurs. In this case the operation name is provided, arguments are provided delimited by ampersand (&), and the operation signature (set of java classes corresponding to the arguments) is passed in the same way.
Keyword and Value

invokeoperation=1; invokeoperationname=setRange; invokeoperationarguments=70&100; invokeoperationsignature= java.lang.Integer&java.lang. Integer;
invokeoperationobjectspecified=0; If invokeoperationobjectspecified is 0, the operation that has been defined will invokeoperationobject=; be invoked on the same MBean that originated the alarm. If invokeoperationobjectspecified is 1, the operation that has been defined will be invoked on the MBean indicated by invokeoperationobject.
227
228
Chapter
12
12
Log File Monitoring

The PATROL for WebSphere Application Server product contains a log monitoring capability designed with two major goals:
I
providing you with information from and about log files so you can make sound management decisions monitoring log files with the lowest possible impact on product performance
The following sections explain log monitoring: Log Monitoring Benefits and Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Log Monitoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Files Monitored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Monitoring Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Monitoring Parameters and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InfoBoxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activate or Deactivate Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Log Monitor Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting Log Monitor Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Log File Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rewind Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 230 231 231 232 232 233 233 235 235 236 236 237
Log File Monitoring
229
Log Monitoring Benefits and Costs
Log Monitoring Benefits and Costs

As events occur in the IBM WebSphere Application Server, component subsystems record these events by writing a variety of messages to log files on the application server. Although some of these messages are only informational about various status changes or operational actions, others contain warnings and record errors that can indicate potential problems or alert you to critical current situations. Being warned or alerted to a particular problem might help you anticipate and prevent losses to your customers or your company. In addition, log monitoring can be a very useful tool in diagnosing and correcting certain kinds of problems that can develop over time. On the other hand, log monitoring can become quite expensive, both in time and in system resources. How expensive it is depends on three factors:
I
the size of log files the rate at which log files grow the number and complexity of patterns the log monitor is looking for
Performance reductions generally grow proportionally with the size of log files being monitored. The more quickly log files grow, the greater the performance impact is for monitoring those files. Performance reductions grow geometrically as the number and complexity of search patterns increases. BMC Software suggests that you use log monitoring as sparingly as possible. By default, log monitoring is inactive. Leaving it in that state as much as possible and returning it to that state as quickly as possible will significantly enhance system performance.
Default Log Monitoring Settings

When PATROL for WebSphere Application Server detects new messages written to a log during a discovery cycle, an instance icon will be created for the log. Instances are not created for logs that have not had at least one message written to them in the previous 24 hours. Based on a set of defined log monitoring rules, the KM automatically identifies and flags critical log messages as they are written to log files.
230
Default Log Monitoring Settings
Log Files Monitored

PATROL for WebSphere Application Server automatically discovers log files for WebSphere servers on the local machine. The files discovered for monitoring depend on the version of WebSphere in use and whether the file is active (changed within the previous 24 hours) and not empty (not 0 bytes). WebSphere 5.x does not have an Administrative Server and will therefore have administrative server log files for each application server. Some files, such as the activity log (also known as the IBM Service log), appear for all environments. For WebSphere 5.x and later, other files you may see include the process logs (native_stderr.log and native_stdout.log), startServer.log and stopServer.log, and the JVM standard logs (SystemOut.log and SystemErr.log).
NOTE
There is no log monitoring for remote servers.
Default Monitoring Behavior

The default monitoring behavior is based on three factors: whether the entire log file is scanned during a collection cycle what kinds of text messages are scanned how much of the log file is to be scanned, if the entire log file is not scheduled for scanning during a collection cycle The following sections explains default for each of these factors.
Scanning Deferral
By default, the log monitor scans only a specified amount of the log file during a collection cycle and defers scanning the remainder of the file until one or more subsequent collection cycles. If the log file is no longer than the specified amount, the entire file is scanned.
Chapter 12
Log File Monitoring
231
Log Monitoring Parameters and InfoBoxes
Messages Scanned For

By default, the log monitor scans for all specified text messages, whether the messages are associated with INFORMATION events, WARNING events, or ALARM events. However, if the default for scanning only a specified amount of the log file has been changed so that all newly written messages are scanned regardless of log file size, the log monitor scans for all text messages only for a defined maximum number of bytes. Thereafter, the log monitor scans only for messages about ALARM events and ignores messages about INFORMATION and WARNING events.
Default Maximum Scan Size

By default, the log monitor scans only the first 100,000 bytes of newly written log file messages during a collection cycle. The remaining newly written log file messages are deferred until the next collection cycle. If the default has been overridden for scanning only part of the log file during a collection cycles and deferring the remainder for the next cycle, only the first 100,000 bytes are scanned for all messages. Newly written messages about 100,000 bytes are scanned only for messages about ALARM events.
NOTE
Default monitoring behavior should be completely adequate for most businesses, and should not need modification. If needed, the default behavior can be modified through changes to Pconfig variables. Such changes should not be made except by administrators who have extensive experience working with PATROL products. Refer to Advanced Tuning for Large Sites on page 140 for details.

Parameters and InfoBoxes display a variety of useful information about log monitoring.
Parameters
By default the LogGrowthSize parameter, which displays the number of kilobytes by which the log file has grown during the collection cycle, and the LogFileSize parameter are available if log monitoring is selected as part of the KM Setup.
232
The ServerLogCollector parameter, with a poll time of 4393 seconds, makes a fresh discovery of the log files. All the log monitoring parameters are described briefly on page 321 in Appendix B, Parameter Reference. For further information about specific parameters, consult the online Help as explained in Appendix A, Accessing Menu Commands, InfoBoxes, and Online Help.
InfoBoxes
Beyond the standard InfoBoxes, each log file displayed on the PATROL Console has a FileName InfoBox entry that lists the path and file name of the log file being monitored. For a list of all product InfoBoxes, refer to Standard InfoBox Fields on page 428.
Add Log Monitor Rules

You can define filter patterns that generate PATROL events that can be managed using the PATROL Event Manager.
To add log monitor rules 1 Access the instance icon of the log file you are monitoring, and from the KM
Commands menu choose Define Log Monitor Rules. The Log Monitor dialog is displayed.
2 Click the Add button in the Action area, then click OK.
Chapter 12
Log File Monitoring
233
The Log Filter Pattern dialog is displayed.
3 Type the text string or regular expression that you want to use as your filter
pattern. You can also specify strings to be excluded from the search and you can have messages written to the PATROL history file for later viewing on the PATROL Console via the LogMessage parameter by selecting the Annotate Log Messages checkbox.
NOTE
The search based on the filter and excluded patterns is case-sensitive.
4 Select the event type you want assigned to this rule from the Event Type drop
down menu.
5 Type the name of the PATROL event class to which you want this rule associated. 6 Click OK.

After defining text patterns, you can activate or deactivate monitoring based on your patterns by using the Log Monitor dialog box. See Activate or Deactivate Log Monitor Rules on page 235.
234
Activate or Deactivate Log Monitor Rules

The pattern matching filters that you define can be turned on or off at any time. Only active rules are applied against the log. For information about defining pattern matching filters, see Add Log Monitor Rules on page 233.
To activate or deactivate a log monitor rule 1 Access the instance icon of the log file you are monitoring, and from the KM
2 Click Activate/Inactivate in the Action area. This is a toggle switch that changes the
state of a filter between active and inactive.
3 Click OK.
Modifying Log Monitor Rules

You can change defined filter patterns.
NOTE
You need to create filter patterns before you can change patterns. See Activate or Deactivate Log Monitor Rules on page 235.
To change a log filter pattern 1 Access the instance icon of the log file you are monitoring, and from the KM
2 From the list of filters, choose the filter you want to change. You can select multiple
filters by holding down the CTRL key as you click.
3 Click Update in the Action area. 4 Click OK.
Chapter 12
Log File Monitoring
235
The Log Filter Pattern dialog is displayed.
5 Change your patterns using the same guidelines you used to create them. See
Add Log Monitor Rules on page 233.
6 Click OK.
The Log Monitor dialog reappears.
7 Verify that your changes were made. 8 Click OK.
Resetting Log Monitor Defaults

If you make changes to the log monitor rules, you can later reset defaults, discarding your changes.
To reset log monitor defaults 1 Access the instance icon of the log file you are monitoring, and from the KM
Commands menu choose Reset Default. The Log Monitor dialog is displayed.
2 Click Reset Default Action. 3 Click OK.
View Log File Messages

You can view messages in the log file, effectively taking a snap shot of the log messages at a point in time.
To view log file messages 1 Access the instance icon of the log file you are monitoring, and from the KM
Commands menu choose View Log File. The View Log dialog is displayed.
236
2 Position the slide bar near the right to view only the most recent messages. Move it
to the left to display more, and older messages. The counter below the slide bar shows the current setting.
3 Click OK.
Rewind Log File

You can reset the point in the log file at which PATROL starts monitoring.
To rewind a log file 1 Access the instance icon of the log file you want rewound, and from the KM
Commands menu choose Rewind Log File. The Log Rewind dialog is displayed
Chapter 12
Log File Monitoring
237
2 Move the slide bar to the point in the file at which you want to begin. The current
offset (in bytes from the beginning of the file) is shown below the slider.
3 Click OK.
Discovering Log Files

To discover of all the log files for monitoring by PATROL, access the PMW_SERVER_LOGS application class and from the KM menu commands, choose force log discovery.
238
Appendix
Accessing Menu Commands, InfoBoxes, and Online Help

A
BMC Software offers several PATROL consoles from which you can view a PATROL Knowledge Module (KM). Because of the different environments in which these consoles run, each one uses a different method to display and access information in the KM. This appendix provides instructions for accessing the KM menu commands, InfoBoxes, and online Help on each of the PATROL consoles. See the Product Name online Help for more detailed information about navigation in the PATROL Consoles. Accessing KM Commands and InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
239
Accessing KM Commands and InfoBoxes
Accessing KM Commands and InfoBoxes

Table 20 provides information about how to access KM commands and InfoBoxes from the various PATROL consoles. Table 20 Console Accessing KM Commands and InfoBoxes To access menu commands To access InfoBoxes In either the Desktop tree tab or the work area, right-click an application class or parameter icon and choose InfoBox from the pop-up menu.
PATROL Console for Microsoft In either the Desktop tree tab or Windows Servers work area, right-click a computer or application icon and choose KM Commands from the pop-up menu. PATROL Console for Unix
In the work area, right-click a With the middle mouse button, computer or application icon to click an application class or display a pop-up menu that parameter icon. contains KM-specific commands. In the navigation pane, right-click a managed system or application icon and choose Knowledge Module Commands from the pop-up menu. In the navigation pane, right-click a PATROL object and choose InfoBox from the pop-up menu.
PATROL Central Operator Windows Edition
PATROL Central Operator Web Edition
In the tree view area, right-click In the tree view area, right-click an application icon and choose a PATROL object and choose Knowledge Module Commands Infobox from the pop-up menu. from the pop-up menu.
240
Accessing Online Help

Table 21 provides information about how to access Help from each console.
NOTE
If you are trying to access Help from a Unix console, see the PATROL Installation Reference Manual for specific instructions about installing and setting up a browser in the Unix environment.
Table 21 Console
Accessing Online Help (Part 1 of 2) To access product help

I
To access application class help Double-click an application class in the KM tab of the console. From the Application Properties dialog box, click the Help tab. Then click Show Help.
To access parameter help

I
PATROL Console for Microsoft Windows Servers
Right-click the Product Name application icon and choose KM Commands => Product Help. From the console menu bar, choose Help => Help Topics => PATROL Knowledge Modules.
Right-click a parameter icon and choose Help On from the pop-up menu. Double-click a parameter icon; click the ? icon or Help button in the parameter display window. Double-click a parameter in the KM tab of the console; from the properties dialog box, click the Help tab; then click Show Help.
PATROL Console for Unix
Right-click the Product Name application icon and choose KM Commands => Product Help. From the console menu bar, choose Help On => Knowledge Modules.
Choose Attributes => Right-click a parameter Application Classes and icon and click Help On. double-click the application name. Click Show Help in the Application Definition dialog box.
Appendix A
241
Table 21 Console
Accessing Online Help (Part 2 of 2) To access product help To access application class help In the Operator tab of the navigation pane, select an application icon and press F1. In the tree view, right-click an application class and choose Help. To access parameter help In the Operator tab of the navigation pane, select a parameter icon and press F1. In the tree view, right-click a parameter and choose Help.
PATROL Central From the console menu Operator - Windows bar, choose Help => Edition Help Topics. In the Contents tab, click the name of your product. PATROL Central Operator - Web Edition In the upper right corner of PATROL Central, click Help and choose PATROL KM Help.
242
Appendix
Parameter Reference
The PATROL for WebSphere Application Server product contains many parameters that provide statistical information about resources, operating status, and performance. Some of the parameters are available for use with only one version of IBM WebSphere Application Server. Additionally, some parameters are available only when JVM profiling or JVM bytecode instrumentation is active. This information is noted below each parameter description. This appendix contains the following sections: Column Headings Defined. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Abbreviations Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Core Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consumer-Collector Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 245 245 383 386
Parameter Reference
243
Column Headings Defined
Column Headings Defined

Column headings in Table 22 and Table 23 are defined as follows: Description states the parameter name and describes the parameters function; for consumer parameters, lists the collector parameters that gather the data displayed by this parameter indicates two things:
I
Active?
whether a parameter is active by defaultthis information is reflected in the words yes or no whether a parameter requires that JVM profiling or J2EE bytecode instrumentation be activated through the service setup process as explained in if this information applies, it will appear as a second line in the cell with the word prof or
inst
Note: BMC Software recommends that profiling be used only in test and development environments. Parameter Type indicates the parameter type: standard (std) gathers and displays a single data value; collector (coll) gathers multiple data values but has no display capabilities; consumer (con) displays values gathered by collector or standard parameters. Some standards have collector properties. specifies the thresholds for the first-level alarm; not applicable to collector parameters specifies the thresholds for the second-level alarm; not applicable to collector parameters specifies how frequently the parameter will run and collect data (polling cycle); not applicable to consumer parameters specifies whether the parameter is represented as a graph, gauge, text box, stop light (signal), or boolean state specifies the unit of measure in which the parameter output is expressed, such as a percentage, a number, or bytes
Alarm1 Rangea Alarm2 Rangea Scheduling (poll time) Icon Style Unit
a
Border, Alarm1, and Alarm2 ranges that are also labeled inactive by default may not be recommended ranges for the parameter.
244
Abbreviations Defined
Abbreviations Defined
The following abbreviations may be used in Table 22 and Table 23: bool coll con disc GB hr KB MB MHz min msec NA nsec sec std TB undef warn Boolean; shows a state, such as on or off, OK or not OK collector parameter consumer parameter discovery; refers to the PATROL discovery process gigabyte or gigabytes hour or hours kilobyte or kilobytes megabyte or megabytes megahertz minute or minutes millisecond or milliseconds not applicable; a value cannot be set nanosecond or nanoseconds second or seconds standard parameter terabyte or terabytes undefined; a value can be set, but no default is provided warning; type of alert
Core Parameters
The parameters in this table constitute the largest group of parameters in the KM, and apply to the application classes beginning with the PMW_ prefix.
Appendix B
Parameter Reference
245
Core Parameters
Table 22
PATROL for WebSphere Application Server Core Parameters (Part 1 of 137) Scheduling Warning (Alarm1) Alarm (Alarm2)
Active?
PMW_ALARM_MANAGER application class

AlarmCancelled (PMW_ALARM_MANAGER) Displays the number of alarms cancelled by the application. Collector: PerfCollector2 WebSphere version: 6.x AlarmCreated (PMW_ALARM_MANAGER) Displays the number of alarms created by all asynchronous scopes for this Work Manager. Collector: PerfCollector2 WebSphere version: 6.x AlarmFired (PMW_ALARM_MANAGER) Displays the number of alarms fired. Collector: PerfCollector2 WebSphere version: 6.x AlarmLatencyDuration (PMW_ALARM_MANAGER) Latency of alarms fired (in milliseconds). Collector: PerfCollector2 WebSphere version: 6.x AlarmPendingSize (PMW_ALARM_MANAGER) Displays the number of alarms waiting to fire. Collector: PerfCollector2 WebSphere version: 6.x AlarmRate (PMW_ALARM_MANAGER) Displays the number of alarms firing per second. Collector: PerfCollector2 WebSphere version: 6.x yes con undef undef set by coll graph number yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph msec yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph number of alarms
246
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_ALARM_SUMMARY application class

AlarmCancelled (PMW_ALARM_SUMMARY) Displays the total number of alarms cancelled by any application. Collector: PerfCollector2 WebSphere version: 6.x AlarmCreated (PMW_ALARM_SUMMARY) Displays the total number of alarms created by all asynchronous scopes for all Work Managers. Collector: PerfCollector2 WebSphere version: 6.x AlarmFired (PMW_ALARM_SUMMARY) Displays the total number of alarms fired. Collector: PerfCollector2 WebSphere version: 6.x AlarmLatencyDuration (PMW_ALARM_SUMMARY) Latency of alarms fired (in milliseconds). Collector: PerfCollector2 WebSphere version: 6.x AlarmPendingSize (PMW_ALARM_SUMMARY) Displays the total number of alarms waiting to fire. Collector: PerfCollector2 WebSphere version: 6.x AlarmRate (PMW_ALARM_SUMMARY) Displays the number of alarms firing per second. Collector: PerfCollector2 WebSphere version: 6.x yes con undef undef set by coll graph number yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph msec yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph number of alarms yes con undef undef set by coll graph number of alarms
Appendix B
Parameter Reference
247
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_APPSERVER application class

AppServerAvailability (PMW_APPSERVER) Indicates the availability of the application server during the collection interval: running (0) or unavailable (1). Collector: AppServerCollector DbUrlsDisc (PMW_APPSERVER) Collects a list of DBURL names available during runtime within the collection interval. If data is available during setup, the setup routine populates a selection list of DBURLs for monitoring during bytecode instumentation. Collector: not applicable HTTPTransportConnState (PMW_APPSERVER) Shows the connection status of the HTTP transport connection. Collector: ServerTransportCol PerfCollector2 (PMW_APPSERVER) Serves as the primary collector for the PATROL for WebSphere Application Server. This collector creates and populates the instances and data performance metrics for most consumer parameters in the product. Collector: not applicable PjsClassNameDisc (PMW_APPSERVER) Collects a list of Java class names available during runtime within the collection interval. If data is available during the setup time, setup will populate a selection list of classes for monitoring method profiling. Collector: not applicable yes coll NA NA 10 min NA (600 sec) none yes coll NA NA 63 sec NA none no con 1-10 10-10 set by coll state bool. 0=OK, 1=failed yes coll NA NA 3 min (180 sec) NA none yes con 1 to 1 1 to 1 set by coll state bool 0=running 1=stopped.
248
Units
Type
Icon
Core Parameters
Table 22
Active?
PjsMethodProfileDisc (PMW_APPSERVER) Collects a list of method names available within a Java class during runtime within the collection interval. If data is available during the setup time, setup will populate a selection list of methods for monitoring during method profiling. Collector: not applicable WebSphere version: all supported versions PjsServletMethodDisc (PMW_APPSERVER) Collects a list of servlet methods and populates the selection lists for method profiling. Collector: not applicable WebSphere version: all supported versions PmiLevel (PMW_APPSERVER) Shows the current setting of the PMI level. The PMI level determines whether data are collected for different sets of parameters. This parameter shows a level from 0 to 4, with 0 representing no PMI data, 1 low, 2 medium, 3 high, and 4 maximum. Collector: PerfCollector2 WebSphere versions: all supported versions
yes
coll
NA
NA
2 min (120 sec)
NA
none
yes
coll
NA
NA
4 min (240 sec)
NA
none
no
con
0-4 (inact.)
4-4 (inact.)
set by coll
gauge
0=none 1=low 2=med 3=high 4=max
PMW_BEANS application class

ActiveMethods (PMW_BEANS) Displays the number of concurrent method invocations of the bean that took place during the collection interval, averaged across all methods of the bean. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high AvgDrainSize (PMW_BEANS) Displays the number of objects returned to the object pool when the object pool was drained, averaged across the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium no con undef undef set by coll graph number of objects no con undef undef set by coll graph number of invocations
Appendix B
Parameter Reference
249
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanActivates (PMW_BEANS) Displays the number of times that an instance of the bean was activated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanActivateRate (PMW_BEANS) Displays the number of times per second that an instance of the bean was activated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanActivateTime (PMW_BEANS) Displays the average time a beanActivate call takes, including the time at the database (if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeanCreates (PMW_BEANS) Displays the number of instances of the bean that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanCreateRate (PMW_BEANS) Displays the number of instances of the bean that were created per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of activations
no
con
undef
undef
set by coll
graph
number of activations
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of calls
no
con
undef
undef
set by coll
graph
number of calls
250
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanCreateTime (PMW_BEANS) Displays the average elapsed time required to execute the bean's create method during the collection interval, including load time (if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeanDestroys (PMW_BEANS) Displays the number of instances of the bean that were destroyed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanDestroyRate (PMW_BEANS) Displays the number of instances of the bean that were destroyed per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanInstantiates (PMW_BEANS) Displays the number of times that beans were instantiated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanInstantiateRate (PMW_BEANS) Displays the number of times that beans were instantiated per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of bean objects
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
number of times instantiated
no
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
251
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanLoads (PMW_BEANS) Displays the number of times during the collection interval that bean data was loaded from persistent storage Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanLoadRate (PMW_BEANS) Displays the number of times during the collection interval that bean data was loaded per second from persistent storage Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanMethodCalls (PMW_BEANS) Displays the number of times during the collection interval that methods were invoked. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanMethodCallsPerSec (PMW_BEANS) Displays the number of times per second during the collection interval that methods were invoked. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanMethodCallsRate (PMW_BEANS) Displays the rate at which methods were invoked during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high
no
con
undef
undef
set by coll
graph
number of loads
no
con
undef
undef
set by coll
graph
number of loads
yes
con
undef
undef
set by coll
graph
number of invocations
yes
con
undef
undef
set by coll
graph
number of invocations per second
yes
con
undef
undef
set by coll
graph
invocations per minute
252
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanMethodLoads (PMW_BEANS) Displays the average number of method invocations that were processed concurrently over all methods during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max BeanMethodRT (PMW_BEANS) Reports the average response time for all methods of the remote interface for this bean (execution time). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max BeanPassivates (PMW_BEANS) Displays the number of times during the collection interval that instances of the bean were passivated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanPassivateRate (PMW_BEANS) Displays the number of times per second during the collection interval that instances of the bean were passivated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanPassivateTime(PMW_BEANS) Displays the average time a beanPassivate call takes, including the time at the database (if any) Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium
no
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number of passivation s
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
253
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanPoolSize (PMW_BEANS) Displays the average number of available connections in the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanRemoves (PMW_BEANS) Displays the number of times during the collection interval that the bean's remove method was called. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanRemoveRate (PMW_BEANS) Displays the number of times per second during the collection interval that the bean's remove method was called. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanRemoveTime (PMW_BEANS) Displays the average elapsed time required to execute the bean's remove method during the collection interval (including database access time if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeansActive (PMW_BEANS) Displays the average number of times bean instances are in the ready state. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high
no
con
undef
undef
set by coll
graph
number of beans
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number of times ready
254
Units
Type
Icon
Core Parameters
Table 22
Active?
BeansLive (PMW_BEANS) Displays the average number of times bean objects exist in runtime. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanStores (PMW_BEANS) Displays the number of times during the collection interval that bean data was moved to persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanStoreRate (PMW_BEANS) Displays the number of times during the collection interval that bean data was moved to persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low DrainsFromPool (PMW_BEANS) Displays the number of times during the collection interval that WebSphere found the connection pool was idle and attempted to drain unneeded connections. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low DrainsFromPoolRate (PMW_BEANS) Displays the number of times during the collection interval that WebSphere found the connection pool was idle and attempted to drain unneeded connections. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of objects
no
con
undef
undef
set by coll
graph
number of writes
no
con
undef
undef
set by coll
graph
number of writes
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
Appendix B
Parameter Reference
255
Units
Type
Icon
Core Parameters
Table 22
Active?
GetsFound (PMW_BEANS) Displays the number of get requests processed during the collection interval that found the requested object in the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFoundRate (PMW_BEANS) Displays the number of get requests processed per second during the collection interval that found the requested object in the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFromPool (PMW_BEANS) Displays the number of get requests for objects in the object pool that were processed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFromPoolRate (PMW_BEANS) Displays the number of get requests for objects in the object pool that were processed per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsBackedOut (PMW_BEANS) Displays the number of messages that failed to be delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of messages
256
Units
Type
Icon
Core Parameters
Table 22
Active?
MsgsBackedOutRate (PMW_BEANS) Displays the number of average number of messages per second that failed to be delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsDelivered (PMW_BEANS) Displays the number of messages that were delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsDeliveredRate (PMW_BEANS) Displays the average number of messages per second that were delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsDiscarded (PMW_BEANS) Displays the number of times during the collection interval that objects that had been returned to the object pool were discarded from the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsDiscardedRate (PMW_BEANS) Displays the number of times per second during the collection interval that objects that had been returned to the object pool were discarded from the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
yes
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
yes
con
undef
undef
set by coll
graph
number of messages
yes
con
undef
undef
set by coll
graph
number of times returned
yes
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
257
Units
Type
Icon
Core Parameters
Table 22
Active?
ReturnsToPool (PMW_BEANS) Displays the number of objects that were returned to the object pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsToPoolRate (PMW_BEANS) Displays the number of objects that were returned to the object pool each second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low SvrSessionUtilization (PMW_BEANS) Percentage of server session pool in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high SvrSessionWait (PMW_BEANS) Average time to obtain ServerSession from the pool (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium
yes
con
undef
undef
set by coll
graph
number of objects returned
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
percent
no
con
undef
undef
set by coll
graph
msec
PMW_BLACKOUT application class

PMW_BlackoutCollector (PMW_BLACKOUT) Determines whether a blackout period is due to begin or expire by schedule. Also determines whether a command has been issued to suspend or resume monitoring on one or more application servers. Generates the events needed to implement the blackout schedule or to execute the suspend or resume command. Collector: not applicable WebSphere version: all supported versions yes std NA NA 60 sec NA none
258
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_CACHE_SUMMARY application class

ClientRequests (PMW_CACHE_SUMMARY) Requests for this cacheable object generated by applications running on the application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ClientRequestRate (PMW_CACHE_SUMMARY) Requests per second for this cacheable object. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom CurrentEntries (PMW_CACHE_SUMMARY) Current number of cache entries created from this template. Refers to the per-template equivalent of totalCacheSize. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom CurrentEntriesInMemory (PMW_CACHE_SUMMARY) Number of cache entries currently in memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvalidations (PMW_CACHE_SUMMARY) Total explicit invalidations issued for this template. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number yes con undef undef set by coll graph number yes con undef undef set by coll graph number yes con undef undef set by coll graph number no con undef undef set by coll graph number
Appendix B
Parameter Reference
259
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvalidationRate (PMW_CACHE_SUMMARY) Total explicit invalidations per second issued for this template. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvDisk (PMW_CACHE_SUMMARY) Explicit invalidations resulting in an entry being removed from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvDiskRate (PMW_CACHE_SUMMARY) Explicit invalidations per second resulting in an entry being removed from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvLocal (PMW_CACHE_SUMMARY) Explicit invalidations generated locally, either programmatically or by a cache policy. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
260
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvLocalRate (PMW_CACHE_SUMMARY) Explicit invalidations per second generated locally, either programmatically or by a cache policy. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvMemory (PMW_CACHE_SUMMARY) Explicit invalidations resulting in an entry being removed from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvMemoryRate (PMW_CACHE_SUMMARY) Explicit invalidations per second resulting in an entry being removed from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvNoEntry (PMW_CACHE_SUMMARY) Explicit invalidations received for this template where no corresponding entry exists. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
261
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvNoEntryRate (PMW_CACHE_SUMMARY) Explicit invalidations received per second for this template where no corresponding entry exists. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvRemote (PMW_CACHE_SUMMARY) Explicit invalidations received from a cooperating JVM in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
ExplicitInvRemoteRate (PMW_CACHE_SUMMARY) yes Explicit invalidations received per second from a cooperating JVM in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsInMemory (PMW_CACHE_SUMMARY) Requests for this cacheable object served from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no
con
undef
undef
set by coll
graph
number
con
undef
undef
set by coll
graph
number
262
Units
Type
Icon
Core Parameters
Table 22
Active?
HitsInMemoryRate (PMW_CACHE_SUMMARY) Requests per second for this cacheable object served from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsOnDisk (PMW_CACHE_SUMMARY) Requests for this cacheable object served from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsOnDiskRate (PMW_CACHE_SUMMARY) Requests per second for this cacheable object served from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom JVMRequests (PMW_CACHE_SUMMARY) Requests for this cacheable object generated by cooperating caches in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom JVMRequestRate (PMW_CACHE_SUMMARY) Requests per second for this cacheable object generated by cooperating caches in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
263
Units
Type
Icon
Core Parameters
Table 22
Active?
LruInvalidations (PMW_CACHE_SUMMARY) Cache entries evicted from memory by a Least Recently Used (LRU) algorithm. These entries are passivated to disk if disk overflow is enabled. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LruInvalidationsRate (PMW_CACHE_SUMMARY) Cache entries evicted from memory per second by a Least Recently Used (LRU) algorithm. These entries are passivated to disk if disk overflow is enabled. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom MaxEntriesInMemory (PMW_CACHE_SUMMARY) Maximum number of in-memory cache objects. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom Misses (PMW_CACHE_SUMMARY) Requests per second for this cacheable object that were not found in the cache. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
264
Units
Type
Icon
Core Parameters
Table 22
Active?
MissRate (PMW_CACHE_SUMMARY) Requests for this cacheable object that were not found in the cache. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RemoteCreations (PMW_CACHE_SUMMARY) Entries received from cooperating dynamic caches. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RemoteCreationRate (PMW_CACHE_SUMMARY) Entries received per second from cooperating dynamic caches. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom TemplateTimeouts (PMW_CACHE_SUMMARY) Aggregate of template timeouts and disk timeouts. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom TemplateTimeoutRate (PMW_CACHE_SUMMARY) Aggregate of template timeouts per second and disk timeouts per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
265
Units
Type
Icon
Core Parameters
Table 22
Active?
TimeoutInvalidations (PMW_CACHE_SUMMARY) Cache entries evicted from memory and/or disk because their timeout expired. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom TimeoutInvalidationRate (PMW_CACHE_SUMMARY) Cache entries evicted per second from memory and/or disk because their timeout expired. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
PMW_CACHE_TEMPLATE application class

ClientRequests (PMW_CACHE_TEMPLATE) Requests for this cacheable object generated by applications running on the application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ClientRequestRate (PMW_CACHE_TEMPLATE) Requests per second for this cacheable object. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom yes con undef undef set by coll graph number no con undef undef set by coll graph number
266
Units
Type
Icon
Core Parameters
Table 22
Active?
CurrentEntries (PMW_CACHE_TEMPLATE) Current number of cache entries created from this template. Refers to the per-template equivalent of totalCacheSize. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom CurrentEntriesInMemory (PMW_CACHE_TEMPLATE) Number of cache entries currently in memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvalidations (PMW_CACHE_TEMPLATE) Total explicit invalidations issued for this template. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvalidationsRate (PMW_CACHE_TEMPLATE) Total explicit invalidations per second issued for this template. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
267
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvDisk (PMW_CACHE_TEMPLATE) Explicit invalidations resulting in an entry being removed from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvDiskRate (PMW_CACHE_TEMPLATE) Explicit invalidations per second resulting in an entry being removed from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvLocal (PMW_CACHE_TEMPLATE) Explicit invalidations generated locally, either programmatically or by a cache policy. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvLocalRate (PMW_CACHE_TEMPLATE) Explicit invalidations per second generated locally, either programmatically or by a cache policy. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
268
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvMemory (PMW_CACHE_TEMPLATE) Explicit invalidations resulting in an entry being removed from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvMemoryRate (PMW_CACHE_TEMPLATE) Explicit invalidations per second resulting in an entry being removed from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvNoEntry (PMW_CACHE_TEMPLATE) Explicit invalidations received for this template where no corresponding entry exists. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvNoEntryRate (PMW_CACHE_TEMPLATE) Explicit invalidations received per second for this template where no corresponding entry exists. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
269
Units
Type
Icon
Core Parameters
Table 22
Active?
ExplicitInvRemote (PMW_CACHE_TEMPLATE) Explicit invalidations received from a cooperating JVM in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExplicitInvRemoteRate (PMW_CACHE_TEMPLATE) Explicit invalidations received per second from a cooperating JVM in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsInMemory (PMW_CACHE_TEMPLATE) Requests for this cacheable object served from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsInMemoryRate (PMW_CACHE_TEMPLATE) Requests per second for this cacheable object served from memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
270
Units
Type
Icon
Core Parameters
Table 22
Active?
HitsOnDisk (PMW_CACHE_TEMPLATE) Requests for this cacheable object served from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom HitsOnDiskRate (PMW_CACHE_TEMPLATE) Requests per second for this cacheable object served from disk. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom JVMRequests (PMW_CACHE_TEMPLATE) Requests for this cacheable object generated by cooperating caches in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom JVMRequestRate (PMW_CACHE_TEMPLATE) Requests per second for this cacheable object generated by cooperating caches in this cluster. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
271
Units
Type
Icon
Core Parameters
Table 22
Active?
LruInvalidations (PMW_CACHE_TEMPLATE) Cache entries evicted from memory by a Least Recently Used (LRU) algorithm. These entries are passivated to disk if disk overflow is enabled. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LruInvalidationRate (PMW_CACHE_TEMPLATE) Cache entries evicted from memory per second by a Least Recently Used (LRU) algorithm. These entries are passivated to disk if disk overflow is enabled. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom MaxEntriesInMemory (PMW_CACHE_TEMPLATE) Maximum number of in-memory cache objects. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom Misses (PMW_CACHE_TEMPLATE) Requests for this cacheable object that were not found in the cache. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
272
Units
Type
Icon
Core Parameters
Table 22
Active?
MissRate (PMW_CACHE_TEMPLATE) Requests for this cacheable object that were not found in the cache. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RemoteCreations (PMW_CACHE_TEMPLATE) Entries received from cooperating dynamic caches. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RemoteCreationRate (PMW_CACHE_TEMPLATE) Entries received per second from cooperating dynamic caches. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom TemplateTimeouts (PMW_CACHE_TEMPLATE) Aggregate of template timeouts and disk timeouts. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
TemplateTimeoutRate (PMW_CACHE_TEMPLATE) yes Aggregate of template timeouts per second and disk timeouts per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
273
Units
Type
Icon
Core Parameters
Table 22
Active?
TimeoutInvalidations (PMW_CACHE_TEMPLATE) Cache entries evicted from memory and/or disk because their timeout expired. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom TimeoutInvalidationRate (PMW_CACHE_TEMPLATE) Cache entries evicted per second from memory and/or disk because their timeout expired. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
PMW_CELL application class

DMgrAvailability (PMW_CELL) Availability (up or down) of the Deployment Manager. Collector: PerfCollector WebSphere version: all supported versions yes con 1 to 1 undef set by coll state bool 0=running, 1=stopped
PMW_CLUSTER application class

AvailableServers (PMW_CELL) Number of servers available in the cluster. Collector: PerfCollector WebSphere version: all supported versions yes con undef undef set by coll graph number of servers
PMW_DATASOURCE application class

AvgJDBCTime (PMW_DATASOURCE) Amount of time (in milliseconds) spent executing the JDBC driver (includes time spent in JDBC driver, network, and database). Collector: PerfCollector2 WebSphere version: 5.0 WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic no con undef undef set by coll graph msec
274
Units
Type
Icon
Core Parameters
Table 22
Active?
AvgTimeHeld (PMW_DATASOURCE) Displays the average length of time during the collection interval that a connection was active. Collector: PerfCollector2 WebSphere version: 5.0 WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic AvgWaitTime (PMW_DATASOURCE) Displays the average length of time during the collection interval that a thread had to wait for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ConcurrentWaiters (PMW_DATASOURCE) Displays the average number of threads waiting for an available connection from the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ConnectionAllocates (PMW_DATASOURCE) Displays the number of connections that were allocated from the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionAllocateRate (PMW_DATASOURCE) Displays the number of connections per minute that were allocated from the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of connections
no
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
275
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionCreates (PMW_DATASOURCE) Displays the number of connections that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionCreateRate (PMW_DATASOURCE) Displays the number of connections per minute that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionDestroys (PMW_DATASOURCE) Displays the number of connections that were destroyed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionDestroyRate (PMW_DATASOURCE) Displays the number of connections that were destroyed per minute during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionFaults (PMW_DATASOURCE) Displays the number of times during the collection interval that a thread timed out while waiting for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
number of threads
276
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionFaultRate (PMW_DATASOURCE) Displays the number of times per minute during the collection interval that a thread timed out while waiting for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionReturns (PMW_DATASOURCE) Displays the number of connections that were deactivated and made available for re-use during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionReturnRate (PMW_DATASOURCE) Displays the number of connections that were deactivated per minute and made available for re-use during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsInUse (PMW_DATASOURCE) Displays the number of connections in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom DataSource_Col (PMW_DATASOURCE) Launches a Java class file that retrieves required data source and JDBC driver information from the admin repository. This is a background process only and does not set values for any consumer parameters. Collector: not applicable WebSphere version: all supported versions
yes
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
yes
coll
NA
NA
4 NA hours (14400 sec)
none
Appendix B
Parameter Reference
277
Units
Type
Icon
Core Parameters
Table 22
Active?
DbFreePoolSize (PMW_DATASOURCE) Average free pool size. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended DbPercentMaxed (PMW_DATASOURCE) Displays the percentage of time during the collection interval that all possible connections in the connection pool were active. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended DbPoolSize (PMW_DATASOURCE) Displays the average number of available connections in the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended JDBCConnectState (PMW_DATASOURCE) Indicates the availability of the data source JDBC connection during the collection interval: 1 (available) or 0 (unavailable). Collector: standard parameterself collecting WebSphere version: all supported versions ManagedConnectionsInUse (PMW_DATASOURCE) Displays the number of ManagedConnections objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
percentage
yes
con
undef
undef
set by coll
graph
yes
std
0 to 0
0 to 0
600 sec state bool
1=OK 0=down
yes
con
undef
undef
set by coll
graph
278
Units
Type
Icon
Core Parameters
Table 22
Active?
PercentUsed (PMW_DATASOURCE) Displays the average percentage of the connection pool that was active during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended PrepStmtCacheDiscards (PMW_DATASOURCE) Displays the number of prepared SQL statements that were discarded from the cache during the collection interval because the cache was full. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom PrepStmtCacheDiscardRate (PMW_DATASOURCE) Displays the number of prepared SQL statements that were discarded per minute from the cache during the collection interval because the cache was full. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
80 - 90
90 - 100 set by coll
graph
percentage
no
con
undef
undef
set by coll
graph
number of statements discarded
no
con
undef
undef
set by coll
graph
PMW_DBPOOLS_SUMMARY application class

AvgJDBCTime (PMW_DBPOOLS_SUMMARY) Amount of time (in milliseconds) spent executing the JDBC driver (includes time spent in JDBC driver, network, and database). Collector: PerfCollector2 WebSphere version: 5.0 WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic yes con undef undef set by coll graph msec
Appendix B
Parameter Reference
279
Units
Type
Icon
Core Parameters
Table 22
Active?
AvgTimeHeld (PMW_DBPOOLS_SUMMARY) Displays the average length of time during the collection interval that a connection was active. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic AvgWaitTime (PMW_DBPOOLS_SUMMARY) Displays the average length of time during the collection interval that a thread had to wait for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ConcurrentWaiters (PMW_DBPOOLS_SUMMARY) Displays the average number of threads waiting for an available connection from the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended
no
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of threads
ConnectionAllocates (PMW_DBPOOLS_SUMMARY) yes Displays the number of connections that were allocated from the connection pool during the collection interval Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
con
undef
undef
set by coll
graph
280
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionAllocateRate (PMW_DBPOOLS_SUMMARY) Displays the number of connections that were allocated from the connection pool during the collection interval Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionCreates (PMW_DBPOOLS_SUMMARY) Displays the number of connections that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionCreateRate (PMW_DBPOOLS_SUMMARY) Displays the number of connections per second that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
ConnectionDestroys (PMW_DBPOOLS_SUMMARY) no Displays the number of connections that were destroyed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionDestroyRate (PMW_DBPOOLS_SUMMARY) Displays the number of connections per second that were destroyed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no
con
undef
undef
set by coll
graph
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
281
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionFaults (PMW_DBPOOLS_SUMMARY) Displays the number of times during the collection interval that a thread timed out while waiting for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionFaultRate (PMW_DBPOOLS_SUMMARY) Displays the number of times during the collection interval that a thread timed out while waiting for an available connection from the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionReturns (PMW_DBPOOL_SUMMARY) Displays the number of connections that were deactivated and made available for re-use during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionReturnRate (PMW_DBPOOL_SUMMARY) Displays the number of connections per second that were deactivated and made available for re-use during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number of threads
yes
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
282
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionsInUse (PMW_DBPOOLS_SUMMARY) Displays the number of connections from the pool that were being used at the time the collector last ran. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom DbFreePoolSize (PMW_DBPOOLS_SUMMARY) Average free pool size. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended DbPercentMaxed (PMW_DBPOOLS_SUMMARY) Displays the percentage of time during the collection interval that all possible connections in the connection pool were active. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended DbPoolSize (PMW_DBPOOLS_SUMMARY) Displays the average number of available connections in the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ManagedConnectionsInUse (PMW_DBPOOLS_SUMMARY Displays the number of ManagedConnections objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
yes
con
80-90
90-100
set by coll
graph
percentage
no
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
283
Units
Type
Icon
Core Parameters
Table 22
Active?
PercentUsed (PMW_DBPOOLS_SUMMARY) Displays the average percentage of the connection pool that was active during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended PrepStmtCacheDiscards (PMW_DBPOOL_SUMMARY) Displays the number of prepared SQL statements that were discarded from the cache during the collection interval because the cache was full. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom PrepStmtCacheDiscardRate (PMW_DBPOOL_SUMMARY) Displays the number of prepared SQL statements that were discarded per second from the cache during the collection interval because the cache was full. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
percentage
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
PMW_DBURL application class

AggregatedInvocationRate (PMW_DBURL) Displays the rate at which SQL statements were invoked over all SQL statements generated from the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions no, inst con undef undef set by coll graph invocations per sec
284
Units
Type
Icon
Core Parameters
Table 22
Active?
AvgRespTime (PMW_DBURL) Displays the average response time for all SQL statement invocations over all SQL statements generated from the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions DbUrlCollector (PMW_DBURL) Invokes four byte code instrumentation collectors that discover up to the top 30 SQL statements and collect information required for the SQL Performance Report by Database URL menu command. Collector: PMW_DBURLS/SvrDbUrlCollector WebSphere version: all supported versions HighestInvocationRate (PMW_DBURL) Displays the highest rate of invocations of any SQL statement generated from the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions HighestInvocations (PMW_DBURL) Displays the highest number of invocations of any SQL statement generated from the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions MostCumulativeTime (PMW_DBURL) Displays the highest amount of cumulative time (in milliseconds) that it took to respond to all invocations of an SQL statement generated from the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions
no, inst
con
undef
undef
set by coll
graph
msec
yes, inst
coll
NA
NA
4 min (240 sec)
NA
none
no, inst
con
undef
undef
set by coll
graph
invocations per sec
no, inst
con
undef
undef
set by coll
graph
invocations
no, inst
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
285
Units
Type
Icon
Core Parameters
Table 22
Active?
SlowestRespTime (PMW_DBURL) Displays the slowest response time (in milliseconds) for a single invocation of an SQL statement generated from the database URL during the collection cycle Collector: DbUrlCollector WebSphere version: all supported versions TotalCumulativeTime (PMW_DBURL) Displays the total cumulative response time (in milliseconds) for all invocations to all SQL statements generated from the database URL in the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions TotalInvocations (PMW_DBURL) Displays the total number of invocations to all SQL statements generated from the database URL in the database URL during the collection cycle. Collector: DbUrlCollector WebSphere version: all supported versions
no, inst
con
undef
undef
set by coll
graph
msec
no, inst
con
undef
undef
set by coll
graph
msec
no, inst
con
undef
undef
set by coll
graph
invocations
PMW_DBURLS application class

SvrDbUrlCollector (PMW_DBURLS) Invokes four byte code instrumentation collectors that discover all database URLs and collect information required for the SQL Performance Report by Application Server menu command. Collector: not applicable WebSphere version: all supported versions yes, inst coll NA NA 306 sec NA none
PMW_DCS application class

CoalesceTime (PMW_DCS) Displays the amount of time that it actually takes to coalesce a view. Collector: PerfCollector2 WebSphere version: 6.x no con undef undef set by coll graph msec
286
Units
Type
Icon
Core Parameters
Table 22
Active?
HighSeverityCongestionEvent (PMW_DCS) Displays the number of times that a high severity congestion event for outgoing messages was raised. Collector: PerfCollector2 WebSphere version: 6.x IncomingMessageSize (PMW_DCS) Displays the minimal, maximal, and average size of messages that were received by the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x JoinViewChangeTime (PMW_DCS) Displays the amount of time for joining existing partitions. Collector: PerfCollector2 WebSphere version: 6.x LocalMessageRetransmission (PMW_DCS) Displays the number of messages that were retransmitted. Collector: PerfCollector2 WebSphere version: 6.x MessageBufferReallocation (PMW_DCS) Displays the number of message buffer reallocations due to inadequate buffer size. If this number is larger than 20 percent of the number of sent messages, you may want to contact IBM support. Collector: PerfCollector2 WebSphere version: 6.x OutgoingMessageSize (PMW_DCS) Displays the minimal, maximal, and average size of the messages that were sent through the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
bytes
Appendix B
Parameter Reference
287
Units
Type
Icon
Core Parameters
Table 22
Active?
ReceivedMessages (PMW_DCS) Displays the number of messages received by the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x RemoveViewChangeTime (PMW_DCS) Displays the amount of time for splitting a group. Collector: PerfCollector2 WebSphere version: 6.x SentMessageCount (PMW_DCS) Displays the number of messages sent through the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x Suspicion (PMW_DCS) Displays the number of times that the local member suspected other members. Collector: PerfCollector2 WebSphere version: 6.x SynchronizationCompleteTime (PMW_DCS) Displays the amount of time needed to guarantee that all view members are synchronized. Collector: PerfCollector2 WebSphere version: 6.x SynchronizationTimeout (PMW_DCS) Displays the number of times that the synchronization procedure timed out. Collector: PerfCollector2 WebSphere version: 6.x ViewChange (PMW_DCS) Displays the number of times that the member underwent view changes. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
288
Units
Type
Icon
Core Parameters
Table 22
Active?
ViewChangeTimeout (PMW_DCS) Displays the number of times that a view/change procedure timed out. Collector: PerfCollector2 WebSphere version: 6.x ViewGroupSize (PMW_DCS) Displays the size of the group to which the local member belongs. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
bytes
PMW_DCS_SUMMARY application class

CoalesceTime (PMW_DCS_SUMMARY) Displays the amount of time that it actually takes to coalesce a view. Collector: PerfCollector2 WebSphere version: 6.x HighSeverityCongestionEvent (PMW_DCS_SUMMARY) Displays the number of times that a high severity congestion event for outgoing messages was raised. Collector: PerfCollector2 WebSphere version: 6.x IncomingMessageSize (PMW_DCS_SUMMARY) Displays the minimal, maximal, and average size of messages that were received by the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x JoinViewChangeTime (PMW_DCS_SUMMARY) Displays the amount of time for joining existing partitions. Collector: PerfCollector2 WebSphere version: 6.x no con undef undef set by coll graph msec no con undef undef set by coll graph bytes no con undef undef set by coll graph number no con undef undef set by coll graph msec
Appendix B
Parameter Reference
289
Units
Type
Icon
Core Parameters
Table 22
Active?
LocalMessageRetransmission (PMW_DCS_SUMMARY) Displays the number of messages that were retransmitted. Collector: PerfCollector2 WebSphere version: 6.x MessageBufferReallocation (PMW_DCS_SUMMARY) Displays the number of message buffer reallocations due to inadequate buffer size. If this number is larger than 20 percent of the number of sent messages, you may want to contact IBM support. Collector: PerfCollector2 WebSphere version: 6.x OutgoingMessageSize (PMW_DCS_SUMMARY) Displays the minimal, maximal, and average size of the messages that were sent through the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x ReceivedMessages (PMW_DCS_SUMMARY) Displays the number of messages received by the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number of messages
RemoveViewChangeTime (PMW_DCS_SUMMARY) no Displays the amount of time for splitting a group. Collector: PerfCollector2 WebSphere version: 6.x SentMessageCount (PMW_DCS_SUMMARY) Displays the number of messages sent through the DCS stack. Collector: PerfCollector2 WebSphere version: 6.x no
con
undef
undef
set by coll
graph
msec
con
undef
undef
set by coll
graph
number of messages
290
Units
Type
Icon
Core Parameters
Table 22
Active?
Suspicion (PMW_DCS_SUMMARY) Displays the number of times that the local member suspected other members. Collector: PerfCollector2 WebSphere version: 6.x SynchronizationCompleteTime (PMW_DCS_SUMMARY) Displays the amount of time needed to guarantee that all view members are synchronized. Collector: PerfCollector2 WebSphere version: 6.x SynchronizationTimeout (PMW_DCS_SUMMARY) Displays the number of times that the synchronization procedure timed out. Collector: PerfCollector2 WebSphere version: 6.x ViewChange (PMW_DCS_SUMMARY) Displays the number of times that the member underwent view changes. Collector: PerfCollector2 WebSphere version: 6.x ViewChangeTimeout (PMW_DCS_SUMMARY) Displays the number of times that a view/change procedure timed out. Collector: PerfCollector2 WebSphere version: 6.x ViewGroupSize (PMW_DCS_SUMMARY) Displays the size of the group to which the local member belongs. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
bytes
Appendix B
Parameter Reference
291
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_EJB_METHOD application class

MethodCalls (PMW_EJB_METHOD) Displays the number of times during the collection interval that the method was invoked. Collector: PerfCollector WebSphere version: all supported versions WebSphere 6 PMI Level: all MethodCallRate (PMW_EJB_METHOD) Displays the rate at which the method was invoked during the collection interval. Collector: PerfCollector WebSphere version: all supported versions WebSphere 6 PMI Level: all MethodCallsPerSec (PMW_EJB_METHOD) Displays the number of times per second during the collection interval that the method was invoked. Collector: PerfCollector WebSphere version: all supported versions WebSphere 6 PMI Level: all MethodConcurrentCalls (PMW_EJB_METHOD) Number of concurrent invocations to call a method. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max WebSphere 6 PMI Level: all MethodRT (PMW_EJB_METHOD) Displays the elapsed time required to execute the method during the collection interval. Collector: PerfCollector WebSphere version: all supported versions WebSphere 6 PMI Level: all no con undef undef set by coll graph msec yes con undef undef set by coll graph number of calls no con undef undef set by coll graph invocations per second no con undef undef set by coll graph invocations per minute no con undef undef set by coll graph number of invocations
292
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_EJB_SUMMARY application class

ActiveMethods (PMW_EJB_SUMMARY) Displays the number of concurrent method invocations of the bean that took place during the collection interval, averaged across all methods of summarized beans. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high AvgDrainSize (PMW_EJB_SUMMARY) Displays the number of objects returned to the object pool when the object pool was drained, averaged across the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeanActivates (PMW_EJB_SUMMARY) Displays the number of times that an instance of the bean was activated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanActivateRate (PMW_EJB_SUMMARY) Displays the number of times per second that an instance of the bean was activated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanActivateTime (PMW_EJB_SUMMARY) Average time (in milliseconds) a beanActivate call takes, including the time at the database, if any. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium no con undef undef set by coll graph msec no con undef undef set by coll graph number of activations no con undef undef set by coll graph number of activations no con undef undef set by coll graph number of objects no con undef undef set by coll graph number of invocations
Appendix B
Parameter Reference
293
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanCreates (PMW_EJB_SUMMARY) Displays the number of instances of the bean that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanCreateRate (PMW_EJB_SUMMARY) Displays the number of instances of the bean that were created per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanCreateTime (PMW_EJB_SUMMARY) Displays the average elapsed time required to execute the bean's create method during the collection interval, including load time (if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeanDestroys (PMW_EJB_SUMMARY) Displays the number of instances of the bean that were destroyed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanDestroyRate (PMW_EJB_SUMMARY) Displays the number of instances of the bean that were destroyed per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of calls
no
con
undef
undef
set by coll
graph
number of calls
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
294
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanInstantiates (PMW_EJB_SUMMARY) Displays the number of times that beans were instantiated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanInstantiateRate (PMW_EJB_SUMMARY) Displays the number of times that beans were instantiated per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanLoads (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that bean data was loaded from persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanLoadRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that bean data was loaded from persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanMethodCalls (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that methods were invoked. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
number of loads
no
con
undef
undef
set by coll
graph
number of loads
yes
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
295
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanMethodCallsPerSec (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that methods were invoked. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max BeanMethodCallRate (PMW_EJB_SUMMARY) Displays the rate at which methods were invoked during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max BeanMethodRT (PMW_EJB_SUMMARY) Displays the average elapsed time during the collection interval required to execute the method, including load time (if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanPassivates (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that instances of the bean were passivated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanPassivatesRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that instances of the bean were passivated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
yes
con
undef
undef
set by coll
graph
number of invocations per second
yes
con
undef
undef
set by coll
graph
invocations per minute
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
296
Units
Type
Icon
Core Parameters
Table 22
Active?
BeanPassivateTime (PMW_EJB_SUMMARY) Average time (in millisecodns) a beanPassivate call takes , including the time at the database, if any. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium BeanPoolSize (PMW_EJB_SUMMARY) Displays the average number of available connections in the connection pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanRemoves (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that the bean's remove method was called. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanRemoveRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that the bean's remove method was called. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanRemoveTime (PMW_EJB_SUMMARY) Displays the average elapsed time required to execute the bean's remove method during the collection interval (including database access time if any). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of beans
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
297
Units
Type
Icon
Core Parameters
Table 22
Active?
BeansActive (PMW_EJB_SUMMARY) Displays the average number of ready beans. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeansLive (PMW_EJB_SUMMARY) Displays the number of concurrently live beans. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high BeanStores (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that bean data was moved to persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low BeanStoresRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that bean data was moved to persistent storage. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low DrainsFromPool (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that WebSphere found the connection pool was idle and attempted to drain unneeded connections. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
yes
con
undef
undef
set by coll
graph
number of times ready
no
con
undef
undef
set by coll
graph
number of times existing
no
con
undef
undef
set by coll
graph
number of writes
no
con
undef
undef
set by coll
graph
number of writes
no
con
undef
undef
set by coll
graph
number of times
298
Units
Type
Icon
Core Parameters
Table 22
Active?
DrainsFromPoolRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that WebSphere found the connection pool was idle and attempted to drain unneeded connections. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFound (PMW_EJB_SUMMARY) Displays the number of get requests processed during the collection interval that found the requested object in the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFoundRate (PMW_EJB_SUMMARY) Displays the number of get requests per second processed during the collection interval that found the requested object in the object pool. Collector: PerfCollector2 WebSphere version: all supported versions GetsFromPool (PMW_EJB_SUMMARY) Displays the number of get requests for objects in the object pool that were processed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low GetsFromPoolRate (PMW_EJB_SUMMARY) Displays the number of get requests per second for objects in the object pool that were processed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
no
con
undef
undef
set by coll
graph
number of times
Appendix B
Parameter Reference
299
Units
Type
Icon
Core Parameters
Table 22
Active?
MsgsBackedOut (PMW_EJB_SUMMARY) Number of messages that failed to be delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsBackedOutRate (PMW_EJB_SUMMARY) Number of messages per second that failed to be delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsDelivered (PMW_EJB_SUMMARY) Number of messages delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low MsgsDeliveredRate (PMW_EJB_SUMMARY) Number of messages per second delivered to the bean onMessage method (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsDiscarded (PMW_EJB_SUMMARY) Displays the number of times during the collection interval that objects that had been returned to the object pool were discarded from the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
yes
con
undef
undef
set by coll
graph
300
Units
Type
Icon
Core Parameters
Table 22
Active?
ReturnsDiscardedRate (PMW_EJB_SUMMARY) Displays the number of times per second during the collection interval that objects that had been returned to the object pool were discarded from the object pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsToPool (PMW_EJB_SUMMARY) Displays the number of objects that were returned to the object pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low ReturnsToPoolRate (PMW_EJB_SUMMARY) Displays the number of objects per second that were returned to the object pool during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low SvrSessionUtilization (PMW_EJB_SUMMARY) Percentage of server session pool in use (message driven). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high SvrSessionWait (PMW_EJB_SUMMARY) Average time to obtain a ServerSession from the pool (message driven bean). Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
percent
no
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
301
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_EJB_TRANSACTION application class

ActiveGlobalTrans (PMW_EJB_TRANSACTION) Displays the average number of concurrent active global transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended ActiveLocalTrans (PMW_EJB_TRANSACTION) Displays the average concurrent active local transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended GlobalBeforeCompletionDuration (PMW_EJB_TRANSACTION) Displays the average duration for before-completion for global transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: custom GlobalCommitDuration (PMW_EJB_TRANSACTION) Displays the average duration for commit for global transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic no con undef undef set by coll graph msec no con undef undef set by coll graph msec no con undef undef set by coll graph number of transaction no con undef undef set by coll graph number of transaction
302
Units
Type
Icon
Core Parameters
Table 22
Active?
GlobalPrepareDuration (PMW_EJB_TRANSACTION) Displays the average duration for commit for global transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic GlobalTransBegun (PMW_EJB_TRANSACTION) Displays the number of global transactions that were started during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransBegunRate (PMW_EJB_TRANSACTION) Displays the number of global transactions that were started per minute during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransCommitted (PMW_EJB_TRANSACTION) Displays the number of global transactions that were committed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransCommittedRate (PMW_EJB_TRANSACTION) Displays the number of global transactions that were committed per minute during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of transaction
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
303
Units
Type
Icon
Core Parameters
Table 22
Active?
GlobalTransDuration (PMW_EJB_TRANSACTION) Displays the average duration of global transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic GlobalTransInvolved (PMW_EJB_TRANSACTION) Displays the total number of global transactions begun and imported. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransInvolvedRate (PMW_EJB_TRANSACTION) Displays the total number of global transactions per minute begun and imported. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransRolledBack (PMW_EJB_TRANSACTION) Displays the total number of global transactions rolled back. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransRolledBackRate (PMW_EJB_TRANSACTION) Displays the total number of global transactions rolled back per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
304
Units
Type
Icon
Core Parameters
Table 22
Active?
GlobalTransTimeout (PMW_EJB_TRANSACTION) Displays total number of global transactions that timed out. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GlobalTransTimeoutRate (PMW_EJB_TRANSACTION) Displays total number of global transactions that timed out per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalBeforeCompletionDuration (PMW_EJB_TRANSACTION) Displays the average duration for before-completion for local transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
msec
LocalCommitDuration (PMW_EJB_TRANSACTION) no Displays the average duration for commit for local transactions. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic LocalTransBegun (PMW_EJB_TRANSACTION) Displays the number of local transactions that were started during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no
con
undef
undef
set by coll
graph
msec
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
305
Units
Type
Icon
Core Parameters
Table 22
Active?
LocalTransBegunRate (PMW_EJB_TRANSACTION) Displays the number of local transactions per minute that were started during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalTransCommitted (PMW_EJB_TRANSACTION) Displays the number of local transactions that were committed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalTransCommittedRate (PMW_EJB_TRANSACTION) Displays the number of local transactions per minute that were committed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalTransDuration (PMW_EJB_TRANSACTION) Displays the average duration of local transactions during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
msec
LocalTransRolledBack (PMW_EJB_TRANSACTION) yes Displays the total number of local transactions rolled back during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
con
undef
undef
set by coll
graph
306
Units
Type
Icon
Core Parameters
Table 22
Active?
LocalTransRolledBackRate (PMW_EJB_TRANSACTION) Displays the total number of local transactions per minute rolled back during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalTransTimeout (PMW_EJB_TRANSACTION) Displays the number of local transactions timed out during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LocalTransTimeoutRate (PMW_EJB_TRANSACTION) Displays the number of local transactions timed out per minute during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom Optimizations (PMW_EJB_TRANSACTION) Displays the number of global transactions converted to single phase for optimization. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom OptimizationRate (PMW_EJB_TRANSACTION) Displays the number of global transactions converted per minute to single phase for optimization. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
yes
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
307
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_ENVIRONMENT application class

Messages (PMW_ENVIRONMENT) Environment discovery messages. Collector: PerfCollector WebSphere version: all supported versions PerfCollector (PMW_ENVIRONMENT) Retrieves performance and transaction data for application performance monitoring. WebSphere version: all supported versions BCICollector (PMW_ENVIRONMENT) Retrieves transaction data for application performance monitoring. WebSphere version: all supported versions yes coll undef undef 31 sec NA none yes coll undef undef 60 sec NA none no con undef undef set by coll text none
PMW_HA_MANAGER application class

LocalGroups (PMW_HA_MANAGER) Total number of local groups. Collector: PerfCollector2 WebSphere version: 6.x LocalSubject (PMW_HA_MANAGER) Total number of subjects being posted locally. The number includes proxy postings (if any) done by the core group bridge service on behalf of servers belonging to different WebSphere cells. Collector: PerfCollector2 WebSphere version: 6.x LocalSubscription (PMW_HA_MANAGER) Total number of bulletin-board subscriptions. Collector: PerfCollector2 WebSphere version: 6.x no con undef undef set by coll graph number of subs. no con undef undef set by coll graph number of subjects no con undef undef set by coll graph number of groups
308
Units
Type
Icon
Core Parameters
Table 22
Active?
RebuildManagedTime (PMW_HA_MANAGER) Time to rebuild the global state of the bulletin board. During this time, no messages will be received by subscribers. If this time is too high, increase the number of coordinators. For this counter to operate correctly, you must host the active coordinator on an application server other than the deployment manager. Collector: PerfCollector2 WebSphere version: 6.x RebuildTime (PMW_HA_MANAGER) Time to rebuild the global group state. During the rebuild, no fail-over can happen. If this time is too high, increase the number of coordinators. For this counter to operate correctly, you must host the active coordinator on an application server other than the deployment manager. Collector: PerfCollector2 WebSphere version: 6.x SubjectManaged (PMW_HA_MANAGER) Total number of subjects managed. Collector: PerfCollector2 WebSphere version: 6.x SubscriptionManaged (PMW_HA_MANAGER) Total number of subscriptions managed. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of subjects
no
con
undef
undef
set by coll
graph
number of subs.
PMW_HA_SUMMARY application class

LocalGroups (PMW_HA_SUMMARY) Total number of local groups. Collector: PerfCollector2 WebSphere version: 6.x no con undef undef set by coll graph number of groups
Appendix B
Parameter Reference
309
Units
Type
Icon
Core Parameters
Table 22
Active?
LocalSubject (PMW_HA_SUMMARY) Total number of subjects being posted locally. The number includes proxy postings (if any) done by the core group bridge service on behalf of servers belonging to different WebSphere cells. Collector: PerfCollector2 WebSphere version: 6.x LocalSubscription (PMW_HA_SUMMARY) Total number of bulletin-board subscriptions. Collector: PerfCollector2 WebSphere version: 6.x RebuildManagedTime (PMW_HA_SUMMARY) Time to rebuild the global state of the bulletin board. During this time, no messages will be received by subscribers. If this time is too high, increase the number of coordinators. For this counter to operate correctly, you must host the active coordinator on an application server other than the deployment manager. Collector: PerfCollector2 WebSphere version: 6.x RebuildTime (PMW_HA_SUMMARY) Time to rebuild the global group state. During the rebuild, no fail-over can happen. If this time is too high, increase the number of coordinators. For this counter to operate correctly, you must host the active coordinator on an application server other than the deployment manager. Collector: PerfCollector2 WebSphere version: 6.x SubjectManaged (PMW_HA_SUMMARY) Total number of subjects managed. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number of subjects
no
con
undef
undef
set by coll
graph
number of subs.
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of subjects
310
Units
Type
Icon
Core Parameters
Table 22
Active?
SubscriptionManaged (PMW_HA_SUMMARY) Total number of subscriptions managed. Collector: PerfCollector2 WebSphere version: 6.x
no
con
undef
undef
set by coll
graph
number of subs.
PMW_J2C_FACTORY application class

AvgHeldTime (PMW_J2C_FACTORY) Average time in milliseconds that connections are in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic AvgWaitTime (PMW_J2C_FACTORY) Average waiting time in milliseconds until a connection is granted. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: custom ConnectionFaults (PMW_J2C_FACTORY) Number of faults, such as timeouts, in the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionFaultRate (PMW_J2C_FACTORY) Number of faults per second, such as timeouts, in the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom yes con undef undef set by coll graph number no con undef undef set by coll graph number yes con undef undef set by coll graph msec no con undef undef set by coll graph msec
Appendix B
Parameter Reference
311
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionsAllocated (PMW_J2C_FACTORY) Total number of connections allocated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsAllocatedRate (PMW_J2C_FACTORY) Number of connections allocated per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsCreated (PMW_J2C_FACTORY) Total number of connections created. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsCreatedRate (PMW_J2C_FACTORY) Total number of connections created per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsDestroyed (PMW_J2C_FACTORY) Total number of connections destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
312
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionsDestroyedRate (PMW_J2C_FACTORY) Total number of connections destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsFreed (PMW_J2C_FACTORY) Total number of connections freed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsFreedRate (PMW_J2C_FACTORY) Total number of connections freed per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsInUse (PMW_J2C_FACTORY) Total number of connection objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionWaiters (PMW_J2C_FACTORY) Average number of threads concurrently waiting for a connection. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
313
Units
Type
Icon
Core Parameters
Table 22
Active?
FreeConnections (PMW_J2C_FACTORY) Number of free connections in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended ManagedConnectionsInUse (PMW_J2C_FACTORY) Number of managed connection objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom PercentMaxed (PMW_J2C_FACTORY) Average percentage of the time that all connections are in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: basic PercentUsed (PMW_J2C_FACTORY) Average percentage of the pool that is currently in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: exnteded PoolSize (PMW_J2C_FACTORY) Pool size; the total number of connections in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
percent
yes
con
undef
undef
set by coll
graph
percent
no
con
undef
undef
set by coll
graph
number
314
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_J2C_SUMMARY application class

AvgHeldTime (PMW_J2C_SUMMARY) Average time in milliseconds that connections are in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic AvgWaitTime (PMW_J2C_SUMMARY) Average waiting time in milliseconds until a connection is granted. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ConnectionFaults (PMW_J2C_SUMMARY) Number of faults, such as timeouts, in the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionFaultsRate (PMW_J2C_SUMMARY) Number of faults per second, such as timeouts, in the connection pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsAllocated (PMW_J2C_SUMMARY) Total number of connections allocated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number yes con undef undef set by coll graph number no con undef undef set by coll graph number yes con undef undef set by coll graph msec no con undef undef set by coll graph msec
Appendix B
Parameter Reference
315
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionsAllocatedRate (PMW_J2C_SUMMARY) Number of connections allocated per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsCreated (PMW_J2C_SUMMARY) Total number of connections created. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsCreatedRate (PMW_J2C_SUMMARY) Total number of connections created per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsDestroyed (PMW_J2C_SUMMARY) Total number of connections destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
ConnectionsDestroyedRate (PMW_J2C_SUMMARY) no Total number of connections destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
con
undef
undef
set by coll
graph
number
316
Units
Type
Icon
Core Parameters
Table 22
Active?
ConnectionsFreed (PMW_J2C_SUMMARY) Total number of connections freed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsFreedRate (PMW_J2C_SUMMARY) Total number of connections freed per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionsInUse (PMW_J2C_SUMMARY) Total number of connection objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ConnectionWaiters (PMW_J2C_SUMMARY) Average number of threads concurrently waiting for a connection. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended FreeConnections (PMW_J2C_SUMMARY) Number of free connections in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
317
Units
Type
Icon
Core Parameters
Table 22
Active?
ManagedConnectionInUse (PMW_J2C_SUMMARY) Number of managed connection objects in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom PercentMaxed (PMW_J2C_SUMMARY) Average percentage of the time that all connections are in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: basic PercentUsed (PMW_J2C_SUMMARY) Average percentage of the pool that is currently in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended PoolSize (PMW_J2C_SUMMARY) Pool size; the total number of connections in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
percent
yes
con
undef
undef
set by coll
graph
percent
no
con
undef
undef
set by coll
graph
number
PMW_J2EE_OBJ application class

EJBRequestRate (PMW_J2EE_OBJ) Displays the rate at which EJB methods are invoked (number per minute). Collector: PerfCollector WebSphere version: all supported versions yes con undef undef set by coll graph number per minute
318
Units
Type
Icon
Core Parameters
Table 22
Active?
EJBResponseReport (PMW_J2EE_OBJ) Generates a text report showing response time details. Collector: PerfCollector WebSphere version: all supported versions EJBResponseTime (PMW_J2EE_OBJ) Displays the average response time for EJB methods. Collector: PerfCollector WebSphere version: all supported versions ServletRequestRate (PMW_J2EE_OBJ) Displays the rate at which servlet methods are invoked (number of invocations per minute). Collector: PerfCollector WebSphere version: all supported versions ServletResponseReport (PMW_J2EE_OBJ) Displays a report showing response time details. Collector: PerfCollector WebSphere version: all supported versions ServletResponseTime (PMW_J2EE_OBJ) Displays the average response time for servlet methods. Collector: PerfCollector WebSphere version: all supported versions SQLDeleteReqRate (PMW_J2EE_OBJ) Displays the rate at which SQL DELETE requests are issued. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLDeleteRespTime (PMW_J2EE_OBJ) Displays the average response time for SQL DELETE statements. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions
yes
con
undef
undef
set by coll
text
n/a
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number per minute
yes
con
undef
undef
set by coll
text
n/a
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number per minute
no
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
319
Units
Type
Icon
Core Parameters
Table 22
Active?
SQLInsertReqRate (PMW_J2EE_OBJ) Displays the rate at which SQL INSERT statements are issued. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLInsertRespTime (PMW_J2EE_OBJ) Displays the average response time for SQL INSERT statements. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLSelectReqRate (PMW_J2EE_OBJ) Displays the rate at which SQL SELECT statements are issued. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLSelectRespTime (PMW_J2EE_OBJ) Displays the average response time for SQL SELECT statements. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLUpdateReqRate (PMW_J2EE_OBJ) Displays the rate at which SQL UPDATE statements are issued. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions SQLUpdateRespTime (PMW_J2EE_OBJ) Displays the average response time for SQL UPDATE statements. Requires bytecode instrumentation. Collector: BCICollector WebSphere version: all supported versions
no
con
undef
undef
set by coll
graph
number per minute
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number per minute
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number per minute
no
con
undef
undef
set by coll
graph
msec
320
Units
Type
Icon
Core Parameters
Table 22
Active?
TransactionLongCount (PMW_J2EE_OBJ) Displays the number of transactions exceeding a user-specified threshold for transaction elapsed time. This parameter is generated by IBM Request Metrics or BMC ByteCode Instrumentation. If this parameter is generated by IBM Request Metrics, monitoring of request metrics must be enabled. Collector: BCICollector/PerfCollector (Request Metrics) WebSphere version: all supported versions TransactionMaximum (PMW_J2EE_OBJ) Maximum transaction time used by a transaction that exceeded the user-specified threshold for elapsed transaction duration.This parameter is generated by IBM Request Metrics or BMC ByteCode Instrumentation. If this parameter is generated by IBM Request Metrics, monitoring of request metrics must be enabled. Collector: BCICollector/PerfCollector (Request Metrics) WebSphere version: all supported versions TxDetailCollector (PMW_J2EE_OBJ) Retrieves data for viewing the transactions for application monitoring. WebSphere version: all supported versions TransactionReport (PMW_J2EE_OBJ) Generates a report showing details about the longest-running transactions. This parameter requires monitoring of request metrics to be enabled. Collector: PerfCollector (Request Metrics) WebSphere version: all supported versions
no
con
undef
undef
set by coll
graph
number of transactions
no
con
undef
undef
set by coll
graph
msec
yes
coll
undef
undef
23 sec
NA
none
no
con
undef
undef
set by coll
text
n/a
PMW_LOG application class

LogFileSize (PMW_LOG) Displays the size (in KB) of the log file at the most recent collection interval. Collector: LogSizeCollector WebSphere version: all supported versions yes con undef undef set by coll gauge kilobytes
Appendix B
Parameter Reference
321
Units
Type
Icon
Core Parameters
Table 22
Active?
LogGrowthSize(PMW_LOG) Displays the number of KB by which the log file grew during the collection interval. Collector: LogSizeCollector WebSphere version: all supported versions LogMessages (PMW_LOG) Displays the number of log messages that matched patterns being scanned for by the log monitor during the collection interval. Collector: LogMonitorCollector WebSphere version: all supported versions LogMonitorCollector (PMW_LOG) Periodically scans the log looking for matching patterns. Collector: not applicable WebSphere version: all supported versions LogMonitorStatus (PMW_LOG) Indicates the results of log monitoring during the collection interval: OKno matching warning or error or alarm messages were found (0), matching messages were found that triggered warnings (1), errors (2), or alarms (3). Collector: LogMonitorCollector WebSphere version: all supported versions LogSizeCollector (PMW_LOG) Periodically records the log files size and calculates its growth Collector: not applicable WebSphere version: all supported versions
yes
con
100 to 500
501 to 999999 99
set by coll
graph
kilobytes
no
con
100 to 800
800 to 999999
set by coll
graph
number of messages
yes
coll
NA
NA
300 sec NA
none
no
con
set by coll
stop light
none
yes
coll
NA
NA
10 min NA (600 sec)
none
PMW_MAIN application class

AppServerCollector (PMW_MAIN) Collects information about the application server and administration server. Collector: not applicable WebSphere version: all supported versions yes coll NA NA 1 min (60 sec) NA none
322
Units
Type
Icon
Core Parameters
Table 22
Active?
MessageCollector (PMW_MAIN) Collects information about JRAS messages. Collector: not applicable WebSphere version: all supported versions PostProcess (PMW_MAIN) Handles a number of internal processes This parameter displays no user information and should not be modified in any way. Collector: not applicable WebSphere version: all supported versions ServerTransportCol (PMW_MAIN) Determines the state of the HTTP transport connection. Collector: not applicable WebSphere version: all supported versions
yes
coll
NA
NA
1 min (60 sec)
NA
none
yes
std
NA
NA
10 min none (600 sec)
none
yes
coll
NA
NA
6 min (480 sec)
NA
none
PMW_NODE application class

JMSServerAvailability (PMW_NODE) Indicates whether the JMS Server is up and reachable. Collector: PerfCollector2 WebSphere version: all supported versions NodeAgentAvailability (PMW_NODE) Displays whether the node agent is available. Collector: PerfCollector2 WebSphere version: all supported versions yes con 1 to 1 1 to 1 alarm set by coll state bool. 0=running 1=stopped yes con 0-0 OK 1 to 1 alarm set by coll state bool. 0=running 1=stopped
PMW_OBJECT_POOL application class

IdlePoolSize (PMW_OBJECT_POOL) Displays the average number of idle object instances in this object pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x yes con undef undef set by coll graph number of objects
Appendix B
Parameter Reference
323
Units
Type
Icon
Core Parameters
Table 22
Active?
ObjectAllocated (PMW_OBJECT_POOL) Displays the average number of objects requested from the pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x ObjectCreated (PMW_OBJECT_POOL) Displays the number of objects created in the pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x ObjectReturned (PMW_OBJECT_POOL) Displays the average number of objects returned to the pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x
yes
con
undef
undef
set by coll
graph
number of objects
yes
con
undef
undef
set by coll
graph
number of objects
yes
con
undef
undef
set by coll
graph
number of objects
PMW_OBJECT_SUMMARY application class

IdlePoolSize (PMW_OBJECT_SUMMARY) Displays the average number of idle object instances across all pools. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x ObjectAllocated (PMW_OBJECT_SUMMARY) Displays the total number of objects requested from any pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x ObjectCreated (PMW_OBJECT_SUMMARY) Displays the total number of objects created in any pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x yes con undef undef set by coll graph number of objects yes con undef undef set by coll graph number of objects yes con undef undef set by coll graph number of objects
324
Units
Type
Icon
Core Parameters
Table 22
Active?
ObjectReturned (PMW_OBJECT_SUMMARY) Displays the total number of objects returned to any pool. Collector: PerfCollector (ENVIRONMENT) WebSphere version: 6.x
yes
con
undef
undef
set by coll
graph
number of objects
PMW_ORB_INTERCEPTOR application class

ORBInterceptTime (PMW_ORB_INTERCEPTOR) Time (in milliseconds) it takes a registered portable interceptor to run. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic yes con undef undef set by coll graph msec
PMW_ORB_SUMMARY application class

ObjectLookupTime (PMW_ORB_SUMMARY) Time (in milliseconds) to look up an object reference before method dispatch can be carried out. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ORBInterceptTime (PMW_ORB_SUMMARY) Time (in milliseconds) it takes a registered portable interceptor to run. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ORBRequestRate (PMW_ORB_SUMMARY) Total number of requests sent to the ORB per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom yes con undef undef set by coll graph number yes con undef undef set by coll graph msec yes con undef undef set by coll graph msec
Appendix B
Parameter Reference
325
Units
Type
Icon
Core Parameters
Table 22
Active?
ORBRequests (PMW_ORB_SUMMARY) Total number of requests sent to the ORB. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ORBRequestsActive (PMW_ORB_SUMMARY) Number of requests that are concurrently processed by the ORB. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
PMW_PROF_CLASS application class

PjsClassMethodDiscCol (PMW_PROF_CLASS) Invokes a collector for a given Java class selected for profiling. Collector: not applicable WebSphere version: all supported versions yes, prof coll NA NA 2 min (120 sec) NA none
PMW_PROF_METHOD application class

MethodCalls (PMW_PROF_METHOD) Displays the number of methods invoked in the specified Java class during the collection cycle. Collector: PMW_PROF_METHOD/PjsClassMethodDiscCol WebSphere version: all supported versions MethodCallsPerSec (PMW_PROF_METHOD) Displays the number of methods invoked per second in the specified Java class during the collection cycle. Collector: PMW_PROF_METHOD/PjsClassMethodDiscCol WebSphere version: all supported versions no, prof con undef undef set by coll graph invocations per sec no, prof con undef undef set by coll graph number of invocations
326
Units
Type
Icon
Core Parameters
Table 22
Active?
MethodCpu (PMW_PROF_METHOD) Displays the CPU consumption of methods invoked in the profiled Java class during the collection cycle. Collector: PMW_PROF_METHOD/PjsClassMethodDiscCol WebSphere version: all supported versions MethodRT (PMW_PROF_METHOD) Displays the average response time in milliseconds that it took for methods to execute in the profiled Java class during the collection cycle. Collector: PMW_PROF_METHOD/PjsClassMethodDiscCol WebSphere version: all supported versions
no, prof
con
undef
undef
set by coll
graph
KB
no, prof
con
undef
undef
set by coll
graph
msec
PMW_RAS_MESSAGES application class

AuditMsgCount (PMW_RAS_MESSAGES) Number of audit messages logged. Collector: PerfCollector WebSphere version: all supported versions ErrorMsgCount (PMW_RAS_MESSAGES) Number of error messages logged. Collector: PerfCollector WebSphere version: all supported versions FatalMsgCount (PMW_RAS_MESSAGES) Number of fatal messages logged. Collector: PerfCollector WebSphere version: all supported versions InfoMsgCount (PMW_RAS_MESSAGES) Number of informational messages logged. Collector: PerfCollector WebSphere version: all supported versions no con inact. by def. inact. by def. set by coll graph number no con 1 - 500 500 500 set by coll graph number no con 1 to 500 500 500 set by coll graph number no con undef undef set by coll graph number
Appendix B
Parameter Reference
327
Units
Type
Icon
Core Parameters
Table 22
Active?
ServiceMsgCount (PMW_RAS_MESSAGES) Number of service messages logged. Collector: PerfCollector WebSphere version: all supported versions WarningMsgCount (PMW_RAS_MESSAGES) Number of warning messages logged. Collector: PerfCollector WebSphere version: all supported versions
no
con
inact. by def.
inact. by def.
set by coll
graph
number
no
con
1 - 500
500 500
set by coll
graph
number
PMW_SCHEDULER application class

FailedTasks (PMW_SCHEDULER) Displays the number of tasks that failed to execute. Collector: PerfCollector2 WebSphere version: 6.x PollDuration (PMW_SCHEDULER) Displays the number of seconds between poll cycles. Collector: PerfCollector2 WebSphere version: 6.x PollQueryDuration (PMW_SCHEDULER) Displays the execution time for each poll daemon threads database poll query. Collector: PerfCollector2 WebSphere version: 6.x RunDuration (PMW_SCHEDULER) Displays the time needed to execute a task. Collector: PerfCollector2 WebSphere version: 6.x TaskCollisionRate (PMW_SCHEDULER) Displays the number of collisions encountered per second between competing poll daemons. Collector: PerfCollector2 WebSphere version: 6.x yes con undef undef set by coll graph number of collisions yes con undef undef set by coll graph msec yes con undef undef set by coll graph msec yes con undef undef set by coll graph seconds yes con undef undef set by coll graph number of tasks
328
Units
Type
Icon
Core Parameters
Table 22
Active?
TaskDelayDuration (PMW_SCHEDULER) Displays the period of time that the task is delayed. Collector: PerfCollector2 WebSphere version: 6.x TaskExpirationRate (PMW_SCHEDULER) Displays number of tasks in a poll query. Collector: PerfCollector2 WebSphere version: 6.x TaskFinish (PMW_SCHEDULER) Displays the number of tasks executed successfully. Collector: PerfCollector2 WebSphere version: 6.x TasksFinishRate (PMW_SCHEDULER) Displays the number of tasks executed per second. Collector: PerfCollector2 WebSphere version: 6.x TaskRunRate (PMW_SCHEDULER) Displays the number of tasks executed by each poll daemon thread. Collector: PerfCollector2 WebSphere version: 6.x TotalPolls (PMW_SCHEDULER) Displays the number of poll cycles completed for all daemon threads. Collector: PerfCollector2 WebSphere version: 6.x
yes
con
undef
undef
set by coll
graph
seconds
yes
con
undef
undef
set by coll
graph
number of tasks
yes
con
undef
undef
set by coll
graph
number of tasks
yes
con
undef
undef
set by coll
graph
number of tasks per second
yes
con
undef
undef
set by coll
graph
number of tasks
yes
con
undef
undef
set by coll
graph
number of cycles
PMW_SCHEDULER_SUMMARY application class

FailedTasks (PMW_SCHEDULER_SUMMARY) Displays the number of tasks that failed to execute. Collector: PerfCollector2 WebSphere version: 6.x yes con undef undef set by coll graph number of tasks
Appendix B
Parameter Reference
329
Units
Type
Icon
Core Parameters
Table 22
Active?
PollDuration (PMW_SCHEDULER_SUMMARY) Displays the number of seconds between poll cycles. Collector: PerfCollector2 WebSphere version: 6.x PollQueryDuration (PMW_SCHEDULER_SUMMARY) Displays the execution time for each poll daemon threads database poll query. Collector: PerfCollector2 WebSphere version: 6.x RunDuration (PMW_SCHEDULER_SUMMARY) Displays the time needed to execute a task. Collector: PerfCollector2 WebSphere version: 6.x TaskCollisionRate (PMW_SCHEDULER_SUMMARY) Displays the number of collisions encountered per second between competing poll daemons. Collector: PerfCollector2 WebSphere version: 6.x TaskDelayDuration (PMW_SCHEDULER_SUMMARY) Displays the period of time that the task is delayed. Collector: PerfCollector2 WebSphere version: 6.x TaskExpirationRate (PMW_SCHEDULER_SUMMARY) Displays number of tasks in a poll query. Collector: PerfCollector2 WebSphere version: 6.x TaskFinish (PMW_SCHEDULER_SUMMARY) Displays the number of tasks executed successfully. Collector: PerfCollector2 WebSphere version: 6.x
yes
con
undef
undef
set by coll
graph
seconds
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number of collisions
yes
con
undef
undef
set by coll
graph
seconds
yes
con
undef
undef
set by coll
graph
number of tasks
yes
con
undef
undef
set by coll
graph
number of tasks
330
Units
Type
Icon
Core Parameters
Table 22
Active?
TasksFinishRate (PMW_SCHEDULER_SUMMARY) Displays the number of tasks executed per second. Collector: PerfCollector2 WebSphere version: 6.x TaskRunRate (PMW_SCHEDULER_SUMMARY) Displays the number of tasks executed by each poll daemon thread. Collector: PerfCollector2 WebSphere version: 6.x TotalPolls (PMW_SCHEDULER_SUMMARY) Displays the number of poll cycles completed for all daemon threads. Collector: PerfCollector2 WebSphere version: 6.x
yes
con
undef
undef
set by coll
graph
number of tasks per second
yes
con
undef
undef
set by coll
graph
number of tasks
yes
con
undef
undef
set by coll
graph
number of cycles
PMW_SERVER_RESOURCES application class

ActiveThreads (PMW_SERVER_RESOURCE) Displays the average number of active threads in the pool. Collector: PerfCollector2 WebSphere version: all supported versions AllocatedHeaps (PMW_SERVER_RESOURCE) Displays the total amount of heap storage (both used and unused) allocated for objects at the end of the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions CpuPercent (PMW_SERVER_RESOURCE) Displays the percentage of CPU resources in use at the time of the latest collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions no, prof con undef undef set by coll graph percent no, prof con undef undef set by coll graph MB yes con undef undef set by coll graph number of threads
Appendix B
Parameter Reference
331
Units
Type
Icon
Core Parameters
Table 22
Active?
CpuUtilization (PMW_SERVER_RESOURCE) Displays the amount of CPU time (in seconds) consumed by the JVM during the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions FreeMemory (PMW_SERVER_RESOURCE) Displays the amount of free JVM memory at the end of the collection cycle. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom GarbageCollectionDuration (PMW_SERVER_RESOURCE) Displays the average amount of time (in seconds) spent to complete each garbage collection during the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version:5.x, 6.x WebSphere 5 PMI Level: max GarbageCollectionInterval (PMW_SERVER_RESOURCE) Displays the number of seconds between garbage collection calls over the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max GarbageCollectionObjectsInUsed (PMW_SERVER_RESOURCE) Displays the number of used objects in the heap during the most recent garbage collection. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions
no, prof
con
undef
undef
set by coll
graph
sec
yes
con
undef
undef
set by coll
graph
megabytes
no, prof
con
undef
undef
set by coll
graph
sec per invocation
no
con
undef
undef
set by coll
graph
sec
no, prof
con
undef
undef
set by coll
graph
number of objects
332
Units
Type
Icon
Core Parameters
Table 22
Active?
GarbageCollections (PMW_SERVER_RESOURCE) Displays the total number of garbage collections during the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max GarbageCollectionRate (PMW_SERVER_RESOURCE) Displays the number of garbage collections per minute during the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max HeapsInUse (PMW_SERVER_RESOURCE) Displays the amount of heap storage allocated for objects that running JVM threads were still using at the end of the collection cycle. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions HighestCpuThread (PMW_SERVER_RESOURCE) Displays the highest CPU time (in seconds) used by one JVM thread in general. This CPU time might indicate that the thread was stuck. Collector: JVMCollector (Requires JVM profiling to be active) WebSphere version: all supported versions JVMCollector (PMW_SERVER_RESOURCE) Collects information to populate all Server Resource consumer parameters displaying profiler generated information Collector: JVMCollector
no, prof
con
undef
undef
set by coll
graph
number of collections
no, prof
con
undef
undef
set by coll
graph
number of collections
no, prof
con
undef
undef
set by coll
graph
MB
no, prof
con
undef
undef
set by coll
graph
sec
yes, prof
coll
NA
NA
301 sec n/a
none
Appendix B
Parameter Reference
333
Units
Type
Icon
Core Parameters
Table 22
Active?
LockWaits (PMW_SERVER_RESOURCE) Displays the number of times that a thread waited for a lock during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max LockWaitRate (PMW_SERVER_RESOURCE)
no, opt. conf.
con
undef
undef
set by coll
graph
number of threads waiting
no, opt. Displays the number of times per minute that a thread conf. waited for a lock during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max LockWaitTime (PMW_SERVER_RESOURCE) Displays the average time that a thread waited for a lock during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsAllocated (PMW_SERVER_RESOURCE) Displays the number of objects that were allocated during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsAllocatedRate (PMW_SERVER_RESOURCE) no, opt. Displays the number of objects that were allocated per conf. minute during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max no, opt. conf. no, opt. conf.
con
undef
undef
set by coll
graph
number of threads waiting
con
undef
undef
set by coll
graph
msec
con
undef
undef
set by coll
graph
number of objects
con
undef
undef
set by coll
graph
number of objects
334
Units
Type
Icon
Core Parameters
Table 22
Active?
ObjectsFreed (PMW_SERVER_RESOURCE)
no, opt. Displays the number of objects that were discontinued conf. and whose resources were reclaimed during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsFreedRate (PMW_SERVER_RESOURCE) no, opt. Displays the number of objects that were discontinued conf. per minute and whose resources were reclaimed during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsInUse (PMW_SERVER_RESOURCE) Displays the number of objects that are currently being used. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsMoved (PMW_SERVER_RESOURCE) Displays the number of objects that were moved within the heap during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max ObjectsMovedRate (PMW_SERVER_RESOURCE) Displays the number of objects that were moved per minute within the heap during the previous polling cycle. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions WebSphere 5 PMI Level: max no, opt. conf. no, opt. conf. no, opt. conf.
con
undef
undef
set by coll
graph
number of objects
con
undef
undef
set by coll
graph
number of objects
con
undef
undef
set by coll
graph
number of objects
con
undef
undef
set by coll
graph
number of objects
con
undef
undef
set by coll
graph
number of objects
Appendix B
Parameter Reference
335
Units
Type
Icon
Core Parameters
Table 22
Active?
PeakNTRealMemory (PMW_SERVER_RESOURCE) Displays the peak amount of real memory allocated by the JVM during the collection cycle (NT only). Collector: JVMCollector (Requires JVM profiling) WebSphere version: all supported versions PeakNTVirtualMemory (PMW_SERVER_RESOURCE) Displays the peak amount of virtual memory allocated by the JVM during the collection cycle (NT only). Collector: JVMCollector (Requires JVM profiling) WebSphere version: all supported versions
no, prof
con
undef
undef
set by coll
graph
bytes
no, prof
con
undef
undef
set by coll
graph
bytes
PercentMemoryUsed (PMW_SERVER_RESOURCES) yes Displays the used memory at the end of the collection cycle as a percentage of the maximum heap allowed for an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 6 PMI Level: custom VirtualMemory (PMW_SERVER_RESOURCE) Displays the total amount of virtual memory allocated by the JVM during the collection cycle. Collector: JVMCollector (Requires JVM profiling) WebSphere version: all supported versions ThreadCreates (PMW_SERVER_RESOURCE) Displays the number of threads that were created during the collection interval. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions ThreadCreateRate (PMW_SERVER_RESOURCE) Displays the number of threads that were created per minute during the collection interval. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions no no no, prof
con
80-90
90-100
set by coll
graph
percentage
con
undef
undef
set by coll
graph
MB
con
undef
undef
set by coll
graph
number of threads
con
undef
undef
set by coll
graph
number of threads
336
Units
Type
Icon
Core Parameters
Table 22
Active?
ThreadDestroys (PMW_SERVER_RESOURCES) Displays the number of threads that were destroyed during the collection interval. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions ThreadDestroyRate (PMW_SERVER_RESOURCES) Displays the number of threads that were destroyed per minute during the collection interval. Collector: PerfCollector2 (requires WebSphere Standard Profiling to be active) WebSphere version: all supported versions ThreadMaxSize (PMW_SERVER_RESOURCE) Displays the maximum configured size of the thread pool. This parameter is available only after thread object collection is activated. Collector: PerfCollector2 WebSphere version: all supported versions ThreadPercentMaxed (PMW_SERVER_RESOURCE) Displays the average percent of time during the collection cycle that threads reached the maximum limit. Collector: PerfCollector2 WebSphere version: all supported versions ThreadPoolSize (PMW_SERVER_RESOURCE) Displays the average number of threads in the pool. Collector: PerfCollector2 WebSphere version: all supported versions Threads (PMW_SERVER_RESOURCE) Displays the number of threads in the JVM. Collector: JVMCollector (Requires JVM profiling) WebSphere version: all supported versions
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
percent
yes
con
undef
undef
set by coll
graph
number of threads
no, prof
con
undef
undef
set by coll
graph
number of threads
Appendix B
Parameter Reference
337
Units
Type
Icon
Core Parameters
Table 22
Active?
ThreadsObjects (PMW_SERVER_RESOURCE) Displays the number of objects in use by JVM threads that were still running at the end of the collection cycle. This parameter is available only after thread object collection is activated. Collector: JVMCollector (Requires JVM profiling) WebSphere version: all supported versions TotalMemory (PMW_SERVER_RESOURCE) Displays the total amount of JVM memory. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: custom UpTime (PMW_SERVER_RESOURCE) Displays the amount of time that the JVM has been running. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom UsedMemory (PMW_SERVER_RESOURCE) Displays the amount of JVM memory that has been used. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no, prof
con
undef
undef
set by coll
graph
number of thread objects
yes
con
undef
undef
set by coll
graph
MB
no
con
undef
undef
set by coll
graph
sec
yes
con
undef
undef
set by coll
graph
megabytes
PMW_SERVLET application class

ServletConcurrentRequests (PMW_SERVLET) Displays the number of requests that were processed by the servlet during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended yes con undef undef set by coll graph number of requests
338
Units
Type
Icon
Core Parameters
Table 22
Active?
ServletErrors (PMW_SERVLET) Displays the number of servlet requests that encountered errors or exceptions during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletErrorRate (PMW_SERVLET) Displays the number of servlet requests per second that encountered errors or exceptions during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletLoadedSince (PMW_SERVLET) Displays the time that has elapsed (in milliseconds) since the servlet was loaded. Collector: PerfCollector WebSphere version: all supported versions ServletLoads (PMW_SERVLET) Number of servlets that were loaded. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletReloads (PMW_SERVLET) Number of servlets that were reloaded. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number of errors
yes
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
339
Units
Type
Icon
Core Parameters
Table 22
Active?
ServletRequestRate (PMW_SERVLET) Displays the rate at which servlet requests were processed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletRequestsPerSec (PMW_SERVLET) Displays the number of servlet requests per second that were processed during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletResponseTime (PMW_SERVLET) Displays the average elapsed time required to complete a servlet request during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ServletTotalRequests (PMW_SERVLET) Displays the number of requests that were processed by the servlet during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number of requests per minute
yes
con
undef
undef
set by coll
graph
number of requests per second
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
number of requests
PMW_SERVLET_ENGINE application class

ServerServletCollector (PMW_SERVLET_ENGINE) Collects data required to generate the Servlet Performance Report, showing statistic of up to the 30 worst performing servlets. Collector: not applicable WebSphere version: all supported versions yes, inst coll NA NA 10 min NA (600 sec) none
340
Units
Type
Icon
Core Parameters
Table 22
Active?
WebAppCollector (PMW_SERVLET_ENGINE) Collects data required to generate the WebApp Performance Report, showing statistic of up to the 30 worst performing Web applications. Collector: not applicable WebSphere version: all supported versions
yes, inst
coll
NA
NA
303 sec NA
none
PMW_SERVLET_GROUP application class

AvgRespTime (PMW_SERVLET_GROUP) Displays the average response time over all servlets and JSPs in the Web application during the collection cycle. Collector: PjsWebAppTopNCol WebSphere version: all supported versions HighCumulativeTime (PMW_SERVLET_GROUP) Displays the amount of time used by the servlet with the most accumulated run time during the collection cycle. Collector: PjsWebAppTopNCol WebSphere version: all supported versions HighUsed (PMW_SERVLET_GROUP) Displays the number of invocations for the most often called servlet or JSP during the collection cycle. Collector: PjsWebAppTopNCol WebSphere version: all supported versions HighUsedRate (PMW_SERVLET_GROUP) Displays the rate at which the most-used servlet or JSP was invoked. Collector: PjsWebAppTopNCol WebSphere version: all supported versions InvocationRate (PMW_SERVLET_GROUP) Displays the average invocation rate over all servlets and JSPs in the Web application during the collection cycle. Collector: PjsWebAppTopNCol WebSphere version: all supported versions no, inst con undef undef set by coll graph invocations per sec no, inst con undef undef set by coll graph times per second no, inst con undef undef set by coll graph invocations no, inst con undef undef set by coll graph msec no, inst con undef undef set by coll graph msec
Appendix B
Parameter Reference
341
Units
Type
Icon
Core Parameters
Table 22
Active?
PjsServletClassCol (PMW_SERVLET_GROUP) Collects data to generate the performance report of servlets within the Web application and to populated the PMW_SERVLET_METHOD parameters. WebSphere version: all supported versions PjsWebAppTopNCol (PMW_SERVLET_GROUP) Invokes three PJS collectors for the alternate servlet method across all Web applications based on the response time, number of invocations, and cumulative time, and calculates the rate of invocation. SelectedAliasesActive (PMW_SERVLET_GROUP) Displays the number of virtual hosts selected through the PMW_SERVLET_GROUP => Configure VHost Alias Ping List menu command that returned a successful ping during the most recent collection cycle. Collector: standard parameter, self collecting WebSphere version: all supported versions SlowestRespTime (PMW_SERVLET_GROUP) Displays the slowest response time of any servlet or JSP during the collection cycle Collector: PjsWebAppTopNCol WebSphere version: all supported versions TotalCumulativeTime (PMW_SERVLET_GROUP) Displays the total cumulative response time of all servlets and JSPs. Collector: PjsWebAppTopNCol WebSphere version: all supported versions TotalInvocations (PMW_SERVLET_GROUP) Displays the total number of invocations of servlets and JSPs in the Web application during the collection cycle. Collector: PjsWebAppTopNCol WebSphere version: all supported versions
yes, inst
coll
NA
NA
5 min (300 sec)
NA
none
yes, inst
coll
NA
NA
5 min (300 sec)
NA
none
no, inst
std
undef
undef
360 sec graph
number of active virtual host aliases
no, inst
con
3 mill.120 mill.
120 mill. 2.15 bill.
set by coll
graph
msec
no, inst
con
undef
undef
set by coll
graph
msec
no, inst
con
undef
undef
set by coll
graph
invocations
342
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_SERVLET_METHOD application class

MethodCalls (PMW_SERVLET_METHOD) Displays the number of times during the collection interval that the servlet method was invoked.This parameter requires bytecode instrumentation. Collector: PjsServletClassCol WebSphere version: all supported versions MethodCallsPerSec (PMW_SERVLET_METHOD) Displays the rate at which the servlet method was invoked during the collection interval. This parameter appears in the PATROL tree as a result of the calculations made on the MethodCalls parameter. This parameter requires bytecode instrumentation. Collector: PjsServletClassCol WebSphere version: all supported versions MethodRT (PMW_SERVLET_METHOD) Reports the average response time for all methods of the remote interface for this servlet. Collector: PjsServletClassCol WebSphere version: all supported versions no, inst con undef undef set by coll graph msec no, inst con undef undef set by coll graph invocations per sec no, inst con undef undef set by coll graph number of invocations
PMW_SERVLET_SUMMARY application class

ServletConcurrentRequests (PMW_SERVLET_SUMMARY) Displays the number of requests that were processed by the servlet during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ServletErrors (PMW_SERVLET_SUMMARY) Displays the number of servlet requests that encountered errors or exceptions during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom yes con undef undef set by coll graph number of errors yes con undef undef set by coll graph number of requests
Appendix B
Parameter Reference
343
Units
Type
Icon
Core Parameters
Table 22
Active?
ServletErrorRate (PMW_SERVLET_SUMMARY) Displays the number of servlet requests that encountered errors or exceptions per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletLoads (PMW_SERVLET_SUMMARY) Displays the current number of loaded servlets. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletReloads (PMW_SERVLET_SUMMARY) Displays the number of times that servlets were re-loaded during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ServletRequestRate (PMW_SERVLET_SUMMARY) Displays the rate at which servlet requests were processed during the collection interval. Collector: PerfCollector WebSphere version: all supported versions ServletRequestsPerSec (PMW_SERVLET_SUMMARY) Displays the number of servlet requests that were processed per second during the collection interval. Collector: PerfCollector WebSphere version: all supported versions
yes
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of reloads
no
con
undef
undef
set by coll
graph
number of requests per minute
no
con
undef
undef
set by coll
graph
number of requests per second
344
Units
Type
Icon
Core Parameters
Table 22
Active?
ServletResponseTime (PMW_SERVLET_SUMMARY) Displays the average elapsed time required to complete a servlet request during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
yes
con
undef
undef
set by coll
graph
msec
ServletTotalRequests (PMW_SERVLET_SUMMARY) yes Displays the number of requests that were processed by the servlet during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
con
undef
undef
set by coll
graph
number of requests
PMW_SESSIONS application class

ActiveSessions (PMW_SESSIONS) Displays the average number of sessions that were active (in use) during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended AffinityBreaks (PMW_SESSIONS) Number of requests received for sessions that were last accessed from another web application. This can indicate failover processing or a corrupt plug-in configuration. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number of requests no con undef undef set by coll graph number of sessions
Appendix B
Parameter Reference
345
Units
Type
Icon
Core Parameters
Table 22
Active?
AffinityBreakRate (PMW_SESSIONS) Number of requests received per second for sessions that were last accessed from another web application. This can indicate failover processing or a corrupt plug-in configuration. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom CacheDiscards (PMW_SESSIONS) Number of session objects that were forced out of the cache. (An LRU algorithm removes old entries to make room for new objects.) Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom CacheDiscardRate (PMW_SESSIONS) Number of session objects per second that were forced out of the cache. (An LRU algorithm removes old entries to make room for new objects.) Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ExternalReadSize (PMW_SESSIONS) Size of session data read from persistent store. Applicable only for (serialized) persistent sessions; similar to ExternalReadTime. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
no
con
undef
undef
set by coll
graph
number of requests
no
con
undef
undef
set by coll
graph
number of objects
no
con
undef
undef
set by coll
graph
number of objects
no
con
undef
undef
set by coll
graph
bytes
346
Units
Type
Icon
Core Parameters
Table 22
Active?
ExternalReadTime (PMW_SESSIONS) Time (in milliseconds) taken to read session data from persistent storage. For multirow sessions, the metrics are for the attribute; for single row, the metrics are for the whole session. Applicable only for persistent sessions and for serialized data. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ExternalWriteSize (PMW_SESSIONS) Size of session data written to persistent store. Applicable only for (serialized) persistent sessions; similar to ExternalReadTime. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ExternalWriteTime (PMW_SESSIONS) Time (in milliseconds) taken to write session data to persistent storage. For multirow sessions, the metrics are for the attribute; for single row, the metrics are for the whole session. Applicable only for persistent sessions and for serialized data. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic FinalizedSessions (PMW_SESSIONS) Displays the number of servlet sessions that were finalized during the collection interval. InvalidatedSessions (PMW_SESSIONS) Displays the number of sessions that were invalidated during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by col
graph
number
no
con
undef
undef
set by coll
graph
number of sessions
Appendix B
Parameter Reference
347
Units
Type
Icon
Core Parameters
Table 22
Active?
InvalidatedSessionRate (PMW_SESSIONS) Displays the number of sessions that were invalidated per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom InvalidatedSessionsPerSec (PMW_SESSIONS) Displays the number of sessions that were invalidated per second during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom InvReqNonExistent (PMW_SESSIONS) Number of requests for a session that no longer exists, presumably because the session timed out. Use this counter to help determine if the timeout is too short. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom InvReqNonExistentRate (PMW_SESSIONS) Number of requests per session for a session that no longer exists, presumably because the session timed out. Use this counter to help determine if the timeout is too short. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom InvReqTimeout (PMW_SESSIONS) Displays the number of requests for a session for which no CountStatistic exists, presumably because the session timed out. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number of sessions per minute
yes
con
undef
undef
set by coll
graph
number of sessions per sec
no
con
undef
undef
set by coll
graph
number of requests
no
con
undef
undef
set by coll
graph
number of requests
no
con
undef
undef
set by coll
graph
number of requests
348
Units
Type
Icon
Core Parameters
Table 22
Active?
InvReqTimeoutRate (PMW_SESSIONS) Number of requests for a session that no CountStatistic exists, presumably because the session timed out. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom LiveSessions (PMW_SESSIONS) Displays the average number of live client sessions during the collection interval. Collector: PerfCollector WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended MaxSessionsExceeded (PMW_SESSIONS) Number of times that a request for a new session can not be handled because it would exceed the maximum session count. Applies only to sessions in memory with AllowOverflow=false. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom MaxSessionsExceededRate (PMW_SESSIONS) Number of times per second that a request for a new session can not be handled because it would exceed the maximum session count. Applies only to sessions in memory with AllowOverflow=false. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number of requests
yes
con
undef
undef
set by coll
graph
number of sessions
no
con
undef
undef
set by coll
graph
number of requests
yes
con
undef
undef
set by coll
graph
number of requests
Appendix B
Parameter Reference
349
Units
Type
Icon
Core Parameters
Table 22
Active?
SerializableSessObjSize (PMW_SESSIONS) Size in bytes of the serializable attributes of in-memory sessions. Only count session objects that contain at least one serializable attribute object are reflected. Note: a session may contain both serializable and non-serializable attributes. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: max WebSphere 6 PMI Level: all SessionCreates (PMW_SESSIONS) Displays the number of sessions that were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SessionCreateRate (PMW_SESSIONS) Displays the rate at which clients sessions were created during the collection interval. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SessionLifetime (PMW_SESSIONS) Displays the average elapsed time between session creation and session invalidation during the collection interval. Collector: PerfCollector WebSphere version: all supported versions WebSphere 6 PMI Level: basic TimeSinceLastActivated (PMW_SESSIONS) Time difference between previous and current access time stamps. Does not include session timeout. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number of sessions
no
con
undef
undef
set by coll
graph
number of sessions per minute
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
msec
350
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_SIB_SERVICE application class

AssuredPersistMsgConsumed (PMW_SIB_SERVICE) no Number of assured persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 AssuredPersistMsgProduced (PMW_SIB_SERVICE) Number of assured persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 AvailableConsumedMessage (PMW_SIB_SERVICE) Number of messages waiting to be consumed. Collector: PerfCollector2 WebSphere version: 6 BestEffortNonPersistMsgConsume (PMW_SIB_SERVICE) Number of best effort non-persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 BestEffortNonPersistMsgProduce (PMW_SIB_SERVICE) Number of best effort non-persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ClientsConnectToServer (PMW_SIB_SERVICE) Number of distinct client processes currently connected through the network to this application server. Collector: PerfCollector2 WebSphere version: 6 no con undef undef set by coll graph number of processes no con undef undef set by coll graph number of messages no con undef undef set by coll graph number of messages no con undef undef set by coll graph number of messages no con undef undef set by coll graph number of messages con undef undef set by coll graph number of messages
Appendix B
Parameter Reference
351
Units
Type
Icon
Core Parameters
Table 22
Active?
CommunicationErrors (PMW_SIB_SERVICE) Number of communication errors that occurred and that resulted in a disconnected network connection to the messaging engine. Collector: PerfCollector2 WebSphere version: 6 ConnectionErrors (PMW_SIB_SERVICE) Number of communication errors that occurred and that resulted in a disconnected network connection to the client. Collector: PerfCollector2 WebSphere version: 6 ExpressNonPersistMsgConsumed (PMW_SIB_SERVICE) Number of express non-persistent messages consumed over the lifetime of the messaging engine. Collector: PerfCollector2 WebSphere version: 6 ExpressNonPersistMsgProduced (PMW_SIB_SERVICE) Number of express non-persistent messages produced over the lifetime of the messaging engine. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
HighestPriorityRecvdMsgSize (PMW_SIB_SERVICE) no Number of bytes of data received at the highest priority. Message data cannot be transmitted at highest priority, so this data comprises flow control transmissions. Collector: PerfCollector2 WebSphere version: 6
con
undef
undef
set by coll
graph
bytes
352
Units
Type
Icon
Core Parameters
Table 22
Active?
HighestPrioritySentMsgSize (PMW_SIB_SERVICE) Number of bytes of data sent at the highest priority. Message data cannot be transmitted at highest priority, so this data comprises flow control transmissions. Collector: PerfCollector2 WebSphere version: 6 IncompletedPublication (PMW_SIB_SERVICE) Number of publications not yet received by all current subscribers. If this number is suspect, use the Admin console to view publications and take any necessary action. Collector: PerfCollector2 WebSphere version: 6 IncompletedReads (PMW_SIB_SERVICE) Number of read operations that could not be immediately completed. This number reflects network congestion when communicating with client processes. Collector: PerfCollector2 WebSphere version: 6 IncompletedWrites (PMW_SIB_SERVICE) Number of write operations that could not be immediately completed. This number reflects network congestion when communicating with client processes. Collector: PerfCollector2 WebSphere version: 6 LowestPriorityRecvdMsgSize (PMW_SIB_SERVICE) Number of bytes received at lowest possible priority. This priority is not used for message traffic and typically reflects message flow control transmissions. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number of publications
no
con
undef
undef
set by coll
graph
number of operations
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
bytes
Appendix B
Parameter Reference
353
Units
Type
Icon
Core Parameters
Table 22
Active?
LowestPrioritySentMsgSize (PMW_SIB_SERVICE) Number of bytes sent at lowest possible priority. This priority is not used for message traffic and typically reflects message flow control transmissions. Collector: PerfCollector2 WebSphere version: 6 MediatedThread (PMW_SIB_SERVICE) Number of messages being concurrently mediated. Collector: PerfCollector2 WebSphere version: 6 MediationTime (PMW_SIB_SERVICE) Amount of time taken to mediate a message at a mediated destination. Collector: PerfCollector2 WebSphere version: 6 MessageEngineConnectToServer (PMW_SIB_SERVICE) Number of distinct application server processes hosting messaging engines currently connected to this application server via the network. Collector: PerfCollector2 WebSphere version: 6 ReliableNonPersistMsgConsumed (PMW_SIB_SERVICE) Number of reliable non-persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ReliableNonPersistMsgProduced (PMW_SIB_SERVICE) Number of reliable non-persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number of processes
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
354
Units
Type
Icon
Core Parameters
Table 22
Active?
ReliablePersistMsgConsumed (PMW_SIB_SERVICE) no Number of reliable persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ReliablePersistMsgProduced (PMW_SIB_SERVICE) Number of reliable persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 WMQQueueManagerConnectToServer (PMW_SIB_SERVICE) Total number of WebSphere MQ Queue Managers currently attached to this application server via the network. Collector: PerfCollector2 WebSphere version: 6 no no
con
undef
undef
set by coll
graph
number of messages
con
undef
undef
set by coll
graph
number of messages
con
undef
undef
set by coll
graph
number of queue managers
PMW_SIB_SUMMARY application class

AssuredPersistMsgConsumed (PMW_SIB_SUMMARY) Number of assured persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 AssuredPersistMsgProduced (PMW_SIB_SUMMARY) Number of assured persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 AvailableConsumedMessage (PMW_SIB_SUMMARY) Number of messages waiting to be consumed. Collector: PerfCollector2 WebSphere version: 6 no con undef undef set by coll graph number of messages no con undef undef set by coll graph number of messages no con undef undef set by coll graph number of messages
Appendix B
Parameter Reference
355
Units
Type
Icon
Core Parameters
Table 22
Active?
BestEffortNonPersistMsgConsume (PMW_SIB_SUMMARY) Number of best effort non-persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 BestEffortNonPersistMsgProduce (PMW_SIB_SUMMARY) Number of best effort non-persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ClientsConnectToServer (PMW_SIB_SUMMARY) Number of distinct client processes currently connected through the network to this application server. Collector: PerfCollector2 WebSphere version: 6 CommunicationErrors (PMW_SIB_SUMMARY) Number of communication errors that occurred and that resulted in a disconnected network connection to the messaging engine. Collector: PerfCollector2 WebSphere version: 6 ConnectionErrors (PMW_SIB_SUMMARY) Number of communication errors that occurred and that resulted in a disconnected network connection to the client. Collector: PerfCollector2 WebSphere version: 6 ExpressNonPersistMsgConsumed (PMW_SIB_SUMMARY) Number of express non-persistent messages consumed over the lifetime of the messaging engine. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of processes
no
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
number of errors
no
con
undef
undef
set by coll
graph
number of messages
356
Units
Type
Icon
Core Parameters
Table 22
Active?
ExpressNonPersistMsgProduced (PMW_SIB_SUMMARY) Number of express non-persistent messages produced over the lifetime of the messaging engine. Collector: PerfCollector2 WebSphere version: 6 HighestPriorityRecvdMsgSize (PMW_SIB_SUMMARY) Number of bytes of data received at the highest priority. Message data cannot be transmitted at highest priority, so this data comprises flow control transmissions. Collector: PerfCollector2 WebSphere version: 6 HighestPrioritySentMsgSize (PMW_SIB_SUMMARY) Number of bytes of data sent at the highest priority. Message data cannot be transmitted at highest priority, so this data comprises flow control transmissions. Collector: PerfCollector2 WebSphere version: 6 IncompletedPublication (PMW_SIB_SUMMARY) Number of publications not yet received by all current subscribers. If this number is suspect, use the Admin console to view publications and take any necessary action. Collector: PerfCollector2 WebSphere version: 6 IncompletedReads (PMW_SIB_SUMMARY) Number of read operations that could not be immediately completed. This number reflects network congestion when communicating with client processes. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number of publications
no
con
undef
undef
set by coll
graph
Appendix B
Parameter Reference
357
Units
Type
Icon
Core Parameters
Table 22
Active?
IncompletedWrites (PMW_SIB_SUMMARY) Number of write operations that could not be immediately completed. This number reflects network congestion when communicating with client processes. Collector: PerfCollector2 WebSphere version: 6 LowestPriorityRecvdMsgSize (PMW_SIB_SUMMARY) Number of bytes received at lowest possible priority. This priority is not used for message traffic and typically reflects message flow control transmissions. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
no
con
undef
undef
set by coll
graph
bytes
LowestPrioritySentMsgSize (PMW_SIB_SUMMARY) no Number of bytes sent at lowest possible priority. This priority is not used for message traffic and typically reflects message flow control transmissions. Collector: PerfCollector2 WebSphere version: 6 MediatedThread (PMW_SIB_SUMMARY) Number of messages being concurrently mediated. Collector: PerfCollector2 WebSphere version: 6 MediationTime (PMW_SIB_SUMMARY) Amount of time taken to mediate a message at a mediated destination. Collector: PerfCollector2 WebSphere version: 6 MessageEngineConnectToServer (PMW_SIB_SUMMARY) Number of distinct application server processes hosting messaging engines currently connected to this application server via the network. Collector: PerfCollector2 WebSphere version: 6 no no no
con
undef
undef
set by coll
graph
bytes
con
undef
undef
set by coll
graph
number of messages
con
undef
undef
set by coll
graph
msec
con
undef
undef
set by coll
graph
number of processes
358
Units
Type
Icon
Core Parameters
Table 22
Active?
ReliableNonPersistMsgConsumed (PMW_SIB_SUMMARY) Number of reliable non-persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ReliableNonPersistMsgProduced (PMW_SIB_SUMMARY) Number of reliable non-persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ReliablePersistMsgConsumed (PMW_SIB_SUMMARY) Number of reliable persistent messages consumed over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 ReliablePersistMsgProduced (PMW_SIB_SUMMARY) Number of reliable persistent messages produced over the lifetime of this messaging engine. Collector: PerfCollector2 WebSphere version: 6 WMQQueueManagerConnectToServer (PMW_SIB_SUMMARY) Total number of WebSphere MQ Queue Managers currently attached to this application server via the network. Collector: PerfCollector2 WebSphere version: 6
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of messages
no
con
undef
undef
set by coll
graph
number of queue managers
Appendix B
Parameter Reference
359
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_SQL application class

AvgResponseTime (PMW_SQL) Displays the average response time of invocations of the SQL statement during the collection cycle. Collector: SQLCollector WebSphere version: all supported versions InvocationRate (PMW_SQL) Displays the rate at which the SQL statement was invoked during the collection cycle. Collector: SQLCollector WebSphere version: all supported versions SQLCollector (PMW_SQL) Collects information about the SQL statement to populate the consumer parameters concerning this SQL statement and to populate reports that are generated about this SQL statement. Collector: not applicable WebSphere version: all supported versions TotalCumulativeTime (PMW_SQL) Displays the cumulative total elapsed time between invocation and completion for all invocations of this SQL statement during the collection cycle. Collector: SQLCollector WebSphere version: all supported versions TotalInvocations (PMW_SQL) Displays the total number of times this SQL statement was invoked during the collection cycle. Collector: SQLCollector WebSphere version: all supported versions no, inst con undef undef set by coll graph invocations no, inst con undef undef set by coll graph msec yes, inst coll NA NA 3 min (180 sec) NA none no, inst con undef undef set by coll graph invocations per sec no, inst con undef undef set by coll graph msec
360
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_THREADPOOL application class

ActiveThreads (PMW_THREADPOOL) Displays the number of concurrently active threads. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ActiveTime (PMW_THREADPOOL) Displays the average time that threads spent in an active state. Collector: PerfCollector2 WebSphere version: 5.1.1 and later WebSphere 5 PMI Level: high WebSphere 6 PMI Level: all ClearedHungThread (PMW_THREADPOOL) Displays the number of hung threads that were cleared. Collector: PerfCollector2 WebSphere version: 5.1.1 and later WebSphere 5 PMI Level: high WebSphere 6 PMI Level: all ConcurrentHungThread (PMW_THREADPOOL) Displays the number of threads that have been declared hung. Collector: PerfCollector2 WebSphere version: 5.1.1 and later WebSphere 5 PMI Level: high WebSphere 6 PMI Level: all ThreadCreates (PMW_THREADPOOL) Displays the total number of threads created. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number of threads yes con undef undef set by coll graph number of threads yes con undef undef set by coll graph number of threads yes con undef undef set by coll graph msec yes con undef undef set by coll graph number of threads
Appendix B
Parameter Reference
361
Units
Type
Icon
Core Parameters
Table 22
Active?
ThreadCreateRate (PMW_THREADPOOL) Displays the total number of threads created per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadDestroys (PMW_THREADPOOL) Displays the number of threads destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadDestroyRate (PMW_THREADPOOL) Displays the number of threads destroyed per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadHung (PMW_THREADPOOL) Displays the number of concurrently hung threads. Collector: PerfCollector2 WebSphere version: 5.1.1 and later WebSphere 5 PMI Level: high WebSphere 6 PMI Level: all ThreadMaxSize (PMW_THREADPOOL) Displays the configured maximum size of the threadpool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
362
Units
Type
Icon
Core Parameters
Table 22
Active?
ThreadPercentMaxed (PMW_THREADPOOL) Average percent of the time that all threads were in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ThreadPoolSize (PMW_THREADPOOL) Average number of threads in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended
yes
con
undef
undef
set by coll
graph
percent
yes
con
undef
undef
set by coll
graph
number of threads
PMW_THREADPOOL_SUMMARY application class

ActiveThreads (PMW_THREADPOOL_SUMMARY) Displays the number of concurrently active threads. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ThreadCreates (PMW_THREADPOOL_SUMMARY) Displays the total number of threads created. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadCreateRate (PMW_THREADPOOL_SUMMARY) Displays the total number of threads created per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number of threads no con undef undef set by coll graph number of threads no con undef undef set by coll graph number of threads
Appendix B
Parameter Reference
363
Units
Type
Icon
Core Parameters
Table 22
Active?
ThreadDestroys (PMW_THREADPOOL_SUMMARY) Displays the number of threads destroyed. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadDestroyRate (PMW_THREADPOOL_SUMMARY) Displays the number of threads destroyed per minute. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number of threads
no
con
undef
undef
set by coll
graph
number of threads
ThreadMaxSize (PMW_THREADPOOL_SUMMARY) no Displays the configured maximum size of the threadpool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ThreadPercentMaxed (PMW_THREADPOOL_SUMMARY) Average percent of the time that all threads were in use. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended ThreadPoolSize (PMW_THREADPOOL_SUMMARY) Average number of threads in the pool. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: high WebSphere 6 PMI Level: extended no no
con
undef
undef
set by coll
graph
number of threads
con
undef
undef
set by coll
graph
percent
con
undef
undef
set by coll
graph
number of threads
364
Units
Type
Icon
Core Parameters
Table 22
Active?
PMW_WEBSERVICE application class

AsynchRequests (PMW_WEBSERVICE) Number of asynchronous requests that were made. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AsynchRequestRate (PMW_WEBSERVICE) Number of asynchronous requests that were made per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AsynchResponses (PMW_WEBSERVICE) Number of asynchronous responses that were made. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AsynchResponseRate (PMW_WEBSERVICE) Number of asynchronous responses per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AvgPayloadSize (PMW_WEBSERVICE) Average payload size (in bytes) of a received request or reply. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: custom yes con undef undef set by coll graph bytes yes con undef undef set by coll graph number no con undef undef set by coll graph number yes con undef undef set by coll graph number no con undef undef set by coll graph number
Appendix B
Parameter Reference
365
Units
Type
Icon
Core Parameters
Table 22
Active?
AvgReplySize (PMW_WEBSERVICE) Average payload size of a reply. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic AvgRequestSize (PMW_WEBSERVICE) Average payload size of a request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic LoadedServices (PMW_WEBSERVICE) Number of loaded web services. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsDispatched (PMW_WEBSERVICE) Number of requests for service dispatched or delivered. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsDispatchedRate (PMW_WEBSERVICE) Number of requests for service dispatched or delivered per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
bytes
yes
con
undef
undef
set by coll
graph
bytes
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
366
Units
Type
Icon
Core Parameters
Table 22
Active?
RequestsReceived (PMW_WEBSERVICE) Number of requests for service received. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsReceivedRate (PMW_WEBSERVICE) Number of requests for service received per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsSuccessful (PMW_WEBSERVICE) Number of requests for service that were successfully processed. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsSuccessfulRate (PMW_WEBSERVICE) Number of requests for service that were successfully processed per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ResponseTimeDispatch (PMW_WEBSERVICE) Average response time (in milliseconds) to dispatch a request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
msec
Appendix B
Parameter Reference
367
Units
Type
Icon
Core Parameters
Table 22
Active?
ResponseTimeReply (PMW_WEBSERVICE) Average response time, in milliseconds, to prepare a reply after dispatch. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ResponseTimeRequest (PMW_WEBSERVICE) Average response time to prepare a request to dispatch. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ResponseTimeSuccessful (PMW_WEBSERVICE) Average response time for a successful request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic SynchRequests (PMW_WEBSERVICE) Number of synchronous requests that were made. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SynchRequestRate (PMW_WEBSERVICE) Number of synchronous requests that were made per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
368
Units
Type
Icon
Core Parameters
Table 22
Active?
SynchResponses (PMW_WEBSERVICE) Number of synchronous responses that were sent. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SynchResponseRate (PMW_WEBSERVICE) Number of synchronous responses that were sent per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
PMW_WEBSERVICE_SUMMARY application class

AsynchRequests (PMW_WEBSERVICE_SUMMARY) no Number of asynchronous requests that were made. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AsynchRequestRate (PMW_WEBSERVICE_SUMMARY) Number of asynchronous requests that were made per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AsynchResponses (PMW_WEBSERVICE_SUMMARY) Number of asynchronous responses that were made. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number yes con undef undef set by coll graph number con undef undef set by coll graph number
Appendix B
Parameter Reference
369
Units
Type
Icon
Core Parameters
Table 22
Active?
AsynchResponsesRate (PMW_WEBSERVICE_SUMMARY) Number of asynchronous responses per second. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom AvgPayloadSize (PMW_WEBSERVICE_SUMMARY) Average payload size (in bytes) of a received request or reply. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: custom AvgReplySize (PMW_WEBSERVICE_SUMMARY) Average payload size of a reply. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
bytes
yes
con
undef
undef
set by coll
graph
bytes
AvgRequestSize (PMW_WEBSERVICE_SUMMARY) yes Average payload size of a request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic LoadedServices (PMW_WEBSERVICE_SUMMARY) Number of loaded web services. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no
con
undef
undef
set by coll
graph
bytes
con
undef
undef
set by coll
graph
number
370
Units
Type
Icon
Core Parameters
Table 22
Active?
RequestsDispatched (PMW_WEBSERVICE_SUMMARY) Number of requests for service dispatched or delivered. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsDispatchedRate (PMW_WEBSERVICE_SUMMARY) Number of requests for service dispatched or delivered per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsReceived (PMW_WEBSERVICE_SUMMARY) Number of requests for service received. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsReceivedRate (PMW_WEBSERVICE_SUMMARY) Number of requests for service received per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom RequestsSuccessful (PMW_WEBSERVICE_SUMMARY) Number of requests for service that were successfully processed. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
371
Units
Type
Icon
Core Parameters
Table 22
Active?
RequestsSuccessfulRate (PMW_WEBSERVICE_SUMMARY) Number of requests for service that were successfully processed per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom ResponseTimeDispatch (PMW_WEBSERVICE_SUMMARY) Average response time (in milliseconds) to dispatch a request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ResponseTimeReply (PMW_WEBSERVICE_SUMMARY) Average response time, in milliseconds, to prepare a reply after dispatch. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ResponseTimeRequest (PMW_WEBSERVICE_SUMMARY) Average response time to prepare a request to dispatch. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic ResponseTimeSuccessful (PMW_WEBSERVICE_SUMMARY) Average response time for a successful request. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
yes
con
undef
undef
set by coll
graph
msec
372
Units
Type
Icon
Core Parameters
Table 22
Active?
SynchRequests (PMW_WEBSERVICE_SUMMARY) Number of synchronous requests that were made. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SynchRequestRate (PMW_WEBSERVICE_SUMMARY) Number of synchronous requests that were made per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
SynchResponses (PMW_WEBSERVICE_SUMMARY) no Number of synchronous responses that were sent. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom SynchResponseRate (PMW_WEBSERVICE_SUMMARY) Number of synchronous responses that were sent per second. Collector: PerfCollector2 WebSphere version: 5.0.2 and above WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom yes
con
undef
undef
set by coll
graph
number
con
undef
undef
set by coll
graph
number
PMW_WLM application class

WLMClientClustUpd (PMW_WLM) Number of times initial or updated server cluster data is sent to a WLM enabled client from server cluster member. Use this metric to determine how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom no con undef undef set by coll graph number
Appendix B
Parameter Reference
373
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMClientClustUpdRate (PMW_WLM) Number of times per second initial or updated server cluster data is sent to a WLM enabled client from server cluster member. Use this metric to determine how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMClientRespTime (PMW_WLM) Response time (in milliseconds) of IIOP requests being setnt from a client. The response time is calculated based on the time the request is sent from the client to the time the reply is received from the server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: basic WLMClientsServiced (PMW_WLM) Number of WLM enabled clients that have been serviced by this application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMClientsServicedRate (PMW_WLM) Number of WLM enabled clients that have been serviced per second by this application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMCurrentRequests (PMW_WLM) Number of remote IIOP requests being processed by this server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
374
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMMinReq (PMW_WLM) Total number of incoming IIOP requests to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMMinReqRate (PMW_WLM) Total number per second of incoming IIOP requests to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMNonAffinReq (PMW_WLM) Number of incoming IIOP requests to an application server based on no affinity. This request was sent to this server based on workload management selection policies that were decided in the Workload Management (WLM) runtime of the client. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMNonAffinReqRate (PMW_WLM) Number of incoming IIOP requests per second to an application server based on no affinity. This request was sent to this server based on workload management selection policies that were decided in the Workload Management (WLM) runtime of the client. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
375
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMNonWLMRequests (PMW_WLM) Number of incoming IIOP requests to an application server that came from a client that does not have the WLM runtime present or where the object reference on the client was flagged not to participate in workload management. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMNonWLMRequestRate (PMW_WLM) Number of incoming IIOP requests per second to an application server that came from a client that does not have the WLM runtime present or where the object reference on the client was flagged not to participate in workload management. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMOutReq (PMW_WLM) Total number of outgoing IIOP requests being sent from a client to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMOutReqRate (PMW_WLM) Total number of outgoing IIOP requests per second being sent from a client to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
376
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMServClustUpdate (PMW_WLM) Number of times initial or updated server cluster data is sent to a server member from the deployment manager. This metric determines how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMServClustUpdateRate (PMW_WLM) Number of times per second initial or updated server cluster data is sent to a server member from the deployment manager. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMServRespTime (PMW_WLM) Response time of IIOP requests being serviced by the server. (Based on time request received to time reply sent out.) Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic WLMStrongAffinReq (PMW_WLM) Number of incoming requests based on strong affinity. Strong affinity is defined as a request that must be serviced by this server because of a dependency that resides on the server. This request could not be serviced by another server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
377
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMStrongAffinReqRate (PMW_WLM) Number of incoming requests per second based on strong affinity. Strong affinity is defined as a request that must be serviced by this server because of a dependency that resides on the server. This request could not be serviced by another server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
yes
con
undef
undef
set by coll
graph
number
PMW_WLM_SUMMARY application class

WLMClientClustUpd (PMW_WLM_SUMMARY) Number of times initial or updated server cluster data is sent to a WLM enabled client from server cluster member. Use this metric to determine how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMClientClustUpdRate (PMW_WLM_SUMMARY) Number of times per second initial or updated server cluster data is sent to a WLM enabled client from server cluster member. Use this metric to determine how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMClientRespTime (PMW_WLM_SUMMARY) Response time (in milliseconds) of IIOP requests being setnt from a client. The response time is calculated base don the time the request is sent from the client to the time the reply is received from the server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: basic yes con undef undef set by coll graph msec yes con undef undef set by coll graph number no con undef undef set by coll graph number
378
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMClientsServiced (PMW_WLM_SUMMARY) Number of WLM enabled clients that have been serviced by this application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMClientsServicedRate (PMW_WLM_SUMMARY) Number of WLM enabled clients that have been serviced per second by this application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMCurrentRequests (PMW_WLM_SUMMARY Number of remote IIOP requests being processed by this server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: extended WLMMinReq (PMW_WLM_SUMMARY) Total number of incoming IIOP requests to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMMinReqRate (PMW_WLM_SUMMARY) Total number per second of incoming IIOP requests to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
379
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMNonAffinReq (PMW_WLM_SUMMARY) Number of incoming IIOP requests to an application server based on no affinity. This request was sent to this server based on workload management selection policies that were decided in the Workload Management (WLM) runtime of the client. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMNonAffinReqRate (PMW_WLM_SUMMARY) Number of incoming IIOP requests per second to an application server based on no affinity. This request was sent to this server based on workload management selection policies that were decided in the Workload Management (WLM) runtime of the client. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMNonWLMRequests (PMW_WLM_SUMMARY) Number of incoming IIOP requests to an application server that came from a client that does not have the WLM runtime present or where the object reference on the client was flagged not to participate in workload management. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
number
380
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMNonWLMRequestRate (PMW_WLM_SUMMARY) Number of incoming IIOP requests per second to an application server that came from a client that does not have the WLM runtime present or where the object reference on the client was flagged not to participate in workload management. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMOutReq (PMW_WLM_SUMMARY) Total number of outgoing IIOP requests being sent from a client to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMOutReqRate (PMW_WLM_SUMMARY) Total number of outgoing IIOP requests per second being sent from a client to an application server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMServClustUpdates (PMW_WLM_SUMMARY) Number of times initial or updated server cluster data is sent to a server member from the deployment manager. This metric determines how often cluster information is being propagated. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
Appendix B
Parameter Reference
381
Units
Type
Icon
Core Parameters
Table 22
Active?
WLMServClustUpdateRate (PMW_WLM_SUMMARY) Number of times per second initial or updated server cluster data is sent to a server member from the deployment manager. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMServRespTime (PMW_WLM_SUMMARY) Response time of IIOP requests being serviced by the server. (Based on time request received to time reply sent out.) Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: medium WebSphere 6 PMI Level: basic WLMStrongAffinReq (PMW_WLM_SUMMARY) Number of incoming requests based on strong affinity. Strong affinity is defined as a request that must be serviced by this server because of a dependency that resides on the server. This request could not be serviced by another server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom WLMStrongAffinReqRate (PMW_WLM_SUMMARY) Number of incoming requests per second based on strong affinity. Strong affinity is defined as a request that must be serviced by this server because of a dependency that resides on the server. This request could not be serviced by another server. Collector: PerfCollector2 WebSphere version: all supported versions WebSphere 5 PMI Level: low WebSphere 6 PMI Level: custom
no
con
undef
undef
set by coll
graph
number
yes
con
undef
undef
set by coll
graph
msec
no
con
undef
undef
set by coll
graph
number
no
con
undef
undef
set by coll
graph
number
382
Units
Type
Icon
JMX Parameters
JMX Parameters
The parameters in this group collect and display information about the operations of JMX technology in the PATROL for WebSphere Application Server product. They are used only with version 5.x of the IBM WebSphere Application Server product. Table 23 JMX Parameters (Part 1 of 4) Scheduling Warning (Alarm1) Alarm (Alarm2)
Active?
Parameter JMX_CONDITION application class

AnnotatedStatus (JMX_CONDITION) Tracks the status of a condition. The numeric value indicates the status of the condition. When the status changes or actions are taken, the graph is annotated. Collector: JMX Discovery WebSphere version: all supported versions BooleanFalseCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current value of the attribute is false. Collector: JMX Discovery WebSphere version: all supported versions BooleanTrueCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current value of the attribute is true. Collector: JMX Discovery WebSphere version: all supported versions MBeanCount (JMX_CONDITION) Displays the number of MBeans being monitored by this condition. Collector: JMX Discovery WebSphere version: all supported versions yes no no yes
con
3 to 5
1 to 3
set by coll
stop light
flag value: 0 = OK 2 = WARN 4 = ALARM
con
undef
undef
set by coll
graph
number of MBeans
con
undef
undef
set by coll
graph
number of MBeans
con
undef
undef
set by coll
graph
number of MBeans
Appendix B
Parameter Reference
383
Units
Type
Icon
JMX Parameters
Table 23
JMX Parameters (Part 2 of 4) Scheduling Warning (Alarm1) Alarm (Alarm2)
Active?
Parameter
StatusCriticalCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current status is alarm, as defined by notifications or attribute values. Collector: JMX Discovery WebSphere version: all supported versions StatusOKCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current status is OK, as defined by notifications or attribute values. Collector: JMX Discovery WebSphere version: all supported versions StatusWarningCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current status is warning, as defined by notifications or attribute values. Collector: JMX Discovery WebSphere version: all supported versions StringMatchCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current value of the string matches the specified value. Collector: JMX Discovery WebSphere version: all supported versions StringNoMatchCount (JMX_CONDITION) Displays the number of monitored MBeans for which the current value of the string does not match the specified value. Collector: JMX Discovery WebSphere version: all supported versions no no yes yes yes
con
110000
10000 10000
set by coll
graph
number of MBeans
con
undef
undef
set by coll
graph
number of MBeans
con
110000
10000 10000
set by coll
graph
number of MBeans
con
undef
undef
set by coll
graph
number of MBeans
con
undef
undef
set by coll
graph
number of MBeans
384
Units
Type
Icon
JMX Parameters
Table 23
Active?
Parameter
ValueAverage (JMX_CONDITION) Displays the average attribute value across all MBeans being monitored by this condition. Collector: JMX Discovery WebSphere version: all supported versions ValueMaximum (JMX_CONDITION) Displays the highest value in any MBean being monitored by this condition. Collector: JMX Discovery WebSphere version: all supported versions ValueMinimum (JMX_CONDITION) Displays the lowest value in any MBean being monitored by this condition. Collector: JMX Discovery WebSphere version: all supported versions ValueSum (JMX_CONDITION) Displays the total value of all MBeans being monitored by this condition. Collector: JMX Discovery WebSphere version: all supported versions no no no no
con
undef
undef
set by coll
graph
number
con
undef
undef
set by coll
graph
number
con
undef
undef
set by coll
graph
number
con
undef
undef
set by coll
graph
number
JMX_DOMAIN application class

MBeanCount (JMX_DOMAIN) Displays the number of MBeans registered in the MBean domain. Collector: JMX Discovery WebSphere version: all supported versions yes con undef undef set by coll graph number of MBeans
Appendix B
Parameter Reference
385
Units
Type
Icon
Consumer-Collector Dependencies
Table 23
Active?
Parameter JMX_MAIN application class

SetupRequired (JMX_MAIN) Indicates that setup is required for the KM Collector: JMX Discovery WebSphere version: all supported versions no
con
undef
undef
set by coll
text
none
JMX_SERVER application class

Availability (JMX_SERVER) Displays the availability of the registered server (up or down). This parameter triggers an alarm if the server is down or if the JMX client is unable to connect to the server. A value of 0 indicates a server is unavailable, a value of 1 indicates available. Collector: JMX Discovery WebSphere version: all supported versions MBeanCount (JMX_SERVER) Displays the number of MBeans registered in the MBean server. Collector: JMX Discovery WebSphere version: all supported versions yes con undef undef set by coll graph number of MBeans yes con 0 to 0 undef set by coll bool none
This section lists the dependencies between the consumer and the collector parameters.
Predominance of PerfCollector2
The vast majority of data performance monitoring parameters, including those that monitor virtually all WebSphere components, are populated by the PerfCollector2 parameter in the APPSERVER application class. You may occasionally want to turn off some collectors, but not PerfCollector2. Data on enterprise applications is collected by the PerfCollector parameter in the ENVIRONMENT class.
Units
Type
Icon
NOTE
Consumer parameters are set by PerfCollector2 during its scheduled interval (63 seconds by default). In addition, any of these consumer parameters for which alarm thresholds are established are checked on the PerfCollector interval (1 minute by default). New values are set on this shorter interval for those consumer parameters who values crossed a threshold. If you change the specified interval for these collector parameters, the PerfCollector2 interval should divide evenly by the PerfCollector interval.
Parameters Populated by PerfCollector (ENVIRONMENT)

All consumer parameters in the following PATROL for WebSphere Application Server application classes are populated by the PerfCollector parameter:
I
PMW_J2EE
Additionally, any of the parameters populated by PerfCollector2 can also be set by

PerfCollector if values cross an alarm threshold.
Parameters Populated by PerfCollector2 (APPSERVER)

All consumer parameters in the following PATROL for WebSphere Application Server application classes are populated by the PerfCollector2 parameter:
I I I I I I I I I I I I I I I I I I
PMW_ALARM_MANAGER PMW_ALARM_SUMMARY PMW_BEANS PMW_CACHE_SUMMARY PMW_CACHE_TEMPLATE PMW_DATASOURCE PMW_DBPOOLS_SUMMARY PMW_DCS PMW_DCS_SUMMARY PMW_EJB_METHOD PMW_EJB_SUMMARY PMW_EJB_TRANSACTION PMW_HA_MANAGER PMW_HA_SUMMARY PMW_J2C_FACTORY PMW_J2C_SUMMARY PMW_J2EE_OBJ PMW_ORB_INTERCEPTOR
Appendix B
Parameter Reference
387
I I I I I I I I I I I I I I I
PMW_ORB_SUMMARY PMW_SCHEDULER PMW_SCHEDULER_SUMMARY PMW_SERVER_RESOURCES (some also collected by PerfCollector) PMW_SERVLET PMW_SERVLET_SUMMARY PMW_SESSIONS PMW_SIB_SERVICE PMW_SIB_SUMMARY PMW_THREADPOOL PMW_THREADPOOL_SUMMARY PMW_WEBSERVICE PMW_WEBSERVICE_SUMMARY PMW_WLM PMW_WLM_SUMMARY
Dependencies for JVM Profiling Parameters

Parameters in the PMW_SERVER_RESOURCES application class that are not populated under PMI by the PerfCollector2 display information about server resources such as memory allocation, garbage collection in the JVM, and JVM threads. These parameter are populated by the JVMCollector parameter: Table 24 PMW_SERVER_RESOURCES Parameters Populated by JVMCollector GarbageCollectionObjectsInUsed GarbageCollections GarbageCollectionRate HeapsInUse HighestCpuThread PeakNTRealMemory PeakNTVirtualMemory VirtualMemory Threads ThreadsObjects
AllocatedHeaps CpuPercent CpuUtilization GarbageCollectionDuration
Dependencies for JVM Bytecode Instrumentation Parameters

Consumer parameters associated JVM bytecode instrumentation display information about the effectiveness of SQL statements, about Web applications, and about servlet methods.
388
The following parameters in the PMW_DBURL application class display information about the effectiveness of SQL statement queries among SQL statements within a DBURL. These parameter are populated by the DbUrlCollector parameter: Table 25 PMW_DBURL Parameters Populated by DbUrlCollector HighestInvocations MostCumulativeTime SlowestRespTime TotalCumulativeTime TotalInvocations
AggregatedInvocationRate AvgRespTime HighestInvocationRate
The following parameters in the PMW_SQL application class display information about queries made through a specific SQL statement. These parameter are populated by the SQLCollector parameter: Table 26 PMW_SQL Parameters Populated by SQLCollector InvocationRate TotalCumulativeTime TotalInvocations
AvgRespTime
The following parameters in the PMW_SERVLET_GROUP application class display information about invocations to servlets and JSPs in a Web application. These parameter are populated by the PjsWebAppTopNCol parameter: Table 27 PMW_SERVLET_GROUP Parameters Populated by PjsWebAppTopNCol HighUsed HighUsedRate InvocationRate SlowestRespTime TotalCumulativeTime TotalInvocations
AvgRespTime HighCumulativeTime
The following parameters in the PMW_SERVLET_METHOD application class display information about invocations to methods in a specific servlet or JSP. These parameter are populated by the PjsServletClassCol parameter: Table 28 PMW_SERVLET_METHOD Parameters Populated by PjsServletClassCol MethodCallsRate MethodRT
MethodCalls
Appendix B
Parameter Reference
389
Dependencies for Availability Parameters

Table 29 shows consumer-collector dependencies of parameters that show the availability of the application server, deployment manager, node agent, the HTTP transport connection, and key components. Table 29 Dependencies for Availability Consumer Parameters Consumer AppServerAvailability HTTPTransportConn State DMgrAvailability JMSServerAvailability NodeAgentAvailability Availability Collector AppServerCollector (MAIN) ServerTransportCol (MAIN) AppServerCollector (MAIN) none (standard parameter) AppServerCollector (MAIN) AppServerCollector (MAIN) JMX Discovery
Application Class PMW_APPSERVER PMW_APPSERVER PMW_CELL PMW_NODE PMW_NODE JMX_SERVER
PMW_DATASOURCE JDBCConnectState
Dependencies Log Monitoring Parameters

The following table shows consumer-collector dependencies of parameters in the PMW_LOG application class: Table 30 Dependencies for Log Consumer Parameters Consumer LogMessages LogMonitorStatus LogFileSize LogGrowthSize LogSizeCollector Collector LogMonitorCollector
Application Class PMW_LOG
Standard Parameters
The following standard parameters perform their own collection. With the exception of PMW_BlackoutCollector and PostProcess (which have no icon), each also displays its own icon: Table 31 PMW Standard Parameters Standard Parameter PMW_BlackoutCollector JDBCConnectState
Application Class PMW_BLACKOUT PMW_DATASOURCE
390
Table 31
PMW Standard Parameters Standard Parameter PostProcess SelectedAliasesActive
Application Class PMW_MAIN PMW_SERVLET_GROUP
Appendix B
Parameter Reference
391
392
Appendix
C
395 395 395 396 396 397 397 397 397 398 398 398 399 399 400 400 400 400 401 401 401 402 402 402 402 403 403 403 403 404 404 404
393
Menu Summary
This chapter summarizes the application menus and menu commands for the PATROL for WebSphere Application Server product. The following topics are discussed in this chapter: Core Product Application Class Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_ALARM_MANAGER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_ALARMMGR_GRP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_ALARM_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_APPSERVER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_BEANS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CACHE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CACHE_SUMMARY Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CACHE_TEMPLATE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CELL Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CLUSTER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DATASOURCE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBPOOLS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBPOOLS_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBURL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBURLS Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DCS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DCS_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DCS_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_EJB_CONTAINER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_EJB_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_EJB_METHOD Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_EJB_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_EJB_TRANSACTION Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_HA_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_HA_MANAGER Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_HA_SUMMARY Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_J2C Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_J2C_FACTORY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_J2C_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_J2EE_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_J2EE_OBJ Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Summary
PMW_LOG Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 PMW_MAIN Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 PMW_NODE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 PMW_OBJECT_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 PMW_OBJECT_POOL Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_OBJECT_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_ORB Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 PMW_ORB_INTERCEPTOR Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_ORB_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_PROF_CLASS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_SCHEDULER Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 PMW_SCHEDULER_SERVICES Application Menu . . . . . . . . . . . . . . . . . . . . . . . 409 PMW_SCHEDULER_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . 409 PMW_SERVER_RESOURCES Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . 410 PMW_SERVLET Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 PMW_SERVLET_ENGINE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 PMW_SERVLET_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SERVLET_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SESSIONS Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 PMW_SETUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 PMW_SIB_GROUP Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SIB_SERVICE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SIB_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_SQL Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 PMW_THREADPOOL Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 PMW_THREADPOOL_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . 415 PMW_THREADPOOL_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . 415 PMW_WEBSERVICE Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 PMW_WEBSERVICE_GROUP Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . 416 PMW_WEBSERVICE_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . 416 PMW_WLM Application Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 PMW_WLM_SUMMARY Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Application Menus for JMX Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 JMX_CONDITION Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 JMX_DOMAIN Application Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 JMX_SERVER commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
394
Core Product Application Class Menus

The menus explained in this section are associated with the primary application classes for the PATROL for WebSphere Application Server product. Each of these classes begins with the designation PMW*. Subsequent sections in this chapter will explain menus for the application classes associated with JMX* classes, which provide product integration of the Java MBean Extension technology, and with MMW* classes, which provide the basis for integration of PATROL for WebSphere Application Server and MAINVIEW for WebSphere Application Server.
PMW_ALARM_MANAGER Application Menu

The menu commands in Table 32 are the PATROL KM menu commands for the PMW_ALARM_MANAGER application class. Table 32 PMW_ALARM_MANAGER commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_ALARM_MANAGER class
Menu Command Performance Collector Report
PMW_ALARMMGR_GRP Application Menu

The menu commands in Table 33 are the PATROL KM menu commands for the PMW_ALARMMGR_GRP application class. Table 33 PMW_ALARMMGR_GRP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_ALARMMGR_GROUP class
Appendix C
Menu Summary
395
PMW_ALARM_SUMMARY Application Menu

The menu commands in Table 34 are the PATROL KM menu commands for the PMW_ALARM_SUMMARY application class. Table 34 PMW_ALARM_SUMMARY commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_ALARM_SUMMARY class
PMW_APPSERVER Application Menu

The menu commands in Table 35 are the PATROL KM menu commands for the PMW_APPSERVER application class. Table 35 PMW_APPSERVER commands Action determine the availability (up or down, reflecting WebSpheres running or stopping states) of a WebSphere application server display recent reliability and serviceability messages for the application server; messages will be displayed from the last five times that the MessageCollector parameter ran start a currently stopped WebSphere application server (requires logon ID) stop a currently running WebSphere application server (requires logon ID) define connection information used by the HTTPTransport parameter
Menu Command Ping Application Server
View Recent Messages
Start Application Server Stop Application Server Configure HTTPTransport Connection Info Advanced Monitoring Profiling Set Profiling Level Configure Method Profiling Class Activate JVM Thread Object Collection Deactivate JVM Thread Object Collection Remove Instrumentation and Profiling
specify level of profiling to be enabled specify classes to monitor during method-level profiling turn on collection of performance data on thread objects turn off collection of thread objects turn off JVM bytecode instrumentation and JVM profiling
396
PMW_BEANS Application Menu

The menu commands in Table 36 are the PATROL KM menu commands for the PMW_BEANS application class. Table 36 PMW_BEANS commands Action create a report of PMI performance data related to Java beans
PMW_CACHE Application Menu

The menu commands in Table 37 are the PATROL KM menu commands for the PMW_CACHE application class. Table 37 PMW_CACHE commands Action create a report of PMI performance data related to the dynamic cache
PMW_CACHE_SUMMARY Application Menu

The menu commands in Table 38 are the PATROL KM menu commands for the PMW_CACHE_SUMMARY application class. Table 38 PMW_CACH_SUMMARY commands Action create a report of summary PMI performance metrics for the dynamic cache
PMW_CACHE_TEMPLATE Application Menu

The menu commands in Table 39 are the PATROL KM menu commands for the PMW_CACHE_TEMPLATE application class. Table 39 PMW_CACH_TEMPLATE commands Action create a report of PMI performance metrics for a dynamic cache template
Appendix C
Menu Summary
397
PMW_CELL Application Menu

The menu commands in Table 40 are the PATROL KM menu commands for the PMW_CELL application class. Table 40 PMW_CELL commands Action determine the availability status of the deployment manager view recent performance messages start a new deployment manager stop a running deployment manager
Menu Command Ping Deployment Manager View Recent Messages Start Deployment Manager Stop Deployment Manager
PMW_CLUSTER Application Menu

The menu commands in Table 41 are the PATROL KM menu commands for the PMW_CELL application class. Table 41 PMW_CLUSTER commands Action start all nodes on the cluster stop and restart all nodes on the cluster stop all nodes on the cluster
Menu Command Start Cluster Ripplestart Cluster Stop Cluster
PMW_DATASOURCE Application Menu

The menu commands in Table 42 are the PATROL KM menu commands at the PMW_DATASOURCE top level of the menu tree hierarchy. Table 42 PMW_DATASOURCE commands (Part 1 of 2) Action determine the availability (up or down, reflecting WebSpheres running or stopping states) of the JDBC connection, which manages connections between the application server and the database for a given data source set the username and password that will be used to establish database connections for each data source display database configuration information for a given data source
Menu Command Ping JDBC Connection
Setup DataSource Login Update DataSource Info
398
Table 42
PMW_DATASOURCE commands (Part 2 of 2) Action produces a report of JDBC connection pool information and displays it in the task output window create a report of PMI performance metrics for a data source change connection information used by PATROL to monitor the JDBC connection restart the collector that determines whether the JDBC connection is currently active stop the collector and associated overhead with monitoring whether the JDBC connection is currently active
Menu Command View Connection Pool Report Performance Collector Report JDBC Connection Configuration Modify JDBC Connection Info Resume JDBC Conn Monitoring Stop JDBC Conn Monitoring
PMW_DBPOOLS Application Menu

The menu commands in Table 43 are the PATROL KM menu commands for the PMW_DBPOOLS application class. Table 43 PMW_DBPOOLS commands Action create a report of PMI performance metrics for a database connection pool
PMW_DBPOOLS_SUMMARY Application Menu

The menu commands in Table 43 are the PATROL KM menu commands for the PMW_DBPOOLS_SUMMARY application class. Table 44 PMW_DBPOOLS_SUMMARY commands Action create a report of PMI summary performance metrics for database connection pools
Appendix C
Menu Summary
399
PMW_DBURL Application Menu

The menu commands in Table 45 are the PATROL KM menu commands at the PMW_DBURL top level of the menu tree hierarchy. Table 45 PMW_DBURL commands Action generates a report about the performance of up to 30 SQL statements in the DBURL refreshes discovery of the DBURL refreshes discovery of SQL statements in the DBURL
Menu Command SQL Performance Report Refresh DBURL Discovery Refresh SQL Discovery
PMW_DBURLS Application Menu

The menu commands in Table 46 are the PATROL KM menu commands at the PMW_DBURLS top level of the menu tree hierarchy. Table 46 PMW_DBURLS commands Action generates a report about the performance of up to 30 SQL statements in all of the discovered DBURLs
Menu Command SQL Performance Report
PMW_DCS Application Menu

The menu commands in Table 47 are the PATROL KM menu commands for the PMW_DCS application class. Table 47 PMW_DCS commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_DCS class
PMW_DCS_GROUP Application Menu

The menu commands in Table 48 are the PATROL KM menu commands for the PMW_DCS_GROUP application class.
400
Table 48
PMW_DCS_GROUP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_DCS_GROUP class
PMW_DCS_SUMMARY Application Menu

The menu commands in Table 49 are the PATROL KM menu commands for the PMW_DCS_SUMMARY application class. Table 49 PMW_DCS_SUMMARY commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_DCS_SUMMARY class
PMW_EJB_CONTAINER Application Menu

The menu commands in Table 50 are the PATROL KM menu commands at the PMW_EJB_CONTAINER top level of the menu tree hierarchy. Table 50 Start Stop PMW_EJB_CONTAINER commands Action start a previously stopped enterprise application (WebSphere versions 5 and 6) stop a currently running enterprise application (WebSphere versions 5 and 6)
,
Menu Command
PMW_EJB_GROUP Application Menu

The menu commands in Table 51 are the PATROL KM menu commands for the PMW_EJB_GROUP application class. Table 51 PMW_EJB_GROUP commands Action create a report that shows PMI performance metrics related to an EJB group
Appendix C
Menu Summary
401
PMW_EJB_METHOD Application Menu

The menu commands in Table 52 are the PATROL KM menu commands for the PMW_EJB_METHOD application class. Table 52 PMW_EJB_METHOD commands Action create a report that shows PMI performance metrics related to an EJB method
PMW_EJB_SUMMARY Application Menu

The menu commands in Table 53 are the PATROL KM menu commands for the PMW_EJB_SUMMARY application class. Table 53 PMW_EJB_SUMMARY commands Action create a report that shows PMI summary performance metrics for all EJB groups
PMW_EJB_TRANSACTION Application Menu

The menu commands in Table 54 are the PATROL KM menu commands for the PMW_EJB_TRANSACTION application class. Table 54 PMW_EJB_TRANSACTION commands Action create a report that shows PMI performance metrics for EJB transactions
PMW_HA_GROUP Application Menu

The menu commands in Table 55 are the PATROL KM menu commands for the PMW_HA_GROUP application class. Table 55 PMW_HA_GROUP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_HA_GROUP class
402
PMW_HA_MANAGER Application Menu

The menu commands in Table 56 are the PATROL KM menu commands for the PMW_HA_MANAGER application class. Table 56 PMW_HA_MANAGER commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_HA_MANAGER class
PMW_HA_SUMMARY Application Menu

The menu commands in Table 57 are the PATROL KM menu commands for the PMW_HA_SUMMARY application class. Table 57 PMW_HA_SUMMARY commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_HA_SUMMARY class
PMW_J2C Application Menu

The menu commands in Table 58 are the PATROL KM menu commands for the PMW_J2C application class. Table 58 PMW_J2C commands Action create a report that shows PMI performance metrics for J2C
PMW_J2C_FACTORY Application Menu

The menu commands in Table 59 are the PATROL KM menu commands for the PMW_J2C_FACTORY application class. Table 59 PMW_J2C_FACTORY commands Action create a report that shows PMI performance metrics for a J2C factory
Appendix C
Menu Summary
403
PMW_J2C_SUMMARY Application Menu

The menu commands in Table 60 are the PATROL KM menu commands for the PMW_J2C_SUMMARY application class. Table 60 PMW_J2C_SUMMARY commands Action create a report that shows summary PMI performance metrics for all J2C factories
PMW_J2EE_GROUP Application Menu

The menu commands in Table 61 are the PATROL KM menu commands for the PMW_J2EE_GROUP application class. Table 61 PMW_J2EE_GROUP commands Action Configure a servlet or JSP for application performance monitoring Configure an EJB for application performance monitoring Turn on transaction monitoring; this will enable monitoring of individual transactions by activating bytecode instrumentation for servers in the environment Turn off transaction monitoring
Menu Command Monitor Servlet/JSP Monitor EJB Monitor Transactions Activate
Deactivate
PMW_J2EE_OBJ Application Menu

The menu commands in Table 62 are the PATROL KM menu commands for the PMW_J2EE_OBJ application class. Table 62 PMW_J2EE_OBJ commands Action Change the options for monitoring an enterprise application, servlet, or EJB Stop monitoring an enterprise application, servlet, or EJB Show information about long-running and recent transactions; this command is available only if bytecode instrumentation is enabled or IBM Request Metrics are activated.
Menu Command Modify Monitoring Remove Monitoring View Transactions
404
PMW_LOG Application Menu

The menu commands in Table 63 are the PATROL KM menu commands for the PMW_LOG application class. Table 63 PMW_LOG commands Action specify criteria used when scanning log files for messages that should trigger warnings or alarms display messages from the log file set the starting point for the next log monitoring cycle acknowledge that error conditions occurred and reset the log file to a normal state
Menu Command Define Log Monitor Rules View Log File Rewind Log File Clear ALARM or WARN State
PMW_MAIN Application Menu

The menu commands in Table 64 are the PATROL KM menu commands for the PMW_MAIN application class. Table 64 PMW_MAIN commands Action run discovery to update all objects manually begin a blackout of this application at the beginning of the next blackout collection cycle manually terminate a blackout of this application at the beginning of the next blackout collection cycle list all objects currently blacked out through any blackout mechanism provided by the KM create a report of performance data
Menu Command Refresh Discovery Blackout Suspend Monitoring Resume Monitoring List Blackout Objects Performance Collector Report
Appendix C
Menu Summary
405
PMW_NODE Application Menu

The menu commands in Table 65 are the PATROL KM menu commands for the PMW_NODE application class.
NOTE
The menu commands in Table 65 are for use only with IBM WebSphere Application Server 5.x in the Network Deployment configuration.
Table 65
PMW_NODE commands Action verifies the availability of a node agent display recent reliability and serviceability messages for the node; messages will be displayed from the last five times that the MessageCollector parameter ran starts a specified node agent stops a specified node agent verifies that a JMS server is online and available starts a specified JMS server stops a specified JMS server
Menu Command Ping Node Agent View Recent Messages
Start Node Agent Stop Node Agent Ping JMS Server Start JMS Server Stop JMS Server
PMW_OBJECT_GROUP Application Menu

The menu commands in Table 66 are the PATROL KM menu commands for the PMW_OBJECT_GROUP application class. Table 66 PMW_OBJECT_GROUP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_OBJECT_GROUP class
406
PMW_OBJECT_POOL Application Menu

The menu commands in Table 67 are the PATROL KM menu commands for the PMW_OBJECT_POOL application class. Table 67 PMW_OBJECT_POOL commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_OBJECT_POOL class
PMW_OBJECT_SUMMARY Application Menu

The menu commands in Table 68 are the PATROL KM menu commands for the PMW_OBJECT_SUMMARY application class. Table 68 PMW_OBJECT_SUMMARY commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_OBJECT_SUMMARY class
PMW_ORB Application Menu

The menu commands in Table 69 are the PATROL KM menu commands for the PMW_ORB application class. Table 69 PMW_ORB commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_ORB class
Appendix C
Menu Summary
407
PMW_ORB_INTERCEPTOR Application Menu

The menu commands in Table 70 are the PATROL KM menu commands for the PMW_ORB_INTERCEPTOR application class. Table 70 PMW_ORB_INTERCEPTOR commands Action create a report that shows PMI performance metrics for an ORB interceptor
PMW_ORB_SUMMARY Application Menu

The menu commands in Table 70 are the PATROL KM menu commands for the PMW_ORB_SUMMARY application class. Table 71 PMW_ORB_SUMMARY commands Action create a report that shows summary PMI performance metrics for all ORB interceptors
PMW_PROF_CLASS Application Menu

The menu commands in Table 72 are the PATROL KM menu commands for the PMW_PROF_CLASS application class. Table 72 PMW_PROF_CLASS commands Action stops method profiling in one or more specified Java application classes
Menu Command Stop Monitoring
PMW_SCHEDULER Application Menu

The menu commands in Table 73 are the PATROL KM menu commands for the PMW_SCHEDULER application class. Table 73 PMW_SCHEDULER commands Action create a report that shows summary performance metrics for the collector handling a specific scheduler
408
PMW_SCHEDULER_SERVICES Application Menu

The menu commands in Table 74 are the PATROL KM menu commands for the PMW_SCHEDULER_SERVICES application class. Table 74 PMW_SCHEDULER_SERVICES commands Action create a report that shows composite performance metrics for the collector handling scheduler services
PMW_SCHEDULER_SUMMARY Application Menu

The menu commands in Table 75 are the PATROL KM menu commands for the PMW_SCHEDULER_SUMMARY application class. Table 75 PMW_SCHEDULER_SUMMARY commands Action create a report that shows summary performance metrics for all schedulers
Appendix C
Menu Summary
409
PMW_SERVER_RESOURCES Application Menu

The menu commands in Table 76 are the PATROL KM menu commands for the PMW_SERVER_RESOURCES application class. Table 76 PMW_SERVER_RESOURCES commands Action Generates a report, based on JVM profiling data, about JVM threads. The report include such information as
I I I I I I I
Menu Command AppServer JVM Performance
dates and times when the thread started and stopped OS thread ID and JVM thread ID for the thread process ID of JVM that created the thread thread name, thread group name, thread parent name number of times thread was loaded CPU consumption of the thread in seconds number of objects still in use by the thread at the end of the collection cycle space in KB allocated for objects still in use by the thread at the end of the collection cycle
This menu command requires Advanced JVMPI profiling to be enabled. Performance Collector Report create a report of performance data
PMW_SERVLET Application Menu

The menu commands in Table 77 are the PATROL KM menu commands for the PMW_SERVLET application class. Table 77 PMW_SERVLET commands Action create a report that shows summary PMI performance metrics for a servlet
PMW_SERVLET_ENGINE Application Menu

The menu commands in Table 78 are the PATROL KM menu commands for the PMW_SERVLET_ENGINE application class.
410
Table 78
PMW_SERVLET_ENGINE commands Action generates a report generates a report based on performance criteria for up to the 30 worst responding servlets over all discovered Web applications create a report of performance data
Menu Command WebApp Performance Report Servlet Performance Report
Performance Collector Report
PMW_SERVLET_GROUP Application Menu

The menu commands in Table 79 are the PATROL KM menu commands at the PMW_SERVLET_GROUP top level of the menu tree hierarchy. Table 79 PMW_SERVLET_GROUP commands Action reports performance criteria for up to the 30 worst responding servlets in a single Web application pings for active virtual hosts based on user-defined criteria submitted through dialog boxes set up list of virtual host aliases that will be pinged when Ping Virtual Hosts command is used
Menu Command Servlet Performance Report Ping Virtual Hosts Configure VHost Alias Ping List
PMW_SERVLET_SUMMARY Application Menu

The menu commands in Table 80 are the PATROL KM menu commands for the PMW_SERVLET_SUMMARY application class. Table 80 PMW_SERVLET_SUMMARY commands Action create a report that shows summary PMI performance metrics for servlets
PMW_SESSIONS Application Menu

The menu commands in Table 81 are the PATROL KM menu commands at the PMW_SESSIONS top level of the menu tree hierarchy. Table 81 PMW_SESSIONS commands Action create a report of performance data
Appendix C Menu Summary 411
.
PMW_SETUP Application Menu

The menu commands in Table 82 are the PATROL KM menu commands at the PMW_SETUP top level of the menu tree hierarchy. Table 82 KM Setup PMW_SETUP commands (Part 1 of 2) Action configure the PATROL for WebSphere Application Server KM product by use of the following submenu commands: launches a wizard that goes through the following steps:
I I I
Menu Command
Initial Setup ...
WebSphere Admin registration Java client registration WebSphere global security account registration (if global security is enabled) display of report of setup, later viewable through Post-Install Runtime Verification ...
Post-Install Runtime Verification ...
displays details of the runtime environment:

I I I I I I I I I
local IBM WebSphere version WebSphere home directory Java home directory name of host KM connection port number WebSphere Admin username global security authentication type global security login account name WebSphere AdminDB account name (if IBM WebSphere version is earlier than 5.0 servlet version of registered environment
also provides option to print the above listed information to the console output window
412
Table 82
PMW_SETUP commands (Part 2 of 2) Action create blackout periods and specify

I
Menu Command Blackout Setup Blackout Schedule
I I
which application servers will be blacked out when blackout periods will begin how long each blackout period will endure before terminating
List Blackout Objects
list all objects currently blacked out through any blackout mechanism provided by the KM specify monitor and general alarm options for one, several, or all application servers specify which services (application classes) to activate and which parameters in each activated service to make available manually check the performance data level for the monitored environment and adjust the level if desired enable the features that provide JMX Mbean management (See Chapter 11, Managing JMX-Instrumented Applications.) turn off the features that provide JMX Mbean management configure the JMX listener set the default e-mail settings used when JMX notifications are generated turn debug options on or off for JMX management turn debug options on or off for various KM functions, including setup, discovery, performance data collection, and KM commands
Customization Monitor Options ...
Performance Data Selection ...
WebSphere Performance Data Setting ...
JMX Activate JMX Management
Deactivate JMX Management Setup Listener Setup E-mail Set Debug Flags Debug Options
Appendix C
Menu Summary
413
PMW_SIB_GROUP Application Menu

The menu commands in Table 83 are the PATROL KM menu commands for the PMW_SIB_GROUP application class. Table 83 PMW_SIB_GROUP commands Action create a report that shows performance metrics for the SIB_GROUP class
PMW_SIB_SERVICE Application Menu

The menu commands in Table 84 are the PATROL KM menu commands for the PMW_SIB_SERVICE application class. Table 84 PMW_SIB_SERVICE commands Action create a report that shows performance metrics for the SIB_SERVICE class
PMW_SIB_SUMMARY Application Menu

The menu commands in Table 85 are the PATROL KM menu commands for the PMW_SIB_SUMMARY application class. Table 85 PMW_SIB_SUMMARY commands Action create a report that shows performance metrics for the SIB_SUMAMRY class
PMW_SQL Application Menu

The menu commands in Table 86 are the PATROL KM menu commands at the PMW_SQL top level of the menu tree hierarchy. Table 86 PMW_SQL commands Action displays the full name of the SQL statement stops monitoring of one or more SQL statements
.
Menu Command View SQL Name Stop Monitoring
414
PMW_THREADPOOL Application Menu

The menu commands in Table 87 are the PATROL KM menu commands for the PMW_THREADPOOL application class. Table 87 PMW_THREADPOOL commands Action create a report that shows PMI performance metrics for a threadpool
PMW_THREADPOOL_GROUP Application Menu

The menu commands in Table 88 are the PATROL KM menu commands for the PMW_THREADPOOL_GROUP application class. Table 88 PMW_THREADPOOL_GROUP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_THREADPOOL_ GROUP class
PMW_THREADPOOL_SUMMARY Application Menu

The menu commands in Table 89 are the PATROL KM menu commands for the PMW_THREADPOOL_SUMMARY application class. Table 89 PMW_THREADPOOL commands Action create a report that shows summary PMI performance metrics for threadpools
PMW_WEBSERVICE Application Menu

The menu commands in Table 90 are the PATROL KM menu commands for the PMW_WEBSERVICE application class. Table 90 PMW_WEBSERVICE commands Action create a report that shows PMI performance metrics for a web service
Appendix C
Menu Summary
415
PMW_WEBSERVICE_GROUP Application Menu

The menu commands in Table 91 are the PATROL KM menu commands for the PMW_WEBSERVICE_GROUP application class. Table 91 PMW_WEBSERVICE_GROUP commands Action create a report that shows performance metrics for the PATROL collector that handles the PMW_WEBSERVICE_ GROUP class
PMW_WEBSERVICE_SUMMARY Application Menu

The menu commands in Table 92 are the PATROL KM menu commands for the PMW_WEBSERVICE_SUMMARY application class. Table 92 PMW_THREADPOOL commands Action create a report that shows summary PMI performance metrics for web services
PMW_WLM Application Menu

The menu commands in Table 93 are the PATROL KM menu commands for the PMW_WLM application class. Table 93 PMW_WLM commands Action create a report that shows PMI performance metrics for the workload manager
PMW_WLM_SUMMARY Application Menu

The menu commands in Table 94 are the PATROL KM menu commands for the PMW_WLM_SUMMARY application class. Table 94 PMW_WLM commands Action create a report that shows summary PMI performance metrics for all workload managers
416
Application Menus for JMX Classes

JMX_CONDITION Application Menu
The menu commands in Table 95 are the PATROL KM menu commands at the JMX_CONDITION top level of the menu tree hierarchy. Table 95 JMX_CONDITION commands Action report on all MBeans being monitored for this condition, including status of each; if notifications are enabled on an MBean, the report will include the number of outstanding notifications; attribute-based MBeans will include the attribute value change the definition of a condition, including thresholds on attributes and e-mail settings on notifications remove a condition definition, stopping all monitoring and actions associated with the condition remove automatic notification settings from a condition
Menu Command View Condition Report
Modify Condition Remove Condition Reset Notifications
JMX_DOMAIN Application Menu

The menu commands in Table 96 are the PATROL KM menu commands at the JMX_DOMAIN top level of the menu tree hierarchy. Table 96 JMX_DOMAIN commands Action view and configure registered MBeans on a domain; options are provided to filter a list of MBeans, select MBeans to view, set attributes, invoke operations, and define conditions view and configure MBeans from a select subset of registered MBeans on a domain; before filtering and setting MBean options (as in the previous command), you can narrow the range of selected MBeans based on property keys and values
Menu Command All MBeans...
Select MBeans...
Appendix C
Menu Summary
417
JMX_SERVER commands
The menu commands in Table 97 are the PATROL KM menu commands at the JMX_SERVER top level of the menu tree hierarchy. See the online help for more details about these commands. Table 97 JMX_SERVER commands Action view and configure registered MBeans on this server; options are provided to filter a list of MBeans, select MBeans to view, set attributes, invoke operations, and define conditions view and configure MBeans from a select subset of registered MBeans on this server; before filtering and setting MBean options (as in the previous command), you can narrow the range of selected MBeans based on property keys and values create and register a new MBean in the server; a dialog requests information about the MBean object name, class, and a list of URLs or files to be searched for MBeans and their referenced classes view and modify conditions being monitored by this server; condition definitions include JMX notifications or attribute thresholds
Menu Command Manage MBeans All MBeans...
Select MBeans...
Register MBean
Define Conditions
418
Appendix
Agent Configuration Variables

The variables described in this section are PATROL for WebSphere Application Server variables that are set in the PATROL Agent. You can use the PATROL Configuration Manager or the wpconfig utility to view variable settings or to deploy them to others machines. See the PATROL Configuration Manager User Guide or the PATROL Agent Reference Manual for more information.
WARNING
Changing any of these variables may prevent some functions from working properly, and may affect your entire installation. Make a record of the original setting for a variable before you change it.
WARNING
Many PATROL for WebSphere Application Server variables are set by menu commands or functions. Do not use the wpconfig utility or PATROL Configuration Manager to remove variables or add new variables. Doing so may prevent some functions from working properly and can affect your entire installation. BMC Software recommends that you set agent configuration variables by using a console to configure PATROL for WebSphere Application Server.
NOTE
Some of the variables described in this appendix may not appear in your environment. Some variables exist only when their corresponding features are enabled or when non-default performance options are selected.
419
Table 98 Variable
Agent Variables Used by PATROL for WebSphere Application Server (Part 1 of 6) Description Location
Flag indicating whether availability alarms are /AgentSetup/PMW_ enabled for a specific server. APPSERVE.<appserve>. OS account to be used in starting Java clients /AgentSetup/PMW_ and accessing WebSphere files for this CHANNEL.<environment>. environment. The format is username/password. Password can be encrypted. If not specified, the value used is from: /AgentSetup/PMW_MAIN.WebSphere. defaultAccount Operating system account under which a web application runs Server ID and password used in connecting to WebSphere servers for this environment. The format is username/password. Password can be encrypted. If not specified, no account will be specified on connection (which is valid only if WebSphere global security is not enabled). Operating system account used by default to run commands issued under PATROL for WebSphere Application Server /AgentSetup/PMW_ DATASOURCE.<datasource instance>. /AgentSetup/PMW_ ENVIRONMENT.<environment>.
OfflineAlarm defaultAccount
defaultAccount
defaultAccount
OSdefaultAccount
/AgentSetup/PMW_ WEBSPHERE.PMW_ WEBSPHERE.
defaultAccount
Security server ID and password. Needed only /AgentSetup/PMW_ if global security is enabled. The format is WEBSPHERE.PMW_ username/password. Password can be in the WEBSPHERE. defaultAccount encrypted form as returned by the psl encrypt() function. Operating system account used to access the server log files. Operating system account under which log monitoring functions run. OS account to be used in starting Java clients and accessing WebSphere files in the local file system (unless overridden by an account specific to the environment). The format is username/password. Password can be encrypted. Operating system account used to set up PATROL for WebSphere Application Server. Operating system account under which IBM WebSphere runs Port on which the JMX listener waits for connections. By default this is 3604. /AgentSetup/PMW_LOG. /AgentSetup/PMW_LOG. /AgentSetup/PMW_MAIN. <environment>.
OSdefaultAccount OSdefaultAccountAppliestoCmd defaultAccount
OSdefaultAccount OSdefaultAccount ListenPort OSdefaultAccount
/AgentSetup/PMW_SETUP. /AgentSetup/WEBSPHERE. /JMX/
User credentials used to collect information /AgentSetup/PMW_SERVER_LO from the log files; is used only in the LOG KM. GS.
420
Table 98 Variable
activateJMX
Agent Variables Used by PATROL for WebSphere Application Server (Part 2 of 6) Description
Flag indicating whether the JMX management capability is to be activated. A value of 1 indicates activation. This requires that the Version variable be set to 5.0 or 5.1. Activation occurs when the server is restarted. Once activated, conditions can be defined in variables conforming to the format: /JMX/ConditionDef/<apply token>/ <condition name>, where <apply token> defines the servers to which the condition is applicable and <condition name> names the condition. The arguments are a list of semicolon delimited keyword/value pairs that define the condition. See the discussion of using JMX in this user guide.
Location
/WEBSPHERE/
bci.*
Controls global activation of bytecode /WEBSPHERE/ instrumentation for any servers discovered for which bci.<cell>.<node>.<server> does not exist. When such a server is discovered, bci.<cell>.<node>.<server> is created using the value from bci.* Flag indicating whether bytecode instrumentation is activated. 0 = deactivate bytecode instrumentation, 1 = activate Controls global activation of bytecode instrumentation for any servers discovered for which bcithresh.<cell>.<node>.<server> does not exist. When such a server is discovered, bcithresh.<cell>.<node>.<server> is created using the value from bcithresh.* Transaction threshold in milliseconds. Transactions that complete faster than the threshold value are not reported by bytecode instrumentation to the application server. /WEBSPHERE/
bci.<cell>.<node>.<server>
bcithresh.*
/WEBSPHERE/
bcithresh.<cell>.<node>.<server>
/WEBSPHERE/
bcixmon.<environment>
Flag indicating whether transaction monitoring /WEBSPHERE/ with bytecode instrumentation is activated for all servers in the environment. 0 = deactivate transaction monitoring at the environment level, 1 = activate Allows the KM to ping the HTTP transport port /WEBSPHERE/ even if the server is stopped. This is a boolean, true or false variable. Sets the HTTP transport collector timeout interval if the server is not responding with a timeout interval; default value (not set) is 60. /WEBSPHERE/
httpPingOverride
httpPingTimeOut
logReadDefer
Specifies whether to scan only a specified /WEBSPHERE/ number of bytes during a collection cycle, and defer the rest of scanning to subsequent cycles. Values are Y or N.
Appendix D
421
Table 98 Variable
Specifies the maximum number of bytes for the /WEBSPHERE/ collector to scan, in conjunction with logReadDefer. Default is 100,000. Maximum time (in seconds) that a client can be /WEBSPHERE/ locked while awaiting a response. the PostProcess (PMW_MAIN) parameter will stop any clients locked longer than this time. Default is 60 seconds. Flag indicating whether availability alarms are /WEBSPHERE/ enabled system wide. Flag indicating whether to enable JVM profiling.
I I I
logScanMaxSize
maximumClientLockTime
OfflineAlarm profiling.<cell>.<node>.<server>
/WEBSPHERE/
0 = no profiling 1 = profiling by WebSphere 2 = profiling by BMC
After setting the value, discovery of the WebSphere class will configure the target server. The server must be restarted to complete activation of profiling. Version WAS_HOME Version of IBM WebSphere Application Server /WEBSPHERE/ in use. Directory path in which the WebSphere application server is installed. For example: /opt/Websphere/AppServer /WEBSPHERE/
XMLConfig zOsMaximumClientLockTime
Name of the script used to start the Websphere /WEBSPHERE/ XMLConfig utility, for example: XMLConfig.sh Maximum time (in seconds) that a client can be /WEBSPHERE/ locked while awaiting a response. the PostProcess (PMW_MAIN) parameter will stop any clients locked longer than this time. Default is 60 seconds. If set to 1, this indicates Java clients started by PATROL for WebSphere will end when the WebSphere server for which the connection is established terminates Timeout value (in seconds). If an attempt to contact the server does not complete within this time, the server is considered unavailable. The default is 10 seconds. Controls the monitoring of WebSphere EJBs and servlets and JSPs. Activate PMI-based parameters in the PMW_CACHE_SUMMARY and PMW_CACHE_TEMPLATE classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. /WEBSPHERE/ or /WEBSPHERE/registered/ <environment> /WEBSPHERE/ or /WEBSPHERE/registered/ <environment> /WEBSPHERE/<application server>. /WEBSPHERE/<server>.
terminateWithServer
timeout
monitorAppServerObjects cacheParameters
422
Table 98 Variable
Activate PMI-based parameters in the PMW_DBPOOLS_SUMMARY and PMW_DBPOOLS classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details.
Location
/WEBSPHERE/<server>.
dbPoolsParameters
ejbBeanParameters
Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_BEANS and PMW_EJB_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the PMW_EJB_METHOD class. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the PMW_EJB_TRANSACTION class. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. /WEBSPHERE/<server>.
ejbMethodParameters
ejbTransParameters
j2cParameters
Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_J2C and PMW_J2C_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_SERVER_RESOURCES class. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_ORB and PMW_ORB_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Determines the level at which PATROL for WebSphere will set performance monitoring. The recommended default is 2. Values are:
I I I I I
jvmRuntimeParameters
orbParameters
PMISetting
1 - maximum (v5) / all (v6) 2 - high (v5) / extended (v6) 3 - medium (v5) / basic (v6) 4 - low (v5) / custom (v6) 5 - none
Appendix D
423
Table 98 Variable
Activate PMI-based parameters in the PMW_SERVLET_SUMMARY and PMW_SERVLET classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the PMW_SESSIONS class. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details.
Location
servletJspParameters
sessionParameters
threadPoolsParameters
Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_THREADPOOLS and PMW_THREADPOOLS_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_WEBSERVICES and PMW_WEBSERVICES_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Activate PMI-based parameters in the /WEBSPHERE/<server>. PMW_WLM and PMW_WLM_SUMMARY classes. By default, only a subset of parameters are active. The value is a list of specific parameters to be activated. See APPENDIX B for details. Comma-delimited list consisting of host:port to /WEBSPHERE/<servlet group be used in testing HTTP server availability for instance>/ web applications. Two options, delimited by a vertical bar, each option set to 0 or 1. The first option indicates whether to create SelectedAliasesActive parameter for the servlet group instance, the second indicates whether to alarm when the value of this parameter reaches 0. /WEBSPHERE/<servlet group instance>/
webServiceParameters
wlmParameters
SELECTED_VIRTUAL_HOSTS_ NAME SELECTED_VIRTUAL_HOSTS_ PARM_OPTION
SELECTED_VIRTUAL_HOSTS_ PORT cell
Comma-delimited list consisting of host:port to /WEBSPHERE/<servlet group be used in testing HTTP server availability for instance>/ web applications. Cell name of the environment. Only applies for /WEBSPHERE/registered/ LOCAL_NODE, LOCAL_CELL. For remote <environment>/ environments, the cell name is determined upon connection to the applicable process. This variable is optional; if not provided, the cell name will be determined by the environment variable WAS_CELL, as specified in the setupCmdLine script provided by WebSphere.
424
Table 98 Variable
dir
Optional configuration directory, if different /WEBSPHERE/registered/ from WAS_HOME. Only applies for <environment>/ LOCAL_NODE, LOCAL_CELL. This is optional; if not provided, the value of the value of WEBSPHERE/WAS_HOME will be used. Set to 0 if app servers are not to be grouped /WEBSPHERE/registered/ under cluster headers in the PATROL <environment>/ hierarchy. The default behavior is that servers will be grouped under cluster headers for REMOTE_CELL and LOCAL_CELL. Grouping by cluster is not supported for LOCAL_NODE or REMOTE_ SRVR. Host name or IP address for remote connection /WEBSPHERE/registered/ to the deployment manager (REMOTE_CELL) <environment>/ or base application server (REMOTE_SRVR). Only applies to REMOTE_CELL, REMOTE_ SRVR. If not provided, the value localhost is used. Node name of the environment. Only applies /WEBSPHERE/registered/ for LOCAL_NODE. For cell environments, all <environment>/ nodes are managed. For remote server environments, the node name is determined upon connecting to the applicable remote process. This variable is optional; if not provided, the name will be provided by the environment variable WAS_NODE, as specified in the setupCmdLine script provided by WebSphere. IP port where the remote deployment manager /WEBSPHERE/registered/ (REMOTE_CELL) or base application server <environment>/ (REMOTE_SRVR) is listening to connections, corresponding to the SOAP or RMI protocol (as specified in the protocol variable). Only aplies to REMOTE_CELL, REMOTE_SRVR. If not specified, 8880 is used for SOAP or 2803 for RMI. Protocol used to communicate with WebSphere /WEBSPHERE/registered/ servers. Set to soap or rmi. Any other value <environment>/ is treated as soap. Applies to all environments. Set to the full path name of an optional user override script to be run at client startup or to provide all settings if setupCmdLine was not called. A value of indicates no script. /WEBSPHERE/registered/ <environment>/
groupByCluster
host
node
port
protocol
script
setup
Set to true if setupCmdLine script should be /WEBSPHERE/registered/ run at client startup; otherwise false. Default <environment>/ is true. Indicates the environment type: LOCAL_NODE, LOCAL_CELL, REMOTE_CELL, or REMOTE_SERVER. Any other value is treated as LOCAL_NODE. /WEBSPHERE/registered/ <environment>/
type
Appendix D
425
Application Performance Variables

Your environment may contain many variables that control monitoring of J2EE application and transaction performance. These variables are located under /WEBSPHERE/appPerf/<environment name>. Example: To monitor something under the myServlet label in an environment called myEnvironment, the variable would be: /WEBSPHERE/appPerf/myEnvironment/myServlet The variable data takes the format: <type>, <object>, <label>, <long threshold>, <SQL monitor>, <count> where:
I
<type> this is ear for monitoring at the enterprise application level, servlet for monitoring a servlet or JSP, or ejb for monitoring an EJB <object> this takes one of the following forms, depending on the <type>. For example: ear: enterprise application name servlet: <enterprise application name># <war file name># <servlet name> ejb: <enterprise application name># <jar file name># <ejb name> <label> this is the instance name, the label under which monitoring occurs <long threshold> this is the elapsed time (in milliseconds) that constitutes a long running transaction <SQL monitor> this is set to 1 for type ear and activates monitoring of SQL statement activity by type (select, insert, delete, etc.) <count> this identifies how many transactions will be made available from the View Transactions operation
426
Appendix
E
428 428 428 429 429 430 430 430 431 431 432 432 432 433
Product InfoBoxes
This chapter summarizes InfoBoxes available in the PATROL for WebSphere Application Server product. Some application classes may appear only if certain features are enabled in your environment or configured for your PATROL monitoring environment. The following topics are discussed in this chapter: Standard InfoBox Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Core Product Application Class InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_APPSERVER InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_CELL InfoBox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DATASOURCE InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_DBURL InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_LOG InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_NODE InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_MAIN InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_SERVER_RESOURCES InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMW_SETUP InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX InfoBoxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_CONDITION InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMX_SERVER InfoBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product InfoBoxes
427
Standard InfoBox Fields
Standard InfoBox Fields

Table 99 lists the fields that are standard for all application class InfoBoxes in the PATROL for WebSphere Application Server product. All other InfoBox fields explained in this chapter appear in addition to these standard fields. Table 99 Item History Retention Worst Parameter Default username Application class State Icon type PATROL for WebSphere Application Server Standard InfoBox Fields Description number of days for which a current history has been kept name of the parameter with the worst performance in the application class account name used if not otherwise specified name of the application class (PATROL application class, not Java application class) current state of the application, such as OK, running, or stopped icon typefor application class InfoBoxes, this will be Application
Core Product Application Class InfoBoxes

The application class InfoBoxes explained in this section are part of the core PATROL for WebSphere Application Server product. Each of these application classes begins with PMW_*.
PMW_APPSERVER InfoBox
Table 100 lists the items beyond standard InfoBox items for the PMW_APPSERVER application class. Table 100 PMW_APPSERVER Application Class InfoBox Items (Part 1 of 2) Item Server Offline Alarm Setting HTTP Transport Cell Node Description setting alarm if the application server goes offline, this will be either Enable or Disable host and port number (for each server) representing the HTTP transport cell name for the environment node name for the environment
428
Table 100 PMW_APPSERVER Application Class InfoBox Items (Part 2 of 2) Item Server Application Server Host Bootstrap Port Soap Port Server Version Description server name host name or IP address of the machine hosting the application server bootstrap port for finding name service port number for SOAP connections version of WebSphere Application Server running on the application server
PMW_CELL InfoBox
Table 101 lists the items beyond standard InfoBox items for the PMW_CELL application class. Table 101 PMW_CELL Application Class InfoBox Items Item Cell Deployment Manager Host Bootstrap Port Soap Port Server Version Description cell name for the environment host name or IP address for Deployment Manager local or remote connection bootstrap port for finding name service port number for SOAP connection version of WebSphere Application Server running on the cell manager
PMW_DATASOURCE InfoBox
Table 102 lists the items beyond standard InfoBox items for the PMW_DATASOURCE application class. Table 102 PMW_DATASOURCE Application Class InfoBox Items Item DB Driver Name DB Name DB URL Description name of the driver for this database name of this database URL for this database
Appendix E
Product InfoBoxes
429
Table 102 PMW_DATASOURCE Application Class InfoBox Items Item DB Node Name DB Drive Jar File JDBC Conn State Description name of the node associated with this jar file path and name of the .jar file associated with the connection to this database state of the collector monitoring this JDBC connection pool
PMW_DBURL InfoBox
Table 103 lists the items beyond standard InfoBox items for the PMW_DBURL application class. Table 103 PMW_DBURL Application Class InfoBox Items Item Database URL Description URL for this database
PMW_LOG InfoBox
Table 104 lists the items beyond standard InfoBox items for the PMW_LOG application class. Table 104 PMW_LOG Application Class InfoBox Items Item FileName Description path and file name for the log file being monitored in this application instance
PMW_NODE InfoBox
Table 105 lists the items beyond standard InfoBox items for the PMW_NODE application class. Table 105 PMW_NODE Application Class InfoBox Items Item Cell Node Node Agent Host
430
Description cell name for the environment node name for the environment host name or IP address of the machine hosting the node
Table 105 PMW_NODE Application Class InfoBox Items Item Bootstrap Port Soap Port JMS Server Bootstrap Port JMS Server SOAP Port Server Version Description bootstrap port for finding name service port number for SOAP connection bootstrap RMI port used for the JMS Server SOAP port used for the JMS Server version of WebSphere Application Server running on the application server
PMW_MAIN InfoBox
Table 99 lists the items beyond standard InfoBox items for the PMW_MAIN application class. Table 106 PMW_MAIN InfoBox Fields Item KM Version WebSphere Product Name WebSphere Product Edition WebSphere Product Version WebSphere Product Build WebSphere JDK Version Description version number of PATROL for WebSphere Application Server name of the monitored WebSphere installation edition of WebSphere being monitored version of WebSphere being monitored build of the WebSphere version being monitored version of the JDK used by WebSphere
PMW_SERVER_RESOURCES InfoBox
Table 107 lists the items beyond standard InfoBox items for the PMW_SERVER_RESOURCES application class. Table 107 PMW_SERVER_RESOURCES Application Class InfoBox Items Item Last Garbage Collection Start Last Garbage Collection End Description date and time that the most recent garbage collection started date and time that the most recent garbage collection was completed
Appendix E
Product InfoBoxes
431
JMX InfoBoxes
PMW_SETUP InfoBox
Table 108 lists the items beyond standard InfoBox items for the PMW_SETUP application class. Table 108 PMW_SETUP Application Class InfoBox Items Item KM Version KM Build Number Description version of PATROL for WebSphere Application Server currently running on this computer build number of the KM
JMX InfoBoxes
The application class InfoBoxes explained in this section are part of the JMX service that ships with the PATROL for WebSphere Application Server product. These application classes are available only with IBM WebSphere Application Server 5.x or later, and only if JMX has been enabled on the PATROL for WebSphere Application Server product. Each of these application classes begins with JMX_*.
JMX_CONDITION InfoBox
Table 109 describes the InfoBox available from the JMX_CONDITION icon. Table 109 JMX_CONDITION InfoBox Item Condition Name Monitored MBean(s) Monitored element Monitored condition Sampling frequency (seconds) PATROL instantiation Description assigned name for this condition names of one or more MBeans monitored by this condition part of the MBean being monitored criteria for monitoring frequency at which PATROL checks condition label on the icon for this instance, as it appears in the PATROL Console
432
JMX InfoBoxes
JMX_SERVER InfoBox
Table 110 describes the InfoBox available from the JMX_SERVER icon. Table 110 Item Client start time Client arguments JMX_SERVER InfoBox Description time that the JMX client communication with this server was started arguments passed to the client at startup; the format depends on the environment under which the MBean is running version of the JMX implementation under which the MBean Server is running name of the vendor who provided the JMX environment name of the JMX implementation, as provided by the JMX vendor unique identifier for the MBean server, as assigned by the JMX implementation when the server was initialized version of BMCs MBean, in the format vrmmbb (v=version, r=release, mm=modification, bb=build) file containing definitions; these are generally in PATROL_HOME, but may vary due to permission settings and the account under which the MBean server is running unique identifier for the BMC MBean; this is also used in the MBeans object name destination of all notifications captured from this server; this should correspond to the local host, port number on which the JMX listener is attached
JMX implementation version JMX implementation vendor JMX implementation name MBean server ID BMC MBean version BMC MBean condition def file
BMC MBean agent id BMC MBean notification target
Appendix E
Product InfoBoxes
433
JMX InfoBoxes
434
Appendix
Installed Files, Directories, and System Changes

F
This appendix describes how installing PATROL for WebSphere Application Server affects the computers on which it is installed. The appendix describes
I I I I
directories and files installed by the product processes and services installed and run by the product modifications to the Microsoft Windows registry additional files, processes, and applications required by the product
This appendix does not list files, directories, or other details for other PATROL components, such as the PATROL Agent or PATROL console. Main File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Objects and Dependencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directories and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processes and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microsoft Windows Registry Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product and Process Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 437 437 443 444 444
435
Main File Types
Main File Types

This section summarizes the main types of files that PATROL for WebSphere Application Server uses. Note that these same file types may be used differently by other applications, for example, not all .htm files are help files. Table 111 File Types By File Extension (Part 1 of 2) Comments used as help files used as help files, contains information about an application class lists the KMs that the .kml file loads contains data that the application references contains log data in plain text format contains plain text temporary archive file used by BMC Common Installer text of events data
File Extension File Type All Platforms .htm .jar .km .kml .lib .log .psl .txt .cat .ctg Windows .bat .bmp .bmk batch file bitmap image bitmap mask file HTML file Executable Jar file Knowledge Module file Knowledge Module List file library file log file uncompiled PATROL Script Language text file security catalog event catalog
contains icons for application classes used with PATROL Console for Windows. contains mask information for icons for application classes used with PATROL Console for Windows stored on PATROL Console Server (which might be a Unix computer), but used on PATROL Central Operator - Windows Edition used with PATROL Console for Windows contains data that the application references contains an executable file created automatically when a WinHelp file is opened
.chm
compiled HTML Help file
.cmd .cnt .dll .exe .gid
Microsoft Windows command file WinHelp Help contents file application extension application WinHelp temporary file
436
Product Objects and Dependencies
Table 111 .hlp .sys .tlb .vbe .vbs Unix .bin .sh *
File Types By File Extension (Part 2 of 2) Comments used with PATROL Console for Windows WinHelp Help file System file for device driver or hardware configuration Remote Automation OLE TypeLib files, Dynamic Link Library Visual Basic script Visual Basic for Applications script binary file shell script executable executes program instructions file extensions, or lack thereof, do not prevent Unix files from executing instructions
File Extension File Type

This section describes the directories, files, services, processes, and dependencies that belong to the PATROL for WebSphere Application Server files installation, including files and processes for the JVM profiling and byte-code instrumentation component and the JMX management component.
Directories and Files

This section lists directories and files that are laid down when you install PATROL for WebSphere Application Server. Most of these files and directories are created during installation of either the PATROL Agent or the PATROL for WebSphere Application Server KM. If a directory or file is created after installation, it is noted in the comments. Four tables are provided:
I I I I
Files installed on the Agent computer (Table 112) Files installed on the Console Server computer (Table 113) Files installed on the Console computer (Table 114) Common files installed on both Agents and Consoles (Table 115)
Appendix F
437
Table 112 Windows
Directories and Files Installed on a PATROL Agent Computer Comments
Directories and Files %BMC_ROOT%\Patrol3\Windows_NT-x86\pmw_WebSphere pmwconn.jar pmw.jar PMW_perflist.ini PMW_Version PMW_startClient.bat PMW_startJava.bat %BMC_ROOT%\Patrol3\Windows_NT-x86 PMW_Version PMW_startClient.bat %BMC_ROOT%\Patrol3\Windows_NT-x86\bin PMW_LogTail.exe %BMC_ROOT%\Patrol3\JMX jmxsupport.jar jmxbundle.jar jmx_startJava.bat Unix $BMC_ROOT/Patrol3/pmw_WebSphere pmwconn.jar pmw.jar PMW_startClient.sh PMW_startJava.sh PMW_Version PMW_perflist.ini $BMC_ROOT/Patrol3/JMX jmxsupport.jar jmxbundle.jar jmx_startJava.sh
438
Table 113 Windows
Directories and Files Installed on a PATROL Console Server Computer (Part 1 of 2) Comments
Directories and Files %BMC_ROOT%\lib\knowledge\pmw_2.4.00\lib\nls EN_USA\1031.cat, 1032.cat, 1034.cat JA_JPN\1031.cat, 1032.cat, 1034.cat KO_KOR\1031.cat, 1032.cat, 1034.cat ZH_CHN\1031.cat, 1032.cat, 1034.cat ZH_TWN\1031.cat, 1032.cat, 1034.cat %BMC_ROOT%\Patrol3\lib\knowledge\pmw_2.4.00\lib\help\ EN_USA pmw.chm EN_USA\pmw_2.4.00_en_usa.jar JA_JPN\pmw_2.4.00_en_usa.jar KO_KOR\pmw_2.4.00_en_usa.jar ZH_CHN\pmw_2.4.00_en_usa.jar ZH_TWN\pmw_2.4.00_en_usa.jar %BMC_ROOT%\Patrol3\lib\knowledge\jmx_1.1.05\lib\help\ EN_USA jmx.chm EN_USA\jmx_1.1.05_en_usa.jar JA_JPN\jmx_1.1.05_en_usa.jar KO_KOR\jmx_1.1.05_en_usa.jar ZH_CHN\jmx_1.1.05_en_usa.jar ZH_TWN\jmx_1.1.05_en_usa.jar %BMC_ROOT%\lib\knowledge\jmx_1.1.05 resource.mk4 package.mof %BMC_ROOT%\lib\knowledge\jmx_1.1.05 EN_USA\1033.cat JA_JPN\1033.cat KO_KOR\1033.cat ZH_CHN\1033.cat ZH_TWN\1033.cat
message catalogs, English message catalogs, Japanese message catalogs, Korean message catalogs, China message catalogs, Taiwan
help (PATROL Central Operator) help (PATROL Central Web), English
help (PATROL Central) help (PATROL Central Web), English
Appendix F
439
Table 113 Unix
Directories and Files Installed on a PATROL Console Server Computer (Part 2 of 2) Comments
Directories and Files $BMC_ROOT/lib/knowledge/pmw_2.4.00/lib/nls EN_USA/1031.cat, 1032.cat, 1034.cat JA_JPN/1031.cat, 1032.cat, 1034.cat KO_KOR/1031.cat, 1032.cat, 1034.cat ZH_CHN/1031.cat, 1032.cat, 1034.cat ZH_TWN/1031.cat, 1032.cat, 1034.cat $BMC_ROOT/lib/knowledge/jmx_1.1.05 resource.mk4 package.mof $BMC_ROOT/lib/knowledge/jmx_1.1.05 EN_USA/1033.cat JA_JPN/1033.cat KO_KOR/1033.cat ZH_CHN/1033.cat ZH_TWN/1033.cat
Table 114 Windows
Directories and Files Installed on a PATROL 3.x Console Computer (Part 1 of 2) Comments
Directories and Files %BMC_ROOT%\Patrol3\lib\images pmw*.bmk, jmx*.bmk pmw*.bmp, jmx*.bmp pmw*.msk, jmx*.msk pmw*.xpm, jmx*.xpm %BMC_ROOT%\Patrol3\lib\help\WinHelp km_help_pmw, km_help_jmx pmw.cnt, jmx.cnt pmw.hlp, jmx.hlp
for icons
help flag file help table of contents help (PATROL 3.x Console)
440
Table 114 Unix
Directories and Files Installed on a PATROL 3.x Console Computer (Part 2 of 2) Comments
Directories and Files $BMC_ROOT/Patrol3/lib/images pmw*.bmk, jmx*.bmk pmw*.bmp, jmx*.bmp pmw*.msk, jmx*.msk pmw*.xpm, jmx*.xpm $BMC_ROOT/Patrol3/lib/help/pmw *.gif *.htm $BMC_ROOT/Patrol3/lib/help pmw.hlp, jmx.hlp km_help_pmw, km_help_jmx
for icons
images for help help
NOTE
The files in Table 115 are installed on both the PATROL agent and console computers. These files are called common files.
Table 115
Common Directories and Files Installed Regardless of Computer Role (Part 1 of 2) Comments
Directories and Files Windows) %BMC_ROOT%\Patrol3\lib\kmmergemap pmw_2_3_00.map pmw_2_2_00.map pmw_2_1_00_40.map pmw_2_1_00_35.map pmw_2_1_00_01_35.map pmw_2_1_00_01_40.map pmw_2_1_01_35.map pmw_2_1_01_40.map jmx_1_1_00.map %BMC_ROOT%\Patrol3\lib\knowledge PMW.kml, JMX.kml PMW_*.km, JMX_*.km %BMC_ROOT%\Patrol3\lib\nls\C\103
merge map files for KM migration
KM list file knowledge module files
Appendix F
441
Table 115
Common Directories and Files Installed Regardless of Computer Role (Part 2 of 2) Comments catalog file, WebSphere catalog file, JMX PSL library files 1.cat 3.cat
Directories and Files
%BMC_ROOT%\Patrol3\lib\psl PMW_PjsCommonL.lib PMW_PjsSQLLib.lib PMW_PjsWebLib.lib PMW_BlackoutLib.lib JMX_Functions.lib JMX_Message.lib Unix $BMC_ROOT/Patrol3/lib/kmmergemap pmw_2_3_00.map pmw_2_2_00.map pmw_2_1_00_40.map pmw_2_1_00_35.map pmw_2_1_00_01_35.map pmw_2_1_00_01_40.map pmw_2_1_01_35.map pmw_2_1_01_40.map $BMC_ROOT/Patrol3/lib/knowledge PMW.kml, PMW_JVM_PROFILER.kml PMW_*.km $BMC_ROOT/Patrol3/lib/nls/C/103 1.cat, 4.cat $BMC_ROOT/Patrol3/lib/psl PMW_PjsCommonL.lib PMW_PjsSQLLib.lib PMW_PjsWebLib.lib PMW_BlackoutLib.lib PMW_StdLib.lib PMW_CommonLib.lib PMW_AppPerf.lib PSL library files catalog file KM list file knowledge module files merge map files for KM migration
442
Processes and Services

Table 116 lists processes and services that are specific to PATROL for WebSphere Application Server. It does not list other processes or services for other PATROL components, such as the PATROL Agent or PATROL console. All processes run on the Agent computer. There are no processes specifically launched by PATROL for WebSphere Application Server that are run on either Console or Console Server computers.
About JVM Process Names

Most of the processes launched by PATROL for WebSphere Application Server are JVM processes. All of the JVM processes include a tag that begins with the strings -Dpmw.channel or -Djmx.channel. This string is followed by the PATROL Agent port number, the PSL global channel name under which the process was launched, and the process start time in seconds since January 1, 1970 0:00 GMT. The tag follows the form: -Dpmw.channel=<port>@<channel>@<start time> Table 116 Process xmlMsgClient.xpc Processes Run by PATROL for WebSphere Application Server Function Non-JVM Processes collects instrumentation and profiling data; exists only if these options are enabled. The xmlMsgClient.xpc process collects all data for BCI and Advanced JVMPI and runs a low priority process that consumes idle CPU time to prepare the data before displaying it on PATROL. JVM Processes for WebSphere 5 and later JMX_Listener PMW_<environment> one instance is launched to handle JMX notifications and receive performance data one instance is launched for each registered environment; this process handles WebSphere discovery and requests and collects PMI data from WebSphere one instance is launched if the JMX component is activated via setup; this process handles JMX management component discovery and requests
JMX_websphere
Appendix F
443
Microsoft Windows Registry Modifications

PATROL for WebSphere Application Server does not modify the Windows Registry.
Product and Process Dependencies

For PATROL for WebSphere Application Server to operate correctly, certain additional BMC Software and third-party products and processes must be installed and running in the PATROL for WebSphere Application Server environment.
File and Process Dependencies

PATROL for WebSphere Application Server requires specific release and patch levels of the Java Runtime Environment (JRE). PATROL for WebSphere Application Server will not function properly without these third party files and processes. The complete list of specific JREs required for PATROL for WebSphere Application Server is in Chapter 2 of this user guide.
Application Dependencies
Any additional software products or components that PATROL for WebSphere Application Server requires are listed in Table 3 PATROL for WebSphere Application Server Installation Requirements on page 50.
444
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
Symbols
%PATROL_CACHE% 64 %PATROL_HOME% 64 alarms enabling and disabling on app servers 103 AllocatedHeaps (PMW_SERVER_RESOURCE) 331 AllocatedHeaps (PMW_SERVER_RESOURCES) 162 AnnotatedStatus (JMX_CONDITION) 383 application classes accessing Help on 45 descriptions 34 icons for 34 instance naming convention 45 See also PMW_* application monitoring 188 application server JVM performance report 163 application servers advanced monitoring options 158 blackout 168 enabling and disabling alarms 103 monitoring options 155 monitoriong options 105 starting and stopping 156 AppServer JVM Performance command 410 AppServerAvailability (PMW_APPSERVER) 155, 248 AppServerCollector (PMW_MAIN) 322 architecture application classes 23 data collection 26 AssuredPersistMsgConsumed (PMW_SIB_SERVICE) 351 AssuredPersistMsgConsumed (PMW_SIB_SUMMARY) 355 AssuredPersistMsgProduced (PMW_SIB_SERVICE) 351 AssuredPersistMsgProduced (PMW_SIB_SUMMARY) 355 AsynchRequestRate (PMW_WEBSERVICE) 365 AsynchRequestRate (PMW_WEBSERVICE_SUMMARY) 369 AsynchRequests (PMW_WEBSERVICE) 365 AsynchRequests (PMW_WEBSERVICE_SUMMARY) 369 AsynchResponseRate (PMW_WEBSERVICE) 365 AsynchResponses (PMW_WEBSERVICE) 365 AsynchResponses (PMW_WEBSERVICE_SUMMARY) 369 AsynchResponsesRate (PMW_WEBSERVICE_SUMMARY) 370 AuditMsgCount (PMW_RAS_MESSAGES) 327 availability resources 20 server 156
A
accessing KM Commands and InfoBoxes 437 account requirements Unix 53, 124 WebSphere Admin account 123 Windows 52, 128 action, defining for JMX 217 Activate JMX Management command 212, 413 Activate JVM Thread Object Collection command 396 active virtual host aliases pinging for availability 175 ActiveGlobalTrans (PMW_EJB_TRANSACTION) 302 ActiveLocalTrans (PMW_EJB_TRANSACTION) 302 ActiveMethods (PMW_BEANS) 249 ActiveMethods (PMW_EJB_SUMMARY) 293 ActiveSessions (PMW_SESSIONS) 345 ActiveThreads (PMW_SERVER_RESOURCE) 331 ActiveThreads (PMW_THREADPOOL) 361 ActiveThreads (PMW_THREADPOOL_SUMMARY) 363 ActiveTime (PMW_THREADPOOL) 361 Admin server, see WebSphere Admin 28 Advanced Monitoring Configuration command 396 AffinityBreakRate (PMW_SESSIONS) 346 AffinityBreaks (PMW_SESSIONS) 345 agent described 27 installing a KM to 56 AggregatedInvocationRate (PMW_DBURL) 284 AlarmCancelled (PMW_ALARM_MANAGER) 246 AlarmCancelled (PMW_ALARM_SUMMARY) 247 AlarmCreated (PMW_ALARM_MANAGER) 246 AlarmCreated (PMW_ALARM_SUMMARY) 247 AlarmFired (PMW_ALARM_MANAGER) 246 AlarmFired (PMW_ALARM_SUMMARY) 247 AlarmLatencyDuration (PMW_ALARM_MANAGER) 246 AlarmLatencyDuration (PMW_ALARM_SUMMARY) 247 AlarmPendingSize (PMW_ALARM_MANAGER) 246 AlarmPendingSize (PMW_ALARM_SUMMARY) 247 AlarmRate (PMW_ALARM_MANAGER) 246 AlarmRate (PMW_ALARM_SUMMARY) 247
Index
445
Availability (JMX_SERVER) 386 AvailableConsumedMessage (PMW_SIB_SERVICE) 351 AvailableConsumedMessage (PMW_SIB_SUMMARY) 355 AvailableServers (PMW_CLUSTER) 274 AvgDrainSize (PMW_BEANS) 249 AvgDrainSize (PMW_EJB_SUMMARY) 293 AvgHeldTime (PMW_J2C_FACTORY) 311 AvgHeldTime (PMW_J2C_SUMMARY) 315 AvgJDBCTime (PMW_DATASOURCE) 274 AvgJDBCTime (PMW_DBPOOLS_SUMMARY) 279 AvgPayloadSize (PMW_WEBSERVICE) 365 AvgPayloadSize (PMW_WEBSERVICE_SUMMARY) 370 AvgReplySize (PMW_WEBSERVICE) 366 AvgReplySize (PMW_WEBSERVICE_SUMMARY) 370 AvgRequestSize (PMW_WEBSERVICE) 366 AvgRequestSize (PMW_WEBSERVICE_SUMMARY) 370 AvgResponseTime (PMW_SQL) 360 AvgRespTime (PMW_DBURL) 285 AvgRespTime (PMW_SERVLET_GROUP) 341 AvgTimeHeld (PMW_DATASOURCE) 275 AvgTimeHeld (PMW_DBPOOLS_SUMMARY) 280 AvgWaitTime (PMW_DATASOURCE) 275 AvgWaitTime (PMW_DBPOOLS_SUMMARY) 280 AvgWaitTime (PMW_J2C_FACTORY) 311 AvgWaitTime (PMW_J2C_SUMMARY) 315 BeanMethodCalls (PMW_BEANS) 252 BeanMethodCalls (PMW_EJB_SUMMARY) 295 BeanMethodCallsPerSec (PMW_BEANS) 252 BeanMethodCallsPerSec (PMW_EJB_SUMMARY) 296 BeanMethodCallsRate (PMW_BEANS) 252 BeanMethodLoads (PMW_BEANS) 253 BeanMethodRT (PMW_BEANS) 253 BeanMethodRT (PMW_EJB_SUMMARY) 296 BeanPassivateRate (PMW_BEANS) 253 BeanPassivates (PMW_BEANS) 253 BeanPassivates (PMW_EJB_SUMMARY) 296 BeanPassivatesRate (PMW_EJB_SUMMARY) 296 BeanPassivateTime (PMW_BEANS) 253 BeanPassivateTime (PMW_EJB_SUMMARY) 297 BeanPoolSize (PMW_BEANS) 254 BeanPoolSize (PMW_EJB_SUMMARY)@@ 297 BeanRemoveRate (PMW_BEANS) 254 BeanRemoveRate (PMW_EJB_SUMMARY) 297 BeanRemoves (PMW_BEANS) 254 BeanRemoves (PMW_EJB_SUMMARY) 297 BeanRemoveTime (PMW_BEANS) 254 BeanRemoveTime (PMW_EJB_SUMMARY) 297 BeansActive (PMW_BEANS) 254 BeansActive (PMW_EJB_SUMMARY) 298 BeansLive (PMW_BEANS) 255 BeansLive (PMW_EJB_SUMMARY)@@ 298 BeanStoreRate (PMW_BEANS) 255 BeanStores (PMW_BEANS) 255 BeanStores (PMW_EJB_SUMMARY) 298 BeanStoresRate (PMW_EJB_SUMMARY) 298 BestEffortNonPersistMsgConsumed (PMW_SIB_SERVICE) 351 BestEffortNonPersistMsgConsumed (PMW_SIB_SUMMARY) 356 BestEffortNonPersistMsgProduced (PMW_SIB_SERVICE) 351 BestEffortNonPersistMsgProduced (PMW_SIB_SUMMARY) 356 binary files 435 Blackout commands 405 blackout application server 168 creating schedule 112 described 112 listing objects 115 performance considerations 139 Blackout commands 413 BMC Software, contacting 2 BooleanFalseCount (JMX_CONDITION) 383 BooleanTrueCount (JMX_CONDITION) 383 Bourne shell 74 bytecode instrumentation 22, 28, 188 deleting libraries 205 transaction monitoring 190, 191
B
backing up current installation before migration 67 BCICollector (PMW_ENVIRONMENT) 308 BeanActivateRate (PMW_BEANS) 250 BeanActivateRate (PMW_EJB_SUMMARY) 293 BeanActivates (PMW_BEANS) 250 BeanActivates (PMW_EJB_SUMMARY) 293 BeanActivateTime (PMW_BEANS) 250 BeanActivateTime (PMW_EJB_SUMMARY) 293 BeanCreateRate (PMW_BEANS) 250 BeanCreateRate (PMW_EJB_SUMMARY) 294 BeanCreates (PMW_BEANS) 250 BeanCreates (PMW_EJB_SUMMARY) 294 BeanCreateTime (PMW_BEANS) 251 BeanCreateTime (PMW_EJB_SUMMARY) 294 BeanDestroyRate (PMW_BEANS) 251 BeanDestroyRate (PMW_EJB_SUMMARY) 294 BeanDestroys (PMW_BEANS) 251 BeanDestroys (PMW_EJB_SUMMARY) 294 BeanInstantiateRate (PMW_BEANS) 251 BeanInstantiateRate (PMW_EJB_SUMMARY) 295 BeanInstantiates (PMW_BEANS) 251 BeanInstantiates (PMW_EJB_SUMMARY) 295 BeanLoadRate (PMW_EJB_SUMMARY) 295 BeanLoads (PMW_BEANS) 252 BeanLoads (PMW_EJB_SUMMARY) 295 BeanLoadsRate (PMW_BEANS) 252 BeanMethodCallRate (PMW_EJB_SUMMARY) 296
446
C
C shell 74 CacheDiscardRate (PMW_SESSIONS) 346 CacheDiscards (PMW_SESSIONS) 346 capabilities, see features cell-based management described 20, 29 local deployment manager 31 local node 31 remote application server 32 remote deployment manager 32 Clear ALARM or WARN State command 405 ClearedHungThread (PMW_THREADPOOL) 361 client, Java 28 ClientRequestRate (PMW_CACHE_SUMMARY) 259 ClientRequestRate (PMW_CACHE_TEMPLATE) 266 ClientRequests (PMW_CACHE_SUMMARY) 259 ClientRequests (PMW_CACHE_TEMPLATE 266 ClientsConnectToServer (PMW_SIB_SERVICE) 351 ClientsConnectToServer (PMW_SIB_SUMMARY) 356 CoalesceTime (PMW_DCS) 286 CoalesceTime (PMW_DCS_SUMMARY) 289 collectors 26 Java client 28 tuning 201, 212, 213, 217, 218 colormap option 73 command line interface 170 commands accessing 437 CommunicationErrors (PMW_SIB_SERVICE) 352 CommunicationErrors (PMW_SIB_SUMMARY) 356 ConcurrentHungThread (PMW_THREADPOOL) 361 ConcurrentWaiters (PMW_DATASOURCE) 275 ConcurrentWaiters (PMW_DBPOOLS_SUMMARY) 280 condition JMX, defining 210, 213 configuration variables tuning 140 Configure HTTPTransport Connection Info command 157 Configure Method Profiling Class command 396 Configure VHost Alias Ping List command 411 configuring advanced tuning 140 Java classes 165 method profiling 165 PATROL for WebSphere Application Server 87 troubleshooting setup problems 118 ConnectionAllocateRate (PMW_DATASOURCE) 275 ConnectionAllocateRate (PMW_DBPOOLS_SUMMARY) 281 ConnectionAllocates (PMW_DATASOURCE) 275 ConnectionAllocates (PMW_DBPOOLS_SUMMARY) 280 ConnectionCreateRate (PMW_DATASOURCE) 276 ConnectionCreateRate (PMW_DBPOOLS_SUMMARY) 281 ConnectionCreates (PMW_DATASOURCE) 276
ConnectionCreates (PMW_DBPOOLS_SUMMARY) 281 ConnectionDestroyRate (PMW_DATASOURCE) 276 ConnectionDestroyRate (PMW_DBPOOLS_SUMMARY) 281 ConnectionDestroys (PMW_DATASOURCE) 276, 277 ConnectionDestroys (PMW_DBPOOLS_SUMMARY) 281 ConnectionErrors (PMW_SIB_SERVICE) 352 ConnectionErrors (PMW_SIB_SUMMARY) 356 ConnectionFaultRate (PMW_DATASOURCE) 277 ConnectionFaultRate (PMW_DBPOOLS_SUMMARY) 282 ConnectionFaultRate (PMW_J2C_FACTORY) 311 ConnectionFaults (PMW_DATASOURCE) 276 ConnectionFaults (PMW_DBPOOLS_SUMMARY) 282 ConnectionFaults (PMW_J2C_FACTORY) 311 ConnectionFaults (PMW_J2C_SUMMARY) 315 ConnectionFaultsRate (PMW_J2C_SUMMARY) 315 ConnectionReturnRate (PMW_DATASOURCE) 277 ConnectionReturnRate (PMW_DBPOOL_SUMMARY) 282 ConnectionReturns (PMW_DATASOURCE) 277 ConnectionReturns (PMW_DBPOOL_SUMMARY) 282 ConnectionsAllocated (PMW_J2C_FACTORY) 312 ConnectionsAllocated (PMW_J2C_SUMMARY) 315 ConnectionsAllocatedRate (PMW_J2C_FACTORY) 312 ConnectionsAllocatedRate (PMW_J2C_SUMMARY) 316 ConnectionsCreated (PMW_J2C_FACTORY) 312 ConnectionsCreated (PMW_J2C_SUMMARY) 316 ConnectionsCreatedRate (PMW_J2C_FACTORY) 312 ConnectionsCreatedRate (PMW_J2C_SUMMARY) 316 ConnectionsDestroyed (PMW_J2C_FACTORY) 312 ConnectionsDestroyed (PMW_J2C_SUMMARY) 316 ConnectionsDestroyedRate (PMW_J2C_FACTORY) 313 ConnectionsDestroyedRate (PMW_J2C_SUMMARY) 316 ConnectionsFreed (PMW_J2C_FACTORY) 313 ConnectionsFreed (PMW_J2C_SUMMARY) 317 ConnectionsFreedRate (PMW_J2C_FACTORY) 313 ConnectionsFreedRate (PMW_J2C_SUMMARY) 317 ConnectionsInUse (PMW_DBPOOLS_SUMMARY) 283 ConnectionsInUse (PMW_J2C_FACTORY) 313 ConnectionsInUse (PMW_J2C_SUMMARY) 317 ConnectionWaiters (PMW_J2C_FACTORY) 313 ConnectionWaiters (PMW_J2C_SUMMARY) 317 console described 27 installing a KM to 55 saving the settings 88 console systems overview 55, 56 containers, application 33 conventions, for naming application instances 45 CpuPercent (PMW_SERVER_RESOURCE) 331 CpuUtilization (PMW_SERVER_RESOURCE) 162, 332 CurrentEntries (PMW_CACHE_SUMMARY) 259 CurrentEntries (PMW_CACHE_TEMPLATE) 267 CurrentEntriesInMemory (PMW_CACHE_SUMMARY) 259 CurrentEntriesInMemory (PMW_CACHE_TEMPLATE) 267
Index
447
custom installation option 58 customer support 3 DrainsFromPoolRate (PMW_BEANS) 255 DrainsFromPoolRate (PMW_EJB_SUMMARY) 299
D
data collection, see collectors data flow, collection 26 database registering data source connection 146 database monitoring 23 Database URL InfoBox item 430 DataSource_Col (PMW_DATASOURCE) 277 DB Drive Jar File InfoBox item 430 DB Driver Name InfoBox item 429 DB Name InfoBox item 429 DB Node Name InfoBox item 430 DB URL InfoBox item 429 DbFreePoolSize (PMW_DATASOURCE) 278 DbFreePoolSize (PMW_DBPOOLS_SUMMARY) 283 DbPercentMaxed (PMW_DATASOURCE) 278 DbPercentMaxed (PMW_DBPOOLS_SUMMARY) 283 DbPoolSize (PMW_DATASOURCE) 278 DbPoolSize (PMW_DBPOOLS_SUMMARY) 283 DbUrlCollector (DBURL) 389 DbUrlCollector (PMW_DBURL) 285 DbUrlsDisc (PMW_APPSERVER) 248 Deactivate JMX Management command 413 Deactivate JVM Thread Object Collection command 396 debug JMX 119, 223 trace flag 119 Debug Options command 413 default login shell 59 Define Conditions command 418 Define Log Monitor Rules command 405 deleting old version 69 demonstration license 52 deployment manager defined 29 directories 435 disabling alarms 103 disabling instrumentation 105 disabling profiling 105 discovery verifying 116, 118 DLL, conflict 118 DMgrAvailability (PMW_CELL) 274 documentation 46 DrainsFromPool (PMW_BEANS) 255 DrainsFromPool (PMW_EJB_SUMMARY) 298
E
EJB management, described 21 method-level monitoring 185 monitoring 183, 193 profiling 197 transactions 184 EJBRequestRate (PMW_J2EE_OBJ) 318 EJBResponseReport (PMW_J2EE_OBJ) 319 EJBResponseTime (PMW_J2EE_OBJ) 319 e-mail JMX monitoring 212 enabling alarms on application servers 103 enabling instrumentation 105 enabling profiling 105 end-to-end response time 18 environment variable PATROL_CACHE 64 PATROL_HOME 64 environment variables LANG 74 PATH 74 PATROL_BROWSER 74 setting for Help browser 74 setting for the browser 74 EPM performance level 137 ErrorMsgCount (PMW_RAS_MESSAGES) 327 event log monitoring, defining rules 233 eXceed 74 executables 435 expireInactivityCollCycles configuration variable 141 ExplicitInvalidationRate (PMW_CACHE_SUMMARY) 260 ExplicitInvalidations (PMW_CACHE_SUMMARY) 259 ExplicitInvalidations (PMW_CACHE_TEMPLATE) 267 ExplicitInvalidationsRate (PMW_CACHE_SUMMARY) 267 ExplicitInvDisk (PMW_CACHE_SUMMARY) 260 ExplicitInvDisk (PMW_CACHE_TEMPLATE) 268 ExplicitInvDiskRate (PMW_CACHE_SUMMARY) 260 ExplicitInvDiskRate (PMW_CACHE_TEMPLATE) 268 ExplicitInvLocal (PMW_CACHE_SUMMARY) 260 ExplicitInvLocal (PMW_CACHE_TEMPLATE) 268 ExplicitInvLocalRate (PMW_CACHE_SUMMARY) 261 ExplicitInvLocalRate (PMW_CACHE_TEMPLATE) 268 ExplicitInvMemory (PMW_CACHE_SUMMARY) 261 ExplicitInvMemory (PMW_CACHE_TEMPLATE) 269 ExplicitInvMemoryRate (PMW_CACHE_SUMMARY) 261 ExplicitInvMemoryRate (PMW_CACHE_TEMPLATE) 269 ExplicitInvNoEntry (PMW_CACHE_SUMMARY) 261 ExplicitInvNoEntry (PMW_CACHE_TEMPLATE) 269 ExplicitInvNoEntryRate (PMW_CACHE_SUMMARY) 262
448
ExplicitInvNoEntryRate (PMW_CACHE_TEMPLATE) 269 ExplicitInvRemote (PMW_CACHE_SUMMARY) 262 ExplicitInvRemote (PMW_CACHE_TEMPLATE) 270 ExplicitInvRemoteRate (PMW_CACHE_SUMMARY) 262, 270 ExpressNonPersistMsgConsume (PMW_SIB_SERVICE) 352 ExpressNonPersistMsgConsume (PMW_SIB_SUMMARY) 356, 357 extension, file name 436 ExternalReadSize (PMW_SESSIONS) 346, 347 ExternalWriteSize (PMW_SESSIONS) 347 ExternalWriteTime (PMW_SESSIONS) 347 GetsFromPoolRate (PMW_BEANS) 256 GetsFromPoolRate (PMW_EJB_SUMMARY) 299 global security 130 overview 122 GlobalBeforeCompletionDuration 302 GlobalCommitDuration 302 GlobalPrepareDuration (PMW_EJB_TRANSACTION) 303 GlobalTransBegun (PMW_EJB_TRANSACTION) 303 GlobalTransBegunRate (PMW_EJB_TRANSACTION) 303 GlobalTransCommitted (PMW_EJB_TRANSACTION) 303 GlobalTransCommittedRate (PMW_EJB_TRANSACTION) 303 GlobalTransDuration (PMW_EJB_TRANSACTION) 304 GlobalTransInvolved (PMW_EJB_TRANSACTION) 304 GlobalTransInvolvedRate (PMW_EJB_TRANSACTION) 304 GlobalTransRolledBack (PMW_EJB_TRANSACTION) 304 GlobalTransRolledBackRate (PMW_EJB_TRANSACTION) 304 GlobalTransTimeout (PMW_EJB_TRANSACTION) 305 GlobalTransTimeoutRate (PMW_EJB_TRANSACTION) 305
F
FailedTasks (PMW_SCHEDULER) 328 FailedTasks (PMW_SCHEDULER_SUMMARY) 329 FatalMsgCount (PMW_RAS_MESSAGES) 327 features 18 file permissions 123 FileName InfoBox item 430 files installed by product 435 type 436 filter, log file messages 234 firewalls HTTP server status not validated across 175 first-time installation typical installation option 58 flag debug trace 119 FreeConnections (PMW_J2C_FACTORY) 314 FreeConnections (PMW_J2C_SUMMARY) 317 FreeMemory (PMW_SERVER_RESOURCE) 332
H
HeapsInUse (PMW_SERVER_RESOURCE) 333 Help, accessing online 45 hierarchy application classes 23 HighCummulativeTime (PMW_SERVLET_GROUP) 341 HighestCpuThread (PMW_SERVER_RESOURCE) 333 HighestInvocationRate (PMW_DBURL) 285 HighestInvocations (PMW_DBURL) 285 HighestPriorityRecvdMsgSize (PMW_SIB_SERVICE) 352 HighestPriorityRecvdMsgSize (PMW_SIB_SUMMARY) 357 HighestPrioritySentMsgSize (PMW_SIB_SERVICE) 353 HighestPrioritySentMsgSize (PMW_SIB_SUMMARY) 357 HighSeverityCongestionEvent (PMW_DCS) 287 HighSeverityCongestionEvent (PMW_DCS_SUMMARY) 289 HighUsed (PMW_SERVLET_GROUP) 341 HighUsedRate (PMW_SERVLET_GROUP) 341 HitsInMemory (PMW_CACHE_SUMMARY) 262 HitsInMemory (PMW_CACHE_TEMPLATE) 270 HitsInMemoryRate (PMW_CACHE_SUMMARY) 263 HitsInMemoryRate (PMW_CACHE_TEMPLATE) 270 HitsOnDisk (PMW_CACHE_SUMMARY) 263 HitsOnDisk (PMW_CACHE_TEMPLATE) 271 HitsOnDiskRate (PMW_CACHE_SUMMARY) 263 HitsOnDiskRate (PMW_CACHE_TEMPLATE) 271 HTTP server status not validated across firewalls 175 HTTP servers pinging for connection to 175 HTTPTransportConnState (PMW_APPSERVER) 157, 248
G
garbage collection, parameters JVM runtime statistics 162 GarbageCollectionDuration (PMW_SERVER_RESOURCE) 332 GarbageCollectionInterval (PMW_SERVER_RESOURCE) 332 GarbageCollectionObjectsInUsed (PMW_SERVER_RESOURCE) 332 GarbageCollectionRate (PMW_SERVER_RESOURCE) 333 GarbageCollections (PMW_SERVER_RESOURCE) 333 GetsFound (PMW_BEANS) 256 GetsFound (PMW_EJB_SUMMARY) 299 GetsFoundRate (PMW_BEANS) 256 GetsFoundRate (PMW_EJB_SUMMARY) 299 GetsFromPool (PMW_BEANS) 256 GetsFromPool (PMW_EJB_SUMMARY) 299
Index
449
I
icons defined 34 naming conventions 45 organization of 24 setup 33 WebSphere 33 IdlePoolSize (PMW_OBJECT_POOL) 323 IdlePoolSize (PMW_OBJECT_SUMMARY) 324 IncomingMessageSize (PMW_DCS) 287 IncomingMessageSize (PMW_DCS_SUMMARY) 289 IncompletedPublication (PMW_SIB_SERVICE) 353 IncompletedPublication (PMW_SIB_SUMMARY) 357 IncompletedReads (PMW_SIB_SERVICE) 353 IncompletedReads (PMW_SIB_SUMMARY) 357 IncompletedWrites (PMW_SIB_SERVICE) 353 IncompletedWrites (PMW_SIB_SUMMARY) 358 InfoBoxes, accessing 437 InfoMsgCount (PMW_RAS_MESSAGES) 327 Initial Setup ... command 412 installation backing up before migration 67 custom option 58 quick start overview 61 typical option 58 Unix account requirements 53 Windows account requirements 52 installation prerequisites 54 installation utility determining the version 54 version 54 installing clearing cache 69 instance naming convention 45 instrumentation deleting libraries 205 enabling 105 using 197 InvalidatedSessionRate (PMW_SESSIONS) 348 InvalidatedSessions (PMW_SESSIONS) 347 InvalidatedSessionsPerSec (PMW_SESSIONS) 348 InvocationRate (PMW_SERVLET_GROUP) 341 InvocationRate (PMW_SQL) 360 InvReqNonExistent (PMW_SESSIONS) 348 InvReqNonExistentRate (PMW_SESSIONS) 348 InvReqTimeout (PMW_SESSIONS) 348 InvReqTimeoutRate (PMW_SESSIONS) 349
JDBC connection state 147 monitoring 146, 149 JDBC Conn State InfoBox item 430 JDBCConnectState (PMW_DATASOURCE) 147, 278 JMSServerAvailability (PMW_NODE) 323 JMX activating 211 advanced features 220 condition 224 debug 223 management, described 22, 28 management, using 209 monitoring MBeans 210 JMX listener described 30 port requirements 51 JMX_CONDITION described 44 InfoBox 432 parameters 383 JMX_DOMAIN described 44 parameters 385 JMX_MAIN described 44 parameters 386 JMX_SERVER described 44 InfoBox 433 parameters 386 JoinViewChangeTime (PMW_DCS) 287 JoinViewChangeTime (PMW_DCS_SUMMARY) 289 JSP monitoring 193 JVM memory allocation 162 performance report 163 process names 443 profiling features, using 204 profiling, described 22 JVMCollector (PMW_SERVER_RESOURCE) 333 JVMRequestRate (PMW_CACHE_SUMMARY) 263 JVMRequestRate (PMW_CACHE_TEMPLATE) 271 JVMRequests (PMW_CACHE_SUMMARY) 263, 271
K
KM loading 88 see also application classes KM Setup commands 412 KM Version displayed in PMW_SETUP InfoBox 432 KM version 431
J
Java client 28, 30 Java method profiling configuring classes 165 enabling and disabling 105 Java Virtual Machine, see JVM
450
KMs installing individual 58 Korn shell 74 scanning 231 viewing 236 LogFileSize (PMW_LOG) 232, 321 LogGrowthSize (PMW_LOG) 232 LogGrowthSize(PMW_LOG) 322 login shell default 59 LogMessages (PMW_LOG) 322 LogMonitorCollector (PMW_LOG) 322 LogMonitorStatus (PMW_LOG) 322 LogReadDefer configuration variable 141 logScanMaxSize configuration variable 142 LogSizeCollector (PMW_LOG) 322 LowestPriorityRecvdMsgSize (PMW_SIB_SERVICE) 353 LowestPriorityRecvdMsgSize (PMW_SIB_SUMMARY) 358 LowestPrioritySentMsgSize (PMW_SIB_SERVICE) 354 LowestPrioritySentMsgSize (PMW_SIB_SUMMARY) 358 LruInvalidationRate (PMW_CACHE_TEMPLATE) 272 LruInvalidations (PMW_CACHE_SUMMARY) 264 LruInvalidations (PMW_CACHE_TEMPLATE) 272 LruInvalidationsRate (PMW_CACHE_SUMMARY) 264
L
label instance naming conventions 45 LANG environment variable 74 Last Garbage Collection End InfoBox item 431 Last Garbage Collection Start InfoBox item 431 library advanced monitoring, removing 205 license demonstration 52 permanent 52 List Blackout Objects command 169, 405, 413 LiveSessions (PMW_SESSIONS) 349 load KM 88 LoadedServices (PMW_WEBSERVICE) 366 LoadedServices (PMW_WEBSERVICE_SUMMARY) 370 local deployment manager, described 31 local node environment, described 31 LocalBeforeCompletionDuration (PMW_EJB_TRANSACTION) 305 LocalCommitDuration (PMW_EJB_TRANSACTION) 305 LocalGroups (PMW_HA_MANAGER) 308 LocalGroups (PMW_HA_SUMMARY) 309 LocalMessageRetransmission (PMW_DCS) 287 LocalMessageRetransmission (PMW_DCS_SUMMARY) 290 LocalSubject (PMW_HA_MANAGER) 308 LocalSubject (PMW_HA_SUMMARY) 310 LocalSubscription (PMW_HA_MANAGER) 308 LocalSubscription (PMW_HA_SUMMARY) 310 LocalTransBegun (PMW_EJB_TRANSACTION) 305 LocalTransBegunRate (PMW_EJB_TRANSACTION) 306 LocalTransCommitted (PMW_EJB_TRANSACTION) 306 LocalTransCommittedRate (PMW_EJB_TRANSACTION) 306 LocalTransDuration (PMW_EJB_TRANSACTION) 306 LocalTransRolledBack (PMW_EJB_TRANSACTION) 306 LocalTransRolledBackRate (PMW_EJB_TRANSACTION) 307 LocalTransTimeout (PMW_EJB_TRANSACTION) 307 LocalTransTimeoutRate (PMW_EJB_TRANSACTION) 307 LockWaitRate (PMW_SERVER_RESOURCE) 334 LockWaits (PMW_SERVER_RESOURCE) 334 LockWaitTime (PMW_SERVER_RESOURCE) 334 log file monitoring 229 pattern matching 138, 233 performance considerations 230 rewinding 237
M
maintenance period, see blackout Manage MBeans command 418 managed systems overview 56 ManagedConnectionInUse (PMW_J2C_SUMMARY) 318 ManagedConnectionsInUse 314 ManagedConnectionsInUse (PMW_DATASOURCE) 278 ManagedConnectionsInUse (PMW_DBPOOLS_SUMMARY) 283 manuals, see documentation MaxEntriesInMemory (PMW_CACHE_SUMMARY) 264 MaxEntriesInMemory (PMW_CACHE_TEMPLATE) 272 MaxSessionsExceeded (PMW_SESSIONS) 349 MaxSessionsExceededRate (PMW_SESSIONS) 349 MBean defining conditions 220 manually registering 220 MBeanCount (JMX_CONDITION) 383 MBeanCount (JMX_DOMAIN) 385 MBeanCount (JMX_SERVER) 386 MBeans monitoring 210 MediatedThread (PMW_SIB_SERVICE) 354 MediatedThread (PMW_SIB_SUMMARY) 358 MediationTime (PMW_SIB_SERVICE) 354 MediationTime (PMW_SIB_SUMMARY) 358 memory JVM allocations 162 MessageBufferReallocation (PMW_DCS) 287 MessageBufferReallocation (PMW_DCS_SUMMARY) 290 MessageCollector (PMW_MAIN) 323
Index
451
MessageEngineConnectToServer (PMW_SIB_SERVICE) 354 MessageEngineConnectToServer (PMW_SIB_SUMMARY) 358 Messages (PMW_ENVIRONMENT) 308 method profiling servlet profiling 197 MethodCallRate (PMW_EJB_METHOD) 292 MethodCalls (PMW_EJB_METHOD) 292 MethodCalls (PMW_PROF_METHOD) 326 MethodCalls (PMW_SERVLET_METHOD) 343 MethodCallsPerSec (PMW_EJB_METHOD) 292 MethodCallsPerSec (PMW_PROF_METHOD) 326 MethodCallsPerSec (PMW_SERVLET_METHOD) 343 MethodConcurrentCalls (PMW_EJB_METHOD) 292 MethodCpu (PMW_PROF_METHOD) 327 MethodRT (PMW_EJB_METHOD) 292 MethodRT (PMW_PROF_METHOD) 327 MethodRT (PMW_SERVLET_METHOD) 343 migration backing up current installation before 67 Misses (PMW_CACHE_SUMMARY) 264 Misses (PMW_CACHE_TEMPLATE) 272 MissRate (PMW_CACHE_SUMMARY) 265 MissRate (PMW_CACHE_TEMPLATE) 273 Modify Condition command 417 Modify JDBC Connection Info command 399 Monitor EJB command 194 Monitor Options ... command 413 Monitor Servlet/JSP command 193 Monitor Transactions command 190 monitorAppServerObjects configuration variable 143 monitoring mode setting 103 monitoring options setting 105 specifying for app servers 105 monitoring services specifying 106 MostCumulativeTime (PMW_DBURL) 285 MsgsBackedOut (PMW_BEANS) 256 MsgsBackedOut (PMW_EJB_SUMMARY) 300 MsgsBackedOutRate (PMW_BEANS) 257 MsgsBackedOutRate (PMW_EJB_SUMMARY) 300 MsgsDelivered (PMW_BEANS) 257 MsgsDelivered (PMW_EJB_SUMMARY) 300 MsgsDeliveredRate (PMW_BEANS) 257 MsgsDeliveredRate (PMW_EJB_SUMMARY) 300 new PATROL users easy install option 58 NodeAgentAvailability (PMW_NODE) 323 NTRegistry.dll file 118
O
ObjectAllocated (PMW_OBJECT_POOL) 324 ObjectAllocated (PMW_OBJECT_SUMMARY) 324 ObjectCreated (PMW_OBJECT_POOL) 324 ObjectCreated (PMW_OBJECT_SUMMARY) 324 ObjectLookupTime (PMW_ORB_SUMMARY) 325 ObjectReturned (PMW_OBJECT_POOL) 324 ObjectReturned (PMW_OBJECT_SUMMARY) 325 ObjectsAllocated (PMW_SERVER_RESOURCE) 334 ObjectsAllocatedRate (PMW_SERVER_RESOURCE) 334 ObjectsFreed (PMW_SERVER_RESOURCE) 335 ObjectsFreedRate (PMW_SERVER_RESOURCE) 335 ObjectsInUse (PMW_SERVER_RESOURCE) 335 ObjectsMoved (PMW_SERVER_RESOURCE) 335 ObjectsMovedRate (PMW_SERVER_RESOURCE) 335 online Help installing 56 online Help, accessing 45 operating system requirements 50 operating systems supported 50 OptimizationRate (PMW_EJB_TRANSACTION) 307 Optimizations (PMW_EJB_TRANSACTION) 307 ORBInterceptTime (PMW_ORB_INTERCEPTOR) 325 ORBInterceptTime (PMW_ORB_SUMMARY) 325 ORBRequestRate (PMW_ORB_SUMMARY) 325 ORBRequests (PMW_ORB_SUMMARY) 326 ORBRequestsActive (PMW_ORB_SUMMARY) 326 OutgoingMessageSize (PMW_DCS) 287 OutgoingMessageSize (PMW_DCS_SUMMARY) 290 overview of product 18
P
Parameter Selection dialog box 108 parameters accessing Help on 45 transaction monitoring 189 PATH environment variable 74 PATROL Agent described 27 installing a KM to 56 PATROL Agent, required versions 50 PATROL Central Operator - Web Edition installing 56 PATROL Console and Netscape Navigator 73 described 27 installing a KM to 55
N
naming conventions for application instances 45 Netscape Navigator 73 network management, see cell-based management
452
saving the configuration 88 PATROL Console, required versions 50 PATROL Event Manager 233 PATROL for IBM WebSphere description of 18 features 18 PATROL for WebSphere Application Server configuring 87 loading 88 PATROL security 132 PATROL_BROWSER variable 74 PATROL_BROWSER environment variable 74 PATROL_CACHE 64, 69 PATROL_HOME 64 PatrolCli tool 170 pattern log file 138, 233 PeakNTRealMemory (PMW_SERVER_RESOURCE) 336 PeakNTVirtualMemory (PMW_SERVER_RESOURCE) 336 PercentMaxed (PMW_J2C_FACTORY) 314, 318 PercentMemoryUsed (PMW_SERVER_RESOURCES) 336 PercentUsed (PMW_DATASOURCE) 279 PercentUsed (PMW_DBPOOLS_SUMMARY) 284 PercentUsed (PMW_J2C_FACTORY) 314 PercentUsed (PMW_J2C_SUMMARY) 318 PerfCollector (ENVIRONMENT) 386 PerfCollector (PMW_ENVIRONMENT) 308 PerfCollector2 135 PerfCollector2 (APPSERVER) 386 PerfCollector2 (PMW_APPSERVER) 248 performance tuning for large sites 140 Performance Collector Report command 186, 397, 399, 401, 402, 404, 405, 407, 410, 411, 415, 416 performance data collection setting 105 performance data level 135 Performance Data Selection ... command 413 Performance Data Selection dialog box 106, 107 sections explained 107 performance monitoring options specifying 105 performance report JVM 163 permanent license 52 permissions security considerations 124 permissions for WebSphere Admin OS account 123 Ping Application Server command 156, 396 Ping Deployment Manager command 398 Ping JDBC Connection command 148, 398 Ping Node Agent command 406 Ping Virtual Host Aliases command validating HTTP server status 177 Ping Virtual Hosts command 411 PjsClassMethodDiscCol (PMW_PROF_CLASS) 326 PjsClassNameDisc (PMW_APPSERVER) 248 PjsMethodProfileDisc (PMW_APPSERVER) 249 PjsServletClassCol (PMW_SERVLET_GROUP) 342 PjsServletClassCol (SERVLET_GROUP) 389 PjsServletMethodDisc (PMW_APPSERVER) 249 PjsWebAppTopNCol (PMW_SERVLET_GROUP) 342 PjsWebAppTopNCol (SERVLET_GROUP) 389 platforms supported 49 PMI defined 28 described 21 PmiLevel (PMW_BEANS) 249 PMW.kml 88 PMW_ALARM_MANAGER commands 395 parameters 246 PMW_ALARM_SUMMARY commands 396 description 35 parameters 247 PMW_ALARMMGR_GROUP commands 395 description 35 PMW_ALARMMGR_GRP description 35 PMW_APPSERVER commands 396 description 35 InfoBox 428 parameters 248 PMW_BEANS commands 397 description 38 parameters 249 PMW_BLACKOUT description 35 parameters 258 PMW_BlackoutCollector (PMW_BLACKOUT) 258 PMW_CACHE commands 397 description 36 PMW_CACHE_SUMMARY commands 397 description 36 parameters 259, 266 PMW_CACHE_TEMPLATE commands 397 description 36 PMW_CELL commands 398 description 35 InfoBox 429 parameters 274 PMW_CHANNEL description 36 PMW_CLUSTER
Index
453
commands 398 description 35 parameters 274 PMW_DATASOURCE commands 398 description 36 InfoBox 429 parameters 274 PMW_DBPOOLS commands 399 description 36 PMW_DBPOOLS_SUMMARY commands 399 description 36 parameters 279 PMW_DBPROVIDER description 36 PMW_DBURL commands 400 description 37 InfoBox 430 parameters 284 PMW_DBURLS commands 400 description 37 parameters 286 PMW_DCS commands 400 description 37 parameters 286 PMW_DCS_GROUP commands 400 description 37 PMW_DCS_SUMMARY commands 401 description 37 parameters 289 PMW_EJB_CONTAINER commands 401 description 38 PMW_EJB_GROUP commands 401 description 37 PMW_EJB_JAR description 37 PMW_EJB_METHOD commands 402 description 38 parameters 292 PMW_EJB_SUMMARY commands 402 description 37 parameters 293 PMW_EJB_TRANSACTION commands 402 description 38 parameters 302 PMW_ENVIRONMENT description 34 parameters 308 PMW_HA_GROUP commands 402 description 38 PMW_HA_MANAGER commands 403 parameters 308, 309 PMW_HA_SUMMARY commands 403 description 38 PMW_J2C commands 403 description 39 PMW_J2C_FACTORY commands 403 description 39 parameters 311 PMW_J2C_SUMMARY commands 404 description 39 parameters 315 PMW_J2EE_GROUP commands 404 description 39 PMW_J2EE_OBJ commands 404 description 39 parameters 318 ReqMetrics instance 189 PMW_LOG commands 405 description 39 InfoBox 430 parameters 321 PMW_LOG_GROUP description 39 PMW_MAIN commands 405 description 34 InfoBox 431 parameters 322 PMW_NODE commands 406 description 34 InfoBox 430 parameters 323 PMW_OBJECT_GROUP commands 406 description 39 PMW_OBJECT_POOL commands 407 description 40 parameters 323 PMW_OBJECT_SUMMARY commands 407
454
description 40 parameters 324 PMW_ORB commands 407 description 40 PMW_ORB_INTERCEPTOR commands 408 description 40 parameters 325 PMW_ORB_SUMMARY commands 408 description 40 parameters 325 PMW_PROF_CLASS commands 408 parameters 326 PMW_PROF_METHOD parameters 326 PMW_RAS_MESSAGES description 40 parameters 327 PMW_SCHEDULER commands 408 description 40 parameters 328 PMW_SCHEDULER_SERVICES commands 409 description 40 PMW_SCHEDULER_SUMMARY commands 409 description 41 parameters 329 PMW_SERVER_LOGS description 41 PMW_SERVER_RESOURCES commands 410 description 41 InfoBox 431 parameters 331 PMW_SERVLET commands 410 description 41 parameters 338 PMW_SERVLET_CONTAINER description 41 PMW_SERVLET_ENGINE commands 410 description 41 parameters 340 PMW_SERVLET_GROUP commands 411 description 41 parameters 341 PMW_SERVLET_METHOD description 42 parameters 343 PMW_SERVLET_SUMMARY commands 411 description 42 parameters 343 PMW_SESSIONS commands 411 description 41 parameters 345 PMW_SETUP commands 412 description 34 InfoBox 432 PMW_SIB_GROUP commands 414 described 42 PMW_SIB_SERVICE commands 414 described 42 parameters 351 PMW_SIB_SUMMARY described 42 parameters 355 PMW_SQL commands 414 description 42 parameters 360 PMW_THREADPOOL commands 415 description 43 parameters 361 PMW_THREADPOOL_GROUP commands 415 description 43 PMW_THREADPOOL_SUMMARY commands 415 description 43 parameters 363 PMW_WEBSERVICE commands 415 description 43 parameters 365, 369 PMW_WEBSERVICE_GROUP commands 416 description 43 PMW_WEBSERVICE_SUMMARY commands 416 description 43 PMW_WEBSPHERE description 34 PMW_WLM commands 416 parameters 373, 378 PMW_WLM_GROUP description 44 PMW_WLM_SUMMARY commands 416 description 44 PollDuration (PMW_SCHEDULER) 328
Index
455
PollDuration (PMW_SCHEDULER_SUMMARY) 330 PollQueryDuration (PMW_SCHEDULER) 328 PollQueryDuration (PMW_SCHEDULER_SUMMARY) 330 PoolSize (PMW_J2C_FACTORY) 314 PoolSize (PMW_J2C_SUMMARY) 318 port requirements 51 Post-Install Runtime Environment Verification 99 Post-Install Runtime Verification ... command 412 PostProcess (PMW_MAIN) 323 PrepStmtCacheDiscardRate (PMW_DATASOURCE) 279 PrepStmtCacheDiscards (PMW_DATASOURCE) 279 PrepStmtCacheDiscards (PMW_DBPOOL_SUMMARY) 284 PrepStmtCacheDiscardsRate (PMW_DBPOOL_SUMMARY) 284 prerequisites installation 54 processes 435 product description 18 product support 3 products uninstalling in Unix environments 77 uninstalling in Windows environments 81 profiling deleting libraries 205 described 22, 28 enabling 105 overhead 137, 139 using 197 ReliableNonPersistMsgProduced (PMW_SIB_SUMMARY) 359 ReliablePersistMsgConsumed (PMW_SIB_SERVICE) 355 ReliablePersistMsgConsumed (PMW_SIB_SUMMARY) 359 ReliablePersistMsgProduced (PMW_SIB_SERVICE) 355 ReliablePersistMsgProduced (PMW_SIB_SUMMARY) 359 remote application server, described 32 remote deployment manager, described 32 RemoteCreationRate (PMW_CACHE_SUMMARY) 265 RemoteCreationRate (PMW_CACHE_TEMPLATE) 273 RemoteCreations (PMW_CACHE_SUMMARY) 265 RemoteCreations (PMW_CACHE_TEMPLATE) 273 Remove Advanced Monitoring command 396 Remove Condition command 417 RemoveViewChangeTime (PMW_DCS) 288 RemoveViewChangeTime (PMW_DCS_SUMMARY) 290 ReqMetrics instance of J2EE_OBJ 189 Request Metrics 188, 189 RequestsDispatched (PMW_WEBSERVICE) 366 RequestsDispatched (PMW_WEBSERVICE_SUMMARY) 371 RequestsDispatchedRate (PMW_WEBSERVICE) 366 RequestsDispatchedRate (PMW_WEBSERVICE_SUMMARY) 371 RequestsReceived (PMW_WEBSERVICE) 367 RequestsReceived (PMW_WEBSERVICE_SUMMARY) 371 RequestsReceivedRate (PMW_WEBSERVICE) 367 RequestsReceivedRate (PMW_WEBSERVICE_SUMMARY) 371 RequestsSuccessful (PMW_WEBSERVICE) 367 RequestsSuccessful (PMW_WEBSERVICE_SUMMARY) 371 RequestsSuccessfulRate (PMW_WEBSERVICE) 367 RequestsSuccessfulRate (PMW_WEBSERVICE_SUMMARY) 372 requirements systems 50 Unix account 53 Windows account 52 Reset Notifications command 417 response time transaction 18 ResponseTimeDispatch (PMW_WEBSERVICE) 367 ResponseTimeDispatch (PMW_WEBSERVICE_SUMMARY) 372 ResponseTimeReply (PMW_WEBSERVICE) 368 ResponseTimeReply (PMW_WEBSERVICE_SUMMARY) 372 ResponseTimeRequest (PMW_WEBSERVICE) 368 ResponseTimeRequest (PMW_WEBSERVICE_SUMMARY) 372 ResponseTimeSuccessful (PMW_WEBSERVICE) 368 ResponseTimeSuccessful (PMW_WEBSERVICE_SUMMARY) 372 Resume JDBC Conn Monitoring command 399 Resume Monitoring command 405
R
READ requirements Unix 124, 126 READ/EXECUTE requirements Unix 127 RebuildManagedTime (PMW_HA_MANAGER) 309 RebuildManagedTime (PMW_HA_SUMMARY) 310 RebuildTime (PMW_HA_MANAGER) 309 RebuildTime (PMW_HA_SUMMARY) 310 ReceivedMessages (PMW_DCS) 288 ReceivedMessages (PMW_DCS_SUMMARY) 290 Refresh DBURL Discovery command 400 Refresh Discovery command 405 Refresh SQL Discovery command 400 Register MBean command 418 registering for global security 130 ReliableNonPersistMsgConsumed (PMW_SIB_SERVICE) 354 ReliableNonPersistMsgConsumed (PMW_SIB_SUMMARY) 359 ReliableNonPersistMsgProduced (PMW_SIB_SERVICE) 354
456
ReturnsDiscarded (PMW_BEANS) 257 ReturnsDiscarded (PMW_EJB_SUMMARY) 300 ReturnsDiscardedRate (PMW_BEANS) 257 ReturnsDiscardedRate (PMW_EJB_SUMMARY) 301 ReturnsToPool (PMW_BEANS) 258 ReturnsToPool (PMW_EJB_SUMMARY) 301 ReturnsToPoolRate (PMW_BEANS) 258 ReturnsToPoolRate (PMW_EJB_SUMMARY) 301 Rewind Log File command 405 Ripplestart Cluster command 398 rule log file, pattern 233 rules log monitoring 233 RunDuration (PMW_SCHEDULER) 328 RunDuration (PMW_SCHEDULER_SUMMARY) 330 runtime environment verifying 99 ServletLoads (PMW_SERVLET_SUMMARY) 344 ServletReloads (PMW_SERVLET) 339 ServletReloads (PMW_SERVLET_SUMMARY) 344 ServletRequestRate (PMW_J2EE_OBJ) 319 ServletRequestRate (PMW_SERVLET) 340 ServletRequestRate (PMW_SERVLET_SUMMARY) 344 ServletRequestsPerSec (PMW_SERVLET) 340 ServletRequestsPerSec (PMW_SERVLET_SUMMARY) 344 ServletResponseReport (PMW_J2EE_OBJ) 319 ServletResponseTime (PMW_J2EE_OBJ) 319 ServletResponseTime (PMW_SERVLET) 340 ServletResponseTime (PMW_SERVLET_SUMMARY) 345 ServletTotalRequests (PMW_SERVLET) 340 ServletTotalRequests (PMW_SERVLET_SUMMARY) 345 SessionCreateRate (PMW_SESSIONS) 350 SessionCreates (PMW_SESSIONS) 350 SessionLifetime (PMW_SESSIONS) 350 sessions monitoring 182 Set Debug Flags command 413 Set Profiling Level command 396 setting environment variables for Help browser 74 setting performance collection data preferences 105 setup icon 33 troubleshooting problems 118 Setup Blackout Schedule command 413 Setup DataSource Login command 398 Setup E-mail command 413 Setup E-mail Notification command 212 Setup Listener command 413 SetupRequired (JMX_MAIN) 386 shell default login 59 shells Bourne 74 C 74 Korn 74 SlowestRespTime (PMW_DBURL) 286 SlowestRespTime (PMW_SERVLET_GROUP) 342 SQL Performance Report command 199, 400 SQL statement most critical 198 profiling 197 SQLCollector (PMW_SQL) 360 SQLCollector (SQL) 389 SQLDeleteReqRate (PMW_J2EE_OBJ) 319 SQLDeleteRespTime (PMW_J2EE_OBJ) 319 SQLInsertReqRate (PMW_J2EE_OBJ) 320 SQLInsertRespTime (PMW_J2EE_OBJ) 320 SQLSelectReqRate (PMW_J2EE_OBJ) 320 SQLSelectRespTime (PMW_J2EE_OBJ) 320 SQLUpdateReqRate (PMW_J2EE_OBJ) 320 SQLUpdateRespTime (PMW_J2EE_OBJ) 320 Start Application Server command 396 Start Cluster command 398 Start command 401
S
security overview 122 PATROL settings 59 security requirements Unix 124 security requirements for WebSphere Admin Windows 128 Select MBeans... command 417, 418 SelectedAliasesActive (PMW_SERVLET_GROUP) 342 SelectedAliasesActive parameter generating 176 SentMessageCount (PMW_DCS) 288 SentMessageCount (PMW_DCS_SUMMARY) 290 SerializableSessObjSize (PMW_SESSIONS) 350 Server Offline Alarm Setting InfoBox item 428 ServerLogCollector (PMW_SERVER_LOGS) 233 ServerServletCollector (PMW_SERVLET_ENGINE) 340 ServerTransportCol (PMW_MAIN) 323 service integration bus (SIBus) 42 service packs, required 50 ServiceMsgCount (PMW_RAS_MESSAGES) 328 servlet monitoring 193 servlet method performance 182 servlet performance report 179 Servlet Performance Report command 179, 180, 411 ServletConcurrentRequests (PMW_SERVLET) 338 ServletConcurrentRequests (PMW_SERVLET_SUMMARY) 343 ServletErrorRate (PMW_SERVLET_SUMMARY) 344 ServletErrors (PMW_SERVLET) 339 ServletErrors (PMW_SERVLET_SUMMARY) 343 ServletErrorsRate (PMW_SERVLET) 339 ServletLoads (PMW_SERVLET) 339
Index
457
start command, resources 20 Start Deployment Manager command 398 Start Node Agent command 406 StatusCriticalCount (JMX_CONDITION) 384 StatusOKCount (JMX_CONDITION) 384 StatusWarningCount (JMX_CONDITION) 384 Stop Application Server command 396 Stop Cluster command 398 Stop command 401 stop command, resources 20 Stop Deployment Manager command 398 Stop JDBC Conn Monitoring command 399 Stop Monitoring command 408, 414 Stop Node Agent command 406 string log file 233 StringMatchCount (JMX_CONDITION) 384 StringNoMatchCount (JMX_CONDITION) 384 SubjectManaged (PMW_HA_MANAGER) 309 SubjectManaged (PMW_HA_SUMMARY) 310 SubscriptionsManaged (PMW_HA_MANAGER) 309 SubscriptionsManaged (PMW_HA_SUMMARY) 311 support, customer 3 Suspend Monitoring command 405 suspend monitoring, see blackout Suspicion (PMW_DCS) 288 Suspicion (PMW_DCS_SUMMARY) 291 SvrDbUrlCollector (PMW_DBURLS) 286 SvrSessionUtilization (PMW_BEANS) 258 SvrSessionUtilization (PMW_EJB_SUMMARY) 301 SvrSessionWait (PMW_BEANS) 258 SvrSessionWait (PMW_EJB_SUMMARY) 301 SynchRequestRate (PMW_WEBSERVICE) 368 SynchRequestRate (PMW_WEBSERVICE_SUMMARY) 373 SynchRequests (PMW_WEBSERVICE) 368 SynchRequests (PMW_WEBSERVICE_SUMMARY) 373 SynchResponseRate (PMW_WEBSERVICE) 369 SynchResponseRate (PMW_WEBSERVICE_SUMMARY) 373 SynchResponses (PMW_WEBSERVICE) 369 SynchResponses (PMW_WEBSERVICE_SUMMARY) 373 SynchronizationCompleteTime (PMW_DCS) 288 SynchronizationCompleteTime (PMW_DCS_SUMMARY) 291 SynchronizationTimeout (PMW_DCS) 288 SynchronizationTimeout (PMW_DCS_SUMMARY) 291 system requirements 50 listed 49 system roles console systems 55, 56 managed systems 56 TaskCollisionRate (PMW_SCHEDULER_SUMMARY) 330 TaskDelayDuration (PMW_SCHEDULER) 329 TaskDelayDuration (PMW_SCHEDULER_SUMMARY) 330 TaskExpirationRate (PMW_SCHEDULER) 329 TaskExpirationRate (PMW_SCHEDULER_SUMMARY) 330 TaskFinish (PMW_SCHEDULER) 329 TaskFinish (PMW_SCHEDULER_SUMMARY) 330 TaskRunRate (PMW_SCHEDULER) 329 TaskRunRate (PMW_SCHEDULER_SUMMARY) 331 TasksFinishRate (PMW_SCHEDULER) 329 TasksFinishRate (PMW_SCHEDULER_SUMMARY) 331 technical support 3 TemplateTimeoutRate (PMW_CACHE_SUMMARY) 265 TemplateTimeoutRate (PMW_CACHE_TEMPLATE) 273 TemplateTimeouts (PMW_CACHE_SUMMARY) 265 TemplateTimeouts (PMW_CACHE_TEMPLATE) 273 ThreadCreateRate (PMW_SERVER_RESOURCE) 336 ThreadCreateRate (PMW_THREADPOOL) 362 ThreadCreateRate (PMW_THREADPOOL_SUMMARY) 363 ThreadCreates (PMW_SERVER_RESOURCE) 336 ThreadCreates (PMW_THREADPOOL) 361 ThreadCreates (PMW_THREADPOOL_SUMMARY) 363 ThreadDestroyRate (PMW_SERVER_RESOURCES) 337 ThreadDestroyRate (PMW_THREADPOOL) 362 ThreadDestroyRate (PMW_THREADPOOL_SUMMARY) 364 ThreadDestroys (PMW_SERVER_RESOURCES) 337 ThreadDestroys (PMW_THREADPOOL) 362 ThreadDestroys (PMW_THREADPOOL_SUMMARY) 364 ThreadHung (PMW_THREADPOOL) 362 ThreadMaxSize (PMW_SERVER_RESOURCE) 337 ThreadMaxSize (PMW_THREADPOOL) 362 ThreadMaxSize (PMW_THREADPOOL_SUMMARY) 364 ThreadPercentMaxed (PMW_SERVER_RESOURCE) 337 ThreadPercentMaxed (PMW_THREADPOOL) 363 ThreadPercentMaxed (PMW_THREADPOOL_SUMMARY) 364 ThreadPoolSize (PMW_SERVER_RESOURCE) 337 ThreadPoolSize (PMW_THREADPOOL) 363 ThreadPoolSize (PMW_THREADPOOL_SUMMARY) 364 Threads (PMW_SERVER_RESOURCE) 337 ThreadsObjects (PMW_SERVER_RESOURCE) 338 TimeoutInvalidationRate (PMW_CACHE_SUMMARY) 266 TimeoutInvalidationRate (PMW_CACHE_TEMPLATE) 274 TimeoutInvalidations (PMW_CACHE_SUMMARY) 266 TimeoutInvalidations (PMW_CACHE_TEMPLATE) 274 TimeSinceLastActivated (PMW_SESSIONS) 350 TotalCumulativeTime (PMW_DBURL) 286 TotalCumulativeTime (PMW_SERVLET_GROUP) 342 TotalCumulativeTime (PMW_SQL) 360 TotalInvocations (PMW_DBURL) 286 TotalInvocations (PMW_SERVLET_GROUP) 342
T
TaskCollisionRate (PMW_SCHEDULER) 328
458
TotalInvocations (PMW_SQL) 360 TotalMemory (PMW_SERVER_RESOURCE) 338 TotalPolls (PMW_SCHEDULER) 329 TotalPolls (PMW_SCHEDULER_SUMMARY) 331 trace debug flag 119 transaction monitoring 18, 188 activating 189 parameters 189 TransactionLongCount (PMW_J2EE_OBJ) 321 TransactionMaximum (PMW_J2EE_OBJ) 321 TransactionReport (PMW_J2EE_OBJ) 321 tuning considerations performance tuning 134 TxDetailCollector(PMW_J2EE_OBJ) 321 typical installation option 58 ViewChange (PMW_DCS) 288 ViewChange (PMW_DCS_SUMMARY) 291 ViewChangeTimeout (PMW_DCS) 289 ViewChangeTimeout (PMW_DCS_SUMMARY) 291 ViewGroupSize (PMW_DCS) 289 ViewGroupSize (PMW_DCS_SUMMARY) 291 virtual host aliases pinging for availability 175 VirtualMemory (PMW_SERVER_RESOURCE) 336 VMWare, support 51
W
WarningMsgCount (PMW_RAS_MESSAGES) 328 web application instrumenting performance 203 performance report 177 profiling 197 web server defined 29 WebApp Performance Report command 177, 411 WebAppCollector (PMW_SERVLET_ENGINE) 341 WebSphere 5 mixed environment with WebSphere 6 18 mixed environments with WebSphere 6 153 WebSphere 6 mixed environment with WebSphere 5 18 mixed environments with WebSphere 5 153 supported features 18 WebSphere Admin server, described 28 Windows security requirements 128 WebSphere Admin account general charcteristics 124 Unix requirements 124 WebSphere Admin OS account 123 WebSphere global security 122 WEBSPHERE icon 33 WebSphere Performance Data Setting ... command 413 WebSphere server, described 27 WebSphere Setup icon 33 Windows account requirements 52 registry 435 Windows NT DLL conflict 118 WLMClientClustUpd (PMW_WLM) 373 WLMClientClustUpd (PMW_WLM_SUMMARY) 378 WLMClientClustUpdRate (PMW_WLM) 374 WLMClientClustUpdRate (PMW_WLM_SUMMARY) 378 WLMClientRespTime (PMW_WLM) 374 WLMClientRespTime (PMW_WLM_SUMMARY) 378 WLMClientsServiced (PMW_WLM) 374 WLMClientsServiced (PMW_WLM_SUMMARY) 379 WLMClientsServicedRate (PMW_WLM) 374
U
uninstalling products in Unix environments 77 in Windows environments 81 JVM profiling and J2EE bytecode instrumentation 205 Unix account requirements 53 Unix requirements for WebSphere Admin 124 Update DataSource Info command 148, 398 upgrading backing up current installation before 67 UpTime (PMW_SERVER_RESOURCE) 338 UsedMemory (PMW_SERVER_RESOURCE) 338 user account 74
V
validating HTTP server status failure across firewalls 175 ValueAverage (JMX_CONDITION) 385 ValueMaximum (JMX_CONDITION) 385 ValueMinimum (JMX_CONDITION) 385 ValueSum (JMX_CONDITION) 385 variable PATROL_BROWSER 74 verifying discovery 116 verifying runtime environment 99 version installation utility 54 WebSphere 153 version, installation utility 54 version, of KM 431, 432 View Condition Report command 417 View Connection Pool Report command 399 View Log File command 405 View Recent Messages command 396, 398, 406 View SQL Name command 414
Index
459
WLMClientsServicedRate (PMW_WLM_SUMMARY) 379 WLMCurrentRequests (PMW_WLM 374 WLMCurrentRequests (PMW_WLM_SUMMARY) 379 WLMMinReq (PMW_WLM 375 WLMMinReq (PMW_WLM_SUMMARY) 379 WLMMinReqRate (PMW_WLM 375 WLMMinReqRate (PMW_WLM_SUMMARY) 379 WLMNonAffinReq (PMW_WLM) 375 WLMNonAffinReq (PMW_WLM_SUMMARY) 380 WLMNonAffinReqRate (PMW_WLM) 375 WLMNonAffinReqRate (PMW_WLM_SUMMARY) 380 WLMNonWLMRequestRate (PMW_WLM 376 WLMNonWLMRequestRate (PMW_WLM_SUMMARY) 381 WLMNonWLMRequests (PMW_WLM 376 WLMNonWLMRequests (PMW_WLM_SUMMARY) 380 WLMOutReq (PMW_WLM) 376 WLMOutReq (PMW_WLM_SUMMARY) 381 WLMOutReqRate (PMW_WLM) 376 WLMOutReqRate (PMW_WLM_SUMMARY) 381 WLMServClustUpdate (PMW_WLM) 377 WLMServClustUpdateRate (PMW_WLM) 377 WLMServClustUpdateRate (PMW_WLM_SUMMARY) 382 WLMServClustUpdates (PMW_WLM_SUMMARY) 381 WLMServRespTime (PMW_WLM) 377 WLMServRespTime (PMW_WLM_SUMMARY) 382 WLMStrongAffinReq (PMW_WLM) 377 WLMStrongAffinReq (PMW_WLM_SUMMARY) 382 WLMStrongAffinReqRate (PMW_WLM) 378 WLMStrongAffinReqRate (PMW_WLM_SUMMARY) 382 WMQQueueManagerConnectToServer (PMW_SIB_SERVICE) 355 WMQQueueManagerConnectToServer (PMW_SIB_SUMMARY) 359
X
XMLConfig.sh file 118 XPC debug, advanced monitoring 120 XPC, defined 30
460
Notes
*60323* *60323* *60323* *60323*

*60323*

Websphere KM

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Websphere KM

Transféré par

Droits d'auteur :

Formats disponibles

PATROL for WebSphere Application Server

Contacting BMC Software

United States and Canada

Outside United States and Canada

Restricted rights legend

Support by telephone or e-mail

Before contacting BMC Software

PATROL for WebSphere Application Server User Guide

Web Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server User Guide

Product Components and Capabilities

Product Components and Capabilities

PATROL for WebSphere Application Server Features

PATROL for WebSphere Application Server Features

Application-Centric Transaction Monitoring and End-to-End Response Time

Support for WebSphere 6.0.02

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server Features

Application Server Monitoring and Management

PATROL for WebSphere Application Server Features

Resources you can ping for availability through menu commands

Resources you can stop and start through menu commands

PATROL for WebSphere Application Server User Guide

PATROL for WebSphere Application Server Features

Availability of Full Range of PMI-Provided Metrics

Fine Grained Control of the Monitoring Environment

Enterprise Java Bean Monitoring and Management

Product Components and Capabilities

PATROL for WebSphere Application Server Features

J2EE Bytecode Instrumentation and JVM Profiling

Application Monitoring and Management with JMX

PATROL for WebSphere Application Server User Guide

Database Connection Monitoring

Application Class Hierarchy

Product Components and Capabilities

Application Class Hierarchy in PATROL for WebSphere

console SETUP MAIN CELL-BASED MANAGEMENT ENVIRONMENT (J2EE_GROUP)

J2EE_OBJ CELL (0 or more) CLUSTER (0 or more) SERVER LOG

APPSERVER classes and containers

PATROL for WebSphere Application Server User Guide

Application Class Hierarchy for Monitored WebSphere Components

GENERAL CONTAINER ORGANIZATION CONTAINER

INSTANCE2 Number varies

ORGANIZATION OF SOME SPECIFIC CONTAINERS Database Pools

SERVLET GROUP corresponds to Web application

SERVLET SUMMARY SESSIONS SERVLET

BEANS TRANSACTION SUMMARY SUMMARY

Product Components and Capabilities

JMX Component Class Hierarchy

JMX CONDITION JMX DOMAIN

WebSphere Data Collection

PATROL for WebSphere Application Server User Guide

Architecture of PATROL for WebSphere Application Server

PATROL for WebSphere Application Server Other PATROL KM products

Base App Server

An explanation of the diagram components follows:

PATROL Consoles, PATROL Console Servers

Product Components and Capabilities

PATROL for WebSphere Application Server User Guide

PATROL in a Cell-Based Management Environment