LTIRISﬁ CONNECTOR PACK 6.0 FOR HP...

ALTIRIS®

CONNECTOR PACK 6.0 FOR HP OPENVIEW PRODUCT GUIDE

Altiris Connector Pack for HP OpenView Product Guide 2

Notice

Copyright © 1998-2005 Altiris Inc. All rights reserved.

Product Version: 6.0

Document Date: March 9, 2005

Bootworks U.S. Patent No. 5,764,593.

RapiDeploy U.S. Patent No. 6,144,992.

Recovery Solution U.S. Patent No. 5,778,395, 5,907,672, 4701745, 5016009, 5146221, 5144425, 5463390, 5506580, 5532694, GB 2172127, B 904359, 3606869.

Other patents pending.

Due to the inherently complex nature of computer software, Altiris does not warrant that the Altiris software is error-free, will operate without interruption, is compatible with all equipment and software configurations, or will otherwise meet your needs.

The content of this documentation is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Altiris. Altiris Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. For the latest documentation, visit our Web site at www.altiris.com.

Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy, and RapidInstall are registered trademarks of Altiris, Inc. in the United States and in other countries.

Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark of Altiris, Inc. in other countries.

Altiris eXpress, Altiris Protect, Application Management Solution, Application Metering Solution, Asset Control Solution, Asset Management Suite, Client Management Suite, Compliance Toolkit, Connector Solution, Conflict Analysis Solution, Contract Management Solution, Deployment Server, Deployment Solution, Energy Saver Toolkit, Education Management Suite, Helpdesk Solution Software, Lab Management Suite, Migration Toolkit, Mobile Client for SMS, Monitor Solution, Notification Server, Patch Management Solution, Problem Management Suite, Recovery Solution, Server Management Suite, Site Monitor Solution, Software Delivery Solution, TCO Management Solution, UNIX Client for SMS, Web Administrator for SMS, Web Reports, and other product names are trademarks of Altiris, Inc. in the United States and other countries.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

HP and Compaq are registered trademarks of the Hewlett-Packard Corporation.

Dell is a registered trademark of Dell Inc.

Macintosh is a registered trademark of the Apple Computer Corporation.

Palm OS is a registered trademark of Palm Computing, Inc.

BlackBerry is a service mark and a trademark of Research In Motion Limited Corporation.

RIM is a service mark and trademark of Research In Motion (RIM)

All other brand names are trademarks or registered trademarks of their respective companies.

http://www.altiris.com

Contents

Altiris®Connector Pack 6.0 for HP OpenView Product Guide

Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Two-way Integration with HP OpenView NNM and Operations Servers . . . . . . . . . . . . . . . . . . . . . . . . 9Using with Altiris Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing the Connector for HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Uninstalling the Connector for HP OpenView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Using the Connector for HP OpenView Service Desk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Setting Up and Using the Connector for HP OpenView Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . 17

Install the Altiris Connector Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Configure the Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Run a Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Configure the Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Run a Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Verify the Data Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Integrate the UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Using with Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Configure Data Exports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Download Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Database Access Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Out of Memory Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Database Scalability Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Using the Connector for HP OpenView Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Setting Up and Using the Connector for HP OpenView Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Add your Operations Servers to the SNMP Destinations Collection . . . . . . . . . . . . . . . . . . . . . . . 40Create a Connector Agent Installer for each Operations Server . . . . . . . . . . . . . . . . . . . . . . . . . . 41Install the Connector Agent Installer on your Operations Servers . . . . . . . . . . . . . . . . . . . . . . . . . 41Access Altiris Items on the Operations Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Making a Trap a Critical Error in HP OpenView Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 42Accessing Resource Manager in HP OpenView Operations . . . . . . . . . . . . . . . . . . . . . . . . . . 42


Contents
How the SNMP Management Agent Interacts with the HP OpenView Operations Server . . . 43How to set up and use Contextual Menu Integration Between HP OpenView Operations and Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Using the Connector for HP OpenView Network Node Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Setting Up and Using the Connector for HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Add your NNM Servers to the SNMP Destinations Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Create a Connector Agent Installer for each NNM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Install the Connector Agent Installer on your NNM Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Access Altiris Items on the NNM Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Altiris Integration with HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Making a Trap a Critical Error in HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Accessing Resource Manager in HP OpenView NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51How the NS SNMP Agent Interacts with the HP OpenView NNM Server . . . . . . . . . . . . . . . . 52

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56OVSD Configuration Item (CI) Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56OVSD Person Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Altiris Connector Pack 6.0 for HP OpenView Product Guide 5

Getting StartedThis section will introduce you to the Altiris Connector for HP OpenView and an overview of its features, including installation.

Quick Links

�Overview� on page 6 Provides an introduction to the Connector for HP OpenView.

�Installation� on page 13 Install the Connector for HP OpenView on your Notification Server.

Overview

The Altiris Connector Pack for HP OpenView provides seamless integration that extends and enhances HP OpenView solutions including Network Node Manager, Service Desk, and Operations. The complementary strengths of Altiris and HP solutions allows you to implement a more comprehensive management solution that will prevent downtime, resolve problems faster and keep computers running efficiently. The Altiris IT lifecycle management strategy extends HP OpenView management to provide inventory, asset, software and configuration management for desktops, notebooks, handhelds, and servers.

As a strategic partner for HP OpenView, Altiris is a registered HP OpenView Solution Alliance Partner and has obtained certification for the Altiris Connector for HP OpenView. HP OpenView provides a proactive, service centric approach to monitoring the network, system, applications and storage. By anticipating hardware and software problems before they occur, HP OpenView optimizes system performance and availability. As an IT manager, you can leverage the complementary strengths of HP OpenView and Altiris solutions to implement a more comprehensive management solution that will provide alerts, detailed computer information, and access to problem resolution solutions that will keep your computers running optimally. Altiris' comprehensive Web-enabled solutions empower organizations to manage computers throughout the IT lifecycle.

IT Infrastructure Library (ITIL) provides best practice processes that enable IT to realize their key objective of service management. Altiris solutions support many ITIL processes, but significantly support Configuration, Change, Release and Problem Management. Integration between Altiris and HP OpenView further enhances the quality of IT service that is delivered, reduces overall cost of ownership and helps align IT services with business needs.

You can, through your central HP OpenView consoles, gain additional visibility and get a more complete picture of your enterprise IT resources, allowing for more efficient management. By integrating your Altiris solutions into the HP OpenView consoles, you extend your tracking of issues to client computers and applications. Alerts from installed Altiris solutions can be forwarded to the HP OpenView consoles for comprehensive system monitoring of your IT environment. Detailed inventory from Altiris is accessible from within HP OpenView, providing the information needed to properly troubleshoot problems. Access to Altiris solutions is integrated in the integrated HP OpenView consoles to provide management tools that will reduce the time needed to resolve issues such as image deployment, software repair and updates, identifying inventory changes, software license management, remote control and management reporting. By integrating HP OpenView with Altiris solutions, you can move easily between the two management systems and problem resolution capabilities.

HP OpenView and Altiris integration help you achieve a higher return on investment (ROI) through an integrated approach to PC deployment and migration, inventory and asset management, and software, change, and SLA management. Providing you with solutions that address your business needs and keep your systems operating optimally is a key benefit of the integrated approach between Altiris and HP OpenView.

Altiris offers server provisioning across heterogeneous server hardware and manages heterogeneous client systems. Enhanced capabilities exist for HP/Compaq clients or ProLiant servers that take advantage of co-developed technology from Altiris and HP. HP Client Manager Software is a free hardware management solution for HP clients that generates hardware-specific alerts such as memory changes, chassis intrusion, or hard disk errors that can be forwarded to HP OpenView. HP specific hardware information is combined with other Altiris software inventory to provide additional troubleshooting information that is accessible from within HP OpenView consoles. HP ProLiant Essentials Rapid Deployment Pack uses the same Altiris infrastructure to deploy all ProLiant servers. Altiris solutions complement and extend HP OpenView.


Overview
Features and BenefitsHP OpenView Network Node Manager (NNM) and Operations
� Event forwarding via SNMP traps - Meet service level agreements (SLAs) with additional monitoring capabilities.

� Right-click access to detailed Altiris inventory - Streamline IT problem resolution via contextual access to in-depth client and server inventory.

� Launch Altiris solutions from within the HP OpenView console - Speed IT service delivery through quick access to the Altiris suite of tools to image, update software and configuration, track, and fix computer problems.

HP OpenView Service Desk (OVSD)

� Import Altiris hardware and software inventory into the Service Desk Configuration Management Database (CMDB) - Maximize IT asset management integrating inventory data with service, incident, change, and contract data.

� Automatically create parent/child relationships between hardware, software, and host systems - Provide comprehensive picture of the computer, including all installed hardware and software.

� Create new hardware and software records as components are added to the environment - Enable automated change management, software licensing, and full hardware component inventory.

� Standard and user-configurable inventory data and category mapping between Altiris and OVSD - Adapt to your specific setup by permitting level of inventory integration to be defined.

� Import uses ITIL business rules to establish parent/child relationships, record changes, and add new records to OVSD - Automate processes including set record status, check for duplicate records, enable software license tracking, and determine record type, category, and data defaults.

Altiris Notification Policies are designed to notify IT administrators of certain conditions that have occurred on an IT resource, namely desktop computers, notebooks, and servers. Based on these notifications, Altiris provides you many tools to assess and repair the condition.


Overview
The Connector for HP OpenView provides integration between Altiris solutions and HP OpenView modules, including HP OpenView Network Node Manager (OVNNM), HP OpenView Operations (OVO), and HP OpenView Service Desk (OVSD). Altiris can forward events to OVNNM and OVO and forward inventory to Service Desk.
The Connector for HP OpenView includes three components:

� OVNNM Event Management - This component lets you forward events to an HP OpenView Network Node Manager server via SNMP traps, view Altiris inventory via right-clicking on a node, and launch the Altiris console from within HP OpenView.

� OVO Event Management - This component lets you forward events to an HP OpenView Operations server via SNMP traps and launch the Altiris console from within HP OpenView.

� OVSD Data Extraction - This component lets you extract Notification Server inventory data in XML format for import into HP OpenView Service Desk.

See Also� �Two-way Integration with HP OpenView NNM and Operations Servers� on page 9� �Using with Altiris Solutions� on page 10� �Installing the Connector for HP OpenView� on page 13� �Using the Connector for HP OpenView Service Desk� on page 17� �Using the Connector for HP OpenView Operations� on page 40� �Using the Connector for HP OpenView Network Node Manager� on page 47


Overview Two-way Integration with HP OpenView NNM and Operations Servers
Two-way Integration with HP OpenView NNM and
Operations ServersThe Connector for HP OpenView provides for a two-way integration with HP OpenView NNM and Operations servers:

1 You can configure Notification Server to forward all or selected Notification Policies to an HP OpenView server. A configuration page has been created that lets you set up the link to the HP OpenView server, configure which policies will be forwarded, and test a sample trap for communication validation.

2 On the HP OpenView side, there is a MIB that is imported into HP OpenView to translate all the Notification Server traps to standard SNMP alerts. You can individually configure these traps as to whether they are critical, major, minor, normal, or a warning and whether they change the color of the resource in the console.There is also an ARF (application registration file) installed that allows 3rd party integration. This allows Altiris to provide a menu option from the HP OpenView console, to launch the Altiris Resource Manager, which provides detail information about the device, and provides a user interface that allows you to remote control the device. By simply right-mouse clicking on a computer within HP OpenView, there will be a new option to launch the Resource Manager for that computer.

Figure 1 below illustrates what can be set up with this integration. In our example, a computer has experienced a low disk space condition:

1 An Altiris enabled computer notifies the Notification Server that it is low on disk space.2 The Notification Server has an enabled policy with an Automated Action to forward an SNMP

trap to an HP OpenView server (when it gets a low disk space alert from an Altiris enabled computer).

3 HP OpenView receives the SNMP trap identifying the problem computer and records the trap in the Alarms browser.

4 The computer is displayed in HP OpenView. Right-clicking on the computer in HP OpenView provides an option to launch Resource Manager.


Overview Using with Altiris Solutions
5 Altiris reports and Resource Manager provides you with a complete diagnostics set of reports,
including disk space usage reports. One report can also tell you how much disk space can be freed up if you empty the Internet cache, temp directory, etc. Another report shows you how many MP3, GIF, JPG, or other audio/video files are on the drive. You can remote control the computer from here (using Carbon Copy).

Figure 1

Integrating Altiris with HP OpenView provides a complete pro-active systems management solution for both your infrastructure as well as all the devices it services. While HP OpenView can provide the active monitoring and notifying of all systems across the infrastructure, Notification Server provides all the integrated tools necessary to control, manage, and repair those conditions.

Using with Altiris SolutionsQuick Links� �Altiris HP Client Manager Software� on page 11� �Altiris Asset Control� on page 11� �Altiris Inventory Solution� on page 12

Network PCs Altiris Notification Server

HP OpenView Server

1.

2.

3.

4. 5. Notification Server


Altiris HP Client Manager SoftwareAltiris solutions support heterogeneous clients. However, you can take advantage of hardware management for HP/Compaq clients by using the Altiris HP Client Manager software. Hardware-specific alerts such as memory changes, chassis intrusion, or hard disk errors that are generated with HP Client Manager software can also be forwarded to the HP OpenView console. Additional hardware information is combined with other Altiris inventory data to provide the best management for HP clients.
The HP Client Manager software is specifically designed for HP computers, and leverages HP�s Intelligent Manageability technology.

HP Client Manager offers the following capabilities to provide you with the ability to efficiently manage HP and Compaq desktops and notebook computers:

� Client information Client information allows you to perform a hardware inventory of HP and Compaq computers, memory, hard disks, monitors, batteries and more. This information is stored in a central database, so you can quickly find information about any computer associated with the network. You can generate numerous reports to help you analyze the network, resolve TCP/IP address problems, and do growth planning stategies.

� Health monitoring HP Client Manager allows you to monitor the �health�, or proper function, of computer components such as the hard drive, memory, processor, and battery. When a problem arises, an alert is automatically generated and user-specified actions take place to alert you of the problem.

� Diagnostics HP Client Manager gathers diagnostic information and helps track down and analyze problems for supported computers on the network.

� SoftPaq deployment SoftPaqs (software support files such as, BIOS and driver updates) can be deployed from a central location to those computers that need the them. HP Client Manager keeps track of which computers on the network have received SoftPaq updates and those that have not.

For more information on HP Client Manager and other Altiris Solutions, see the Altiris Web site at www.altiris.com.

Altiris Asset ControlThe Connector for HP OpenView lets you export data from Notification Server and import it into HP OpenView Service Desk. If you own Altiris Asset Control, you can import Asset Inventory into OVSD.

Asset Control provides an integrated solution to managing your assets, invoices, purchase orders, and projects.

This solution allows you to do the following:

� Track assets, invoices, purchase orders, projects, and catalog items You can track assets, such as phones, printers, monitors, copiers, and users. You can also track invoices, purchase orders, projects, and catalog items. All of this data can be associated with each other, so assets can be linked to applicable invoices, purchase orders, and projects.

� Associate depreciation schedules with assets You can associate depreciation schedules with assets, which makes it easy to know the current value of an asset.

� Import data from and export data to numerous source types and files Asset, invoice, purchase order, project, and catalog data can be imported from or exported to Microsoft SQL Server, Oracle, Microsoft Access, Microsoft Excel, ODBC sources, and text files. This saves substantial effort in entering data manually, especially if the data is already available. The procedures can be done one time or regularly on a schedule.

� Create inventory data histories Connector Pack for HP OpenView allows you to create a history of inventory data in the Notification Server database, which helps in identifying changes and determining trends.



Tight integration with other solution data Connector Pack for HP OpenView integrates tightly with other Altiris solutions, such as Contract Management and Inventory Solution. With Contract Management, you can associate Connector Pack for HP OpenView assets, invoices, purchase orders, and projects with contracts. With Inventory Solution, you can associate additional computer related data with the computer data collected by Inventory Solution.
For more information on Asset Control and other Altiris Solutions, see the Altiris Web site at www.altiris.com.

Altiris Inventory SolutionThe Connector for HP OpenView lets you export data from Notification Server and import it into HP OpenView Service Desk. If you own Altiris Inventory Solution, you can import computer inventory into OVSD.

Inventory Solution gathers comprehensive software and hardware data from virtually any computer.

Inventory Solution provides these features and benefits:

� Works with Non-Networked Windows workstations Works with computers with no IP connectivity. A floppy disk method has been designed for these non-networked Windows workstations.

� Works with Non-SMS clients Windows workstations that are not SMS clients can be inventoried into Notification Server and integrated into the SMS database.

� Provides full access to all the data from any browser Data can be accessed through Web Reports on Notification Server or through Web Administrator for Microsoft SMS using data that has been forwarded to the SMS database.

� Includes integrated Web Reports Inventory Solution comes with numerous built-in reports that help you analyze and make proactive management decisions based upon Inventory Solution data. This allows quick and easy access to inventory information without having to create custom SQL scripts. Custom reports may also be added and scheduled to run automatically.

� Posts data through files and HTTP Inventory Solution data can be sent to Notification Server through a file or through an HTTP post.

� Deploys through e-mail, URL, login scripts Inventory Solution can be deployed through e-mail, a URL, login scripts, or any other method you have in place to run a program on the target systems running a Windows 32-bit Operating System.

For more information on Inventory Solution and other Altiris Solutions, see the Altiris Web site at www.altiris.com.




Installation

This section tells you how to install the Connector for HP OpenView.

� �Installing the Connector for HP OpenView� on page 13� �Uninstalling the Connector for HP OpenView� on page 14� �Registration� on page 15

Installing the Connector for HP OpenViewThis section explains how to install the Connector for HP OpenView. See �Prerequisites� on page 13 before you install or upgrade.

Quick Links� �Upgrading� on page 13� �Installing� on page 14

Prerequisites� Notification Server 6.0 or higher must be installed on the computer you are installing the

Connector for HP OpenView on. For more information, see Altiris Notification Server Help.� The Notification Server computer with this Connector installed must have access to an HP

OpenView server.IMPORTANT: Only one Notification Server should be connected to any HP OpenView server. If more than one Notification Server tries to connect to an HP OpenView server, files will be overwritten on the HP OpenView computer. However, you can connect one Notification Server to as many HP OpenView servers as you want.Note: The Connector for HP OpenView supports HP OpenView Service Desk 4.5 SP11, HP OpenView Operations 7.0 for Windows, and HP OpenView Network Node Manager 6.2 for Windows.Note: If you are using any service pack prior to HP OpenView Service Desk SP11, you will need to replace the Web API file (web-api.jar) in the ConnectHPOVSDAgent\Lib folder after the Connector Agent installation on the Service Desk computer with the version that matches your service pack level.

� Altiris Connector Solution 6.1 must be installed on Notification Server.

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

To Upgrade the Connector for HP OpenView1 Uninstall the Connector 5.5 for HP OpenView by following the instructions in the Connector 5.5

for HP OpenView documentation.2 Install the Connector 6.0 for HP OpenView (see �Installing� on page 14)


Installation Uninstalling the Connector for HP OpenView
InstallingIf you are installing this Connector without any previous version installed, follow these steps.
To Install the Connector for HP OpenView1 Open the Altiris Console.

� Click Start > Programs > Altiris > Altiris Console

2 Click the Configuration tab.3 In the treeview pane, click Upgrade/Install Additional Solutions.4 In the content pane, click the Available Solutions tab.5 Click the Segments sub-tab.6 Expand either the Connectors or the Partner Solutions list.7 Click Altiris Connector Pack for HP OpenView.8 Click Start.

Uninstalling the Connector for HP OpenViewTo uninstall the Connector for HP OpenView1 Open the Altiris Console.

� Click Start > Programs > Altiris > Altiris Console

2 Click the Configuration tab.3 In the treeview pane, click Upgrade/Install Additional Solutions.4 In the content pane, click the Currently Installed tab.5 Remove the following components by clicking the Remove button next to them:

� Altiris Connector for HP OpenView Service Desk

� Altiris Connector for HP OpenView Operations

� Altiris Connector for HP OpenView Network Node Manager

� Altiris Connector

� Altiris Context Factory

To uninstall the Altiris Connector Agent from the HP OpenView server1 To remove the Connector Agent for HP OpenView Service Desk:

a On the HP OpenView server, go to Add or Remove Programs in the Control Panel and remove Altiris Connector Agent for HP OpenView Service Desk.

b Remove the shared folder that you created (Program Files\Altiris\ConnectHPOVSDAgent\Import by default) and any files that were imported from the Connector.

c If you have customized the Service Desk user interface (either manually or by using one of the files in the ACES folder), manually remove those customizations.

2 To remove the Connector Agent for HP OpenView Operations:a On the HP OpenView server, go to Add or Remove Programs in the Control Panel and remove

Altiris Connector Agent for HP OpenView Operations.b Manually undeploy the �Altiris-Aggregate-Mib� SNMP Interceptor from the management

server node.c Manually delete the �Altiris-Aggregate-Mib� SNMP Interceptor from the list of SNMP

Interceptors.d Manually delete the tools.


Installation Registration
3 To remove the Connector Agent for HP OpenView Network Node Manager:
a On the HP OpenView server, go to Add or Remove Programs in the Control Panel and remove Altiris Connector Agent for HP OpenView Network Node Manager.

b Manually delete the �Altiris� Alert category.

RegistrationEven though this Connector Pack is downloaded as one product, Network Node Manager, Operations, and Service Desk are separate components and need to be licensed separately.

Each Altiris product comes with a 7-day trial license that is installed by default. You can register and obtain a 30-day evaluation license through our Web site at www.altiris.com or purchase a full product license.

To view your current license, open the Altiris Console, click the Configuration tab, and select Licensing.

For more information, see �Licensing Altiris Software� in the Altiris Getting Started Guide on the product CD or on our Web site at www.altiris.com/support/documentation.



http://www.altiris.com/support/documentation


Using the Connector for HP OpenViewThis section provides information about using the Connector for HP OpenView.

Quick Links

�Using the Connector for HP OpenView Service Desk� on page 17

Provides a comprehensive guide for using the Service Desk component.

�Using the Connector for HP OpenView Operations� on page 40

Provides a comprehensive guide for using the Operations component.

�Using the Connector for HP OpenView Network Node Manager� on page 47

Provides a comprehensive guide for using the Network Node Manager component.

Using the Connector for HP OpenView Service Desk

Quick Links� �Setting Up and Using the Connector for HP OpenView Service Desk� on page 17� �User Interface� on page 37� �Troubleshooting� on page 39

Setting Up and Using the Connector for HP OpenView Service Desk

This section walks you through the steps you need to export data from Notification Server, download the Connector Agent, configure the Connector Agent for the data import, and perform a data import. This section assumes that you have successfully installed the Connector for HP OpenView on your Notification Server and have Service Desk set up.

To successfully set up and use the Connector, follow these Quick Steps in order.

Quick Steps� �Install the Altiris Connector Agent� on page 17� �Configure the Data Export� on page 19� �Run a Data Export� on page 20� �Configure the Data Import� on page 21� �Run a Data Import� on page 34� �Verify the Data Import� on page 35� �Integrate the UI� on page 35

See Also� �Using with Solaris� on page 37

Install the Altiris Connector AgentThe Altiris Connector Agent installs files and folders on your Service Desk server that are needed for performing a data import. The Connector Agent installs to the Program Files\Altiris\ConnectHPOVSDAgent folder.

We recommend that after the Connector is installed, you install the Connector Agent before doing anything else with the Connector. This lets you place the Import folder inside the ConnectHPOVSDAgent folder, which is recommended. The Import folder is where the data export component places the XML files that are exported from Notification Server.

See Also� �Configure the Data Export� on page 19


Using the Connector for HP OpenView Service Desk Setting Up and Using the Connector for HP OpenView Service
The following files and folders are included in the Connector Agent installation� ACES - This folder contains templates that you can use for contextual menu integration.� Archive - The Connector Agent places all processed data XML files in this folder.� Lib - This folder contains the Java application files that perform the data import.� Configuration.dtd - This file describes the structure of the Configuration.xml file. This DTD can
help you when you need to edit the Configuration.xml file.� Configuration.xml - This file is where you set up your configuration for the Data Import.� ConnectHPOVSDAgent.bat - This file is for running the Data Import in Windows. You can set

up your Windows Task Scheduler to run the Data Import on a schedule. Alternatively, you can put the command line found in this batch file directly into the Windows Task Scheduler.

� Log.txt - This file contains all logging information generated during the Data Import. Initially, it is empty. During each Data Import, all generated logging information is entered in it. This file will continue to grow and may need to be purged periodically. If you want to save the information that is generated in this file, we recommend that you periodically rename this file. A new Log file will then be created the next time that a data import is run.

To Install the Connector Agent onto a Service Desk server1 From the Service Desk server, open an internet browser.2 Access the Altiris Console and click the Configuration tab view.3 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView

Service Desk > Download Agent Install.


4 Install the Connector Agent to the Service Desk server by clicking the Open button in the File
Download window that appears. This is installed in the Program Files\Altiris\ConnectHPOVSDAgent folder.Note: If the File Download window does not appear, you can click the click here link to install the Connector Agent.Note: If you have Software Delivery Solution installed, you can create a package that deploys the Connector Agent to one or more Service Desk servers. To push the Connector Agent down as a package, the Service Desk server must have the Altiris Agent installed on it.

5 Create an Import folder in the Program Files\Altiris\ConnectHPOVSDAgent\Import folder. This name and location is the default but can be changed to meet your needs. See �Configure the Data Import� on page 21 for more information.

6 Share the Import folder with the Notification Server administrator account.IMPORTANT: We recommend that you not share the Program Files\Altiris\ConnectHPOVSDAgent folder because the Configuration.xml file contains unencrypted user login information.

Configure the Data ExportThis section walks you through the steps of creating a data export configuration. Data export configurations are used for exporting data to the Import folder (by default). You can create as many configurations as you want. For more information, see �Configure Data Exports� on page 37.

After you have created a configuration, you can use it to export data from Notification Server to XML files and place them in a UNC path.

See Also� �Run a Data Export� on page 20

To create a data export configuration1 Open the Altiris Console.

a Click Start > Programs > Altiris > Altiris Console.2 From the Configuration tab, in the treeview pane, navigate to Configuration > Solutions Settings >

Connectors > HP OpenView Service Desk > Configure Data Exports.3 In the Name field, enter the name for the configuration.4 In the Description field, enter a description for the configuration.5 In the Folder Path for Export field, enter the path for the XML files to be exported to. We

recommend that this path be on your Service Desk server. By default in the Configuration.xml file, this path is Program Files\Altiris\ConnectHPOVSDAgent\Import. This folder should be a shared folder to which Notification Server has access.Note: This folder needs to be accessible from the Service Desk server by sharing it. We recommend that this be an empty folder.

6 In the Collection To Export field, select the collection which contains the data you want to export.7 Select Only Export Changes if you want to only export changes each time after the first full data

export.Note: The first data export for any configuration will always be a full data export. Thereafter, a full data export will be performed only if the Only Export Changes checkbox is cleared.

8 In the Data Classes to Export section, select all of the data classes that you want to export. We recommend that you start with Basic Inventory. After you see what gets exported with Basic Inventory, then you can add more data classes as desired. Note: In tests run by Altiris, the data export/import process took approximately 7 seconds per computer when only basic inventory was selected. Your time may vary depending on your system configuration. Remember, the more data classes that you select, the slower the data export/import will be.


9 In the Scheduling section, select Enable Schedule, then select the schedule that you this data
export to run on. This lets you automate the data export to fit your needs.10 Click the Apply button to save all changes and add this configuration to the configuration list.

Run a Data ExportThis section walks you through the steps of running and verifying a data export.

Note: The first time the Data Export runs, it will perform a full data export. If the Only Export Changes checkbox is selected, it will perform a delta export (only changes are updated). If you want to perform a full export at any time, clear the Only Export Changes checkbox, apply the changes and run the data export.

You can automate the data export by creating different configurations on the Configure Data Exports page to fit your needs. Each configuration can be run on a schedule.

See Also� �Configure the Data Export� on page 19� �Configure the Data Import� on page 21

To Export Data from Notification Server1 Open the Altiris Console.

a Click Start > Programs > Altiris > Altiris Console.2 From the Configuration tab, in the treeview pane, navigate to Configuration > Solutions Settings >

Connectors > HP OpenView Service Desk > Configure Data Exports.3 In the content pane, select a configuration that is created.4 In the toolbar, click the Run the Selected Configuration icon.Note: You can click the Test the Selected Configuration icon to make sure the data export works without performing a full data export. This tests all of the queries of which the data export is composed to ensure that they run appropriately; however, no export files are produced. There should be up to 10 data export XML files in the directory you specified. You can view one or more of these files to make sure that the data export worked correctly.

Note: Even if you did not select any data classes, resource records will still be exported containing very minimal information, including the resource name. This information, however, can be quite useful. Once it is imported into Service Desk, you will be able to double-click on the resource name, open Resource Manager, and view all of the data on that resource that is in the Notification Database. If you have Carbon Copy installed, you can then access that resource directly from Resource Manager.

To verify the data exportVerify the data export by checking the Import folder. There should be one or more XML files in this folder. They are named �Altiris� followed by the date and time.

The Data Export XML FileInventory data is exported in groups of whole classes based on the category or sub-category selected in the Data Classes to Export section.

Here is an example of the formatting of a data export XML file:

<nsDataExport> <columns> column data... </columns> <exportExecution> <rows> <row> row data... </row> <row n>


row data... </row n> </rows> </exportExecution></nsDataExport>
The exporting process assures the following:

� During a full data export, all data classes on the host computer will show up in a data export XML file.

� During a delta data export, only classes that have changed will show up in a data export XML file.

ErrorsErrors that occur during the Data Export are entered in the Notification Server error logs. For more information on these log files, see �Error Logging� in Altiris Notification Server Help.

Configure the Data ImportTo configure the data import, you need to change the Configuration.xml file. This file contains the default configuration for importing data. This section discusses the Configuration.xml file and how to configure it to run a data import.

The Configuration.xml file contains four main element sections: EXECUTION, LOGGING, CONNECTION, and RULES.

To perform a basic data import, you can leave the settings in the Configuration.xml file unchanged with one exception. In the CONNECTION section, you will most likely need to change the defaults to reflect the hostname, username, and password for logging onto your Service Desk application server.

If you want to make changes to the Configuration.xml file, see the sections below for detailed information.

Note: See the Configuration.dtd file for a better understanding of the structure of the Configuration.xml file.

See Also� �Run a Data Import� on page 34

EXECUTION ElementThe EXECUTION element lets you configure import paths and whether or not to continue if an error is found. There can be zero or one EXECUTION elements in the Configuration.xml file. The attributes listed in the following table are associated with the EXECUTION element. They are all optional, but if not listed in the Configuration.xml file, their default is used.

Attribute DescriptionimportFolderPath The path to the shared Import folder where the

XML files get exported to. This is also the path that the Connector Agent uses to place data in Service Desk. The default is \Import.

importArchiveFolderPath The path where the XML files are moved after they are imported. The default is \Archive.

importErrorFolderPath The path where XML files are moved if application was unable to parse everything in the file. If there are any errors during the parsing of the XML file, it is placed in this folder instead of the Archive folder. The default is \Error.



How the data import uses thresholdsThe data import is divided into three processes: load, configuration, and save.

The load process loads all of the data from the XML files into memory.

The configuration process checks the Service Desk database and configures in memory the data that was loaded by the load process.

The save process saves the data into the Service Desk database that is configured in memory if it is different than what is in the Service Desk database.

As the data import goes through the three processes, if the data import is able to do it all without descending below either the percentageFreeMemoryThresholdForConfigure or the percentageFreeMemoryThresholdForSave thresholds, then these thresholds are not applicable. In this case, the data import will run the load process, then the configuration process, and then the save process.

If, while the load process is loading data, the amount of free memory falls below the percentageFreeMemoryThresholdForConfigure threshold, then the load process temporarily stops, and the configuration process starts and processes that data.

If, while the configuration process is configuring data, the amount of free memory falls below the percentageFreeMemoryThresholdForSave threshold, then the configuration process temporarily stops, and the data is processed by the save process.

After the data moves through the three processes, the load process loads more data and the processing continues according to the percentageFreeMemoryThresholdForConfigure and percentageFreeMemoryThresholdForSave thresholds.

The data import uses these two thresholds to decide when it should start the next step of the import so that it does not run out of memory.

We recommend that you not change these two thresholds from their original values in the Configuration.xml file (20 for percentageFreeMemoryThresholdForConfigure and 10 for percentageFreeMemoryThresholdForSave) unless you receive an Out of Memory error while

continueOnError If true, the data import tries to continue past errors (all errors are logged to the Log file). If false, the import stops when errors occur. The default is True.Note: These errors are errors related to importing the data into Service Desk.

percentageFreeMemoryThresholdForConfigure This sets the minimal percentage of memory you want to use for the configuration process. This is based on the memory that was available when the data import starts. This memory is the memory allocated to the Java Runtime environment when the data import runs. This can be any number between 0 and 100. The default is 0.For more information, see �How the data import uses thresholds� on page 22

percentageFreeMemoryThresholdForSave This sets the minimal percentage of memory you want to use for the save process. This is based on the memory that was available when the data import starts. This memory is the memory allocated to the Java Runtime environment when the data import runs. This can be any number between 0 and 100. The default is 0.For more information, see �How the data import uses thresholds� on page 22

Attribute Description


performing a data import. If this happens, you can try adjusting these thresholds slightly higher; however setting them too high can decrease import speed substantially. Contact Altiris Support if you have any questions regarding changing these two thresholds.
These two thresholds are configurable to help you improve the efficiency of your data import based on the amount of data you are importing.

The data import process takes much longer than the data export. These two thresholds give you flexibility so that you can decrease the data import time depending on the data you are importing. For example, if you are importing data for Configuration Items already associated with a lot of data in Service Desk, you may need to increase the percentageFreeMemoryThresholdForSave threshold.

Another way you can decrease your data import time is to increase the Java Runtime environment memory if you can do so. For more information, see �Out of Memory Error� on page 39.

LOGGING ElementThe LOGGING element lets you configure logging information for the data import. There can be zero or one LOGGING elements in the Configuration.xml file. The attributes listed in the following table are associated with the LOGGING element. They are both optional, but if not listed in the Configuration.xml file, their default is used.

CONNECTION ElementThe CONNECTION element lets you configure your settings for connecting to Service Desk. There can be zero or one CONNECTION elements in the Configuration.xml file. The attributes listed in the following table are associated with the CONNECTION element. They are all optional, but if not listed in the Configuration.xml file, their default is used.

Note: These settings will most likely need to be changed before you can run a data import.

RULES ElementThe RULES element lets you configure the data import rules. There can be zero or one RULES elements in the Configuration.xml file. The RULES element can contain zero or one of these four elements: RESOURCETYPES, RESOURCES, DATACLASSES, and DATASUBCLASSES. These four elements correspond to the four different kinds of information you import into Service Desk: Resource Types, Resources, Data Classes, and Data Subclasses.

Attribute DescriptionfilePath The location of the Log file. The default (if no filePath is listed) is to

output log messages to the command line only.verbose This lets you increase the amount of logging information that gets

entered in the Log file. The default is false, which means only the minimum is entered in the Log file. We recommend that you only set this to true when you want to troubleshoot. If this is set to true, the Log file size can increase quickly, and import speed can decrease substantially. The default is False.

Attribute Descriptionhostname The name of the Service Desk server. The default is �localhost�.username The user name for logging onto the Service Desk application server.

The default is �system�.password The password for logging onto the Service Desk application server.

The default is �servicedesk�.


Resource Types are asset categories, and examples include �Computer�, �User�, �Monitor� and �Keyboard�. Resources are individual assets, such as individual computers or individual users. Data Classes are properties associated with asset categories, including software and hardware for computers and contact information for users; for example, the Data Class �MS Office Apps� may be associated with the computer asset category. Data Subclasses are unique instances of Data Classes and are properties associated with individual assets; for example, the Data Subclass �MS Word 97� may be associated with an individual computer.
See the Configuration.xml file to get a better understanding of the element and attribute structure described in this section.

RESOURCETYPES ElementThe RESOURCETYPES element lets you configure how and where your Resource Types appear in Service Desk. There can be zero or one RESOURCETYPES elements in the Configuration.xml file. The RESOURCETYPES element can contain zero or more RESOURCETYPE elements. The attributes listed in the following table are associated with the RESOURCETYPES element. They are all optional, but if not listed in the Configuration.xml file, their default is used.



Note: The statuses (attributes that start with the word �status�) listed above are listed in a hierarchy in order of importance with statusWhenCreated being most important and statusWhenUpdated being least important. For example, if the Resource Type is updated, but none of its Users or Resources change, then the status gets set to the statusWhenUpdated status. However, if the Resource Type gets updated and one of its Users change, then the status gets set to the statusWhenChangedUser status.

Under the RESOURCETYPES section, you can create as many RESOURCETYPE elements as you want. This gives you the freedom to customize individual Resource Types when you want them to be different from the configuration in the RESOURCETYPES section.

There are three ways that you can classify where a resource appears in the Service Desk Windows console: lowest priority, middle priority, and highest priority. The lowest priority categorization is the defaultCategory attribute on the RESOURCES element. This is the category a resource will get if it is not categorized in any of the other two higher priority categorizations. The middle priority categorization is on the RESOURCETYPE element that corresponds to the Resource Type that is being categorized. For example, optionally there is a RESOURCETYPE element named �Computer�. If you want, you can add a resourceCategory attribute to the Computer RESOURCETYPE element giving it another category. In this case, all of your resources that are not computers would go in the default category, but then all of your resources of Resource Type �Computer� would go to the new category that you specify in the resourceCategory attribute in the Computer RESOURSETYPE element. The highest priority categorization is given by categorizing an individual resource directly by its name. You do this by creating a RESOURCE element by the

Attribute DescriptioncreateConfigurationItem This controls whether or not you want to create a Configuration

Item for each Resource Type.In Service Desk, by default, the data import creates a Configuration Item for each Resource Type. Resources that are imported are then assigned to the appropriate Resource Type as a child Configuration Item. For example, a Computer Configuration Item could have children called Computer1 and Computer2, which are specific computer names.If this is set to False, the data import will create Resource Configuration Items, but those Resources will not be associated with any parent Resource Type.The default is True.

category The category into which all Resource Types are imported into Service Desk. The default is �Altiris|Resource Type�.

searchCodeSuffix The suffix you want to add to the end of the search code for each Configuration Item that is created for a Resource Type. This can be used to better describe the Configuration Item.This improves the probability of uniqueness for the search code.The default is �-RESOURCETYPE�.

statusWhenCreated The name of the status that Resource Types are given when they are created. The default is �Created�.

statusWhenChangedUser The name of the status that Resource Types are given when their associated users change. This affects only the �User� Resource Type. The default is �User Changed�.

statusWhenChangedResource The name of the status that Resource Types are given when their associated Resources change. The default is �Resource Changed�.

statusWhenUpdated The name of the status that Resource Types are given when they are updated. The default is �Updated�.


name of that individual resource and give it a category attribute. So, if you have an individual computer named Computer1, you can assign that computer its own category. This is the highest priority.
If an individual resource, such as a specific computer, has its own category, this takes precedence and it is placed into the assigned category.

If a resource type, such as Computer, has its own category, then all resources of that resource type that have not been assigned an individual resource category are assigned to that category.

All resources that do not have categories assigned to them through a highest or middle priority category are assigned the category given to all resources.

Note: The Search Code Suffix attributes have the same priority classifications as discussed above for categories. The highest priority is the searchCodeSuffix attribute in the RESOURCE element. The middle priority is the resourceSearchCodeSuffix attribute in the RESOURCETYPE element. The lowest priority is the defaultSearchCodeSuffix attribute in the RESOURCES element.

Note: The Status attributes (any attribute that has the name �status� in it) have the same priority classifications as discussed above for categories and Search Code Suffix. The highest priority are the Status attributes in the RESOURCE element. The middle priority are the Status attributes in the RESOURCETYPE element. The lowest priority are the Status attributes in the RESOURCES element.

RESOURCETYPE ElementThe RESOURCETYPE element lets you configure how and where a specific Resource Type appears in Service Desk. There can be zero or more RESOURCETYPE elements under the RESOURCETYPES element in the Configuration.xml file. The attributes listed in the following table are associated with the RESOURCETYPE element. One is required. The others are optional.



Note: The statuses (attributes that start with �resourceStatus�) listed above are listed in a hierarchy in order of importance with resourceStatusWhenCreated being most important and resourceStatusWhenUpdated being least important.

RESOURCES ElementThe RESOURCES element lets you configure how and where your Resources appear in Service Desk. There can be zero or one RESOURCES elements in the Configuration.xml file. The RESOURCES element can contain zero or more RESOURCE elements. The attributes listed in the following table are associated with the RESOURCES element. They are all optional, but if not listed in the Configuration.xml file, their default is used.

Attribute Descriptionname The name of the Resource Type in the Notification

Database. This attribute is required.resourceCategory The category into which all Resources of this

Resource Type is imported into Service Desk.resourceSearchCodeSuffix The suffix you want to add to the end of the search

code for all Configuration Items that are created for Resources of this Resource Type. This can be used to better describe the Configuration Item.This improves the probability of uniqueness for the search code.

resourceStatusWhenCreated The name of the status that Resources of this Resource Type are given when they are created.

resourceStatusWhenChangedDataField The name of the status that Resources of this Resource Type are given when their data fields change.

resourceStatusWhenChangedUser The name of the status that Resources of this Resource Type are given when their associated users change.

resourceStatusWhenChangedDataSubclass The name of the status that Resources of this Resource Type are given when their associated Data Subclasses change.

resourceStatusWhenChangedResourceType The name of the status that Resources of this Resource Type are given when their associated Resource Types change.

resourceStatusWhenUpdated The name of the status that Resources of this Resource Type are given when they are updated.



Note: The statuses (attributes that start with the �defaultStatus�) listed above are listed in a hierarchy in order of importance, with defaultStatusWhenCreated being most important and defaultStatusWhenUpdated being least important. For example, if the Resource is updated, but none of its Resource Types, Data Subclasses, or Data Fields change, then the status gets set to the defaultStatusWhenUpdated status. However, if the Resource gets updated and one of its Data Subclasses change, then the status gets set to the defaultStatusWhenChangedDataField status.

Under the RESOURCES section, you can create as many RESOURCE elements as you want. This gives you the freedom to customize individual Resources when you want them to be different from the configuration in the RESOURCES section.

Attribute DescriptiondefaultCategory The category into which all Resources are imported

into Service Desk. The category can be overridden by using RESOURCE elements. The default is �Altiris|Resource�.

defaultSearchCodeSuffix The suffix you want to add to the end of the search code for the Configuration Item that is created for this Resource. This can be used to better describe the Configuration Item.This improves the probability of uniqueness for the search code.This is the default suffix that all types get unless they are overwritten by the resourceSearchCodeSuffix attribute in the RESOURCETYPE element or the searchCodeSuffix attribute of the RESOURCE element, in that order. For more information on prioritization, see the discussion on category prioritization in �RESOURCETYPES Element� on page 24.The default is �-RESOURCE�.

defaultStatusWhenCreated The name of the status that Resources are given when they are created. The default is �Created�.Note: The Status attributes in the RESOURCES element are the default Statuses that all types get unless they are overwritten by the comparable attribute in the RESOURCETYPE element or the comparable attribute of the RESOURCE element, in that order. For more information on prioritization, see the discussion on category prioritization in �RESOURCETYPES Element� on page 24.

defaultStatusWhenChangedDataField The name of the status that Resources are given when any of the Resource's data fields change. The default is �Data Field Changed�.

defaultStatusWhenChangedUser The name of the status that Resources are given when their associated users change. This affects only a Resource of a �User� Resource Type. The default is �User Changed�.

defaultStatusWhenChangedDataSubclass The name of the status that Resources are given when any of their Data Subclasses are changed during the import. The default is �Data Subclass Changed�.

defaultStatusWhenChangedResourceType The name of the status that Resources are given when they change Resource Type. The default is �Resource Type changed�.

defaultStatusWhenUpdated The name of the status that Resources are given when they are updated. The default is �Updated�.


RESOURCE ElementThe RESOURCE element lets you configure how and where a specific Resource appears in Service Desk. There can be zero or more RESOURCE elements under the RESOURCES element in the Configuration.xml file. The attributes listed in the following table are associated with the RESOURCE element. One is required. The others are optional.
Note: The statuses (attributes that start with the word �status�) listed above are listed in a hierarchy in order of importance with statusWhenCreated being most important and statusWhenUpdated being least important.

DATACLASSES ElementThe DATACLASSES element lets you configure how and where your Data Classes appear in Service Desk. There can be zero or one DATACLASSES elements in the Configuration.xml file. The DATACLASSES element can contain zero or more DATACLASS elements. The attributes listed in the following table are associated with the DATACLASSES element. They are all optional, but if not listed in the Configuration.xml file, their default is used.

Attribute Descriptionname The name of the Resource in the Notification Database. This

attribute is required.category The category into which this Resource is imported into

Service Desk.searchCodeSuffix The suffix you want to add to the end of the search code for all

Configuration Items that are created for this Resource. This can be used to better describe the Configuration Item.This improves the probability of uniqueness for the search code.

statusWhenCreated The name of the status that this Resource is given when it is created.

statusWhenChangedDataField The name of the status that this Resource is given when any of its data fields change.

statusWhenChangedUser The name of the status that this Resource is given when its associated users change.

statusWhenChangedDataSubclass The name of the status that this Resource is given when its associated Data Subclasses change.

statusWhenChangedResourceType The name of the status that this Resource is given when it changes to a different Resource Type.

statusWhenUpdated The name of the status that this Resource is given when it is updated.

Attribute Descriptioncategory The category into which all Data Classes are imported into

Service Desk. The category can be overridden by using DATACLASS elements. The default is �Altiris|Resource�.

searchCodeSuffix The suffix you want to add to the end of the search code for the Configuration Item that is created for this Data Class. This can be used to better describe the Configuration Item.This improves the probability of uniqueness for the search code.The default is �-DATACLASS�.

statusWhenCreated The name of the status that Data Classes are given when they are created. The default is �Created�.



Note: The statuses (attributes that start with the word �status�) listed above are listed in a hierarchy in order of importance with statusWhenCreated being most important and statusWhenUpdated being least important.

DATACLASS ElementThe DATACLASS element lets you configure how and where a specific Resource appears in Service Desk. There can be zero or more DATACLASS elements under the DATACLASSES element in the Configuration.xml file. The DATACLASS element can contain zero or more DATAFIELD elements. The attributes listed in the following table are associated with the DATACLASS element. One is required. The others are optional.

statusWhenChangedDataSubclass The name of the status that Data Classes are given when any of their Data Subclasses are changed during the import. The default is �Data Subclass Changed�.

statusWhenUpdated The name of the status that Data Classes are given when they are updated. The default is �Updated�.

Attribute Descriptionname The name of the Data Class in the Notification

Database. This attribute is required.createConfigurationItem This controls whether or not you want to create a

Configuration Item for each Data Class and its children and associate the appropriate Data Subclasses with it.In Service Desk, by default, the data import creates a Configuration Item for each Data Class. Data Subclasses that are imported are then assigned to the appropriate Data Class as a child Configuration Item.If this is set to False, the data import will not create the Data Class Configuration Item or any of its child Data Subclass Configuration Items. The default is True.For an example of why you would use this, see �DATACLASS createConfigurationItem Example� on page 31.

dataSubclassCategory The category into which all Data Subclasses of this Data Class are imported into Service Desk.

dataSubclassSearchCodeSuffix The suffix you want to add to the end of the search code for all Configuration Items that are created for Data Subclasses of this Data Class. This can be used to better describe the Configuration Item.

dataSubclassStatusWhenCreated The name of the status that Data Subclasses of this Data Class are given when they are created.

dataSubclassStatusWhenChangedUser The name of the status that Data Subclasses of this Data Class are given when their associated users change.

dataSubclassStatusWhenChangedResource The name of the status that Data Subclasses of this Data Class are given when their associated Resource is changed.

dataSubclassStatusWhenChangedDataClass The name of the status that Data Subclasses of this Data Class are given when their associated Data Classes change.

dataSubclassStatusWhenUpdated The name of the status that Data Subclasses of this Data Class are given when they are updated.



Note: The statuses (attributes that start with �dataSubclassStatus�) listed above are listed in a hierarchy in order of importance with dataSubclassStatusWhenCreated being most important and dataSubclassStatusWhenUpdated being least important.
DATACLASS createConfigurationItem Example

An example for using createConfigurationItem is in the Configuration.xml file in the DATACLASSES section.

<DATACLASS name=�AeX AC TCPIP� createConfigurationItem=�false�> <DATAFIELD name=�IP Address� resourceField=�IPAddress� resourceFieldAccumulate=�false� /></DATACLASS>

In this example, createConfigurationItem is false. This means that there will not be a Data Class called AeX AC TCPIP created. Also, there will not be a child Data Subclass created for any of the computers that have an IP address. However, since there is a Data Field IP Address mapping, the IP Address will be placed directly into the Resource Configuration Item.

So, instead of having a relationship between a computer and a Data Subclass for an IP Address, the IP Address is placed directly into the Resource Configuration Item in Service Desk.

DATAFIELD Element

The DATAFIELD element lets you associate fields with a Data Class that appears in Service Desk. There can be zero or more DATAFIELD elements under the DATACLASS element in the Configuration.xml file. The attributes listed in the following table are associated with the DATAFIELD element. Two are required. The other three are optional.

Attribute Descriptionname The name of the Data Field in the Notification Database. This

attribute is required.resourceField The Resource Field name which is mapped to the name of the

field in the Service Desk database. This should be one of the fields found in the Resource Field Name column of the table in �OVSD Configuration Item (CI) Custom Fields� on page 56.

resourceFieldAccumulate If this is set to true, all of the instances of a Data Class found in a Resource are accumulated and placed into the ResourceField in the Configuration Item. If these instances are numbers, they are mathematically added together and the total is placed in the field. If these instances are text, they are comma-separated and placed in the field.If this is set to false, the last instance is the one that gets mapped into the Configuration Item in Service Desk.To see an example for using this, see �DATAFIELD resourceFieldAccumulate Example� on page 32.



Every Data Class in Notification Server has a number of fields associated with it. You can direct any one of those fields into a specific field on any Configuration Item. When you use a Data Field, you are setting fields on a Configuration Item, not relating Configuration Items together. For more information, see �Appendix A� on page 56.

DATAFIELD resourceFieldAccumulate Example

An example for using resourceFieldAccumulate is in the Configuration.xml file in the DATACLASSES section.

<DATACLASS name=�AeX AC Roles� createConfigurationItem=�false�> <DATAFIELD name=�Role� resourceField=�Name2�

dataSubclassSearchCodeExclude The field designated by the name attribute will be excluded when the data import creates the Data Subclass name in Service Desk.If set to true, the data field is excluded from the Data Subclass name. If false, the data field name is included in the search code.The search codes for Data Subclass names that you see in Service Desk are generated based on the fields in the Data Class for that particular Resource. This attribute lets you exclude fields when creating the search code for Data Subclass names. Each use of this attribute will exclude one field designated by the name attribute.A unique search code is generated for each unique instance of a Data Class. If this attribute is not used, all columns in the Data Class are used to generate the search code for the Data Subclass name.To see an example for using this, see �DATAFIELD dataSubclassSearchCodeExclude Example� on page 33You have two ways of controlling the search code for Data Subclass names: use this attribute to exclude fields from the generated name of a Data Subclass and place a suffix on the generated name of a Data Subclass.

isUserName This prompts the data import to either attempt to associate the particular resource that is currently being imported with a person in Service Desk or create a new person in Service Desk and associate that new person as a user of that Configuration Item.This gives you the ability to associate any Resource with a user of that Resource. This must be used in conjunction with the isUserDomain attribute.Use this when there is a user name and domain in two separate fields that should be associated together.When the data import sees that a particular record has both a user name and a domain, it attempts to associate the particular resource that is currently being imported with a person in Service Desk. It will then relates the person with the Configuration Item as a user of that Configuration Item. If that person does not exist in Service Desk, the data import creates a person and associates that new person as a user of that Configuration Item.See the Configuration.xml for examples on using this attribute.

isUserDomain This prompts the data import to either attempt to associate the particular resource that is currently being imported with a person in Service Desk or create a new person in Service Desk and associate that new person as a user of that Configuration Item.This gives you the ability to associate any Resource with a user of that Resource. This must be used in conjunction with the isUserName attribute.



resourceFieldAccumulate=�true� /></DATACLASS>
In this example resourceFieldAccumulate is true. This means that all instances of the AeX AC Roles Data Class will be combined and mapped into the Name2 resourceField in the Configuration Item in Service Desk. If the AEX AC Roles Data Class has instances called �Altiris Agent� and �Notification Server Client�, then the �Altiris Agent, Notification Server Client� will be placed in the Name2 field in the Configuration Item.

If resourceFieldAccumulate were set to false in this example, then �Notification Server Client� would be placed in the Name2 field in the Configuration Item.

DATAFIELD dataSubclassSearchCodeExclude Example

An example for using dataSubclassSearchCodeExclude is in the Configuration.xml file in the DATACLASSES section.

<DATACLASS name=�AeX AC NT Services� createConfigurationItem=�true� dataSubclassCategory=�Altiris|Data Subclass|Software|Operating System|Service� DataSubclassSearchCodeSuffix=�-SERVICE�> <DATAFIELD name=�Path� dataSubclassSearchCodeExclude=�true� /> <DATAFIELD name=�StartupType� dataSubclassSearchCodeExclude=�true� /> <DATAFIELD name=�LogonAs� dataSubclassSearchCodeExclude=�true� /></DATACLASS>

The AeX AC NT Services Data Class shows multiple services running on a computer. Each of these services has multiple fields of data associated with it (Name, Description, Path, StartupType, LogonAs, and Version).

When a Configuration Item for each of these services is created in Service Desk, the values for each of these fields are used to generate a unique search code for the Data Subclass name.

In this example the Path, StartupType, and LogonAs fields are excluded from the search code of the the Data Subclass name.

DATASUBCLASSES ElementThe DATASUBCLASSES element lets you configure how and where your Data Subclasses to appear in Service Desk. There can be zero or one DATASUBCLASSES elements in the Configuration.xml file. The attributes listed in the following table are associated with the DATASUBCLASSES element. They are all optional, but if not listed in the Configuration.xml file, their default is used.

Attribute DescriptiondefaultCategory The category into which all Data Subclasses are imported

into Service Desk. The default is �Altiris|Data Subclass�.defaultSearchCodeSuffix The suffix you want to add to the end of the search code for

all Configuration Items that are created for all Data Subclasses.The default is �-DATASUBCLASS�.

defaultStatusWhenCreated The name of the status that Data Subclasses are given when they are created. The default is �Created�.

defaultStatusWhenChangedUser The name of the status that Data Subclasses are given when their associated users change. The default is �User Changed�.

defaultStatusWhenChangedResource The name of the status that Data Subclasses are given when their associated Resources change. The default is �Resource Changed�.



Note: The statuses (attributes that start with �defaultStatus�) listed above are listed in a hierarchy in order of importance with defaultStatusWhenCreated being most important and defaultStatusWhenUpdated being least important.

There are two ways to categorize a Data Subclass: its defaultCategory and its category.

The lowest priority for specifying the category, statuses, and Search Code Suffix for Data Subclasses is the DATASUBCLASSES element. The highest priority for getting the category, statuses, and Search Code Suffix for Data Subclasses is the DATACLASS element.

You are not allowed to categorize a Data Subclass by its name as you are with Resources because the names of Data Subclasses are very complex.

The default category for a Data Subclass is set by the defaultCategory attribute under the DATASUBCLASSES element. If you want to categorize that Data Subclass according to whatever Data Class it belongs to, then you will have to make a specific entry for that Data Class (as a Data Class element under the DATACLASSES section) and then any Data Subclasses of that category will go to the specified path in that Data Class element.

Run a Data ImportAfter you have performed a data export and configured the Configuration.xml file, it is easy to run a data import.

In the Program Files\Altiris\ConnectHPOVSDAgentfolder folder, run the ConnectHPOVSDAgent.bat file. This batch file imports the data found in the Import folder into Service Desk.

After the files have been imported, they are placed in the Archive folder.

IMPORTANT: Service Desk needs to be running in order to perform a data import.

Notes� The ConnectHPOVSDAgent.bat file calls the Java runtime environment which launches an

executable Jar file, sets the memory that you want to have allocated to that application, and then calls the Jar executable. The Jar executable is what actually performs the data import.

� By default, the Connector Agent allocates 256 MB of Java runtime memory. This memory is used to store the data before it gets placed in Service Desk. You can change this default higher or lower depending on how much memory you have available. The performance of the data import increases when the Java runtime memory is increased.

� The speed of the data import depends on how many computers you are importing, how many data classes you exported, and whether or not you are performing a delta (update-only) data import. Service Desk uses numerous rules for importing data and may take some time importing data. The data import process takes quite a bit longer than the data export process. The first time you perform a data import, it will take longer than subsequent delta data imports.

� This Connector never deletes information from Service Desk. It only imports data from Notification Server and creates appropriate relationships of that data in Service Desk. As new data is imported, these relationships can be changed or even broken. For example, if a computer is no longer associated with a hard drive, that relationship is broken, but the hard drive is not deleted from Service Desk.

See Also� �Verify the Data Import� on page 35

defaultStatusWhenChangedDataClass The name of the status that Data Subclasses are given when their associated Data Classes change. The default is �Data Class Changed�.

defaultStatusWhenUpdated The name of the status that Data Subclasses are given when they are updated. The default is �Updated�.



To automate the process of importing data into Service DeskYou can automate the data import by setting up the Windows Task Scheduler on the Service Desk server. The following steps walk you through this process.
1 On the Service Desk server, open the Control Panel.2 Select Schedule Tasks.3 Double-click Add Scheduled Task to run the Scheduled Task Wizard.4 Select the ConnectHPOVSDAgent.bat file as the program to run (found in Program

Files\Altiris\ConnectHPOVSDAgent).5 Select the schedule that meets your needs.

Verify the Data ImportWhen you import inventory data into Service Desk, you will be able to double-click on the resource name, open Resource Manager, and view all of the data on that resource that is in the Notification Database. If you have Carbon Copy installed, you can then access that resource directly from Resource Manager.

See Also� �Integrate the UI� on page 35

To view the Initial Import Results1 Open Service Desk.2 In the left pane, click CMDB.3 Select Configuration Items.4 In the tree view, under CI Category, there should be an Altiris category.

Class CIs appear in the Altiris category. Host names appear in the computer sub-category. Inventory CIs appear in the Hardware, Operating System, and Software sub-categories.

Integrate the UIThis connector provides templates for automatically setting up contextual menu integration. These templates can be found in the ACES folder that is found in the ConnectHPOVSDAgent folder.

There are two Aces templates and one shortcut template in this folder.

The shortcut template sets up some links to the Altiris Console, the Altiris Reports, and the Connector Configuration window. These appear in the shortcut bar under Altiris in Service Desk.

The Actions Aces template is for the contextual menu integration. The Views Aces template lets you have customized views of your Configuration Items (for example, this lets you display only those Configuration Items that have changed, or have been updated, or that have had a field change). To use these templates, you need to either edit the Notification Server name in the URL found in the template and import it, or import the template and change the Notification Server name in Service Desk.

To import the template into Service Desk, navigate to Tools > System > File > Aces > Aces Import Wizard.


Manually set up contextual menu integration between OVSD and Resource ManagerThe following describes how to manually set up menu integration between OVSD and Resource Manager. This process can be used if you don�t use the templates that are provided in the ACES folder.
1 Open the HP OpenView Service Desk console.The Tools drop-down menu appears at the top of the console.

2 Click on the Tools drop-down menu.System appears in the drop-down menu.

3 Select System.The Business Logic node appears in the left pane of the Administrator Console window.

4 Expand the Business Logic node.The Actions node appears as a child node of the Business Logic node.

5 Expand the Actions node.The Smart Actions node appears as a child node of the Actions node.

6 Expand the Smart Actions node.The Configuration Item node appears as a child node of the Smart Actions node.

7 Select the Configuration Item node.The Smart action pane appears in right-pane of the Administrator Console window.

8 Right-click in the Smart action pane.New Smart Action appears in the popup menu.

9 Select New Smart Action.The New - Smart Action dialog appears.

10 Type �Altiris Resource Manager� in the Text field.11 Click the Application button.12 Select the Internet Explorer application.13 Enter the URL.

The URL should be http:\\NSServerName\Altiris\ContextFactory\Selectionview.aspx?cfresourceidentifier=

14 Click the Field button.Source ID appears in the popup menu.

15 Select Source ID.[Source ID] appears after URL in the Parameters field.

16 Click the OK button.�Altiris Resource Manager� appears in the Smart action pane of the Administrator Console window.

Using Contextual Menu Integration between OVSD and Resource Manager1 Open the HP OpenView Service Desk console.

CMDB appears in the left pane of the console.2 Click on CMDB.

The Configuration Item icon appears under CMDB.3 Click on the Configuration Item icon.

The Category tree sub-pane appears in the left sub-pane of the Configuration Item pane in the right pane of the console.


Using the Connector for HP OpenView Service Desk User Interface
4 Navigate in the Category tree to the node containing the hostnames.
The hostnames appear in the right sub-pane of the Configuration Item pane.5 Double-click on a hostname.

The Actions drop-down menu appears at the top of the ...- Configuration Item window.6 Click on the Actions drop-down menu.

Altiris Resource Manager appears in the drop-down menu.7 Select Altiris Resource Manager.

Altiris Resource Manager appears containing contextual data (if the hostname was previously imported from Notification Server).

Using with SolarisThis release of the Connector for HP OpenView Service Desk supports Service Desk servers running on Unix Solaris.

Here are some notes of interest if you are running Service Desk on Solaris.

� Solaris does not natively support Microsoft Windows shares. Yet, we recommend that you create a shared directory on your Service Desk server into which the data export places the XML files. To share the Import directory, you need to install a third-party component, such as Samba, to create a shared directory that Windows can see via UNC paths. Then, you can point the data export to that shared directory. Note: There are other ways to get the XML files to your Solaris Service Desk server besides using a shared directory. Do what works best for you if you do not want to install a third-party component.

� If you want the data import to run on a schedule, you must set up a UNIX cron job to launch the data import application from time to time.

User InterfaceThis section describes the elements that are added to the Altiris Console when this Connector gets installed.

Quick Links� �Configure Data Exports� on page 37� �Download Agent Install� on page 38� �Reports� on page 38

Configure Data Exports This page lets you set up one or more data export configurations. After a configuration has been set up, you can select it from the Select a Configuration drop-down list and run it.

For best performance, we recommend that you create multiple data exports that run on different schedules. For example, you can create a full data export that exports all of the needed data periodically according to your needs (such as weekly or monthly). Then, create a delta data export that updates your data more often and in less time (such as daily). The connector gives you the flexibility you need to export the data you want, how you want, and where you want into Service Desk.


Using the Connector for HP OpenView Service Desk User Interface
To access this page1 In the Altiris Console, select the Configuration tab. 2 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView
Service Desk > Configure Data Exports.

Download Agent Install This page installs the Connector Agent executable to the Service Desk server. When you click on Download Agent Install, a File Download window should appear. Click Open to install the Connector Agent to the Service Desk server.

Note: If the File Download window does not appear automatically, click the click here link in the content pane.

ReportsThe Data Export component provides several reports that let you view import and export data.

To view these reports1 Open the Altiris Console.2 Click the Reports tab view.3 In the treeview pane, navigate to Reports > Connector > Import/Export Results.

Page Items

Item DescriptionSelect a Configuration

A drop-down list containing the names of configurations you have created. Select the configuration you want and click an icon in the toolbar to test, run, or delete that configuration.

Name The configuration name. This is the name that will appear in the Select a Configuration drop-down list.

Description The configuration description. Enter any description you want.Folder Path for Export

The full path of a local or network folder where the exported XML files will be placed. This can be any UNC path.

Collection To Export

The collection to export. Data from the collection you select will be exported as XML files.

Only Export Changes

Select this if you want to perform delta exports after the first export. The first export will always export the full data. If this is not selected, each export will be a full export.

Data Classes To Export

The data classes to export. Select one or more data classes from this list to export. We recommend that you start with Basic Inventory. After you see what gets exported with Basic Inventory, then you can add more data classes as desired.Note: You can select all data classes in a folder by selecting it or expand the folder to select individual data classes inside the folder.

Enable Schedule Configure when and how often the data export described by this configuration will run.

Apply Click to save your changes and add this configuration to the configuration list.Cancel Click to cancel your changes.


Using the Connector for HP OpenView Service Desk Troubleshooting
Troubleshooting
Quick Links� �Database Access Error� on page 39� �Out of Memory Error� on page 39� �Database Scalability Limitation� on page 39

Database Access ErrorDuring import, you may receive the following error (this error is logged both in the Parse.log file and on the console):

java.lang.RuntimeException: You are not allowed to view this kernel code hierarchical or this may have been deleted by another user.

This is a database access error.

The solution is to adjust your database security settings to give administrative rights to the identity that is running the import process.

Out of Memory ErrorDuring import, you may receive the following error (this error is logged both in the Parse.log file and on the console):

Exception in thread �main� java.lang.OutOfMemoryError <<no stack trace available>>

This error happens when the computer runs out of RAM while trying to import data.

The following are solutions to solve this error, in order of preference.

1 Increase the numbers in these parameters which are found in the ConnectHPOVSDAgent.bat file: -xms256m and -xmx256m. The 256 in these parameters represents the amount of memory (in MB) allocated to the java runtime environment. Increase these to 512 or higher (for example, -xms512m and -xmx512m).

2 Increase the amount of RAM on your computer.

Database Scalability LimitationThe 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.


Using the Connector for HP OpenView Operations

This connector lets you configure Notification Server to forward Automated Actions and menu items to an HP OpenView Operations server. The SNMP Management component of Connector Solution lets you define the HP OpenView Operations server that will receive Automated Actions and choose which Automated Actions will be forwarded (for more information, see the Altiris Connector Solution Product Guide). Examples of the kinds of Automated Actions that can be forwarded include: change in computer name or low disk space (provided by Inventory Solution), memory module alerts, PC card thermal alerts, and DHCP services error and warnings and DNS error and warnings (provided by Server Monitor Solution).

On the HP OpenView Operations server, MIBs imported into Operations translate all the Automated Actions to standard SNMP alerts. These Automated Actions can be individually configured as to whether they are critical, major, minor, normal, or a warning.

Altiris-specific menu items can also be added to the HP OpenView Console that lets you launch directly into any installed Altiris console.

Quick Links� �Setting Up and Using the Connector for HP OpenView Operations� on page 40� �User Interface� on page 44

Setting Up and Using the Connector for HP OpenView Operations

This section walks you through the steps you need to set up integration between Notification Server and your Operations servers.

To successfully set up and use this Connector, follow these Quick Steps in order.

Quick Steps� �Add your Operations Servers to the SNMP Destinations Collection� on page 40� �Create a Connector Agent Installer for each Operations Server� on page 41� �Install the Connector Agent Installer on your Operations Servers� on page 41� �Access Altiris Items on the Operations Console� on page 42

Add your Operations Servers to the SNMP Destinations CollectionIn order to send Automated Actions to your Operations servers, you need to add your Operations computers to the HP OpenView Operations collection in the SNMP Destination Collections folder. The SNMP Destination Collections folder gets installed by Connector Solution as part of the Event Integration component.

When the Connector for HP OpenView gets installed, an HP OpenView Operations collection gets created in the SNMP Destination Collections folder. Because this collection is empty, you need to add your Operations computers to this collection before you can send Automated Actions. Automated Actions become SNMP alerts in Operations.


Using the Connector for HP OpenView Operations Setting Up and Using the Connector for HP OpenView Operations
Note: The SNMP Destination Collections folder is found in the Configuration tab view by navigating in the treeview pane to Configuration > Server Settings > Notification Server Settings > SNMP Management.
Add your computers to this collection as explained in the Altiris Connector Solution Product Guide. After you have added computers to this collection, you can enable and edit the Automated Actions for the collection. Follow the instructions found in �Enabling and Editing Automated Actions for SNMP Destination Collections� in the Altiris Connector Solution Product Guide.

Note: All discovered Computers can be added to an SNMP destination collection. See the Notification Server Help for information on discovering computers.

Note: This connector creates the necessary MIBs for you (see �Configuration� on page 45), so you do not need to create the MIBs as explained in the Altiris Connector Solution Product Guide.

Quick Link� �Create a Connector Agent Installer for each Operations Server� on page 41

Create a Connector Agent Installer for each Operations ServerThe Configuration page lets you create a Connector Agent Installer for each of your Operations servers. After this Installer is created, you can install it on the appropriate Operations server. This Installer installs the necessary files can components to configure your Notification Server with your Operations servers.

To create a Connector Agent Installer, do the following for each HP OpenView computer you have1 Open the Altiris Console and click on the Configuration tab.2 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView

Operations > Configuration.3 In the content pane, select an Operations server from the Select an OpenView Operations Computer

drop-down list.4 Select the menu items you want to add to the selected computer.5 Click Apply. When you click Apply, a Connector Agent Installer, a Connector Agent package, and

a Connector Agent collection are all created.

Quick Links� �Configuration� on page 45� �Install the Connector Agent Installer on your Operations Servers� on page 41

Install the Connector Agent Installer on your Operations ServersDownload and install the Connector Agent Installer to the appropriate Operations server by either clicking the Download the Configuration Package icon on the OpenView Configuration page or delivering it as a Software Delivery Package if you have Software Delivery Solution.

Each Connector Agent Installer is unique to the Operations server for which it was created.

Note: You can download the Connector Agent Installer directly by accessing the Altiris Console from the Operations server and clicking the Download the Configuration Package icon.


Access Altiris Items on the Operations ConsoleThis section tells you how to access Altiris items on the Operations console. Common connector tasks are also provided.
MIBs can be accessed from Operations by opening up Policy Management > Policy Groups > Altiris.

Quick Links� �Making a Trap a Critical Error in HP OpenView Operations� on page 42� �Accessing Resource Manager in HP OpenView Operations� on page 42� �How the SNMP Management Agent Interacts with the HP OpenView Operations Server� on

page 43� �How to set up and use Contextual Menu Integration Between HP OpenView Operations and

Resource Manager� on page 43

Making a Trap a Critical Error in HP OpenView OperationsAll Altiris traps are set to the severity they are in Notification Server (or the closest match). To change the severity of a trap to another severity (such as critical), you must first modify the Altiris event associated with that trap.

To change the severity of a trap1 In the HP OpenView Operations main window, in the HP OpenView tree, navigate to Operations

Manager > Policy management > Policy groups > Altiris.2 In the right pane, double-click on an Altiris MIB.3 Double-click on the event (trap) that you want to change the severity for.4 Click the Actions tab.5 Click the Message... button.

Note: You can also click the Automatic commands button and enter a command to run as an action for the event.

6 In the Outgoing Message window, click the Message attributes tab.7 Click the Severity drop-down menu and select Critical.8 Click OK.9 You may now close the Altiris MIB window or continue to modify rules as described in steps 3

through 8.

Accessing Resource Manager in HP OpenView OperationsThe Connector for HP OpenView lets you use Resource Manager while using HP OpenView Operations. Resource Manager lets you see everything about an Altiris enabled computer.

Note: You will not be able to view Resource Manager on your HP OpenView Operations server unless you have installed the Connector Agent Installer.

You can access Resource Manager from HP OpenView Operations in one of two ways:

� Select a pertinent node (Altiris enabled computer) and then select Resource Manager from the drop-down menu.

� Open the Resource Manager tool, then select the pertinent node.


To access Resource Manager via the node (Altiris-enabled computer)Do one of the following:
1 Select a node object in the right pane.a In the HP OpenView Operations main window, in the HP OpenView tree, navigate to

Operations Manager > Nodes.b Right-click on Nodes and select View > Map. You need to be in the Map view to launch

Resource Manager.c In the right pane, select a node.d Right-click on Nodes and select Launch Tool.e Select Altiris Resource Manager. f Click Launch.

2 Select a node object from the tree.a In the HP OpenView Operations main window, in the HP OpenView tree, navigate to

Operations Manager > Nodes.b Under Nodes, right-click on the desired Altiris enabled computer, then select All Tasks >

Launch Tool.c Select Altiris Resource Manager. d Click Launch.

To access Resource Manager via the tools1 In the HP OpenView Operations main window, in the HP OpenView tree, navigate to Operations

Manager > Tools > Altiris.2 In the right pane, double-click on Altiris Resource Manager.3 Select the desired node, then click Launch.

How the SNMP Management Agent Interacts with the HP OpenView Operations ServerThe SNMP Management agent sends the SNMP trap to the HP OpenView Operations server. The SNMP Manager on the HP OpenView server does the following:

1 Looks in the Altiris MIB.2 Records the trap information in the Message browser.

How to set up and use Contextual Menu Integration Between HP OpenView Operations and Resource ManagerSetting up Contextual Menu Integration between HP OpenView Operations and Resource Manager1 Open the HP OpenView Operations console.

The Tools node of the HP OpenView tree appears in the left pane of the console.2 Right-click on the Tools node.

Configure appears in the popup menu.3 Select Configure and Nodes....

The Nodes root node appears in the right pane of the Configure Managed Nodes dialog.4 Right-click on the Nodes root node.

Properties appears in the popup menu.5 Select Properties.


Using the Connector for HP OpenView Operations User Interface
The Tools tab appears in the Folder Properties dialog.
6 Select the Tools tab.The Add... button appears next to Tools Associated with this node group:.

7 The on the Add... button.The Altiris node appears as a child node of the Tools root node in the Associate Tools with Node Group dialog.

8 Expand Altiris.Altiris Resource Manager appears as a child node of the Altiris node.

9 Select Altiris Resource Manager.The OK button appears at the bottom of the Associate Tools with Node Group dialog.

10 Click the OK button.The OK button appears at the bottom of the Folder Properties dialog.

11 Click the OK button.The OK button appears at the bottom of the Configure Managed Nodes button.

12 Click the OK button.

Using Contextual Menu Integration between HP OpenView Operations and Resource Manager1 Open the HP OpenView Operations console.

The Nodes node of the HP OpenView tree appears in the left pane of the console.2 Expand the Nodes node.

The hostname nodes appear as children nodes of the Nodes node.3 Right-click on a hostname node.

All Tasks appears in the popup menu.4 Select All Tasks and Launch Tool.

The Altiris Resource Manager tool appears in the Select the Tool to Execute dialog.5 Select the Altiris Resource Manager tool.

The Launch... button appears at the bottom of the Select the Tool to Execute dialog.6 Click the Launch... button.

Altiris Resource Manager appears containing contextual data (if the hostname was previously inventoried by Notification Server).


Quick Links� �Agent� on page 44� �Configuration� on page 45

AgentThe Agent folder contains collections, packages, and tasks that are created for each Operations computer that you configure on the HP OpenView Operations Configuration page.

Generally, each collection in the Agent folder contains only one computer.


To access this folder1 In the Altiris Console, select the Configuration tab. 2 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView
Operations > Agent.

ConfigurationThis page lets you build a unique configuration package (Connector Agent Installer) to install on each HP OpenView Operations server you have.

The Connector Agent Installer contains Altiris MIBs and menu items that let you integrate Notification Server with your HP OpenView Operations servers.

To add computers to the Select an OpenView Operations Computer drop-down list, click the Add or Remove a Computer button and add one or more computers to the HP OpenView Operations collection. Click the Apply button to save your changes, then navigate back to the Configuration page. The HP OpenView Operations collection can be viewed by navigating to Configuration > Server Settings > Notification Server Settings > SNMP Management > SNMP Destination Collections.

To configure an HP OpenView computer, select a computer from the Select an OpenView Operations Computer drop-down list. Then, select the menu items you want for that computer from the Select the Menu Items to Display OpenView Operations list.

Each HP OpenView Operations computer has its own configuration. All actions performed on this page apply to the selected HP OpenView Operations computer on the Select an OpenView Operations Computer drop-down list.

Click Add or Remove a Computer to add a computer to the list or remove a computer from the list.

From the Agent package, you can set up a schedule to install the Connector Agent Installer. Then, when you update the configuration and click Apply, the Connector Agent Installer gets installed according to the schedule.


Operations > Configuration.

Page Items

Item DescriptionSelect an OpenView Operations Computer

Displays available HP OpenView Operations servers. Select the computer that you want to configure and send the Connector Agent Installer to.

Add or Remove a Computer

This lets you add a computer to or remove a computer from the Select an OpenView Operations Computer list.

Select the Menu Items to Display in OpenView Operations

Select the menu items that you want to have available on this Operations server.



Configuration ToolbarThe configuration toolbar appears at the top of the contents pane. The clickable icons let you perform actions on the configuration of the selected HP OpenView computer.

The clickable icons on the configuration toolbar are:

� Add or Remove a Computer - Lets you add a computer to or remove a computer from the Select an OpenView Computer list.

� Go to the Software Delivery Package - Takes you to the Software Delivery Package for this Operations server.

� Download the Configuration Package - Opens a download page, which lets you download and install the Connector Agent Installer to the appropriate Operations server.

� Configure SNMP Destination - Takes you to the SNMP Destinations Configuration page. This page lets you enable and edit the Automated Actions for the collection. This information is used for creating the Altiris MIBs that get placed in the Connector Agent Installer.

� Right click menu - Displays the right click menu for the folder.

Apply Click to save your changes. When you click Apply, the following happens:� a Connector Agent Installer is created that contains Altiris MIBs and the

selected menu items� a Connector Agent collection for this Operations server is created and

placed in the Agent Packages Collections folder� a Connector Agent package for this Operations server is created and placed

in the Agent Packages folderCancel Click to cancel your changes.

Page Items

Item Description


Using the Connector for HP OpenView Network Node Manager

This connector lets you configure Notification Server to forward Automated Actions and menu items to an HP OpenView Network Node Manager (NNM) server. The SNMP Management component of Connector Solution lets you define the HP OpenView NNM server that will receive Automated Actions and choose which Automated Actions will be forwarded (for more information, see the Altiris Connector Solution Product Guide). Examples of the kinds of Automated Actions that can be forwarded include: change in computer name or low disk space (provided by Inventory Solution), memory module alerts, PC card thermal alerts, and DHCP services error and warnings and DNS error and warnings (provided by Server Monitor Solution).

On the HP OpenView NNM server, MIBs imported into NNM translate all the Automated Actions to standard SNMP alerts. These Automated Actions can be individually configured as to whether they are critical, major, minor, normal, or a warning.

Altiris also uses an Application Registration File (ARF) to add a context sensitive menu option to the HP OpenView console for Altiris Resource Manager. With a right-click on your mouse, you can launch the Altiris Resource Manager which provides detailed information about the device and a user interface that allows you to remote control the device.

Altiris-specific menu items can also be added to the HP OpenView Console that lets you launch directly into any installed Altiris console.

Quick Links� �Setting Up and Using the Connector for HP OpenView NNM� on page 47� �User Interface� on page 52

Setting Up and Using the Connector for HP OpenView NNMThis section walks you through the steps you need to set up integration between Notification Server and your NNM servers.

To successfully set up and use this Connector, follow these Quick Steps in order.

Quick Steps� �Add your NNM Servers to the SNMP Destinations Collection� on page 47� �Create a Connector Agent Installer for each NNM Server� on page 48� �Install the Connector Agent Installer on your NNM Servers� on page 48� �Access Altiris Items on the NNM Console� on page 49

Add your NNM Servers to the SNMP Destinations CollectionIn order to send Automated Actions to your NNM servers, you need to add your NNM computers to the HP OpenView Network Node Manager collection in the SNMP Destination Collections folder. The SNMP Destination Collections folder gets installed by Connector Solution as part of the Event Integration component.


Using the Connector for HP OpenView Network Node ManagerSetting Up and Using the Connector for HP OpenView
When the Connector for HP OpenView gets installed, an HP OpenView Network Node Manager collection gets created in the SNMP Destination Collections folder. Because this collection is empty, you need to add your NNM computers to this collection before you can send Automated Actions. Automated Actions become SNMP alerts in NNM.
Note: The SNMP Destination Collections folder is found in the Configuration tab view by navigating in the treeview pane to Configuration > Server Settings > Notification Server Settings > SNMP Management.

Add your computers to this collection as explained in the Altiris Connector Solution Product Guide. After you have added computers to this collection, you can enable and edit the Automated Actions for the collection. Follow the instructions found in �Enabling and Editing Automated Actions for SNMP Destination Collections� in the Altiris Connector Solution Product Guide.

Note: All discovered Computers can be added to an SNMP destination collection. See the Notification Server Help for information on discovering computers.

Note: This connector creates the necessary MIBs for you (see �Configuration� on page 52), so you do not need to create the MIBs as explained in the Altiris Connector Solution Product Guide.

Quick Link� �Create a Connector Agent Installer for each NNM Server� on page 48

Create a Connector Agent Installer for each NNM ServerThe Configuration page lets you create a Connector Agent Installer for each of your NNM servers. After this Installer is created, you can install it on the appropriate NNM server. This Installer installs the necessary files can components to configure your Notification Server with your NNM servers.

To create a Connector Agent Installer, do the following for each HP OpenView computer you have1 Open the Altiris Console and click on the Configuration tab.2 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView

Network Node Manager > Configuration.3 In the content pane, select an NNM server from the Select an OpenView Network Node Manager

Computer drop-down list.4 Select the menu items you want to add to the selected computer.5 Click Apply. When you click Apply, a Connector Agent Installer, a Connector Agent package, and

a Connector Agent collection are all created.

Quick Links� �Configuration� on page 52� �Install the Connector Agent Installer on your NNM Servers� on page 48

Install the Connector Agent Installer on your NNM ServersDownload and install the Connector Agent Installer to the appropriate NNM server by either clicking the Download the Configuration Package icon on the OpenView Configuration page or delivering it as a Software Delivery Package if you have Software Delivery Solution.

Each Connector Agent Installer is unique to the NNM server for which it was created.

Note: You can download the Connector Agent Installer directly by accessing the Altiris Console from the NNM server and clicking the Download the Configuration Package icon.


Access Altiris Items on the NNM ConsoleThis section tells you how to access Altiris items on the NNM console. Common connector tasks are also provided.
After the Connector Agent Installer is installed on the NNM computer, Altiris tools can be accessed by clicking Tools > Altiris from the NNM console.

MIBs can be accessed from NNM by opening up Policy Management > Policy Groups > Altiris.

Quick Links� �Altiris Integration with HP OpenView NNM� on page 49� �Making a Trap a Critical Error in HP OpenView NNM� on page 49� �Accessing Resource Manager in HP OpenView NNM� on page 51� �How the NS SNMP Agent Interacts with the HP OpenView NNM Server� on page 52

Altiris Integration with HP OpenView NNMThe following describes the additions to the HP OpenView NNM browser after the install package has been installed to the HP OpenView server.

Altiris ButtonsTwo new Altiris standard buttons appear on the NNM browser.

1 The Altiris button lets you access the Altiris Console.

2 The Altiris Resource Manager button lets you access Resource Manager when a node is selected.

Altiris Alarms BrowserWhen the HP OpenView NNM browser opens, an Alarm Categories window is displayed. There is an Altiris option that, when selected, displays the Altiris Alarms Browser.

Making a Trap a Critical Error in HP OpenView NNMAll Altiris traps are set to warning severity (HP OpenView default). To change the severity of a trap to any other severity, such as critical, you must first modify the Altiris event associated with that trap.


To do so, follow these steps:
1 In the HP OpenView NNM main window, click on the Options drop-down menu and select Event Configuration. The Event Configuration window will open.

2 Select the altiris enterprise in the top pane of the window, and then double-click on the pertinent event in the bottom pane of the window. The Modify Events window will open.

3 Click on the Event Message tab to reveal the Event Message configuration options.


4 Set the Severity drop-down menu option to Critical, and click the OK button. The Modify Events
window will close, and you will return to the Event Configuration window.

5 Click on the File drop-down menu and select Save. The event will now produce a critical error notification when it receives the associated trap from Notification Server.

6 You may now close the Event Configuration window or continue to modify events as described in Step 2 through Step 5.

Accessing Resource Manager in HP OpenView NNMThe Connector for HP OpenView lets you use Resource Manager while using HP OpenView. Resource Manager lets you view all inventory data collected from an Altiris enabled computer. It also lets you launch Carbon Copy, if it has been installed, to remote control to the Altiris enabled computer.

Note: You will not be able to view Resource Manager on your HP OpenView NNM server unless you have installed the Connector Agent Installer.

To access Resource Manager from HP OpenView NNM, you must select a pertinent node (Altiris-enabled computer) and then select Resource Manager from the drop-down menu.

Note: If Resource Manager notifies you that Summary data is not ready for the node you selected, then you must use Notification Server to inventory the node before you can use Resource Manager to navigate its resources. For instructions on how to use Notification Server to inventory a node (using the Altiris Agent), please refer to the Altiris Notification Server Help.

To access Resource Manager from HP OpenView NNM1 In the HP OpenView main window, select the node for which you would like to launch Resource

Manager. Please note that the node must display a host name that has been inventoried by Notification Server.

2 Open Resource Manager by doing one of the following:


Using the Connector for HP OpenView Network Node Manager User Interface
a Click on the Altiris Resource Manager button . Note that this button is only available
when a node is selected.b Click on the Tools drop-down menu and select Altiris > Resource Manager. This will launch

Resource Manager in a Web browser window.c Right-click on the selected node to reveal the contextual pop-up menu and select Altiris

Resource Manager.3 Navigate the resources of the node you selected in Resource Manager. If Resource Manager

notifies you that Summary data is not ready for the node you selected, then you must use Notification Server to inventory the node before you can use Resource Manager to navigate its resources. For instructions on how to use Notification Server to inventory a node (using the Altiris Agent), please refer to the Altiris Notification Server Help.Note: If you are using Altiris HP Client Manager, you can view HP and Compaq hardware specific information in Resource Manager.

How the NS SNMP Agent Interacts with the HP OpenView NNM ServerThe NS SNMP agent sends the SNMP trap to the HP OpenView NNM server. The SNMP manager on the HP OpenView server does the following:

1 Looks in the Altiris MIB.2 Records the trap information in the Alarms browser. You can also look at all Altiris information

using the Altiris Alarms browser.


Quick Links� �Agent� on page 52� �Configuration� on page 52

AgentThe Agent folder contains collections, packages, and tasks that are created for each NNM computer that you configure on the HP OpenView NNM Configuration page.

Generally, each collection in the Agent folder contains only one computer.

To access this folder1 In the Altiris Console, select the Configuration tab. 2 In the treeview pane, navigate to Configuration > Solutions Settings > Connectors > HP OpenView

Network Node Manager > Agent.

ConfigurationThis page lets you build a unique configuration package (Connector Agent Installer) to install on each HP OpenView NNM server you have.

The Connector Agent Installer contains Altiris MIBs and menu items that let you integrate Notification Server with your HP OpenView NNM servers.


To add computers to the Select an OpenView Network Node Manager Computer drop-down list, click the Add or Remove a Computer button and add one or more computers to the HP OpenView Network Node Manager collection. Click the Apply button to save your changes, then navigate back to the Configuration page. The HP OpenView Network Node Manager collection can be viewed by navigating to Configuration > Server Settings > Notification Server Settings > SNMP Management > SNMP Destination Collections.
To configure an HP OpenView computer, select a computer from the Select an OpenView Network Node Manager Computer drop-down list. Then, select the menu items you want for that computer from the Select the Menu Items to Display OpenView Network Node Manager list.

Each HP OpenView NNM computer has its own configuration. All actions performed on this page apply to the selected HP OpenView NNM computer on the Select an OpenView Network Node Manager Computer drop-down list.

Click Add or Remove a Computer to add a computer to the list or remove a computer from the list.

From the Agent package, you can set up a schedule to install the Connector Agent Installer. Then, when you update the configuration and click Apply, the Connector Agent Installer gets installed according to the schedule.


Network Node Manager > Configuration.

Configuration ToolbarThe configuration toolbar appears at the top of the contents pane. The clickable icons let you perform actions on the configuration of the selected HP OpenView computer.

The clickable icons on the configuration toolbar are:

� Add or Remove a Computer - Lets you add a computer to or remove a computer from the Select an OpenView Computer list.

Page Items

Item DescriptionSelect an OpenView Network Node Manager Computer

Displays available HP OpenView NNM servers. Select the computer that you want to configure and send the Connector Agent Installer to.

Add or Remove a Computer

This lets you add a computer to or remove a computer from the Select an OpenView Network Node Manager Computer list.

Select the Menu Items to Display in OpenView Network Node Manager

Select the menu items that you want to have available on this NNM server.

Apply Click to save your changes. When you click Apply, the following happens:� a Connector Agent Installer is created that contains Altiris MIBs and the

selected menu items� a Connector Agent collection for this NNM server is created and placed in

the Agent Packages Collections folder� a Connector Agent package for this NNM server is created and placed in

the Agent Packages folderCancel Click to cancel your changes.


� Go to the Software Delivery Package - Takes you to the Software Delivery Package for
this NNM server.

� Download the Configuration Package - Opens a download page, which lets you download and install the Connector Agent Installer to the appropriate NNM server.

� Configure SNMP Destination - Takes you to the SNMP Destinations Configuration page. This page lets you enable and edit the Automated Actions for the collection. This information is used for creating the Altiris MIBs that get placed in the Connector Agent Installer.

� Right click menu - Displays the right click menu for the folder.



ReferenceThis section provides reference information for the Connector for HP OpenView.

Quick Links

�Appendix A� on page 56 This appendix lists the custom fields found in OVSD Configuration Item records.

Appendix A

This appendix lists the custom fields found in OVSD Configuration Item and Person records.

The items in the Resource Field Name column are what is available for the values of the ResourceField attribute of the DATAFIELD element in the Configuration.xml file.

Quick Link� �OVSD Configuration Item (CI) Custom Fields� on page 56� �OVSD Person Custom Fields� on page 61

OVSD Configuration Item (CI) Custom Fields

CI Custom Field Name CI Custom Field Data Type (Max Length)

Resource Field Name

Resource Field Data Type

CCF_CIDATE1 datetime(8) CIDate1 DoubleCCF_CIDATE2 datetime(8) CIDate2 DoubleCCF_CIDATE3 datetime(8) CIDate3 DoubleCCF_CIDATE4 datetime(8) CIDate4 DoubleCCF_CIDATE5 datetime(8) CIDate5 DoubleCCF_CIDATE6 datetime(8) CIDate6 DoubleCCF_CIDATE7 datetime(8) CIDate7 DoubleCCF_CIDATE8 datetime(8) CIDate8 DoubleCCF_CIDATE9 datetime(8) CIDate9 DoubleCCF_CIDATE10 datetime(8) CIDate10 DoubleCCF_CINOTSELECTABLE decimal(5) CINotSelectable BooleanCCF_CINUMBER1 decimal(9) CINumber1 IntegerCCF_CINUMBER2 decimal(9) CINumber2 IntegerCCF_CINUMBER3 decimal(9) CINumber3 IntegerCCF_CINUMBER4 decimal(9) CINumber4 IntegerCCF_CINUMBER5 decimal(9) CINumber5 IntegerCCF_CINUMBER6 decimal(9) CINumber6 IntegerCCF_CINUMBER7 decimal(9) CINumber7 IntegerCCF_CINUMBER8 decimal(9) CINumber8 IntegerCCF_CINUMBER9 decimal(9) CINumber9 IntegerCCF_CINUMBER10 decimal(9) CINumber10 IntegerCCF_CINUMBER11 decimal(9) CINumber11 IntegerCCF_CINUMBER12 decimal(9) CINumber12 Integer


Appendix A OVSD Configuration Item (CI) Custom Fields
CCF_CINUMBER13 decimal(9) CINumber13 IntegerCCF_CINUMBER14 decimal(9) CINumber14 IntegerCCF_CINUMBER15 decimal(9) CINumber15 IntegerCCF_CISHORTTEXT1 nvarchar(40) CIShortText1 StringCCF_CISHORTTEXT2 nvarchar(40) CIShortText2 StringCCF_CISHORTTEXT3 nvarchar(40) CIShortText3 StringCCF_CISHORTTEXT4 nvarchar(40) CIShortText4 StringCCF_CISHORTTEXT5 nvarchar(40) CIShortText5 StringCCF_CISHORTTEXT6 nvarchar(40) CIShortText6 StringCCF_CISHORTTEXT7 nvarchar(40) CIShortText7 StringCCF_CISHORTTEXT8 nvarchar(40) CIShortText7 StringCCF_CISHORTTEXT9 nvarchar(40) CIShortText9 StringCCF_CISHORTTEXT10 nvarchar(40) CIShortText10 StringCI1_4K1 nvarchar(4000) Cit4k1 StringCI2_4K2 nvarchar(4000) Cit4k2 StringCI3_4K3 nvarchar(4000) Cit4k3 StringCI4_4K4 nvarchar(4000) Cit4k4 StringCI5_4K5 nvarchar(4000) Cit4k5 StringCCF_CITBOOLEAN1 decimal(5) CitBoolean1 BooleanCCF_CITBOOLEAN2 decimal(5) CitBoolean2 BooleanCCF_CITBOOLEAN3 decimal(5) CitBoolean3 BooleanCCF_CITBOOLEAN4 decimal(5) CitBoolean4 BooleanCCF_CITBOOLEAN5 decimal(5) CitBoolean5 BooleanCCF_CITEXT1 nvarchar(255) CIText1 StringCCF_CITEXT2 nvarchar(255) CIText2 StringCCF_CITEXT3 nvarchar(255) CIText3 StringCCF_CITEXT4 nvarchar(255) CIText4 StringCCF_CITEXT5 nvarchar(255) CIText5 StringCCF_CITEXT6 nvarchar(255) CIText6 StringCCF_CITEXT7 nvarchar(255) CIText7 StringCCF_CITEXT8 nvarchar(255) CIText8 StringCCF_CITEXT9 nvarchar(255) CIText9 StringCCF_CITEXT10 nvarchar(255) CIText10 StringCCF_CITEXT11 nvarchar(255) CIText11 StringCCF_CITEXT12 nvarchar(255) CIText12 StringCCF_CITEXT13 nvarchar(255) CIText13 StringCCF_CITEXT14 nvarchar(255) CIText14 StringCCF_CITEXT15 nvarchar(255) CIText15 StringCCF_CITEXT16 nvarchar(255) CIText16 StringCCF_CITEXT17 nvarchar(255) CIText17 StringCCF_CITEXT18 nvarchar(255) CIText18 StringCCF_CITEXT19 nvarchar(255) CIText19 String

CCF_CITEXT20 nvarchar(255) CIText20 StringCCF_CITEXT21 nvarchar(255) CIText21 StringCCF_CITEXT22 nvarchar(255) CIText22 StringCCF_CITEXT23 nvarchar(255) CIText23 StringCCF_CITEXT24 nvarchar(255) CIText24 StringCCF_CITEXT25 nvarchar(255) CIText25 StringCCF_CITEXT26 nvarchar(255) CIText26 StringCCF_CITEXT27 nvarchar(255) CIText27 StringCCF_CITEXT28 nvarchar(255) CIText28 StringCCF_CITEXT29 nvarchar(255) CIText29 StringCCF_CITEXT30 nvarchar(255) CIText30 StringCCF_CITEXT31 nvarchar(255) CIText31 StringCCF_CITEXT32 nvarchar(255) CIText32 StringCCF_CITEXT33 nvarchar(255) CIText33 StringCCF_CITEXT34 nvarchar(255) CIText34 StringCCF_CITEXT35 nvarchar(255) CIText35 StringCCF_CITEXT36 nvarchar(255) CIText36 StringCCF_CITEXT37 nvarchar(255) CIText37 StringCCF_CITEXT38 nvarchar(255) CIText38 StringCCF_CITEXT39 nvarchar(255) CIText39 StringCCF_CITEXT40 nvarchar(255) CIText40 StringCCF_CITEXT41 nvarchar(255) CIText41 StringCCF_CITEXT42 nvarchar(255) CIText42 StringCCF_CITEXT43 nvarchar(255) CIText43 StringCCF_CITEXT44 nvarchar(255) CIText44 StringCCF_CITEXT45 nvarchar(255) CIText45 StringCCF_CITEXT46 nvarchar(255) CIText46 StringCCF_CITEXT47 nvarchar(255) CIText47 StringCCF_CITEXT48 nvarchar(255) CIText48 StringCCF_CITEXT49 nvarchar(255) CIText49 StringCCF_CITEXT50 nvarchar(255) CIText50 StringCCF_CITEXT51 nvarchar(255) CIText51 StringCCF_CITEXT52 nvarchar(255) CIText52 StringCCF_CITEXT53 nvarchar(255) CIText53 StringCCF_CITEXT54 nvarchar(255) CIText54 StringCCF_CITEXT55 nvarchar(255) CIText55 StringCCF_CITEXT56 nvarchar(255) CIText56 StringCCF_CITEXT57 nvarchar(255) CIText57 StringCCF_CITEXT58 nvarchar(255) CIText58 StringCCF_CITEXT59 nvarchar(255) CIText59 StringCCF_CITEXT60 nvarchar(255) CIText60 StringCCF_CITEXT61 nvarchar(255) CIText61 String

CCF_CITEXT62 nvarchar(255) CIText62 StringCCF_CITEXT63 nvarchar(255) CIText63 StringCCF_CITEXT64 nvarchar(255) CIText64 StringCCF_CITEXT65 nvarchar(255) CIText65 StringCCF_CITEXT66 nvarchar(255) CIText66 StringCCF_CITEXT67 nvarchar(255) CIText67 StringCCF_CITEXT68 nvarchar(255) CIText68 StringCCF_CITEXT69 nvarchar(255) CIText69 StringCCF_CITEXT70 nvarchar(255) CIText70 StringCCF_CITEXT71 nvarchar(255) CIText71 StringCCF_CITEXT72 nvarchar(255) CIText72 StringCCF_CITEXT73 nvarchar(255) CIText73 StringCCF_CITEXT74 nvarchar(255) CIText74 StringCCF_CITEXT75 nvarchar(255) CIText75 StringCCF_CITEXT76 nvarchar(255) CIText76 StringCCF_CITEXT77 nvarchar(255) CIText77 StringCCF_CITEXT78 nvarchar(255) CIText78 StringCCF_CITEXT79 nvarchar(255) CIText79 StringCCF_CITEXT80 nvarchar(255) CIText80 StringCCF_CITEXT81 nvarchar(255) CIText81 StringCCF_CITEXT82 nvarchar(255) CIText82 StringCCF_CITEXT83 nvarchar(255) CIText83 StringCCF_CITEXT84 nvarchar(255) CIText84 StringCCF_CITEXT85 nvarchar(255) CIText85 StringCCF_CITEXT86 nvarchar(255) CIText86 StringCCF_CITEXT87 nvarchar(255) CIText87 StringCCF_CITEXT88 nvarchar(255) CIText88 StringCCF_CITEXT89 nvarchar(255) CIText89 StringCCF_CITEXT90 nvarchar(255) CIText90 StringCCF_CITEXT91 nvarchar(255) CIText91 StringCCF_CITEXT92 nvarchar(255) CIText92 StringCCF_CITEXT93 nvarchar(255) CIText93 StringCCF_CITEXT94 nvarchar(255) CIText94 StringCCF_CITEXT95 nvarchar(255) CIText95 StringCCF_CITEXT96 nvarchar(255) CIText96 StringCCF_CITEXT97 nvarchar(255) CIText97 StringCCF_CITEXT98 nvarchar(255) CIText98 StringCCF_CITEXT99 nvarchar(255) CIText99 StringCCF_CITEXT100 nvarchar(255) CIText100 StringCCF_ID decimal(9) ID LongCCF_IPADDRESS nvarchar(50) IPAddress StringCCF_MAXINSTALLATIONS decimal(9) MaxInstallations Integer

CCF_NAME1 nvarchar(255) Name1 StringCCF_NAME2 nvarchar(255) Name2 StringCCF_ORDERNR nvarchar(50) OrderNr StringCCF_PRICE decimal(9) Price DoubleCCF_PURCHASEDATE datetime(8) PurchaseDate DoubleCCF_REMARK nvarchar(255) Remark StringCCF_SERIALNUMBER nvarchar(50) SerialNumber StringCCF_SERVICENAVNAME nvarchar(255) ServiceNavName StringCCF_SHORTTEXT11 nvarchar(40) ShortText11 StringCCF_SHORTTEXT12 nvarchar(40) ShortText12 StringCCF_SHORTTEXT13 nvarchar(40) ShortText13 StringCCF_SHORTTEXT14 nvarchar(40) ShortText14 StringCCF_SHORTTEXT15 nvarchar(40) ShortText15 StringCCF_SHORTTEXT16 nvarchar(40) ShortText16 StringCCF_SHORTTEXT17 nvarchar(40) ShortText17 StringCCF_SHORTTEXT18 nvarchar(40) ShortText18 StringCCF_SHORTTEXT19 nvarchar(40) ShortText19 StringCCF_SHORTTEXT20 nvarchar(40) ShortText20 StringCCF_SHORTTEXT21 nvarchar(40) ShortText21 StringCCF_SHORTTEXT22 nvarchar(40) ShortText22 StringCCF_SHORTTEXT23 nvarchar(40) ShortText23 StringCCF_SHORTTEXT24 nvarchar(40) ShortText24 StringCCF_SHORTTEXT25 nvarchar(40) ShortText25 StringCCF_SHORTTEXT26 nvarchar(40) ShortText26 StringCCF_SHORTTEXT27 nvarchar(40) ShortText27 StringCCF_SHORTTEXT28 nvarchar(40) ShortText28 StringCCF_SHORTTEXT29 nvarchar(40) ShortText29 StringCCF_SHORTTEXT30 nvarchar(40) ShortText30 StringCCF_SHORTTEXT31 nvarchar(40) ShortText31 StringCCF_SHORTTEXT32 nvarchar(40) ShortText32 StringCCF_SHORTTEXT33 nvarchar(40) ShortText33 StringCCF_SHORTTEXT34 nvarchar(40) ShortText34 StringCCF_SHORTTEXT35 nvarchar(40) ShortText35 StringCCF_SHORTTEXT36 nvarchar(40) ShortText36 StringCCF_SHORTTEXT37 nvarchar(40) ShortText37 StringCCF_SHORTTEXT38 nvarchar(40) ShortText38 StringCCF_SHORTTEXT39 nvarchar(40) ShortText39 StringCCF_SHORTTEXT40 nvarchar(40) ShortText40 StringCCF_SHORTTEXT41 nvarchar(40) ShortText41 StringCCF_SHORTTEXT42 nvarchar(40) ShortText42 StringCCF_SHORTTEXT43 nvarchar(40) ShortText43 StringCCF_SHORTTEXT44 nvarchar(40) ShortText44 String

Appendix A OVSD Person Custom Fields
OVSD Person Custom Fields
CCF_SHORTTEXT45 nvarchar(40) ShortText45 StringCCF_SHORTTEXT46 nvarchar(40) ShortText46 StringCCF_SHORTTEXT47 nvarchar(40) ShortText47 StringCCF_SHORTTEXT48 nvarchar(40) ShortText48 StringCCF_SHORTTEXT49 nvarchar(40) ShortText49 StringCCF_SHORTTEXT50 nvarchar(40) ShortText50 StringCCF_SHORTTEXT51 nvarchar(40) ShortText51 StringCCF_SHORTTEXT52 nvarchar(40) ShortText52 StringCCF_SHORTTEXT53 nvarchar(40) ShortText53 StringCCF_SHORTTEXT54 nvarchar(40) ShortText54 StringCCF_SHORTTEXT55 nvarchar(40) ShortText55 StringCCF_SHORTTEXT56 nvarchar(40) ShortText56 StringCCF_SHORTTEXT57 nvarchar(40) ShortText57 StringCCF_SHORTTEXT58 nvarchar(40) ShortText58 StringCCF_SHORTTEXT59 nvarchar(40) ShortText59 StringCCF_SHORTTEXT60 nvarchar(40) ShortText60 StringCCF_UNIQUE decimal(5) Unique BooleanCCF_WARRANTYDATE datetime(8) WarrantyDate Double

Person Custom Field Name

Person Custom Field Data Type (Max Length)

Resource Field Name Resource Field Data Type

PER_ALLOWEMAIL decimal(5) AllowEmail BooleanPER_ALLOWINASSIGNMENT

decimal(5) AllowInAssignment Boolean

PER_BIRTHDATE datetime(8) Birthdate DoublePER_EMAIL nvarchar(255) Email StringPER_EMAILLOWER nvarchar(255) EmailLowerCase StringPER_GENDER decimal(5) Gender IntegerPER_IDENTIFICATIONNUMBER

nvarchar(50) IdentificationNumber String

PER_INITIALS nvarchar(50) Initials StringPER_JOBTITLE nvarchar(50) Jobtitle StringPER_NAME nvarchar(80) Name StringPEC_PERSHORTTEXT1 nvarchar(40) PerShorttext1 StringPEC_PERSHORTTEXT2 nvarchar(40) PerShorttext2 StringPEC_PERSHORTTEXT3 nvarchar(40) PerShorttext3 StringPEC_PERSHORTTEXT4 nvarchar(40) PerShorttext4 StringPEC_PERSHORTTEXT5 nvarchar(40) PerShorttext5 StringPEC_PERSHORTTEXT6 nvarchar(40) PerShorttext6 String


PEC_PERSHORTTEXT7 nvarchar(40) PerShorttext7 StringPEC_PERSHORTTEXT8 nvarchar(40) PerShorttext8 StringPEC_PERSHORTTEXT9 nvarchar(40) PerShorttext9 StringPEC_PERSHORTTEXT10 nvarchar(40) PerShorttext10 StringPEC_PERSONDATE1 datetime(8) PersonDate1 DoublePEC_PERSONDATE2 datetime(8) PersonDate2 DoublePEC_PERSONDATE3 datetime(8) PersonDate3 DoublePEC_PERSONDATE4 datetime(8) PersonDate4 DoublePEC_PERSONDATE5 datetime(8) PersonDate5 DoublePEC_PERSONDATE6 datetime(8) PersonDate6 DoublePEC_PERSONDATE7 datetime(8) PersonDate7 DoublePEC_PERSONDATE8 datetime(8) PersonDate8 DoublePEC_PERSONDATE9 datetime(8) PersonDate9 DoublePEC_PERSONDATE10 datetime(8) PersonDate10 DoublePER_NOTSELECTABLE decimal(5) PersonNotSelectable BooleanPEC_PERSONNUMBER1 decimal(9) PersonNumber1 IntegerPEC_PERSONNUMBER2 decimal(9) PersonNumber2 IntegerPEC_PERSONNUMBER3 decimal(9) PersonNumber3 IntegerPEC_PERSONNUMBER4 decimal(9) PersonNumber4 IntegerPEC_PERSONNUMBER5 decimal(9) PersonNumber5 IntegerPEC_PERSONNUMBER6 decimal(9) PersonNumber6 IntegerPEC_PERSONNUMBER7 decimal(9) PersonNumber7 IntegerPEC_PERSONNUMBER8 decimal(9) PersonNumber8 IntegerPEC_PERSONNUMBER9 decimal(9) PersonNumber9 IntegerPEC_PERSONNUMBER10 decimal(9) PersonNumber10 IntegerPEC_PERSONTEXT1 nvarchar(255) PersonText1 StringPEC_PERSONTEXT2 nvarchar(255) PersonText2 StringPEC_PERSONTEXT3 nvarchar(255) PersonText3 StringPEC_PERSONTEXT4 nvarchar(255) PersonText4 StringPEC_PERSONTEXT5 nvarchar(255) PersonText5 StringPEC_PERSONTEXT6 nvarchar(255) PersonText6 StringPEC_PERSONTEXT7 nvarchar(255) PersonText7 StringPEC_PERSONTEXT8 nvarchar(255) PersonText8 StringPEC_PERSONTEXT9 nvarchar(255) PersonText9 StringPEC_PERSONTEXT10 nvarchar(255) PersonText10 StringPEC_PERSONTEXT11 nvarchar(255) PersonText11 StringPEC_PERSONTEXT12 nvarchar(255) PersonText12 StringPEC_PERSONTEXT13 nvarchar(255) PersonText13 StringPEC_PERSONTEXT14 nvarchar(255) PersonText14 StringPEC_PERSONTEXT15 nvarchar(255) PersonText15 StringPEC_PERSONTEXT16 nvarchar(255) PersonText16 StringPEC_PERSONTEXT17 nvarchar(255) PersonText17 String

PEC_PERSONTEXT18 nvarchar(255) PersonText18 StringPEC_PERSONTEXT19 nvarchar(255) PersonText19 StringPEC_PERSONTEXT20 nvarchar(255) PersonText20 StringPEC_PERSONTEXT21 nvarchar(255) PersonText21 StringPEC_PERSONTEXT22 nvarchar(255) PersonText22 StringPEC_PERSONTEXT23 nvarchar(255) PersonText23 StringPEC_PERSONTEXT24 nvarchar(255) PersonText24 StringPEC_PERSONTEXT25 nvarchar(255) PersonText25 StringPEC_TEXT64KB ntext(16) PersonText64kB StringPER_PRIMARYTELNR nvarchar(50) PrimaryTelephoneNumber StringPER_REMARK nvarchar(255) Remark StringPER_SENDMEMAILIFINEEDTOAPPROVE
decimal(5) SendMeMailIfINeedToApprove Boolean



Aaction

command 42automate data import/export 35

CCarbon Copy 35, 42, 51command

action 42configure data export 19configure data exports 37configure data import 21connector agent

download 38install 17, 18

copyright 2creation date of document 2critical error

in HP OpenView NNM 49in HP OVO 42

Ddata export

configure 19run 20

data export xml file 20data exports

configure 37data import

configure 21run 34verify 35

documentprint date 2

Eerror

database access 39out of memory 39

errors 21export

automate 35

HHelpdesk Solution 42, 51HP OpenView server 43, 52

Iimport

automate 35view initial results 35

install connector agent 17, 18installing

Connector for HP OpenView 13integrate service desk 35

Llegal notice 2licensing 15log files 21

Mmenu integration

operations 43service desk 35

MIB 9

Nnotice 2NS SNMP agent 43, 52

Ppatent 2prerequisites 13product version 2

Rregistration 15reports 38Resource Manager 9, 35, 42, 51, 52run data export 20run data import 34

Ssetting up 17, 40setting up network node manager 47solaris 37

Ttrademark 2trap

making it a critical error in NNM 49making it a critical error in OVO 42

troubleshooting 39

Uuninstall 14upgrade 13user interface 37

NNM 52OVO 44

Vverify data import 35version 2

Xxml file

data export 20

Index

Date post:	29-Apr-2018
Category:	Documents
Upload:	ngocong
View:	219 times
Download:	1 times

LTIRISﬁ CONNECTOR PACK 6.0 FOR HP...

Documents