OvORB is a Operations Center software component that wraps the HP OpenView Network Node Manager (NNM) network management system with a JAVA RMI object interface, thus enabling access to many of OpenView’s alarm-oriented core functions and data over a network.
For instructions on creating and configuring HP OpenView Network Node Manager adapters after the OvORB is installed, see Section 2.12, HP OpenView Network Node Manager.
The HP OpenView NNM adapter in Operations Center software connects to the OvORB over the network or locally, if OpenView and Operations Center software are installed on the same machine. The OvORB provides real-time access to OpenView alarms from any Web browser using the Operations Center console. It is also possible to place OpenView alarms in a centralized location using the Operations Center software automation functions.
Accessing OpenView alarm information in Operations Center software requires running both the OvORB and the HP OpenView NNM adapter.
Table 10-10 outlines the system requirements for installing the OvORB:
Table 10-10 System Requirements
|
OS |
Description |
|---|---|
|
Windows |
HP OpenView NNM 6.4, 7.0x, or 7.5 for Windows 2000 |
|
HP‑UX (PA-RISC Only), Linux, and Solaris |
HP OpenView NNM 6.4, 7.0x, or 7.5 For Linux only, RedHat Linux Application Server 2.1 (AS2.1) ‑ 7.01 of NNM |
The default port for OvORB is 1572. Prior to installing OvORB, determine if port 1572 is already in use on the OpenView server.
To verify port 1572 is available:
Enter one of the following at a command prompt:
|
Windows: |
netstat ‑an | find "LISTEN" | find "1572" |
|
UNIX: |
netstat ‑an | grep "LISTEN" | grep "1572" |
If either command results in a line ending with LISTENING, the port is in use; therefore, select a different port.
For UNIX, select an available port number above 1000 if running the OpenView client as a user other than root.
The ORB requires some manual configuration after the installer is finished. Note the file permissions must be at least r‑xr‑xr‑x.
To configure the OvORB:
Register the OvORB as an OV managed process.
From the command line, use the HP ovaddobj command to add the OvORB as an OV managed process. For example, if the OvORB is installed in the D:/root/ovorb directory, execute the command:
ovaddobj D:/root/ovorb/lrf/ovorb.lrf
Copy the Operations Center Application Registration file to the OpenView Registration directory.
For example, if the OvORB is installed in the D:/root/ovorb directory for Windows, execute the command:
copy "D:/root/ovorb/registration/C/*" "C:/Program Files/HP OpenView/registration/C"
For UNIX, execute the command is:
cp /root/ovorb/registration/C/* /etc/opt/OV/share/registration/C
Issue the following command to start the OvORB:
ovorb start
The registration is a one-time process. When you register the OvORB as an OV managed process, it automatically stops and starts when OV is stopped and started.
Operations Center is now ready to connect the NNM adapter.
Multiple OvORBs can run on the same UNIX server.
To install multiple OvORB instances:
Install the OvORB as described in the previous section.
When the OvORB Customizer opens, click the drop-down list and select an instance of the OvORB installation.
Select from 1–10 based on the number of OvORBs previously installed.
For example, if this is the first installation of an OvORB, the Program Instance is 1. For the second installation, the Program Instance is 2.
The OvORB is an OpenView managed process that starts and stops automatically. It is no longer started by the NNM as in previous adapter versions.
If the OvORB is not set up as an OV managed process, or if there is a need to restart the ORB, start or stop it via the command line.
To manually start the OvORB, enter the following HP NNM command:
/opt/OV/bin/ovstart ovorb
To manually stop the OvORB, enter the following HP NNM command:
/opt/OV/bin/ovstop ovorb