HP Operations Smart Plug-in for IBM WebSphere Application Server Release Notes

for HP Operations Manager for Windows®


Software version: 7.04

Publication date: January 2011

This document is an overview of the changes made to HP Operations Smart Plug-in for IBM WebSphere Application Server (WebSphere SPI) for HP Operations Manager (HPOM) for Windows 9.00. 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
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

WebSphere SPI for HPOM for Windows 9.00 contains the following new features and other changes:

Installation Notes

Installation instructions for installing the WebSphere SPI, are documented in the HP Operations Smart Plug-in for IBM WebSphere Application Server Installation and Configuration Guide provided in PDF (.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 versions at this location: http://support.openview.hp.com/selfsolve/document/KM323488.

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.

Enhancements

QCCR1A112970: Enhance WebSphere SPI to support WebSphere Portal Servers.

QCCR1A101543: Enhance WebSphere SPI to discover WebSphere on Hypervisor Edition.

Fixes

 

QCCR1A105280: Enable WebSphere SPI 7.00 to work with OMi 9.0.

QCCR1A107795: The script wasspi_perl_su fails on AIX node.

QCCR1A107796: The files ovosysdetect_WBSSPI.pl and ovosysdetect_WBSSPIRemote.pl fail to execute on AIX nodes.

QCCR1A107797: Logfile match rules are incorrect for WebSphere Text Logs 7.x policy.

QCCR1A108345: Config.pm and Domain.pm bundled with WASSPIs conflict with SI SPI.

QCCR1A110083: The WebSphere SPI 7.x does not support instance-based licensing.

QCCR1A112923: SiteConfig does not get deployed on the nodes in Clustered Management Server.

QCCR1A114453: Metric 0001 alert does not work as expected.

QCCR1A115761: ThreadpoolAveSize metric value is less than the Threadpool active thread.

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.

When the server permanent licenses are installed, the remote license count becomes zero,

PROBLEM: If the permanent licenses are installed for WebSphere SPI, the remote license count resets to zero.

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 Self Healing Service (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 preceded 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 if 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 9.00) 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:
  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, follow these steps:
  1. In the /var/opt/OV/wasspi/wbs/conf/SPIConfig file, set the DATA_LOGGING_EXECUTABLE_NAME
    property after the “#--------- Dynamic definitions -----------“ entry. This property 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 value /opt/perf/bin/dsilog. If you are running CODA, set the property to the 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

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.1 or 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: 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).

Limitations

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

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

 

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

Trademark Notices

Java is a registered trademark of Oracle and/or its affiliates.
Windows® is U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Adobe® is a trademark of Adobe Systems Incorporated.