HP Operations Smart Plug-in for BEA WebLogic 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 BEA WebLogic Server for HP Operations Manager for Windows. It contains important information that is not included in 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
Local Language Support
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 BEA WebLogic Server for HP Operations Manager for Windows provides additional support to the following platforms:

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

Installation Notes

Installation instructions for installing WebLogic SPI, are documented in the HP Operations Smart Plug-In for BEA WebLogic 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 managed node OS and version and its supported WebLogic Application Server versions are listed below:

WebLogic Server Version Managed Node OS and Version
WebLogic Application Server 7.0 HP-UX 11.11
HP Tru64 5.1B, 5.2
Solaris 8, 9, 10
Windows 2000, 2003 IA64
WebLogic Application Server 8.1 sp1+

HP-UX 11.11, 11.23, 11.23 IA64
HP Tru64 5.1B, 5.2
Solaris 8, 9, 10
Windows 2000, 2003 IA64, 2003 x86
Windows 2003 on AMD 64 bit processor
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux ES 9.0 (32 bit)
AIX 5.2, 5.3
WebLogic Application Server 9.0, 9.1

HP-UX 11.11, 11.23, 11.23 IA64
AIX 5.2, 5.3
HP Tru64 5.1B, 5.2
Solaris 8, 9, 10
Windows 2000, 2003 IA64, 2003 x86
Windows 2003 on AMD 64 bit processor
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux ES 9.0 (32 bit)
WebLogic Application Server 9.2

HP-UX 11.11, 11.23, 11.23 IA64, 11.31 IA64, 11.31 PARISC
AIX 5.2, 5.3
HP Tru64 5.1B, 5.2
Solaris 8, 9, 10
Windows 2000, 2003 IA64, 2003 x86
Windows 2003 on AMD 64 bit processor
Red Hat Enterprise Linux AS/ES 4.0 (32 bit)
SuSe Linux 9.0 (32 bit), 10.0 (64 bit)
WebLogic Application Server 10.0

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

NOTE: Support on Windows x64 nodes is available only on DCE Agents in 32 bit emulation mode.

 

Software and Hardware Requirements

Before installing HP Operations Smart Plug-in for BEA WebLogic Server for HP Operations Manager for Windows, 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

QXCR1000836121: Required change in formula for formula WLSSPI_005

Known Problems, Limitations, and Workarounds

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

Problems

Discovery, Discover Oracle AS, and (or) Configure OASSPI tool hangs

PROBLEM: The Discovery policy, the Discover Oracle AS tool, and (or) the Configure OASSPI 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\wls\conf\SiteConfig.lock where <OvOWShareInstallDir> is typically (for HPOM for Windows 8.10 or 8.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.

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.

QXCM1000304720: Growing wls.log file

PROBLEM: The wls.log file grows very large.
WORKAROUND: Limit the size of the data saved to the log file each time the logfile encapsulator is run. In the SPIConfig file (located in /var/opt/OV/wasspi/wls/conf/ or /var/opt/OV/conf/wls/ on UNIX platforms and /usr/OV/wasspi/wls/conf/ on Windows platforms), add the following:
# maximum number of lines to save to the log file / run LOG_LINE_LIMIT=16667
# maximum number of characters to save from each log file / run LOG_SIZE_PER_FILE_LIMIT=600000

Discover WebLogic or Configure WLSSPI tool may misplace the SPI configuration file on a managed node

PROBLEM: If multiple managed nodes are selected when running the Discover WebLogic or Configure WebLogic tools, or if the Discover WebLogic and Configure WebLogic 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 WebLogic tool for each managed node that is reporting errors (run the tool on each managed node one at a time).

getAttributes returns a null value on WebLogic 6.1

PROBLEM: When using WebLogic Server 6.1, getAttributes returns a null value.
WORKAROUND: Install WebLogic Server 6.1 sp7 (service pack 7).

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/wls/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/wls/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 …/wls/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 WebLogic 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.

If WebLogic Server is not started from the Home directory, WebLogic SPI cannot locate and monitor WebLogic log file.

PROBLEM: WebLogic Server SPI cannot locate and therefore is unable to monitor the WebLogic log file when WebLogic Server is not started from the HOME directory.This problem occurs only in WebLogic Server 6.0 and 6.1.
The location and name of the WebLogic Server log file is specified in the WebLogic Administration Console in the "Logging" tab on the server configuration page. If this log file is specified with a relative path, this path is relative to the directory in which the WebLogic Server is started. The default is the WebLogic home (WL_HOME) directory specified when the WebLogic SPI is configured. The startup scripts installed by BEA start WebLogic Server from its home directory.
No means currently exists for querying the server for its startup directory. So, if the WebLogic Server is started up in a directory other than WL_HOME and the log file is specified as a relative path, the WLSSPI may not be able to locate and monitor the WebLogic Server log file.
WORKAROUND:

Choose one of the following workarounds:

Option A:
Configure the LAUNCH_DIR variable in the WebLogic Server SPI configuration file to define the location of the WebLogic Server startup directory. Please see Chapter 2 of the User’s Guide for details.

Option B:
Ensure that WebLogic Server is started from the WL_HOME directory, which is the default if you use the startup scripts provided by BEA. Also, note that the WLSSPI will not recognize a fully qualified path name for the log file. You must use a relative path for the WebLogic Server log file in order for it to be located and monitored by the WLSSPI.

Option C:
In the WLS-SPI configuration file, include the fully qualified name of the WebLogic Server logfiles you want to monitor. For multiple logfile entries, separate each logfile name with a comma. To edit the file:

  1. Run Tools for WebLogic Server SPI Admin Configure WLSSPI to edit the file.
  2. Insert an additional line beginning with keyword SERVER<n>_LOGFILE as shown below, followed by the fully qualified file name: SERVER<n>_LOGFILE = <path>/<file_name_1>,<path>/file_name_2>
  3. Save the file and deploy to the node.
NOTE: This workaround is an enhancement to the syntax as documented in the HP OpenView Smart Plug-in for BEA WebLogic Server Configuration Guide.

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.

View weblogic log tool does not display correct content in cmd windows

PROBLEM: The View WebLogic Log tool does not display non-English content which is present in the WebLogic log files.
WORKAROUND: N/A.

The uninstallation process does not uninstall WebLogic SPI completely

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

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.

Localization Support

HP Operations Smart Plug-In for BEA WebLogic Server Configuration Guide is localized in Japanese.

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.