HP OpenView Operations SMART PLUG-INFOR EB OGIC ERVER · 2010. 6. 24. · User’s Guide B9145-90000 Release A.01.00.00. ii Legal Notices Hewlett-Packard makes no warranty of any

HP OpenView Operations

SMART PLUG-IN FOR WEBLOGIC SERVER

User’s Guide

B9145-90000Release A.01.00.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 particularpurpose.

Hewlett-Packard Company shall not be liable for errors contained herein or forincidental or consequential damages in connection with the furnishing, performance, oruse of this material.

Hewlett-Packard assumes no responsibility for the use or reliability of its software onequipment that is not furnished by Hewlett-Packard.

This document is protected by copyright. All rights are reserved. No part of thisdocument may be photocopied, reproduced, or translated to another language withoutprior written consent of Hewlett-Packard Company. The information contained in thisdocument is subject to change without notice.

Hewlett-Packard respects all registered trademarks and copyrights.

Microsoft and Windows NT are U.S. registered trademarks of MicrosoftCorporation.

Pentium is a U.S. registered trademark of Intel Corporation.

UNIX is a registered trademark in the United States and other countries, licensedexclusively 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 theyare associated.Hewlett-Packard CompanyOpenView Business Unit8000 Foothills BoulevardRoseville, CA 95747-5726 USA

© Copyright Hewlett-Packard Company, 2001.

ii

Conventions

Boldface Words in boldface type represent user selections, programs, andcommands.

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 appearon your screen, or text you should type on your workstation orterminal.

Italics Words in italics represent variables in syntax statementsor 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

Printing History

New editions are complete revisions of the manual. The printing dates for eachedition are listed below.

Edition 1 November 2001

iv

Contents

Chapter 1: WebLogic Server SPI Concepts ................................. 1-1Introduction ...........................................................................................1-2Introducing the SMART Plug-In for WebLogic Server ........................1-3How the SMART Plug-In for WebLogic Server Works .......................1-4

Components of the SMART Plug-In for WebLogic Server ............. 1-10Applications ...................................................................................... 1-11Templates.......................................................................................... 1-14Reports: from OVO Actions or WLSSPI Applications .................... 1-16

Chapter 2:Installing & Configuring the WebLogic Server SPI . 2-1Introduction ...........................................................................................2-2How to Install & Configure WLS-SPI ..................................................2-3Check the Installed WebLogic Server SPI Nodes for License Count .2-17How to Remove WLS-SPI ..................................................................2-18

Chapter 3: Using and Customizing the WebLogic Server SPI ... 3-1Introduction ...........................................................................................3-2Using WebLogic Server SPI Templates ................................................3-3

WebLogic Server SPI Template Groups ............................................ 3-3OVO Template Types and WLS-SPI ................................................. 3-4

Basic Template Customizations ............................................................3-6Modifying Monitor Templates ........................................................... 3-6

Advanced Template Customizations ...................................................3-11Choosing Metrics To Monitor .......................................................... 3-11Changing the Collection Interval for All Scheduled Metrics ........... 3-15Changing the Collection Interval for Selected Metrics .................... 3-16Customize the Threshold for Different Servers................................ 3-18Creating Custom, Tagged Templates ............................................... 3-19

Re-installing the WLS-SPI Templates ................................................3-21Using Templates/Applications to View Annotation Reports and Graphs ..

3-22Sample Report .....................................................................................3-26

i

Chapter 4: Using HP OpenView Reporting andGraphing Features with WLS-SPI ............................................. 4-1

Introduction ........................................................................................... 4-2Integrating WebLogic Server SPI with Reporter to Generate Reports . 4-3

WebLogic Server SPI Reports ........................................................... 4-5Integrating WLS-SPI Performance Manager ........................................ 4-8

Chapter 5: WebLogic Server SPI User Defined Metrics ............. 5-1Introduction to User Defined Metrics ................................................... 5-2

Metric Definitions Structure .............................................................. 5-2Create User-defined Metrics ............................................................ 5-12Create a UDM Template Group....................................................... 5-14Sample Metric Definition Document ............................................... 5-16

Chapter 6: Troubleshooting and Log File Text ............................ 6-1Error Messages ..................................................................................... 6-2

.......................................................................................................... 6-48WASSPI-226 ................................................................................... 6-49All Other Errors................................................................................ 6-50

Appendix: Directory Locations

ii

1

WebLogic Server SPI Concepts

Chapter 1: WebLogic Server SPI ConceptsIntroduction

Introduction

The SMART Plug-In for WebLogic Server is a full-featured SPI that allows youto manage WebLogic servers from an HP OpenView Operations console. Thischapter offers a basic introduction to its concepts. It is suggested you read thechapter before installing and configuring the SPI in Chapter 2. The followingtopics 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

Chapter 1: WebLogic Server SPI ConceptsIntroducing the SMART Plug-In for WebLogic Server

Introducing the SMART Plug-In forWebLogic Server

The SMART Plug-In for WebLogic Server (WLS-SPI) adds monitoringcapabilities otherwise unavailable to HP OpenView Operations (OVO).

SMART Plug-In integration uses: Used in conjunction with OVO, theWLS-SPI offers centralized tools that help you monitor and manage systemsusing WebLogic Server. From the OVO console, an operator can apply the samefamiliar HP OpenView performance and problem managing processes tomonitor a system using WebLogic Server. WLS-SPI metrics are automaticallysent 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, youcan find dozens of key server-related metrics. Among them are metrics thatcover 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 thosemetrics that are most crucial to the successful operation of WebLogic Server bymodifying WLS-SPI templates. The templates contain settings that allowincoming data to be measured against predefined rules that generate usefulinformation in the form of messages. These messages with severity-levelcolor-coding can be reviewed for problem analysis and resolution. Correctiveactions that are pre-defined for specific events or threshold violations can beautomatically triggered or operator-initiated.

1 - 3

Chapter 1: WebLogic Server SPI ConceptsHow the SMART Plug-In for WebLogic Server Works

How the SMART Plug-In for WebLogicServer Works

WebLogic Server SPI (WLS-SPI) messaging, reporting, and action-executingcapabilities are based on the OVO concept of templates. The settings withinthese templates define various conditions within the WebLogic Server. Once inuse, WLS-SPI templates allow information to be sent back to the OpenViewOperations management server to help you proactively address potential orexisting problems and avoid serious disruptions to Web transaction processing.

HOW WLS-SPI COLLECTS AND INTERPRETSSERVER 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 thedeployed templates. Those templates, described in a later section, defineconditions that can occur within the WebLogic Server, such as queue throughputrates, cache use percentages, timeout rates, average transaction times, etc.Default thresholds, set within the templates, monitor these conditions and triggermessages to the console when a threshold has been exceeded.

1 - 4


HOW WLS-SPI DISPLAYS THE INFORMATION

Messages in the Message Browser: Comparing the values gathered forWebLogic Server performance/availability against the monitor template settingsrelating to those specific areas, OVO agent software forwards the appropriatemessages to the OVO console. These messages are displayed with color-codedseverity levels in the OVO Message Browser.

1 - 5


Instruction Text: Messages generated by WLS-SPI programs containinstruction text to help diagnose and remedy problems. Corrective actions thatare preassigned to events can be triggered automatically or manually by anoperator.

You can usually find instruction text in the message details; this same text is also available in theHP OpenView SMART Plug-In for WebLogic Server SPI Reference manual metric definition.

ASCII-Text Reports: In addition to the instruction text mentioned above, somemessages cause automatic action reports to be generated. These reports showconditions of specific WebLogic Server instance. When a report is available, likethe instruction text, you can find it within the Message Details, specifically in theAnnotations area.

1 - 6


GENERATING REPORTS USING HP OPENVIEW REPORTER

The WebLogic Server-SPI also integrates with HP OpenView Reporter toprovide you with 20 management-ready, Web-based reports. WLS-SPI includesthe templates for generating these reports within its Report package, which youcan install on the Reporter Windows system. After you have installed the productand completed some configuration steps (all detailed in Chapter 2), you canexpect to see new reports of summarized, consolidated data generated nightlythat 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 generatedreports.

1 - 7


GRAPHING DATA WITH OPENVIEW PERFORMANCEMANAGER

Another OpenView product, Performance Manager 4.0 (OVPM), integrateswith WLS-SPI to enable use of the WLSSPI Admin→View Graphs applicationto generate WLS-SPI graphs. OVPM also allows you to view WLS-SPI grapheddata from most WLS-SPI alarm messages by pressing the Perform Actionbutton. You see this button in both the Message Browser and in the messagedetails (access details by either double-clicking the message or selecting theDetails... button) in the Message Browser. The action launches your Webbrowser, where you can choose a graph that shows values for the metric thatgenerated the message as well as other related metrics.

Metrics collected by WLS-SPI can be graphed. The values can then be viewed fortrend analysis

1 - 8


CHANGES YOU CAN MAKE

You can use WLS-SPI templates with no customization, or you can change themas you find necessary. Minor modifications and major customizations are listedhere:

Modification of Default Templates: Within a template you can change thedefault settings for (1) collection interval, (2) threshold, (3) message text,(4) duration (5) severity level of the condition, (6) actions assigned to thecondition (operator-initiated or automatic).

Creation of Custom Template Groups: Create custom template groups, usingdefault templates as a starting point. To do this, see Chapter 3.

Custom Metrics: The ability to define your own metrics or user-definablemetrics (UDMs) is a powerful feature that you can use to expand the monitoringcapabilities of WLS-SPI. Instructions are available in Chapter 5.

1 - 9


Components of the SMART Plug-In forWebLogic Server

The WebLogic Server SMART Plug-In components include applications andtemplates that allow you to configure and receive data in the form of messagesand short reports. These messages (available in the Message Browser) and shortreports (through applications or message details) provide you with informationabout conditions present in the server(s) running on specific managed nodes.

WLS-SPI configuration applications let you configure the management server’sconnection to named server instances on specific managed nodes. After you haveconfigured the connection, you can assign templates to the nodes. With OVOagent software running on the manage nodes, you can use WLS-SPI reportingapplications to generate reports. In addition, you can generate graphs that showWLS-SPI data.

Chapter 2 details how to install the components and use them to configure serverinstances on the managed nodes and then deploy the template groups. Thesections that follow here give you brief descriptions of all components.

1 - 10


Applications

The WebLogic Server SPI applications include configuration, troubleshooting,and report-generating utilities. In the OVO Application Bank window theWebLogic Server SPI applications are divided into two groups.

WebLogic Server SPI applications. The applications in the WLSSPI groupallow you to configure the connection to the server you are monitoring and toturn collections and tracing on and off. The group contains subgroups andapplications that are nearly duplicate for UNIX and NT nodes.

NOTE Any group name that includes “NT” within it indicates its applications are forNT nodes. No “NT” within the group name means those applications are forUNIX nodes.

! WLSSPI Admin. This group contains configuration and troubleshootingapplications requiring “root” permission, so it is recommended the groupbe assigned to the OVO administrator.

WLSSPI-Admin applications allow you configure, control, and troubleshoot the WLS-SPI.

1 - 11


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 syntaxexamples for configuring the connection to the WebLogic Server on amanaged node. (After you save the file, the examples are deleted.) Thisfile contains information about the WebLogic servers being monitored,such as the server name and port number, as well as other informationsuch as the location of a user-defined metrics definition file, ifapplicable.

" View Error File. Allows user to view the entire WebLogic Server SPIerror log.

" Start Monitoring. Turns collection off for the entire WebLogic ServerSPI or for a selected server on the managed node.

" Stop Monitoring. Turns collection on for the entire WebLogic ServerSPI or for a selected server on the managed node.

" Verify. Verifies that the WebLogic Server SPI is properly installed onthe server or managed node.

" View Graphs. For users of OpenView Performance Manager, you canconfigure your Web browser (see Chapter 2 and Chapter 4) to displayWLS-SPI graphs. The ovweb program launches your browser, whichallows you to graph WLS-SPI metric data.

WebLogic applications. These applications offer a quick way of checkingthe status or logfiles of a WebLogic server and starting or stopping a server.

1 - 12


WebLogic applications provide you with convenient access to WebLogic functions.You can open the WebLogic applications by double-clicking WLSSPI→WebLogic inthe Application Bank window.

The group contains the following:

" Check WebLogic. Does an interactive status check of the WebLogicServer.

" Start WLS Console. Launches your Web browser, which displays theWebLogic Server Admin Console. You need to set this up before it willwork. Set up involves a couple of steps, detailed in Chapter 2 (Task 2and Task 6).

" Start WebLogic. Allows OpenView Operations user to start theWebLogic server (requires setup).

" Stop WebLogic. Allows OpenView Operations user to stop theWebLogic server (requires setup).

" View WebLogic Log. Allows user to view the entire specifiedWebLogic Server log file.

1 - 13


Templates

The SPI for WebLogic Server template group contains three subgroups withtemplates corresponding to WebLogic Server versions:

" WebLogic Server 6.0

" WebLogic Server 6.1

" WebLogic Server 5.1 (minimal functionality, equivalent to the GallerySPI; included here for your convenience; contains a single metric thatmonitors the availability of WebLogic Server).

The two full-featured groups, WebLogic Server 6.0 and 6.1, contain twotemplate subgroups for monitoring WebLogic Server-related metrics and logfilesand another template for intercepting messages as follows:

" Metrics: monitors incoming values that reflect WebLogic Server’sperformance levels and availability. Each value is evaluated accordingto 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 triggeringalerts/messages and collector templates, which show the metrics (each ofwhich has a unique number) whose values are collected for that interval.Each collector template group is assigned a collection interval of5 minutes, 15 minutes, one hour, or one day. The collection intervalindicates how often data is collected for that specific group.

Each monitor template determines the threshold conditions for themonitored metric, the message text that is triggered when the threshold isexceeded, 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/analyzerat each collection interval and (2) to show all monitor templates within thegroup, and (3) to specify which metrics are collected.

1 - 14


" Logfiles: monitors WebLogic Server- and WebLogic SPI-generatedlogfiles. The information captured from these logfiles includes changesto WebLogic Server configurations and errors that occur in theoperation of the WebLogic Server or the WebLogic SPI itself.

" WLSSPI Messages. Not a group, but a single template that can be usedto intercept specific messages.

1 - 15


The last three messages belong to the WebLogic and WLSSPI Message Groups (seethe column titled MsgGrp), indicating their origins. The WebLogic messagesindicate conditions occurring in WebLogic Server, while the WLSSPI messagesindicate conditions occurring in the WebLogic Server SPI.

Reports: from OVO Actions or WLSSPIApplications

WLS-SPI reports can show information on past or current conditions in theserver. These reports can be triggered by alarm conditions or generated whenyou need information on the current state of a server.

Reports generated through Automatic actions are context sensitive, relating onlyto a single server on the managed node. Reports generated through theApplication Bank show information on all servers configured on the managednode.

Specifically, each report type is defined as follows:

1 - 16


! Automatic Action Reports: generated automatically by an alarmcondition in relation to an individual server instance on a managed node.These reports are available by clicking the Annotations button in the OVOMessage Browser. If you have configured your Message Browser todisplay the SUIAONE columns, a flag under the S column (adjacent to themessage) indicates that the report was generated successfully and iswaiting in the Annotations of the message.

! Application Bank Reports: generated manually by dragging the managednode onto the report in the Application Bank. These reports reflect thecurrent condition of all configured server instances on the managed nodeat the time you generate it.

WLS-SPI Application Bank Reports. You can generate a report on all servers of amanaged node by dragging the node onto a report in the Application Bank window.

1 - 17


COMPONENT INTERACTION

WLS-SPI components must all work together in order to retrieve data anddeliver useful information regarding the health of the targeted server. The tasksthat components complete and the windows you use to access the individualcomponents are as follows:

Task Window you open — Component you use:

Connecting to the server &configuring the managednode

Application Bank window — WebLogic SPI →SPIAdmin→Config WLSSPI: When you run the applicationWLS SPI Config, you enter information about the Webapplication server running on the managed node, so the SPIknows how to connect to the server and gather data formetrics and reports.

Interpreting/ displayinginformation on theWebLogic server conditions

Message Source Templates window — monitortemplates: Defines conditions relating to each metric valueused by OVO agent software to generate messages and otherinformation made available in the OVO Message Browser.

Configuring metriccollections

Message Source Templates: collector template. Lists allmetrics within the template group and directs thecollector/analyzer to collect the values of the specifiedmetrics at predefined intervals, compare them to permissiblelevels, and call OVO to check threshold values and triggeralarms.

1 - 18

2

Installing & Configuring theWebLogic Server SPI

Chapter 2: Installing & Configuring the WebLogic Server SPIIntroduction

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

Chapter 2: Installing & Configuring the WebLogic Server SPIHow 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 yourWeb 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 (fromthe command line) for both HP-UX or Solaris systems. For HP-UX systems, youcan also use the graphical user interface (GUI), but the GUI method is notcovered in this section due to the numerous differences in displays for thevarious HP-UX versions.

Prerequisite/pre-installation information: OpenView Operations (OVO)management server must be installed. It is not necessary to stop OVO sessionsbefore 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.01.00.DEPOT WLSSPI

To install all bundles for a Solaris* management server, enter:

/usr/sbin/swinstall -s /cdrom/WLSSPI_SOL_ITO_A.01.00.DEPOT WLSSPI

* For managing SOLARIS managed nodes from an HP-UX management server, install theHP-UX version, NOT the SOLARIS version.

2 - 3


The WebLogic Server SPI bundles and filetsets are as follows:

NOTE *For Windows NT 4.0 managed nodes, on the managed node the TEMPenvironment variable must be set in the OVO agent’s environment. One way toensure this is the case is by setting TEMP as a System Variable. Usually TEMP isset as a User Variable, but it may not be set for the user that OVO runs as. Youcan add TEMP to the System Variables by opening theControl Panel→System→Environment tabbed dialog.

If you do not establish this setting, WLS-SPI programs may not executesuccessfully on the NT 4.0 managed node.

BUNDLE SPIWebLogicHPUX FILESET WLSSPI.WLSSPI-CORE

FILESET WLSSPI.WLSSPI-HPUX

END_BUNDLE

BUNDLE SPIWebLogicSOL FILESET WLSSPI.WLSSPI-COREFILESET 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.WLSSPI-SOL

FILESET WLSSPI.WLSSPI-NT*

PRODUCT WLSSPI(Filesets can be selectedindividually for UNIX/Solaris/NTenvironments)

FILESET WLSSPI-CORE

FILESET WLSSPI-HPUX

FILESET WLSSPI-SOL

FILESET WLSSPI-NT*

2 - 4


TASK 2: (OPTIONAL) CONFIGURE THE MANAGEMENTSERVER TO LAUNCH YOUR WEB BROWSER

WLS-SPI uses the ovweb utility to start your Web browser for displayinggraphed metrics (which require OpenView Performance Manager 4.0 or higher)and also for launching the WebLogic Administration Console. If you do not useOpenView Performance Manager and do not want to start the WebLogic consolefrom the OVO console, you can skip this task.

Before ovweb can launch your Web browser, however, you must insert thebrowser invocation command within the ovweb.conf file. If no browserinvocation command is included in the ovweb.conf file, ovweb tries to startNetscape (which must be version 4.7 or higher).

NOTE The ovweb.conf file must be located in the directory specified by theenvironment variable $OV_CONF, used by OpenView Operations. If necessary todiscover the OpenView Operations directory structure on your managementserver, 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 theWebLogic SPI to pass a URL to the browser. Open the file and insertthe command according to the entry syntax and example as follows:

Syntax: Browser: <browser command> %sExample: 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 settingwithin the browser’s Preferences.

NOTE An additional step, covered in Task 6, is required for the graph display. In thistask you enter the location of the Reporter Windows system in the WLS-SPIconfiguration file.

For more information about launching a browser in OpenView Operations,consult the manpages for ovweb and ovweb.conf and ov.envvars. To accessinstructions for enabling graph displays, at a command prompt enter:

man ovweb

2 - 5


TASK 3: ASSIGN OPERATOR RESPONSIBILITIES FORADMINISTRATOR

1. Log on to OVO as administrator (opc_adm).

2. Open the User Bank window, right-click the opc_adm user, and chooseModify.

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 appropriateoperators.

2 - 6


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 needonly place any nodes running WebLogic Server in the correct node group.

1. From the Window menu, open both the Node Group Bank and the NodeBank to display (side-by-side) the WLS-SPI node groups and the managednodes.

2. Drag and drop managed nodes running WebLogic Server into theappropriate WLSSPI node group, according to the WebLogic Server versionrunning on the node.

NOTE WLS-SPI can monitor multiple WebLogic servers running on one managednode. 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 thefollowing component check boxes:

" Actions

" Monitors

" Commands

(Do NOT select “Templates.”)

2 - 7


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 Browserfor each managed node:

The following configuration information was successfullydistributed: Actions Commands Monitors

The WLS-SPI is now installed on the Management Server and selected managednode(s). If you want to install the WLS-SPI on other managed nodes, repeatsteps 1-5).

2 - 8


TASK 6: CONFIGURE A WEBLOGIC SERVER USER

In order to run the WLS-SPI data collector with a WebLogic user name otherthan 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 youplan to use for the WLS-SPI if it does not already exist.

2. Create an ACL named weblogic.admin.mbean if it does not alreadyexist.

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 3.

5. In the next task, where you configure the SPI connection to WebLogicServer, you must add the user/password information within theconfiguration file. (See the SERVER<n>_LOGIN andSERVER<n>_PASSWORD keywords in Task 7.)

2 - 9


TASK 7: CONFIGURE SERVER CONNECTIONS AND GRAPHS

With WLS-SPI installed on the OVO management server, you must nowconfigure the connection to WebLogic Server on each managed node. A singlefile on the on the management server contains all WLS-SPI configuration, whereyou define:

" WebLogic Server and Java program file locations

" WebLogic Server server information

" user information

" (optional) OpenView Performance Manager system location (forgraphing)

When you save the file as part of the configuration process, only the relevantinformation for each node is transmitted to the node. Convenience and securityare the result, for you have all configuration information in one place on themanagement server but only relevant information present on each managednode.

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 iconsWLSSPI→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 editorby setting the EDITOR environment variable in the root user setup.

4. Enter the information (as explained in the sections that follow) into the fileand save.

When you save the file, OVO automatically deploys the configuration to theselected node and displays the message:

2 - 10


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 sectionsthat follow for the correct syntax for your specific entries.

WL_HOME= /opt/bea/wlserver6.0sp1JAVA_HOME= /op/bea/jdk130NUM_SERVERS= 1SERVER1_NAME= myserverSERVER1_PORT= 7001

GROUP production_nodes{pnodea.company.compnodeb.company.com}

NODE tnodez.company.com{SERVER1_NAME= testserverSERVER1_PORT= 7010}

NODE production_nodes{SERVER1_NAME= real_server}

NODE bignode.company.com{NUM_SERVERS=2SERVER2_NAME= petstoreSERVER2_PORT= 7101}

2 - 11


Syntax Structure

Lines preceded by # are treated as comments and are ignored.

variable=<value>vaiable=<value>

GROUP <group_name>{node_namenode_name...}NODE <node_name | group_name>{var=valuevar=value...}

Variable (variable=<value>) definitions outside NODE blocks apply to allnodes but are overriden by variable definitions inside a NODE block, which applyonly to the specified node_name or node group_name.

Entries for GROUP | NODE Blocks

Group blocks (sections identified as GROUP <group_name>) are used to groupnodes together that have common variables. The method works in this way:

" To define a GROUP, follow GROUP with a group_name to identify thegroup of nodes with common variables, and then list the nodes in thegroup.

In a node block below you will repeat the group_name (following NODE) to definethe variables of the group as described below.

Node blocks (sections identified as NODE <group_name> | <node_name>) workeither in conjunction with group blocks (as described above) to define variablesfor a group, or stand-alone to define variables for a single node. Node blocks,then, work in this way:

" To define group variables in the node block, follow NODE with the<group_name>, and between the curly brackets list the variablescommon to the group.

" To define individual node variables in the node block, follow NODE witha node_name, and within the curly brackets that follow list the variable

2 - 12


definitions that apply to that node.

Any configuration file entry occurring more than once within theconfiguration file is resolved by the last definition taking precedenceover any previous entry.

NOTE The node name specified in a node or group block must match the valuereturned by the OVO variable $OPC_NODES, which usually is the fully qualifieddomain name of the node.

Entries for SERVER Numbering and Variables

Each variable specified as SERVER<n>_var refers to a specific WebLogic Serverinstance. When more than one WebLogic Server is running on a given managednode, the number <n> differentiates the servers. Numbering must begin at “1”for each managed node, with the NUM_SERVERS variable set to the actualnumber of WebLogic Servers running on the node.

Configuration file variables (keywords) are as follows:

Variable (Keyword) Value entered

WL_HOME Enter the directory where WebLogic Server isinstalled.Example:WL_HOME = /opt/bea/wlserver6.0sp1

JAVA_HOME Enter the directory where Java is installed. The javaengine is expected to be$JAVA_HOME/bin/java:Example:$JAVA_HOME = /opt/bea/jdk130

NUM_SERVERS Enter the number of WebLogic servers on themanaged node.Example:NUM_SERVERS = 3

SERVER<n>_NAME Enter the server name as defined in WebLogicServer.Example:SERVER1_NAME = myserver

2 - 13


SERVER<n>_PORT Enter the port the WebLogic server listens on.Example:SERVER1_PORT = 7001

WL_USER Enter the system username for starting and stoppingWebLogic Server from the OVO Application Bank.The default is the username under which the OVOagent runs.Example: WL_USER = weblogic

SERVER<number>_START_CMD Enter a fully qualified system command that startsWebLogic Server from the OVO Application Bankapplication Start WebLogic. This command is runby WL_USER (defined above) and must be includedin order for the Start WebLogic application to work.NOTE: This command must exit; that is, theWebLogic Server process must run in thebackground or as a service, and it must be protectedfrom its parent process dying.Example: SERVER1_START_CMD =/sbin/init.d/weblogic start

SERVER<number>_STOP_CMD Enter a fully qualified system command that stopsWebLogic Server. This command is run from theOVO Application Bank application Stop WebLogicand is run by WL_USER (defined above) and mustbe included in order for the Stop WebLogicapplication to work.Example: SERVER1_STOP_CMD =/sbin/init.d/weblogic stop

SERVER<number>_LOGIN Enter a WebLogic Server-defined user (not a systemuser) that will be used to monitor the WebLogicServer. If not specified, the default user is guest.Example: SERVER1_USER = janedoe

SERVER<number>_PASSWORD Enter the password for the SERVER<n>_USER. IfSERVER<n>_USER is not specified, user guestwith no password is assumed.Example:SERVER1_PASSWORD = janedoe123

SERVER<number>_VERSION Enter the version number if using WebLogic 5.1. Ifomitted, WebLogic Server SPI assumes the versionto be 6 or higher. You may specify the major version(5) or the full version (5.1).Example: SERVER1_VERSION = 5

GRAPH_SERVER Enter the name of the Windows system wherePerformance Manager (for graphing) is installed.

Example: GRAPH_SERVER = graphserv

2 - 14


The following entries are applicable only when SERVER<n>_VERSION is5 or 5.1

MAX_ERROR_LOG_SIZE Enter the maximum number of MB allowed for theerror logfile. When the error logfile reaches themaximum limit, it is renamed as a backup file andlogging resumes. When a new backup file replacesan old backup file, the old backup is deleted.NOTE: The default is 10MBExample: MAX_ERROR_LOG_SIZE = 20

UDM_DEFINITIONS_FILE If you have user-defined metrics, enter the fullyqualified path name to the metric definitions XMLdocument.

SERVER<n>_ADMIN_HOST Enter the location of the WebLogic administrationserver for this server. Must be included in order forthe WebLogic Start/Stop applications to work.Example: SERVER1_ADMIN_HOST=localhost

SERVER<n>_ADMIN_PORT Enter the port of the WebLogic administrationserver for this server. Must be included in order forthe WebLogic Start/Stop applications to workExample: SERVER1_ADMIN_PORT=7005

SERVER<n>_LOGFILE Enter the fully qualified path of the WebLogicServer log file. If not specified, the default value is<wl_home>/<SERVER<n>_name>/weblogic.log.

SERVER<n>_CLUSTER Enter the name of the cluster to which thisWebLogic Server belongs if WebLogic clusteringis implemented on this node.Example: SERVER1_CLUSTER=mycluster

2 - 15


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 selectAgents→Install/Update SW & Config.

2. In the Target Nodes section select the Nodes in List Requiring Updateradio button.

3. In the Install/Update Software and Configuration window check theTemplates check box.

4. Select Force Update; then click OK.

The following message is displayed in the Message Browser:

The following configuration information was successfullydistributed: Templates

The WLS-SPI templates are now distributed to the selected node group.WLS-SPI monitors can now begin running according to their specific collectioninterval.

NOTE If you use HP OpenView Reporter, please see the Chapter 4 for informationon integrating WLS-SPI with Reporter for generating WebLogic Server reportsthat show more consolidated information.

2 - 16

Chapter 2: Installing & Configuring the WebLogic Server SPICheck the Installed WebLogic Server SPI Nodes for License Count

Check the Installed WebLogic Server SPINodes for License Count

You can use an OVO reporting utility to check the number of templates you haveinstalled on your managed nodes. In reviewing the number of templates permanaged node, you can see if you have consistently installed templates acrossyour managed systems. In addition, by running this report, you can also ensurethat the number of licenses you have purchased is in compliance with the reportresults.

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....

3. In the Reports window among the reports listed select WLSSPI LicenseCheck.

4. Select an output destination and click OK.

2 - 17

Chapter 2: Installing & Configuring the WebLogic Server SPIHow to Remove WLS-SPI

How to Remove WLS-SPI

The complete removal of the WebLogic SPI installation deletes all WLS-SPIprogram components as well as the WLS-SPI templates. If you have customizedtemplates (copies of WLS-SPI default templates) residing in other OVOtemplate groups, you should remove them as well. If you are upgradingWLS-SPI, complete only the first section “Removing WLS-SPI software from theManagement Server.”

TASK 1: REMOVE WLS-SPI SOFTWARE FROM THEMANAGEMENT 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 belowvar/opt/OV/share/databases/OpC/mgd_node/customer thatbegins with wasspi.

NOTE If you are upgrading WLS-SPI, STOP HERE!

The swremove command removes the files from the file system only. TheWLS-SPI templates are still in the OVO data repository and must be deletedmanually. First, however, they (and the WLS-SPI software) must be de-assignedfrom the managed nodes.

TASK 2: REMOVE WLS-SPI SOFTWARE FROM NODEGROUPS AND MANAGED NODES

Before beginning the procedure below, de-assign the WLS-SPI template groupsthat you have deployed from the node groups.

1. Open the Node Bank and from the Actions menu select Agents→Assign

2 - 18


Templates.

2. In the window that opens select WebLogic 5.x, WebLogic 6.0, orWebLogic 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 theNode Group window and select the targeted node group.

5. In the Node Bank window from the Action menu selectInstall/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 fromthe managed node(s). The following message is displayed in the MessageBrowser:

The following configuration information was successfullyremoved: 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 levelindividual templates within the group and work your way up to the SPI forWEbLogic Server group at the top.

2 - 19


1. Open the Message Source Templates window and select the SPI forWebLogic Server template group

2. Double-click the WLS-SPI group below it (WLS-6.0, 6.1, or 5.1) until youreach 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 samemethod until you have deleted all WLS-SPI individual and group templatesfrom 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 theycontain) 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 (UserBank→Responsibilities...window) and WebLogic SPI node groups (NodeBank window).

2 - 20


Deleting the WLSSPI Application Groups

TASK 5: FINISH UP—DELETE THE WLS-SPI MESSAGE ANDNODE GROUPS; REMOVE WLS-SPI DIRECTORY

1. From the Window menu select Message Group Bank.

2 - 21


2. In the Message Group Bank window right-click the WLSSPI group andselect 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 selectDelete.

6. Repeat with the WebLogic Group.

7. From a command line remove the directory by entering:rm /var/opt/OV/wasspi/wls.

2 - 22

3

Using and Customizing theWebLogic Server SPI

Chapter 3: Using and Customizing the WebLogic Server SPIIntroduction

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 theWebLogic Server SPI connections, and deployed the templates. In the OVOmessage browser, some messages may be appearing regarding the performanceof WebLogic Server.

As you become familiar with the WebLogic Server SPI, you can determinewhich 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 howto make those changes. In addition, the chapter will also provide information onusing the WLS-SPI with HP OpenView Reporter.

In general the following topics are covered:

! Using the WebLogic Server SPI Templates

! Basic Template Customizations

! Advanced Template Customizations

! Reinstalling WLS-SPI Templates

! Using Templates/Applications to Generate Reports

3 - 2

Chapter 3: Using and Customizing the WebLogic Server SPIUsing WebLogic Server SPI Templates

Using WebLogic Server SPI Templates

You can customize WebLogic Server SPI templates, although they work withoutany modifications. To help you in understanding how you might customize theWLS-SPI templates, the following sections cover the OpenView Operationstemplates 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 OVOtemplates. 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 thresholdsettings monitoring WebLogic availability and performance metricsgrouped according to collection intervals. The metrics group contains alist of monitor templates that fall into two categories according to theirfunction.Monitor templates pertain to individual metrics. Collector templatespertain to all metrics scheduled to be collected in the specifiedcollection interval.

3 - 3


" Logfile templates: generate messages according to logfile and errortext detected in both the WebLogic Server logfiles and in the WLS-SPIlogfiles.

The WLSSPI-Messages template is used as a means of intercepting WLS-SPImessage for the OVO message browser.

OVO Template Types and WLS-SPI

Monitor templates define how data is collected for the individual metric and set athreshold value that when exceeded generates alerts/messages in the MessageBrowser. You can change the threshold within a monitor template byhighlighting the template and clicking the Conditions...button. Thendouble-click one of the conditions shown.

Incoming values for metric WLSSPI-0012.1 are compared against its monitor template settings. Inthe illustration below, the default threshold is set at 10.

Collector templates define all metrics for the WebLogic Server application thatare scheduled for collection at the specified interval. Though still identified as a“monitor” in the OVO lists of templates, you will notice that these templateshave names different from the individual metric monitor templates. Within thename of each collector template is its collection interval; for example

3 - 4


WLSSPI-60-1h. When you open any collector template, you see all metrics (bynumber) collected within the interval following the -m option of thecollector/analyzer command wasspi_wls_ca.

The illustration shows the Monitor Program or MIB ID text box, which contains thecollector/analyzer command (wasspi_wls_ca), followed by the collection parameter and collectionname (- c wlsspi-60-1h), followed by the metric parameter and each metric (- m 2,210-212).

3 - 5

Chapter 3: Using and Customizing the WebLogic Server SPIBasic Template Customizations

Basic Template Customizations

After you begin using the WLS-SPI you may decide that specific WLS-SPItemplates need some modification. Descriptions contained in the previoussection of metric monitor templates (rules for interpreting metric data; forexample, thresholds,) and collector templates (rules for the scheduled metriccollection) show you where to go to make the various changes. For example, tochange a threshold, you would open a metric monitor template. To schedule ordelete a metric from data collection, you open the collector template. Thosekinds of basic customizations are covered in this section.

NOTE In most cases, it is advisable to make copies of the original templates so that thedefault templates remain intact.

Modifying Monitor Templates

Many metric attributes can be easily modified for all monitored instances ofWebLogic 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 SuppressConditions window.

4. Double-click the desired condition to modify (there is usually only one).

3 - 6


The Message and Suppress Conditions Window

The Condition window is displayed. The following attributes can be easilymodified:

" Threshold. Enter a value for the metric data that when exceeded wouldsignify a problem either about to occur or already occurring.

" Duration. The length of time that the incoming data values for a metriccan exceed the established threshold before an alarm is generated.

" Severity. Click the Severity button and select the desired severitysetting.

3 - 7


" Message Text. Be careful not to modify any of theparameters—surrounded by <> brackets, beginning with $—in amessage.

" Actions. This field provides the ability to generate PerformanceManager graphs or reports, or to add custom programs. The reports orgraphs 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 theaction was triggered from an exceeded threshold. You can view thereport in the message Annotations.

Operator initiated action. The operator action delivered with the SPIprovides that within a message’s details window you can press thePerform Action button to view a graph of the metric whose exceededthreshold generated the message along with other related metric values.

The Condition window, showing a threshold setting of 10 for WLSSPI-0026. The incoming valuesfor 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 theclient experiences, generating a Warning message.

An alarm can be generated once or multiple times, depending on its setting in theModify Threshold Monitor window, which shows:

3 - 8


To change the Alarm Generation Type, modify the settings below, completingthe steps that follow.

" Reset: Alarms are generated once when the threshold value isexceeded. At the same time a reset threshold value is activated. Onlywhen the reset threshold value is exceeded, does the original thresholdvalue become active again. Then when the threshold value is againexceeded, another alarm is generated and the process starts all overagain.

" Without Reset. Alarms are generated once when the monitoringthreshold value is exceeded. Alarms reset automatically when metricvalues are no longer in violation of the thresholds and are generatedagain when the threshold is exceeded.

" Continuously. Messages are sent/alerts generated each time the metricvalues are collected and the threshold is exceeded.

The Modify Threshold Monitor Window

1. Open the Message Source Templates window.

3 - 9


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

Chapter 3: Using and Customizing the WebLogic Server SPIAdvanced Template Customizations

Advanced Template Customizations

The template changes suggested here range from making copies of defaulttemplate groups in order to customize a few settings, to deleting whole groups ofmetrics within a template’s command line. This section is considered advancedbecause all changes described here, whether simple or complex, require someadvanced knowledge of the WLS-SPI metrics.

Choosing Metrics To Monitor

As a start, determine which metrics you want to change and what templateswithin 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 templateand rename it.

5. Delete the originals.

6. Alter the renamed templates within the group as necessary.

3 - 11


Creating a new template group allows you to keep custom templates separate from the original defaulttemplates, which you copy and place within the new group.

Using the WLS-SPI Collector/Analyzer Command withParameters

The wasspi_wls_ca command is used in every collector template, namedaccording to its collection interval. You can view the default command lineparameters within each collector template in the Monitor Program or MIB IDtext box in OVO.

3 - 12


USING THE WEBLOGIC SERVER COMMAND PARAMETERS

WLS-SPI data collections are started with the wasspi_wls_ca command, towhich you can add other parameters, as identified in the following table.

Parameter Function Syntax with Example

-c (collector) Specifiescollector template name.

(required)

-c <collector_template_name>Note: Must match the collector template namein which it appears.

Example: -c WLSSPI-05min

-m (metric) Specifies themetric numbers ornumber ranges on whichto collect data.

-m <metric_number,metric_number_range>

Example: -m 1,3-5,9-11,15

-t (tag) Allows you to createa new template group byadding a prefix to anexisting collectortemplate along with themetric number(s).

wasspi_wls_ca<prefix>-<collector _template>-m <metric_number> -t <prefix>-

Example:wasspi_wls_ca -c DEV-WLSSPI-61-1h-m 220-223 -t DEV-

-i (include) Allows you tolist specific servers tomonitor. This option maynot be used with -eoption.

-i <server_name>

Example: -i server1,server3

-e (exclude) Allows you toexclude specific servers;may not be used with -ioption.

-e <server_name>

Example: -e server1,server3

3 - 13


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 -iserver_1,server_2 -t STAGE_

(Inserting “server_1” and “server_2” in the Monitor Program or MIB ID text boxof the collector template results in collecting data for the specified metrics fromthese servers only).

-x Allows you to specify aproperty/value as follows:

alarm: when off,overrides any alarmingcondition as set up in themetric monitor template.

print: when on, prints themetric name, instancename, and metric value toSTDOUT in addition toany configured alarmingor logging.

log: when off, preventsgraphing or reportingfunctions.

-x <property>=<property_value>

-x alarm=off

-x print=on

-x log=off

Parameter Function Syntax with Example

3 - 14


Changing the Collection Interval for AllScheduled Metrics

To change the metric collection interval, simply change the Polling Interval inthe appropriate collector template. For example, to change the collection ofdefault metrics from 5 minutes to 10 minutes for the WebLogic 6.0 templategroup, follow these steps:

1. Select the Message Source Templates window.

2. Select the template group SPI for WebLogic Server and openWebLogic 6.1→WLS-6.1-Metrics.

3. Select the collector template WLSSPI-61-05min.

4. Click the Modify... button. and change the Monitor Name toWLSSPI-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....

7. Distribute the new templates (described in Chapter 2, Task 8: DistributeWLS-SPI Templates, page 2-16).

3 - 15


Changing the Collection Interval for SelectedMetrics

To change the collection interval for selected metrics, copy the appropriatecollector template and rename with a name reflecting the new interval, deletingall but the metrics you are changing. Set the new interval. Edit the originaltemplate to remove the changing metrics. For example, to change the collectioninterval 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 openWebLogic 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 -mexcept 70-77.

6. Change the Polling Interval to 10m.

3 - 16


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.

3 - 17


Customize the Threshold for DifferentServers

Customize the threshold as needed. For example, you may want to set thethreshold for SERVER_1 for metric 0012 to 20 and leave it at 10 for all otherservers. To do so, copy the existing condition and modify it to serve as theexception. 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 ofthe condition.

3. Name the condition WLSSPI-0012.2.

4. In the Object Pattern field, enter the desired characters to use for patternmatching (in this example SERVER_1). For example, to match on all serverswith a specific character string in the name, enter the string in the ObjectPattern field. (see the OVO online Help or the OVO Administrators TaskGuide for pattern matching syntax).

5. Click the Test Pattern Matching… button to test the pattern and verifypattern matching (you must set up a match file first).

3 - 18


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 thecommand line), which allows the collector/analyzer to recognize customizedtemplates that have a tag attached to the name. This option provides you with theflexibility of using more than a single set of templates to define conditionspertaining to specific installations of WebLogic Server.

When multiple nodes are managed by a number of groups, this option allows youto create specially tagged templates that are obviously separate from youroriginal setup. In such a case, you would make copies of the templates, renamethem with the tag and re-work the collector template to pick up the taggednames, then assign them to the various groups.

For example, you might create a group of templates and change each templatename to include CLIENT01 in it. A metric monitor template might be namedCLIENT01-WLSSPI_0012 (retaining the metric number, which must be used).The collector template name would be named FIRST_CLIENT-61_05min. Youcould then set up another group for SECOND_CLIENT and change all thosetemplates to include the SECOND_CLIENT in the name.

To create the new template group:

1. Copy the original template group: In the Message Source Templateswindow select the group and click the Copy... button.

2. Name the new group according to how you plan to identify the new monitorand collector templates; for example, if you are including FIRST_CLIENTin the template names, include that within the new template group name.

3. In the Message Source Template window expand the new template group toshow all templates and select each template you plan to use, click theCopy... button, and rename it according to your naming scheme.

" The names you give the new metric monitor templates in the group

3 - 19


would contain the new name followed by the original metric number.For example, a copy of WLSSPI-0001 could be calledCLIENT01-WLSSPI_0001.

" The name you give the new collector monitor template would alsocontain the identifying name. You would also modify the scheduledcollection for the new group by inserting the -t property on thecommand 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

Chapter 3: Using and Customizing the WebLogic Server SPIRe-installing the WLS-SPI Templates

Re-installing the WLS-SPI Templates

When WLS-SPI templates are installed in OVO, the commands shown belowautomatically uploads them when swinstall is run. Any customized templatesettings you may have done for the previous installation are overwritten.

To restore the default SPI for WebLogic Server template group you hadoriginally installed, delete all current templates first, then run the command:

Scripts Run by swinstall

*Alternatively, you can use the -verbose option instead of the -silentoption.

OVO Scripts

>6.x /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

3 - 21

Chapter 3: Using and Customizing the WebLogic Server SPIUsing Templates/Applications to View Annotation Reports and Graphs

Using Templates/Applications to ViewAnnotation Reports and Graphs

Some templates have actions defined with theshold violations or error conditionsthat automatically cause reports to appear in the message Annotations. Thesereports are snapshots of data values collected form the server around the timethat the alarm occurred.

Other templates have operator actions associated with them that allow you togenerate a graph.

NOTE The reports discussed in this section should not be confused with thosegenerated by OpenView Reporter, which show more consolidated, historicaldata 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 OVOmessage browser, or just select the message and click Annotations. Youcan 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 Bankwindows. Continue to open application windows WLSSPI→WLSSPIAdmin→Reports. Select a node and drag it onto the WLSSPI metricreport you need. These reports show all server data on a node.

" To view graphs. Open both the Node Bank and Application Bankwindows. Continue to open application windows WLSSPI→WLSSPIAdmin. Drag a node onto the View Graphs application to launch youWeb browser, which displays the graphing feature available in HPOpenView Performance Manager (which requires a separate purchase).

3 - 22


Checking for indications of Automatic Reports in the OVO Message Browser

AUTOMATIC ACTION REPORTS

Many metrics generate Automatic Action Reports. These reports are generatedas 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 queriedfor additional data. If your message browsser is set to display the SUIAONEcolumn, you will see an “S” under the “A” column (see illustration), whichindicates that a generated report is available in the Annotations area of theMessage 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


HOW AUTOMATICALLY GENERATED AND

MANUALLY GENERATED REPORTS DIFFER

Automatic Action reports show the state of the system moments after the alarmoccurred. You can manually generate a report that shows the current state of thesystem by dragging the managed node from the Node Bank onto the desiredreport in the Application Bank (see the next section for details on ApplicationBank reports).

Application Bank Reports—use these applications to manually generate a reportsimilar to an Automatic Action report. These reports differ by showing data on ALLWebLogic Server instances on the managed node. The Automatic Action reportshows data on the single WebLogic Server instance with the exceeded threshold

3 - 24


APPLICATION BANK REPORTS

Application Bank reports run for all WebLogic Server instances configured onthe managed node, in contrast to Automatic Action Reports which are generatedfor a single WebLogic Server instance. The reports generated from theApplication Bank reflect the current state of WebLogic Server on the managednode.

To generate a report in OVO, simply drag the managed node from the NodeBank window to the desired report in the Application Bank window.

The report below appears in the Annotations area of the message details.

3 - 25

Chapter 3: Using and Customizing the WebLogic Server SPISample Report

Sample Report

The following example shows the format of a WLS-SPI report. This report isautomatically generated (automatic action report).

Report on metric B-011

3 - 26

4

Using HP OpenView Reporting andGraphing Features with WLS-SPI

Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPIIntroduction

Introduction

HP OpenView Reporter (which you can separately purchase) integrates fullywith the SMART Plug-In for WebLogic Server. Reporter producesmanagement-ready, Web page reports, showing historical and trendinginformation.

The WebLogic Serve SPI working in conjunction with Reporter produces a variety ofreports, showing consolidated information on WebLogic Server.

Another OpenView product, Performance Manager 4.0, provides a graphingcapability. With this added capability you can use the WLSSPI Admin ViewGraphs application to generate graphs of current conditions. In addition,Performance Manager also works to generate graphs associated withOperator-initiated actions (wherever included in a WLS-SPI template). BothReporter and Performance Manager run on Windows, but because their reportsand graphs are generated as Web pages, you can configure your UNIX system toremotely display them.

4 - 2

Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPIIntegrating WebLogic Server SPI with Reporter to Generate Reports

This chapter provides information on how to fully integrate WLS-SPI withHP OpenView Reporter and Performance Manager. After you complete theinstructions in this chapter, every night Reporter generates reports that show theperformance and availability of WebLogic Server on configured managed nodes.You will also be able to take advantage of the built-in graphing capabilities of theWLS-SPI, coupled with Performance Manager.

Integrating WebLogic Server SPI withReporter to Generate Reports

Prerequisite: Installation of the WebLogic Server SPI according to theinstructions in Chapter 2, which includes software deployment, serverconnection configuration, and assignment/distribution of templates to targetednodes.

The WLS-SPI report package must be installed on the Windows system runningReporter. You can install it directly from the CD as explained below.

1. On the Windows client system, insert the CD in the CDROM drive anddouble-click:\reporter\WLSSPI-Reporter.exe

2. Follow the instructions as they appear.

NOTE During the installation an error message may appear that indicates the installerhas detected an older version of the installer on your system. The note is forinformation purposes only and can safely be ignored.

3. Check the Reporter status pane (see the illustration that follows) to notechanges to the Reporter configuration.

4 - 3


The status pane (at the bottom of the Reporter window) shows you information on the programsrunning and any errors occurring. You can check the status pane to see that Reporter has beenupdated with the WLS-SPI reports.

You can find instructions in the Reporter Help for assigning WLS-SPI reports tothe targeted nodes. To access Help, select Reports or Discovered Systems in theleft panel of the Reporter main window and right-click it. Select Report Help orDiscovered Systems Help from the submenu that appears. See the topic “Toassign a report definition to a Discovered Systems Group.”

4 - 4


4. Add group and single system reports by assigning reports as desired. (Seethe Reporter Help and the online Concepts Guide for completeinformation.)

NOTE Group and single system WLS-SPI reports require that you identify systems bytheir 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 andWLS-SPI show consolidated data on server performance and availability on allWebLogic Server systems. In addition, other reports show data for singlesystems. These reports are available the day following your installation of theWebLogic Server SPI report package on the Reporter Windows system. (Pleaserefer 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 top20 execute queues of all servers.

10

TOP 20 Servlet AverageExecution Times

Shows the average execution time for thetop 20 requested servlets for all servers.

240

TOP 20 Servlet RequestRates

Shows the total servlet request rate beingreceived by the top 20 servers.

242

Execute Queue ThreadUtilization

Shows the execute queue`s threadutilization as a percent for the top 20execute queues of all servers.

11

TOP 20 AverageTransaction Throughput

Shows the average transaction throughputfor the top 20 servers.

76

TOP 20 EJB Free Pool WaitRate

Shows the number of times per minute thata request had to wait for an EJB to becomeavailable for the top 20 servers.

25

4 - 5


Availability

Single System Reports

TOP 20 EJB Timeout Rate Shows the number of times per minute thata request timed out while waiting for an EJBto become available for the top 20 servers.

26

TOP 20 EJB TransactionThroughput

Shows the average EJB transactionthroughput for the top 20 servers.

35



Server Availability Contains a daily histogram showing thepercentages of uptime, downtime for allservers. Top 20 execute queues of allservers.

2

Server Availability Details Contains spectrum graphs showing minutesof uptime by day and hour for eachWebLogic Server.

2


JDBC Throughput AndConnection Utilization

Charts the throughput against the utilizationfor the JDBC connection pools for eachWebLogic server.

260,262

Throughput And UtilizationOf JMS Server By ByteCount

Charts the throughput against the queueutilization by byte count for destinations onthe JMS servers for each WebLogic Server.

252,256

Throughput And UtilizationOf JMS Server By MessageCount

Charts the throughput against queueutilization by message count on the JMSservers for each WebLogic server.

251,255

Queue Utilization versusThroughput On Server

Shows the throughput against the threadutilization for each WebLogic server.

10,11

4 - 6


TOP 20 Servlet RequestRate On Server

Shows a stacked area chart with the requestrate (requests per second) for the top 20servlets for each day and a table with dataof the top 100 servlets for each WebLogicServer.

242

Transaction Throughput OnServer

Shows the average transaction throughputfor each WebLogic Server by day.

76

Transaction RollbackTypes

Shows the transaction rollbacks by errortype for each WebLogic Server.

72-75

EJB TransactionThroughput By EJB

Charts the throughput (transactions persecond) for the top 20 EJBs for eachWebLogic Server.

227-230

TOP 20 EJB TransactionRollback Percent By EJB

Charts the transaction rollbacks for the top20 EJBs for each WebLogic Server.

231-234

TOP 20 Stateless EJBCache Utilization

Shows the EJB cache utilization percent forthe top 20 EJBs for each WebLogic Server.

224


4 - 7

Chapter 4: Using HP OpenView Reporting and Graphing Features with WLS-SPIIntegrating WLS-SPI with HP OpenView Performance Manager

Integrating WLS-SPI with HP OpenViewPerformance Manager

To use Performance Manager, you must separately purchase it, then completesome tasks to configure the Web page display for the OVO console (UNIXsystem). Some required tasks you have completed already. Specifically, therequired 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 ManagementServer to Launch your Web Browser, page 2-5.

2. Configure the location of the graphing system within the WLS-SPIconfiguration file, also explained in Chapter 2, Task 7: Configure ServerConnections and Graphs, page 2-10.

3. Install the WebLogic Server SPI reporting/graphing package at thePerformance Manager Windows system by inserting the CD in theCD-ROM drive and selecting Start→Run→\<CD-ROM drive>:\Products\WLSSPI Performance Manager Package\setup.exeand follow the instructions on screen.

VIEWING GRAPHS THAT SHOW ALARM CONDITIONS

For graphing purposes, the WebLogic Server SPI organizes metrics according totype and includes the following four groupings. When a message is generated forany metric appearing in a table in the section that follows, you can view a chartof its and other metric values.

To view a graph associated with an alarm condition (Operator-initiated actionhas 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


The resulting action displays the metric’s WLS-SPI graph, which charts itsvalues along with the values of other metrics in the same group.

VIEWING GRAPHS THAT SHOW PAST/CURRENTCONDITIONS

You can also generate any of the four available graphs manually by using theWLSSPI-Admin application View Graphs.

To manually generate a graph:

1. At the OVO console open both the Node Bank and the Application Bankwindows.

2. In the Node Bank window select the node for which you want the graphgenerated.

3. In the Application Bank window double-click WLSSPI and in the nextwindow 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 collectedmetric values. If you are interested in viewing any one of the metrics included inany 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, 91Metric number/name Metrics Description

B005_JVMMemUtilPct JVM Utilization Percent

B013_ SocketTrafficRt Socket Traffic Rate

B014_AtiveSocketCnt Active Socket Count

B061_JDBCConPlWtCnt JDBC Pool Wait Count

B085_InvLoginAttCnt Invalid Login Atempts Count

4 - 9


Enterprise Java Beans (EJB); 25, 26, 35, 36

Transaction; 70, 71, 72, 73, 74 75, 76, 77

Cluster; 80, 81

B091_TimeSerThruRt Time Services Throughput Rate

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

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

B080_ClsOutMesFailRt Cluster Outgoing MessageFailure Rate

B081_ClsInMesFailRt Cluster Incoming Message Failure Rate

4 - 10


LAUNCHING THE WEB PAGE DISPLAY WITH AN OPERATORACTION THAT GENERATE GRAPHS

Performance Manager graphs can be generated from most WLS-SPI alarmmessages by pressing Perform Action from the message details (or Properties) orfrom the Message Browser. The operator action launches your Web browser,which can then display a graph of the metric that generated the message as wellas 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 changingdisplay settings.

4 - 11


4 - 12

5

WebLogic Server SPI User DefinedMetrics

Chapter 5: WebLogic Server SPI User Defined MetricsIntroduction to User Defined Metrics

Introduction to User Defined Metrics

The WebLogic Server SPI can collect data on roughly 55 metrics. However, youcan, if you choose, add your own metrics. In defining your own metrics, you canmonitor your own applications by registering application MBeans with theWebLogic MBean server and creating user-defined metrics (UDMs) that instructthe SPI to gather data from these MBeans.

NOTE A custom MBean must expose a “Name” attribute. The WebLogic SPI uses thisname as the identifying name for the MBean. If your custom MBean is amulti-instance MBean, then each MBean instance must have a unique value inits Name attribute. For example, WebLogic's ServletRuntime MBeans aremulti-instance because a ServletRuntime MBean is instantiated by WebLogicfor each deployed servlet. The Name attribute of the MBean identifies theservlet that the MBean is monitoring.

Please see the JMX documentation for more information about creatingMBeans. Also refer to the WebLogic documentation for more information aboutregistering MBeans. The sections that follow assume you are familiar withXML and DTDs.

Metric Definitions Structure

When you define metrics, you create an XML file and structure its contentaccording to the MetricsDefintions.dtd (Document Type Definition) file includedwith the WSL-SPI. The MetricsDefinitions.dtd file content is describedand a sample XML shown in the sections that follow.

THE WLS-SPI METRICS DEFINITIONS FILE (DTD FILE)

The WLS-SPI includes a document type definition (DTD) file that shows howthe elements of your WLS-SPI XML metric definitions should appear. This file,MetricDefinitions.dtd, provides the structure and syntax for the XML filethat you create. The WLS-SPI uses this file to parse and validate the XML fileyou create.

5 - 2


The MetricDefinitions Element

Within the WLS-SPI MetricDefinitions.dtd file, the MetricDefinitionselement is the top-level element within the document. It contains one collectionof metrics, consisting of one or more metric definitions.

<!ELEMENT MetricDefinitions (Metrics)><!ELEMENT Metrics (Metric+)>

The Metric Element

The Metric element represents one metric. Each metric has a unique ID (forexample, “WLSSPI_0701”). If a user-defined metric is an alarming or reportingmetric, the metric ID must be "WLSSPI_0xxx" where xxx must be a numberfrom 700 through 799. Otherwise, if the metric is used only within thecalculation of another metric, the metric ID must begin with a letter(case-sensitive) and can be followed by any combination of letters, numbers, andunderscores.

A Metric element contains one or more elements that represent the metric datasource. Two data sources are supported: Mbeans and calculations.

<!ELEMENT Metric (MBean+ | Calculation+)><!ATTLIST Metric id ID #REQUIRED

name CDATA ""alarm (yes | no) "no"report (yes | no) "no"graph (yes | no) "no"previous (yes | no) "yes"description CDATA #IMPLIED >

Metric element attributes are described in the following table.

Attribute Type Required Default Description

id ID yes -- The metric ID.

name Text no "no" The metric name, used forgraphing and reporting.

5 - 3


The MBean Element

The MBean element is used when the data source of the metric is an attribute ofa JMX MBean. The MBean element contains an ObjectName element, anAttribute element, and, optionally, an AttributeValueMapping element. Theseelements are explained as follows:

" The ObjectName element content specifies the JMX-compliant objectname of the MBean. The object name can include JMX-compliantpattern matching.

" The Attribute element specifies the MBean attribute name.

" The AttributeValueMapping specifies numeric values that should besubstituted for the values returned by the MBean attribute. This can beused to convert string attributes to numbers so they can be compared toa threshold. Each AttributeValueMapping contains a number of Map

alarm "yes""no"

no "no" If yes, the metric valuewill be sent to the agentvia opcmon.

report "yes""no"

no "no" If yes, the metric valuewill be logged forreporting.

previous "yes""no"

no "yes" If yes, the metric value issaved in a history file sothat deltas can becalculated. If you are notcalcuating deltas on ametric, set this to "no" forbetter performance.

graph "yes""no"

no "no" Graphing of user-definedmetrics is not notsupported. This must be"no" for user-definedmetrics.

description text no "" A description of the metric.


5 - 4


elements. Each Map element specifies one value to be mapped.

" The FromVersion and ToVersion elements are used to specify for whichversions of WebLogic this MBean element is valid.

" The AttributeFilter element provides basic filtering of MBeans basedon an MBean attribute.

<!ELEMENT MBean (FromVersion?, ToVersion?, ObjectName,Attribute,AttributeValueMapping?,AttributeFilter?)>

<!ATTLIST MBean instanceType (single | multi) "single"dataType (numeric | string) "numeric" >

<!ELEMENT ObjectName (#PCDATA)>

<!ELEMENT Attribute (#PCDATA)><!ATTLIST Attribute description CDATA #IMPLIED

units CDATA "">

<!ELEMENT AttributeValueMapping (Map+)><!ELEMENT Map EMPTY><!ATTLIST Map from CDATA #REQUIRED

to CDATA #REQUIRED >

<!ELEMENT AttributeFilter EMPTY><!ATTLIST AttributeFilter type (include | exclude) "include"

name CDATA #REQUIREDoperator (initialSubString |

finalSubString |anySubString | match |gt | geq | lt | leq | eq)#REQUIRED

value CDATA #REQUIRED >

MBean element attributes are described in the following table.

Attribute PossibleValues

Required Default Description

instanceType "single""multi"

No "single" Indicates whether therecould be multiple instancesof this MBean.

5 - 5


Map element attributes are described in the following table.

AttributeFilter element attributes are described in the following table.

dataType "numeric""string"

no "numeric" Indicates whether the valuereturned from the MBeanattribute is a string or anumeric value.


from text yes no default The value that is to bemapped.

to text yes no default The new metric value to bereturned in place of themapped value.





type "include""exclude"

no "include" Specifies whether anMBean that matchesthis filter should beincluded or excludedfrom consideration bythe data collector.

name text yes no default Specifies the MBeanattribute on which toapply the filter.

5 - 6


The Calculation element is used when the data source of the metric is acalculation using other defined metrics. The Calculation element contains aFormula element whose content is a string that specifies the mathematicalmanipulation of other metric values to obtain the final metric value. The metricsare referred to in the calculation expression by their metric ID.

<!ELEMENT Calculation (FromVersion?, ToVersion?,Formula)><!ELEMENT Formula (#PCDATA)>

See the section “Metric Calculations” for more information on the correct syntaxfor the contents of the Formula element.

operator "initialSubString"

"finalSubString"

"anySubString"

"match"

"gt"

"geq"

"lt"

"leq"

"eq"

yes no default Specifies the filter toapply."initialSubString","finalSubString","anySubString", and"match" can be usedwith MBean attributesthat return text values.

"gt", "geq", "lt","leq", "eq" can beused for MBeanattributes that returnnumeric values. Seethe JMXdocumentation formore informationabout filteringMBeans.

value text or number yes no default Specifies the value tocompare. The metricdefinition creator isresponsible formaking sure the valuedata type matches thedata type of thecorresponding MBeanattribute.



5 - 7


More than one metric source element (MBean and/or Calculation) may beindicated in a Metric element. Each metric source element is scanned for aFromVersion or ToVersion child element to determine which metric sourceelement to use for the version of the application server being monitored. Thefollowing algorithm is used for determining what application server version issupported by each metric source element within the Metric element.

1. If a FromVersion element is not present, no lower limit exists to the serverversions supported by this metric.

2. If a FromVersion element is present, the server attribute indicates thelowest server version supported by this metric. If an update attribute exists,it additionally qualifies the lowest server version supported by specifyingthe lowest service pack or patch supported for that version.

3. If a ToVersion element is not present, no upper limit exists to the serverversions supported by this metric.

4. If a ToVersion tag is present, the server attribute indicates the highest serverversion supported by this metric. If an update attribute exists, it additionallyqualifies the server version supported by specifying the highest service packor patch supported for that version.

<!ELEMENT FromVersion (EMPTY)><!ELEMENT ToVersion (EMPTY)>

<!ATTLIST FromVersion server CDATA #REQUIREDupdate CDATA "*">

<!ATTLIST ToVersion server CDATA #REQUIREDupdate CDATA "*">

FromVersion and ToVersion element attributes are described in the followingtable.


server numericstring

yes none Specifies a primary server version;for example,<FromVersion server=6.0"/>

5 - 8


The following examples illustrate the use of the FromVersion and ToVersionelements.

Example 1: Metric 10 uses metric "mbean1" in its calculation. This calculatedmetric applies to all WebLogic Server versions. However, the MBean metric onwhich it is based has changed. Originally the MBean for metric 10 wasintroduced on server version 6.0, service pack 1. However in version 6.1, theattribute name changed, and this change remains the same up to the currentserver version, 6.5.

<Metric id="mbean1" alarm="no"><MBean >

<FromVersion server="6.0" update="1"/><ToVersion server="6.099"/><ObjectName>*:*,Type=ExecuteQueue</ObjectName><Attribute>ServicedRequestTotalCount</Attribute>

</MBean><MBean >

<FromVersion server="6.1"/><ObjectName>*:*,Type=ExecuteQueue</ObjectName><Attribute>ServicedRequestCount</Attribute>

</MBean></Metric><Metric id="WLSSPI_0710" alarm="yes">

<Calculation><Formula>

(delta(mbean1) / interval(mbean1))*1000)</Formula>

</Calculation></Metric>

update numericstring

no "*" Specifies a secondary server version,such as "1" for service pack 1.A "*" indicates that no secondaryversion is specified.


5 - 9


Example 2: Using the example above, a decision was made to make metric 10 aper-minute rate instead of a per-second rate as of server version 7.0. The changesthat had to be made to the metric definitions are in bold type. Note that theversions supported by the base metrics and calculated metrics are not necessarilyin sync.

<Metric id="mbean1" alarm="no"><MBean->

<FromVersion server="6.0" update="1"/><ToVersion server="6.099"/><ObjectName>*:*,Type=ExecuteQueue</ObjectName><Attribute>ServicedRequestTotalCount</Attribute>

</MBean><MBean>

<FromVersion server="6.1"/><ObjectName>*:*,Type=ExecuteQueue</ObjectName><Attribute>ServicedRequestCount</Attribute>

</MBean></Metric><Metric id="WLSSPI_0710" alarm="yes">

<Calculation><FromVersion server="6.0"/><ToVersion server="6.999"/><Formula>

(delta(mbean1) / interval(mbean1))*1000)</Formula>

</Calculation><Calculation>

<FromVersion server="7.0"/><Formula>(delta(mbean1) / interval(mbean1))*1000 * 60)

</Formula></Calculation>

</Metric>

5 - 10


METRIC CALCULATIONS

The collector can perform calculations that combine one or more metrics todefine a new metric. These calculations are specified in the Metric DefinitionsXML document using the Formula element as described in the previous section.The result of the calculation is the metric value. See the section “Sample MetricDefinitions Document” for examples of calculated metrics.

SYNTAX

Calculations must use syntax as follows.

" Operators supported are +, -, /, *, and unary minus.

" Operator precedence and associativity follows the Java model.

" Parentheses can be used to override the default operator precedence.

" Allowable operands are metric IDs and literal doubles.

A metric ID can refer to either an MBean metric or another calculated metric.Literal doubles can be specified with or without the decimal notation. The metricID refers to the id attribute of the Metric element in the metric definitionsdocument.

The following example defines a metric whose value is the ratio (expressed as apercent) of Metric_1 to Metric_3.

<Formula>(Metric_1 / Metric_3) *100</Formula>

FUNCTIONS

The calculation parser also supports the following functions. All function namesare lowercase and take a single parameter which must be a metric ID.

" delta returns the result of subtracting the previous value of themetric from the current value.

" interval returns the time in milliseconds that has elapsed since thelast time the metric was collected.

" sum returns the summation of the values of all the instances of amulti-instance metric.

5 - 11


" 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 oftimes per second) for Metric_1.

<Formula>(delta(Metric_1)/interval(Metric_1))*1000</Formula>

Create User-defined Metrics

Now that you have reviewed the structure required for creating UDMs, thesection below shows the tasks to complete. A sample WLS-SPI metricdefinitions file follows this section to provide you with a reference for how thesyntax looks in an actual file and is included on the management server in/var/opt/OV/wasspi/wls/conf/udmmerics_sample.xml.

TASK 1: CREATE A UDM METRIC DEFINITIONS FILE.

The UDM file must be an XML file that follows the format defined by the metricdefinitions DTD file described in the preceding section. The DTD file is namedMetricDefinitions.dtd and is located in the /conf/ directory.

NOTE Because the WLS-SPI DTD file (MetricDefinitions.dtd) is used atruntime, you should not edit, rename, or move it.

In addition, refer to the sample metric definitions file on page 5-16

TASK 2: ADD THE FILE NAME AND LOCATION TO THECONFIGURATION FILE.

In order for the UDM data collection to occur, the WLS-SPI configuration filemust include the name of the user-defined metrics file and its location, precededby the its identifying keyword as shown below:

UDM_DEFINITIONS_FILE = <full path of user metric definitions file>

5 - 12


To add the UDM file name and its location to the WLS-SPI configuration fileinformation:

1. At the OVO console from the Window menu select the Application Bankwindow.

2. In the Application Bank window double-click the WLSSPI applicationgroup and in the next window that appears double-click the WLSSPIAdmin group.

3. Right-click the Config WLSSPI application and select Execute.

4. Edit the file that appears to include the following:

UDM_DEFINITIONS_FILE = <full path of user metric definitions file>

TASK 3: CREATE A MONITOR TEMPLATE FOR THE UDMS.

To run the UDM data collection and establish thresholds for alarming, copy acollector template and monitor template to use as models for your UDMs.Configure the collector template command line (the MIB or Program text box) toinclude the template name and UDM metric number; configure thresholds in themonitor template as appropriate.

5 - 13


Create a UDM Template Group

To set up monitor and collector templates for UDMs, copy and rename anexisting WLS-SPI template group. Then copy and rename every existing templateyou 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. In the Message Source Templates window select the WLS-SPI group youwant to use as a starting point, and click the Copy... button.

3. Name the new group according to how you plan to identify the new monitorand collector templates; for example, you might include UDM to clearlyindicate that the group is made up of custom metric monitors.

4. In the Message Source Template window expand the new template group toshow all templates and select each template you plan to use, click theCopy... button, and rename it according to your naming scheme.

" The names you give the new metric monitor templates in the groupwould contain each new UDM number. For example, a copy ofWLSSPI-0001 could be called WLSSPI-0701.

" The name you give the new collector monitor template would alsocontain the identifying name. You also include the monitor templatename after the -c parameter on the command line as in the example:

wasspi_wls_ca -c UDM-61-15min -m 701

In this case the copied collector template has been renamed:UDM-61-15min

5. Delete all original templates from the new group.

5 - 14


How to Generate automatic actions (reports):

If you have a UDM for which you want an automatic report to be generatedwhen alarm conditions occur, you need to link the condition to the newly createdtemplate. For example, to link metric WLSSPI-701 to the new templateUDM_0701, you would do the following:

1. Select the newly created template and click the Conditions... button, ordouble-click your newly created template (in our example, WLSSPI-0701).

2. Select the condition for which you want to generate an automatic action andclick the Modify... button.

3. In the Condition window in the Automatic Actions/Command box, insertWLSSPI_0701.1 for the existing template as well as the -reportparameter.The entry for a report on all servers on a managed node would be:

wasspi_wls_ca -report -m 0701 -i <$OPTION (server_name)>

or

The entry for a report on the specific instance* that caused the report on themanaged node would be:

wasspi_wls_ca -report -m 0701 -i <$OPTION (server_name)>-o <$MSG_OBJECT>

*The specific instance is identified as the OBJECT in <$MSG_OBJECT>

5 - 15


Sample Metric Definition Document

The following is a sample metric definition document to illustrate how youmight create your own user-defined metrics. This sample document also containsexamples of calculated metrics.

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE MetricDefinitions SYSTEM "MetricDefinitions.dtd">

<MetricDefinitions><Metrics>





<Metric id="WLSSPI_0700" name="UDM_700" alarm="yes"><MBean instanceType="multi">

<FromVersion server="6.0" update="1"/><ObjectName>*:*,Type=ExecuteQueueRuntime</ObjectName><Attribute>PendingRequestCurrentCount</Attribute>

</MBean></Metric>

<Metric id="JVM_HeapFreeCurrent" alarm="no" >

5 - 16


<MBean instanceType="single"><FromVersion server="6.0" update="1"/><ObjectName>*:*,Type=JVMRuntime</ObjectName><Attribute>HeapFreeCurrent</Attribute>

</MBean></Metric><Metric id="JVM_HeapSizeCurrent" alarm="no"><MBean>

<FromVersion server="6.0" update="1"/><ObjectName>*:*,Type=JVMRuntime</ObjectName><Attribute>HeapSizeCurrent</Attribute>

</MBean></Metric>



<Metric id="WLSSPI_0705" name="B705_JVMMemUtilPct"alarm="yes" graph="yes"><Calculation>

<FromVersion server="6.0" update="1"/><Formula>((JVM_HeapSizeCurrent-JVM_HeapFreeCurrent)/JVM_HeapSize Current)*100</Formula>

</Calculation></Metric>



<Metric id="WLSSPI_0701" alarm="yes" report="no"><MBean dataType="string">

<ObjectName>*:*,Type=ServerRuntime</ObjectName><Attribute>State</Attribute><AttributeValueMapping>

<Map from="Running" to="1"/><Map from="Shutdown Pending" to="2"/><Map from="Shutdown In Progress" to="3"/><Map from="Suspended" to="4"/><Map from="Unknown" to="5"/>

5 - 17


</AttributeValueMapping></MBean>

</Metric>



<Metric id="Testing_0992" name="Testing_Metric" alarm="yes"><MBean>

<ObjectName>*:*,Type=ServerRuntime</ObjectName><Attribute>OpenSocketsCurrentCount</Attribute>

</MBean></Metric>

</Metrics></MetricDefinitions>

5 - 18

6

Troubleshooting and Log File Text

Chapter 6: Troubleshooting and Log File TextError Messages

Error Messages

This section provides detailed information on error messages, resulting fromconditions detected in the operation of WebLogic Server SPI, not WebLogicServer itself. The error messages discussed here are all within the WLSSPIMessage Group.

The last two messages are a result of errors in the operation of WebLogic Server SPI. These errorsare identified as belonging to the WLSSPI Message Group (see the MsgGrp column in theillustration below).

6 - 2


WASSPI-1Description: Unable to create the lock file <filename>. File already exists.

Severity: Critical

Help Text: Probable Cause: Temporary lock files are used to avoidcollisions when multiple WebLogic SPI data collector processesattempt to access the same data file. This error occurs when thelock file cannot be created after several attempts because italready exists.

Suggested Action:

If a file by the same name already exists, it may not have beendeleted by a previous run of the WebLogic SPI data collector.You should delete this file manually.

6 - 3


WASSPI-2Description: Cannot access the SPI configuration.

Severity: Critical

Help Text: Probable Cause: A WebLogic SPI configuration file could notbe located or accessed. Either the file does not exist or there wasa problem reading the file.

Suggested Action:

1. Verify that the collector template that runs the WebLogicSPI data collector specifies the correct directory on thecommand line. The option'-Dwasspi.config.dir=<configDirectory>' must be specifiedon command line invocation of the data collector.<configDirectory> must be'/var/opt/OV/wasspi/wls/conf/' on Unix platformsor '\usr\OV/wasspi\wls\conf\' on NT platforms.

2. Verify that the WebLogic SPI configuration files,'SiteConfig' and 'SPIConfig', are located in the directoryspecified on the command line in step 1. If not, run theWebLogic SPI configuration utility from the applicationbank to reinstall the files.

3. Refer to the text following the error message in theWebLogic SPI error log to help identify the underlyingcause of the problem, e.g., an I/O exception.You can viewthe SPI error log for a managed node by using the ViewError File application accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.

6 - 4


WASSPI-3Description: Error parsing command line.

Severity: Critical

Help Text: Probable Cause: The WebLogic SPI data collector commandline is incorrectly specified in a collector template.

Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the data collectorcommand line syntax error. You can view the SPI error logfor a managed node by using the View Error Fileapplication accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.

2. If the error occurred in a collector template that shippedwith the WebLogic SPI, reinstall the SPI.

3. If the error occurred in a collector template not shippedwith the WebLogic SPI, correct the collector template thatcontains the incorrect command line. Refer to theWebLogic SPI User's Guide for more information on theWebLogic SPI data collector command line.

6 - 5


WASSPI-4Description: Error getting the metric definitions.

Severity: Critical

6 - 6


Help Text: Probable Cause:

The WebLogic SPI data collector could not read the metricdefinitions XML document. This error can be caused by amissing configuration property, an I/O error, an XML parsingerror, a missing file, or a corrupted serialized data file.

Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the underlyingcause of the problem. You can view the SPI error log for amanaged node by using the View Error File applicationaccessed from the Application Bank→WLSSPI→WLSSPIAdmin windows. The error message can be identified bythe date/time stamp.

2. If the METRIC_DEFINITIONS_FILE property ismissing from the WebLogic SPI configuration file, reinstallthe SPI and run the WLSSPI Config application accessedfrom the Application Bank→WLSSPI→WLSSPI Adminwindows.

3. If the problem is with the metric definitions file(MetricDefinitions.xml) that is shipped with theWebLogic SPI, then reinstall the WebLogic SPI. Run theSPI configuration utility from the application bank.

4. If the problem is with a user-defined metric definitions filethat is not shipped with the WebLogic SPI, verify that thisXML file adheres to the MetricDefinitions.dtdspecification. Refer to the Chapter 5 for more informationon writing user-defined metrics. Reinstall your user-definedmetric definition file. Run the SPI configuration utility andverify that the UDM_DEFINITIONS_FILE property in theSPI configuration file, is specified correctly.

5. If the underlying error is 'ClassNotFound', this is aninternal error. Report this to HP support.

6 - 7


WASSPI-5Description: Error processing metric <metric_number>.

Severity: Major


An error occurred while trying to collect data or performcalculations for the specified metric.

Suggested Action:

Refer to the text following the error message in the WebLogicSPI error log to help identify the underlying cause of theproblem. The error messages previous to this one will providemore information about the problem. You can view the SPIerror log for a managed node by using the View Error Fileapplication accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.

6 - 8


WASSPI-6Description: The name or port for server # <server_number> is missing from

the WebLogic SPI configuration.

Severity: Major


One or more of the properties, SERVERx_NAME,SERVERx_PORT, is missing from the WebLogic SPIconfiguration file. (x is the server number on the managednode.)

Suggested Action:

1. Run the WebLogic SPI configuration utility from theapplication bank. Verify that you have specified the correctserver name and port information for the WebLogic serverson this managed node.

2. Verify that the properties, SERVERx_NAME andSERVERx_PORT, are specified correctly in the WebLogic SPIconfiguration file('/var/opt/OV/wasspi/wls/conf/ SiteConfig' on

Unix platformsor'/usr/OV/wasspi/wls/conf/SiteConfig' on

Windows platforms)on the managed node in question.

6 - 9


WASSPI-7Description: Unable to contact server <server_name> at url=<URL>,

port=<port>.

Severity: Major


The specified server is not running at the specified port.

Suggested Action:

1. Run the WebLogic SPI configuration utility from theapplication bank. Verify that you have specified the correctserver name and port information for the WebLogic serverson this managed node.

2. Verify that the properties, SERVERx_NAME and

SERVERx_PORT, are specified correctly in the WebLogicSPI configuration file('/var/opt/OV/wasspi/wls/conf/ SiteConfig' onUnix platformsor'/usr/OV/wasspi/wls/conf/SiteConfig' on NT

platforms) on the managed node in question.

3. Verify that the WebLogic server is running on the managednode.

6 - 10


WASSPI-8Description: Error saving graphing or reporting data to file <file_name>.

Severity: Critical


The specified graphing or reporting data file could not be foundor an I/O error occurred when trying to access the file.

Suggested Action:


2. Identify the steps to reproduce the problem.

3. Turn on tracing and reproduce the problem. Refer to theWebLogic SPI User's Guide for instructions on how to turnon tracing.

4. Contact HP support with the information gathered in theprevious steps

6 - 11


WASSPI-9Description: Unable to retrieve property <property_name>.

Severity: Critical


A required property is missing from one of the WebLogic SPIconfiguration files.

Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the missingproperty. You can view the SPI error log for a managednode by using the View Error File application accessedfrom the Application Bank→WLSSPI→WLSSPI Adminwindows. The error message can be identified by thedate/time stamp.

2. From the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility. Verify that you havespecified the correct information for the WebLogic serverson the managed node in question.

3. Verify that the missing property is now specified in theWebLogic SPI configuration file('/var/opt/OV/wasspi/wls/conf/ SiteConfig' onUnix platforms or'/usr/OV/wasspi/wls/conf/SiteConfig' on NTplatforms) on the managed node in question.

6 - 12


WASSPI-10Description: Encountered problem accessing file <filename>.

Severity: Critical


The specified file could not be found, created, or accessed. Thisfile could be a temporary file.

Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the file in questionand the underlying cause of the problem. You can view theSPI error log for a managed node by using the View ErrorFile application accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.

2. Verify that you have enough disk space to create temporaryfiles.

6 - 13


WASSPI-11Description: No servers have been specified in the WebLogic SPI

configuration file.

Severity: Major


The number of WebLogic servers specified in the WebLogicSPI configuration file for the managed node in question is 0.

Suggested Action:

1. From the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility. Verify that you havespecified the correct server name and port information forthe WebLogic servers on this managed node.

2. Verify that the property, NUM_SERVERS, in the WebLogicSPI configuration file('/var/opt/OV/wasspi/wls/conf/ SiteConfig' onUnix platformsor'/usr/OV/wasspi/wls/conf/SiteConfig' on NTplatforms)is set to the number of WebLogic servers on this managednode.

6 - 14


WASSPI-12Description: Opcmon returned an error code of <error_number> for the

command <opcmon_command>.

Severity: Severity


The opcmon process started by the WebLogic SPI collector hasreturned an error (non-zero) exit code.

Suggested Action:


2. Turn on tracing and reproduce the problem. Refer to thebeginning of this chapter for instructions on how to turn ontracing.

3. Contact HP support with the information gathered in theprevious steps.

6 - 15


WASSPI-13Description: Exception occurred while running an opcmon process.

Severity: Critical


The WebLogic SPI data collector attempted to run a process toexecute an opcmon call. Either the process could not be createdor was interrupted.

Suggested Action:

For Unix systems make sure the kernel configurable parametersNPROC and MAXUPRC are set high enough to allow processcreation.

6 - 16


WASSPI-14Description: Unable to find file <file_name>.

Severity: Critical


A file required by the WebLogic SPI data collector could not befound.

Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the file in questionand the underlying cause of the problem.You can view theSPI error log for a managed node by using the View ErrorFile application accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.

2. Reinstall the WebLogic SPI.

3. From the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility.

6 - 17


WASSPI-15Description: Error parsing XML document <file_name>.

Severity: Critical


An error occurred while parsing the specified XML document.

Suggested Action:

1. Refer to the text following the error message in the WebLogicSPI error log to help identify the underlying cause of theproblem. You can view the SPI error log for a managed node byusing the View Error File application accessed from theApplication Bank→WLSSPI→WLSSPI Admin windows. Theerror message can be identified by the date/time stamp.

2. If the XML document was provided by the user, correct thedocument. Refer to the WebLogic SPI User's Guide for moreinformation about the correct format for a user-defined metricdefinition document.

3. If the XML document is a document that is shipped with theWebLogic SPI, from the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility to reinstall the WebLogicSPI configuration files.

6 - 18


WASSPI-16Description: A bad filter (<filter_value>) was specified for metric

<metric_number>.

Severity: Major


A metric filter is incorrectly specified in the metric definitionsXML document.

Suggested Action:

1. If the metric is specified in an XML document that wasprovided by the user, correct the document. Refer to theWebLogic SPI User's Guide for more information about thecorrect format for a user-defined metric definition document.

2. If the metric is a pre-defined metric that is shipped with theWebLogic SPI, from the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility in order to reinstall theWebLogic SPI configuration files.

6 - 19


WASSPI-17Description Could not access MBean server on server <server_name> at

url=<URL>, port=<port_number>.

Severity: Critical


A problem occurred while the WebLogic SPI data collector wasrequesting access to the JMX MBean server on the WebLogicserver. This could be caused by:

1. The JNDI lookup to find the JMX MBean server in theapplication server failed.

2. The login name specified in the WebLogic SPIconfiguration file does not have the correct permissions inthe application server.

3. The password specified in the WebLogic SPI configurationfile is incorrect.

6 - 20


Suggested Action:


2. From the Application Bank selectWLSSPI→WLSSPI Admin→ Config WLSSPI to run theWebLogic SPI configuration utility. Verify that the loginname and password are correct for the server in question.

3. In the WebLogic Administration Console, verify that theuser is a valid WebLogic user and has the correctpermissions. To set the correct permissions, refer to theWebLogic SPI User's Guide.

4. In the WebLogic Administration Console, verify that theMBean server(weblogic.management.home.<server_name>) is in theJNDI tree of the server in question. Right-click on theserver in the left pane to view the JNDI tree. If it is notthere, restart the WebLogic server.

6 - 21


WASSPI-18Description: Data logging failed: ddflog returned error <error_number>.

Severity: Critical


The ddflog process started by the WebLogic SPI datacollector returned a non-zero error code.

Suggested Action:




6 - 22


WASSPI-19Description: Encountered problem instantiating XSLT transformer with

<file_name>.

Severity: Major


The XSL document that specifies the auto action report outputcontains errors.

Suggested Action:



6 - 23


WASSPI-20Description: Encountered problem creating report for metric

<metric_number>.

Severity: Major


An error occurred while producing a text report for the specifiedmetric.

Suggested Action:



6 - 24


WASSPI-201Description: File <filename> not found.

Severity: Critical

Help Text: Probable Cause: A configuration file could not be found.

Suggested Action:


2. Verify that the correct information has been specified for theWebLogic servers on the managed node on which the error occurred.

6 - 25


WASSPI-202Description: Cannot read file <filename>.

Severity: Critical


1. A file could not be opened or it could not be found.

2. Permissions may be incorrect or a directory may be corrupt.

Suggested Action:


2. Verify that you have specified the correct information for theWebLogic servers on the managed node on which the erroroccurred.

2. Verify that the permissions are correct for the OVO user toread this file.

6 - 26


WASSPI-203Description: Cannot write file <filename>.

Severity: Critical


Permissions may be incorrect, or a file or directory may becorrupt.

Suggested Action:



3. Verify that the permissions are correct for the OVO user towrite this file.

6 - 27


WASSPI-204Description: Error sending opcmsg <message>.

Severity: Critical


There was a problem running opcmsg. ‘opcmsg’ may bemissing or not have permissions to execute (OVO installationerrors) or the system process table may be full.

Suggested Action:

Confirm that OVO is properly installed and deployed to themanaged node.

Ensure that the process table is not full. If it is, consider havingthe system administrator increase it.

6 - 28


WASSPI-205Description: Error sending opcmon <command>.

Severity: Critical


There was a problem running opcmon. ‘opcmon’ may bemissing or not have permissions to execute (OVO installationerrors) or the system process table may be full.

Suggested Action:

Confirm that OVO is properly installed and deployed to themanaged node.

Ensure that the process table is not full. If it is, consider havingthe system administrator increase it.

6 - 29


WASSPI-206Description: Cannot read directory <directory>.

Severity: Critical


The permissions on the directory prevent the OVO user fromreading it or the directory is corrupt.

Suggested Action:

Verify that the permissions are correct for the OVO user for thisdirectory.

6 - 30


WASSPI-207Description: Cannot move <filename> to <filename>.

Severity: Critical


1. Insufficient permissions.

2. Insufficient disk space.

3. File table problems.

Suggested Action:

1. Verify that the permissions are correct for the OVO user.

2. Verify that there is enough disk space to create files.


6 - 31


WASSPI-208Description: WLSSPI must be configured before it can be used.

Severity: Critical


The SPI has not been configured on this node

Suggested Action:



3. Run the Verify utility from the Application Bank to confirmthat the SPI has been successfully configured.

6 - 32


WASSPI-209Description: Cannot contact WebLogic Server.

Severity: Critical


1. The server could be down or not responding.

2. The SPI may be configured incorrectly.

Suggested Action:

1. Verify that WebLogic Server is up and running properly.



4. Run the Verify utility from the Application Bank to confirmthat the SPI has been successfully configured.

6 - 33


WASSPI-210Description: Cannot configure WLSSPI.

Severity: Critical


The SPI configuration process failed.

Suggested Action:

1. Refer to the text following the error message in the WebLogicSPI error log to help identify the underlying cause of theproblem. The error messages previous to this one will providemore information about the problem. You can view the SPIerror log for a managed node by using the 'View Error File'application in the Application Bank window. The error messagecan be identified by the date/time stamp.

2. Reinstall the SPI.


6 - 34


WASSPI-211Description: Cannot create directory <directory>.

Severity: Critical


There are insufficient permissions for the OVO user to createthe directory or there is insufficient disk space.

Suggested Action:

Verify that the permissions are correct for the OVO user for thisdirectory. Verify that there is enough disk space.

6 - 35


WASSPI-212Description: Cannot configure WLSSPI.

Severity: Critical


The SPI configuration process failed.

Suggested Action:

1. Refer to the text following the error message in the WebLogicSPI error log to help identify the underlying cause of theproblem. The error messages previous to this one will providemore information about the problem. You can view the SPIerror log for a managed node by using the 'View Error File'application in the Application Bank window. The error messagecan be identified by the date/time stamp.



6 - 36


WASSPI-213Description: Improper parameters to program <name>. Usage: <usage>.

Severity: Critical


The parameters to the program are incorrect.

Suggested Action:

Correct the parameters.

6 - 37


WASSPI-214Description: Cannot run program <program name>.

Severity: Critical


The program failed to run. It may be missing, permissions maybe incorrect, the process table may be full.

Suggested Action:

1. Verify that the file exists. If it is a SPI program and the file ismissing, reinstall the SPI and run the WebLogic SPIconfiguration utility from the Application Bank.

2. Verify that the permissions are correct for the ITO user.

6 - 38


WASSPI-215Description: A WebLogic server was not found in <directory>.

Severity: Critical


The directory specified as WL_HOME in the SPI configuration

does not exist on the managed node.

Suggested Action:

1. Verify that WebLogic is installed on the managed node.

2. Run the WebLogic SPI configuration utility from theApplication Bank.

3. Verify that the correct information has been specified forWL_HOME on the managed node on which the error occurred.

6 - 39


WASSPI-216Description: Configuration variable <name> missing for server

<server_name>.

Severity: Critical


A required SPI configuration variable was not found.

Suggested Action:

1. Run the WebLogic SPI configuration utility from theApplication Bank.

2. Verify that the correct information has been specified in theconfiguration for the managed node on which the erroroccurred.

6 - 40


WASSPI-218Description: WebLogic monitoring has been turned OFF for

<server_name>.

Severity: Warning


Collection has been turned off for the specified server

Suggested Action:

If desired, collection can be turned on by setting COLLECT =ON in the SiteConfig file in the SPI configuration directory onthe managed node. The configuration directory is'/var/opt/OV/wasspi/wls/conf/' on Unix platforms or'/usr/OV/wasspi/wls/conf/' on NT platforms.

6 - 41


WASSPI-219Description: WebLogic monitoring has been turned ON for <server_name>.

Severity: Critical


Collection has been turned on for the specified server

Suggested Action:

If desired, collection can be turned off by setting COLLECT =OFF in the SiteConfig file in the SPI configuration directory onthe managed node. The configuration directory is'/var/opt/OV/wasspi/wls/conf/' on Unix platforms or'/usr/OV/wasspi/wls/conf/' on NT platforms.

6 - 42


WASSPI-220Description: This feature only applies to WebLogic 5.1.

Severity: Warning


User attempted to perform a function on a WebLogic 6 serverthat only applies to WebLogic 5 servers.

Suggested Action:

This function can only be performed on a WebLogic Serverversion 6.0 and above.

6 - 43


WASSPI-221Description: <file_name> does not exist.

Severity: Critical


The specified file does not exist. If it is a log file, no entrieshave ever been logged to it. If it is a property file, then it has notbeen configured.

Suggested Action:

Log files: If there have never been any entries written to the file,no action is necessary. Otherwise, run the WebLogic SPIconfiguration utility from the Application Bank.

Property files: Run the WebLogic SPI configuration utility fromthe application bank.

6 - 44


WASSPI-222Description: <file_name> is empty.

Severity: Critical


The specified file is empty. If it is a log file, no entries haveever been logged to it, or the entries have been cleaned out. If itis a property file, then it is not properly configured.

Suggested Action:

If the file is a configuration file, run the WebLogic SPIconfiguration utility from the Application Bank.

6 - 45


WASSPI-223Description: Cannot read <file_name>.

Severity: Critical




Suggested Action:

1. Run the WebLogic SPI configuration utility from theApplication Bank. Verify that you have specified the correctinformation for the WebLogic servers on the managed node onwhich the error occurred.

2. Verify that the permissions are correct for the ITO user toread this file.

6 - 46


WASSPI-224Description: ddfcomp returned an error configuring <name>.

Severity: Critical


‘ddfcomp’ returned an error. This could be because neitherMeasureWare nor CODA is installed on the system or becausean error configuring MeasureWare or CODA.

Suggested Action:

1. If MeasureWare nor CODA is not installed, this error can beignored.




6 - 47


WASSPI-225Description: No logfiles were found. Did you run ‘Config WLSSPI’?

Severity: Critical


The logfile list is empty.

Suggested Action:



6 - 48


WASSPI-226Description: Cannot read file <file_name>.

Severity: Critical




Suggested Action:



3. Verify that the permissions are correct for the ITO user toread this file.

6 - 49


All Other ErrorsDescription: An unknown error appears in the WebLogic SPI error log.

Severity: Major

Help Text: Suggested Action:

1. Refer to the text following the error message in theWebLogic SPI error log to help identify the problem. Youcan view the SPI error log for a managed node by using theView Error File application accessed from the ApplicationBank→WLSSPI→WLSSPI Admin windows. The errormessage can be identified by the date/time stamp.




6 - 50

Appendix

AppendixDirectory Locations

Directory Locations

You can find WLS-SPI configuration files and error logs in directories asfollows.

" Management servers — HP-UX or Solaris:

Configuration file is in:/opt/OV/wasspi/wls/conf

" Managed nodes — HP-UX or Solaris:

Configuration file is in:/var/opt/OV/wasspi/wls/conf

Error logs are in:/var/opt/OV/wasspi/wls/log

" Managed nodes — NT:

Configuration file is in:\usr\ov\wasspi\wls\conf

Error logs are in:\usr\ov\wasspi\wls\log

Appendix - 2

Index

A

actionsautomatic, description of 3-8operator-initiated 3-8

Annotations, function of 1-17Application Bank

reports generated from 3-25reports included in 1-17

applicationsConfig WLSSPI, description of 1-12deleting 2-20description of WebLogic SPI group 1-11general description of 1-10listing of and description of each 1-11WLSSPI Admin group, description of 1-11

automatic action reports 1-17generating 5-15

automatic actionsgenerating for customized metrics 5-15

C

cluster metrics, graph for, table listing allgraphs

cluster metrics, table with list of 4-10collection intervals

changing for all servers 3-15changing for selected metrics 3-16template groups, as organized by 1-14

collector templatedescription of 1-14

collector/analyzerdescription of 3-5what it does 1-14

commandwasspi._wls_ca, description of 3-5

componentsinteraction of the WebLogic Server SPI 1-18overview of WebLogic Server SPI 1-10

conditionsin templates, changing 3-7

Config WLSSPI description of 1-12configuration file

complete text of 2-10inserting entries 1-18

configuration file directory location 6-2customizations

creating new templates 3-19suggestions for 1-3

D

deinstallationdeleting WLS-SPI templates 2-19removing WLS-SPI 2-18removing WLS-SPI from managed nodes 2-18

directorieslocations for configuration file and error logs 6-2

duration setting, description 3-7

E

error log directory location 6-2error messages

undocumented, what to do 6-50WASSPI-01 6-3WASSPI-02 6-4WASSPI-03 6-5WASSPI-04 6-6WASSPI-05 6-8WASSPI-06 6-9WASSPI-07 6-10WASSPI-08 6-11

i

WASSPI-09 6-12WASSPI-10 6-13WASSPI-11 6-14WASSPI-12 6-15WASSPI-13 6-16WASSPI-14 6-17WASSPI-15 6-18WASSPI-16 6-19WASSPI-17 6-20WASSPI-18 6-22WASSPI-19 6-23WASSPI-20 6-24, 6-25, 6-26, 6-27, 6-28,

6-29, 6-30, 6-31, 6-32, 6-33, 6-34,6-35, 6-36, 6-37, 6-38, 6-39, 6-40,6-41, 6-42, 6-43, 6-44, 6-45, 6-46,6-47, 6-48, 6-49

G

graphsEJBs, drawing for 4-10generating with Reporter’s graphing capabilities

4-8generating with the HP OpenView graphing tool

4-2how to access 1-8illustration of one 1-8instructions for manually generating 4-9launching display within Web browser 4-10list of metrics for server status graph 4-9showing alarm conditions 4-8specifying date range within 4-11templates available for 4-9transaction metrics, table with list of 4-10

graphs, instructions for enabling 2-5graphs, Performance Manager 4 requirement for 4-2

H

HP OpenView Reporter, integrating WLS-SPI with4-2HP Performance Manager, using WLS-SPI with 4-2

I

installationconfiguring WLS-SPI on managed nodes 2-10on the Management Server 2-3summary of 2-3

instancesdifferentiating server instances within a collector

template 3-14instruction text, where to find it 1-6

J

jWindows managed nodesNT 4, special setting for 2-4

L

logfile templatesdescription of 3-4

M

Message Source template groups, description ofWLS-SPI groups 3-3messages

grouping according to type 1-15instruction text with 1-6template configuration for 3-8

messages templatedescription of 3-4

messages, how they are displayed 1-5metric element attributes for creating user definedmetrics (UDMs) 5-3metrics

modifying collections in the collector template3-12

metrics templatesdescription of 3-3

monitor templateschanging 3-6deleting 2-19description of 1-18, 3-3, 3-4

ii

N

NT 4.0 settingWLS-SPI program executions on NT 4 systems

2-4

O

operator actionsgraphs generated from 4-8

P

Performance Manager, using WLS-SPI with 4-2

R

removing WLS-SPI software 2-18Reporter

integrating WLS-SPI to work with 4-2setting up WLS-SPI to work with 4-3

reportsApplication Bank generated 1-17, 3-22, 3-25automatic action reports 1-17general description of automatic and operator-ini-

tiated 1-10generated from HP OpenView Reporter 4-5generating for customized metrics , modifying

monitor templates 5-15sample automatic action 3-26showing WebLogic Server availability 4-6showing WebLogic Server data for single systems

4-6showing WebLogic Server performance 4-5types and how generated 1-16using HP OpenView Reporter to generate 4-2

reports (automatic action)how they are generated 3-22

reports, automatic actionhow to link to condition 5-15

reports, types included with WLS-SPI 1-7

S

server statusgraphing metrics showing informaton for 4-9

serverssetting thresholds for different 3-18

severity level of alert, changing 3-7swinstall

restoring defaults with 3-21swremove

using to remove WLS-SPI 2-18

T

tag optioncreating custom template groups with 3-19

TEMP environment variablesetting for NT 4.0 managed nodes 2-4

template groupschanging collection intervals 3-16creating custom with the tag parameter 3-19description 3-3messages, use of 3-4

templatesactions, description 3-8continuously setting, description of 3-9customizing message displayed for alerts 3-8customizing message text 3-8customizing thresholds 3-7customizing with the tag option 3-19deleting 2-19distributing 2-16general description of 1-10modifying for databases 3-6monitor, description of 1-14operator-initiated actions 3-8re-installing defaults 3-21resetting thresholds, description of 3-9thresholds without reset, description 3-9WLSSPI-Message Group 1-15

thresholds

iii

customizing 3-7settings for different servers 3-18

thresholds, exceededviewing graphs resulting from 4-8

U

UDMs, please see user defined metricsuser defined metrics

MBean Element, description of 5-4metric definitions element, description of 5-3metric element atttributes, description of 5-3metric element, description of 5-3overview of 5-2sample XML file for 5-16

W

wasspi_wls_ca, description of 3-5WASSPI-01, error message 6-3WASSPI-02, error message 6-4WASSPI-03, error message 6-5WASSPI-04, error message 6-6WASSPI-05, error message 6-8WASSPI-06, error message 6-9WASSPI-07, error message 6-10WASSPI-08, error message 6-11WASSPI-09, error message 6-12WASSPI-10, error message 6-13WASSPI-11, error message 6-14WASSPI-12, error message 6-15WASSPI-13, error message 6-16WASSPI-14, error message 6-17

WASSPI-15, error message 6-18WASSPI-16, error message 6-19WASSPI-17, error message 6-20WASSPI-18, error message 6-22WASSPI-19, error message 6-23WASSPI-20, error message 6-24, 6-25, 6-26, 6-27,6-28, 6-29, 6-30, 6-31, 6-32, 6-33, 6-34, 6-35,6-36, 6-37, 6-38, 6-39, 6-40, 6-41, 6-42, 6-43,6-44, 6-45, 6-46, 6-47, 6-48, 6-49WebLogic Server

instances, differentiating within the collector tem-plate 3-14

WebLogic Server SPIcomponents

overview 1-10general description of 1-4

WLSSPI Message Groupsdescription of templates group 1-15

WLS-SPI, removing 2-18

iv

Documents

HP OpenView Operations SMART PLUG-INFOR EB OGIC ERVER · 2010. 6. 24. · User’s Guide B9145-90000 Release A.01.00.00. ii Legal Notices Hewlett-Packard makes no warranty of any