HP OpenView Dashboard Operations View 2.0

Release Notes

July, 2006

This document provides an overview of the HP OpenView Dashboard Operations View 2.0 Release.  It contains important information not included in the manuals or in online help.

In This Version
Installation Notes
Product Documentation
Known Problems, Limitations, and Workarounds
Local Language Support
Supported Integration with Other OpenView Solutions
Legal Notices

In This Version

This version is the first production use of Operations View, the follow-on to the HP OpenView Service Information Portal (SIP) version 3.2 product. For this release, Operations View is only intended to run in either the BEA WebLogic Portal 8.1 or the Jetspeed 1.6 portal environment. The Jetspeed 1.6 portal environment is provided with Operations View.

Background Information:

All existing SIP 3.2 modules have been ported to JSR168 portlets.  This port has allowed us to move the SIP product model from a standalone management-centric portal to providing a set of industry standard portlets that can be integrated into enterprise portals that are running industry standard JSR168 portal software.

Two new tools have been added to assist the user to successfully integrate the Operations View portlets into a chosen portal server environment:

• Administrator Tool: This user interface allows you to configure and deploy Operations View portlets into a portal server environment. It eliminates the need to hand edit XML files.  This tool is installed as:

      UNIX:            /opt/OV/bin/ovopviewadmingui

      Windows:    C:\Program Files\HP OpenView\bin\ovopviewadmingui.bat

• SIP Version 3.2 Migration Wizard: This tool assists you in the process of moving SIP 3.2 configuration data into an Operations View environment.  Note that this tool does not completely automate the process; some manual intervention is still required.  This functionality is accessible from the Tools menu of the Operations View Administrator Tool.

Installation Notes

Prior to installing Operations View, you must completely uninstall any previous HP OpenView Dashboard or Operations View DP or Beta products.

For detailed installation information, refer to the HP OpenView Dashboard Installation Guide.

Software and Hardware Requirements

Before installing Operations View, make sure that your system meets the minimum specified hardware and software requirements.  For detailed information regarding these requirements, refer to the HP OpenView Dashboard Installation Guide.

Uninstalling Operations View

Prior to uninstalling Operations View, shut down the Administrator Tool and stop all portlets that are running in your portal server.  This allows for a clean uninstall of the product.  Only one uninstall or install process is allowed to run at a time. 

During the uninstall of Operations View, the version of Jetspeed installed by Operations View will be removed. Before uninstalling Operations View, back up any user-created portlet application data to a location where the data can be retrieved at a later date. In order to use the configuration later, copy the entire contents of the <installdir>/nonOV/dashboard/jetspeed/1.6 directory to another location before removing the product.  This backup is a manual step that must be completed by the user to preserve data.

NOTE: OV Dashboard 2.0 DVD-ROMs use a new format, which is slightly different from older CD formats. As a result, HP-UX 11.0 systems require a system patch to read the DVD-ROM properly. Visit http://www4.itrc.hp.com/service/index.html and follow the patch database link under maintenance and support (hp products) section to download the following patch:

PHKL_28060 - s700_800 11.00 Y2k; Rock Ridge extension for ISO-9660

Once the patch is installed, use the following command to mount the DVD:

#mount –F cdfs –orr <device_name> <mount_name>

Product Documentation

For information on the documentation available with this product, see the documentation roadmap.

Known Problems, Limitations, and Workarounds

Jetspeed Header Designer Portlet can corrupt portal configuration

PROBLEM:	After using the Jetspeed Header Designer and restarting your server, you consistently get "Service Registry failed to initialize" stack trace when viewing a portal page.
FIX:	Do not use this feature. There is no work around other than replacing the original JetspeedResources.properties file. Contact support for a copy of this file.

Multiple copies of the NNM Topology portlet on one page can display wrong map

PROBLEM:	If you define a single NNM Topology portlet and place it multiple times on a page, some of the portlets may not display correct map(s).
FIX:	Create and use more than one Topology portlet definition, making sure that each has a unique portlet name within the Administrator Tool.

Jetspeed 1.6:  Preferences are not unique to an individual user

PROBLEM:	Individual users are not allowed to set unique preferences.
CAUSE:	Jetspeed 1.6 does not keep preferences unique to an individual user. The behavior is that when a portlet is on a page, only one set of preferences is used no matter which user accesses the portlet. The portlet specification states that each user should have unique preferences, which is not the observed behavior. However, if a portlet is placed in two separate locations (that is, two views (or psml files)), each portlet maintains unique preferences (even though they share the same portlet definition in the portlet.xml file).
FIX:	As a workaround, deployments will need to have each user with unique preferences maintain their own unique psml and view files.

Jetspeed 1.6 uses system's default encoding to read portlet preferences

PROBLEM:	Jetspeed uses the system's default encoding to read portlet preferences. If there are any non-ASCII preferences specified, Jetspeed does not read them correctly.
FIX:	This problem will be fixed in the 1.6.1 release of Jetspeed.

Authentication using LDAP does not work correctly with Jetspeed 1.6

PROBLEM:	Jetspeed throws an exception if it is configured to use LDAP for authetication and authorization.
FIX:	This problem will be fixed in the 1.6.1 release of Jetspeed. The workaround is to download Sun's JavaMail 1.2 jar file and place it in the following directory: UNIX: /opt/OV/nonOV/dashboard/jetspeed/1.6/jakarta-tomcat-5.5.9/webapps/jetspeed/WEB-INF/lib Windows: <install_dir>\nonOV\dashboard\jetspeed\1.6\jakarta-tomcat-5.5.9\webapps\jetspeed\WEB-INF\lib Then restart Jetspeed.

Log file link at end of install brings up empty browser

PROBLEM:	The HTML code produced in the install log may be incompatible with certain web browsers. In this case, the browser displays an empty file.
FIX:	Open the log file in a text editor, or upgrade your browser to a supported version. The install log file is located in the following directory: UNIX:  /var/tmp/HPOvInstaller/dashboard_<version> Windows: %TEMP%\HPOvInstaller\dashboard_<version>

Migration of users and/or roles to BEA WebLogic does not work with special strings

PROBLEM:	While executing the weblogic.Admin tool from BEA WebLogic, many errors can occur on special strings that are surrounded with the " character.
FIX:	BEA WebLogic has bugs submitted (CR214241, CR111896) around this issue. The workaround is to remove the quoted strings from the batch file, and then execute them as individual weblogic.Admin commands.

Very large list of nodes or services in portlet preference prevents Jetpeed from loading the application

PROBLEM:	Jetspeed throws an exception while reading portlet.xml, if it finds a preference value larger than 8192 characters in length. This could happen for example, if you have a very large list of nodes configured in the OVPM portlet. Jetspeed will not load the application if this exception is thrown and none of the portlets will be available.
FIX:	Create portlets such that the preferences are not very large. For example, if you have a lot of nodes in the OVPM portlet, then instead of showing them all in a single portlet, create multiple portlets with smaller lists of nodes.

The repair option in the Windows installer does not repair configuration files and some .bat files

PROBLEM:	On Windows, the installer repair option does not repair the configuration files and some .bat files.
CAUSE:	During installation, these files are copied to their final location as a post-processing step. The configuration files are located in the <datadir>\conf\dashboard\opview directory.  The .bat files are used to run the Administrator Tool, self healing, and so forth. During the installation, some of these files also have substitutions done to configure the file to work on the system. On Windows, repair does not run the processing step to do the copy and substitution steps.
FIX:	Only repair files that seem to be corrupt.  The initial location for the configuration files is <installdir>\newconfig\DataDir\conf\dashboard\opview in a structure that matches <datadir>\conf\dashboard\opview. The set of files copied with substitutions also resides in the <installdir>\newconfig structure.  If you repair these files, perform the substitutions manually:  Replace @INSTALLDIR@ with <installdir> path  Replace @DATADIR@ with <datadir> path  Replace @JETSPEED_DIR@ with <installdir>\nonOV\dashboard\jetspeed\1.6 path  Replace @JETSPEED_TOMCAT_VERSION@ with jakarta-tomcat-5.5.9 File Name Information Path.properties Source Location: <installdir>\newconfig\DataDir\conf\dashboard\opview Destination Location: <datadir>\conf\dashboard\opview Replace @INSTALLDIR@ and @DATADIR@ ovopviewxmlvalidate.bat Source Location: <installdir>\newconfig\bin\dashboard\opview Destination Location: <installdir>\bin Replace @INSTALLDIR@ and @DATADIR@ ovopviewadmingui.bat Source Location: <installdir>\newconfig\bin\dashboard\opview Destination Location: <installdir>\bin Replace @INSTALLDIR@ and @DATADIR@ opviewEnv.bat Source Location: <installdir>\newconfig\support\dashboard\opview Destination Location: <installdir>\support\dashboard\opview\dc Replace @INSTALLDIR@ and @DATADIR@ opview-collector-config.xml Source Location: <installdir>\newconfig\support\dashboard\opview Destination Location: <installdir>\support\dashboard\opview\dc\conf Replace @INSTALLDIR@ and @DATADIR@ opview.xml Source Location: <installdir>\newconfig\support\dashboard\opview\reg Destination Location: <installdir>\support\dashboard\opview\reg\dc Replace @INSTALLDIR@ and @DATADIR@ ovdshbdjetspeed.bat Source Location: <installdir>\newconfig\lbin\dashboard\jetspeed\1.6 Destination Location: <installdir>\lbin\dashboard\jetspeed\1.6 Replace @INSTALLDIR@, @JETSPEED_DIR@, and @JETSPEED_TOMCAT_VERSION@

OV Dashboard DVD appears to mount properly, but the installation fails on HP-UX 11.11

PROBLEM:	OV Dashboard installation on certain HP-UX 11.11 systems fails.
CAUSE:	Certain HP-UX 11.11 systems released prior to December 2003 are unable to read the new DVD format properly. As a result, the names of files on the DVD to appear garbled and consequently the installation fails. The reason for installation failure is improper mounting of the DVD.
FIX:	To mount new DVD format correctly, visit http://www4.itrc.hp.com/service/index.html and follow the patch database link under maintenance and support (hp products) section to download the following patches for your system: PHKL_28060 - s700_800 11.00 Y2k; Rock Ridge extension for ISO-9660 PHKL_28025 - s700_800 11.11 CDFS cumulative patch PHCO-25841 - s700_800 11.11 Add Rock Ridge extension to mount_cdfs(1M) After the patches are installed, use the following command to mount the DVD: #mount –F cdfs –orr <device_name> <mount_name>

Local Language Support

For this release, no local language support is provided.

Supported Integration with Other HP OpenView Solutions

Refer to the HP OpenView Dashboard Installation Guide for a list of all supported HP OpenView integrations.

Legal Notices

©Copyright 2005-2006 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice.

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.

This product includes i-net OPTA software, which is © Copyright 2002-2006 i-net software GmbH, Berlin, Germany.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

AMD is a trademark of Advanced Micro Devices, Inc.

HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products.

Intel and Pentium are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java™ and all Java based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of The Open Group.