HP OpenView Operations SMART PLUG-IN FOR WEBLOGIC SERVER User’s Guide B9145-90000 Release A.01.00.
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.
Conventions Boldface Words in boldface type represent user selections, programs, and commands. Capitalization Capitalized first letters represent company or product names. Computer font 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. Italics Words in italics represent variables in syntax statements or words that are emphasized in the text.
Printing History New editions are complete revisions of the manual. The printing dates for each edition are listed below.
Contents Chapter 1: WebLogic Server SPI Concepts ................................. 1-1 Introduction ...........................................................................................1-2 Introducing the SMART Plug-In for WebLogic Server ........................1-3 How the SMART Plug-In for WebLogic Server Works .......................1-4 Components of the SMART Plug-In for WebLogic Server ............. 1-10 Applications ................................................................................
Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI ............................................. 4-1 Introduction ........................................................................................... 4-2 Integrating WebLogic Server SPI with Reporter to Generate Reports . 4-3 WebLogic Server SPI Reports ........................................................... 4-5 Integrating WLS-SPI Performance Manager ........................................
1 WebLogic Server SPI Concepts
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
Chapter 1: WebLogic Server SPI Concepts How the SMART Plug-In for WebLogic Server Works ! Automatic Action Reports: generated automatically by an alarm condition in relation to an individual server instance on a managed node. These reports are available by clicking the Annotations button in the OVO Message Browser.
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.
2 Installing & Configuring the WebLogic Server SPI
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.
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: C
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 FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-HPUX END_BUNDLE BUNDLE SPIWebLogicSOL FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-SOL BUNDLE SPIWebLogicNT* FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-NT* BUNDLE SPIWebLogicAll FILESET WLSSPI.WLSSPI-CORE FILESET WLSSPI.WLSSPI-HPUX FILESET WLSSPI.
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 B ROWSER 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.
Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI TASK 3: ASSIGN O PERATOR 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.
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.
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.
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.
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.
Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI Set configuration for ? [yes] Transferring configuration to followed by: Importing configuration on . 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.
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= vaiable= GROUP { node_name node_name ... } NODE { var=value var=value ...
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.
Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI SERVER_PORT Enter the port the WebLogic server listens on. Example: SERVER1_PORT = 7001 WL_USER 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.
Chapter 2: Installing & Configuring the WebLogic Server SPI How to Install & Configure WLS-SPI MAX_ERROR_LOG_SIZE 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.
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; then click OK.
Chapter 2: Installing & Configuring the WebLogic Server SPI Check the Installed WebLogic Server SPI Nodes for License Count Check the Installed WebLogic Server SPI 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.
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.
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.
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.
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.
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.
3 Using and Customizing the WebLogic Server SPI
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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. -c Note: Must match the collector template name in which it appears.
Chapter 3: Using and Customizing the WebLogic Server SPI Advanced Template Customizations Parameter Function -x -x = Allows you to specify a property/value as follows: alarm: when off, overrides any alarming condition as set up in the metric monitor template. Syntax with Example -x alarm=off print: when on, prints the -x print=on metric name, instance name, and metric value to STDOUT in addition to any configured alarming or logging.
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.
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.
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 70-77 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 2-16.
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).
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.
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.
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.
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.
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.
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.
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.
Chapter 3: Using and Customizing the WebLogic Server SPI Sample Report Sample Report The following example shows the format of a WLS-SPI report. This report is automatically generated (automatic action report).
4 Using HP OpenView Reporting and Graphing Features with WLS-SPI
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.
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.
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.
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.
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 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. 26 TOP 20 EJB Transaction Throughput Shows the average EJB transaction throughput for the top 20 servers.
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 Shows a stacked area chart with the request 242 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. Transaction Throughput On Shows the average transaction throughput Server for each WebLogic Server by day.
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.
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 G RAPHS 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.
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 Metri
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 G ENERATE 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.
Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPI Integrating WLS-SPI with HP OpenView Performance Manager 4 - 12
5 WebLogic Server SPI User Defined Metrics
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Introduction to User Defined Metrics The WebLogic Server SPI can collect data on roughly 55 metrics. However, you can, if you choose, add your own metrics. In defining your own metrics, you can monitor your own applications by registering application MBeans with the WebLogic MBean server and creating user-defined metrics (UDMs) that instruct the SPI to gather data from these MBeans.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics The MetricDefinitions Element Within the WLS-SPI MetricDefinitions.dtd file, the MetricDefinitions element is the top-level element within the document. It contains one collection of metrics, consisting of one or more metric definitions. The Metric Element The Metric element represents one metric.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Attribute Type Required Default Description alarm "yes" "no" no "no" If yes, the metric value will be sent to the agent via opcmon. report "yes" "no" no "no" If yes, the metric value will be logged for reporting. previous "yes" "no" no "yes" If yes, the metric value is saved in a history file so that deltas can be calculated.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics elements. Each Map element specifies one value to be mapped. " The FromVersion and ToVersion elements are used to specify for which versions of WebLogic this MBean element is valid. " The AttributeFilter element provides basic filtering of MBeans based on an MBean attribute.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Attribute Possible Values Required Default Description dataType "numeric" "string" no "numeric" Indicates whether the value returned from the MBean attribute is a string or a numeric value. Map element attributes are described in the following table. Attribute Type Required Default Description from text yes no default The value that is to be mapped.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Attribute Possible Values operator "initialSubString" Required yes Default Description no default Specifies the filter to apply. "initialSubString", "finalSubString", "anySubString", and "match" can be used with MBean attributes that return text values. "finalSubString" "anySubString" "match" "gt" "geq" "gt", "geq", "lt", "leq", "eq" can be used for MBean attributes that return numeric values.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics More than one metric source element (MBean and/or Calculation) may be indicated in a Metric element. Each metric source element is scanned for a FromVersion or ToVersion child element to determine which metric source element to use for the version of the application server being monitored.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Attribute Type Required Default Description update numeric string no "*" Specifies a secondary server version, such as "1" for service pack 1. A "*" indicates that no secondary version is specified. The following examples illustrate the use of the FromVersion and ToVersion elements. Example 1: Metric 10 uses metric "mbean1" in its calculation. This calculated metric applies to all WebLogic Server versions.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Example 2: Using the example above, a decision was made to make metric 10 a per-minute rate instead of a per-second rate as of server version 7.0. The changes that had to be made to the metric definitions are in bold type. Note that the versions supported by the base metrics and calculated metrics are not necessarily in sync. PAGE 95Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics METRIC CALCULATIONS The collector can perform calculations that combine one or more metrics to define a new metric. These calculations are specified in the Metric Definitions XML document using the Formula element as described in the previous section. The result of the calculation is the metric value. See the section “Sample Metric Definitions Document” for examples of calculated metrics.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics " count returns the number of instances of a multi-instance metric. The following example could be used to define a metric that is a rate (number of times per second) for Metric_1. (delta(Metric_1)/interval(Metric_1))*1000 Create User-defined Metrics Now that you have reviewed the structure required for creating UDMs, the section below shows the tasks to complete.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics To add the UDM file name and its location to the WLS-SPI configuration file information: 1. At the OVO console from the Window menu select the Application Bank window. 2. In the Application Bank window double-click the WLSSPI application group and in the next window that appears double-click the WLSSPI Admin group. 3. Right-click the Config WLSSPI application and select Execute. 4.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Create a UDM Template Group To set up monitor and collector templates for UDMs, copy and rename an existing WLS-SPI template group. Then copy and rename every existing template you want to use. Delete the originals from the group. To set up the UDM templates: 1. From the Window menu select the Message Source Templates. 2.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics How to Generate automatic actions (reports): If you have a UDM for which you want an automatic report to be generated when alarm conditions occur, you need to link the condition to the newly created template. For example, to link metric WLSSPI-701 to the new template UDM_0701, you would do the following: 1. Select the newly created template and click the Conditions...
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics Sample Metric Definition Document The following is a sample metric definition document to illustrate how you might create your own user-defined metrics. This sample document also contains examples of calculated metrics.
Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics *:*,Type=JVMRuntime HeapFreeCurrent PAGE 102Chapter 5: WebLogic Server SPI User Defined Metrics Introduction to User Defined Metrics
