HP OpenView Service Navigator Value Pack

This document contains the HP OpenView Service Navigator Value Pack Release Notes. It includes last-minute information that could not be included in the documentation and describes known problems and limitations.

In This Version

Welcome to the HP OpenView Service Navigator Value Pack 8.0 software! The Service Navigator Value Pack enhances our successful HP OpenView Operations for UNIX product by providing Service Configuration, a graphical user interface for Service Navigator, designed for maximum efficiency and ease-of-use. This version includes the following new features and enhancements:

View builder (Service desk integration only) The new view builder enables you to set up rules that automatically build service hierarchies based on your Service Desk object structure.
Status simulation The new simulation mode enables you to test status propagation and calculation before you deploy a hierarchy to Service Navigator.
Download and upload service hierarchies Two new tools, cadm_DumpHierachy and cadm_LoadHierarchy, enable you to download a service hierarchy to a file and upload it again. These tools are useful for making backup copies and migrating data.
Stop bothering me! If you are tired of acknowledging messages in the console, you can now disable them.
Enhanced deployment
- Root objects are now by excluded from deployment by default. You can change this setting.
- cadm_Deploy enables you to deploy service hierarchies from the command line.
Improved delete It is now simpler to delete objects from a hierarchy and to exclude generated and discovered objects.
Showing the origin of objects It is now easier to see how an object was added to a service hierarchy: generated, discovered, or manually added.
Finding objects in a service hierarchy The new Find in Service Hierarchy tool enables you to quickly locate an object in a service hierarchy.
Increased quality Many issues identified in version 7.1 have been resolved in this version.
OVO for UNIX 8.0 This version of the Service Configuration software is compatible with both OVO for UNIX version 7.1 and 8.0.
Data collection for HP OpenView Self-Healing Services Service Configuration now supports Self-Healing Services by collecting application data when a fault occurs.
Service Desk service pack 7 This version of the software is compatible with Service Desk service pack 7. The service pack is included on the Service Configuration CD-ROMs.
Windows 2000 with service pack 4 This version of the software can be installed on computers with the Windows 2000 operating system (service pack 4).
Client console on Windows XP This version of the Service Configuration client console can be installed on computers with the Windows XP operating system (service pack 1).

Not Supported With This Version

This version of the Service Navigator Value Pack software has the following limitations:

Non-English languages The software is only available in the English language. Localized versions, for example for the Japanese language, are planned for future releases.
Supported platforms The software is exclusively supported on the platforms listed in the Supported Platforms document, which is available at http://ovweb.external.hp.com/lpe/doc_serv/ by selecting the product operations for UNIX, version 8.x.
Two service reports The software causes two service reports to display incorrect data. The reports Message Trend by Service and Top Active Messages by Service are available with HP OpenView Reporter and should not be used in conjunction with the Service Navigator Value Pack software.
Sun Cluster, VERITAS Cluster Installation of the Service Navigator Value Pack software in Sun Cluster or VERITAS Cluster environments is not supported. The only supported cluster solution is MC/ServiceGuard on HP-UX. The only component of the Service Navigator Value Pack software that can be installed in an MC/ServiceGuard cluster is the connector (running on the OVO management server).

Installation Notes

To install the Service Navigator Value Pack software:

Installation overview Before you start the installation, thoroughly read chapter 1 of the Service Navigator Value Pack Installation Guide. To ensure a smooth and successful installation, it is essential that you are familiar with the components and architecture of the Service Navigator Value Pack software and that you understand where and how the installation packages must be installed.
Hardware and software requirements Make sure the systems where you plan to install the Service Navigator Value Pack software meet the hardware and software requirements listed in the Supported Platforms document.
You can download the latest version of the Supported Platforms document at http://ovweb.external.hp.com/lpe/doc_serv/ by selecting the product operations for UNIX, version 8.x.
Installation Install and configure the Service Navigator Value Pack software as described in the Service Navigator Value Pack Installation Guide.
Licensing The HP OpenView Operations for UNIX management server license to use (LTU) entitles you to use the Service Navigator Value Pack. An additional LTU is not required.

Troubleshooting

Known Problems with the Console
Known Problems with Deployment
Known Problems with Service Desk Integration
Different Output Format of opcsvcterm

Known Problems with the Console

Problem:	QXCR1000107875
Symptom:	GUI problems may occur when using a mouse configured to use the pointer shadow. In a standard installation of the Windows 2000 operating system, the pointer shadow is enabled by default. Problems may occur around the mouse pointer especially when: selecting a service hierarchy with the mouse in the drop-down menu in the upper right corner selecting a menu item with the mouse The problems are typically small rectangular trails of inverse color left by the mouse when moving across menu items.
Solution:	Avoid using remote desktop solutions like vnc. Always use the latest version of Windows certified graphic drivers.

Problem:

QXCR1000107875

Symptom:

GUI problems may occur when using a mouse configured to use the pointer shadow. In a standard installation of the Windows 2000 operating system, the pointer shadow is enabled by default. Problems may occur around the mouse pointer especially when:

selecting a service hierarchy with the mouse in the drop-down menu in the upper right corner
selecting a menu item with the mouse

The problems are typically small rectangular trails of inverse color left by the mouse when moving across menu items.

Solution:

Avoid using remote desktop solutions like vnc. Always use the latest version of Windows certified graphic drivers.

Problem:	QXCR1000091803
Symptom:	By default, the GUI starts with a setting instructing the Java Virtual Machine (JVM) to use up to 512MB of system memory. When using the GUI, the amount of memory used will keep increasing until the 512MB limit is reached.
Solution:	The user can force the JVM to perform 'garbage collection' before the 512MB limit on memory use is reached. This is a process during which unused but reserved memory is returned to operating system. Garbage collection can be triggered by, for example, minimizing the GUI.

Problem:	QXCR1000189642
Symptom:	Using the Find in Service Hierarchy dialog box with the criteria 'Parent objects;Weight is empty' or 'Message weight is empty', produces an unexpected set of results.
Solution:	Only user defined weightings are stored in the database, default weightings are not. Therefore searching with the criteria 'weight is empty' returns a list of objects for which the default weighting has not been changed.

Problem:	QXCR1000192982
Symptom:	If no service hierarchies exist, it is not possible to delete calculation rules, propagation rules, actions, child object rules, and parent-and-child object rules. In some cases an exception message appears.
Solution:	Create a dummy service hierarchy with one root object. Delete the rules and actions in question and then delete the dummy hierarchy.

Known Problems with Deployment

Problem:	QXCM1000194534
Symptom:	When manually deploying a service hierarchy, the generated XML file is empty. When automatically deploying a service hierarchy, the deployment process hangs.
Solution:	Ensure that you have the multi-language version of the Java Runtime Environment (JRE) 1.3.1_03 or higher (but not version 1.4) installed on the application server and client system. A suitable version of the JRE is available on the Service Configuration installation CD-ROMs.

Known Problems with Service Desk Integration

Problem:	QXCM1000192603
Symptom:	If Service Configuration is installed on top of a localized installation of Service Desk, problems occur when adding an OVO management server in the GUI. The error messages that appear are incorrect.
Solution:	To install Service Configuration on an existing, localized Service Desk installation: Install Service Configuration. Run the localization tool again from the Service Desk client. Update the database using the Service Desk database wizard.

Problem: QXCR1000107496

Symptom: After deploying a hierarchy to OVO 7.x, certain icons are not correctly displayed in Service Navigator (workgroup, project, person, and organization).

Solution:

On the OVO server, change to the directory /opt/OV/www/htdocs/ito_op/images and create copies of the following files:

File to copy	Name of copy
person.32.gif	Person.32.gif
WorkGroup.32.gif	Workgroup.32.gif
organization.gif	Organization.gif
project.32.gif	Project.32.gif

Problem:	QXCR1000107677
Symptom:	When launching a Service Desk data form from within the OVO Java GUI, the data form is sometimes opened in the background and therefore hidden from view.
Solution:	Click the Service Desk data form button on the taskbar to move the program to the foreground.

Different Output Format of opcsvcterm

The format of results returned by the opcsvcterm interface is different with the Service Navigator Value Pack installed. There are two major differences:

Element content opcsvcterm does not immediately return a line feed after an end-tag. Instead, it waits until the service engine returns the complete content part of an element before displaying the content with the line feed. Without the Service Navigator Value Pack installed, opcsvcterm returns line feeds immediately.
Empty elements opcsvcterm returns a start-tag immediately followed by an end-tag to represent an empty element. Without the Service Navigator Value Pack installed, opcsvcterm returns empty-element tags.

The following table gives example output for opcsvcterm without and with the Service Navigator Value Pack installed:

Service Navigator	<Results>'\n'	[space][space]<OK/>'\n'				</Results>'\n'
Service Navigator Value Pack	<Results>	'\n'[space][space]	<OK>	</OK>	'\n'	</Results>	'\n'

NOTE:

Hewlett-Packard reserves the right to change the output and the output format of Service Navigator interfaces with product releases. Check the Service Navigator DTDs for changes to the XML definitions. The DTDs can be found on the OVO management server in the /etc/opt/OV/share/conf/OpC/mgmt_sv/dtds directory. In general, it is recommended to use an XML parser to interpret the service engine output rather than your own pattern-matching algorithms.

Problem:	QXCR1000192582
Symptom:	The online help topic "Copy and Paste between Service Hierarchies" contains the following incorrect text: If one of the copied objects already exists in that hierarchy, you can either cancel the paste operation or overwrite the existing object(s).
Solution:	Note that it is not possible to paste an object into the same hierarchy more than once. The note below the incorrect text explains what happens if you try to do this.

Problem:	QXCR1000189477
Symptom:	The documentation for the command-line interfaces `cadm_DumpHierarchy` and `cadm_LoadHierarchy` does not clearly state that the user should type the absolute path for the export and import XML files.
Solution:	Type the absolute path for all command-line options that refer to files. (The documentation provides correct examples.)