HP OpenView Operations. User s Guide

Transcription

1 HP OpenView Operations SMART PLUG-IN FORWEBLOGIC SERVER User s Guide B Release A

2 Legal Notices Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard Company shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice. Hewlett-Packard respects all registered trademarks and copyrights. Microsoft and Windows NT are U.S. registered trademarks of Microsoft Corporation. Pentium is a U.S. registered trademark of Intel Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. BEA and WebLogic, are registered trademarks of BEA Systems, Inc. All other product names may be trademarks of the respective companies with which they are associated. Hewlett-Packard Company OpenView Business Unit 8000 Foothills Boulevard Roseville, CA USA Copyright Hewlett-Packard Company, ii

3 Conventions Boldface Capitalization Computer font Italics Words in boldface type represent user selections, programs, and commands. Capitalized first letters represent company or product names. Words in computer font represent file or path names, command syntax statements, prompts or messages that appear on your screen, or text you should type on your workstation or terminal. Words in italics represent variables in syntax statements or words that are emphasized in the text. { } Represents required elements in a syntax statement. When several elements are separated by the symbol, you must select one of the elements. [ ] Represents optional elements in a syntax statement. iii

4 Printing History New editions are complete revisions of the manual. The printing dates for each edition are listed below. Edition 1 November 2001 iv

5 Contents Chapter 1: WebLogic Server SPI Concepts Introduction Introducing the SMART Plug-In for WebLogic Server How the SMART Plug-In for WebLogic Server Works Components of the SMART Plug-In for WebLogic Server Applications Templates Reports: from OVO Actions or WLSSPI Applications Chapter 2:Installing & Configuring the WebLogic Server SPI. 2-1 Introduction How to Install & Configure WLS-SPI Check the Installed WebLogic Server SPI Nodes for License Count.2-17 How to Remove WLS-SPI Chapter 3: Using and Customizing the WebLogic Server SPI Introduction Using WebLogic Server SPI Templates WebLogic Server SPI Template Groups OVO Template Types and WLS-SPI Basic Template Customizations Modifying Monitor Templates Advanced Template Customizations Choosing Metrics To Monitor Changing the Collection Interval for All Scheduled Metrics Changing the Collection Interval for Selected Metrics Customize the Threshold for Different Servers Creating Custom, Tagged Templates Re-installing the WLS-SPI Templates Using Templates/Applications to View Annotation Reports and Graphs Sample Report i

6 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Introduction Integrating WebLogic Server SPI with Reporter to Generate Reports. 4-3 WebLogic Server SPI Reports Integrating WLS-SPI Performance Manager Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Metric Definitions Structure Create User-defined Metrics Create a UDM Template Group Sample Metric Definition Document Chapter 6: Troubleshooting and Log File Text Error Messages WASSPI All Other Errors Appendix: Directory Locations ii

7 WebLogic Server SPI Concepts 1

8 Chapter 1: WebLogic Server SPI Concepts Introduction Introduction The SMART Plug-In for WebLogic Server is a full-featured SPI that allows you to manage WebLogic servers from an HP OpenView Operations console. This chapter offers a basic introduction to its concepts. It is suggested you read the chapter before installing and configuring the SPI in Chapter 2. The following topics are covered:! Introducing SMART Plug-In for WebLogic Server! How the SMART Plug-In for WebLogic Server Works! Components of the SMART Plug-In for WebLogic Server 1-2

9 Chapter 1: WebLogic Server SPI Concepts Introducing the SMART Plug-In for WebLogic Server Introducing the SMART Plug-In for WebLogic Server The SMART Plug-In for WebLogic Server (WLS-SPI) adds monitoring capabilities otherwise unavailable to HP OpenView Operations (OVO). SMART Plug-In integration uses: Used in conjunction with OVO, the WLS-SPI offers centralized tools that help you monitor and manage systems using WebLogic Server. From the OVO console, an operator can apply the same familiar HP OpenView performance and problem managing processes to monitor a system using WebLogic Server. WLS-SPI metrics are automatically sent to the Operations Agent and can be graphed using OpenView Reporter (purchased separately), which helps you to analyze trends in server usage, availability, and performance. SMART Plug-In data: After completing the easy WLS-SPI installation, you can find dozens of key server-related metrics. Among them are metrics that cover the following areas: " server availability " server performance " memory usage " transaction rates " servlet executing times, time-outs, request rates " JDBC connection status " Web application processing " Java message service processing " cluster processing " exception counts of scheduled WLS actions SMART Plug-In uses/customizations: WLS administrators can choose those metrics that are most crucial to the successful operation of WebLogic Server by modifying WLS-SPI templates. The templates contain settings that allow incoming data to be measured against predefined rules that generate useful information in the form of messages. These messages with severity-level color-coding can be reviewed for problem analysis and resolution. Corrective actions that are pre-defined for specific events or threshold violations can be automatically triggered or operator-initiated. 1-3

10 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works How the SMART Plug-In for WebLogic Server Works WebLogic Server SPI (WLS-SPI) messaging, reporting, and action-executing capabilities are based on the OVO concept of templates. The settings within these templates define various conditions within the WebLogic Server. Once in use, WLS-SPI templates allow information to be sent back to the OpenView Operations management server to help you proactively address potential or existing problems and avoid serious disruptions to Web transaction processing. HOW WLS-SPI COLLECTS AND INTERPRETS SERVER PERFORMANCE/AVAILABILITY INFORMATION The WebLogic Server SPI, once configured and deployed to managed nodes, gathers data that is interpreted and acted upon, according to settings within the deployed templates. Those templates, described in a later section, define conditions that can occur within the WebLogic Server, such as queue throughput rates, cache use percentages, timeout rates, average transaction times, etc. Default thresholds, set within the templates, monitor these conditions and trigger messages to the console when a threshold has been exceeded. 1-4

11 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works HOW WLS-SPI DISPLAYS THE INFORMATION Messages in the Message Browser: Comparing the values gathered for WebLogic Server performance/availability against the monitor template settings relating to those specific areas, OVO agent software forwards the appropriate messages to the OVO console. These messages are displayed with color-coded severity levels in the OVO Message Browser. 1-5

12 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works Instruction Text: Messages generated by WLS-SPI programs contain instruction text to help diagnose and remedy problems. Corrective actions that are preassigned to events can be triggered automatically or manually by an operator. You can usually find instruction text in the message details; this same text is also available in the HP OpenView SMART Plug-In for WebLogic Server SPI Reference manual metric definition. ASCII-Text Reports: In addition to the instruction text mentioned above, some messages cause automatic action reports to be generated. These reports show conditions of specific WebLogic Server instance. When a report is available, like the instruction text, you can find it within the Message Details, specifically in the Annotations area. 1-6

13 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works GENERATING REPORTS USING HP OPENVIEW REPORTER The WebLogic Server-SPI also integrates with HP OpenView Reporter to provide you with 20 management-ready, Web-based reports. WLS-SPI includes the templates for generating these reports within its Report package, which you can install on the Reporter Windows system. After you have installed the product and completed some configuration steps (all detailed in Chapter 2), you can expect to see new reports of summarized, consolidated data generated nightly that will help you assess how WebLogic Server is performing over time The WebLogic Server SPI reports can use WLS-SPI data to vividly illustrate servlet request rates, transaction throughput rates, and average transaction execution time, to name just a few generated reports. 1-7

14 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works GRAPHING DATA WITH OPENVIEW PERFORMANCE MANAGER Another OpenView product, Performance Manager 4.0 (OVPM), integrates with WLS-SPI to enable use of the WLSSPI Admin View Graphs application to generate WLS-SPI graphs. OVPM also allows you to view WLS-SPI graphed data from most WLS-SPI alarm messages by pressing the Perform Action button. You see this button in both the Message Browser and in the message details (access details by either double-clicking the message or selecting the Details... button) in the Message Browser. The action launches your Web browser, where you can choose a graph that shows values for the metric that generated the message as well as other related metrics. Metrics collected by WLS-SPI can be graphed. The values can then be viewed for trend analysis 1-8

15 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works CHANGES YOU CAN MAKE You can use WLS-SPI templates with no customization, or you can change them as you find necessary. Minor modifications and major customizations are listed here: Modification of Default Templates: Within a template you can change the default settings for (1) collection interval, (2) threshold, (3) message text, (4) duration (5) severity level of the condition, (6) actions assigned to the condition (operator-initiated or automatic). Creation of Custom Template Groups: Create custom template groups, using default templates as a starting point. To do this, see Chapter 3. Custom Metrics: The ability to define your own metrics or user-definable metrics (UDMs) is a powerful feature that you can use to expand the monitoring capabilities of WLS-SPI. Instructions are available in Chapter

16 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works Components of the SMART Plug-In for WebLogic Server The WebLogic Server SMART Plug-In components include applications and templates that allow you to configure and receive data in the form of messages and short reports. These messages (available in the Message Browser) and short reports (through applications or message details) provide you with information about conditions present in the server(s) running on specific managed nodes. WLS-SPI configuration applications let you configure the management server s connection to named server instances on specific managed nodes. After you have configured the connection, you can assign templates to the nodes. With OVO agent software running on the manage nodes, you can use WLS-SPI reporting applications to generate reports. In addition, you can generate graphs that show WLS-SPI data. Chapter 2 details how to install the components and use them to configure server instances on the managed nodes and then deploy the template groups. The sections that follow here give you brief descriptions of all components. 1-10

17 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works Applications The WebLogic Server SPI applications include configuration, troubleshooting, and report-generating utilities. In the OVO Application Bank window the WebLogic Server SPI applications are divided into two groups. WebLogic Server SPI applications. The applications in the WLSSPI group allow you to configure the connection to the server you are monitoring and to turn collections and tracing on and off. The group contains subgroups and applications that are nearly duplicate for UNIX and NT nodes. NOTE Any group name that includes NT within it indicates its applications are for NT nodes. No NT within the group name means those applications are for UNIX nodes.! WLSSPI Admin. This group contains configuration and troubleshooting applications requiring root permission, so it is recommended the group be assigned to the OVO administrator. WLSSPI-Admin applications allow you configure, control, and troubleshoot the WLS-SPI. 1-11

18 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works The group contains the following applications: " Config WLSSPI. Opens the SPI configuration file within a text editor (vi is the default). Upon its initial opening, this file contains syntax examples for configuring the connection to the WebLogic Server on a managed node. (After you save the file, the examples are deleted.) This file contains information about the WebLogic servers being monitored, such as the server name and port number, as well as other information such as the location of a user-defined metrics definition file, if applicable. " View Error File. Allows user to view the entire WebLogic Server SPI error log. " Start Monitoring. Turns collection off for the entire WebLogic Server SPI or for a selected server on the managed node. " Stop Monitoring. Turns collection on for the entire WebLogic Server SPI or for a selected server on the managed node. " Verify. Verifies that the WebLogic Server SPI is properly installed on the server or managed node. " View Graphs. For users of OpenView Performance Manager, you can configure your Web browser (see Chapter 2 and Chapter 4) to display WLS-SPI graphs. The ovweb program launches your browser, which allows you to graph WLS-SPI metric data. WebLogic applications. These applications offer a quick way of checking the status or logfiles of a WebLogic server and starting or stopping a server. 1-12

19 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works WebLogic applications provide you with convenient access to WebLogic functions. You can open the WebLogic applications by double-clicking WLSSPI WebLogic in the Application Bank window. The group contains the following: " Check WebLogic. Does an interactive status check of the WebLogic Server. " Start WLS Console. Launches your Web browser, which displays the WebLogic Server Admin Console. You need to set this up before it will work. Set up involves a couple of steps, detailed in Chapter 2 (Task 2 and Task 6). " Start WebLogic. Allows OpenView Operations user to start the WebLogic server (requires setup). " Stop WebLogic. Allows OpenView Operations user to stop the WebLogic server (requires setup). " View WebLogic Log. Allows user to view the entire specified WebLogic Server log file. 1-13

20 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works Templates The SPI for WebLogic Server template group contains three subgroups with templates corresponding to WebLogic Server versions: " WebLogic Server 6.0 " WebLogic Server 6.1 " WebLogic Server 5.1 (minimal functionality, equivalent to the Gallery SPI; included here for your convenience; contains a single metric that monitors the availability of WebLogic Server). The two full-featured groups, WebLogic Server 6.0 and 6.1, contain two template subgroups for monitoring WebLogic Server-related metrics and logfiles and another template for intercepting messages as follows: " Metrics: monitors incoming values that reflect WebLogic Server s performance levels and availability. Each value is evaluated according to the metric with which it is associated. If it is acceptable, it is ignored; if it is not, a message is sent to the OVO Message browser. WLS Metrics contain monitor templates with settings for triggering alerts/messages andcollector templates, which show the metrics (each of which has a unique number) whose values are collected for that interval. Each collector template group is assigned a collection interval of 5 minutes, 15 minutes, one hour, orone day. The collection interval indicates how often data is collected for that specific group. Each monitor template determines the threshold conditions for the monitored metric, the message text that is triggered when the threshold is exceeded, the actions to execute, and instructions that appear. Each collector template controls what metrics are collected. Specifically, the collector template has three functions: (1) to run the collector/analyzer at each collection interval and (2) to show all monitor templates within the group, and (3) to specify which metrics are collected. 1-14

21 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works " Logfiles: monitors WebLogic Server- and WebLogic SPI-generated logfiles. The information captured from these logfiles includes changes to WebLogic Server configurations and errors that occur in the operation of the WebLogic Server or the WebLogic SPI itself. " WLSSPI Messages. Not a group, but a single template that can be used to intercept specific messages. 1-15

22 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works The last three messages belong to the WebLogic and WLSSPI Message Groups (see the column titled MsgGrp), indicating their origins. The WebLogic messages indicate conditions occurring in WebLogic Server, while the WLSSPI messages indicate conditions occurring in the WebLogic Server SPI. Reports: from OVO Actions or WLSSPI Applications WLS-SPI reports can show information on past or current conditions in the server. These reports can be triggered by alarm conditions or generated when you need information on the current state of a server. Reports generated through Automatic actions are context sensitive, relating only to a single server on the managed node. Reports generated through the Application Bank show information on all servers configured on the managed node. Specifically, each report type is defined as follows: 1-16

23 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works! Automatic Action Reports: generated automatically by an alarm conditioninrelationtoanindividual server instance on a managed node. These reports are available by clicking the Annotations button in the OVO Message Browser. If you have configured your Message Browser to display the SUIAONE columns, a flag under the S column (adjacent to the message) indicates that the report was generated successfully and is waiting in the Annotations of the message.! Application Bank Reports: generated manually by dragging the managed node onto the report in the Application Bank. These reports reflect the current condition of all configured server instances on the managed node at the time you generate it. WLS-SPI Application Bank Reports. You can generate a report on all servers of a managed node by dragging the node onto a report in the Application Bank window. 1-17

24 Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works COMPONENT INTERACTION WLS-SPI components must all work together in order to retrieve data and deliver useful information regarding the health of the targeted server. The tasks that components complete and the windows you use to access the individual components are as follows: Task Connecting to the server & configuring the managed node Interpreting/ displaying information on the WebLogic server conditions Configuring metric collections Window you open Component you use: Application Bank window WebLogic SPI SPI Admin Config WLSSPI: When you run the application WLS SPI Config, you enter information about the Web application server running on the managed node, so the SPI knows how to connect to the server and gather data for metrics and reports. Message Source Templates window monitor templates: Defines conditions relating to each metric value used by OVO agent software to generate messages and other information made available in the OVO Message Browser. Message Source Templates: collector template. Lists all metrics within the template group and directs the collector/analyzer to collect the values of the specified metrics at predefined intervals, compare them to permissible levels, and call OVO to check threshold values and trigger alarms. 1-18

25 Installing & Configuring the WebLogic Server SPI 2

26 Chapter 2: Installing & Configuring the WebLogic Server SPI Introduction Introduction This chapter covers installing, configuring, and removing WebLogic Server SPI (WLS-SPI) program components for use with OpenView Operations. The sections that follow provide instructions for:! How to Install and Configure WLS-SPI! How to Remove WLS-SPI 2-2

27 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI How to Install & Configure WLS-SPI To install and configure WLS-SPI, complete the tasks in the order listed: " Task 1: Install on the HP-UX Management Server " Task 2: (optional) Configure the Management Server to Launch your Web Browser " Task 3: Assign Operator Responsibilities for Administrator " Task 4: Add Nodes to the WLS-SPI Node group " Task 5: Distribute Actions, Monitors, Commands " Task 6: Configure a WebLogic Server User " Task 7: Configure Server Connections and Graphs " Task 8: Distribute WLS-SPI Templates TASK 1: INSTALL ON THE HP-UX MANAGEMENT SERVER To install the WebLogic Server SPI, you can use a swinstall command (from the command line) for both HP-UX or Solaris systems. For HP-UX systems, you can also use the graphical user interface (GUI), but the GUI method is not covered in this section due to the numerous differences in displays for the various HP-UX versions. Prerequisite/pre-installation information: OpenView Operations (OVO) management server must be installed. It is not necessary to stop OVO sessions before beginning the WLS-SPI installation. To install all bundles for an HP-UX management server, enter: /usr/sbin/swinstall -s /cdrom/wlsspi_hpux_ito_a depot WLSSPI To install all bundles for a Solaris* management server, enter: /usr/sbin/swinstall -s /cdrom/wlsspi_sol_ito_a depot WLSSPI * For managing SOLARIS managed nodes from an HP-UX management server, install the HP-UX version, NOT the SOLARIS version. 2-3

28 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI The WebLogic Server SPI bundles and filetsets are as follows: BUNDLE SPIWebLogicHPUX BUNDLE SPIWebLogicSOL BUNDLE SPIWebLogicNT* BUNDLE SPIWebLogicAll FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-HPUX END_BUNDLE FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-SOL FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-NT* FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-HPUX FILESET WLSSPI.WLSSPI-SOL FILESET WLSSPI.WLSSPI-NT* PRODUCT WLSSPI (Filesets can be selected individually for UNIX/Solaris/NT environments) FILESET WLSSPI-CORE FILESET WLSSPI-HPUX FILESET WLSSPI-SOL FILESET WLSSPI-NT* NOTE *For Windows NT 4.0 managed nodes, on the managed node the TEMP environment variable must be set in the OVO agent s environment. One way to ensure this is the case is by setting TEMP as a System Variable. Usually TEMP is set as a User Variable, but it may not be set for the user that OVO runs as. You can add TEMP to the System Variables by opening the Control Panel System Environment tabbed dialog. If you do not establish this setting, WLS-SPI programs may not execute successfully on the NT 4.0 managed node. 2-4

29 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 2: (OPTIONAL) CONFIGURE THE MANAGEMENT SERVER TO LAUNCH YOUR WEB BROWSER WLS-SPI uses the ovweb utility to start your Web browser for displaying graphed metrics (which require OpenView Performance Manager 4.0 or higher) and also for launching the WebLogic Administration Console. If you do not use OpenView Performance Manager and do not want to start the WebLogic console from the OVO console, you can skip this task. Before ovweb can launch your Web browser, however, you must insert the browser invocation command within the ovweb.conf file. If no browser invocation command is included in the ovweb.conf file, ovweb tries to start Netscape (which must be version 4.7 or higher). NOTE The ovweb.conf file must be located in the directory specified by the environment variable $OV_CONF, used by OpenView Operations. If necessary to discover the OpenView Operations directory structure on your management server, open the /opt/ov/bin/ov.envvars.sh file and look for the $OV_CONF definition. " Enter the browser invocation command in the ovweb.conf file: The browser invocation command must contain a %s to allow the WebLogic SPI to pass a URL to the browser. Open the file and insert the command according to the entry syntax and example as follows: Syntax: Browser: <browser command> %s Example: Browser: /opt/netscape/netscape %s " Check the Web browser setting: To display the WLS-SPI graphs, ensure that your browser is JavaScript enabled. Check the setting within the browser s Preferences. NOTE An additional step, covered in Task 6, is required for the graph display. In this task you enter the location of the Reporter Windows system in the WLS-SPI configuration file. For more information about launching a browser in OpenView Operations, consult the manpages for ovweb and ovweb.conf and ov.envvars. To access instructions for enabling graph displays, at a command prompt enter: man ovweb 2-5

30 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 3: ASSIGN OPERATOR RESPONSIBILITIES FOR ADMINISTRATOR 1. Log on to OVO as administrator (opc_adm). 2. Open the User Bank window, right-click the opc_adm user, and choose Modify. 3. In the Modify User:opc_adm user window press the Responsibilities... button. 4. For WLSSPI and WebLogic Message Groups, ensure all boxes are checked. 5. Assign the WLSSPI Node or Message Groups to any other appropriate operators. 2-6

31 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI 6. Click Close. TASK 4: ADD NODES TO THE WLS-SPI NODE GROUP WLS-SPI automatically creates three node groups (WLS-SPI 6.0, WLS-SPI 6.1, or WLS-SPI 5.x) with appropriate template groups already assigned. You need only place any nodes running WebLogic Server in the correct node group. 1. From the Window menu, open both the Node Group Bank and the Node Bank to display (side-by-side) the WLS-SPI node groups and the managed nodes. 2. Drag and drop managed nodes running WebLogic Server into the appropriate WLSSPI node group, according to the WebLogic Server version running on the node. NOTE WLS-SPI can monitor multiple WebLogic servers running on one managed node. However, the WebLogic servers must all be the same version. TASK 5: DISTRIBUTE ACTIONS, MONITORS, COMMANDS 1. Select a node or node group on which to install the SPI. 2. From the Node Bank s Actions menu select Agents Install/Update SW & Config. 3. In the Install/Update OVO Software and Configuration window select the following component check boxes: " Actions " Monitors " Commands (Do NOT select Templates. ) 2-7

32 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI Using this dialog, you deploy program components to the managed node(s). 4. Check the Force Update check box. 5. Select the Nodes in list button. Upon completion, the following message appears in the Message Browser for each managed node: The following configuration information was successfully distributed: Actions Commands Monitors The WLS-SPI is now installed on the Management Server and selected managed node(s). If you want to install the WLS-SPI on other managed nodes, repeat steps 1-5). 2-8

33 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 6: CONFIGURE A WEBLOGIC SERVER USER In order to run the WLS-SPI data collector with a WebLogic user name other than guest, you must configure the correct permissions for the user you select. To configure a WebLogic user for the WLS-SPI in WebLogic 6.0 or 6.1: 1. In the WebLogic Server admin console, create the user/password that you plan to use for the WLS-SPI if it does not already exist. 2. Create an ACL named weblogic.admin.mbean if it does not already exist. 3. Create a permission named access for this ACL if it does not already exist. 4. Add the user (created in step 1) to the list of users for the access permission created in step In the next task, where you configure the SPI connection to WebLogic Server, you must add the user/password information within the configuration file. (See the SERVER<n>_LOGIN and SERVER<n>_PASSWORD keywords in Task 7.) 2-9

34 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 7: CONFIGURE SERVER CONNECTIONS AND GRAPHS With WLS-SPI installed on the OVO management server, you must now configure the connection to WebLogic Server on each managed node. A single file on the on the management server contains all WLS-SPI configuration, where you define: " WebLogic Server and Java program file locations " WebLogic Server server information " user information " (optional) OpenView Performance Manager system location (for graphing) When you save the file as part of the configuration process, only the relevant information for each node is transmitted to the node. Convenience and security are the result, for you have all configuration information in one place on the management server but only relevant information present on each managed node. 1. At the OVO console, select the node in the Node Bank window. 2. From the Window menu, select Application Bank. 3. In the Application Bank window double-click the icons WLSSPI WLSPI Admin Config WLSSPI. (If the items do not appear, select Map Reload.) A window running a text editor opens the WLS-SPI configuration file. NOTE The UNIX default text editor for the file is vi. You can select another text editor by setting the EDITOR environment variable in the root user setup. 4. Enter the information (as explained in the sections that follow) into the file and save. When you save the file, OVO automatically deploys the configuration to the selected node and displays the message: 2-10

35 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI Set configuration for <node>? [yes] Transferring configuration to <node> followed by: Importing configuration on <node>. The example below demonstrates how entries might appear. Read the sections that follow for the correct syntax for your specific entries. WL_HOME= /opt/bea/wlserver6.0sp1 JAVA_HOME= /op/bea/jdk130 NUM_SERVERS= 1 SERVER1_NAME= myserver SERVER1_PORT= 7001 GROUP production_nodes { pnodea.company.com pnodeb.company.com } NODE tnodez.company.com { SERVER1_NAME= testserver SERVER1_PORT= 7010 } NODE production_nodes { SERVER1_NAME= real_server } NODE bignode.company.com { NUM_SERVERS=2 SERVER2_NAME= petstore SERVER2_PORT= 7101 } 2-11

36 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI Syntax Structure Lines preceded by # are treated as comments and are ignored. variable=<value> vaiable=<value> GROUP <group_name> { node_name node_name... } NODE <node_name group_name> { var=value var=value... } Variable (variable=<value>) definitions outside NODE blocks apply to all nodes but are overriden by variable definitions inside a NODE block, which apply only to the specified node_name or node group_name. Entries for GROUP NODE Blocks Group blocks (sections identified as GROUP <group_name>)areusedtogroup nodes together that have common variables. The method works in this way: " To define a GROUP, follow GROUP with a group_name to identify the group of nodes with common variables, and then list the nodes in the group. In a node block below you will repeat the group_name (following NODE) to define the variables of the group as described below. Node blocks (sections identified as NODE <group_name> <node_name>)work either in conjunction with group blocks (as described above) to define variables for a group, or stand-alone to define variables for a single node. Node blocks, then,workinthisway: " To define group variables in the node block, follow NODE with the <group_name>, and between the curly brackets list the variables common to the group. " To define individual node variables in the node block, follow NODE with a node_name, and within the curly brackets that follow list the variable 2-12

37 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI definitions that apply to that node. Any configuration file entry occurring more than once within the configuration file is resolved by the last definition taking precedence over any previous entry. NOTE The node name specified in a node or group block must match the value returned by the OVO variable $OPC_NODES, which usually is the fully qualified domain name of the node. Entries for SERVER Numbering and Variables Each variable specifiedasserver<n>_var refers to a specific WebLogic Server instance. When more than one WebLogic Server is running on a given managed node, the number <n> differentiates the servers. Numbering must begin at 1 for each managed node, with the NUM_SERVERS variable set to the actual number of WebLogic Servers running on the node. Configuration file variables (keywords) are as follows: Variable (Keyword) WL_HOME JAVA_HOME NUM_SERVERS Value entered Enter the directory where WebLogic Server is installed. Example: WL_HOME = /opt/bea/wlserver6.0sp1 Enter the directory where Java is installed. The java engine is expected to be $JAVA_HOME/bin/java: Example: $JAVA_HOME = /opt/bea/jdk130 Enter the number of WebLogic servers on the managed node. Example: NUM_SERVERS = 3 SERVER<n>_NAME Enter the server name as defined in WebLogic Server. Example: SERVER1_NAME = myserver 2-13

38 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI SERVER<n>_PORT WL_USER SERVER<number>_START_CMD SERVER<number>_STOP_CMD SERVER<number>_LOGIN SERVER<number>_PASSWORD SERVER<number>_VERSION GRAPH_SERVER Enter the port the WebLogic server listens on. Example: SERVER1_PORT = 7001 Enter the system username for starting and stopping WebLogic Server from the OVO Application Bank. The default is the username under which the OVO agent runs. Example: WL_USER = weblogic Enter a fully qualified system command that starts WebLogic Server from the OVO Application Bank application Start WebLogic. This command is run by WL_USER (defined above) and must be included in order for the Start WebLogic application to work. NOTE: This command must exit; that is, the WebLogic Server process must run in the background or as a service, and it must be protected from its parent process dying. Example: SERVER1_START_CMD = /sbin/init.d/weblogic start Enter a fully qualified system command that stops WebLogic Server. This command is run from the OVO Application Bank application Stop WebLogic and is run by WL_USER (defined above) and must be included in order for the Stop WebLogic application to work. Example: SERVER1_STOP_CMD = /sbin/init.d/weblogic stop Enter a WebLogic Server-defined user (not a system user) that will be used to monitor the WebLogic Server. If not specified, the default user is guest. Example: SERVER1_USER = janedoe EnterthepasswordfortheSERVER<n>_USER. If SERVER<n>_USER is not specified, user guest with no password is assumed. Example: SERVER1_PASSWORD = janedoe123 Enter the version number if using WebLogic 5.1. If omitted, WebLogic Server SPI assumes the version to be 6 or higher. You may specify the major version (5) or the full version (5.1). Example: SERVER1_VERSION = 5 Enter the name of the Windows system where Performance Manager (for graphing) is installed. Example: GRAPH_SERVER = graphserv 2-14

39 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI MAX_ERROR_LOG_SIZE UDM_DEFINITIONS_FILE SERVER<n>_ADMIN_HOST SERVER<n>_ADMIN_PORT The following entries are applicable only when SERVER<n>_VERSION is 5 or 5.1 SERVER<n>_LOGFILE SERVER<n>_CLUSTER Enter the maximum number of MB allowed for the error logfile. When the error logfile reaches the maximum limit, it is renamed as a backup file and logging resumes. When a new backup file replaces an old backup file, the old backup is deleted. NOTE: The default is 10MB Example: MAX_ERROR_LOG_SIZE = 20 If you have user-defined metrics, enter the fully qualified path name to the metric definitions XML document. Enter the location of the WebLogic administration server for this server. Must be included in order for the WebLogic Start/Stop applications to work. Example: SERVER1_ADMIN_HOST=localhost Enter the port of the WebLogic administration server for this server. Must be included in order for the WebLogic Start/Stop applications to work Example: SERVER1_ADMIN_PORT=7005 Enter the fully qualified path of the WebLogic Server log file. If not specified, the default value is <wl_home>/<server<n>_name>/weblogic.log. Enter the name of the cluster to which this WebLogic Server belongs if WebLogic clustering is implemented on this node. Example: SERVER1_CLUSTER=mycluster 2-15

40 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 8: DISTRIBUTE WLS-SPI TEMPLATES In the last task you deploy templates to the managed nodes. 1. Open the Node Bank window and from the Actions menu select Agents Install/Update SW & Config. 2. In the Target Nodes section select the Nodes in List Requiring Update radio button. 3. In the Install/Update Software and Configuration window check the Templates check box. 4. Select Force Update;thenclickOK. The following message is displayed in the Message Browser: The following configuration information was successfully distributed: Templates The WLS-SPI templates are now distributed to the selected node group. WLS-SPI monitors can now begin running according to their specific collection interval. NOTE If you use HP OpenView Reporter, please see the Chapter 4 for information on integrating WLS-SPI with Reporter for generating WebLogic Server reports that show more consolidated information. 2-16

41 Chapter 2: Installing & Configuring the WebLogic Server SPI Check the Installed WebLogic Server SPI Nodes for License Count ChecktheInstalledWebLogicServerSPI Nodes for License Count You can use an OVO reporting utility to check the number of templates you have installed on your managed nodes. In reviewing the number of templates per managed node, you can see if you have consistently installed templates across your managed systems. In addition, by running this report, you can also ensure that the number of licenses you have purchased is in compliance with the report results. To run the report: 1. At the OVO console select the node or node group that you want to check. 2. From the Actions menu select Utilities Reports In the Reports window among the reports listed select WLSSPI License Check. 4. Select an output destination and click OK. 2-17

42 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Remove WLS-SPI How to Remove WLS-SPI The complete removal of the WebLogic SPI installation deletes all WLS-SPI program components as well as the WLS-SPI templates. If you have customized templates (copies of WLS-SPI default templates) residing in other OVO template groups, you should remove them as well. If you are upgrading WLS-SPI, complete only the first section Removing WLS-SPI software from the Management Server. TASK 1: REMOVE WLS-SPI SOFTWARE FROM THE MANAGEMENT SERVER 1. Open a terminal window and log on as root. 2. In the terminal window run swremove by entering: /usr/sbin/swremove WLSSPI 3. To ensure removal of all WLS-SPI files from the management server, enter: ll -R /var/opt/ov/share/databases/opc/mgd_node/customer Delete any file in any directory below var/opt/ov/share/databases/opc/mgd_node/customer that begins with wasspi. NOTE If you are upgrading WLS-SPI, STOP HERE! The swremove command removes the files from the file system only. The WLS-SPI templates are still in the OVO data repository and must be deleted manually. First, however, they (and the WLS-SPI software) must be de-assigned from the managed nodes. TASK 2: REMOVE WLS-SPI SOFTWARE FROM NODE GROUPS AND MANAGED NODES Before beginning the procedure below, de-assign the WLS-SPI template groups that you have deployed from the node groups. 1. Open the Node Bank and from the Actions menu select Agents Assign 2-18

43 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Remove WLS-SPI Templates. 2. In the window that opens select WebLogic 5.x, WebLogic 6.0, or WebLogic 6.1 template groups. 3. Click Remove Selected and click OK. 4. Return to the Node Bank window and select the targeted node, or open the Node Group window and select the targeted node group. 5. In the Node Bank window from the Action menu select Install/Update SW & Config. 6. Check the following check boxes: " Templates " Actions " Monitors " Commands 7. Select the Nodes in List option button. 8. Select the Force Update option button. 9. Click OK to remove the Templates, Actions, Commands and Monitors from the managed node(s). The following message is displayed in the Message Browser: The following configuration information was successfully removed: Templates Actions Commands Monitors TASK 3: DELETE WLS-SPI TEMPLATES The SPI for WebLogic Server template groups that you need to delete are: WebLogic 5.1, WebLogic 6.0, or WebLogic 6.1. Start from the lowest level individual templates within the group and work your way up to the SPI for WEbLogic Server group at the top. 2-19

44 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Remove WLS-SPI 1. Open the Message Source Templates window and select the SPI for WebLogic Server template group 2. Double-click the WLS-SPI group below it (WLS-6.0, 6.1, or 5.1) until you reach the lowest level displaying the individual templates. 3. Use SHIFT+Click to select all templates; then click the Delete from All... button, and select YES in response to the message: Do you really want to delete the template(s)? 4. Go up a level, then double-click the next group. Continue with this same method until you have deleted all WLS-SPI individual and group templates from the Message Source Template window. TASK 4: DELETE WLS-SPI APPLICATIONS Unlike templates, applications can all be removed in a single step. 1. Open the Application Bank. 2. Right-click the WLSSPI application group (and any applications they contain) and from the Edit menu select Delete. 3. Click Yes in response to the following message: Do you really want to delete the application group? 4. Complete the process by deleting the WebLogic SPI message groups (User Bank Responsibilities...window) and WebLogic SPI node groups (Node Bank window). 2-20

45 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Remove WLS-SPI Deleting the WLSSPI Application Groups TASK 5: FINISH UP DELETE THE WLS-SPI MESSAGE AND NODE GROUPS; REMOVE WLS-SPI DIRECTORY 1. From the Window menu select Message Group Bank. 2-21

46 Chapter 2: Installing & Configuring the WebLogic Server SPI How to Remove WLS-SPI 2. In the Message Group Bank window right-click the WLSSPI group and select Delete. 3. Repeat for the WebLogic group. 4. From the Window menu select Node Group Bank. 5. In the Node Group Bank window right-click the WLSSPI group and select Delete. 6. Repeat with the WebLogic Group. 7. From a command line remove the directory by entering: rm /var/opt/ov/wasspi/wls. 2-22

47 Using and Customizing the WebLogic Server SPI 3

48 Chapter 3: Using and Customizing the WebLogic Server SPI Introduction Introduction Like all OpenView plug-ins, the SMART Plug-In for WebLogic Server (WLS-SPI) is easy to use. You should have installed the software, configured the WebLogic Server SPI connections, and deployed the templates. In the OVO message browser, some messages may be appearing regarding the performance of WebLogic Server. As you become familiar with the WebLogic Server SPI, you can determine which templates are most useful to you and which you might want to change. This chapter will assist you by providing further detail on the templates and how to make those changes. In addition, the chapter will also provide information on using the WLS-SPI with HP OpenView Reporter. In general the following topics are covered:! Using the WebLogic Server SPI Templates! BasicTemplateCustomizations! Advanced Template Customizations! Reinstalling WLS-SPI Templates! Using Templates/Applications to Generate Reports 3-2

49 Chapter 3: Using and Customizing the WebLogic Server SPI Using WebLogic Server SPI Templates Using WebLogic Server SPI Templates You can customize WebLogic Server SPI templates, although they work without any modifications. To help you in understanding how you might customize the WLS-SPI templates, the following sections cover the OpenView Operations templates in general and WebLogic Server SPI template groups in particular. WebLogic Server SPI Template Groups WLS-SPI template groups provide a means of organizing various OVO templates. The two primary WLS-SPI template groups (6.0 and 6.1). These groups contain metric and logfile templates as follows: " Metric (monitor) templates: generate messages according to threshold settings monitoring WebLogic availability and performance metrics grouped according to collection intervals. The metrics group contains a list of monitor templates that fall into two categories according to their function. Monitor templates pertain to individual metrics. Collector templates pertain to all metrics scheduled to be collected in the specified collection interval. 3-3

50 Chapter 3: Using and Customizing the WebLogic Server SPI Using WebLogic Server SPI Templates " Logfile templates: generate messages according to logfile and error text detected in both the WebLogic Server logfiles and in the WLS-SPI logfiles. The WLSSPI-Messages template is used as a means of intercepting WLS-SPI message for the OVO message browser. OVO Template Types and WLS-SPI Monitor templates define how data is collected for the individual metric and set a threshold value that when exceeded generates alerts/messages in the Message Browser. You can change the threshold within a monitor template by highlighting the template and clicking the Conditions...button. Then double-click one of the conditions shown. Incoming values for metric WLSSPI are compared against its monitor template settings. In the illustration below, the default threshold is set at 10. Collector templates define all metrics for the WebLogic Server application that are scheduled for collection at the specified interval. Though still identified as a monitor in the OVO lists of templates, you will notice that these templates have names different from the individual metric monitor templates. Within the name of each collector template is its collection interval; for example 3-4

51 Chapter 3: Using and Customizing the WebLogic Server SPI Using WebLogic Server SPI Templates WLSSPI-60-1h. When you open any collector template, you see all metrics (by number) collected within the interval following the -m option of the collector/analyzer command wasspi_wls_ca. The illustration shows the Monitor Program or MIB ID text box, which contains the collector/analyzer command (wasspi_wls_ca), followed by the collection parameter and collection name (- c wlsspi-60-1h), followed by the metric parameter and each metric (- m 2, ). 3-5

52 Chapter 3: Using and Customizing the WebLogic Server SPI Basic Template Customizations Basic Template Customizations After you begin using the WLS-SPI you may decide that specific WLS-SPI templates need some modification. Descriptions contained in the previous section of metric monitor templates (rules for interpreting metric data; for example, thresholds,) and collector templates (rules for the scheduled metric collection) show you where to go to make the various changes. For example, to change a threshold, you would open a metric monitor template. To schedule or delete a metric from data collection, you open the collector template. Those kinds of basic customizations are covered in this section. NOTE In most cases, it is advisable to make copies of the original templates so that the default templates remain intact. Modifying Monitor Templates Many metric attributes can be easily modified for all monitored instances of WebLogic Server by following these steps. 1. Select the Message Source Templates window. 2. Open the template group containing the metric to modify. 3. Double-click the desired metric to open the Message and Suppress Conditions window. 4. Double-click the desired condition to modify (there is usually only one). 3-6

53 Chapter 3: Using and Customizing the WebLogic Server SPI Basic Template Customizations The Message and Suppress Conditions Window The Condition window is displayed. The following attributes can be easily modified: " Threshold. Enter a value for the metric data that when exceeded would signify a problem either about to occur or already occurring. " Duration. The length of time that the incoming data values for a metric can exceed the established threshold before an alarm is generated. " Severity. Click the Severity button and select the desired severity setting. 3-7

54 Chapter 3: Using and Customizing the WebLogic Server SPI Basic Template Customizations " Message Text. Be careful not to modify any of the parameters surrounded by <> brackets, beginning with $ in a message. " Actions. This field provides the ability to generate Performance Manager graphs or reports, or to add custom programs. The reports or graphs are accessible to the user from: Automatic action. The automatic action (delivered with the SPI) generates a snapshot report that show the data values at the time the action was triggered from an exceeded threshold. You can view the report in the message Annotations. Operator initiated action. The operator action delivered with the SPI provides that within a message s details window you can press the PerformActionbuttontoviewagraph of the metric whose exceeded threshold generated the message along with other related metric values. The Condition window, showing a threshold setting of 10 for WLSSPI The incoming values for this metric show the total number of times per minute clients must wait for an available (Enterprise Java) bean; a value of more than 10 would start to impact the server response time the client experiences, generating a Warning message. An alarm can be generated once or multiple times, depending on its setting in the Modify Threshold Monitor window, which shows: 3-8

55 Chapter 3: Using and Customizing the WebLogic Server SPI Basic Template Customizations To change the Alarm Generation Type, modify the settings below, completing the steps that follow. " Reset: Alarms are generated once when the threshold value is exceeded. At the same time a reset threshold value is activated. Only when the reset threshold value is exceeded, does the original threshold value become active again. Then when the threshold value is again exceeded, another alarm is generated and the process starts all over again. " Without Reset. Alarms are generated once when the monitoring threshold value is exceeded. Alarms reset automatically when metric values are no longer in violation of the thresholds and are generated again when the threshold is exceeded. " Continuously. Messages are sent/alerts generated each time the metric values are collected and the threshold is exceeded. The Modify Threshold Monitor Window 1. Open the Message Source Templates window. 3-9

56 Chapter 3: Using and Customizing the WebLogic Server SPI Basic Template Customizations 2. Double-click the template group that contains the monitor template (metric) you want to modify and select the template. 3. Click the Modify button. 3-10

57 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Advanced Template Customizations The template changes suggested here range from making copies of default template groups in order to customize a few settings, to deleting whole groups of metrics within a template s command line. This section is considered advanced because all changes described here, whether simple or complex, require some advanced knowledge of the WLS-SPI metrics. Choosing Metrics To Monitor As a start, determine which metrics you want to change and what templates within the group you want to use. Then proceed as follows: 1. Open the Message Source Template window. 2. Highlight the group you want to use and select the Copy... button. 3. Rename and save the group. 4. Likewise, within the renamed template group, copy each original template and rename it. 5. Delete the originals. 6. Alter the renamed templates within the group as necessary. 3-11

58 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Creating a new template group allows you to keep custom templates separate from the original default templates, which you copy and place within the new group. Using the WLS-SPI Collector/Analyzer Command with Parameters The wasspi_wls_ca command is used in every collector template, named according to its collection interval. You can view the default command line parameters within each collector template in the Monitor Program or MIB ID text box in OVO. 3-12

59 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations USING THE WEBLOGIC SERVER COMMAND PARAMETERS WLS-SPI data collections are started with the wasspi_wls_ca command, to which you can add other parameters, as identified in the following table. Parameter Function Syntax with Example -c (collector) Specifies collector template name. (required) -m (metric) Specifies the metric numbers or number ranges on which to collect data. -t (tag) Allows you to create a new template group by adding a prefix to an existing collector template along with the metric number(s). -i (include) Allows you to list specific servers to monitor. This option may not be used with -e option. -e (exclude) Allows you to exclude specific servers; may not be used with -i option. -c <collector_template_name> Note: Must match the collector template name in which it appears. Example: -c WLSSPI-05min -m <metric_number,metric_number_range> Example: -m 1,3-5,9-11,15 wasspi_wls_ca <prefix>-<collector _template> -m <metric_number> -t <prefix>- Example: wasspi_wls_ca -c DEV-WLSSPI-61-1h -m t DEV- -i <server_name> Example: -i server1,server3 -e <server_name> Example: -e server1,server3 3-13

60 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Parameter Function Syntax with Example -x Allows you to specify a property/value as follows: alarm: whenoff, overrides any alarming condition as set up in the metric monitor template. print:whenon,printsthe metric name, instance name, and metric value to STDOUT in addition to any configured alarming or logging. log: whenoff,prevents graphing or reporting functions. -x <property>=<property_value> -x alarm=off -x print=on -x log=off Syntax Examples: " To specify metrics to collect: wasspi_wls_ca -c WLSSPI-61-15min -m 10-14,25,26 wasspi_wls_ca -c <monitor_template_name> -m <metric_number_range>, <metric_number> " To differentiate server instances: wasspi_wls_ca -c STAGE-WLSSPI-61-05min -m 245,246,260 -i server_1,server_2 -t STAGE_ (Inserting server_1 and server_2 in the Monitor Program or MIB ID text box of the collector template results in collecting data for the specified metrics from these servers only). 3-14

61 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Changing the Collection Interval for All Scheduled Metrics To change the metric collection interval, simply change the Polling Interval in the appropriate collector template. For example, to change the collection of default metrics from 5 minutes to 10 minutes for the WebLogic 6.0 template group, follow these steps: 1. Select the Message Source Templates window. 2. Select the template group SPI for WebLogic Server and open WebLogic 6.1 WLS-6.1-Metrics. 3. Select the collector template WLSSPI-61-05min. 4. Click the Modify... button. and change the Monitor Name to WLSSPI-61-10min. 5. Change the Polling Interval from 5m to 10m. 6. Modify the command line -c parameter to reflect the new template name (WLSSPI-WLS61-10min) as follows: wasspi_wls_ca -c WLSSPI-WLS61-10min Distribute the new templates (described in Chapter 2, Task 8: Distribute WLS-SPI Templates, page 2-16). 3-15

62 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Changing the Collection Interval for Selected Metrics To change the collection interval for selected metrics, copy the appropriate collector template and rename with a name reflecting the new interval, deleting all but the metrics you are changing. Set the new interval. Edit the original template to remove the changing metrics. For example, to change the collection interval to 10 minutes for metrics 70-77, you would follow these steps: Deleting 10-Minute Metrics from the 5-Minute Template 1. Open the Message Source Templates window. 2. Select the template group SPI for WebLogic Server and open WebLogic 6.1 WLS-6.1-Metrics. 3. Select the collector template WLSSPI-61-05min. 4. Click the Copy... button and change monitor name to WLSSPI-61-10min. 5. In the Monitor Program or MIB ID text box, delete all metrics after the -m except Change the Polling Interval to 10m. 3-16

63 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations 7. Change the entry following -c to WLSSPI-61-10min 8. Click the OK button. 9. Select the WLSSPI-61-5min template. 10. Delete from the Monitor Program or MIB ID text box. 11. Re-distribute the modified templates as described in Chapter 2, Task 8: Distribute WLS-SPI Templates, page

64 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Customize the Threshold for Different Servers Customize the threshold as needed. For example, you may want to set the threshold for SERVER_1 for metric 0012 to 20 and leave it at 10 for all other servers. To do so, copy the existing condition and modify it to serve as the exception. Follow these steps: 1. Double-click to open the metric to customize (for example, WLSSPI-0012). The Message and Suppress Conditions window is displayed. 2. Select the desired condition and press the Copy... button to make a copy of the condition. 3. Name the condition WLSSPI In the Object Pattern field, enter the desired characters to use for pattern matching (in this example SERVER_1). For example, to match on all servers with a specific character string in the name, enter the string in the Object Pattern field. (see the OVO online Help or the OVO Administrators Task Guide for pattern matching syntax). 5. Click the Test Pattern Matching button to test the pattern and verify pattern matching (you must set up a match file first). 3-18

65 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations 6. Change the value in the Threshold field from 10 to 20. Creating Custom, Tagged Templates Another advanced customization option is to use the tag option (-t on the command line), which allows the collector/analyzer to recognize customized templates that have a tag attached to the name. This option provides you with the flexibility of using more than a single set of templates to define conditions pertaining to specific installations of WebLogic Server. When multiple nodes are managed by a number of groups, this option allows you to create specially tagged templates that are obviously separate from your original setup. In such a case, you would make copies of the templates, rename them with the tag and re-work the collector template to pick up the tagged names, then assign them to the various groups. For example, you might create a group of templates and change each template name to include CLIENT01 in it. A metric monitor template might be named CLIENT01-WLSSPI_0012 (retaining the metric number, which must be used). The collector template name would be named FIRST_CLIENT-61_05min.You could then set up another group for SECOND_CLIENT and change all those templates to include the SECOND_CLIENT in the name. To create the new template group: 1. Copy the original template group: In the Message Source Templates window select the group and click the Copy... button. 2. Name the new group according to how you plan to identify the new monitor and collector templates; for example, if you are including FIRST_CLIENT in the template names, include that within the new template group name. 3. In the Message Source Template window expand the new template group to show all templates and select each template you plan to use, click the Copy... button, and rename it according to your naming scheme. " The names you give the new metric monitor templates in the group 3-19

66 Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations would contain the new name followed by the original metric number. For example, a copy of WLSSPI-0001 could be called CLIENT01-WLSSPI_0001. " The name you give the new collector monitor template would also contain the identifying name. You would also modify the scheduled collection for the new group by inserting the -t property on the command line; for example: wasspi_wls_ca -c CLIENT01-WLSSPI61-15min -m 16 -t CLIENT01- In this case the copied collector template has been renamed: FIRST_CLIENT-61-15min 4. Delete all original templates from the new group. 3-20

67 Chapter 3: Using and Customizing the WebLogic Server SPI Re-installing the WLS-SPI Templates Re-installing the WLS-SPI Templates When WLS-SPI templates are installed in OVO, the commands shown below automatically uploads them when swinstall is run. Any customized template settings you may have done for the previous installation are overwritten. To restore the default SPI for WebLogic Server template group you had originally installed, delete all current templates first, then run the command: Scripts Run by swinstall OVO >6.x Scripts /opt/ov/bin/opc/opccfgupld -silent -replace -subentity /var/opt/ov/share/tmp/opc_appl/wassspi/wls_set 5.x /opt/ov/bin/opc/opccfgupld -silent -replace -subentity -index /var/opt/ov/share/tmp/opc_appl/wassspi/wls/wls_ito5_set/ C/wls_set.idx /var/opt/ov/share/tmp/opc_appl/wasspi/wls/wls_ito5_set *Alternatively, you can use the -verbose option instead of the -silent option. 3-21

68 Chapter 3: Using and Customizing the WebLogic Server SPI Using Templates/Applications to View Annotation Reports and Graphs Using Templates/Applications to View Annotation Reports and Graphs Some templates have actions defined with theshold violations or error conditions that automatically cause reports to appear in the message Annotations. These reports are snapshots of data values collected form the server around the time that the alarm occurred. Other templates have operator actions associated with them that allow you to generate a graph. NOTE The reports discussed in this section should not be confused with those generated by OpenView Reporter, which show more consolidated, historical data generated as Web pages in management-ready presentation format. You can access the data as follows: " To view the Message Details. Double-click a message in the OVO message browser, or just select the message and click Annotations. You can easily access Annotations by selecting the Annotations button. Reports are available there, showing data values on a single server. " To view reports. Open both the Node Bank and Application Bank windows. Continue to open application windows WLSSPI WLSSPI Admin Reports. Select a node and drag it onto the WLSSPI metric report you need. These reports show all server data on a node. " To view graphs. Open both the Node Bank and Application Bank windows. Continue to open application windows WLSSPI WLSSPI Admin. Drag a node onto the View Graphs application to launch you Web browser, which displays the graphing feature available in HP OpenView Performance Manager (which requires a separate purchase). 3-22

69 Chapter 3: Using and Customizing the WebLogic Server SPI Using Templates/Applications to View Annotation Reports and Graphs Checking for indications of Automatic Reports in the OVO Message Browser AUTOMATIC ACTION REPORTS Many metrics generate Automatic Action Reports. These reports are generated as soon as an alarm is triggered in OVO. HOW YOU KNOW A REPORT HAS BEEN GENERATED When an Automatic Action Report is executed from OVO, the server is queried for additional data. If your message browsser is set to display the SUIAONE column, you will see an S under the A column (see illustration), which indicates that a generated report is available in the Annotations area of the Message Details. HOW TO VIEW THE REPORT To view the report, click the Annotations... button in the Message Browser. Column descriptions provide further clarification. 3-23

70 Chapter 3: Using and Customizing the WebLogic Server SPI Using Templates/Applications to View Annotation Reports and Graphs HOW AUTOMATICALLY GENERATED AND MANUALLY GENERATED REPORTS DIFFER Automatic Action reports show the state of the system moments after the alarm occurred. You can manually generate a report that shows the current state of the system by dragging the managed node from the Node Bank onto the desired report in the Application Bank (see the next section for details on Application Bank reports). Application Bank Reports use these applications to manually generate a report similar to an Automatic Action report. These reports differ by showing data on ALL WebLogic Server instances on the managed node. The Automatic Action report shows data on the single WebLogic Server instance with the exceeded threshold 3-24

71 Chapter 3: Using and Customizing the WebLogic Server SPI Using Templates/Applications to View Annotation Reports and Graphs APPLICATION BANK REPORTS Application Bank reports run for all WebLogic Server instances configured on the managed node, in contrast to Automatic Action Reports which are generated for a single WebLogic Server instance. The reports generated from the Application Bank reflect the current state of WebLogic Server on the managed node. To generate a report in OVO, simply drag the managed node from the Node Bank window to the desired report in the Application Bank window. The report below appears in the Annotations area of the message details. 3-25

72 Chapter 3: Using and Customizing the WebLogic Server SPI Sample Report Report on metric B-011 Sample Report The following example shows the format of a WLS-SPI report. This report is automatically generated (automatic action report). 3-26

73 Using HP OpenView Reporting and Graphing Features with WLS-SPI 4

74 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Introduction Introduction HP OpenView Reporter (which you can separately purchase) integrates fully with the SMART Plug-In for WebLogic Server. Reporter produces management-ready, Web page reports, showing historical and trending information. The WebLogic Serve SPI working in conjunction with Reporter produces a variety of reports, showing consolidated information on WebLogic Server. Another OpenView product, Performance Manager 4.0, provides a graphing capability. With this added capability you can use the WLSSPI Admin View Graphs application to generate graphs of current conditions. In addition, Performance Manager also works to generate graphs associated with Operator-initiated actions (wherever included in a WLS-SPI template). Both Reporter and Performance Manager run on Windows, but because their reports and graphs are generated as Web pages, you can configure your UNIX system to remotely display them. 4-2

75 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WebLogic Server SPI with Reporter to Generate Reports This chapter provides information on how to fully integrate WLS-SPI with HP OpenView Reporter and Performance Manager. After you complete the instructions in this chapter, every night Reporter generates reports that show the performance and availability of WebLogic Server on configured managed nodes. You will also be able to take advantage of the built-in graphing capabilities of the WLS-SPI, coupled with Performance Manager. Integrating WebLogic Server SPI with Reporter to Generate Reports Prerequisite: Installation of the WebLogic Server SPI according to the instructions in Chapter 2, which includes software deployment, server connection configuration, and assignment/distribution of templates to targeted nodes. The WLS-SPI report package must be installed on the Windows system running Reporter. You can install it directly from the CD as explained below. 1. On the Windows client system, insert the CD in the CDROM drive and double-click: \reporter\wlsspi-reporter.exe 2. Follow the instructions as they appear. NOTE During the installation an error message may appear that indicates the installer has detected an older version of the installer on your system. The note is for information purposes only and can safely be ignored. 3. Check the Reporter status pane (see the illustration that follows) to note changes to the Reporter configuration. 4-3

76 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WebLogic Server SPI with Reporter to Generate Reports The status pane (at the bottom of the Reporter window) shows you information on the programs running and any errors occurring. You can check the status pane to see that Reporter has been updated with the WLS-SPI reports. You can find instructions in the Reporter Help for assigning WLS-SPI reports to the targeted nodes. To access Help, select Reports or Discovered Systems in the left panel of the Reporter main window and right-click it. Select Report Help or Discovered Systems Help from the submenu that appears. See the topic To assign a report definition to a Discovered Systems Group. 4-4

77 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WebLogic Server SPI with Reporter to Generate Reports 4. Add group and single system reports by assigning reports as desired. (See the Reporter Help and the online Concepts Guide for complete information.) NOTE Group and single system WLS-SPI reports require that you identify systems by their full name; for example, abc.xyz.com is acceptable while abc is not. WebLogic Server SPI Reports The reports available through the integration of HP OpenView Reporter and WLS-SPI show consolidated data on server performance and availability on all WebLogic Server systems. In addition, other reports show data for single systems. These reports are available the day following your installation of the WebLogic Server SPI report package on the Reporter Windows system. (Please refer to page 4-3 if you have not yet completed the report package installation.) The three tables that follow show all pre-defined reports. Performance Report Title Description Metric TOP 20 Queue Throughput Shows the average throughput for the top execute queues of all servers. TOP 20 Servlet Average Execution Times TOP 20 Servlet Request Rates Execute Queue Thread Utilization TOP 20 Average Transaction Throughput TOP 20 EJB Free Pool Wait Rate Shows the average execution time for the top 20 requested servlets for all servers. Shows the total servlet request rate being received by the top 20 servers. Shows the execute queue`s thread utilization as a percent for the top 20 execute queues of all servers. Shows the average transaction throughput for the top 20 servers. Shows the number of times per minute that a request had to wait for an EJB to become available for the top 20 servers

78 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WebLogic Server SPI with Reporter to Generate Reports Report Title Description Metric TOP 20 EJB Timeout Rate TOP 20 EJB Transaction Throughput Shows the number of times per minute that a request timed out while waiting for an EJB to become available for the top 20 servers. Shows the average EJB transaction throughput for the top 20 servers Availability Report Title Description Metric Server Availability Server Availability Details Single System Reports Contains a daily histogram showing the percentages of uptime, downtime for all servers. Top 20 execute queues of all servers. Contains spectrum graphs showing minutes of uptime by day and hour for each WebLogic Server. Report Title Description Metric JDBC Throughput And Connection Utilization Throughput And Utilization Of JMS Server By Byte Count Throughput And Utilization Of JMS Server By Message Count Queue Utilization versus Throughput On Server Charts the throughput against the utilization for the JDBC connection pools for each WebLogic server. Charts the throughput against the queue utilization by byte count for destinations on the JMS servers for each WebLogic Server. Charts the throughput against queue utilization by message count on the JMS servers for each WebLogic server. Shows the throughput against the thread utilization for each WebLogic server , , , ,11 4-6

79 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WebLogic Server SPI with Reporter to Generate Reports Report Title Description Metric TOP 20 Servlet Request Rate On Server Transaction Throughput On Server Transaction Rollback Types EJB Transaction Throughput By EJB TOP 20 EJB Transaction Rollback Percent By EJB TOP 20 Stateless EJB Cache Utilization Shows a stacked area chart with the request rate (requests per second) for the top 20 servlets for each day and a table with data of the top 100 servlets for each WebLogic Server. Shows the average transaction throughput for each WebLogic Server by day. Shows the transaction rollbacks by error type for each WebLogic Server. Charts the throughput (transactions per second) for the top 20 EJBs for each WebLogic Server. Charts the transaction rollbacks for the top 20 EJBs for each WebLogic Server. Shows the EJB cache utilization percent for the top 20 EJBs for each WebLogic Server

80 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WLS-SPI with HP OpenView Performance Manager Integrating WLS-SPI with HP OpenView Performance Manager To use Performance Manager, you must separately purchase it, then complete some tasks to configure the Web page display for the OVO console (UNIX system). Some required tasks you have completed already. Specifically, the required tasks are: 1. Set up the browser Web page display on the OVO console (UNIX system) as explained in Chapter 2, Task 2: (optional) Configure the Management Server to Launch your Web Browser, page Configure the location of the graphing system within the WLS-SPI configuration file, also explained in Chapter 2, Task 7: Configure Server Connections and Graphs, page Install the WebLogic Server SPI reporting/graphing package at the Performance Manager Windows system by inserting the CD in the CD-ROM drive and selecting Start Run \<CD-ROM drive>: \Products\ WLSSPI Performance Manager Package\setup.exe and follow the instructions on screen. VIEWING GRAPHS THAT SHOW ALARM CONDITIONS For graphing purposes, the WebLogic Server SPI organizes metrics according to type and includes the following four groupings. When a message is generated for any metric appearing in a table in the section that follows, you can view a chart of its and other metric values. To view a graph associated with an alarm condition (Operator-initiated action has been defined with the WLS-SPI monitor template), complete these steps: 1. In the OVO Message Browser double-click the message. 2. In the Message Details window select the Perform Action button. 4-8

81 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WLS-SPI with HP OpenView Performance Manager The resulting action displays the metric s WLS-SPI graph, which charts its values along with the values of other metrics in the same group. VIEWING GRAPHS THAT SHOW PAST/CURRENT CONDITIONS You can also generate any of the four available graphs manually by using the WLSSPI-Admin application View Graphs. To manually generate a graph: 1. At the OVO console open both the Node Bank and the Application Bank windows. 2. In the Node Bank window select the node for which you want the graph generated. 3. In the Application Bank window double-click WLSSPI and in the next window double-click WLSSPI Admin. 4. Drag and drop the node onto the View Graphs application. WLS-SPI METRICS AVAILABLE FOR GRAPHS The four tables that follow show the graphs available for mapping collected metric values. If you are interested in viewing any one of the metrics included in any of these tables, you can use the View Graphs application to launch the graph, which appears in your Web browser. Server Status (Serverstat); 5, 13, 14, 61, 85, 91 Metric number/name B005_JVMMemUtilPct B013_ SocketTrafficRt B014_AtiveSocketCnt B061_JDBCConPlWtCnt B085_InvLoginAttCnt Metrics Description JVM Utilization Percent Socket Traffic Rate Active Socket Count JDBC Pool Wait Count Invalid Login Atempts Count 4-9

82 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WLS-SPI with HP OpenView Performance Manager B091_TimeSerThruRt Time Services Throughput Rate Enterprise Java Beans (EJB); 25, 26, 35, 36 Metric number/name Metrics Description B025_EJBFreePoolWtRt EJB Free Pool Wait Rate B026_EJBTimeoout Rt EJB Timeout Rate B035_EJB_EJBTranThruRt EJB Transaction Throughput Rate B036_EJBTranRbPct EJB Transaction Rollback Percent Transaction; 70, 71, 72, 73, 74 75, 76, 77 Metric number/name Metrics Description B070_TranAveTime Transaction Average Time B071_TranRollbackPct Transaction Rollback Percent B072_TranResErrRbPct Transaction Resource Error Rollback Percent B073_TranAppErrRbPct Transaction Application Error Rollback Percent B074_TranTimErrRbPct Transaction Timeout Error Rollback Percent B075_TranSysErrRbPct Transaction System Error Rollback Percent B076_TranThruRate Transaction Throughput Rate B077_TranHeurCnt Transaction Heuristic Count Cluster; 80, 81 B080_ClsOutMesFailRt B081_ClsInMesFailRt Cluster Outgoing MessageFailure Rate Cluster Incoming Message Failure Rate 4-10

83 Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WLS-SPI with HP OpenView Performance Manager LAUNCHING THE WEB PAGE DISPLAY WITH AN OPERATOR ACTION THAT GENERATE GRAPHS Performance Manager graphs can be generated from most WLS-SPI alarm messages by pressing Perform Action from the message details (or Properties) or from the Message Browser. The operator action launches your Web browser, which can then display a graph of the metric that generated the message as well as other related metrics. A graph generated from an Operator Action SPECIFYING A DATE RANGE Within the Web page display, you can specify a date range of one day, one week, one month, or one year. Please see the online Help for instructions on changing display settings. 4-11