This document provides an overview of the changes made to HP Operations Manager for Windows for the 8.16 release (HPOM for Windows). It contains important information not included in the manuals or in online help.
In This Version
Documentation Updates
Installation Notes
Obsolescence Announcements
Known Problems, Limitations, and Workarounds
Documentation Errors
Local Language Support
Support
Legal Notices
HPOM for Windows is a distributed client/server IT operations solution that enables an IT organization to manage business services from centralized control points. HPOM for Windows is a management solution that snaps into the Microsoft Management Console (MMC). Through this console, HPOM for Windows supplies the information and tools for prioritizing and responding to problems that can affect your business.
HPOM for Windows manages your information technology environment by managing nodes and the services running on these managed nodes. It provides graphical user interfaces to configure policies, nodes, services, service types, tools, and user roles. These components work together to automate detection, evaluation, and responses to events and simplify the process of analyzing and resolving problems.
The HPOM for Windows media kit contains a number of CDs and DVDs required to install the HPOM for Windows foundation product, HP Operations Smart Plug-ins (SPIs), and add-on products. See the HP Operations Manager for Windows Installation Guide for details about the contents of your media kit and instructions for installing HPOM for Windows. For HP Operations Smart Plug-ins, see the HP Operations Smart Plug-ins DVD Installation and Upgrade Guide and the HP Operations Smart Plug-ins DVD Release Notes for details about available SPIs and instructions for installing and configuring them.
HPOM for Windows includes many documents in Adobe® Acrobat® PDF format. You must have Adobe Acrobat Reader to view and print these documents. Click here to download the Acrobat Reader from the Adobe web site.
The HP Operations Smart Plug-ins DVD contains a list that provides links to available documentation. See Documentation\spi_docs_index.htm on the HP Operations Smart Plug-ins DVD.
HPOM 8.16 for Windows is a re-release of HPOM 8.10 for Windows, with the following patches and updated software included:
Installation/migration patches:
OMW_00034: Consolidated installation patch.
Server patches:
OMW_00050: Intermediate server patch.
OMW_00048: Consolidated server and console patch.
Accessories patches:
OMW_00039: HP SiteScope Adapter 2.0 patch.
OMW_00032: Consolidated server accessories patch.
Agent patches:
OMW_00044: HP Operations agent version 8.60 for Windows.
OMW_00043: HP Operations agent version 8.60 for AIX.
OMW_00041: HP Operations agent version 8.60 for Linux.
OMW_00040: HP Operations agent version 8.60 for Solaris.
OMW_00008: HP Operations agent version 8.60 for HP-UX 11 for PA-RISC and Itanium.
For more information about the supported HP Operations agent versions, platforms, known problems, and workarounds, refer to the HP Operations Agent Release Notes, which can be found by selecting Operations Manger for Windows at the HP Software Product Manuals web site.
HPOM 8.16 for Windows includes the following new features:
Before HPOM 8.00 for Windows, management servers and agents communicated using DCE/RPC. HPOM 8.16 for Windows includes an agent that communicates using HTTPS. Although the DCE agent is currently still supported, you are encouraged to use the HTTPS agent for new nodes. If nodes already exist in your environment that have DCE agents, consider migrating to the HTTPS agent.
All communication between management servers, and between management servers and nodes can be strongly encrypted.
Nodes and management servers accept all inbound communications to a single port, so it is simpler to configure firewalls and proxies.
Policies, messages, and actions all contain signatures, which management servers and nodes create and check using certificates. If a malicious user attempts to tamper with a signed policy, message, or action, the signature becomes invalid.
If a firewall blocks inbound HTTPS connections from a node to a management server, you can configure an HTTPS agent to act as a reverse channel proxy (RCP). An RCP handles communication between management servers and nodes, so that they do not need to communicate with each other directly.
You can now change the status display mode in two ways: disable user-specific status calculation and enable operational status calculation. User-specific status calculation is enabled by default and means that the status of services in a user's map is calculated based on the user's subordinate services and messages. Another user with a different set of responsibilities may see a different status for the same services. Operational status calculation is disabled by default. When enabled, owned messages are considered acknowledged and do not affect the severity status of a service.
HPOM 8.16 for Windows distinguishes unplanned and scheduled outages. The outage state can be applied to nodes and node groups, and to services and service hierarchies, either by using the console (for unplanned outages only) or by applying command-line tools (for both unplanned and scheduled outages).
You can now add Windows groups to the HP-OVE-OPERATORS group and assign the Windows group to an operator user role. Windows users who are members of that group automatically receive the permissions associated with that user role. In addition, you can set permissions to view reports and graphs, to change the unplanned outage state, to create message filters, and to perform administrative tasks on policies.
External nodes handle messages from nodes without the need to configure them as nodes. For example, by setting up an external node, you can immediately receive messages from new systems in a certain IP subnet, and then decide later whether it is necessary to set up the systems as managed nodes. Or you can receive messages from systems without an HP Operations agent installed (SNMP devices, for example) for agentless monitoring. When you set up an external node, you define a pattern that must be matched by the node's fully qualified domain name, IP address, or node name.
The management server no longer runs with administrative rights by default. (The HP-OVE-User and HP-OVE-Deleg-User accounts are not members of the local administrators group by default in new installations. You can remove these users from the local administrators group if you migrate from a previous version of HPOM for Windows.)
SQL authenticated database users (ovms_admin, ovdb_user) are no longer created. The management server now accesses the database using Windows authentication. If you need to configure extra read-only users for reporting purposes, see the SQL Server documentation that Microsoft provides for instructions and security options.
The server configuration dialog contains a generic server configuration tab, which enables you to configure many different aspects of a management server's configuration. This eliminates the need to manually configure values on a management server using registry editors or commands.
You can now use a wizard to create new nodes. The wizard guides you through the node setup and helps you to enter the required information. In addition, heartbeat polling and autodeployment can be set for each node individually. A node's properties now also include settings for the agent communication type and binary format.
Custom message attributes represent additional, user-defined properties that can be attached to a message, for example owner, location, or emergency phone number. The administrator defines custom message attributes for outgoing messages. The operator can see custom message attributes in the message browser, can add, modify, and delete them, and can filter messages based on them.
In addition to custom message attributes, HPOM 8.16 for Windows provides the following new message attributes: Time Created, Sender, and Origin.
Message-related tools can be launched on multiple, selected messages.
Owned messages in the message browser will now use a different color. When a new message arrives, the following system tray notifications are available: icon or popup or both, and sound notification.
Messages can now be saved to a .txt or .csv file.
Administrators can assign ownership of messages to other users. Administrators can also give operators the right to assign ownership of messages for particular message groups.
Message browsers can display the following additional message attributes: policy, policy type, origin, sender, user of last state change, message key. Message browsers can also display up to ten columns of custom message attributes.
HPOM 8.16 for Windows includes new server policies to configure the behavior of the management server. They can be deployed to the local management server only and are listed under a new folder Server policies grouped by type.
The following server policy types are available:
HPOM 8.16 for Windows includes an enhanced instrumentation folder structure, which provides more flexibility for associating policies and instrumentation using categories. For more details, see the online help section Administering Your Environment > Policy Management and Deployment > Instrumentation.
Web console users can launch tools directly from the tool group, or in the context of managed services, nodes, or messages.
Console and web console users can search the console tree to quickly find services, nodes, tools, and policies within policy groups.
The Policy Properties dialog box provides a list of policy groups that contain the policy and a list of nodes to which the policy is currently deployed.
HPOM 8.16 for Windows includes localized versions for the Japanese, Korean, and Simplified Chinese languages. On a system with an MUI, the user’s language setting in Windows automatically determines the language that appears in the HPOM console and online help. During the installation of a management server on a system with an MUI, you can select the language for the default tools, policies, and other objects that HPOM provides.
The new ovowserviceutil command-line tool complements the already existing ovownodeutil, ovowtoolutil, and ovowmsgutil range of command-line tools.
The server-based MSI enables you to read messages from the internal message stream on the management server, to modify them as required, and to write them back.
Service logging is configured using the new ServiceLogger Service GUI tool, which is available in the tool group HP Operations Manager Tools > Service Logging. Use the service logger configuration dialog to select or clear the services to be logged. The status of selected service is logged every five minutes. When at least 24 hours of data exist, the data can be used to produce reports. Logging is available for autodiscovered and for self-defined services.
HP Performance Agent Software, version 4.70 can be integrated with HPOM 8.16 for Windows. You can deploy HP Performance Agent Software from the HPOM for Windows console. You can also centrally control and configure HP Performance Agent Software from HPOM for Windows. For more information, refer to the HP Performance Agent Software Deployables Installation Guide and the topic HP Performance Agent Software from the HPOM for Windows console online help.
HPOM for Windows now includes licenses to use HP Reporter and HP Performance Manager. You can install HP Reporter locally on the management server or remotely. The license for HP Performance Manager can only be used on the same computer as your HPOM management server. For more information about what's new in HP Reporter 3.80 and HP Performance Manager 8.10, see the release notes for each product.
If HP Performance Manager is available on the management server, you can access the graphs that it provides from the web console.
The HPOM Incident Web Service exposes messages as ITIL-compliant incidents. The service enables remote clients that you develop to get incidents from HPOM, and to create and update incidents in HPOM.
The HPOM Tool Web Service enables remote clients that you develop to start applications, scripts, and commands on managed nodes using the HPOM action system.
This version of the HP SiteScope Adapter provides predefined HPOM policies for each HP SiteScope monitor class as well as a policy that provides HP Operations Manager i (HP OMi) with advanced information about the UCMDB configuration item (CI) being monitored by the SiteScope monitor.
HPOM 8.16 includes localized versions for the Japanese, Korean, and Simplified Chinese languages. During the installation of management servers that have an English version of a Microsoft Windows operating system, you can choose to install localized versions of the policies that HPOM provides. For this reason, the default hierarchy of policy groups in HPOM 8.16 contains extra subgroups for the localized policies. For example Microsoft Windows > en > Web Servers contains English versions of policies that were previously in the policy group Microsoft Windows > Web Servers.
| New policies and policy groups | Changed policies | Obsolete policies and policy groups | |
|---|---|---|---|
| Self Management Module The name of the self management policy group has changed from OV Operations Self Manager to HPOM Self Management. 1 2 |
|||
| Sample Policies |
|
||
| Service Logging Module |
1 These features were also included in HPOM for Windows 8.00.
2 These features were also included in HPOM for Windows 8.10.
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,
go to the following web site:
http://h20230.www2.hp.com/selfsolve/manuals
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 web site:
http://www.adobe.com
Installation requirements, as well as instructions for installing HPOM for Windows, are documented in the HP Operations Manager for Windows Installation Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's installation media as:
\Documentation\HPOM Guides\en\HPOM_Installation_Guide.pdf
After installation the document can be found at:
%OvInstallDir%\paperdocs\en\
For SPI installations, see the HP Operations Smart Plug-ins DVD Installation and Upgrade Guide and HP Operations Smart Plug-ins DVD Release Notes for more information.
Software and hardware requirements can be found in the HP Operations Manager for Windows Installation Guide.
Supported platforms are specified in detail in the support matrix available at this location:
http://support.openview.hp.com/selfsolve/document/KM323488
NOTE: If you are upgrading from previous versions of HP Operations Manager for Windows, be sure to read the upgrade guide, available in .htm format on the product media. You must take certain steps before installing the current release.
Database in compressed directory not supported (QCCR1A99308)
Symptom: The HPOM for Windows 8.16 installation fails. The detailed installation log file contains the following error message:
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
Solution: The installation attempts to install the database to a compressed volume. This is not supported.
Management server installation on Windows 2008 cannot find the file iisext.vbs. (QCCR1A100502)
Symptom: The HPOM for Windows 8.16 installation on Windows 2008 systems cannot find the file iisext.vbs. The detailed installation log file contains the following error message:
Input Error: Can not find script file "C:\Windows\system32\iisext.vbs".
Solution: The installation completes successfully and HPOM for Windows is fully functional. You can ignore the error message.
Remote console fails to connect to the management server (QCCR1A99969)
Symptom: Remote consoles on Windows XP fail to connect to management servers on Windows Server 2008.
Solution: Install the hotfix KB969442 for Windows XP SP3 on the remote console system:
http://support.microsoft.com/kb/969442
Confusing errors in log files after removing a remote console (QCCR1A99712)
Symptom: The following error is listed in the summary and detailed remove log files after removing a remote console:
Failed to remove 'HP Operations Manager - Server and Console core components'
Solution: Check the detailed remove log file. If the error code returned by Windows Installer for the MSI is 3010, then the MSI was uninstalled successfully and you can safely ignore the error. The remote console installation is removed successfully.
Rollback does not complete on first cluster node (QCCR1A99742)
Symptom: Start a rollback during the installation of the 20th HPOM installation package on the first node in a cluster. The rollback cannot complete because some services cannot be stopped. Stopping these services manually and retrying the rollback does not help the rollback to complete successfully.
Solution:
Wait until the error dialog appears.
Open the Failover Cluster Management Console and stop all but the following resources in the HP Operations Manager Cluster resource group:
Click Repeat in the error dialog.
Some processes are stopped after installing the HPOM management server on the first node in a cluster (QCCR1A19434)
Symptom: After you install the HPOM management server on the first node in a cluster, some processes may have the status 'stopped'. To check the status of these processes, open a command prompt, and then type ovc -status.
Solution: To start the processes, open a command prompt, and then type ovc -start. Alternatively, restart the computer.
The management server installation on a cluster does not configure cluster-aware agents correctly (QCCR1A41110)
Symptom: After HPOM for Windows 8.16 is installed on a cluster, the management server policies configured in the OvOWSelfManagement.apm.xml file are disabled on all nodes of the cluster, including the node that currently owns the HPOM resource group.
Solution: Run the following commands on all cluster nodes:
ovclusterinfo -a to obtain the name of the physical node as it is known in the cluster configuration:
ovclusterinfo -a
ovconfchg -ns conf.cluster -set CLUSTER_LOCAL_NODENAME <name>
Replace <name> with the name of the node as reported in the output of ovclusterinfo -a.
Stop the agent:
ovc -stop AGENT
ovc -stop COREXT
Restart the agent:
ovc -start COREXT
ovc -start AGENT
Agents are missing on cluster nodes after migration (QCCR1A98548)
Symptom: When you migrate a standalone HPOM installation to a cluster installation on which the virtual name of the new cluster is the same as the hostname of the old standalone system, the agents are absent on all cluster nodes. Deployment jobs fail with the description "nodes are managed by another OMW Server."
Solution: When migrating a standalone HPOM installation to a cluster installation, always use a new name for the resource group, a name that has not been used before.
After upgrading from OVO for Windows 7.50 errors occur while uninstalling Reporter packages for SPIs (QCCR1A24866)
Symptom: After upgrading from OVO for Windows 7.50 to HPOM for Windows 8.10, one of the following error messages appears while uninstalling Reporter packages for any of the SPIs:
The errors occur because the upgrade process removes the ReporterLite component.
Solution: Before you upgrade OVO for Windows 7.50 to HPOM for Windows 8.10, manually remove all Reporter packages for all installed SPIs using the Smart Plug-ins, New and Upgraded CD, for use with HP OpenView Operations 7.5 for Windows.
To remove Reporter packages on the management server:
For example, to remove the Reporter package for the SPI for SAP, double-click the file sapspi_reporter.msi in the folder \SPIs\SAP SPI Reporter Package.
The following platforms are obsolete with HP Operations Manager 8.16 for Windows. Some of the platforms listed below may also become obsolete for version 7.50 of HP Operations Manager for Windows.
NOTE: The HP Obsolescence Policy provides you with the guidelines about the obsolescence of this product. To see the published policy, go to:
http://support.openview.hp.com/pdf/obsolescence_policy_v4.3.pdf
Also review the support matrix available at:
http://support.openview.hp.com/selfsolve/document/KM323488
HP discontinues support of the following agent platforms with the release of HP Operations Manager 8.16 for Windows.
HP ended certification of new platforms for the DCE agent at the end of June 2008. New operating system versions and cluster or virtualization solutions released by the respective vendors are no longer tested and supported by the DCE agent.
DCE agent support for HP Operations Manager 8.16 for Windows will be discontinued at the same time as HP Operations Manager 7.50 for Windows will reach end of support. Visit the HP Software Support web page for announcements.
HPOM 8.16 for Windows will not support the following management server platforms. Service Packs will become obsolete as per Microsoft lifecycle policy.
The following console platforms are not supported with HPOM 8.16 for Windows. Service Packs will become obsolete as per Microsoft lifecycle policy.
The following web console platforms are not supported with HPOM 8.16 for Windows:
The following high availability solutions are not supported with HPOM 8.16 for Windows:
HP discontinues support of the following databases:
HPOM 8.16 for Windows does not support the following integrations:
HP plans to obsolete the following platforms, integrations, and languages with the next major release of HP Operations Manager for Windows after version 8.16.
HP appreciates your feedback. Contact your HP sales or support representative if you would like HP to continue supporting the managed node platforms listed in this section with the next major release.
HP is considering to not offer the next major release of HP Operations Manager for Windows after version 8.16 in the following language:
Occasionally the previous HP OpenView Operations product name or its OVO abbreviation may appear as an application name in a message browser message, in error messages, or in a policy name. This is not a cause for concern.
Reinstalling packages on the management server causes misleading error messages and the console closes suddenly (QCCR1A19359)
Symptom: If you create a job to reinstall all packages on a management server, misleading error messages may appear and the console may close suddenly. You may be unable to reopen the console for several minutes. If you are also reinstalling policies, the policy deployment jobs fail.
Solution: Reinstall packages on the management server without reinstalling policies at the same time. After you start the reinstall job, open Windows Task Manager, and view the list of running processes on the management server. Agent installation processes are running with the image name msiexec.exe. (Alternatively, wait until the agent installation log file opc_inst.log no longer exists in %SystemRoot%\temp.)
When all the processes finish, reopen the console if necessary. The job to reinstall all packages on the management server succeeds. Reinstall policies on the management server. If any other deployment jobs have failed, restart them.
In some cases, policy auto-deployment does not start on management servers in a clustered environment (QCCR1A19318)
Symptom: Policy auto-deployment is fully enabled on the management server in a clustered environment, but the management server does not automatically deploy any policies.
Solution: To activate policy auto-deployment:
On each management server cluster node, log in using the same credentials that you used to install HPOM. Open a command prompt, and type the following command:
mofcomp "%OvInstallDir%\misc\OvOW\moffiles\en\OvMiscModel.mof"
Deploy the following policy group to all Windows nodes, including the management server:
Microsoft Windows\en\Auto-Discovery\Auto-Deploy
Deploy the following policy group to all other nodes:
SPI for Unix OS\en\Auto-Discovery\OS SPI Discovery
ovowclusterchkrep does not show the text "Pending uninstallations" or "Missing installations" (QCCR1A97628)
Symptom: If you run the tool ovowclusterchkrep on a management server installed on a cluster (Windows 2003 or 2008), the output does not include information about "Missing installations" or "Pending uninstallations." It is therefore more difficult to detect an inconsistent patch status of the cluster.
Solution: Use vpstat -p on all cluster nodes and compare the results manually.
Permissions for message groups from opposite user roles are not applied properly to members of these user roles (QCCR1A96200)
Symptom: If a user is a member of more than one user role with different permissions for message operations, the more restrictive permissions are applied. This is the correct behavior. If you then reverse the permissions for these user roles, the more liberal permissions are applied, which is incorrect.
Solution: A user should be a member of one user role only.
SiteScope Tomcat policy does not monitor the Tomcat process for HP SiteScope 9.50 (QCCR1A37396)
Symptom: The SiteScope Tomcat policy does not monitor the Tomcat process for HP SiteScope 9.50 because the process name has changed. If the HP SiteScope server stops, only the message "SiteScope Server not running" is sent. The message "Tomcat Java Container not running" is not sent. In HP SiteScope 9.50, the Tomcat process has the name SiteScope.exe. The policy expects java.exe, which was the correct process name in previous versions.
Solution: Edit the policy to replace the process name java.exe with SiteScope.exe. Deploy the policy to the node that has HP SiteScope 9.50.
HPOM for Windows services on the management server fail to start (QCCR1A37349)
Symptom: After a reboot of the HPOM for Windows management server with the HP BAC Adapter installed, the HPOM for Windows services may take a long time to start or may fail to start.
Solution:
Open the Start menu and select Run. Then type regedit and click OK.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HPOvOpc2Bac
DependsOnService to modify it, add the following string at the end of the list (in a new line), then click OK:
OvEpMessageActionServer
Generic Service in the HPOM for Windows resource group, then click Next.HPOvOpc2Bac in the Generic Service Parameters page, then click Next.For more information about certificate management and problems related to certificate handling, see the Certificate Management in Environments with Multiple HP BTO Software Products white paper. This document is located on the product media, in the Documentation\Whitepapers directory.
Incident and Tool Web Services fail if .NET is installed before Microsoft Internet Information Services (IIS)
Symptom: IIS and .NET are prerequisites for the HPOM for Windows management server. The HPOM for Windows installation installs .NET if necessary, but does not automatically install IIS. If you install .NET before IIS, the Incident and Tool Web Services fail. For example, you get a page not found error if you type the following URL in a web browser:
https://<HPOM_server_name>:<IIS_HTTPS_port>/opr-webservice/Incident.svc
(the default IIS HTTPS port is 443).
Solution: Ensure that you install IIS before .NET if possible. Otherwise, after you install IIS, repair the .NET installation as follows:
Additionally, if you have already installed HPOM for Windows on the management server:
Open a command prompt, and type the following command, which ensures that .NET is registered with IIS:
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Insert the HPOM for Windows installation media on the management server. In the command prompt, navigate to the following folder:
\Packages\Web Services
Type the following command, which uninstalls the Incident and Tool Web Services:
msiexec /x HPOprWsInc-08.30.009-WinNT4.0-release.msi ZBIGNORECONDITIONS=TRUE
Type the following command, which reinstalls the Incident and Tool Web Services:
msiexec /i HPOprWsInc-08.30.009-WinNT4.0-release.msi
Restart the World Wide Web Publishing Service.
Documentation contains incorrect version numbers: 8.00 and 8.10 (QCCR1A99833)
Symptom: Not all occurrences of the HPOM for Windows version number have been updated to 8.16 in the online help, manuals, and white papers.
Solution: You can ignore the outdated version number. The documentation provided with HPOM 8.16 for Windows applies to version 8.16, even if the version number of the documentation states 8.00 or 8.10.
HPOM 8.16 for Windows includes localized versions for the Japanese, Korean, and Simplified Chinese languages.
NOTE: The documentation for the Korean version of HPOM 8.16 for Windows has not been updated. HP recommends that you use the updated English documentation with the Korean version of HPOM 8.16 for Windows.
To configure a Korean HPOM installation to use the English online help, rename the folder %OvInstallDir%\help\ko to %OvInstallDir%\help\ko.orig. When you now access the online help from the console, the updated English online help displays.
NOTE: The patches included with HPOM 8.16 for Windows are not localized so you may occasionally encounter English text. The next major release of HPOM for Windows will be fully localized again.
You can visit the HP Software Support web site at:
http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP offers.
HP Software 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 do the following:
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://h20230.www2.hp.com/new_access_levels.jsp
To register for an HP Passport ID, go to the following URL:
http://h20229.www2.hp.com/passport-registration.html
©Copyright 2010 Hewlett-Packard Development Company, L.P.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software developed by the Jaxen Project (http://jaxen.org/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
This product includes Sentry Spelling-Checker Engine, which is Copyright © 2000 Wintertree Software Inc.
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.
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.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java™ is a US trademark of Sun Microsystems, Inc.
Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.