HP OpenView Smart Plug-in for WebSphere Application Server

for HP OpenView Operations for Windows

Release Notes

Software version: 04.10.000 / June 2006

This document provides an overview of the changes made to HP OpenView Smart Plug-in for WebSphere Application Server (WBS SPI) for HP OpenView Operations for Windows 7.5. This release notes contains important information not included in the manuals or in online help

In This Version
Documentation Updates
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Errata
Support
Legal Notices

In This Version

WBS SPI is a full-featured SPI that allows you to manage WebSphere Application Servers from an HP OpenView Operations console.

The following new features have been included in this release:

Support for WebSphere Application Server setup in HTTPS mode
Support for WebSphere 6.0
Support for HP OpenView Reporter 3.7

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 the following URL:

http://ovweb.external.hp.com/lpe/doc_serv/

In the Product list, click the product name.
In the Version list, click the version number.
In the OS list, click the OS type.
In the document list, click the document title.
To retrieve the document, click Open or Download.

NOTE: To view files in PDF format (*.pdf), Adobe Acrobat Reader must be installed on your system. To download Adobe Acrobat Reader, go to the following URL:

http://www.adobe.com/

Installation Notes

Installation instructions for the WBS SPI are documented in the HP OpenView Smart Plug-in for WebSphere Application Server Configuration Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's CD media as:

\Documentation\SPI Guides\WebSphere_AppServer_Config.pdf

Software and Hardware Requirements

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

Software
- HP OpenView Operations for Windows 7.5
- Optional Software
Support Matrix

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.00, 11.11 AIX 4.3.3, 5.1, 5.2, 5.3 Solaris 7, 8 Windows 2000 Red Hat Enterprise Linux 2.1 AS/ES (32 bit)
WebSphere Application Server 5.0	HP-UX 11.11, 11.23, 11.23/IA64 AIX 4.3.3, 5.1, 5.2, 5.3 Solaris 7, 8, 9, 10 Windows 2000, 2003, 2003 IA64 Red Hat Enterprise Linux AS/ES 2.1(32 bit), 3.0 (32 bit)
WebSphere Application Server 5.1	HP-UX 11.11, 11.23, 11.23/IA64 AIX 5.1, 5.2, 5.3 Solaris 7, 8, 9, 10 Windows 2000, 2003, 2003 IA64 Red Hat Enterprise Linux AS/ES 2.1(32 bit), 3.0 (32 bit), 4.0 (32 bit) SuSe Linux 8.0 (x86/64)
WebSphere Application Server 6.0	HP-UX 11.11, 11.23, 11.23 (Itanuim) AIX 5.1, 5.2, 5.3 Solaris 7, 8, 9, 10 Windows 2000, 2003, 2003 IA64 Red Hat Enterprise Linux AS/ES 2.1(32 bit), 3.0 (32 bit), 4.0 (32 bit) SuSe Linux ES 8.0 (32 bit), 9.0 (32 bit)

Enhancements and Fixes

The following items (identified by error tracking number) are fixed in the current software release. To display details about each software fix, click the error tracking number.

Defect Fixes

QXCR1000215317: Requesting SSL support for WebSphere SPI.
QXCR1000236553: Discovery - Add ND server handling.
QXCR1000283795: Don't log error if metric ID or version is missing.
QXCR1000239027: Disallow user to configure both GRAPH_SERVER and GRAPH_URL.
QXCR1000238523: Eliminate RMID stop/start browser message.

Bug Fixes

QXCR1000211153: WebSphere SPI does not load graph in browser when use OVPM 5.0.
QXCR1000298676: WBSSPI : Trace ON application does not produce trace files.
QXCR1000234503: WBSSPI A.03.50, wbsspi tracing can not be activated.
QXCR1000235142: Resetting PMI module levels to none not detected.
QXCR1000242553: Update metrics ref. to reflect version 4/5 impact levels.
QXCR1000299301: WBSPI Configure tool not saving config or transferring to node properly.
QXCR1000237420: collector cmd-line cannot handle argvs with spaces.
QXCR1000291523: JMX ASCII reports formats all numbers as floats.
QXCR1000299107: Update SPI error message WASSPI-18 in docs.
QXCR1000235586: logdata script logic error - does not remove lock.
QXCR1000285945: Need to workaround multiple registry Sun bug.
QXCR1000288197: Default templates collect from JMX Connector servers.
QXCR1000296585: Problem viewing OVPM graphs if there are spaces or special characters in the URL.
QXCR1000205496: UDM guide corrections.
QXCR1000106754: WBSSPI: Stack trace when contacting a downed admin server.

Known Problems, Limitations, and Workarounds

The following problem is known in the current software release. To display details about each problem (including workaround information), click the problem text. To hide details, click again.

Initially running Discovery on SuSe Linux nodes

	Problem:	Discovery fails to discover SuSe Linux managed nodes.
	Workaround:	Use the Configuration Editor and manually set the required properties for each SuSe Linux managed node. Set the HOME, JAVA_HOME, NAME, and PORT properties for each SuSe Linux managed node. After setting these properties, run the Discover WebSphere tool to deploy the Discovery group policies and refresh the Service Map.

Discovery, Discover WebSphere, and/or Configure WBSSPI hang

Problem: The Discovery policy, the Discover WebSphere tool, and/or the Configure WBSSPI tool hang.

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:

	Problem:	The Discovery policy, the Discover WebSphere tool, and/or the Configure WBSSPI tool hang.
	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 `<drive>:\Program Files\HP OpenView\Data\shared\` The locking mechanism automatically deletes the lock directory after two hours.

Remove the lock directory on the management server: <OvOWShareInstallDir>\SPI-Share\wasspi\wbs\conf\SiteConfig.lock where <OvOWShareInstallDir> is typically <drive>:\Program Files\HP OpenView\Data\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.

GRAPH_SERVER and GRAPH_URL properties can be set

	Problem:	The GRAPH_SERVER and GRAPH_URL properties can be set but they are not necessary.
	Workaround:	Do not set the GRAPH_SERVER and GRAPH_URL properties.

Using non-default WebSphere Admin Server user with administrator privileges

	Problem:	In the WebSphere Application Server, a user configured with administrator privileges does not get full administrator privileges. If WBS SPI is configured to access the WebSphere Application Server as this user, the SPI fails because it cannot gather the required data as this user.
	Workaround:	Configure the WBS SPI to use the default WebSphere Admin Server username and password. This is the username and password configured when the WebSphere application server was installed/configured. Using the Configuration Editor, set the LOGIN and PASSWORD properties to the default WebSphere Admin Server username and password.

Discovery does not set properties correctly for the application servers if two or more versions are running on a managed node

	Problem:	Two or more versions of the WebSphere application server are running on a managed node and discovery does not correctly set the properties for the application servers.
	Workaround:	Option 1: Verify the application servers are using non-conflicting ports. If you install an application server in a different home directory, the installer may choose a port used by an existing application server (even if you set the installer to auto-configure non-conflicting ports). If application servers are using the same bootstrap port, modify the port numbers so that each application server uses a unique bootstrap port. Run the Discover WebSphere tool. Option 2: If you want to use the same bootstrap port, run the Configure WBSSPI tool and do the following: Set the HOME, JAVA_HOME, VERSION, and other properties that are incorrectly set. Set a unique ALIAS for each application server using the same port. Uncheck the AUTO_DISCOVER check box for the application server that is not running. Click Finish.

Problem:

Two or more versions of the WebSphere application server are running on a managed node
and discovery does not correctly set the properties for the application servers.

Workaround:

Option 1:

Verify the application servers are using non-conflicting ports. If you install an application server in a different home directory, the installer may choose a port used by an existing application server (even if you set the installer to auto-configure non-conflicting ports).
If application servers are using the same bootstrap port, modify the port numbers so that each application server uses a unique bootstrap port.
Run the Discover WebSphere tool.

Option 2:
If you want to use the same bootstrap port, run the Configure WBSSPI tool and
do the following:

Set the HOME, JAVA_HOME, VERSION, and other properties that are incorrectly set.
Set a unique ALIAS for each application server using the same port.
Uncheck the AUTO_DISCOVER check box for the application server that is not running.
Click Finish.

Discover/Configure application may misplace the SPI configuration file on a node

	Problem:	If multiple managed nodes are selected when running the Discover WebSphere or Configure WebSphere tool, 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 (SiteConfig) for one or more managed nodes is 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 application 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.

Problem:

When the Self-Healing Info application 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.

The wbs.log file grows very large

	Problem:	The `wbs.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/wbs/conf/` or `/var/opt/OV/conf/wbs/` on UNIX platforms and `/usr/OV/wasspi/wbs/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`

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:

	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`

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

The WBS-SPI requires that PMI be enabled in WebSphere in order to gather metrics

	Problem:	With WebSphere 4,. the SPI automatically enables PMI if it is not enabled and sets the impact level of PMI to that required for the metrics that the user selects. WebSphere 5 servers have no capability for PMI to be enabled except from the WebSphere console. The WBS-SPI will fail if it tries to monitor a WebSphere 5 server that does not have PMI enabled.
	Workaround:	Before configuring the SPI, use the WebSphere console and enable PMI.

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 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, 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 WebShpere log tool does not display content with non-asii character

	Problem:	The View WebSphere log tool does not display the non-ascii characters which are present in the WebSphere log files.
	Workaround:	N/A

Start/Stop WebShpere tool may not work on non-English machines

	Problem:	The Start WebSphere and Stop WebSphere tools may not work on non-English machines.
	Workaround:	N/A

Documentation Errata

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

Support

Please visit the HP OpenView support web site at:

http://www.hp.com/managementsoftware/support

This web site provides contact information and details about the products, services, and support that HP OpenView offers.

HP OpenView online 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

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 the following URL:

http://www.hp.com/managementsoftware/access_level

To register for an HP Passport ID, go to the following URL:

http://www.managementsoftware.hp.com/passport-registration.html

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.