Altiris® Connector™ 6.0 SP1 for HP OpenView Release Notes

Article:DOC1275  |  Created: 2006-10-30  |  Updated: 2006-11-03  |  Article URL
Article Type


What do I need to know about the 6.0 SP1 release of Altiris® Connector™ for HP OpenView?


Release Notes
for Altiris® Connector™ 6.0 SP1 for HP OpenView

Installation and Upgrade

New Features in this Release

Fixes in this Release

Known Issues

Additional Documentation

Document History

Installation and Upgrade


  • Altiris® Notification Server™ 6.0 or higher must be installed on the computer you are installing Altiris® Connector™ 6.0 SP1 for HP OpenView on. For more information, see the Altiris Notification Server Help.
  • The Notification Server computer with this Connector installed must have access to an HP* OpenView* server.

Caution: Only one Notification Server should be connected to any HP OpenView server. If more than one Notification Server attempts to connect to an HP OpenView server, files will be overwritten on the HP OpenView computer. However, you can connect a single Notification Server to as many HP OpenView servers as you require.

Note: Connector for HP OpenView supports HP OpenView Service Desk* 4.5 SP6 – SP18, HP OpenView Operations* 7.0 for Windows*, and HP OpenView Network Node Manager* 6.2 for Windows*.

Note: After the installation of the Connector Agent, it is necessary to replace the web API file (web-api.jar) in the ConnectHPOVSDAgent\Lib folder on the Service Desk computer with the matching service pack version.

  • Altiris® Connector Solution™ 6.1 must be installed on the Notification Server.

Where to Download Connector for HP OpenView

Altiris Connector Pack for HP OpenView.exe can be downloaded from to install for the first time or upgrade from previous versions.

New installation

If you are installing this Connector without any previous version installed, follow these steps.

  1. Open the Altiris Console by selecting Start > Programs > Altiris > Altiris Console.
  2. Click the Configuration tab.
  3. In the left pane, click Upgrade/Install Additional Solutions.
  4. In the content pane, click the Available Solutions tab.
  5. Click the Segments sub-tab.
  6. Click Connectors.
  7. Click Altiris Connector Pack for HP OpenView.
  8. Click Start.

Upgrading from Version 5.5

If you are upgrading from Connector 5.5 for HP OpenView, follow these steps for installation.

  1. Uninstall Connector 5.5 for HP OpenView by following the instructions in the Connector 5.5 for HP OpenView documentation.
  2. Install Connector 6.0 for HP OpenView.

Upgrade Issues

The following items should be considered when upgrading to Connector 6.0 SP1 for HP OpenView.

 Upgrade Issue
Configuration Item Search Codes May or May Not be Replaced with Data Import

For the 6.0 SP1 release the algorithm designed for creating search codes was updated. As a result, search codes created for configuration items are now different. In some cases the data import may update previously imported configuration item search codes; however, we strongly recommend that this functionality be verified in your test environment first, before rolling out the upgrade to a production environment.

User Search Codes Will Not be Replaced with Data Import

Previously imported user search codes cannot be updated with a new data import. Users should first be removed in the HP Openview service desk and then re-imported. This eliminates the possible duplication of users stored in the system.

New Features in this Release

Improvements for this release include the following new features:

Feature Description

1.      Support for UNIX Solaris

This release of Connector for HP OpenView supports HP OpenView Service Desk* servers running on UNIX* Solaris*.

Configuring your UNIX Solaris server to work with Connector for HP OpenView Service Desk
The following are configuration steps for using Connector for HP OpenView Service Desk with a Solaris server.

  1. Make sure that HP OpenView Service Desk and the latest service packs are installed and configured on the Solaris computer.
    Note: In Altiris testing, we used HP OpenView Service Desk Server installed on a Solaris server, while MS SQL* database and HP OpenView Service Desk Client were installed on a separate Windows* computer. (The server-database communication was established through a JDBC driver.)
  2. Create a file structure on Solaris similar to that in the Windows* environment for the Altiris Connector Agent. Namely, create the \Altiris\ConnectHPOVSDAgent directory with Import, Archive, Error, and Lib subdirectories.
  3. Install and configure a file share on the Solaris computer, and share it with the Notification Server. Place the .XML files generated from the data export there.
    Note: In our tests, a SAMBA file share was used.
  4. Get the Connector Agent application files from the Notification Server computer in the \Altiris\ConnectHPOVSD\Agent\Manual folder and copy them to the \Altiris\ConnectHPOVSDAgent folder on the Solaris server.
  5. On Solaris, in the Configuration.xml file, make the necessary changes. Make sure that the importFolderPath, importArchiveFolderPath, importErrorFolderPath, and filePath point to the correct directories on Solaris.
  6. Create a file. This file is to be used instead of the ConnectHPOVSDAgent.bat file used in a Windows environment.
  7. You may use the following content to create the file:
    #!/usr/bin/sh java -jar -Xmx256m -Xms256m "./Lib/connectHPOVSDAgent.jar" Configuration.xml
  8. From the Terminal, run the file to initiate the data import.
  9. Upon completion, view the results of the import in the Log.txt file and in the HP OpenView Service Desk Client Console in the same manner as in a Windows environment.

2.      Faster Export Configuration Page

The Export Configuration page loads faster than it has in previous releases.

3.      New Computers are Now Captured in the “changes only” Export

When running a “changes only” export, new computers added to the specified collection are now captured in the export.

4.      It is now possible to create multiple Export Configurations

This feature of Connector for HP OpenView is now fully functional.

Fixes in this Release

The following issues were resolved in this release.

Fixed Issue
Upgrade code duplication with ConnectHPOVO and ConnectHPOVNNM has been fixed

This fix applies to new agent installations only. Previously, there was duplication of connector agent installer GUIDs for HP OpenView Operations and Network Node Manager. However, if your connector agent has already been installed and is working correctly, then no agent update is required.

Data Import Errors have been removed

An error found with writing to the Name2 field has been resolved.

Duplicate Records in Export Files have been fixed

Known Issues

The following are unresolved issues in this release:

Known Issues for for Connector for HP OpenView Service Desk

Configuration and Log Files Over-Written On Connector Agent Upgrades

If you have the Connector BETA for HP OpenView installed, you may want to back up your Configuration.xml and log.txt files in your ConnectHPOVSDAgent folder before installing the Connector.

Requires HP OpenView Service Desk SP6 or Above to Support Computer to User Associations

You are required to have HP OpenView Service Desk SP6 or above in order to support computer-to-user associations.

Data Integration Component of Connector Solution Limits Exports to 50,000 Rows

The data integration component of Connector Solution sets a limit of 50,000 rows on report results being exported. This means that if you are using the Connector for large databases, you may be unable to export everything desired.

Requires Replacement of Web API JAR File

After the installation of the Connector Agent, it is necessary to replace the web API file (web-api.jar) in the ConnectHPOVSDAgent\Lib folder on the Service Desk computer with the matching service pack version.

Known Issues for Connector for HP OpenView Operations and Network Node Manager
Connector Agent Install Package May Be Created Multiple Times When Configuration "Apply" Button Clicked

This is sometimes associated with a timeout of the process and you will need to click "Apply" a second time.

Manual Steps Required for Uninstalling Connector Agent from HPOV Computers due to Integration Limitations in HPOV Apps

You must uninstall the Connector Agent manually from HP OpenView computers. For information on doing this, see the Altiris Connector for HP OpenView Product Guide.

Additional Documentation

Altiris product documentation is available in Microsoft HTML Help* (.CHM) and Adobe Acrobat* (.PDF) formats. To view Altiris product documentation in .PDF format, use Adobe Acrobat Reader* (available at:

Documentation files are installed in the following directory on the Altiris® Notification Server™ computer:
C:\Program Files\Altiris\Notification Server\NSCap\Help.

The following documentation is provided with Altiris Connector for HP OpenView

Connector 6.0 SP1 for HP OpenView Product Guide (HPOVConnector.pdf & HPOVConnector.chm)

You can access documentation from the Altiris Console by clicking the following icons in the upper-right corner of the console:

Access the contextual online help by clicking the online help icon .
Access an index of all installed help by clicking the index icon help index.

Altiris Information Resources

Source What Information it Includes Where to Find it
Altiris Documentation Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as Release Notes, Help, Reference Guides, Best Practice Articles, and Technical Reference Articles.
Altiris Knowledgebase Comprehensive collection of articles, incidents, and issues for Altiris solutions.
Altiris Juice:
an online magazine for Altiris users
Best Practices, tips and tricks, and articles for users of Altiris solutions.
Online Forums Forums for Altiris solutions and suites.

Document History

 Date  Changes
10/30/2006 The initial document draft was posted to the Altiris Knowledgebase for review.
11/02/2006 The document's formal edit #1 was completed.
11/06/2006 Formal edit requests from the formal edit were added.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices