HP Operations Smart Plug-in for IBM WebSphere Application Server

Release Notes

for HP Operations Manager for Windows®

Software version: 7.00

Publication date: December 2009

This document is an overview of the changes made to HP Operations Smart Plug-in for IBM WebSphere Application Server for HP Operations Manager for Windows versions 8.10 and 8.16. It contains important information that is not included in the manuals or Online Help. You can find the following information in this document:

What's New in This Release?
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Updates
Documentation Errata
Support
Legal Notices

Hidden Text

To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.

Hidden text example

This text was hidden. Now it is visible. Click the link to hide the text.

Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.

What's New in This Release

HP Operations Smart Plug-in for IBM WebSphere Application Server for HP Operations Manager for Windows contains these new features and other changes:

Support for distributed network deployer scenario for WebSphere Application Servers 7.0

Support for HP Operations Manager i (HP OMi) 8.10
For more information on how the SPI works with HP OMi, see HP Operations Manager i 8.10 documentation.

WebSphere SPI 7.00 is the last release that supports DCE agents

PMI Counter is not supported for WebSphere Application Server version 6.0 and above

Enhanced log file monitoring

Enhanced error logging

Implemented monitoring of discovery and collector error logs

Replaced the Discover WebSphere and Configure WBSSPI tools with a single tool Discover or Configure WBSSPI tool to enable both discovery and configuration

Enhanced Configuration Editor

Introduced golden metrics that monitor the basic functionality of the WebSphere Application Server

Added the following new metrics for monitoring JVM, EJB, ThreadPool, and Connection Pool

Metric Name	Description
I807_JVMMemFreePct	Percent of JVM Free Memory available
I808_JVMCpuUsagePct	The CPU Usage of the Java virtual machine
I809_GCIntervalTime	The average garbage collection value in seconds between two garbage collections
I810_MsgBackoutRate	The rate at which the messages failed to be delivered to the bean onMessage method (message driven beans)
I811_ReturnDiscardRate	The rate at which the returning object was discarded because the pool was full (entity and stateless)
I812_ThrdPoolHungRt	The rate at which the threads are declared hung
I813_CncrntThrdPoolHngCt	The number of concurrently hung threads
I814_PrprdstcachdiscrdRt	The rate at which the prepared statements are discarded by the least recently used (LRU) algorithm of the statement cache

Removed the following metrics:
- WBSSPI_0003
- WBSSPI_0004
- WBSSPI_0803
- WBSSPI_0804
- WBSSPI_0805

For more information about customer-related enhancements and software fixes, see Enhancements and Fixes.

Installation Notes

Installation instructions for installing WebSphere SPI, are documented in the HP Operations Smart Plug-in for IBM WebSphere Application Server Installation and Configuration Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's DVD media in the Documentation directory.

Support Matrix

Refer to the Support Matrix (SUMA) link to find the Support Matrix for this product that lists the supported HP Operations Manager, application servers, HP Performance Agent, HP Performance Manager, and HP Reporter version at this location: HP Support matrices. For information on the archived obsolescence programs, refer to the Obsolescence Archive link.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

Enhancements and Fixes

To display details about each software enhancement or fix, click the reference number link to go to the HP Software Support web site. The first time you click a link, you must enter your HP passport information. To set up your passport profile, go to: HP Support.

Fixes

QXCR1000785668 : <5.10><WEBSPHERE 6.0 ><OVOW/WIN2003> <WIN2003><SystemOut.log errormessage>
QCCR1A90228: Documentation defect for PMI Counters for UDM
QCCR1A89015: OMi Support Required for WBSSPI
QCCR1A92743: WBSSPI 6.x collector not working in non ND mode
QCCR1A91990: wasspi_wbs_files wbstextlogs shows repeated files in the command output
QCCR1A99355: Documentation Defect : Metric 220-225 do not work due to specific bean is not installed

Known Problems, Limitations, and Workarounds

This release contains the following unresolved problems. Workarounds are provided wherever applicable. Click on the problem statement to see the complete description.

WBSSPI_0220 to WBSSPI_0225 returns a valid value only if Entity Beans are present in the application(s) deployed on the WebSphere Application Server(s)

Limitation:

The metrics WBSSPI_220 to WBSSPI_225 returns a valid value only if Entity Beans are present in the application(s) deployed on the WebSphere Application Server(s).

Error message appears if the instrumentation files of more than one Web Application Server SPI are deployed on the same node

PROBLEM:

If the instrumentation files of more than one Web Application Server SPI are deployed on the same node, an error message (File name collision detected) appears in the HPOM message browser whenever a multiple occurrence of an instrumentation file is identified.

Error message appears when the instrumentation files of the WebSphere SPI and SHS component are deployed on the same node

PROBLEM: When the instrumentation files of the WebSphere SPI and SHS component are deployed on the same node, an error message (File name collision detected) appears in the HPOM message browser whenever a multiple occurrence of XMLParser.pm is identified. This does not affect the configuration. You can ignore this error message.

Discovery and collection is getting delayed in a network deployer scenario

PROBLEM:

In a Network Deployer scenario, the time taken for the discovery and the collection process to complete is delayed if one or more federated nodes are configured to the deployment manager.

Policy is not deployed if you install the same version of the policy twice

PROBLEM:	If you install the same version of a policy twice, the policy is not deployed and the discovery process stops. The policy name is preceeded by '*'.
WORKAROUND:	Select Policy Management –> Agent policies grouped by type. Select the policy which was installed twice. Right-click the policy and select All Tasks –> Remove the Latest version.

Discovery, Discover or Configure WBSSPI tool hangs

PROBLEM:	The Discovery policy, the Discover or Configure WBSSPI tool hangs.
CAUSE:	When you run any of these components the configuration file is locked so that the file cannot be overwritten. If you select STOP in the Console Status window or these components are stopped while running because of any other reason (for example, a failover), the lock is not removed from the configuration file. When you start any of these components again, the component waits for the lock to be removed before it can continue.
WORKAROUND:	Remove the lock directory on the management server: `<OvOWShareInstallDir> \SPI-Share\wasspi\wbs\conf\SiteConfig.lock` where `<OvOWShareInstallDir >` is typically (for HPOM for Windows 8.10) `C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared.` The locking mechanism automatically deletes the lock directory after two hours.

The output file created by Self-Healing Info tool is hidden

PROBLEM:	When the Self-Healing Info tool is run on a Windows managed node, the output file may be hidden.
WORKAROUND:	If you do not see the file, do the following on the managed node: Open Windows Explorer. From the Tools menu, select Folder Options. Click on the View tab. Under Hidden files and folders, select Show hidden files and folders.

On a Solaris managed node, the ddflog and dsilog processes hang

PROBLEM: On a Solaris managed node, the ddflog and dsilog processes hang. The error message
WASSPI-1: Unable to create the lock file /var/opt/OV/wasspi/wbs/datalog/ddflog.lck. File already exists. is reported and running the command ps –l shows that the ddflog_coda and ddflog or dsilog processes are hung.

WORKAROUND:

On each Solaris managed node on which the problem occurs, do the following:

In the /var/opt/OV/wasspi/wbs/conf/SPIConfig file, set the DATA_LOGGING_EXECUTABLE_NAME
property after the “#--------- Dynamic definitions -----------“ entry. DATA_LOGGING_EXECUTABLE_NAME explicitly sets the data logging program that is used (normally, the collector automatically determines the data logging program to use).

If you are running OVPA, set the property to the following value:
DATA_LOGGING_EXECUTABLE_NAME=/opt/perf/bin/dsilog If you are running CODA, set the property to the following value:
DATA_LOGGING_EXECUTABLE_NAME=/opt/OV/bin/OpC/monitor/ddflog_coda

Kill the hung ddflog_coda and ddflog or dsilog processes. Example excerpt from the SPIConfig file after setting the property:
UDM_GRAPH_CAPACITY=50000 UDM_PERF_CAPACITY=50000 #--------- Dynamic definitions ----------- DATA_LOGGING_ENABLED=TRUE DATA_LOGGING_EXECUTABLE_NAME=/opt/perf/bin/dsilog

Error message appears for managed nodes running Red Hat Linux 4

PROBLEM:	For a managed node running Red Hat Linux 4 or SuSe Linux 9.1or 9.2, both discovery and metric threshold monitor alarming or one of them is not functioning and the following error message is found in the SPI error log: `* glibc detected * double free or corruption: 0x0937d008 ***`
WORKAROUND:	On the OVO agent, set the `MALLOC_CHECK_ environment` variable to 0 (zero) and restart the agent.

The uninstallation process does not uninstall WebSphere SPI completely

PROBLEM:	In a cluster environment, the uninstallation process may not remove the SPI for WebSphere tool group, policy group, and some policies.
WORKAROUND:	Manually delete the tool group, policy group and policies from the management server console.

Discovery times out on the node

PROBLEM:	The Discovery times out on the node in a network deployer scenario.
WORKAROUND:	Change the value for timeout for agtrep on the node. Run the following command: `ovconfchg –edit`. Change the value of ACTION_TIMEOUT to a higher value so that Discovery does not timeout. For example: Change ACTION_TIMEOUT=3 to ACTION_TIMEOUT=20 (or more minutes).

Documentation Updates

The first page of this release notes document contains the following identifying information:

Version number, which indicates the software version.
Publish date, which changes each time the document is updated.

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals

To retrieve a document, select the:

Product name.
Version list.
Operating System.
Preferred Language.
Document title.
Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

Documentation Errata

The following troubleshooting information is missing in the Installation and Configuration Guide for HP Operations Smart Plug-in for IBM WebSphere Application Server.

In the SiteConfig file for Windows managed nodes, "\" character is removed from the value for HOME and JAVA_HOME

PROBLEM:	In the SiteConfig file for Windows managed nodes, the value for HOME and JAVA_HOME appears as: HOME=`CProgram FilesIBMWebSphereAppServer` JAVA_HOME=`CProgram FilesIBMWebSphereAppServerjava` The "\" character is removed from the path.
WORKAROUND:	Replace the character "\" with "/" or "\\" in the path for HOME and JAVA_HOME. For example, HOME=`C:/Program Files/IBM/WebSphere/AppServer` or HOME=`C:\\Program Files\\IBM\\WebSphere\\AppServer`

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

Search for knowledge documents of interest
Submit and track progress on support cases
Submit enhancement requests online
Download software patches
Manage a support contract
Look up HP support contacts
Review information about available services
Enter discussions with other software customers
Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

To register for an HP Passport ID, go to: HP Passport Registration.

Legal Notices

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

For information about third-party license agreements, see the spi-thirdparty-license-agreements directory on the product installation DVD-ROM.

Trademark Notices

Java™ is a US trademark of Sun Microsystems, Inc.
Windows® is U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.