PATROL for BEA WebLogic User Guide. Version

Transcription

1 PATROL for BEA WebLogic User Guide Version June 23, 2003

2 Copyright 2003 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 Corp. All other registered trademarks or trademarks belong to their respective companies. PATROL technology holds U.S. Patent Number 5,655,081. THE USE AND CONTENTS OF THIS DOCUMENTATION ARE GOVERNED BY THE SOFTWARE LICENSE AGREEMENT ENCLOSED AT THE BACK OF THIS DOCUMENTATION. Restricted Rights Legend U.S. GOVERNMENT RESTRICTED RIGHTS. UNPUBLISHED RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in FAR Section Alt. III (g)(3), FAR Section , DFARS (b), or DFARS , as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, T , USA. Any contract notices should be sent to this address. Contacting BMC Software You can access the BMC Software Web site at From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address Telephone BMC Software, Inc CityWest Blvd. Houston T or Fax Outside United States and Canada Telephone Fax (01) (01)

3 Customer Support You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or . To expedite your inquiry, please see Before Contacting BMC Software. Support Web Site You can obtain technical support from BMC Software 24 hours a day, 7 days a week at From this Web site, you can 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 notices when new product versions are released find worldwide BMC Software support center locations and contact information, including addresses, fax numbers, and telephone numbers Support by Telephone or In the United States and Canada, if you need technical support and do not have access to the Web, call Outside the United States and Canada, please contact your local support center for assistance. To find telephone and contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC Software Web site at 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: 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 iii

4 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 iv PATROL for BEA WebLogic User Guide

5 Contents Contents Chapter 1 Chapter 2 Product Components and Capabilities PATROL for BEA WebLogic Features Server Management J2EE Performance Instrumentation JVM Profiling JM MBean Monitoring Log File Monitoring Response Time Probe Component Monitoring Product Architecture WebLogic Data Collection Application Classes and Icons Application Instance Naming Conventions Accessing Product Help From a Windows NT Console From a Unix Console Additional Information Where to Go from Here Installing and Migrating PATROL for BEA WebLogic Installation Requirements System Additional Requirements if Using JVM Profiling Performance and Scalability License Installation Account Preparing to Install Installation Prerequisites Contents v

6 Determine the Version of the Installation Utility Target Computers and Their Roles Determining Where to Install KMs Based on Architecture Typical and Custom Installation Types PATROL Security Installing for the First Time Typical New Installation Upgrading from an Earlier Version Prepare to Upgrade Upgrade Without Migrating Prior-version Customizations Upgrade and Preserve Customizations Migrate Your Customizations Creating and Installing Installable Images Create an Installable Image Install the Created Installable Image Installing the Online Help Browser (Unix) Installing the Unix Version of the Help Browser Uninstalling PATROL for BEA WebLogic Uninstalling PATROL for BEA WebLogic from a Unix Environment Uninstalling PATROL for BEA WebLogic from a Windows Environment Where to Go from Here Chapter 3 Chapter 4 Configuring PATROL for BEA WebLogic Loading PATROL for BEA WebLogic Configuring the KM Enabling Instrumentation and Profiling Features Setting EJB Deployment for WebLogic Verifying and Troubleshooting WebLogic Server Configuration Where to Go from Here Managing the BEA WebLogic Environment Monitoring a WebLogic Environment Working with Parameters Working with Events Managing Events Using PATROL Event Manager Estimating Response Times Test File Transfer Rate Test Web Page Response vi PATROL for BEA WebLogic User Guide

7 Administering Probe Generating Reports Generating a Report Chapter 5 Chapter 6 Chapter 7 Working with Log Files Understanding Logs Rotation Severity Select Log File for Monitoring Configure the Domain Log Configure the Server Log Configure the JDBC Log Configure the HTTP Log Configure the Transaction Log Define Sniff Pattern Stop Monitoring a Log View Log File Watch a Log File View Sniff Patterns Turning Off and Restarting Sniff Patterns Changing the Sniff Type Updating a Log File Location Registering for Log Notification Messages Unregistering for Log Notification Messages Managing Servers Managing WebLogic Servers Boot WebLogic Server Shut Down WebLogic Server Lock or Unlock Server Perform Java Garbage Collection Tuning a Server Configuration Managing WebLogic Components and Services Configuring WebLogic Components Configuring the JTA Configuring the JDBC Configuring the JMS Managing JDBC Pools Creating a JDBC Pool Contents vii

8 Removing a JDBC Pool Administering JDBC Pools Enabling or Disabling JDBC Profiling Generating JDBC Profiling Reports Chapter 8 Chapter 9 Chapter 10 Managing Web Applications Managing Applications Automatically Deploy Domain Applications Deploy and Undeploy Applications to Servers Select Servlet to Monitor Instrumenting and Profiling J2EE Components Instrumenting and Profiling J2EE Objects Running the Top N SQL Report Monitoring SQL Objects Running the Top N EJB Report and the Top N EJB Methods Report 9-9 Monitoring EJB Methods Running the Top N WebApps Report Running the Top N Servlets Report Monitoring Servlets to the Method Level Profiling the Java Virtual Machine Identifying Processes with High CPU Usage Running a Thread Detail Report Managing JM-Instrumented Applications Monitoring JM MBeans Instrumenting Your Application with JM The PATROL for BEA WebLogic MBean Interface Setting Default Address for Notifications Defining Conditions Adding Automatic Actions Adding Notifications Advanced Features for JM Monitoring Manually Registering an MBean Defining Conditions for an Unregistered MBean Setting JM Debug Flags viii PATROL for BEA WebLogic User Guide

9 Chapter 11 Appendix A Appendix B Appendix C Administering the KM Monitoring WebLogic Across the Enterprise Tune Collectors Schedule Blackout Periods Restart PATROL s Java Collector Troubleshooting and Debugging Set PSL Debug Flag Set Debug Status for Server Set Debug Status for Java Collector Record Data Accessing Menu Commands, InfoBoxes, and Online Help Accessing KM Commands and InfoBoxes A-2 Accessing Online Help A-3 Parameter Reference Column Headings Defined B-2 Abbreviations Defined B-3 Parameters for a WebLogic 6.x, 7.0, or 8.1 Environment B-4 Parameters for a WebLogic 5.1 Environment B-25 Collector-Consumer Dependencies B-34 Menu Summary About Menu Commands C-3 BEAWLS_SETUP Application Menu C-4 BEAWLS_SERVER Application Menu C-5 BEAWLS_MANAGED Application Menu C-8 BEAWLS_SERVLET Application Menu C-9 BEAWLS_PROBE Application Menu C-10 BEAWLS_WEBAPP Application Menu C-10 BEAWLS_JMSSERVER Application Menu C-11 BEAWLS_EEC_QUEUE Application Menu C-11 BEAWLS_JDBC Application Menu C-12 BEAWLS_LOG Application Menu C-14 BEAWLS_OS Application Menu C-15 BEAWLS_EJB_HOME Application Menu C-16 BEAWLS_EJB_METHOD Application Menu C-16 BEAWLS_LOCAL_MANAGED Application Menu C-17 BEAWLS_DBURL Application Menu C-19 BEAWLS_SQL Application Menu C-19 Contents ix

10 BEAWLS_JVMPROFILER Application Menu C-20 BEAWLS_PROF_CLASS Application Menu C-20 JM_MAIN Application Menu C-21 JM_SERVER Application Menu C-22 JM_DOMAIN Application Menu C-23 JM_CONDITION Application Menu C-23 BEAWLS_SETUP_V51 Application Menu C-24 BEAWLS_SERVER_V51 Application Menu C-24 BEAWLS_SERVLET_V51 Application Menu C-27 BEAWLS_PROBE_V51 Application Menu C-28 BEAWLS_JDBC_V51 Application Menu C-28 BEAWLS_JOLT_V51 Application Menu C-29 BEAWLS_LOG_V51 Application Menu C-30 BEAWLS_DBURL_V51 Application Menu C-31 BEAWLS_EJB_V51 Application Menu C-31 BEAWLS_SQL_V51 Application Menu C-32 BEAWLS_JVMPROFILER_V51 Application Menu C-32 BEAWLS_PROF_CLASS_V51 Application Menu C-33 BEAWLS_EJB_METHOD_V51 Application Menu C-33 Appendix D InfoBox Summary BEAWLS_CLUSTER InfoBox D-3 BEAWLS_DBURL InfoBox D-3 BEAWLS_EJB InfoBox D-4 BEAWLS_EJB_HOME InfoBox D-4 BEAWLS_EEC_QUEUE InfoBox D-5 BEAWLS_JCA InfoBox D-5 BEAWLS_JDBC InfoBox D-7 BEAWLS_JMSSERVER InfoBox D-8 BEAWLS_JVMPROFILER InfoBox D-9 BEAWLS_JOLT InfoBox D-10 BEAWLS_LOCAL_MANAGED InfoBox D-10 BEAWLS_LOG InfoBox D-11 BEAWLS_MANAGED InfoBox D-12 BEAWLS_OS InfoBox D-13 BEAWLS_PROBE InfoBox D-13 BEAWLS_PROF_CLASS InfoBox D-13 BEAWLS_PROF_METHOD InfoBox D-14 BEAWLS_SERVER InfoBox D-14 BEAWLS_SERVLET InfoBox D-16 x PATROL for BEA WebLogic User Guide

11 BEAWLS_SETUP InfoBox D-16 BEAWLS_SQL InfoBox D-16 BEAWLS_WEBAPP InfoBox D-17 JM_SERVER InfoBox D-17 JM_CONDITION InfoBox D-18 BEAWLS_DBURL_V51 InfoBox D-19 BEAWLS_EJB_V51 InfoBox D-19 BEAWLS_JDBC_V51 InfoBox D-20 BEAWLS_JOLT_V51 InfoBox D-21 BEAWLS_JVMPROFILER_V51 InfoBox D-21 BEAWLS_LOG InfoBox D-22 BEAWLS_PROF_CLASS_V51 InfoBox D-23 BEAWLS_PROF_METHOD_V51 InfoBox D-23 BEAWLS_SERVER_V51 InfoBox D-24 BEAWLS_SERVLET_V51 InfoBox D-25 BEAWLS_SETUP_V51 InfoBox D-25 BEAWLS_SQL_V51 InfoBox D-26 Appendix E Agent Configuration Variables Glossary Index Contents xi

12 xii PATROL for BEA WebLogic User Guide

13 Figures Figures Figure 1-1 Application Class Hierarchy when Monitoring BEA WebLogic Server 6.x, 7.0, or Figure 1-2 Collector Architecture of PATROL for BEA WebLogic Figure 1-3 PATROL Console Figure 2-1 Select Products to Install using Typical Install Figure 2-2 Product Selection Dialog - Custom Install Figure 3-1 WebLogic Server Icon in PATROL Console Figure 3-2 Example Monitored WebLogic 7.0 Server Figure 7-1 Create New JDBC Pool Dialog (WebLogic Server 5.1) Figure 7-2 Create New JDBC Pool Dialog (WebLogic Server 6.x or 7.0) Figures xiii

14 xiv PATROL for BEA WebLogic User Guide

15 Tables Tables Table 1-1 Application Class Icons and Functions Table 1-2 Instance Naming Conventions Table 1-3 Accessing Online Help from a Windows NT Console Table 1-4 Accessing Online Help from a Unix Console Table 2-1 PATROL for BEA WebLogic Installation Requirements Table 2-2 System Requirements for JVM Profiling Table 2-3 PATROL Installation Directories to Back Up Table 2-4 Versions That You Can Migrate Table 2-5 Command Line Options for Installing in a KMDS Environment Table 3-1 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 6.x, 7.0, and 8.1) Table 3-2 Setup Java Environment Dialog Box Fields Table 3-3 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 5.1) Table 3-4 Options for Configuring Advanced Monitoring Table 4-1 Probe Administration dialog box fields Table 4-2 Reports in PATROL for BEA WebLogic Table 5-1 Monitor Another Log dialog box fields Table 5-2 Domain Log Setting dialog box fields Table 5-3 HTTP Log Settings dialog box fields Table 5-4 Add New Sniff Pattern dialog box fields Table 6-1 Server Tuning dialog box fields Table 7-1 JTA Configuration dialog box fields Table 7-2 JMS Server Thresholds and Quotas dialog box fields Table 7-3 Create New JDBC Pool dialog box fields (WebLogic Server 5.1) Tables xv

16 Table 7-4 Create New JDBC Pool dialog box fields (WebLogic Server 6.x and 7.0) Table 7-5 Pool Administration Functions Table 10-1 Setup dialog box Table 10-2 MBean Management dialog box Table 11-1 Blackout Period dialog box fields Table 11-2 Set PSL Debug dialog box fields Table 11-3 Debug Level dialog box fields Table A-1 Accessing KM Commands and InfoBoxes A-2 Table A-2 Accessing Online Help A-3 Table B-1 Parameters in PATROL for BEA WebLogic when monitoring WebLogic Server 6.x, 7.0, or B-4 Table B-2 JM parameters when monitoring WebLogic Server 6.x, 7.0, or B-23 Table B-3 Parameters in PATROL for BEA WebLogic when monitoring WebLogic Server B-25 Table B-4 PATROL for BEA WebLogic ector-consumer dependencies Table B-5 when monitoring WebLogic 6.x, 7.0, or B-34 PATROL for BEA WebLogic ector-consumer dependencies when monitoring WebLogic B-41 Table C-1 BEAWLS_SETUP commands C-4 Table C-2 BEAWLS_SERVER commands C-5 Table C-3 BEAWLS_MANAGED menu commands in a WebLogic 6.1 environment C-8 Table C-4 BEAWLS_SERVLET commands C-9 Table C-5 BEAWLS_PROBE Application Menu Summary C-10 Table C-6 BEAWLS_WEBAPP Application Menu Summary C-10 Table C-7 BEAWLS_JMSSERVER Application Menu Summary C-11 Table C-8 BEAWLS_EEC_QUEUE Application Menu Summary..... C-11 Table C-9 BEAWLS_JDBC Application Menu Summary C-12 Table C-10 BEAWLS_LOG Application Menu Summary C-14 Table 3-11 BEAWLS_OS commands C-15 Table C-12 BEAWLS_EJB_HOME commands C-16 Table C-13 BEAWLS_EJB_METHOD commands C-16 Table C-14 BEAWLS_LOCAL_MANAGED commands C-17 Table C-15 BEAWLS_DBURL commands C-19 Table C-16 BEAWLS_SQL commands C-19 Table C-17 BEAWLS_JVMPROFILER commands C-20 Table C-18 BEAWLS_PROF_CLASS commands C-20 Table C-19 JM_MAIN commands C-21 xvi PATROL for BEA WebLogic User Guide

17 Table C-20 JM_SERVER commands C-22 Table C-21 JM_DOMAIN commands C-23 Table C-22 JM_CONDITION commands C-23 Table C-23 BEAWLS_SETUP_V51 commands C-24 Table C-24 BEAWLS_SERVER_V51 commands C-24 Table C-25 BEAWLS_SERVLET_V51 commands C-27 Table C-26 BEAWLS_PROBE_V51 Application Menu Summary C-28 Table C-27 BEAWLS_JDBC_V51 Application Menu Summary C-28 Table C-28 BEAWLS_JOLT_V51 Application Menu Summary C-29 Table C-29 BEAWLS_LOG_V51 Application Menu Summary C-30 Table C-30 BEAWLS_DBURL_V51 commands C-31 Table C-31 BEAWLS_EJB_V51 commands C-31 Table C-32 BEAWLS_SQL_V51 commands C-32 Table C-33 BEAWLS_JVMPROFILER_V51 commands C-32 Table C-34 BEAWLS_PROF_CLASS_V51 commands C-33 Table C-35 BEAWLS_EJB_METHOD_V51 commands C-33 Table D-1 BEAWLS_CLUSTER InfoBox D-3 Table D-2 BEAWLS_DBURL InfoBox D-3 Table D-3 BEAWLS_EJB InfoBox D-4 Table D-4 BEAWLS_EJB_HOME InfoBox D-4 Table D-5 BEAWLS_EEC_QUEUE InfoBox D-5 Table D-6 BEAWLS_JCA InfoBox D-5 Table D-7 BEAWLS_JDBC InfoBox D-7 Table D-8 BEAWLS_JMSSERVER InfoBox D-8 Table D-9 BEAWLS_JVMPROFILER InfoBox D-9 Table D-10 BEAWLS_JOLT InfoBox D-10 Table D-11 BEAWLS_LOCAL_MANAGED InfoBox D-10 Table D-12 BEAWLS_LOG InfoBox D-11 Table D-13 BEAWLS_MANAGED InfoBox D-12 Table D-14 BEAWLS_OS InfoBox D-13 Table D-15 BEAWLS_PROBE InfoBox D-13 Table D-16 BEAWLS_PROF_CLASS InfoBox D-13 Table D-17 BEAWLS_PROF_METHOD InfoBox D-14 Table D-18 BEAWLS_SERVER InfoBox D-14 Table D-19 BEAWLS_SERVLET InfoBox D-16 Table D-20 BEAWLS_SETUP InfoBox D-16 Table D-21 BEAWLS_SQL InfoBox D-16 Table D-22 BEAWLS_WEBAPP InfoBox D-17 Table D-23 JM_SERVER InfoBox D-17 Table D-24 JM_CONDITION InfoBox D-18 Tables xvii

18 Table D-25 BEAWLS_DBURL_V51 InfoBox D-19 Table D-26 BEAWLS_EJB_V51 InfoBox D-19 Table D-27 BEAWLS_JDBC_V51 InfoBox D-20 Table D-28 BEAWLS_JOLT_V51 InfoBox D-21 Table D-29 BEAWLS_JVMPROFILER_V51 InfoBox D-21 Table D-30 BEAWLS_LOG InfoBox D-22 Table D-31 BEAWLS_PROF_CLASS_V51 InfoBox D-23 Table D-32 BEAWLS_PROF_METHOD_V51 InfoBox D-23 Table D-33 BEAWLS_SERVER_V51 InfoBox D-24 Table D-34 BEAWLS_SERVLET_V51 InfoBox D-25 Table D-35 BEAWLS_SETUP_V51 InfoBox D-25 Table D-36 BEAWLS_SQL_V51 InfoBox D-26 Table E-1 Agent Variables E-1 xviii PATROL for BEA WebLogic User Guide

19 1 Product Components and Capabilities 1 The chapter provides a brief overview of the PATROL for BEA WebLogic product. PATROL for BEA WebLogic Features J2EE Performance Instrumentation JVM Profiling JM MBean Monitoring Log File Monitoring Server Management Response Time Probe Component Monitoring Product Architecture WebLogic Data Collection Application Classes and Icons Application Instance Naming Conventions Accessing Product Help From a Windows NT Console From a Unix Console Additional Information Product Components and Capabilities 1-1

20 PATROL for BEA WebLogic Features PATROL for BEA WebLogic provides a complete monitoring and management solution to ensure reliable, predictable performance of a BEA WebLogic Server environment. This section provides an overview of major product features. PATROL for BEA WebLogic also provides several reporting mechanisms for key parameters and allows you to perform a wide range of WebLogic Server administrative functions from within the PATROL Console environment. Server Management PATROL for BEA WebLogic includes several menu commands and parameters for managing instances of BEA WebLogic Server. In a WebLogic 6.x, 7.0, and 8.1 environments, commands are available to manage both Administrative and Managed Servers. Previous versions of PATROL for BEA WebLogic could manage an Admin server and all of its managed servers, but it did not differentiate which servers had local PATROL Agents running (although it was always assumed that an Admin server had an Agent). In version , the local managed server icon identifies those managed servers that are co-resident with a PATROL Agent, enabling additional capability such as J2EE instrumentation and profiling and the ability to directly monitor local log files. Administrative functions are provided within the PATROL environment. You can shut down or reboot the server, lock out user sessions, perform Java garbage ection, or briefly suspend alarms and event generation during routine maintenance periods. You can also tune the PATROL product for your monitoring environment by turning off selected ectors. 1-2 PATROL for BEA WebLogic User Guide

21 Blackout Periods During a blackout period, PATROL continues to monitor the WebLogic environment but does not report object state changes nor does it generate warnings or alarms. Use blackout periods during routine maintenance to prevent spurious alarms. Tuning Collectors By turning off ectors for parts of the system that are not critical to your WebLogic environment, you can reduce resource demands and improve overall PATROL performance. If you experience slow performance, try turning off unnecessary ectors. Clustering Support PATROL for BEA WebLogic supports a clustered server environment and provides features to manage clustered nodes. The cluster improves scalability by allowing additional servers to be quickly added to the WebLogic environment and it improves availability by providing redundancy and a fail-safe mechanism for rolling functions over to other servers in the event of a server failure. J2EE Performance Instrumentation The PATROL for BEA WebLogic product includes instrumentation technology that allows you to monitor performance at a fine-grained component level and to identify potential performance bottlenecks that may be associated with a single EJB, 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. This product can also measure performance of specific Java methods in individual EJBs and servlets. Product Components and Capabilities 1-3

22 JVM Profiling Version provides the ability to monitor performance of the Java Virtual Machine. New controls allow you to monitor selected Java classes and to profile performance. Available data includes JVM memory statistics, garbage ection metrics, method-level data, and thread data. JM MBean Monitoring Version provides tools that let you monitor MBeans used in a JM-managed WebLogic 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. Log File Monitoring Log files are monitored from the BEAWLS_LOG application class. The domain, server, HTTP, and Java Database Connection (JDBC) logs are monitored by default, however, you can register any log file to be monitored. In addition to being able to watch error and informational messages as they are written to the log, you can define sniff patterns to isolate critical error messages and you can subscribe to or Event Manager notifications; you can also generate PATROL events when specific text patterns are written to the log. Sniff Patterns Set up sniff patterns to match text strings in the log file so that you can pinpoint error messages that are most critical to your monitoring environment. You can define sniff patterns for any kind of text occurrence. Some of the most common strategies are to match: Resource or service type: For example, you could specify a sniff pattern of SSLListenThread to isolate only those messages pertaining to the secure socket listener. 1-4 PATROL for BEA WebLogic User Guide

23 Date: Look at the log file to determine the date format you should match. When you view the server log file, the Message Filter dialog box provides a field for limiting the date range. Severity level: Limit output to only errors or warnings, or show just the informational messages if you are looking for a specific text string. For example, on the server log file, you could set a sniff pattern of <!> to see the warnings, or you could use <I> to find the informational only messages. Host name: If you are monitoring an environment with many servers, you may want to isolate messages based on the server name. You can do that by using the hostname as a sniff pattern. For each log file, you can define multiple sniff patterns. When you use the Sniff Pattern Setup menu commands, the sniff patterns you previously defined can be selected, viewed, edited or deleted. Each sniff pattern can also be set up to generate annotated data points on parameters, and to generate events that can be monitored through the PATROL Event Manager. Events When you define a new sniff pattern, you have the option of having it automatically trigger a PATROL event whenever the message is written to the log file. Triggering the events allows you to monitor the events through the PATROL Event Manager interface. The PATROL Event Manager (PEM) window displays events generated from the selected log file. From within this window, you can manage events as you do for any other PATROL event classes. See the PATROL Event Manager Help in your Console for more information about managing events. Notifications When critically important messages are written to the log file, you can use the notification feature to automatically have PATROL send you an message alerting you to the error situation. You can also have these messages reported to the PATROL Event Manager. Product Components and Capabilities 1-5

24 Response Time Probe The Probe application class provides a way to monitor and manage server timing data. You can automatically generate events based on ping time or response time whenever the status changes to WARNING or ALARM. You can then monitor PATROL events through the familiar PATROL Event Manager (PEM) interface. Component Monitoring Application classes are provided to monitor critical components of the WebLogic environment, including the Java Transaction API (JTA), the Java Messaging Service (JMS), the Java Connection Architecture (JCA), Enterprise Java Beans (EJBs), execution queues, web applications, and Jolt and JDBC pools. Web application monitoring capabilities include the ability to monitor specific servlets. The JTA functions include the ability to generate various reports with performance metric details. JCA is foundation for web applications to interact with other types of business software, including transaction processing systems, databases, and ERP applications. PATROL for BEA WebLogic provides several parameters that can monitor usage of the JCA connectors. The BEAWLS_JMSSERVER application class monitors the Java Messaging System and includes commands to configure the JMS server within the PATROL monitoring environment. JDBC performance information is available for peak usage and number of active connections, as well as for connection waiting times. Additional JDBC features include profiling for connection leaks, prepared statement cache, and SQL roundtrip metrics. 1-6 PATROL for BEA WebLogic User Guide

25 Product Architecture Figure 1-1 shows how PATROL for BEA WebLogic is organized within the console monitoring environment. Most application classes can have multiple instances. Information about how these instances are named is on page For more information about each application class, see Application Classes and Icons on page Product Components and Capabilities 1-7

26 Figure 1-1 Application Class Hierarchy when Monitoring BEA WebLogic Server 6.x, 7.0, or 8.1 console setup icon system-wide icon for WebLogic managed servers one or more managed WebLogic Server instances servers running PATROL Agent are identified as local managed administrative server icon optional cluster local managed server containers JMSSERVER WEBAPP JDBC EEC JCA JOLT LOG EJB PROBE QUEUE Probe is only on admin server JMSERVER DBURL OS JVMPROFILE instances one or more instances EJBHOME only selected servlets are monitored JMDOMAIN SQL PROFCLASS EJBMETHOD SERVLET JMCONDITION PROFMETHOD SERVLETMETHOD 1-8 PATROL for BEA WebLogic User Guide

27 WebLogic Data Collection Figure 1-2 shows how the PATROL Console interacts with the PATROL Agent on a WebLogic administration server. Performance data is maintained by BEA WebLogic using JM Mbeans. This data is then ected by a Java-based PATROL ector and returned to PATROL via a PATROL Script Language (PSL) pipe. Profiling data on J2EE objects (like EJBs, SQL, or servlets) uses the JVMPI interface to communicate with applications running on the server. Figure 1-2 Collector Architecture of PATROL for BEA WebLogic Console PATROL Console PATROL for BEA WebLogic other PATROL Console KMs PATROL Console WebLogic Administration Server PATROL Agent PATROL for BEA WebLogic other PATROL Agent KMs PATROL Agent PSL Pipe PATCOL WebLogic (Java ector) JM JVM WebLogic Server ServerMBean EJBMBean JDBCMBean... J2EE objects profiling data JVMPI PATROL Profiler ML Message Profiling Data Storage Product Components and Capabilities 1-9

28 Application Classes and Icons PATROL for BEA WebLogic contains several applications and application containers. Application containers that group together multiple instances of a managed resource. The BEAWLS_SERVER application container represents the entire BEA WebLogic Server environment and acts as a container for all PATROL for Exchange Server applications. This is the icon that appears in the Console window for a specific computer host. The BEAWLS_SETUP icon and the BEAWLS_SERVER icon are displayed in the computer window along with the operating system application icons and the PATROL Agent icon. See Figure 1-3. The BEAWLS_SETUP icon is used to configure the product (described in Configuring the KM on page 3-3). Figure 1-3 PATROL Console setup icon for PATROL for BEA WebLogic icon for monitoring and managing BEA WebLogic Server 1-10 PATROL for BEA WebLogic User Guide

29 Table 1-1 shows the icon for each application class, the application class name, and a brief description of its function. Table 1-1 Application Class Icons and Functions (Part 1 of 6) Icon Application Class Name Function BEA WebLogic 6.x, 7.0, or 8.1 Server Application Class BEAWLS_SERVER represents a BEA WebLogic administration server application instance; at the PATROL Console level, the icon represents the entire WebLogic monitoring environment BEA WebLogic 5.1 Server Application Class BEAWLS_SERVER_V51 represents a BEA WebLogic Server 5.1 instance; at the PATROL Console level, the icon represents the entire WebLogic monitoring environment Setup Application Class BEAWLS_SETUP BEAWLS_SETUP_V51 provides menu commands used to configure the PATROL for BEA WebLogic product Clustering Application Class BEAWLS_CLUSTER represents WebLogic clustering; this is an optional environment supported in BEA WebLogic Server 6.x, 7.0, and 8.1 Database URL Application Class BEAWLS_DBURL BEAWLS_DBURL_V51 represents a database URL on which there are configured JDBC connection pools Product Components and Capabilities 1-11

30 Table 1-1 Application Class Icons and Functions (Part 2 of 6) Icon Application Class Name Function Enterprise Java Bean Application Class BEAWLS_EJB BEAWLS_EJB_V51 represents all deployed Enterprise Java beans deployed on a given server EJB Home Application Class BEAWLS_EJB_HOME EJB Method Application Class BEAWLS_EJB_METHOD BEAWLS_EJB_METHOD_V51 Execution Queues Application Class BEAWLS_EEC_QUEUE represents home runtime interfaces of an EJB; monitors and adminsters runtime information (transaction counts) for stateful, stateless, entity beans, and message driven beans for BEA WebLogic Server 6.x, 7.0, and 8.1 provides byte-code instrumentation of selected EJB methods; this application class appears only if EJB method level data ection is enabled via the Advanced Monitoring command in the BEAWLS_SERVER class monitors and manages the execution queues on each server; queues are monitored for queue length, thread activity, and requests processed JCA Application Class BEAWLS_JCA Java Database Connection Pool Application Class BEAWLS_JDBC BEAWLS_JDBC_V51 supports the J2EE Connector Architecture (JCA); monitors configuration and runtime information from a JCA connection pool in BEA WebLogic Server 6.x, 7.0, and 8.1 environments represents all deployed JDBC connection pools and is created at main discovery regardless of the number of configured connection pools 1-12 PATROL for BEA WebLogic User Guide

31 Table 1-1 Application Class Icons and Functions (Part 3 of 6) Icon Application Class Name Function JMS Server Application Class BEAWLS_JMSSERVER monitors and manages the messaging service, which enables communication between applications in BEA WebLogic Server 6.x, 7.0, and 8.1 Jolt for WebLogic Application Class BEAWLS_JOLT BEAWLS_JOLT_V51 represents configured Jolt connection pools deployed in the WebLogic environment Jolt is a Java-based client API that manages requests for BEA Tuxedo services JVM Profiler Application Class BEAWLS_JVMPROFILER BEAWLS_JVMPROFILER_V51 provides statistical information about the Java Virtual Machine (JVM) when the profiling advanced monitoring option is enabled Local Managed Application Class BEAWLS_LOCAL_MANAGED Log File Monitoring Application Class BEAWLS_LOG BEAWLS_LOG_V51 monitors and manages a WebLogic managed Server that is running on the same host as the PATROL Agent in the BEA WebLogic Server 6.x, 7.0, and 8.1 environment (see also the Managed Server Application Class, BEAWLS_MANAGED) monitors log files and generates events for the PATROL Event Manager Domain, Server, HTTP, and JDBC log files are monitored Product Components and Capabilities 1-13

32 Table 1-1 Application Class Icons and Functions (Part 4 of 6) Icon Application Class Name Function Managed Server Application Class BEAWLS_MANAGED monitors and manages a managed WebLogic Server that is remote to a given PATROL Agent (see also Local Managed Server Application Class, LOCAL_MANAGED) in an environment with multiple WebLogic Server instances, one server will be designated the administrative server and others designated as managed servers Operating System Application Class BEAWLS_OS monitors the local operating system of a host on which a monitored WebLogic Admin Server JVM is running; also monitors all JVMs on local managed servers Response Time Probe Application Class BEAWLS_PROBE BEAWLS_PROBE_V51 provides connection time and estimated transfer rate to the administrative server via the AvgPingTime and AvgConnTime parameters Profiling Application Class BEAWLS_PROF_CLASS container for Java classes for which method level response information is being ected this application class is created only when JVM performance data ection is turned on via the Advance Monitoring menu command in the BEAWLS_SERVER class and method profiling is turned on via the Configure Method Profiling menu command in BEAWLS_SERVER 1-14 PATROL for BEA WebLogic User Guide

33 Table 1-1 Application Class Icons and Functions (Part 5 of 6) Icon Application Class Name Function Profiling Method Application Class BEAWLS_PROF_METHOD BEAWLS_PROF_METHOD_V51 container for Java classes for which method level response information is being ected this application class is created only when JVM performance data ection is turned on via the Advance Monitoring menu command in the BEAWLS_SERVER class and method profiling is turned on via the Configure Method Profiling menu command in BEAWLS_SERVER HTTP and JSP Servlet Application Class BEAWLS_SERVLET BEAWLS_SERVLET_V51 represents HTTP, JSP, and servlets HTTP, JSP, and servlets represent server-side logic in e-commerce applications Servlet Method Application Class BEAWLS_SERVLET_METHOD BEAWLS_SERVLET_METHOD_ V51 monitors methods for a selected servlet monitors only doget, doput, dodelete, and dopost methods SQL Application Class BEAWLS_SQL BEAWLS_SQL_V51 monitors SQL statements Web Applications Application Class BEAWLS_WEBAPP monitors and manages resources used by a web application running on a configured and managed WebLogic Server monitors all deployed web applications and can monitor specific servlets for a given application this applies only to BEA WebLogic Server 6.x, 7.0, and 8.1 environments Product Components and Capabilities 1-15

34 Table 1-1 Application Class Icons and Functions (Part 6 of 6) Icon Application Class Name Function JM_MAIN Application Class JM_MAIN provides administrative functions for the JM component this applies only to BEA WebLogic Server 6.x, 7.0, and 8.1 environments JM_DOMAIN Application Class JM_DOMAIN each instance represents a grouping of MBeans; from this icon, you can manage all MBeans that have the same domain name this applies only to BEA WebLogic Server 6.x, 7.0, and 8.1 environments JM_SERVER Application Class JM_SERVER each instance represents an MBean server; MBean servers for BEA WebLogic are automatically registered this applies only to BEA WebLogic Server 6.x, 7.0, and 8.1 environments JM_CONDITION Application Class JM_CONDITION each instance represents a monitored condition that you have previously defined; the condition includes definitions of attribute value thresholds and notifications; if a condition applies to a single JM domain, the icon is a child of JM_DOMAIN, if it applies to multiple domains, it is a child of JM_SERVER this applies only to BEA WebLogic Server 6.x, 7.0, and 8.1 environments 1-16 PATROL for BEA WebLogic User Guide

35 Application Instance Naming Conventions The application classes in this product use the naming conventions shown in Table 1-2 for labeling icons to differentiate each application class instance. Table 1-2 Instance Naming Conventions (Part 1 of 2) Application Instance Naming Convention Example BEAWLS_EJB_ HOME BEAWLS_EEC _QUEUE BEAWLS_JCA BEAWLS_JDBC BEAWLS_ JMSSERVER BEAWLS_JOLT BEAWLS_LOG BEAWLS_ MANAGED BEAWLS_ PROBE BEAWLS_PROF_ CLASS full JNDI name of bean, or display name (for 7.0 and 8.1) unique name for the execute queue; these are created at startup the JCA application name which is the name of its resource adapter archive file (.rar) unique user-defined name specified when creating JDBC connection pool unique instance name of the JMS server unique user-defined name specified when creating Jolt connection pool user-defined name specified in Log Name Alias field of the dialog box that appears when setting up monitoring for another log by default, the application creates instances for the JDBC, HTTP, DOMAIN, and Server log files, as defined in the WebLogic MBean server configuration name of the remote managed server (remote to this PATROL Agent) role of the server (admin or local managed) being monitored name of the Java class being profiled portal.portalgrouphierarchyhome, theory.smart.ebusiness.tax. TaxCalculator, TheCart MyAppQueue BlackBoxNoTx commercepool, docpool examplejmsserver ccjoltpool, demojoltpool JDBC, HTTP, SERVER, DOMAIN sales_server2 Admin_PROBE, LocalMgr_PROBE weblogic.managementadmin Product Components and Capabilities 1-17

36 Table 1-2 Instance Naming Conventions (Part 2 of 2) Application Instance Naming Convention Example BEAWLS_PROF_ METHOD BEAWLS_ SERVER BEAWLS_ SERVLET BEAWLS_ WEBAPP JM_SERVER JM_DOMAIN JM_CONDITION name of the method being profiled unique server instance name specified when registering a server file name of the servlet executable file name of the web application a web archive contains all of the files that make up a web application the string MBeans on followed by server name name of the web application containing the bean condition label you specified when defining the condition getshoppingcart WLServer1 surveyresponse, RegistrationForm petstore MBeans on QSERVE5 petstore(administration) MonitorEStoreAcct 1-18 PATROL for BEA WebLogic User Guide

37 Accessing Product Help PATROL provides Help topics for the currently displayed window or dialog box. You can also start Help by right-clicking the PATROL for BEA WebLogic application and choosing KM Commands => Product Help in a Windows NT console or choosing Product Help in a Unix console. To get Help for a specific application class or parameter, see the steps described in Table 1-3 and Table 1-4. From a Windows NT Console Table 1-3 Accessing Online Help from a Windows NT Console Type of Help How to Access a specific application class 1. From the KM tab of the PATROL Console, double-click the application class icon. 2. From the Help tab, click Show Help. a specific parameter Use one of these methods: From the parameter pop-up menu, choose Help On. From the parameter properties dialog box, click the Help tab and then click Show Help. From a Unix Console Table 1-4 Accessing Online Help from a Unix Console Type of Help a specific application class a specific parameter How to Access From the Application Definition dialog box, click the Show Help button. From the parameter pop-up menu, choose Help On. Product Components and Capabilities 1-19

38 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: For the latest updates to product information, refer to the release notes, which are also available at: Where to Go from Here If you are ready to install and configure the PATROL for BEA WebLogic product, see Chapter 2, Installing and Migrating PATROL for BEA WebLogic. If you are already running the product, see Chapter 4, Using PATROL for BEA WebLogic PATROL for BEA WebLogic User Guide

39 2 Installing and Migrating PATROL for BEA WebLogic 2 This chapter describes how to install and upgrade PATROL for BEA WebLogic Installation Requirements System Additional Requirements if Using JVM Profiling Performance and Scalability License Installation Account Preparing to Install Installation Prerequisites Determine the Version of the Installation Utility Target Computers and Their Roles Determining Where to Install KMs Based on Architecture Typical and Custom Installation Types PATROL Security Installing for the First Time Typical New Installation Upgrading from an Earlier Version Prepare to Upgrade Upgrade Without Migrating Prior-version Customizations Upgrade and Preserve Customizations Migrate Your Customizations Creating and Installing Installable Images Create an Installable Image Install the Created Installable Image Installing and Migrating PATROL for BEA WebLogic 2-1

40 Installing the Online Help Browser (Unix) Uninstalling PATROL for BEA WebLogic PATROL for BEA WebLogic User Guide

41 Installation Requirements Before installing PATROL for BEA WebLogic version , 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. System Before installing PATROL for BEA WebLogic, verify that the target computer meets the installation requirements listed in Table 2-1. Table 2-1 PATROL for BEA WebLogic Installation Requirements (Part 1 of 2) Resource Minimum Requirements Comments operating system BEA WebLogic Server Java Development Kit (JDK) Solaris 2.6, 7, or 8 HP-U 11.0 and 11i Compaq Tru64 Unix 4.0G through 5.1 IBM AI 4.3 or 5.1 Red Hat Linux 6.1, 6.2, or 7.1 Windows 2000 or Windows NT 4.0 (SP 4 or higher) Linux for S/390 and zseries 5.1 (any service pack) 6.0 (service pack 2) varies J2EE instrumentation and profiling is not supported for Tru64 or Linux 5.1A or 6.0 with sp1 if used on Tru64 Unix PATROL for BEA WebLogic works with all JDK versions supported by BEA for a particular supported platform. See e-docs.bea.com/wls/certifications/ certifications/index.html Additional requirements for JVM profiling and instrumentation features are described in Table 2-2 Installing and Migrating PATROL for BEA WebLogic 2-3

42 Table 2-1 PATROL for BEA WebLogic Installation Requirements (Part 2 of 2) Resource Minimum Requirements Comments PATROL products PATROL Agent or 3.5 PATROL Clasic Console for Unix or Windows ( or 3.5) or PATROL Central Operator Windows Edition or Web Edition PATROL for Unix PATROL for MS Windows Servers PATROL for Unix and MS Windows KMs are required for OS-level information used in the BEAWLS_OS application class. disk space 50 MB disk space requirements may be less depending on console type memory 1 gigabyte or more basic KM functions will work with less than 1 GB, but if profiling features are enabled, performance will be degraded processor speed 1 gigahertz or more basic KM functions will work with less than 1 GHz, but if profiling features are enabled, performance will be degraded 2-4 PATROL for BEA WebLogic User Guide

43 Additional Requirements if Using JVM Profiling If you plan to use the JVM profiling features of this product, verify that the target computer meets the additional, more specific, installation requirements listed in Table 2-2. Other JDK versions may work with the product on these platforms, but have not been tested. Table 2-2 System Requirements for JVM Profiling Operating System Microsoft Windows NT 4.0 (SP 4 or higher) or Windows 2000 WebLogic Version and Service Pack WebLogic 5.1 SP 13 WebLogic 6.1 SP4 WebLogic 6.1 SP 5 WebLogic 7.0 SP 2 WebLogic 8.1 (GA) JDK Version Sun JRE 1.2.2_007 Sun JDK Sun JDK 1.3.1_06-b01 Sun JDK 1.3.1_07-b02 Sun JDK 1.3.1_06-b01 Sun JDK 1.4.1_02-ea Solaris 7 or 8 WebLogic 5.1 SP 13 Sun JRE version 1.2.2_007 (reference implementation only Sun JDK b24 (production version) WebLogic 6.1 SP 4 WebLogic 7.0 SP 2 WebLogic 8.1 (GA) Sun JDK 1.3.1_06-b01 Sun JDK 1.3.1_06-b01 Sun JDK 1.4.1_02-ea HP-U 11.0 or 11i WebLogic 5.1 SP 13 HP JDK 1.3.1_06 WebLogic 6.1 SP 4 HP JDK _ WebLogic 7.0 SP 2 HP JDK WebLogic 8.1 (GA) N/A IBM AI 4.3 or 5.1 WebLogic 5.1 SP 13 IBM JDK WebLogic 6.1 SP 4 IBM JDK WebLogic 7.0 SP 2 IBM JDK WebLogic 8.1 (GA) N/A The following JDK versions have been tested but found to fail with advanced monitoring features: Sun JDK 1.3.1_01, 1.3.1_02-b02, and 1.3.1_03-b03, and IBM JDK Installing and Migrating PATROL for BEA WebLogic 2-5

44 Performance and Scalability BMC Software tested PATROL for BEA WebLogic version to assess its performance in typical WebLogic environments in different configurations. Generally, we found that: In a basic out-of-the-box configuration, monitoring an active WebLogic environment, PATROL for BEA WebLogic 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. 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 BMC s Contract Administration department for licensing information. Installation Account Install PATROL for BEA WebLogic 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. 2-6 PATROL for BEA WebLogic User Guide

45 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. 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: 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. Installing and Migrating PATROL for BEA WebLogic 2-7

46 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 computers on which you want to install PATROL must have ftp and telnet enabled. PATROL configuration requires privileges usually reserved by the system administrator. These privileges include access to a root account on the hardware where you want to install PATROL. BMC Software recommends that you install PATROL on local partitions, not on NFS-mounted partitions. If you do install PATROL on NFS-mounted partitions, the root account must have been granted root access privileges on the NFS server. 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. Preparing to Install 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. Note If you want to install the product into the PATROL KMDS, do not launch the installation program from the CD. See Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Using the KMDS on page PATROL for BEA WebLogic User Guide

47 The installation program installs only to a local computer. The install program cannot perform remote installations. You must install PATROL for BEA WebLogic and a PATROL Agent on each machine you want monitored (the hosts on which you run BEA WebLogic). You must also install PATROL for BEA WebLogic and a PATROL Console on each machine from which you want to monitor your environment. Note The installation program provides the ability to export an installation package after you make all your selections. If you place the installation package in a shared directory, you can use it to install BMC Software products on all computers that share the same BMC products directory, PATROL default login, PATROL Agent port number, PATROL product directories, and security options. For additional information about the installation process, see the PATROL Installation Reference Manual. Installation Prerequisites Before you install, you must ensure you are using the appropriate version of the installation utility (see page 2-10) understand target machines and their roles (see page 2-11) understand PATROL security options (see page 2-13) (if you are using PATROL KMDS) know how to start the installation utility to install into the KMDS (see Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Using the KMDS on page 2-26) Installing and Migrating PATROL for BEA WebLogic 2-9

48 Determine the Version of the Installation Utility The installation instructions contained in this version of the PATROL for BEA WebLogic User Guide pertain to version 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 , the instructions in this manual may not precisely match what you see on your screen. To determine the version of an installation utility, perform the following steps: Step 1 Step 2 Step 3 Open a command prompt. Navigate to the directory where the installation utility is located. Enter one of the following commands: setup.exe -v (Windows) setup.sh -v (Unix) A message box displays the version of the installation utility PATROL for BEA WebLogic User Guide

49 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. 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, manage, and develop KMs on Unix by using a PATROL Classic Console for Unix monitor, manage, and develop KMs on Windows by using a PATROL Classic Console for Windows 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 host KMs and components that contain the knowledge that PATROL uses to monitor the resources on this computer A Common Services (new with 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 Installing and Migrating PATROL for BEA WebLogic 2-11

50 For more information about these products, see PATROL Console Server and RTserver Getting Started, PATROL Central Operator Web Edition Getting Started, and PATROL Central Operator Web Edition online Help. 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. 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. Typical and Custom Installation Types The installation utility prompts you to select one of the following installation types: In general, use the Typical installation type if you are installing PATROL for BEA WebLogic 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 PATROL for BEA WebLogic User Guide

51 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 BEA WebLogic and have a PATROL environment that may be configured with non-standard settings. 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. 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 PATROL Security User Guide. Installing and Migrating PATROL for BEA WebLogic 2-13

52 Installing for the First Time This section describes how to do a new install of PATROL for BEA WebLogic. If you are experienced with the PATROL KMDS, you can optionally install to PATROL 3.4.x environments using that tool. See Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Using the KMDS on page 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 If you want to use a different port, you must use the Custom installation, see Upgrading from an Earlier Version on page Typical New Installation To do a Typical first time install: Step 1 Step 2 Insert the PATROL for BEA WebLogic product CD in the CD-ROM. If you are using a Unix system, mount the CD. 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 setup.exe (Windows) or setup.sh (Unix). 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: 2-14 PATROL for BEA WebLogic User Guide

53 2.A From a command line prompt, change to the directory in which the installation utility is located. 2.B Start the installation utility using one of the following commands: Unix:./setup.sh -serveronly Windows: setup.exe -serveronly 2.C Start a web browser. 2.D Direct the browser to the URL displayed in the message box (enter the URL in your browser s Go To field). Note If you are installing on Compaq Tru64 4.0, you may need to use the target override option. To do this, start the setup using the following command:./setup.sh -target_override OSF1-alpha-V4 Step 3 Step 4 Step 5 In the Welcome to the Installation Utility window, click Next to begin your installation. Accept Licence Agreement, select Accept then click Next to continue. From the Select Installation Option window, select I want to install products on this computer now, then click Next. The Select Installation Option screen provides the option to export an installable image to a directory. This installable image can be used to install on several computers or to complete an installation on a local computer at a later time. See Creating and Installing Installable Images on page 2-37 for information about using this feature. Step 6 Step 7 From the Select Type of Installation window, select the Typical installation method and click Next. In the Specify Installation Directory window, enter a directory path if you do not wish to accept the default directory. Click Next to continue. Installing and Migrating PATROL for BEA WebLogic 2-15

54 Step 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. If you are not sure which option to choose, select both Console System and Managed System. 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 BEA WebLogic Server). Select Common Services if you are installing to a computer that will host the PATROL Central Operator - Web Edition (PATROL 7.x architecutre) web server, the PATROL Console Servers, or the RTservers. Step 9 From the Select Products and Components to Install window (see Figure 2-1), click + to expand the PATROL Solutions branch, then select PATROL for BEA WebLogic version Figure 2-1 Select Products to Install using Typical Install Step 10 Step 11 Complete the remaining dialogs. The number and contents of the dialogs depends on your KM selections and your inputs to the dialogs. Click Help, as needed, to complete the dialogs. 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 PATROL for BEA WebLogic User Guide

55 Step 12 Step 13 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.) You can click View Log to review details of the installation, or click Exit to close the installation utility. Upgrading from an Earlier Version If you are installing PATROL for BEA WebLogic version as an upgrade to a previous version, you need to decide whether you wish to preserve any local customizations that you made to the KM. Whether you choose to save and migrate your KM customizations or not, customizations to agents and consoles are preserved and incorporated into the new version automatically. Only customizations to Knowledge Modules must be migrated. Note Throughout this section, all references to PATROL_HOME represent $PATROL_HOME in Unix and %PATROL_HOME% in Windows; all references to PATROL_CACHE represent $PATROL_HOME/patrol in Unix and %PATROL_CACHE% in Windows. Prepare to Upgrade Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation remove PATROL for BEA WebLogic files from PATROL_CACHE Installing and Migrating PATROL for BEA WebLogic 2-17

56 Back Up the Current Installation Whether you are upgrading and migrating any customizations or simply upgrading, back up the current PATROL installation before starting to install. Follow these steps to back up the current installation: Step 1 Step 2 Step 3 Shut down any PATROL Agents, Consoles, and related services that are currently running. Ensure that no one is accessing any PATROL files or directories. Perform a full backup of the PATROL_HOME and PATROL_CACHE directories; these are where PATROL executables and data are typically stored. These directories are listed in Table 2-3. Table 2-3 PATROL Installation Directories to Back Up Operating System Windows Unix Directory %PATROL_HOME% for agent and console installation directories %PATROL_CACHE% for the console working cache $PATROL_HOME for agent and console installation directories $PATROL_CACHE for the console working cache Remove PATROL for BEA WebLogic Files from PATROL_CACHE You must remove the current PATROL for BEA WebLogic 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. Delete all PATROL for BEA WebLogic files with the following naming patterns from PATROL_CACHE\knowledge and PATROL_CACHE\psl: BEAWLS* Upgrade Without Migrating Prior-version Customizations Use this upgrade procedure if you made no customizations to a previous versions, or you want to overwrite any customizations that you did make PATROL for BEA WebLogic User Guide

57 Step 1 Step 2 Insert the PATROL for BEA WebLogic product CD in the CD-ROM. If you are using a Unix system, mount the CD. If you are installing into PATROL 3.4.x in a Unix environment, follow these steps to start the installation utility. If you are installing into PATROL 3.4.x in a Windows environment or into PATROL 3.5 in either a Unix or Windows environment, skip to Step 3. 2.A Open a command line prompt. 2.B Change to the drive where the installation CD is located. 2.C At the Unix command line prompt, enter setup.sh -releaseversion v.r where v.r is the version of the PATROL environment into which you are installing (for example, 3.4). Step 3 Step 4 Step 5 Step 6 If the installation program did not automatically start, or if you are installing an electronically downloaded product (EPD), start the installer. From the installation CD, run setup.exe (Windows) or setup.sh (Unix). In the Welcome to the Installation Utility window, click Next to begin your installation. In the Review License Agreement window, review the license agreement, select Accept, and click Next to continue. From the Select Installation Option window, select I want to install products on this computer now, then click Next. The Select Installation Option screen provides the option to export an installable image to a directory. This installable image can be used to install on several computers or to complete an installation on a local computer at a later time. See Creating and Installing Installable Images on page 2-37 for information about using this feature. Step 7 From the Select Type of Installation Window, select Custom then click Next. Installing and Migrating PATROL for BEA WebLogic 2-19

58 Step 8 In the Specify Installation Directory window, enter the directory path based on your environment, then click Next. Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-4 PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-5 the directory path up to the PATROL product directory the full directory path to your previously installed products the directory path up to the PATROL product directory the full directory path to your previously installed products To install PATROL into D:\Program Files\BMC Software\PATROL3-4, enter D:\Program Files\BMC Software in the Specify Installation Directory window. To install into the previously installed directory C:\PATROL3-4, enter C:\PATROL3-4 in the Specify Installation Directory window. To install PATROL into D:\Program Files\BMC Software\Patrol3, enter D:\Program Files\BMC Software in the Specify Installation Directory window. To install into the previously installed directory C:\PATROL3-5, enter C:\PATROL3-5 in the Specify Installation Directory window PATROL for BEA WebLogic User Guide

59 Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Unix PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Unix the full directory path to your previously installed products the full directory path to your previously installed products To install into the previously installed directory /opt/patrol/patrol3.4, enter /opt/patrol/patrol3.4 in the Specify Installation Directory window. To install into the previously installed directory /opt/patrol/patrol3, enter /opt/patrol/patrol3 in the Specify Installation Directory window. The PATROL product directory is appended to the path that you enter in this step. You will specify the PATROL installation directory in Step 11 on page Step 9 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. If you are not sure which option to choose, select both Console System and Managed System. Select Console System if you are installing to computer that will host the PATROL 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 BEA WebLogic Server). Do not select the Common Services option. Step 10 In the Select Products and Components to Install window (see Figure 2-2), click + to expand the PATROL Solutions branch, then select PATROL for BEA WebLogic version All of the components that are part of the WebLogic solution will automatically be selected. Installing and Migrating PATROL for BEA WebLogic 2-21

60 Figure 2-2 Product Selection Dialog - Custom Install click only this solution Step 11 In the Provide the PATROL 3.x Product Directory window, enter the directory where you want to install PATROL for BEA WebLogic as appropriate for your installation scenario. Use the following table as a guide. Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows the directory path up to the PATROL product directory the directory path up to the PATROL product directory To install PATROL into D:\Program Files\BMC Software\PATROL3-4, enter PATROL3-4 in the PATROL 3.x Product Directory field. To install PATROL into D:\Program Files\BMC Software\Patrol3, enter Patrol3 in the PATROL 3.x Product Directory field PATROL for BEA WebLogic User Guide

61 Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-4 PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-5 PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Unix PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Unix do not enter anything; delete any defaults in this field do not enter anything; delete any defaults in this field do not enter anything; delete any defaults in this field do not enter anything; delete any defaults in this field To install into the previously installed directory C:\PATROL3-4, do not enter anything in the PATROL 3.x Product Directory field. To install into the previously installed directory C:\PATROL3-5, do not enter anything in the PATROL 3.x Product Directory field. To install into the previously installed directory /opt/patrol/patrol3.4, do not enter anything in the PATROL 3.x Product Directory field. To install into the previously installed directory /opt/bmc/patrol3, do not enter anything in the PATROL 3.x Product Directory field. Step 12 Complete the Confirm BMC Startup Information window if it appears (this window will not appear in some configuration scenarios). 12.A In the Specify the Current Agent Port Number field, enter the port number you want the PATROL Agent to use. The default is Note If your previous installation used a different port number, change the default to the current port number for the PATROL Agent. Installing and Migrating PATROL for BEA WebLogic 2-23

62 12.B In the Restart the PATROL agent automatically? field, select Yes or No: If you want the installation utility to restart the PATROL Agent after the installation is complete, select Yes. If you want to manually restart the PATROL Agent after the installation is complete, select No. Step 13 Step 14 Complete the remaining dialogs. The number and contents of the dialogs depends on your KM selections and your inputs to the dialogs. Click Help, as needed, to complete the dialogs. 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, or Create Image if you are creating an installable image. Step 15 Step 16 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.) You can click View Log to review details of the installation, or click Exit to close the installation utility. Upgrade and Preserve Customizations Use the appropriate procedure in this section if you want to upgrade to the new version of PATROL for BEA WebLogic and you want to preserve any customizations you have made to the previous version of PATROL for BEA WebLogic PATROL for BEA WebLogic User Guide

63 After you have finished this procedure, see Migrate Your Customizations on page 2-33 for instructions about incorporating your customizations into the new version. You should complete this process on a limited number of machines in the test environment first, test the merged KMs thoroughly, and then deploy them to your production environment. Note To upgrade and preserve customizations, you must either migrate your customizations manually or use the PATROL Migration Tools version 3.5 (no KMDS required), or have the latest version of KMDS installed as well as any available patches. Determine Whether You Can Migrate Before migrating customizations, you must determine whether or not the customizations to the previous version of PATROL for BEA WebLogic that you have installed can be migrated to the new version of PATROL for BEA WebLogic. See Table 2-4 to determine whether migration is supported for your current version of PATROL for BEA WebLogic. If migration is supported, choose one of the following installation procedures to migrate your customizations: migrating customizations using the PATROL Migration Tools version 3.5 (page 2-26) migrating customizations using the PATROL Migration Tools version and the PATROL KMDS(page 2-26) migrating customizations manually (page 2-28) Table 2-4 Versions That You Can Migrate Component Version PATROL for BEA WebLogic , PATROL for BEA WebLogic PATROL for BEA WebLogic PATROL for BEA WebLogic Installing and Migrating PATROL for BEA WebLogic 2-25

64 Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Using the PATROL Migration Tools Version 3.5 Step 1 Ensure that the product CD is accessible when you are running the migration tools. The process of migrating KM customizations from a PATROL 3.x environment to PATROL 3.5 no longer depends on the PATROL KMDS. Because the PATROL Migration Tools version 3.5 copy the new product files directly from the product CD rather than from KMDS, you do not have to install the new version of PATROL for BEA WebLogic into KMDS. Just ensure that the product CD is accessible when you are running the migration tools. Step 2 Use the PATROL Migration, Merge and Probe tools as described in the PATROL Migration Tools User Guide. For specific instructions and detailed information about using the PATROL Migration Tools version 3.5, see the PATROL Migration Tools User Guide. Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Using the KMDS Step 1 Step 2 Open a command line prompt. Change to the drive where the installation CD is located. Step 3 Enter the correct command for your operating system (Table 2-5 describes the command line options.): At the Windows command line prompt, enter setup.exe -kmds [-kmdsportnum portnum] At the Unix command line prompt, enter setup.sh -kmds [-kmdsportnum portnum] [-releaseversion v.r 2-26 PATROL for BEA WebLogic User Guide

65 ] Table 2-5 Command Line Options for Installing in a KMDS Environment KMDS Installation Options -kmdsportnum portnum -releaseversion v.r Description optional; use only if you are not using the default KMDS port number 3182 optional; use only if you are installing to a Unix PATROL 3.4.x environment. v.r designates the version number of the PATROL environment into which you are installing (for example, -releaseversion 3.4). The installation utility opens in KMDS mode. Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 In the Welcome to the Installation Utility window, click Next to begin your installation. In the Review License Agreement window, review the license agreement, select Accept, and click Next to continue. In the Select Installation Option window, select I want to install products. In the Specify KMDS directory window, enter the full path to the directory in which the KMDS is installed and click Next. From the Select Products and Components to Install window, select the KMs that you want to install and click Next. In the Review Selections and Install window, review the selections carefully to make sure they are correct. If you want to change your selections, click Back and make those changes. If the selections are correct, click through the rest of the windows in the installation utility to install PATROL for BEA WebLogic into the KMDS. Installing and Migrating PATROL for BEA WebLogic 2-27

66 Installing the New Version of PATROL for BEA WebLogic If You Are Migrating Customizations Manually Note Use this installation procedure if you do not want to use the PATROL Migration Tools version 3.5 or the PATROL KMDS to migrate the customizations that you have made to the currently installed version of PATROL for BEA WebLogic. Step 1 If you are installing into PATROL 3.4.x in a Unix environment, follow these steps to start the installation utility. If you are installing into PATROL 3.4.x in a Windows environment or into PATROL 3.5 in either a Unix or Windows environment, skip to Step 2. 1.A Open a command line prompt. 1.B Change to the drive where the installation CD is located. 1.C At the Unix command line prompt, enter setup.sh -releaseversion v.r where v.r is the version of the PATROL environment into which you are installing (for example, 3.4). 1.D Skip to Step 3. Step 2 Step 3 Step 4 Step 5 If you have already installed PATROL 3.5 or or you are installing to a Windows environment, start the installation utility by running setup.exe (Windows) or setup.sh (Unix) from the installation CD or from an electronically downloaded (EPD) installation image. In the Welcome to the Installation Utility window, click Next to begin your installation. In the Review License Agreement window, review the license agreement, select Accept, and click Next to continue. In the Select Installation Option window, select select I want to install products on this computer now then click Next to continue PATROL for BEA WebLogic User Guide

67 Step 6 Step 7 From the Select Type of Installation Window, select Custom and click Next. In the Specify Installation Directory window, enter the appropriate directory information based on your installation scenario and click Next. Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-4 PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-5 the directory path up to the PATROL product directory the full directory path to your previously installed products the directory path up to the PATROL product directory the full directory path to your previously installed products To install PATROL into D:\Program Files\BMC Software\PATROL3-4, enter D:\Program Files\BMC Software in the Specify Installation Directory window. To install into the previously installed directory C:\PATROL3-4, enter C:\PATROL3-4 in the Specify Installation Directory window. To install PATROL into D:\Program Files\BMC Software\Patrol3, enter D:\Program Files\BMC Software in the Specify Installation Directory window. To install into the previously installed directory C:\PATROL3-5, enter C:\PATROL3-5 in the Specify Installation Directory window. Installing and Migrating PATROL for BEA WebLogic 2-29

68 Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Unix PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Unix the full directory path to your previously installed products the full directory path to your previously installed products To install into the previously installed directory /opt/patrol/patrol3.4, enter /opt/patrol/patrol3.4 in the Specify Installation Directory window. To install into the previously installed directory /opt/patrol/patrol3, enter /opt/patrol/patrol3 in the Specify Installation Directory window. The PATROL installation directory is appended to the path that you enter in this step. You will specify the PATROL installation directory in Step 10 on page Step 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. If you are not sure which option to choose, select both Console System and Managed System. Select Console System if you are installing to computer that will host the PATROL 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 BEA WebLogic Server). Step 9 From the Select Products and Components to Install window, select the KMs that you want to install and click Next. Note If your previous installation used a different port number, change the default to the current port number for the PATROL Agent PATROL for BEA WebLogic User Guide

69 Step 10 In the Provide the PATROL 3.x Product Directory window, enter the correct information based on your installation scenario and click Next. Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-4 PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Windows where previously installed PATROL products are in a top-level directory such as C:\PATROL3-5 the directory path up to the PATROL product directory the directory path up to the PATROL product directory do not enter anything; delete any defaults in this field do not enter anything; delete any defaults in this field To install PATROL into D:\Program Files\BMC Software\PATROL3-4, enter PATROL3-4 in the PATROL 3.x Product Directory field. To install PATROL into D:\Program Files\BMC Software\Patrol3, enter Patrol3 in the PATROL 3.x Product Directory field. To install into the previously installed directory C:\PATROL3-4, do not enter anything in the PATROL 3.x Product Directory field. To install into the previously installed directory C:\PATROL3-5, do not enter anything in the PATROL 3.x Product Directory field. Installing and Migrating PATROL for BEA WebLogic 2-31

70 Install option Directory Example PATROL for BEA WebLogic into an existing PATROL 3.4 environment on Unix PATROL for BEA WebLogic into an existing PATROL 3.5 environment on Unix do not enter anything; delete any defaults in this field do not enter anything; delete any defaults in this field To install into the previously installed directory /opt/patrol/patrol3.4, do not enter anything in the PATROL 3.x Product Directory field. To install into the previously installed directory /opt/bmc/patrol3, do not enter anything in the PATROL 3.x Product Directory field. Step 11 Complete the Confirm BMC Startup Information window: 11.A In the Specify the Current Agent Port Number field, enter the port number you want the PATROL Agent to use. The default is Note If your previous installation used a different port number, change the default to the current port number for the PATROL Agent. 11.B In the Restart the PATROL agent automatically? field, select Yes or No: If you want the installation utility to restart the PATROL Agent after the installation is complete, select Yes. If you want to manually restart the PATROL Agent after the installation is complete, select No. The Confirm BMC Startup Information window displays only if you are installing into a managed system. Step 12 Complete the remaining windows. The number and content of the windows depend on your KM selections and your inputs to the windows. Step 13 Proceed to Migrate Your Customizations on page PATROL for BEA WebLogic User Guide

71 Migrate Your Customizations Customizations made to PATROL for BEA WebLogic may include changes to the parameter alarm ranges, recovery actions, states, or other parameter properties. You can migrate customizations manually or through the KMDS. Migration of.km files through the KMDS is automated, with the following exceptions: modified PSL code, whether it is embedded in.km files or in.psl files parameter overrides done with a PATROL Operator Console new Knowledge Modules that you created Note Even if you are not using the PATROL KMDS, you can use the PATROL migration tools to help you migrate customizations. For more information about the PATROL migration tools, see the PATROL Migration Tools User Guide. Preparing to Migrate Before you migrate the customizations from the previously installed version of PATROL for BEA WebLogic to the newly installed version of PATROL for BEA WebLogic, you must remove any obsolete KMs from the list of preloaded KMs on each PATROL Agent. See the PATROL Agent Reference Manual for instructions on removing KMs from the preload list. To Migrate Using the PATROL Migration Tools Version 3.5 The following procedure is a general workflow for using the PATROL Migration Tools version 3.5 to migrate your customizations to the new version of PATROL for BEA WebLogic. For detailed explanation and instruction on using the migration tools, see the PATROL Migration Tools User Guide. Installing and Migrating PATROL for BEA WebLogic 2-33

72 Follow this migration procedure only after you have met the following criteria: completed the procedures in Prepare to Upgrade on page installed version 3.5 of the PATROL migration tools, including the KM archive Step 1 Step 2 Step 3 Run the migration probe to locate the base version of PATROL for BEA WebLogic from the KM archive and the new version of PATROL for BEA WebLogic from the product CD. Run the merge tool to merge the base and customized versions of PATROL for BEA WebLogic with the new version of PATROL for BEA WebLogic. Choose one of the following methods to transfer merged KMs to your test environment: Copy the contents of the results directory to the /lib directory where the new version of PATROL for BEA WebLogic is installed. Copy the contents of the packaged results to a CD image then install. Deploy the contents of the merged results directory using a third-party deployment system. Step 4 Perform any additional optional migration tasks as described in the PATROL Migration Tools User Guide. To Migrate Using the PATROL Migration Tools Version and the KMDS Note Before beginning this procedure, ensure that you use the PATROL KMDS version and apply any available patches PATROL for BEA WebLogic User Guide

73 After you have checked your customizations to the previous version of PATROL for BEA WebLogic into the KMDS, use the following steps to migrate your customizations to the new version of PATROL for BEA WebLogic. For detailed instructions about migrating customizations using the KMDS, see the PATROL Migration Tools User Guide. Step 1 Step 2 Use the Probe and Merge tools to identify, preserve, and merge customizations from the prior version of PATROL for BEA WebLogic into the newly installed version of PATROL for BEA WebLogic. See the PATROL Migration Tools User Guide to run the Probe and Merge tools. When prompted during the merge phase of the migration, enter: weblogic_2_2_00.map Warning Make sure that you use the merge map file that was shipped with the new version of PATROL for BEA WebLogic. The default location is PATROL_HOME\lib\migration\new\lib\kmmergemap. Step 3 Step 4 Use KMDS to merge. After you have completed the migration of your changes, load the new version and save the configuration. To Migrate Customizations Manually If you do not want to use the KMDS to migrate customizations, use the following steps to migrate your customizations manually: Step 1 Step 2 Step 3 Move the old PATROL for BEA WebLogic to a new directory that is different from PATROL_HOME. Identify the customizations in PATROL for BEA WebLogic by comparing the content of the text file of the KM in the current PATROL for BEA WebLogic version with the content of the text file for the customized KM that is saved in the PATROL Console cache backup directory. Incorporate your customizations to the new PATROL for BEA WebLogic by performing the following steps: Installing and Migrating PATROL for BEA WebLogic 2-35

74 3.A Restart the PATROL Console. 3.B Load the newly installed PATROL for BEA WebLogic. 3.C Using a PATROL Developer Console, enter the customizations that you identified in Step 2, one by one. To Migrate Customized PATROL Script Language Code Customizations made to PATROL Script Language (PSL) code are not automatically migrated. These customizations may be embedded in.km files or stored in separate.psl files. Migrate these customizations manually, using the following guidelines: If you modified.psl files that were shipped by BMC Software, you must manually re-edit the PSL code in the new KM by using a PATROL Developer Console to reapply your changes. If you modified PSL code embedded in a KM, that code will be overwritten when you install a new version of the product. You must manually edit the.km files by using a PATROL Developer Console to reapply your changes. If you created a new PSL file (not shipped by BMC Software) outside of a.km file, or if you created new PSL code (not shipped by BMC Software) and embedded it in a KM that was shipped by BMC Software, use the pslsearch utility to search your KM for terms that you may have used that have since been adopted by BMC Software as PSL keywords. Reapply your changes by using a PATROL Developer Console. For instructions about using the pslsearch utility, see the PATROL Migration Tools User Guide. Note If you have a customized a PSL library that was compiled with an earlier version of the PSL compiler than the version that was provided with PATROL i, you must manually recompile the library by using the PATROL or later compiler PATROL for BEA WebLogic User Guide

75 Creating and Installing Installable Images The PATROL installation utility installs only to a local computer. The installation utility cannot perform remote installations. You must install a PATROL Agent and PATROL for BEA WebLogic locally on each computer that you want to monitor. You also must install a PATROL Console and PATROL for BEA WebLogic locally on each computer from which you want to view results. The installation utility does provide you with the ability to create an installable image from the products that you select during a regular local installation. If you place the installable image in a shared directory, you can use that installable image to install the selected BMC Software products on all computers that perform the same roles and have these identical requirements: same shared BMC Software directory same PATROL default logon same PATROL Agent port number same platform same security option You can also use a distribution server to distribute the installable images that you create. Note If you create an installable image, all of the computers on which you use the installable image must share the same BMC Software product installation directory, PATROL default logon, PATROL Agent port number, platform, and security option. Create an Installable Image If you selected the I want to create an installable image to be installed later. option in the Select Installation Option window during the installation process, then you elected to share the installation image, execute it later, or execute it several times for computers that share the same roles and installation selections. Installing and Migrating PATROL for BEA WebLogic 2-37

76 Once you select Create Image in the Review Selections and Create Installable Image window, the installation utility finishes exporting the installation image. The installation utility creates an install.ctl file in the specified directory that includes all the configuration information needed to install the products that you selected in the Product Selection window. Before you run the installation image, you might want to change the properties for the image. Read the following instructions and decide whether changing the image is appropriate for your environment: If you want to run the installation package more than once from the same location, change the properties on the installation image file, install.ctl, to Read-Only. Warning The install.ctl file includes the encrypted password for the account that was used during the install process. If the install.ctl file is set to Read-Only, ensure that the install.ctl file is removed from all computers to which the installation image is copied. If you want to distribute the installation image from a central location to multiple machines, do not change the properties of the install.ctl file to Read-Only. Warning If you do not change the install.ctl file to Read-Only, it is deleted after the first time you execute the installation image, and you will not be able to use the exported installation image more than once PATROL for BEA WebLogic User Guide

77 Install the Created Installable Image After you create the installable image, as described on page 2-37, you can then use it to install PATROL for BEA WebLogic on a local computer of the same platform that performs the same roles and has the same shared BMC Software directory, PATROL default logon, PATROL Agent port number, and security options as the options in the installable image. Use the following steps: Step 1 Step 2 Navigate to the directory where the installable image resides. Run the installation utility: On Windows, double-click the install.exe file or type install.exe at a command prompt. On Unix, type./install.sh at a command prompt. The installation utility executes and then creates an installation log that lists the products installed. You can view this log by clicking the View Log button on the final screen of the Installer. The text at the end of the installation log indicates whether or not the installation was successful. Installing the Online Help Browser (Unix) Online help is automatically installed when you install the console KM package (or when you install the KM to the console server). If you are using a PATROL Classic Console for Unix, you must have a supported web browser to be able to view help. These instructions apply only to Unix console users without a supported version of Netscape. Installing and Migrating PATROL for BEA WebLogic 2-39

78 Installing the Unix Version of the Help Browser Summary: The browser that is required for the Unix version of PATROL Help on PATROL version 3.x is Netscape Navigator version 3.01 through 4.xx. However, if you are running a Red Hat Linux platform, you must run Netscape Navigator version 4.x to display the online Help. Currently, PATROL Help does not support Netscape Navigator 6.0. Before You Begin 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. Netscape Navigator is supplied by Netscape Communications Corp. You can locate the browser at Additional Considerations for Using Online Help for Unix When you select Help from the PATROL Console on a Unix system, 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: 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 PATROL for BEA WebLogic User Guide

79 The Exceed for Windows NT 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. To Set Environment Variables 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. Installing and Migrating PATROL for BEA WebLogic 2-41

80 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: Type of Shell Bourne Korn C 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 To use different arguments, set the value of PATROL_BROWSER to the appropriate string. For Korn shell: Example export PATROL_BROWSER=/usr/local/bin/netscape -raise 2-42 PATROL for BEA WebLogic User Guide

81 Uninstalling PATROL for BEA WebLogic You must use the same version of the installation utility that you used to install PATROL for BEA WebLogic to uninstall the product. Use the installation utility in the uninstall mode to uninstall PATROL for BEA WebLogic from your system. 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. Note Before you can uninstall PATROL products, you may need to stop any PATROL processes that are running on the computers where you want to uninstall PATROL. For information about stopping PATROL processes, see the PATROL for Unix User Guide the PATROL Agent Reference Manual the PATROL Knowledge Module Deployment Server Manager User Guide Installing and Migrating PATROL for BEA WebLogic 2-43

82 Uninstalling PATROL for BEA WebLogic from a Unix Environment Summary: The following procedure describes how to uninstall PATROL for BEA WebLogic from a Unix environment. To Uninstall Individual Products Step 1 Step 2 If you had enabled J2EE instrumentation and profiling features in PATROL for BEA WebLogic, remove these features. See To Remove Instrumentation or JVM Performance Monitoring From Your Setup on page Unregister your WebLogic Admin server. 1. Right-click the BEAWLS_SETUP icon. 2. Choose Unregister WebLogic Server from the KM Commands menu. Step 3 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 Step 4 Step 5 Step 6 Step 7 The Welcome window is displayed, and click Next. Select the installation directory from which you want to remove a product, and click Next. Select the product or products that you want to uninstall, and click Next. Review your selections and click Uninstall. After the uninstallation is complete, a window is displayed that tells you whether the uninstallation was successful PATROL for BEA WebLogic User Guide

83 Uninstalling PATROL for BEA WebLogic from a Windows Environment Summary: The following procedures describe how to uninstall products from a Windows environment. To Uninstall Individual Products Step 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. The Welcome window is displayed. Click Next. Step 2 Step 3 Step 4 Select the installation directory from which you want to remove a product, and click Next. Select the product or products that you want to uninstall, and click Next. 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 All Products but Leave Log Files and Configuration Files Step 1 Step 2 Uninstall all products as described in To Uninstall Individual Products. Locate the uninstall.ctl file in the BMC_Products_Installation_directory\Uninstall\Install\instdata directory. Installing and Migrating PATROL for BEA WebLogic 2-45

84 Step 3 Step 4 Step 5 Step 6 Open the uninstall.ctl file in a text editor, such as Notepad, and edit the /BMC/Base variable to specify the name of the directory from which you removed the products in Step 1. Open a command-line prompt. Change to the BMC_Products_Installation_directory\Uninstall\ Install\ instbin directory. Enter the following command: thorinst.exe -uninstall path_to_control_file -log path_to_log_file -output path_to_output_log_file Option Description Value -log -output sends the log information to a standard log file This file contains all installation status information. sends the log information to an output log file This file contains all messages about the progress of the installation that are normally sent to standard output. 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 output 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 PATROL for BEA WebLogic User Guide

85 For example, if C:\Program Files\BMC Software is your product installation directory, you would change to 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 removes 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 are also retained. To Uninstall All Products and Associated Log Files and Configuration Files Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Uninstall all products as described in To Uninstall Individual Products. Locate the uninstall-all.ctl file in the BMC_Products_Installation_directory\Uninstall\Install\instdata directory. Open the uninstall-all.ctl file in a text editor, such as Notepad, and edit the /BMC/Base variable to specify the name of the directory from which you removed the products in Step 1. Open a command-line prompt. Change to the BMC_Products_Installation_directory\Uninstall\ Install\ instbin directory. Enter the following command: thorinst.exe -uninstall path_to_control_file -log path_to_log_file -output path_to_output_log_file Installing and Migrating PATROL for BEA WebLogic 2-47

86 Option Description Value -log -output sends the log information to a standard log file This file contains all installation status information. sends the log information to an output log file This file contains all messages about the progress of the installation that are normally sent to standard output. 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) If a space exists in the path, the entire path must be enclosed in quotation marks. For example, if C:\Program Files\BMC Software is your product installation directory, you would change to 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 removes 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 PATROL for BEA WebLogic User Guide

87 Where to Go from Here Before you can begin using PATROL for BEA WebLogic, you must load the PATROL for BEA WebLogic KMs into the PATROL Console and register WebLogic Server instances. For more information, see Chapter 3, Configuring PATROL for BEA WebLogic. Installing and Migrating PATROL for BEA WebLogic 2-49

88 2-50 PATROL for BEA WebLogic User Guide

89 3 Configuring PATROL for BEA WebLogic 3 After you have installed PATROL for BEA WebLogic and loaded the Knowledge Modules into the PATROL Console, you can begin configuring the product. This chapter describes the following topics. Loading PATROL for BEA WebLogic Configuring the KM To Register a WebLogic 6.x, 7.0, or 8.1 Server To Register a WebLogic 5.1 Server Enabling Instrumentation and Profiling Features Decide What to Enable: Added Value by Feature To Turn On Instrumentation or JVM Performance Monitoring To Disable Either Instrumentation or JVM Performance Monitoring 3-15 To Enable Method-Level Profiling To Disable Method-Level Profiling Setting EJB Deployment for WebLogic To Permanently Deploy the PATROL EJB Collector Verifying and Troubleshooting WebLogic Server Configuration Configuring PATROL for BEA WebLogic 3-1

90 Loading PATROL for BEA WebLogic After you install PATROL for BEA WebLogic, you must load the product KM into the PATROL Console. Before loading the product: start a PATROL Console start a PATROL Agent and BEA WebLogic Server on each machine that you want to monitor load the UNI3 and NT_BASE knowledge files To Load PATROL for BEA WebLogic 1. Add the hosts on which BEA WebLogic Administration Server is running to the PATROL Console. From the PATROL Console menu, choose Hosts => Add. 2. Load the product knowledge files. From the PATROL Console menu, choose File => Load KM Select BEAWLS.kml, then click Open. If you did not previously load UNI3.kml and NT_BASE.kml, select those as well, then click Open. Note If the Unix and NT KMs are not loaded, the BEAWLS_OS application class will not be able to monitor any WebLogic JVM processes. Note This product is enabled for OneKey only when used with the most current versions of the operating system KMs. 4. If your monitoring environment includes any servers running WebLogic Server version 5.1, then select BEAWLS_V51.kml, then click Open. 3-2 PATROL for BEA WebLogic User Guide

91 5. 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 BEA WebLogic is loaded into the PATROL Console, a setup application instance icon is created. This icon is labeled BEAWLS_SETUP. Use this icon to configure the product. Where to Go from Here After you load the KM files, proceed with Configuring the KM. Configuring the KM You must provide configuration information that defines your WebLogic environment to the PATROL monitoring environment. This information includes the server name, the location of WebLogic software on your system, and an administrator account name and password that PATROL can use to perform system management operations. This process is referred to as registering an administration server. Configuration information required for a WebLogic version 5.1 server is somewhat different from that required for a 6.x, 7.0 or 8.1 server. Note Entering a valid administrator account is a mandatory configuration task. If you omit this account or enter an account that is not valid, you cannot complete the configuration nor use the product. Configuring PATROL for BEA WebLogic 3-3

92 To Register a WebLogic 6.x, 7.0, or 8.1 Server 1. Right-click the BEAWLS_SETUP icon and choose KM Commands => Register WebLogic Server. The Select WebLogic Server Version dialog is displayed. 2. Click the button for the version of BEA WebLogic Server you have installed, then click Next. The Register WebLogic Server Manager dialog box is displayed. 3-4 PATROL for BEA WebLogic User Guide

93 3. Enter or change any field values to describe your environment (see Table 3-1). Note You can register and monitor as many managed servers as you wish, but you must always register the WebLogic instance that is designated as Admin. The PATROL Agent and PATROL for BEA WebLogic must be installed on every monitored host (see Chapter 2 for installation information). Table 3-1 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 6.x, 7.0, and 8.1) (Part 1 of 2) Field Name Monitor WebLogic Admin Server ID Description name you want used for this server instance the default is the server name found in the startup batch file (Windows) or script file (Unix); although you can use a different name, each server instance name must be unique the name must begin with a letter, not a number nor special character; do not use a space in this ID Installed WebLogic Home full directory path where the local WebLogic Server application is installed; this is not the same as WebLogic Commerce Server; this is the value in $WL_HOME for example, d:\bea\wlserver6.1 or d:\bea70\weblogic700 or d:\weblogic700 DNS Hostname DNS hostname on which the WebLogic Admin server is running this name will usually be t3://localhost, except when clustering is used; t3 is the WebLogic communication protocol Configuring PATROL for BEA WebLogic 3-5

94 Table 3-1 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 6.x, 7.0, and 8.1) (Part 2 of 2) Field Name Port Number Description port number on which the WebLogic Server is listening the default port number is 7001; the port number is listed in config.xml Note: the PATROL for BEA WebLogic Java ector will be using the specified DNS hostname and port number to connect to the monitored WebLogic Admin server. For example, t3://xyz.com:7001 Administrator Username WebLogic system ID, this may or may not also be an operating system account Note: the account under which the PATROL agent runs must have the following permissions: read for the WebLogic home directory and all subdirectories read-execute for the Java home and all subdirectories Administrator Password enter the password for the username specified in the previous field Note: passwords that contain special characters (such as < or >) may cause error messages and unpredictable results when you use the commands in the BEAWLS_PROBE application class. 4. Click Next. The Setup Java Environment dialog box is displayed. 3-6 PATROL for BEA WebLogic User Guide

95 Table 3-2 Setup Java Environment Dialog Box Fields Field Name JDK Path Description full directory path where the Java Developer Kit is installed; this should reflect the JDK version supported by BEA for your platform, this field is populated by default if the environment variable JAVA_HOME is set if JAVA_HOME is not set, this field will default to the subdirectory of the shipped JDK lib toolkit under the installed WebLogic application directory (for example, d:\bea\jdk130) you can optionally specify the path to an installed JRE, for example, if your Java executables are under /usr/weblogic51/jre1_2/jre/bin, you would enter the path to the directory above bin, /usr/weblogic51/jre1_2/jre Java Class Path optional field list of directory paths that Java searches (in order) when looking for executables; the value in this field is used by the ector you need to change this field only to specify additional paths, for example, you may need to specify additional directories in this field if you have installed service packs the default class path will include weblogic.jar, weblogic_sp.jar, and the java ector path 5. Change the path values, if necessary, then click OK. Note The Java Class Path field must include paths for any WebLogic service packs that you have installed. If you apply additional service packs after registering your server, you will need to update the Java Class Path field by using the Update Registered Server KM menu command. Configuring PATROL for BEA WebLogic 3-7

96 To Register a WebLogic 5.1 Server 1. Right-click the BEAWLS_SETUP_V51 icon and choose KM Commands => Register WebLogic Server. The Register WebLogic Server Manager dialog box is displayed. 2. Enter or change any field values to describe your environment (see Table 3-3). The default values are taken from the batch file that runs when WebLogic starts. 3. Click Next. The Java Environment Setup dialog box is displayed. 4. Change the path values, if necessary, then click OK. Table 3-2 on page 3-7 describes the fields. 3-8 PATROL for BEA WebLogic User Guide

97 Table 3-3 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 5.1) Field Name Monitor WebLogic Server ID Description name you want used for this server instance this server name must be exactly the same (including case) as the WebLogic Server name for example, if the WebLogic server is named myserver, then this field must contain myserver ; if the configuration is for a server in one cluster whose name is also used in another cluster, then this field will contain the cluster and server name separated by an exclamation point in the form: <server_name>!<cluster_name> the default value for this field is the server name found in the startup batch file (Windows) or script file (Unix) the name must begin with a letter, not a number nor special character; do not use a space in this ID Installed WebLogic Home DNS Hostname full directory path where the WebLogic application is installed; this is not the same as WebLogic Commerce Server DNS hostname on which the server is running this name will usually be t3://localhost, except when clustering is used; t3 is the WebLogic communication protocol Port Number port number on which the WebLogic Server is listening this is usually 7001 unless you are running multiple servers; the port number is listed in the weblogic.properties file Configuring PATROL for BEA WebLogic 3-9

98 Table 3-3 Register WebLogic Server Manager Dialog Box Fields (for WebLogic Server version 5.1) Field Name Administrator Username Description WebLogic system ID, this may or may not also be an operating system account Note: the account under which the PATROL agent runs must have the following permissions: read for the WebLogic home directory and all subdirectories read-execute for the Java home and all subdirectories Administrator Password enter the password for the user ID entered in the preceding field Where to Go from Here Before using the product, take a few minutes to verify that it is correctly configured and that key parts of your WebLogic environment are being discovered and monitored correctly. See Verifying and Troubleshooting WebLogic Server Configuration on page If you want to use any of the performance monitoring features, you must enable advanced monitoring. See Enabling Instrumentation and Profiling Features. If your environment includes a server running WebLogic Server version 5.1, then you must also configure the EJB deployment. See Setting EJB Deployment for WebLogic 5.1 on page Enabling Instrumentation and Profiling Features PATROL for BEA WebLogic version provides extensive and flexible features to monitor all aspects of a WebLogic environment at a very detailed level. Many users will not need to monitor such granular data, and to optimize performance, most of these features are turned off by default PATROL for BEA WebLogic User Guide

99 This section explains how to enable and disable advanced monitoring features. Note The J2EE instrumentation and profiling features are available only on servers on which a PATROL Agent is running (servers identified with the LOCAL_MANAGED icon). Decide What to Enable: Added Value by Feature A basic configuration of PATROL for BEA WebLogic monitors most critical components of a WebLogic environment and will be appropriate for most production environments. Enabling additional features provides more detailed information and enables additional application classes. The following table shows which parameters are enabled at each level (this information is also available in a more expanded form in Appendix B); this can help you decide if you need to turn on advanced monitoring options for your WebLogic environment. Tip Most production environments will not want instrumentation, profiling, and method-level data to be ected regularly. BMC Software recommends enabling the advanced instrumentation and profiling features only when you have a need for them and are comfortable with the added resource overhead that they require. Configuring PATROL for BEA WebLogic 3-11

100 If you want... Turn On... And you get... basic parameters instrumented performance data on WebLogic components nothing: use a default, out-of-the-box configuration Enable EJB Method Level, Servlet Method Level, and Database SQL... using the process outlined in To Turn On Instrumentation or JVM Performance Monitoring on page 3-13 CLUSTER: ClusteredServerStatus EJB_HOME: ActivationCount, CacheAccessCount, CacheHitCount, CachedBeansCurrentCount, FreePoolTimeout, FreePoolWaiter, IdleBeans, JMSConnectionAlive, LockEntriesCount, LockManagerAccessCount, LockTimeoutCount, LockWaiterCount, PassivationCount, TransactionCommitRate, TransactionRollbackRate, TransactionTimeoutRate EEC_QUEUE: ExecQThroughput, ExecuteQueueLength, IdleExecThreadCount JCA: ActiveConnectionsCurrentCount, ActiveConnectionsHighCount, AverageActiveUsage, ConnectionIdleProfileCount, ConnectionLeakProfileCount, CreatedConnectionsTotalCount, DestroyedConnectionsTotalCount, FreeConnectionsCurrentCount, FreeConnestionsHighCount, IdleConnectionsTotalCount, LeakedConnectionsTotalCount, MatchedConnectionsTotalCount, RecycledTotalCount, RejectedConnectionsTotalCount JDBC: ActiveConnections, ConnectionDelayTime, ConnectionLeakProfileCount, FailuresToReconnectCount, LeakedConnectionsCount, PoolState, StatementCacheHitCount, StatementCacheMissCount, StatementProfileCount, WaitingForConnections JMSSERVER: (ytescurrentcount, BytesHighCount, BytesPendingCount, BytesReceivedCount, BytesThresholdTime, DestinationsCurrentCount, DestinationsHighCount, DestinationsTotalCount, HealthStatus, MessagesCurrentCount, MessagesHighCount, MessagesPendingC9ount, MessagesReceivedCount, MessagesThresholdTime, SessionPoolsCurrentCount, SessionPoolsHighCount, SessionPoolsTotalCount LOCAL_MANAGED: ConnectionState, ForeignFragmentsDropped, FragmentsReceived, FragmentsSent, FreeHeap, HealthStatus, HeapUsed, MulticastMsgLost, NumOpenConnections, NumOpenSockets, ResentRequests LOG: LogDiskFreeSpace, LogEvent, LogIncreaseRate MANAGED: ConnectionState, ForeignFragmentsDropped, FragmentsReceived, FragmentsSent, FreeHeap, HealthStatus, HeapUsed, MulticastMsgLost, NumOpenConnections, NumOpenSockets, ResentRequests OS: ActiveProcesses, NumActiveJVMProcesses, NumHighCpuJVMProcesses, ServerJVMsCpuUtil, ServerJVMsMemUsage, _ProcColl PROBE: AvgConnTime, AvgPingTime SERVER: AttrDiscovery, CheckNotification, ConnectionStatus, FreeHeap, HealthStatus, HeapUsed, LogDiscovery, MainDiscovery, NumOpenConnections, NumOpenSockets, PatrolCollectorStatus, ServletDiscovery SERVLET: ExecutionTimeAverage, ExecutionTimeHigh, ExecutionTimeLow, ExecutionTimeTotal, InvocationCount SETUP: _monitorregisteredserver WEBAPP: OpenSessionsCount, OpenSessionsHighCount, TotalOpenSessions everything you get at the basic level, plus... DBURL: AvgResponseTime, HighestInvocationCount, LongestSQLAvgRespTime, LongestSQLTotalRespTime, TotalInvocationCount, TotalResponseTime EJB_HOME: AvgResponseTime, InvocationCount, InvocationRate, LongestEJBAvgRespTime, LongestEJBTotalRespTime, MostInvocationEJB, TotalResponseTime EJB_METHOD: AvgResponseTime, InvocationCount, InvocationRate, TotalResponseTime LOCAL_MANAGED: _EJBRespColl, _SQLRespColl, _WebAppRespColl SERVER: _EJBRespColl, _SQLRespColl, _WebAppRespColl SERVLET_METHOD: AvgResponseTime, InvocationCount, InvocationRate, TotalResponseTime SQL: AvgResponseTime, InvocationCount, InvocationRate, TotalResponseTime, _SQLResponseCollector WEBAPP: AvgResponseTime, InvocationCount, InvocationRate, LongestServletAvgRespTime, LongestServletTotalRespTime, MostInvocationServlet, TotalResponseTime 3-12 PATROL for BEA WebLogic User Guide

101 If you want... Turn On... And you get... JVM performance profiling Java method-level profiling Enable JVM Performance Data Collecting Including... using the process outlined in To Turn On Instrumentation or JVM Performance Monitoring on page 3-13 Enable Advance Java Class Method Level... using the process outlined in To Enable Method-Level Profiling on page 3-16 everything you get at the basic level, plus... JVMPROFILER: AvgGCTime, CPUUSage, GCCount, GCTime, MemoryUsage, ThreadHighestCPUTime, TotalHeapSize, TotalThreadCPU, UsedHeapByAllThreads, VMemoryUsage LOCAL_MANAGED: _JVMProfColl SERVER: _JVMProfColl everything you get at the basic level, plus... PROF_METHOD: AvgCPUTime, CPUTime, ExecutionTime LOCAL_MANAGED: _MethodProfColl SERVER: _MethodProfColl To Turn On Instrumentation or JVM Performance Monitoring Note Once setup, instrumentation and profiling options are permanently saved in your agent configuration. If you later want to completely turn off advanced monitoring, you will need to remove it from the configuration, see To Remove Instrumentation or JVM Performance Monitoring From Your Setup on page Step 1 From the KM Commands on the local managed server instance icon, choose Advance Monitoring => Configure. The Configure Advance Monitoring dialog box is displayed. Step 2 Click the types of components for which you want to ect advanced monitoring (instrumented performance) data. Configuring PATROL for BEA WebLogic 3-13

102 Enabling each type turns on additional ector parameters and creates additional application classes in your PATROL console. These ectors require additional memory and CPU resources and may cause noticeable performance decreases on less robust agent hosts. Table 3-4 Options for Configuring Advanced Monitoring Option Enable EJB Method Level... Description select this option to turn on method level performance data ection for EJBs and servlets, and for database SQL performance this option enables the following application classes: BEAWLS_EJB_METHOD, BEAWLS_SERVLET_METHOD, BEAWLS_SQL, BEAWLS_DBURL Enable JVM Performance... select this option to turn on Java Virtual Machine (JVM) performance data ection this option enables the application class BEAWLS_JVMPROFILE Perform Debug for this Advance Monitoring Feature Remove this Advance Monitoring Feature select this option to ect detailed run-time information about the advanced monitoring ectors; the information can be used to troubleshoot some types of problems; this option should be used only under the direction of BMC Software support personnel select this option to remove instrumentation and profiling (see To Remove Instrumentation or JVM Performance Monitoring From Your Setup on page 3-15) Step 3 Step 4 Step 5 Click OK. A dialog box will inform you of potential performance impacts of turning on advanced monitoring features and will tell you to restart the server. Click OK. Reboot the server. Right-click the server instance icon and select Admin => Boot Server from the KM Commands menu. (You can also restart the server using a script file.) 3-14 PATROL for BEA WebLogic User Guide

103 To Disable Either Instrumentation or JVM Performance Monitoring Step 1 Step 2 Step 3 Step 4 From the KM Commands on the server instance icon, choose Advance Monitoring => Configure. The Configure Advance Monitoring dialog box is displayed. Unselect the type of advanced monitoring that you want turned off. Click OK. Reboot the server. Right-click the server instance icon and select Admin => Boot Server from the KM Commands menu. (You can also restart the server using a script file.) To Remove Instrumentation or JVM Performance Monitoring From Your Setup Step 1 Step 2 Step 3 Step 4 From the KM Commands on the server instance icon, choose Advance Monitoring => Configure. The Configure Advance Monitoring dialog box is displayed. Select the checkbox labeled Remove this Advance Monitoring Feature. Click OK. Reboot the server. Right-click the server instance icon and select Admin => Boot Server from the KM Commands menu. (You can also restart the server using a script file.) Note Removing an advanced monitoring feature deletes certain files on your server that are used only for the profiling and instrumentation features of this product. In some cases, file sharing mechanisms may prevent the files from being deleted. If this happens, you must manually delete the following files. - BMCJ2eeExt.jar and BMCSvrExt.jar under $JAVA_HOME/jre/lib/ext - BMCProfiler.dll (on Windows systems) under $JAVA_HOME/jre/bin - libbmcprofiler.so (on Unix systems) under $JAVA_HOME/jre/bin - libbmcprofiler.sl under $JAVA_HOME/jre/bin Configuring PATROL for BEA WebLogic 3-15

104 To Enable Method-Level Profiling Note The components that monitor Java method-level profiling are resource intensive and intended only for use by application developers. Method-level profiling will perform slowly on host machines with CPUs slower than 1 GHz and with less than 1 GB of memory. These features are not recommended for regular use in production environments. Method level data ection can be dynamically enabled if the JVM Performance Monitoring is turned on. It does not require a reboot of the system, WebLogic, nor PATROL, and once enabled, it runs until you disable it (see To Disable Method-Level Profiling on page 3-17). Step 1 From the KM Commands on the server instance icon, choose Advance Monitoring => Configure Method Profiling. The Configure Method Level Profiling dialog box is displayed. this box must be checked to enable method level profiling Step 2 Step 3 Step 4 Select the checkbox next to Enable Advance Java Class Method level CPU Utilization Data Collection. If the box is not selected, method-level profiling will not be turned on. Type the name of the Java class that you want to monitor. Select Add PATROL for BEA WebLogic User Guide

105 Step 5 Step 6 Click OK. Select Exit from the list of actions, then click OK to close the dialog. To Disable Method-Level Profiling» Follow the steps in To Enable Method-Level Profiling (above), but in Step 2, unselect the check box for Enable Advance Java Class Method level CPU Utilization Data Collection. To Stop Monitoring Classes Step 1 From the KM Commands on the server instance icon, choose Advance Monitoring => Configure Method Profiling. The Configure Method Level Profiling dialog box is displayed. Step 2 Step 3 Step 4 Step 5 From the list of monitored classes, select the class for which you want monitoring disabled. Click on an unhighlighted class name to select it. Select Delete from the list of actions. Click OK. Select Exit from the list of actions, then click OK to close the dialog. Setting EJB Deployment for WebLogic 5.1 To permanently deploy the PATROL EJB ector, you must add a statement to the BEA WebLogic Server 5.1 weblogic.properties file. Note Deploying the PATROL_EJB ector needs to be done only if you are monitoring and managing version 5.1 of BEA WebLogic Server. This process does not apply to versions 6.x through 8.1. Configuring PATROL for BEA WebLogic 3-17

106 To Permanently Deploy the PATROL EJB Collector 1. Open your weblogic.properties file in a text editor. 2. Verify that the following line is not commented out. If the line begins with a # character, delete it: weblogic.httpd.register.classes=weblogic.servlet.classpathservlet 3. Find your EJB deployment statement by searching for the text weblogic.ejb.deploy=. 4. Add patrol_home/beawlkm/java_ector/v51/ejb_bmc_wl.jar to the EJB deployment statement, where patrol_home is the full path indicated by your PATROL_HOME environment variable. 5. Restart WebLogic Server. Where to Go from Here Before using the product, take a few minutes to verify that it is correctly configured and that key parts of your WebLogic environment are being discovered and monitored correctly. See Verifying and Troubleshooting WebLogic Server Configuration on page Verifying and Troubleshooting WebLogic Server Configuration After you have registered a BEA WebLogic Server, verify that your instances are discovered and that the BEAWLS_SERVER icon appears in the PATROL Console PATROL for BEA WebLogic User Guide

107 1. From the PatrolMainMap, open the computer window and verify that the PATROL for WebLogic icon is present, as shown in Figure 3-1. This icon is a container that represents your entire BEA WebLogic environment. If you are monitoring an environment that includes servers running WebLogic Server version 5.1 and servers running 6.0 or later, then you will see two WebLogic icons at this level. The icon labeled BEAWLS_SERVER_V51 represents servers running WebLogic Server version 5.1 while the icon labeled BEAWLS_SERVER represents servers running version 6.0, 6.1, 7.0, or 8.1. Figure 3-1 WebLogic Server Icon in PATROL Console PATROL for WebLogic icon Note If the PATROL for WebLogic icon does not appear within two or three minutes, open the PATROL system output window and read the status messages. Look for messages that might indicate a specific problem, such as an incorrect port number, permission access problems on required files or directories, or user authentication failure. Correct any setup problems as described in Configuring the KM on page 3-3. Configuring PATROL for BEA WebLogic 3-19

108 2. Double-click the BEAWLS_SERVER icon to see which servers are being monitored. There will be as many 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. 3. Double-click a server instance icon. You should see several icons in the PATROL window, depending on which WebLogic features you have set up and running. Figure 3-2 shows a PATROL Console monitoring a server running WebLogic Server version PATROL for BEA WebLogic User Guide

109 Figure 3-2 Example Monitored WebLogic 7.0 Server Note It may take several minutes for a server to be fully monitored because some application classes are discovered on different schedules. PATROL for BEA WebLogic discovers environment configuration information in four stages: 1. MainDiscovery discovers and creates instances for all components monitored in the registered WebLogic Server or domain; this includes CLUSTER, SERVER, EEC_QUEUE, EJB, WEBAPP, JDBC, JMSSERVER, JCA, and JOLT. The process runs every 60 seconds (depending on the schedule). Configuring PATROL for BEA WebLogic 3-21

110 MainDiscovery runs when you first configure the product, but it does not run on a regular schedule because configuration of servers and components is generally stable. MainDiscovery does, however, run under the following conditions: When a new domain is initially setup. When a server s status changes (such as from admin to managed server). When the PATROL Agent restarts. When PATROL s Java Collector for WebLogic restarts. When you run the KM menu command Force Objects Discovery from the BEAWLS_SERVER application class. 2. Attribute Discovery retrieves configuration and runtime information for all components discovered by Main Discovery. It runs every 10 minutes by default. 3. Servlet Discovery finds information about the monitored servlets of specified web applications). It runs every 10 minutes by default. 4. Log Discovery retrieves information for the four WebLogic Server default log files. It runs every 10 minutes by default. If application class icons do not appear in the console window within 10 minutes, check the following: WebLogic configuration: icons for monitoring some WebLogic components will not appear if there is nothing for the KM to monitor. Check your WebLogic configuration to verify that the component being monitored by a missing application class is actually enabled. Advanced monitoring: icons for many of the application classes that monitor and instrument performance will not appear unless Advance Monitoring is specifically enabled. These icons include EJB_METHOD, SERVLET_METHOD, SQL, JVMPROFILE, PROF_CLASS, and PROF_METHOD. See Enabling Instrumentation and Profiling Features on page PATROL for BEA WebLogic User Guide

111 Product configuration: icons may not appear if the KM configuration information was incorrect (for example, if an incorrect Java path was specified). The BEAWLS_OS icon will not appear if the required operating system.kml files were not loaded. See Configuring the KM on page 3-3. Where to Go from Here After verifying that PATROL has discovered your server and has instantiated application instances, see Chapter 4, Managing the BEA WebLogic Environment, to begin configuring and using the product monitoring features. Configuring PATROL for BEA WebLogic 3-23

112 3-24 PATROL for BEA WebLogic User Guide

113 4 Managing the BEA WebLogic Environment 4 This chapter explains how to effectively manage a BEA WebLogic environment using the PATROL for BEA WebLogic product. The following topics are discussed: Monitoring a WebLogic Environment Working with Parameters Top Parameters for BEA WebLogic Working with Events Estimating Response Times Test File Transfer Rate Test Web Page Response Administering Probe Generating Reports Generating a Report Managing the BEA WebLogic Environment 4-1

114 Monitoring a WebLogic Environment PATROL for BEA WebLogic relies on features of the PATROL Console for much of its ability to help you improve the reliability and performance of your WebLogic environment. Every user of PATROL for BEA WebLogic should understand how basic Console features and commands work together. This chapter explains how to exploit some key PATROL features to effectively use PATROL for BEA WebLogic. If any step seems too advanced, see the online Help for your Console by clicking Help. The Console Help and the PATROL Event Manager Help explain basic concepts. Working with Parameters When you first install PATROL for BEA WebLogic, take some time to open windows and double-click application class icons to see parameters. The parameters contain the actual data about your system s performance and configuration. Top Parameters for BEA WebLogic While all of the parameters in the product will probably be important to some users at some times, only a small number are of critical importance to almost every environment. These parameters are the top parameters to monitor in order to assure the availability of your WebLogic environment. BMC Software sets alarms on many of them by default. You may also wish to monitor them through the Event Manager and set notifications or recovery actions on some. PatrolCollectorStatus (SERVER, page B-19): If PatrolCollectorStatus goes into alarm, PATROL is not receiving updated data and your monitoring is offline. This and ConnectionStatus are the two most critical parameters to assure availability of your WebLogic environment. 4-2 PATROL for BEA WebLogic User Guide

115 ConnectionStatus (LOCAL_MANAGED, page B-14; MANAGED, page B-16; SERVER, page B-18): Indicates that the PATROL ector cannot communicate with the server. You may need to restart the WebLogic server. ClusteredServerStatus (CLUSTER, page B-4): Indicates whether a clustered server is up or down. HealthStatus (JMSSERVER, page B-12; LOCAL_MANAGED, page B-14; MANAGED, page B-16; SERVER, page B-18): There are four of these parameters for different types of servers. Each indicates an assessment of the health of the server. These parameters are shown only for BEA WebLogic Server 7.0 and 8.1. TransactionTimeoutRate (EJB_HOME, page B-7): Set alarm values to flag abnormally high numbers of timeouts, which may indicate a problem with your EJB pool or may indicate another problem that is preventing EJBs from completing fast enough to free up connections. ExecuteQueueLength (EEC_QUEUE, page B-8): Set alarm values to flag abnormally long queues. PoolState (JDBC, page B-10): Indicates whether pool is available, or has been shutdown or suspended. Working with Events Some features in PATROL for BEA WebLogic (such as log file sniffing and JM MBean monitoring) are intended to be used in conjunction with PATROL events. This section provides a brief look at how events can be managed using the PATROL Event Manager. See the PATROL Event Manager Help in your PATROL Console for more information. Managing the BEA WebLogic Environment 4-3

116 Managing Events Using PATROL Event Manager Summary: Use the PATROL Event Manager to monitor WebLogic events, including those generated by defined JM conditions. The PATROL Event Manager (PEM) is a powerful feature of every PATROL Console. Using the Event Manager, you can view and manage various types of events everything from disk failures to stopped critical processes. You can define the behavior of events for your system, establishing recovery actions, or you can use diary features to log events. To Monitor Events with the PATROL Event Manager Help provides more details about PEM Step 1 Choose Event Manager from the Tools menu of your PATROL Console. The PATROL Event Manager window appears. 4-4 PATROL for BEA WebLogic User Guide

117 Step 2 Right-click an event to see details. You can use the Diary features to track operator comments about any event type, and you can add your own local events and expert advice. More information about these topics and other features of the PATROL Event Manager is available within the online help. Step 3 Click OK to close the window. Managing the BEA WebLogic Environment 4-5

118 Estimating Response Times PATROL for BEA WebLogic contains a Probe feature to estimate server response times. Two timing metrics are provided: response times for serving local or remote web pages in response to iterative requests, or timing data on ping operations with s user-specified packet size. A Probe administration feature lets you manage timing information using annotated data points or PATROL event generation on the AvgPingTime or AvgConnTime parameters. Commands are provided to report timing information in the task window. The Probe is available under the administration server icon. The Probe provides timing data at a macro level. Precise timing data can be generated and monitored for most components of J2EE web applications running in the WebLogic environment. You can use this data to find slow-performing web applications, EJBs, servlets, and SQL statements, and in many cases, isolate and instrument the performance down to the method level. See Instrumenting and Profiling J2EE Components on page 9-1. This section describes how to use the Probe feature. 4-6 PATROL for BEA WebLogic User Guide

119 Test File Transfer Rate Summary: Perform these steps to time data transfer rates from a WebLogic Server. This performs a ping operation, sending a packet of data of a size that you specify, and returning the number of milliseconds elapsed between the time of the request and the time of the response. If the connection fails, the system output window will show a series of messages that may help you isolate the cause. To time transfer rates: Step 1 Step 2 Step 3 Step 4 Right-click the BEAWLS_PROBE application icon. From the KM commands menu, choose Ping Server. Specify the file size that you want tested. Click OK. Managing the BEA WebLogic Environment 4-7

120 Test Web Page Response Summary: Perform these steps to send web page requests to a remote or local web server and produce timing information on the number of milliseconds needed to receive a response. You can set a number of iterations to send multiple requests, which can provide a range of response times. To test response times: Step 1 Step 2 Step 3 Step 4 Step 5 Right-click the BEAWLS_PROBE application icon. From the KM commands menu, choose Test Web Page Response. Specify the address (URL) of the web page you want timed. Use the slide bar to set the number of consecutive requests you want sent. Click OK. 4-8 PATROL for BEA WebLogic User Guide

121 Administering Probe Summary: Perform these steps to turn on or off annotations for Probe parameters and to turn on or off event generation for Probe timing data. Annotations apply to the AvgPingTime and AvgConnTime parameters and include information about the time each data point was ected and the value of the timing data parameter. Event generation sends timing information to the PATROL Event Manager (PEM) when the parameter status is in WARNING or ALARM. Use PEM to manage event data. To use the Probe Administration dialog box: Step 1 Step 2 Right-click the BEAWLS_PROBE application icon. From the KM commands menu, choose Administration. The Probe Administration dialog box is displayed. select this box to generate events when AvgPingTime is in WARNING or ALARM select this box to generate events when AvgConnTime is in WARNING or ALARM Step 3 Step 4 Click checkboxes to turn individual features on or off. A check indicates that the feature is turned on. Additional information about each of the features is provided in Table 4-1. Click OK. Managing the BEA WebLogic Environment 4-9

122 Table 4-1 Probe Administration dialog box fields Field Name Annotation for Ping Time Data Annotation for Connection Time Data Event Trigger for Ping Status Event Trigger for Connection Status Action check this box to produce annotated data points for the AvgPingTime parameter; annotations will include timestamps for each ection cycle and the time (in milliseconds) needed to complete a ping operation check this box to produce annotated data points for the AvgConnTime parameter; annotations include timestamps for each ection cycle and the number of milliseconds needed to establish a connection check this box to generate a PATROL event when the parameter status is WARNING or ALARM; event data can be monitored through the PATROL Event Manager (PEM) check this box to generate a PATROL event each time connection data is ected 4-10 PATROL for BEA WebLogic User Guide

123 Generating Reports PATROL for BEA WebLogic provides a number of reporting functions to list various configuration settings and performance metrics. These reports are always displayed in a system output window. See Generating a Report on page 4-13 if you do not know how to use the reporting commands. Table 4-2 lists the basic types of reports you can generate and describes what type of information will be produced by each. If you enable the advanced monitoring instrumentation and profiling features, additional reports on J2EE object performance will be available. These are described in Chapter 9, Instrumenting and Profiling J2EE Components on page 9-1. Table 4-2 Reports in PATROL for BEA WebLogic (Part 1 of 2) Report Name From Instance Icon of Class... Contents Connection Leak JDBC displays connection leak profile, including stack trace at the time the connection was created Execute Threads Report JMS Server Components EEC_QUEUE SERVER provides usage and activity info for all threads in an execution pool; includes current request, last request, number of requests served, current user, and a flag indicating whether the thread is idle. configurable reports on JMS runtime data, such as connection factories, templates, destination keys, file store, JDBC store, or servers JNDI Report SERVER provides directory mapping information for various aspects of the WebLogic system, such as file system, EJB, JDBC, server, RMI, JMS, transaction, and common JTA Information SERVER provides statistics on the Java Transaction subsystem, including total transactions and total rollbacks JTA Transaction SERVER provides transaction information (such as number of transactions committed, rolled back, heuristics) organized by name, resource, or current transactions (in-flight) Managing the BEA WebLogic Environment 4-11

124 Table 4-2 Reports in PATROL for BEA WebLogic (Part 2 of 2) Report Name License Information Managed Server Response Prepared Statement Cache SERVER PROBE JDBC provides information about the product name (database), the IP address of the host that is licensed to run the product (if any), the license expiration date (if any), the number of hosts that can simultaneously run the product, and the license key value provides statistical information about response performance for a managed server displays cache snapshots stored externally for later analysis Realm Information SERVER for each class in the realm, details are provided showing the class names and the permissions granted to groups or ACLs for that realm Report of Registered Instance Security Information Server Configuration Server Connections SETUP SERVER SERVER SERVER generates a report on all registered WebLogic application servers; server instance names are shown along with settings for their WebLogic and Java paths, and other details for each server in the domain, the report shows security information for ACLs, groups, and users reports WebLogic server configuration attributes reports network configuration attributes such as HTTP settings, SSL settings, tuning parameters, and protocol information SQL Roundtrip JDBC displays SQL text, execution time, start and end time, and transaction name WebLogic MBean Information From Instance Icon of Class... SERVER Contents reports WebLogic configuration and runtime MBean information 4-12 PATROL for BEA WebLogic User Guide

125 Generating a Report Summary: Perform these steps to generate any type of report. To generate a report: Step 1 Step 2 Right-click the icon for the instance on which you want a report. (Most reports are available under the SERVER icon.) From the KM Commands menu, choose the command to generate the desired report type. In the SERVER class, all report commands are submenus of Report. For example, if you wanted to run the Execute Threads Report, you would find the EEC_QUEUE icon and then, from the KM Commands menu, choose Execute Threads Report. The report will be displayed in a system task window. reports appear in system task window Where to go from here See the list of reports in Table 4-2 on page 4-11 and generate some reports about your WebLogic environment. Managing the BEA WebLogic Environment 4-13

126 4-14 PATROL for BEA WebLogic User Guide

127 5 Working with Log Files 5 This chapter explains how to effectively manage WebLogic log files using the PATROL for BEA WebLogic product. The following topics are discussed: Understanding Logs Select Log File for Monitoring Configure the Domain Log Configure the Server Log Configure the JDBC Log Configure the HTTP Log Configure the Transaction Log Define Sniff Pattern Stop Monitoring a Log View Log File Watch a Log File View Sniff Patterns Turning Off and Restarting Sniff Patterns Changing the Sniff Type Updating a Log File Location Registering for Log Notification Messages Unregistering for Log Notification Messages Working with Log Files 5-1

128 Understanding Logs All messages generated by component subsystems are written to log files on the local server. The most critical of these are also written to the domain-wide log files on the administration server. Monitoring the domain log file is a good way to develop an overall performance view of your entire WebLogic environment. Rotation Some log files (including domain and server logs) are periodically archived and a new log file initiated for current messages. The process of retiring a log file and re-initiating it is called rotation. Rotation can be done periodically, or whenever the log file reaches a certain size. Use rotation to keep log files from reaching unmanageable sizes. Note File rotation may conflict with sniff patterns. You will usually need to choose one function or the other for a particular log file. Severity All WebLogic messages contain a severity code. You can use these codes when viewing logs or defining sniff patterns to isolate those messages that you want most to see. You can also have these messages trigger events that can be managed through the PATROL Event Manager. There are 7 severity levels, ranging from Informational (normal operational messages), to Emergency (severe system failure). The levels are: Informational Warning Error Notice Critical 5-2 PATROL for BEA WebLogic User Guide

129 Alert Emergency The top two levels (Emergency and Alert) both indicate severe problems from which WebLogic can probably not automatically recover. Messages at these top two levels should always be logged in the domain-wide log and should trigger PATROL events. The default is usually to send everything with a severity of Error or higher to the domain log. Working with Log Files 5-3

130 Select Log File for Monitoring Summary: Perform these steps to define a non-default log file that you want monitored. The four default WebLogic log files are monitored by default in PATROL for BEA WebLogic they do not need to be specifically selected. You can monitor additional logs, such as the WebLogic KM debug log. To select a log file for monitoring: Step 1 Step 2 Right-click the icon of a log file instance (for example, HTTP, DOMAIN, JDBC, or SERVER). From the KM Commands menu, choose Administration => Monitor Another Log. The Monitor Another Log dialog box appears. Step 3 Step 4 Enter the information needed to set up a new log file instance in the Monitor Another LOG dialog box. Table 5-1 provides detailed information about specifying values for these fields. Click OK. 5-4 PATROL for BEA WebLogic User Guide

131 Table 5-1 Monitor Another Log dialog box fields Field Name Log Name Alias Log File with Full Path File Access User Name File Access Password Action unique alias name for the log file; this will be used as the instance name complete directory path and file name of the log you want monitored username of an account with permissions to read the log file password for the account Working with Log Files 5-5

132 Configure the Domain Log Summary: Perform these steps to manage the domain-wide log file. The domain-wide log file includes the most important messages generated by all managed servers in a WebLogic environment. You can use the configuration commands to view current log configuration settings retrieved from the administration server, and you can define new settings. When you configure the domain log, you can set how often new log files are initiated and you can define which message severity levels to log. To configure the domain log: Step 1 Step 2 Right-click the administration server instance icon. From the KM Commands menu, choose LOG Configuration => Domain Log. The Domain Log Setting dialog box appears. 5-6 PATROL for BEA WebLogic User Guide

133 Step 3 Step 4 Specify a file name and various rotation parameters for determining how and when new log files are automatically created and old ones retired. Table 5-2 describes the information needed to complete these fields. Click OK. Table 5-2 Domain Log Setting dialog box fields Field Name File Name Rotation Type Rotation Size Threshold Rotation Time Span Limit File Number? Limited File Number Action specify the name of the domain-wide log file specify the method to use in determining when to start a new log file this can be TIME, SIZE, or NONE if the rotation type is SIZE, specify the number of kilobytes a log file must contain before it is rotated out and a new log started if the rotation type is TIME, set the number of hours that each log file should span check this box to limit the number of rotated log files (old files) to retain if the previous box is checked, then specify the maximum number of files to retain; once the maximum number is reached, the oldest file is deleted each time a log file rotation occurs Working with Log Files 5-7

134 Configure the Server Log Summary: Perform these steps to manage the server log file. The server log contains messages generated on a given WebLogic Server instance. You can use the configuration commands to view current log configuration settings retrieved from the administration server, and you can define new settings. Note To monitor logs on a managed server when the managed server is running on a different host machine than the administration server, the managed server log files must be on a disk that is accessible to the administrative server (mounted or mapped to the admin server). See Updating a log file location to point to the mapped file path. To configure the server log: Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Right-click the administration server instance icon. From the KM Commands menu, choose LOG Configuration => Server Log. From the list of available servers, select the server whose log you want to configure. Click OK. Specify a file name and various rotation parameters for determining how and when new log files are automatically created and old ones retired. The dialog box fields are the same as those described in Table 5-2, Domain Log Setting dialog box fields, on page 5-7 (with the addition of a checkbox to enable logging to be sent to the Domain Log). Click OK. 5-8 PATROL for BEA WebLogic User Guide

135 Configure the JDBC Log Summary: Perform these steps to manage the JDBC log file. The JDBC log contains messages related to database connections. You can use the configuration commands to view current log configuration settings retrieved from the administration server, and you can define new settings. To configure the JDBC log: Step 1 Step 2 Step 3 Right-click the administration server instance icon. From the KM Commands menu, choose LOG Configuration => JDBC Log. Click a server name from the list of available servers, then click OK. The JDBC Log Setting dialog box is displayed. Step 4 Step 5 Check the box to enable logging and specify a file name in which to save JDBC-related messages (for example, d:\weblogic61\wlserver6.1\config\bookstore\logs\wl-jdbc.log). Click OK. Working with Log Files 5-9

136 Configure the HTTP Log Summary: Perform these steps to manage the HTTP access log file. The HTTP access log records all connections made to a web server. You can use the configuration commands to view current log configuration settings retrieved from the administration server, and you can define new settings. To configure the HTTP log: Step 1 Step 2 Step 3 Right-click the administration server instance icon. From the KM Commands menu, choose LOG Configuration => HTTP Log. Click a server name from the list of available servers, then click OK. The HTTP Log Setting dialog box is displayed PATROL for BEA WebLogic User Guide

137 Step 4 Step 5 Check the box to enable logging and specify a file name in which to save HTTP-related messages. Specify rotation attributes to define how often new log files are initiated. (Fields are defined in Table 5-3.) Click OK. Table 5-3 HTTP Log Settings dialog box fields Field Name Enable HTTP Logging? Format File Name Rotation Type Log Buffer Size (Kbytes) Max Log File Size (Kbytes) Rotation Start Time Rotation Time Period (minutes) Log File Flush Interval (seconds) Action check this box to save HTTP access messages to a log file select the message format from the pull-down list options are common or extended specify the name of the HTTP access log file for example,./config/mydomainname/logs/access.log specify the method to use in determining when to start a new log file this can be DATE or SIZE specify the maximum size of the log file buffer the default value is 8 KB specify the maximum file size for the log file specify when to start rotating the HTTP access log file the format follows java.text.simpledateformat, MM-dd-yyyy-k:mm:ss For example: :30:00 Note: If not set, the next rotation is the next log period. specify the number of minutes between log rotations (the default is so large as to effectively block rotation) specify how often the log file should be flushed Working with Log Files 5-11

138 Configure the Transaction Log Summary: Perform these steps to set the transaction log file directory. You can use the configuration commands to view current log configuration settings retrieved from the administration server, and you can define new settings. To configure the transaction log: Step 1 Right-click the administration server instance icon. Step 2 From the KM Commands menu, choose LOG Configuration => Transaction Log. Step 3 Click a server name from the list of available servers, then click OK. The Transaction Log Setting dialog box is displayed. Step 4 Step 5 Specify a prefix for the log file (a directory path in which to save files, or a directory path and root name). The default is./ (save in current directory). Click OK PATROL for BEA WebLogic User Guide

139 Define Sniff Pattern Summary: Perform these steps to define new sniff patterns and their associated properties. You can also change existing sniff patterns, or delete a sniff pattern. The sniff pattern is a string that is used as a pattern-matching template when working with log files. When the text string defined in the sniff pattern occurs in a log error message, the KM generates an event in the event log and creates annotations, if configured to do so. To define or update a sniff pattern: Step 1 Step 2 Step 3 Step 4 Right-click the instance icon of the log file you want to view. From the KM Commands menu, choose Log Sniffing => Edit Sniff Pattern. In the Log Sniff Setup dialog box, click Add if you want to define a new sniff pattern.click Edit if you want to change a previously defined sniff pattern. Click Take Action. Either the Add New Log Sniff Pattern or the Update Log Sniff Pattern dialog box will display (both are functionally identical). by triggering events, you can manage WebLogic events using the PATROL Event Manager text string to be matched (regular expression syntax) Working with Log Files 5-13

140 Step 5 Step 6 Step 7 In the Add New Log Sniff Pattern dialog box (or Update Selected Log Sniff Pattern dialog box), specify the text or regular expression that you want matched. Field definitions are in Table 5-4. Specify the event type, event trigger, annotation, and event class information. Click OK. Table 5-4 Add New Sniff Pattern dialog box fields Field Name Sniff Pattern Event Type PATROL Event Trigger Annotate Information PATROL Event Class Action text string that you want matched; this can be any text string or regular expression pull-down list of PATROL event types: ERROR, INFORMATION, or WARNING if checked, events are logged in the PATROL event log and can be monitored through the PATROL Event Manager if checked, annotated data points will be generated on parameter s class used to identify error type when working with PATROL events; you can define your own event class or use defaults of ERROR_PATTERN, WARNING_PATTERN, and INFORMATION_PATTERN. An administrator can use a PATROL Developer Console to create customized event classes so that recovery actions can be properly associated to certain string patterns. To delete a sniff pattern: Step 1 Step 2 Step 3 Step 4 Step 5 Right-click the instance icon of the log file you want to view. From the KM Commands menu, choose Log Sniffing => Edit Sniff Pattern. In the Log Sniff Setup dialog box, click Delete, then click Take Action. Click the sniff pattern you want deleted from the list of defined patterns. Click OK PATROL for BEA WebLogic User Guide

141 Working with Log Files 5-15

142 Stop Monitoring a Log Summary: Perform these steps to stop monitoring a log file. To stop monitoring a log file: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file you no longer want to monitor. From the KM Commands menu, choose Administration => Stop Monitoring. If you want to monitor the log file again, you will need to select it for monitoring. See Select Log File for Monitoring on page PATROL for BEA WebLogic User Guide

143 View Log File Summary: Perform these steps to view the contents of a log file. You can view either only the currently active log file, or the entire log file. The entire log file includes all rotated (archived) files. To view only the currently active log file: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file you want to view. From the KM Commands menu, choose View => View Current Log File. If you are viewing a JDBC or HTTP log, the Search Pattern dialog will allow you to specify a text string to be matched. If you are viewing a DOMAIN or SERVER logs, the Message Filter dialog will allow you to specify a wide range of criteria including subsystem components, severity level, date, server and host names, user IDs, and message IDs. Message Filter dialog for DOMAIN or SERVER Working with Log Files 5-17

144 Step 4 Step 5 Specify which types of messages you want displayed. Click OK. To view the entire log file (including rotated files): Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file you want to view. From the KM Commands menu, choose View => View Entire Log File. The Message Filter Dialog is displayed. Step 4 Step 5 Specify which types of messages you want displayed. Click OK. Messages from the log are displayed in groups of 500. After each 500 messages are displayed, a confirmation box asks you if you want to continue displaying messages. Click Yes to display more messages or No to stop viewing log messages PATROL for BEA WebLogic User Guide

145 Watch a Log File Summary: Perform these steps to watch a log file as messages are written to it. When you begin watching a file, the last 10 lines of the log are displayed to an output window. As new messages are spooled to the end of the log file as errors occur, they are simultaneously displayed in the output window. To watch a log file: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file you want to watch. From the KM Commands menu, choose View => Watch Log File. Working with Log Files 5-19

146 View Sniff Patterns Summary: Perform these steps to see information about the pattern matching strings that are currently being applied to the log file. Listed information includes the name of the log file, whether it is being actively monitored, the string pattern being matched, the event category and class, and whether annotation of data points is currently turned on. To view registered sniff patterns: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file for which you want to see sniff pattern information. From the KM Commands menu, choose Log Sniffing => View Registered Patterns. Information about current patterns is displayed in a system output window PATROL for BEA WebLogic User Guide

147 Turning Off and Restarting Sniff Patterns Summary: Perform these steps to stop applying pattern matching strings to log file entries. You can later resume monitoring a log using the sniff pattern. To turn off sniff pattern matching: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file for which you want to turn off sniff patterns. From the KM Commands menu, choose Log Sniffing => Stop Pattern Sniffing. To resume previously turned-off sniff pattern matching: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file for which you want to see sniff pattern information. From the KM Commands menu, choose Log Sniffing => Restart Pattern Sniffing. Working with Log Files 5-21

148 Changing the Sniff Type Summary: Perform these steps to change the way in which log file sniff patterns are applied. You can choose to match sniff patterns with log file messages on either a periodic or on a real-time basis. By default, log files are monitored periodically, which means they are applied when the LogEvent parameter ects data. Real-time monitoring continuously matches patterns but leaves the file open, which may conflict with other processes. To change the sniff type: Step 1 Step 2 Step 3 Double-click the BEAWLS_LOG icon to display the individual log file instances. Right-click the instance icon of the log file for which you want to change the sniff type. From the KM Commands menu, choose Edit Sniffing Pattern => Setup Sniffing Type. The Sniffing Type Setup dialog box is displayed. Step 4 Step 5 Choose either Periodic or Real Time sniffing. Specify periodic if log file rotation is turned on. Click OK PATROL for BEA WebLogic User Guide

149 Updating a Log File Location Summary: Perform these steps to change the PATROL log file monitoring instance when a log file location changes from that of the server. To update location information: Step 1 Step 2 Step 3 Step 4 Right-click the instance icon of the log file you want to update. From the KM Commands menu, choose Administration => Update Log File Location. Change the directory path or file name to reflect the new path. Click OK. Working with Log Files 5-23

150 Registering for Log Notification Messages Summary: Perform these steps to get notifications whenever error messages of type Emergency, Critical, or Alert are written to the WebLogic server log file. To subscribe to log file notification: Step 1 Right-click the administration server instance icon. Step 2 From the KM Commands menu, choose LOG Notification => Register. The Register Log Notification dialog box is displayed. Step 3 Step 4 Step 5 Select a notification method. You can be notified via messages, via alerts sent to the PATROL Event Manager, or both. Specify an outgoing mail server and the address to which you want alerts sent. Click OK PATROL for BEA WebLogic User Guide

151 Unregistering for Log Notification Messages Summary: Perform these steps to stop notifications from being sent when error messages of a certain type are written to the log file. To unsubscribe to log file notification: Step 1 Right-click the administration server instance icon. Step 2 From the KM Commands menu, choose LOG Notification => Unregister. A confirmation dialog box is displayed. Step 3 Click Yes. Working with Log Files 5-25

152 5-26 PATROL for BEA WebLogic User Guide

153 6 Managing Servers 6 This chapter explains how to manage the servers on which you run BEA WebLogic, including administrative, managed, and local managed servers. The following topics are discussed: Managing WebLogic Servers Boot WebLogic Server Shut Down WebLogic Server Lock or Unlock Server Perform Java Garbage Collection Tuning a Server Configuration Managing Servers 6-1

154 Managing WebLogic Servers PATROL for BEA WebLogic provides the ability to run common administration commands on any server in your WebLogic environment from within your monitoring console. These commands include: Shutting down and restarting WebLogic servers (either administration or managed servers). Locking and unlocking servers. Performing Java garbage ection. Tuning server configurations (such as tunneling and process attributes). 6-2 PATROL for BEA WebLogic User Guide

155 Boot WebLogic Server Summary: Perform these steps to shut down and then restart a WebLogic Server. Reboot commands are available for both administration and managed servers. If an administration server goes down while managed servers are running, you do not need to restart the managed servers in order to recover management of the domain. If you restart the administration server with the discover attribute turned on, the administration server can discover managed servers and recover management. (See the WebLogic Server Administration document, available from BEA.) Discovery is turned on by the following setting in the startup script: -Dweblogic.management.discover=true To boot WebLogic Server: Step 1 Step 2 Right-click the instance icon of the server you want to re-boot. From the KM Commands menu, choose Admin => Boot Server. The Boot Server dialog box is displayed. Step 3 Specify the boot command to be run. If you are booting a Unix server, this is the full path to a pre-written script that can start the server. The server should be booted in a non-interactive mode (the password should be read from password.ini or boot.properties, not from the command line). Managing Servers 6-3

156 Step 4 Click OK. 6-4 PATROL for BEA WebLogic User Guide

157 Shut Down WebLogic Server Summary: Perform these steps to completely shut down (turn off) a WebLogic Server. If you change your mind about shutting down a server during the grace period, you can cancel the shutdown operation. To shut down the server: Step 1 Step 2 Right-click the instance icon of the administration or managed server that you want to shut down. From the KM Commands menu, choose Admin => Shutdown Server. The Shut Down Server dialog box is displayed. Step 3 Step 4 Step 5 Slide the grace period selector to set the number of seconds to wait before shutting down. Type a message that will be sent to active users. Click OK. To cancel the shutdown operation: Step 1 Step 2 Right-click the instance icon of the administration or managed server on which you previously issued a shutdown command. From the KM Commands menu, choose Admin => Cancel Shutdown. Managing Servers 6-5

158 Lock or Unlock Server Summary: Perform these steps to lock or unlock a WebLogic Server. This can be done on either an administration or a managed server. When a server is locked, no user other than an administrator can log in until the server is unlocked. To lock a WebLogic Server: Step 1 Step 2 Right-click the instance icon of the server you want to lock. From the KM Commands menu, choose Admin => Lock Server. The Lock Server dialog box is displayed. Step 3 Step 4 Enter a message to be displayed to any user who tries to log in during the lock period. Click OK. To unlock a WebLogic Server: Step 1 Step 2 Step 3 Right-click the instance icon of the server you want to lock. From the KM Commands menu, choose Admin => Lock Server. Click OK. 6-6 PATROL for BEA WebLogic User Guide

159 Perform Java Garbage Collection Summary: Perform these steps to instruct the Java Virtual Machine (JVM) to begin garbage ection. Garbage ection can be done on either an administration or a managed server. JVM garbage ection reclaims memory by discarding unused objects. To begin garbage ection: Step 1 Step 2 Right-click the instance icon of the server on which you want to ect garbage. From the KM Commands menu, choose Admin => Garbage Collection. Managing Servers 6-7

160 Tuning a Server Configuration Summary: Perform these steps to tune server configuration attributes. Tuning can be done on either an administration, managed, or local managed server. The configuration attributes control how a server manages its connections and process threads. To tune server configuration: Step 1 Step 2 Right-click the instance icon of the managed server or administration server that you want to tune. From the KM Commands menu, choose Admin => Server Configuration Tuning. The Server Tuning dialog box is displayed. Information about these configuration parameters is provided in Table PATROL for BEA WebLogic User Guide

161 Table 6-1 Server Tuning dialog box fields Field Name Tunneling Enabled Action check this box to enable tunneling tunneling is a method of establishing a state-based connection via the HTTP protocol; it is often used to create a stateful HTTP connection through a firewall; tunneling decreases your WebLogic performance use it only when necessary; a better option is to use the t3 protocol on port 80 (if your firewall is able to pass IP packets through port 80) Tunneling Client Ping Seconds Tunneling Client Timeout Seconds enter the number of seconds between pings when a tunnel connection is created, the server periodically checks the state (up or down) of the remote client; 45 seconds is the optimum default value for the ping interval; the valid range is 20 to 900 seconds enter the number of seconds that must elapse from the last response from a client before a connection is considered dead if a client does not respond to a request or ping within the timeout period, WebLogic Server closes the HTTP tunnel connection; 40 seconds is the optimum default value; the valid range is 10 to 900 seconds Login Timout (ms) enter the number of seconds in which a login must complete from the time it is initiated if a correct username/password combination is not entered and the login process completed within this time, the login process will be terminated Thread Pool Socket Readers (percent) enter the percentage of execute threads that can be used as socket readers the default value is 33; the allowable range is 1 to 99 Step 3 Step 4 Adjust the tunneling, timeout, and thread attributes as needed. Click OK. Managing Servers 6-9

162 6-10 PATROL for BEA WebLogic User Guide

163 7 Managing WebLogic Components and Services 7 This chapter explains how to effectively manage the component pieces of a WebLogic environment. Reports are available on some of these components. See Generating Reports on page The following topics are discussed: Configuring WebLogic Components Configuring the JTA Configuring the JDBC Configuring the JMS Managing JDBC Pools Creating a JDBC Pool Removing a JDBC Pool Administering JDBC Pools Enabling or Disabling JDBC Profiling Generating JDBC Profiling Reports Managing WebLogic Components and Services 7-1

164 Configuring WebLogic Components PATROL for BEA WebLogic contains several commands run from the Administrative server instance icon (the BEAWLS_SERVER application class) that are used to configure and manage key components of the WebLogic system. These commands include: Configuring the Java Transaction API (JTA) to set timeout and threshold limits. Configuring the Java Database Connection (JDBC) pool to set initial and maximum numbers of connections, and to set a login delay to avoid potential logjams in the connection creation process. Configuring the Java Message Service (JMS) to set quotas and thresholds. 7-2 PATROL for BEA WebLogic User Guide

165 Configuring the JTA Summary: Perform these steps to configure the Java Transaction API (JTA), setting time limits for transactions to complete and commit. To configure the JTA: Step 1 Step 2 Right-click the instance icon of the administrative server. Choose Admin => JTA Configuration. The JTA Configuration dialog box is displayed. Step 3 Step 4 Specify threshold values to set limits on how quickly a transaction must complete. Table 7-1 describes the fields in the JTA Configuration dialog box. Click OK. Managing WebLogic Components and Services 7-3

166 Table 7-1 JTA Configuration dialog box fields Field Name Timeout Seconds Abandon Timeout Seconds Before Completion Iteration Limit Max Transactions Max Unique Name Statistics Forgot Heuristics Action specify the maximum number of seconds that a transaction will be allowed to run before it is rolled back specify the maximum number of seconds in which a transaction must be committed before it is abandoned and rolled back specify the maximum number of iterations (callbacks) that a transaction can perform before being rolled back set the maximum number of transactions that can be simultaneously in progress set the maximum number of unique transaction names for which statistics will be maintained set the flag indicating whether the transaction manager should discard heuristically determined transaction data; set the flag to true to discard the data, or false to retain the data; heuristics are used to define whether and how transactions are completed and committed autonomously by the WebLogic server (for example, if a client-server connection is broken before a transaction can be committed) 7-4 PATROL for BEA WebLogic User Guide

167 Configuring the JDBC Summary: Perform these steps to configure the Java Database Connection (JDBC) pool. You can set initial number of connections in a new pool, the maximum number of connections that can be maintained in a pool, and a pause interval to prevent overrunning the database server with multiple simultaneous login requests. To set the initial number of connections in a pool: Step 1 Step 2 Right-click the instance icon of the JDBC pool you wish to configure. Choose Pool Tuning => Set Initial Pool Capacity. The Set Initial Pool Capacity dialog appears. Step 3 Step 4 Specify the number of connections that this pool should establish when it is initialized. Click OK. To set the maximum number of connections in a pool: Step 1 Step 2 Right-click the instance icon of the JDBC pool you wish to configure. Choose Pool Tuning => Set Max Pool Capacity. The Set Max Pool Capacity dialog appears. Step 3 Step 4 Specify a limit for the maximum number of simultaneous connections that this JDBC pool should establish. Click OK. Managing WebLogic Components and Services 7-5

168 To set the login delay: Step 1 Step 2 Right-click the instance icon of the JDBC pool you wish to configure. Choose Pool Tuning => Set Login Delay. The Set Login Delay dialog appears. Step 3 Step 4 Specify the number of milliseconds that WebLogic should wait before establishing each login connection to the database server. Click OK. 7-6 PATROL for BEA WebLogic User Guide

169 Configuring the JMS Summary: Perform these steps to configure the Java Message Service (JMS). To configure the JMS: Step 1 Step 2 Right-click the instance icon of the JMS Server. Choose Configuration. The JMS Threshold and Quota dialog box is displayed. Step 3 Step 4 Specify threshold values to set limits on how many bytes and messages should be retained on the message server. Table 7-2 describes the fields in the JMS Server Threshold and Quotas dialog box. Click OK. Managing WebLogic Components and Services 7-7

170 Table 7-2 JMS Server Thresholds and Quotas dialog box fields Field Name Bytes Maximum Bytes Threshold High Bytes Threshold Low Messages Maximum Messages Threshold High Messages Threshold Low Action set the maximum number of bytes to be retained on the JMS server set a number of bytes the will constitute the upper threshold level; when the number of bytes stored on the server exceeds this threshold level, a message is triggered set a number of bytes the will constitute the lower threshold level; when the number of bytes stored on the server drops below this threshold level, a message is triggered set the maximum number of messages to be retained by the JMS server set a number of messages that constitute the upper threshold level; when the number of messages stored on the server exceeds this threshold level, a message is triggered set a number of messages that constitute the lower threshold level; when the number of messages stored on the server drops below this threshold level, a message is triggered 7-8 PATROL for BEA WebLogic User Guide

171 Managing JDBC Pools PATROL for BEA WebLogic provides the ability from within the PATROL Console to create and destroy JDBC connection pools and to enable or disable various types of profiling which can be used to generate reports. Topics in this section include: Create JDBC Pools Delete JDBC Pools Enable or Disable Profiling Generating Profile Reports Managing WebLogic Components and Services 7-9

172 Creating a JDBC Pool Summary: Perform these steps to create a new JDBC connection pool. To create a JDBC pool: Step 1 Step 2 Right-click the WebLogic admin server icon. Choose JDBC => Create JDBC Pool. The Create New JDBC Pool dialog box is displayed. This screen varies depending on which version of BEA WebLogic Server you are monitoring. Figure 7-1 shows the fields that display in WebLogic 5.1 environments while Figure 7-2 shows the fields displayed in WebLogic 6.x and 7.0 environments. Step 3 Step 4 Specify a name for the new JDBC pool and other configuration information as described in Table 7-3 or Table 7-4. Click Accept. Figure 7-1 Create New JDBC Pool Dialog (WebLogic Server 5.1) 7-10 PATROL for BEA WebLogic User Guide

173 Table 7-3 Create New JDBC Pool dialog box fields (WebLogic Server 5.1) Field Name Pool Name URL JDBC Driver Initial Capacity Max Capacity Action name of the pool used within WebLogic; this name must be unique, for example, NewJDBCpool address used to locate the database to which the ppol connects; there are three parts to this URL: protocol database type database name for example, jdbc:cloudscape:demo name of the driver specific to your database type; this is supplied by the JDBC driver vendor (see your vendor documentation for more information) number of connections to create in a new pool maximum number of connections in the pool; this can be any number greater than or equal to the initial capacity Managing WebLogic Components and Services 7-11

174 Figure 7-2 Create New JDBC Pool Dialog (WebLogic Server 6.x or 7.0) 7-12 PATROL for BEA WebLogic User Guide

175 Table 7-4 Create New JDBC Pool dialog box fields (WebLogic Server 6.x and 7.0) (Part 1 of 2) Field Name Pool Name URL JDBC Driver Properties ACL Name Password Initial Capacity Max Capacity Capacity Increment Login Delay Seconds Allow Shrinking? Shrink Period Minutes Refresh Period Minutes Support Local Transaction Prepared Statement Cache Size Test Reserved Conn. Action name of the pool used within WebLogic; this name must be unique, for example, NewJDBCpool address used to locate the database to which the ppol connects; there are three parts to this URL (example, jdbc:cloudscape:demo): protocol database type database name name of the driver specific to your database type; this is supplied by the JDBC driver vendor (see vendor documentation for details) the list of properties passed to the 2-tier JDBC driver for use in creating database connections (such as username and server) name of the ACL used to control access to this connection pool password for connecting to the database number of physical database connections to create in a new pool maximum number of physical database connections in the pool; different JDBC drivers and database servers may limit this number number of connections to add when the pool size is increased number of seconds to delay before creating each connection in the pool; this delay occurs on initial creation and throughout the lifetime of the pool whenever a database connection is created flag indicating that JDBC pool is allowed to shrink to InitialCapacity number of minutes to wait before shrinking an incremented pool connection refresh interval; number of minutes between testing connections using TestTableName; failed connections are reopened; if TestTableName is not set, the the test is not performed flag indicating whether A driver supports SQL with no global transactions; this is ignored for non-a drivers size of the prepared statement cache; number of prepared statements from a connection stored for future use; set to 0 to disable flag indicating whether connections in the pool should be tested; the WebLogic Server tests a connection after giving it to the client, adding a small delay in serving connection requests but ensuring that clients receive working connections (assuming database is available and accessible Managing WebLogic Components and Services 7-13

176 Table 7-4 Create New JDBC Pool dialog box fields (WebLogic Server 6.x and 7.0) (Part 2 of 2) Test Released Conn. Test Table Name Targets flag indicating whether connections should be tested before being returned to the pool; if all connections are in use and a client is waiting for connections, this will cause a slightly longer delay as the connection is tested name of a database table used to test connections in the pool target servers for this deployment 7-14 PATROL for BEA WebLogic User Guide

177 Removing a JDBC Pool Summary: Perform these steps to remove an existing JDBC connection pool. To create a JDBC pool: Step 1 Step 2 Right-click the WebLogic admin server icon. Choose JDBC => Destroy JDBC Pool. The Destroy JDBC Pool dialog box is displayed. Step 3 Step 4 Step 5 Click on the pool you want removed from the list of existing pools. Select whether disconnects will be hard or soft. A soft disconnect allows existing jobs to complete and removes connections as they return to the pool. A hard disconnect immediately removes all connections. Click Accept. Managing WebLogic Components and Services 7-15

178 Administering JDBC Pools Summary: Perform these steps to enable, reset, disable, shrink, or shut down a JDBC connection pool. To administer a JDBC pool: Step 1 Step 2 Right-click the instance icon of the pool you wish to administer. From the KM Commands menu, choose Pool Tuning => Pool Administration. The Pool Administration dialog is displayed. Step 3 Step 4 Click the button next to the function you want performed on this pool. Operations are defined in Table 7-5, Pool Administration Functions, on page Click OK PATROL for BEA WebLogic User Guide

179 Table 7-5 Pool Administration Functions Function Enable Pool Reset Pool Shrink Pool Disable Pool by Dropping Disable Pool by Freezing Soft Shutdown Hard Shutdown Description enable a previously disabled connection pool reset each connection in a connection pool shrink the size of a connection pool, releasing resources allocated to unused database connections disable a connection pool preventing client access, any active user operations are cancelled and current transactions are rolled back disable a connection pool preventing client access, any active connections are suspended until the pool is re-enabled although disconnect operations are permitted to continue shut down a connection pool but allow jobs in progress to complete before destroying the connection, connections are closed as they are released back to the pool immediately shut down a JDBC connection pool, disconnecting any jobs in progress Managing WebLogic Components and Services 7-17

180 Enabling or Disabling JDBC Profiling Summary: Perform these steps to turn on or off the ection of various types of JDBC profile information. Three types of profile information can be ected: Statement profiling: generates details about all SQL statements and their execution data. Connection leak profiling: if connection leaks occur, detailed information about the occurrence is saved. Prepared statement profiling: generates details about the usage of cached prepared SQL statements. Note Collecting statement profile or prepared statement profile information is resource intensive and will degrade system performance if used excessively. Profiling should be disabled when not needed for diagnostic purposes. To turn on or turn off profiling: Step 1 Step 2 Step 3 Right-click the instance icon of the pool for which you want profile information turned on or off. From the KM Commands menu, choose Profile Settings. Choose the command to enable or disable the ection of a type of profile data PATROL for BEA WebLogic User Guide

181 Generating JDBC Profiling Reports Summary: Perform these steps to generate a report of JDBC profile data. Three types of profile report can be generated: Statement profile: reports details about all SQL statements and their execution data. Connection leak profile: if connection leaks occur, reports detailed information about the occurrence. Prepared statement profile: reports details about the usage of cached prepared SQL statements. Note Generating JDBC profile reports requires that profiling be enabled. See Enabling or Disabling JDBC Profiling on page To run the profile reports: Step 1 Step 2 Right-click the instance icon of the pool for which you want profile reports. From the KM Commands menu, choose the command that reports on the type of profiling data in which you are interested. The commands are: Profiling Reports => SQL Roundtrip Profiling Reports => Connection Leak Profiling Reports => Prepared Statement Cache The report is displayed in a task output window. Managing WebLogic Components and Services 7-19

182 7-20 PATROL for BEA WebLogic User Guide

183 8 Managing Web Applications 8 This chapter explains how to effectively manage a BEA WebLogic environment using the PATROL for BEA WebLogic product. The following topics are discussed: Managing Applications Automatically Deploy Domain Applications Deploy and Undeploy Applications to Servers Select Servlet to Monitor Managing Web Applications 8-1

184 Managing Applications PATROL for BEA WebLogic provides an application class called BEAWLS_WEBAPP that monitors web applications and selected servlets from one or more applications. From the administration server, you can control whether applications are automatically deployed and the frequency at which the server checks for applications to be auto-deployed. From the administration server, you can deploy applications to specific servers. From a web application, you can select which servlets will be monitored. Tip Servlets can also be monitored at the method level by using PATROL s instrumentation and profiling features, as can EJBs and SQL statements. See Instrumenting and Profiling J2EE Components on page PATROL for BEA WebLogic User Guide

185 Automatically Deploy Domain Applications Summary: Perform these steps to enable applications to be automatically deployed. Applications are deployed automatically only from the directory /config/mydomain/applications of the installed WebLogic home directory. If the application you want deployed is not in that directory, you must copy it there to have it deployed automatically. To enable automatic deployment of applications: Step 1 Step 2 Right-click the icon representing your administration server. From the KM Commands menu, choose Admin => Domain Applications. The Configure Domain Applications dialog box appears. frequency at which the server checks for new auto-deployed applications Step 3 Step 4 Step 5 Check the box to enable auto-deployment. Change the update interval if desired. Click OK. Managing Web Applications 8-3

186 Deploy and Undeploy Applications to Servers Summary: Perform these steps to deploy and application to a WebLogic server. Any web application can be deployed to one or more WebLogic servers in your environment. You can later update deployment information to roll out the application to different servers, and you can undeploy an application from within the PATROL environment. To deploy an application: Step 1 Right-click the icon representing your administration server. Step 2 From the KM Commands menu, choose Application Deployment => Deploy Application. The Domain Applications dialog box appears. frequency at which the server checks for new auto-deployed applications Step 3 Step 4 Type a unique instance name for the application, the path and file name to the application, and click one or more servers to which the application will be deployed. Click OK. 8-4 PATROL for BEA WebLogic User Guide

187 To update application deployment information: Step 1 Right-click the icon representing your administration server. Step 2 From the KM Commands menu, choose Application Deployment => Update Application. The Update Applications dialog box appears, which is functionally identical to the Deploy Applications dialog on the previous page. Step 3 Step 4 Make whatever changes you want to the deployment information. Click OK. To undeploy an application: Step 1 Right-click the icon representing your administration server. Step 2 From the KM Commands menu, choose Application Deployment => Undeploy Application. The Undeploy Applications dialog box appears. Step 3 Step 4 If your application appear in the list of deployed applications, click its name, otherwise you can type the application name. Click OK. Managing Web Applications 8-5

188 Select Servlet to Monitor Summary: Perform these steps to select servlets packaged inside this web application that you want to monitor. To select servlets: Step 1 Step 2 Step 3 Step 4 Step 5 Double-click the BEAWLS_WEBAPP container. Right-click a WEBAPP instance icon. From the KM Commands menu, choose Monitor Servlets. From the list of available servlets, click the name of each servlet you want to monitor. Click OK. 8-6 PATROL for BEA WebLogic User Guide

189 9 Instrumenting and Profiling J2EE Components 9 This chapter explains how to use PATROL for BEA WebLogic to monitor performance of low-level objects, such as individual SQL statements, EJBs, and servlet methods. Note The features described in this chapter are not active in a default product configuration. They become available only when specifically enabled. See Enabling Instrumentation and Profiling Features on page The following topics are described: Instrumenting and Profiling J2EE Objects Using Instrumentation to Identify and Monitor Most Critical SQL Objects Running the Top N SQL Report Monitoring SQL Objects Using Instrumentation to Identify and Monitor Most Critical EJBs. 9-8 Running the Top N EJB or Top N EJB Methods Report Monitoring EJB Methods Identifying and Using Instrumentation to Monitor Most Critical Application Servlets Running the Top N WebApps Report Running the Top N Servlets Report Monitoring Servlets to the Method Level Instrumenting and Profiling J2EE Components 9-1

190 Instrumenting and Profiling J2EE Objects PATROL for BEA WebLogic contains features that can let you discover detailed performance metrics and monitor your WebLogic components to a very granular level. Using tools provided in the product, you can find which SQL statements, EJBs, 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 in this chapter. identify and monitor most crictical SQL (page 9-3) identify and monitor most crictical EJBs (page 9-8) identify and monitor most crictical app servlets (page 9-8) 9-2 PATROL for BEA WebLogic User Guide

191 Using Instrumentation to Identify and Monitor Most Critical SQL Objects By using the instrumentation features of PATROL for BEA WebLogic, you can generate a report showing which SQL objects are most expensive in your environment and you can monitor their performance. run Top SQL report to find critical SQL (page 9-4) monitor most crictical SQL (page 9-6) Once you know which SQL objects are most critical, and you identify their associated DBURLs, you can also make modifications to your WebLogic 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. Instrumenting and Profiling J2EE Components 9-3

192 Running the Top N SQL Report Summary: Run a report to identify which SQL statements are used most often on your WebLogic servers. 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 by using the command from the DBURL icon, or you can run the report to obtain data for all database URLs on the server by using the command from the server instance icon. To run the Top N SQL report: Step 1 Step 2 Right-click the server instance icon or the DBURL instance icon. From the KM Commands, choose Advance Monitoring => Report Top N SQL. The dialog is displayed. Step 3 Step 4 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. Click OK. 9-4 PATROL for BEA WebLogic User Guide

193 The report is displayed in a report task window. This report shows which statements respond slowest or are most often called. 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. are response times too slow? The most useful information is the SQL call tracing section. This information shows what objects (web applications, servlets, methods, or EJBs) are calling the SQL (stack trace). Information contains the calling sequence of an SQL statement executed from the web application to the JSP or servlet to EJB. The calling stack trace will only be available form the Top N Average Response Times. 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. Where to go from here You can select SQL objects for monitoring (page 9-6), and you can further investigate and monitor methods and servlets related to your top SQL. Instrumenting and Profiling J2EE Components 9-5

194 Monitoring SQL Objects Summary: Monitor selected SQL objects. 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. If you are unsure which SQL objects are most important in your environment, start with the objects with the slowest performance or those most called by applications running in your environment. See Running the Top N SQL Report on page 9-4 to find these SQL. To monitor SQL: Step 1 Step 2 Right-click a DBURL instance icon. From the KM Commands menu, choose Select SQL for Monitoring. The Specify Top SQL dialog box appears. Step 3 Step 4 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. Click OK. The Select the SQL dialog appears. Step 5 Select the SQL you want monitored from the list of top SQL objects. 9-6 PATROL for BEA WebLogic User Guide

195 Step 6 Step 7 Type a label name. This label is used to create an instance icon in the PATROL Console. Click OK. Where to go from here 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. Instrumenting and Profiling J2EE Components 9-7

196 Using Instrumentation to Identify and Monitor Most Critical EJBs In addition to showing you which EJBs are the most resource intensive in your environment, PATROL for BEA WebLogic provides a deeper level to delve into the EJBs themselves and identify which specific methods are most critical. run Top EJB report to find critical EJBs (page 9-9) run Top EJB Method report to drill in (page 9-10) monitor critical EJBs and methods (page 9-11) 9-8 PATROL for BEA WebLogic User Guide

197 Running the Top N EJB or Top N EJB Methods Report Summary: Run a report to identify which EJBs run slowest and are used most often on your WebLogic servers, then run another report to find which specific methods in those EJBs are slowest and most frequently called. You can use this information to decide which EJBs and which EJB methods should be watched more closely. You may also be able to tweak problematic EJBs to optimize performance. To run the Top N EJB report: Step 1 Step 2 Right-click the server instance icon. From the KM Commands, choose Advance Monitoring => Report Top N EJB. The Report on Top N EJB Data Collection dialog is displayed. Step 3 Step 4 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. Click OK. Instrumenting and Profiling J2EE Components 9-9

198 The report is displayed in a system output window. This report shows which EJBs respond slowest (in total and on average) and which are most often called. Using information from the report, you can identify which EJBs should be investigated in more depth. Note the EJB_HOME instance for these EJBs. Use that information to run the Top N EJB Method report to identify which specific methods in an EJB are potentially problematic. To run the Top N EJB Method report: Step 1 Step 2 Right-click the EJB_HOME instance icon. From the KM Commands, choose Advance Monitoring => Report Top N EJB Method. The report appears in a system output window. This report shows which specific methods in an EJB are most often called and which have the slowest total and average response rates. Where to go from here You can select EJBs for monitoring (page 9-6), and you can further investigate and monitor methods and servlets related to your top EJB PATROL for BEA WebLogic User Guide

199 Monitoring EJB Methods Summary: Monitor selected EJB methods. No EJB methods are monitored by default because there are far too many of them, the information is far too detailed for most users, and the objects of critical importance are specific to each individual WebLogic environment. If you are unsure which EJB objects are most important in your environment, start by locating EJBs with the slowest performance or those most called by applications running in your environment, and then run a report on Top N EJB Methods to isolate the methods that are most likely to be important to you. See Running the Top N EJB or Top N EJB Methods Report on page 9-9 to find these objects. To monitor EJB methods: Step 1 Step 2 Right-click an EJB_HOME instance icon (running the Top N EJB Report will tell you which EJB_HOME instance to use). From the KM Commands menu, choose Monitor EJB Method. To stop monitoring an EJB method: Step 1 Step 2 Right-click the instance icon of the EJB method that you want to stop monitoring. From the KM Commands menu, choose Stop Monitoring. Where to go from here You can now monitor your selected EJB method and can set alarm thresholds if you wish to be alerted to significant performance changes in this method. Instrumenting and Profiling J2EE Components 9-11

200 Identifying and Using Instrumentation to Monitor Most Critical Application Servlets You can use the instrumentation features in PATROL for BEA WebLogic to identify which web applications are most used, which servlets in those applications are most critical, and which specific methods are most critical to those servlets. run Top WebApp report to find servlets (page 9-13) set critical servlets for monitoring (page 9-15) identify & monitor critical methods (page 9-17) 9-12 PATROL for BEA WebLogic User Guide

201 Running the Top N WebApps Report Summary: Run a report to identify which web applications are used most often and have the longest response rates on your WebLogic servers. You can use this information to decide which web applications should be watched more closely, and you can identify servlets for deeper profiling. Note When monitoring a WebLogic 5.1 server, you can get a report on top servlets from the server instance by using the KM Command Advance Monitoring => Report Top N Servlet. To run the Top N WebApp report: Step 1 Step 2 Right-click the server instance. From the KM Commands, choose Advance Monitoring => Report Top N WebApp. The Configure Top N WebApp Data Collection dialog is displayed. Step 3 Step 4 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. Click OK. Instrumenting and Profiling J2EE Components 9-13

202 The report is displayed in a system output window. This report shows which applications respond slowest or are most often called. It also shows URI and servlet information. 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. Where to go from here Run the Top N Servlets report (page 9-15) for more information about slowest or most frequently used servlets. You can select servlet objects for monitoring (page 9-6), or you can run Top N EJB or run Top N SQL (page 9-4) reports to look for other critical components PATROL for BEA WebLogic User Guide

203 Running the Top N Servlets Report Summary: Run a report to identify which servlets are used most often and have the longest response rates on your WebLogic servers. You can use this information to decide which servlets should be selected for monitoring. To run the Top N Servlet report: Step 1 Step 2 Right-click the WEBAPP instance icon. From the KM Commands, choose Report Top N Servlet. The Configure Top N Servlet Data Collection dialog is displayed. Step 3 Step 4 Select the checkbox for the criterion you want used to determine top servlets, then slide the control to indicate the number of results you want. Click OK. The report is displayed in a system output window. This report shows which servlets respond slowest or are most often called. 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. Instrumenting and Profiling J2EE Components 9-15

204 Where to go from here You can select servlet objects for monitoring (page 9-6), or you can run Top N EJB or Top N SQL reports to look for other critical components PATROL for BEA WebLogic User Guide

205 Monitoring Servlets to the Method Level Summary: Monitor selected servlets and produce and analyze method-level performance data. Servlets 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. If you are unsure which servlets are most important in your environment, start with the objects with the slowest performance or those most called by applications running in your environment. See Running the Top N Servlets Report on page 9-15 to find these servlets. To monitor servlets: Step 1 Step 2 Step 3 Step 4 Step 5 Right-click a WEBAPP instance icon. From the KM Commands menu, choose Monitor Servlets. From the list of available servlets, click the name of each servlet you want to monitor. Click OK. Run the Methods Response Report from the newly created SERVLET icon to see how well individual methods within the servlet are performing. To run the methods response report: Step 1 Step 2 Right-click a SERVLET instance icon. From the KM Commands menu, choose Methods Response Report. Instrumenting and Profiling J2EE Components 9-17

206 The report is displayed in a system output window. Using the report, you can identify performance characteristics (response rates) of every method in the servlet. You may be able to modify the Java code of identified poorly performing methods to optimize response rates. Note Only the doget, doput, dopost, and dodelete methods are monitored for each servlet. The product will automatically create the SERVLET_METHOD instance icon when the report is executed. Where to go from here You can monitor and analyze performance data for other J2EE components to further optimize overall application performance. See Running the Top N SQL Report on page 9-4 and PATROL for BEA WebLogic User Guide

207 Profiling the Java Virtual Machine The BEAWLS_JVMPROFILER application class provides a way for system administrators to look inside the Java Virtual Machine to see how system resources are being used. Parameters provide various statistics on memory usage, CPU usage, and processes and threads, as well as timing details on garbage ection cycles. Note The BEAWLS_OS application class provides operating system level information about the same types of JVM resources, but may sometimes reflect different values for similar parameters because of differences in the ector polling cycles. Instrumenting and Profiling J2EE Components 9-19

208 Identifying Processes with High CPU Usage Summary: Define a high CPU threshold and identify processes exceeding that limit. To define a high CPU threshold: Step 1 Step 2 Right-click the OS icon. From the KM Commands, choose Setup High CPU Threshold. The Setup High CPU dialog is displayed. Step 3 Step 4 Enter the number of milliseconds that you consider to be the maximum reasonable time for a single WebLogic Server JVM process. If you want to see the current value of this threshold, right-click the BEAWLS_OS icon and choose InfoBox. Click OK. To use the high CPU threshold: Step 1 Step 2 Step 3 Double-click the BEAWLS_OS icon to display its parameters. Look at the NumHighCpuJVMProcesses parameter. This indicates the number of WebLogic Server JVM processes resident in this local host of the monitored domain (i.e., the Admin server and any local managed servers) that exceed the threshold you set. You can set alarms on this parameter if you wish to be notified about processes consuming excess CPU time. Look at the ActiveProcesses parameter. This identifies specific processes running in your JVM. Where to go from here To see details of thread usage see Running a Thread Detail Report on page PATROL for BEA WebLogic User Guide

209 Running a Thread Detail Report Summary: Generate a report showing resource usage by threads on this WebLogic Server JVM. You can identify costly threads and trace their parentage to see what processes spawn them. To run the thread detail report: Step 1 Step 2 Right-click the JVMPROFILER icon. From the KM Commands, choose Thread Detail Report. The report appears in a system output window. Performance data include CPU usage and memory usage (in bytes). Where to go from here: Instrumenting and Profiling J2EE Components 9-21

210 9-22 PATROL for BEA WebLogic User Guide

211 10 Managing JM-Instrumented Applications 10 This chapter explains how to effectively monitor and manage applications that are instrumented with Java Management Extensions (JM). The following topics are discussed: Monitoring JM MBeans Setting Default Address for Notifications Defining Conditions Adding Automatic Actions Adding Notifications Advanced Features for JM Monitoring Manually Registering an MBean Defining Conditions for an Unregistered MBean Setting JM Debug Flags Managing JM-Instrumented Applications 10-1

212 Monitoring JM MBeans PATROL for BEA WebLogic provides tools that let you monitor Java MBeans used in a JM-managed WebLogic 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 WebLogic 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 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 JM MBean monitoring in a typical WebLogic environment. Additional information is in the online Help. setup default notification define conditions add automatic actions add notifications Instrumenting Your Application with JM JM is a universal open technology for management and monitoring of Java applications and systems. Information about the JM specification, including how to instrument your application with JM, is at PATROL for BEA WebLogic User Guide

213 The BEA WebLogic Server (release 6.0 and higher) is instrumented with JM, and it includes everything you need to add JM management capabilities to your applications. The WebLogic JM environment is accessible using the weblogic.management.mbeanhome class, provided by BEA. For WebLogic 6.1 and later, you can access MBeanHome by using JNDI to look up MBeanHome.ADMIN.JNDI.NAME or MBeanHome.JNDI_NAME+. +servername. Once you acess MBeanHome, use the getmbeanserver method to acess WebLogic s MBean server, then use the standard JM methods to register MBeans. For more information, see the documentation provided by BEA. Note In some cases, WebLogic Server 7.0 may cause a security exception when an application attempts to create an MBean. If this happens, include the following line in the script that starts your server: -Dweblogic.diableMBeanAuthorization=true The PATROL for BEA WebLogic MBean Interface In PATROL for BEA WebLogic, you can view MBeans with their components, set MBean attributes, invoke MBean operations, and monitor MBean attributes and notifications. These capabilities are available from the instance icon for the JM_SERVER class (the icon labeled MBeans on server ) or from instances of JM_DOMAIN that appear under the server instance. Some domains are recognized as being provided and controlled by BEA for the purpose of managing WebLogic. For MBeans in these domains, you will not be able to change attributes nor 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. Managing JM-Instrumented Applications 10-3

214 Setting Default Address for Notifications Summary: Perform these steps to define a default address that will receive notifications whenever a defined condition is met. The default address receives notifications for all defined conditions. Individual conditions can also have additional notifications (see Adding Notifications on page 10-13). The default address can be a recipient list, if you want notifications sent to multiple addresses. To set a default address for notifications: Step 1 Step 2 Right-click the BEAWLS_SETUP icon. From the KM Commands menu, choose JM Administration => Setup Notification. The Setup dialog box appears. Step 3 Enter the requested configuration information, described in Table Table 10-1 Setup dialog box Field Name SMTP server Internet address of sender JM recipients Location of JavaMail classes Action type the name of your server, for example, mail.mycompany.com type the name of the account from which notification will be sent, for example, patrol@myhost.com type the 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, for example, d:\bea\wlserver6.1\lib\weblogic.jar The location of JavaMail classes is automatically filled in if any WebLogic servers are currently registered. The SMTP server and the JM recipients are automatically filled in if you have already set up LOG notifications in the BEAWLS_SERVER application class PATROL for BEA WebLogic User Guide

215 Step 4 Click OK. Where to go from here Define the criteria for monitoring JM MBeans. See Defining Conditions on page Managing JM-Instrumented Applications 10-5

216 Defining Conditions Summary: Perform these steps to define conditions for monitoring JM 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 JM server, generate PATROL events, and generate notifications. To define conditions: Step 1 Step 2 Right-click a JM server icon or a JM domain icon under which the MBean is registered. From the KM Commands menu, choose Manage MBeans. 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 10-6 PATROL for BEA WebLogic User Guide

217 Step 3 Click on an MBean to select it. Optionally, you can filter the list of MBeans by completing the fields shown in Table For example, if you wanted to find all MBeans whose type is not Runtime or Config, you would: 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 Table 10-2 MBean Management dialog box Field Name Domain Keys Action 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 paris 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 Value (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 Step 4 Step 5 Click Select. The MBean Information dialog box is displayed. Specify the target attribute or exception on which the condition will be based: 5.A Click a numeric, string, or boolean attribute in the top pane, or a notification in the third pane. 5.B Click the Define Conditions button. Managing JM-Instrumented Applications 10-7

218 5.C Click Select. (If you clicked on a condition in the third pane, you will be prompted for a notification type.) 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 10-8 PATROL for BEA WebLogic User Guide

219 Step 6 Complete the condition definition: 6.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. 6.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. 6.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.) 6.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. Step 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 /JM/ConditionDef/ALL-SERVERS 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. Managing JM-Instrumented Applications 10-9

220 Where to go from here You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page You can change the list of recipients to be notified whenever a condition is met. See Adding Notifications on page PATROL for BEA WebLogic User Guide

221 Adding Automatic Actions Summary: 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 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: Step 1 Step 2 Right-click the JM server instance icon. From the KM Commands menu, choose Define Condition. The Defined Conditions dialog box appears. Step 3 Step 4 Step 5 Click the name of the condition to which you want to add notifications. Click the Modify button. Click Select. The Define Condition dialog box appears. automatic actions are set from this pane Managing JM-Instrumented Applications 10-11

222 Step 6 Step 7 Step 8 In the list of actions, click the action you want to modify. Click the Modify/Enable button to set an automatic action. If you want to remove an automatic action, click the Disable button. 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. Where to go from here You can change the list of recipients to be notified whenever a condition is met. See Adding Notifications on page PATROL for BEA WebLogic User Guide

223 Adding Notifications Summary: You can add addresses for notifications to any defined condition. This process assumes that you have already defined conditions. See Defining Conditions on page To add automatic actions to a defined condition: Step 1 Step 2 Right-click the JM server instance icon. From the KM Commands menu, choose Define Condition. The Defined Conditions dialog box appears. Step 3 Step 4 Step 5 Click the name of the condition to which you want to add notifications. Click the Modify button. Click Select. The Define Condition dialog box appears. notifications are set from this pane Step 6 If you want the default address(es) to receive the notification, click the check box. This can be either in addition to or in place of any other addresses you specify. Managing JM-Instrumented Applications 10-13

224 Step 7 Step 8 Type additional addresses in the specified field. Multiple addresses must be separated by a semicolon. Click OK. Where to go from here You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page PATROL for BEA WebLogic User Guide

225 Advanced Features for JM Monitoring Several JM features in PATROL for BEA WebLogic 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: 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. Managing JM-Instrumented Applications 10-15

226 Manually Registering an MBean Summary: You can register and monitor any Java object that complies with JM 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: Step 1 Step 2 Right-click a JM server instance icon (represented by the application name). From the KM Commands menu, choose Register MBean. The Create New MBean dialog appears. Step 3 Step 4 Enter the required object and class information. Click the Help button if you need more information. Click OK. Where to go from here You can define conditions to monitor your newly registered MBean. See Defining Conditions on page PATROL for BEA WebLogic User Guide

227 Defining Conditions for an Unregistered MBean Summary: Perform these steps to define conditions for monitoring a JM 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. 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 To define conditions for an MBean that is not registered: Step 1 Step 2 Right-click a JM server instance icon (represented by the application name). 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. Step 3 Start defining the condition: 3.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. 3.B Type the object name. You can use wildcards (? or *) to specify multiple MBeans to be monitored for the condition. Managing JM-Instrumented Applications 10-17

228 3.C Click a button to indicate the type of attribute (numeric, string, boolean). 3.D Type the name of the notification or attribute on which the monitoring will be based. 3.E Click Next. The Define Condition dialog is displayed. Step 4 Complete the condition definition: 4.A Change the condition name, object name, or element name, if desired. 4.B Complete the remaining fields. These fields vary depending on the element type you selected. Click the Help button if you need more information. 4.C Click OK. Where to go from here You can add automatic actions to your condition. These actions will occur whenever the condition is met. See Adding Automatic Actions on page You can change the list of recipients to be notified whenever a condition is met. See Adding Notifications on page PATROL for BEA WebLogic User Guide

229 Setting JM Debug Flags Summary: 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 JM 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: Step 1 Step 2 Right-click the BEAWLS_SETUP icon. From the KM Commands menu, choose JM Administration => Set Debug Flags. The JM Debug Flag Settings dialog is displayed. each line is a flag click to toggle on or off file location to save debug data Managing JM-Instrumented Applications 10-19

230 Step 3 Step 4 Step 5 Click a line to turn a flag on. Click it again to turn it off. Click the File button and enter a file name and directory path in which to save debugging information. Click Select PATROL for BEA WebLogic User Guide

231 11 Administering the KM 11 This chapter explains how to manage the PATROL for BEA WebLogic product itself, rather than using the product to manage WebLogic. The following topics are discussed: Monitoring WebLogic Across the Enterprise Tune Collectors Schedule Blackout Periods Restart PATROL s Java Collector Troubleshooting and Debugging Set PSL Debug Flag Set Debug Status for Server Record Data Administering the KM 11-1

232 Monitoring WebLogic Across the Enterprise PATROL for BEA WebLogic contains several commands in the BEAWLS_SERVER application class that are initiated from the administration server icon but that affect how PATROL monitors your entire WebLogic environment. These commands include: Tuning ectors: by using only those ectors that are most critical to your monitoring needs, but turning off others, you can improve overall PATROL performance and more easily scale to larger monitoring environments. Scheduling blackout periods: you can suspend PATROL alerts for periods of time when you shut down parts of your WebLogic environment. Routine maintenance shutdowns or backups might ordinarily trigger PATROL alerts, but you can suspend those alerts temporarily by scheduling a blackout period. Start Java ector: you may occasionally need to restart your PATROL ector after routine maintenance shutdowns, or when the ector status shows that it is not operating correctly PATROL for BEA WebLogic User Guide

233 Tune Collectors Summary: You can turn on or off ectors for individual application classes. Turning off ectors for parts of the system that are not critical to your environment can improve overall performance. To tune ectors: Step 1 Step 2 Right-click an administration server instance icon. From the KM Commands menu, choose KM Administration => Tune Collectors. The Collector Status dialog box appears. Step 3 Step 4 Click boxes to select or unselect a ector. Checked boxes are enabled. All ectors are enabled by default. Click Accept. Administering the KM 11-3

234 Schedule Blackout Periods Summary: You can temporarily suspend warnings and alarms. Perform these steps to specify one or more blackout periods, or to remove (delete) a currently defined blackout period. During blackout periods, PATROL continues to monitor the WebLogic server environment but does not report object state changes nor generate warnings or alarms. This feature is useful for scheduled maintenance and planned system downtime. To schedule a blackout period: Step 1 Step 2 Right-click the administration server instance icon. From the KM Commands menu, choose KM Administration => Schedule Blackout Periods. The Schedule Blackout Periods dialog box is displayed PATROL for BEA WebLogic User Guide

235 Step 3 Step 4 Step 5 Select the Add a Blackout Period action. Set the blackout start time, and duration to define a blackout period. Field definitions are in Table 11-1 Click Apply. Table 11-1 Blackout Period dialog box fields Field Name Add a Blackout Period Delete a Blackout Period(s) Blackout Start Time Blackout Duration Blackout Period to Delete Action select this option to define a new blackout period select this option to delete a previously defined blackout period select the day of the week and time that you want to begin blackout click the day of the week on which you want the blackout period to begin; use the arrow keys to select the hour, click the minutes or seconds field and type a value on the keypad to enter more precise times time values must be entered in a 24-hour format, for example, 8:30pm should be entered as 20:30:00 hours set the duration to the length of time you want the blackout to last; type a number in the field and use the pull-down list to choose the units (the default is hours) if you want to delete a previously defined blackout period, click the period from the selection list to highlight it (the Delete Blackout Period radio button must be selected to delete a period) To remove the blackout period: Step 1 Step 2 Step 3 Step 4 Step 5 Right-click the server instance icon. From the KM Commands menu, choose KM Administration => Schedule Blackout Periods. Click the radio button labeled Delete a Blackout Period. Click the blackout period you want deleted from the list of defined periods in the Blackout Period to Delete field. Click Apply. Administering the KM 11-5

236 Restart PATROL s Java Collector Summary: Perform these steps to restart Java data ection. This will restart the Java class PatcolWebLogic.class, which ects data about the BEA WebLogic Server application for monitoring in the PATROL environment. This command is usually used after bringing a server up after a shutdown period for maintenance or backup, or after an abnormal termination. The ector status can be determined by examining the state of the PatrolCollectorStatus parameter; the ector may need to be restarted if PatrolCollectorStatus does not reflect a running state (green stop light). Note Restarting the ector can result in lost data if the command is used at a time when the ector is communicating with the PATROL Agent. You can also check the log file for detailed error messages; the log is located in $PATROL_ROOT\BEAWLKM. To restart the ector: Step 1 Step 2 Step 3 Right-click the administration server instance icon. From the KM Commands menu, choose KM Administration => Restart Java Collector. A warning dialog will appear asking you to confirm that you really want to restart the ector. Click Yes PATROL for BEA WebLogic User Guide

237 Troubleshooting and Debugging Problems occasionally occur even in the best-managed environments. PATROL for BEA WebLogic includes several tools to help isolate and identify problems causes. Information about contacting BMC Software technical support is provided inside the cover of this user guide. Some of the troubleshooting tools provided in PATROL for BEA WebLogic include: Setting PSL debug flags (page 11-8) Setting the debug status for the server (page 11-10) Recording ector data (page 11-12) Setting debug flags for JM (page 10-19) Additionally, troubleshooting information is provided in the online Help for this product. If you are unable to solve a problem with PATROL for BEA WebLogic, you may need to contact BMC Software technical support: contact information is provided inside the front cover of this manual. Administering the KM 11-7

238 Set PSL Debug Flag Summary: Perform these steps to turn on or off debug information logging for PATROL Script Language (PSL) code. PSL generates various types of error and tracing information that you can log by setting flags. To set debug flags: Step 1 Step 2 Right-click the administration server instance icon. From the KM Commands menu, choose KM Administration => Set PSL Debug. The Set PSL DEBUG Flag dialog box lists types of debugging information that you can record. Step 3 Step 4 Click checkboxes next to the types of debugging information you want enabled. A check indicates that the option is turned on. Click the box again to turn the option off (uncheck). Table 11-2 provides more information about the types of information that are logged when each box is checked. Click OK PATROL for BEA WebLogic User Guide