The HP OpenView Operations for UNIX Integration (referred to as OpenView) is Operations Center’
component for integrating with the HP OpenView Operations product line from Hewlett‐Packard.
OpenView supports configurations where the management server can reside on the same or different machine as the Oracle database. The OpenView integration supports both configurations.
The integration relies on efficient sampling of the different database tables for retrieving new and updated message and server data. The OpenView messages contain a number of time stamps that record the message state‐transitions that can be extracted for recording business metrics.
Configure the OpenView integration to enable or disable management functions (e.g., acknowledging alarms) within the Operations Center environment. There are three possible integration strategies:
OpenView Server Install Integration strategy: Install Operations Center and configure the HP OpenView Operations for UNIX adapter on the host OpenView server. This configuration enables management functions and does not require installing an ORB on the management server.
Object Type Property
Incident severity
Node Group status
Node status
Interface status
IP Address none
IP Subnet none
L2 Connection status
Property Value Severity/Condition
CRITICAL CRITICAL
WARNING INFO
MINOR MINOR
MAJOR MAJOR
NORMAL OK
DISABLED UNKNOWN
UNKNOWN UNKNOWN
NOSTATUS UNKNOWN
OVOORB Integration strategy: Install the OVOORB on each OpenView server. This strategy
Section 2.13.1, “Integrating Operations Center with HP OpenView Operations for UNIX,” on page 95
Section 2.13.2, “Quick Start for default OpenView Installations,” on page 96
Section 2.13.3, “View‐only Integrations,” on page 96
Section 2.13.4, “Hierarchy File and Alarm Fields,” on page 96
Section 2.13.5, “Historical Alarms,” on page 96
Section 2.13.6, “Alarm Counts,” on page 96
Section 2.13.7, “Alarm Operations,” on page 98
Section 2.13.8, “Management Operations,” on page 99
Section 2.13.9, “Executing OVO Applications,” on page 100
2.13.1 Integrating Operations Center with HP OpenView Operations for UNIX
Review this section to determine the best strategy for integrating Operations Center with
For more instructions, see Chapter 10, “ORB Installation,” on page 251.
4 Create an adapter for each instance of HP OpenView Operations.
For more instructions, see Section 5.1, “Creating an Adapter,” on page 193.
5 Modify the HP OpenView adapter properties.
For more instructions, see Section A.15, “HP OpenView Operations for UNIX,” on page 319.
2.13.2 Quick Start for default OpenView Installations
The integration adapter properties default values match the default OpenView Installation.
To integrate OpenView using the default OpenView installation:
1 Create an adapter for the HP OpenView Operations system.
For more instructions, see Section 5.1, “Creating an Adapter,” on page 193.
2 Set the DB Host adapter property equal to the hostname of the Oracle database server.
3 Set the DB Pass adapter property equal to the password of the Oracle user specified when configuring the adapter.
The default adapter property value is OpC_op.
4 Start the adapter.
2.13.3 View-only Integrations
To create a view‐only integration:
1 Create an adapter for the HP OpenView Operations system.
For instructions, see Section 5.1, “Creating an Adapter,” on page 193.
2 Verify that the following properties are specified: DB Host, DB Name, DB Poll, DB Port, DB Type, and DB User.
3 Leave the following properties unspecified (empty): OVO Password and OVO Server.
4 Start the adapter.
2.13.4 Hierarchy File and Alarm Fields
The integration ships with a default hierarchy file, DefaultOVOHierarchy.xml. The file contains a list of all of the available alarm fields that the Operations Center XML generator can evaluate.
2.13.5 Historical Alarms
Historical alarms are acknowledged alarms that exist on the OpenView server.
To display only real‐time alarms and hide all acknowledged alarms in Operations Center:
1 Create an alarm filter in the Operations Center console to display only alarms that are not acknowledged (where Acknowledged equals False).
For more information see Filtering Alarms the Operations Center 5.0 User Guide.
2.13.6 Alarm Counts
The following status bars in the Operations Center Alarms view display alarm counts:
The filter bar displays the total number of active alarms by severity regardless of alarm ownership:
The title bar identifies the total number of active alarms by severity with regard to alarm ownership:
These counts do not include alarms owned by the current and other users.
The status bar identifies the total number of active alarms regardless of alarm ownership.
It is located at the bottom of the window and shows a single tally of all alarms.
For example, assume nine active alarms are the responsibility of an OpenView user. There are no messages owned by this or any other user. Figure 2‐8 shows the Operations Center Alarms view for these nine alarms:
Figure 2-8 Alarms View
Both the Filter and Title Bar show 1 MAJOR alarm, 2 INFO alarms and 6 OK alarms. The Status bar shows the total number of alarms equals 9.
Figure 2‐9 shows the alarm counts from OpenView’s Message Browser. It shows 1 MAJOR alarm, 2 INFO alarms and 6 Normal (OK) alarms, the same as Operations Center. Note the 2 ownership counts (the pink and white counters) both show 0.
Figure 2-9 OpenVieew Message Browser shows the same alarms as Operations Center
Now, assume the operator right‐clicks the INFO alarm with the message SWAP Utilization (92.00%) is greater than 80.00% and then clicks Own from the drop‐down menu. The operator claims
ownership of the alarm. The alarm remains in the browser. The new counts are shown in Figure 2‐10.
In Figure 2‐9, the filter bar shows 1 MAJOR alarm, 2 INFO alarms and 6 OK alarms. The status bar also shows the total number of alarms, 9 (1 + 2 + 6). Neither indicator changes based on alarm ownership.
However, note that the title bar count changed. It now shows 1 MAJOR alarm, 1 INFO alarm, and 6 OK alarms. Alarm ownership affects these counts. When the operator claimed ownership of the alarm, the number of INFO alarms in the title bar count decreased by 1. Note that the alarm is still visible in the Alarms view.
In Figure 2‐10, OpenView’s message browser alarm counts show 1 MAJOR alarm, 1 INFO alarm, and 6 OK alarms. Note the “owned by me” counter (the pink one) increased by 1.
Figure 2-10 OpenView Message Browser: The pink “owned by me” counter increased after the alarm ownership changed
To summarize:
Alarm ownership affects the title bar counts.
The filter and status bars in Operations Center display the total number of alarms, regardless of alarm ownership.
Operations Center does not display the “owned by me” and “owned by others” counter displayed in the OpenView message browser window.
2.13.7 Alarm Operations
The following operations are available for all alarms:
Properties: Shows all the details about a single message.
Print: Sends output to printer.
Additional management right‐click alarm operations are available to the user depending on the integration strategy selected when integrating HP OpenView Operations for UNIX (see “Adding Custom Alarm Properties” on page 90).
To enable these additional management operations, one of the following must occur:
An existing Operations Center server installation is on the same machine as the OpenView management server.
The OVOORB must be deployed.
To configure Operations Center on the OpenView Management Server, do the following as necessary: