HP Operations Smart Plug-in for IBM WebSphere Application Server

 

Release Notes

 

for HP Operations Manager for Windows®

Software version: 6.10

Publication date: October 2008

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

Support for distributed network deployer scenario for WebSphere Application Servers 6.1 (Logfile monitoring is not supported in this release.)

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

You can find the Support Matrix for this product that lists all software and hardware requirements at this location: HP Support matrices.

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.

The WebSphere Application Server versions and the supported managed OS versions are listed below:

WebSphere Application Server version Managed Node OS and Version
WebSphere Application Server 4.0, 4.1 HP-UX 11.11
AIX 5.2
Solaris 8
Windows 2000
WebSphere Application Server 5.0 HP-UX 11.11, 11.23
AIX 5.2
Solaris 8, 9, 10
Windows 2000, 2003, 2003 IA64
WebSphere Application Server 5.1

HP-UX 11.11, 11.23, 11.23 IA64
AIX 5.2, 5.3
Solaris 8, 9, 10
Windows 2000, 2003, 2003 IA64
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux ES 9.0 (32 bit)
WebSphere Application Server 6.0 HP-UX 11.11, 11.23, 11.23 IA64
AIX 5.2, 5.3
Solaris 8, 9, 10
Windows 2000, 2003, 2003 IA64
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux ES 9.0 (32 bit)
WebSphere Application Server 6.1

HP-UX 11.11, 11.23, 11.23 IA64, 11.31 IA64, 11.31 PARISC
AIX 5.2, 5.3
Solaris 8, 9, 10
Windows 2000, 2003, 2003 IA64
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux ES 9.0 (32 bit), 9.0 (IA64)

NOTE: For complete support for WebSphere Application 6.1 on Windows nodes, you must update WebSphere's SDK to Pack 4. If you do not make these changes the collector will fail.

Software and Hardware Requirements

Before installing WebSphere SPI, make sure that your system meets the following minimum requirements:

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.

Fix

QXCR1000765253: DOC: Websphere Application Server 6.1 : Update java SDK 1.5 to level "SR4"

 

Known Problems, Limitations, and Workarounds

This release contains certain unresolved problems, some limitations, and there are workaround to help solve certain problems.

Discovery, Discover WebSphere, and (or) Configure WBSSPI tool hangs

PROBLEM: The Discovery policy, the Discover WebSphere tool, and (or) the 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: 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.

Tracing stops or the collector hangs when tracing is on

PROBLEM: If tracing is enabled, when the first 20 MB trace file limit is reached, tracing either stops or the collector hangs and stops monitoring the web application servers.
WORKAROUND: Enable tracing for a short duration of time (for example, 5-6 hours) because the 20 MB limit of the trace file is reached in approximately 7 hours.

Discover WebSphere or Configure WBSSPI tool may misplace the SPI configuration file on a managed node

PROBLEM: If multiple managed nodes are selected when running the Discover WebSphere or Configure WebSphere tools, or if the Discover WebSphere and Configure WebSphere tools are run at the same time, the SPI may report errors for one or more selected managed nodes because the SPI configuration file for one or more managed nodes are misplaced.
WORKAROUND: Run the Configure WebSphere tool for each managed node that is reporting errors (run the tool on each managed node one at a time).

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:
  1. Open Windows Explorer.
  2. From the Tools menu, select Folder Options.
  3. Click on the View tab.
  4. 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:
  1. 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).
    2. 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
  2. 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

SPI's configuration log on a managed node grows without being managed for size

PROBLEM: Information is appended to …/wbs/log/config.log file whenever the SPI's configuration is run (either manually or when the discovery process finds a change that requires configure to run such as a WebSphere Application server being added or removed). Unless there are frequent changes to the environment requiring reconfiguration, this should not be a problem.
WORKAROUND: Manually delete the file if it gets too large.

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.
  1. Run the following command: ovconfchg –edit.
  2. 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:

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:

  1. Product name.
  2. Version list.
  3. Operating System.
  4. Preferred Language.
  5. Document title.
  6. 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

There are no known errors in the WebSphere Application Server SPI documentation.

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:

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

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.

Legal Notices

©Copyright 2008 Hewlett-Packard Development Company, L.P.

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 %ovinstalldir%/license-agreements/SPI 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.

© 2007–2008 Hewlett-Packard Development Company, L.P.