Filter
Top Products
Using the Integration Capabilities of the VPO Motif-based GUI
Integrating External Applications into the VPO GUI
Chapter 3 153
Integrating HP OpenView Windows Applications
HP OpenView windows applications are applications already integrated
into the HP OpenView platform. These applications are defined through
OV application registration files (ARFs), and may then be integrated
into VPO. Depending on the integration method, these applications are
referred to as either OV Applications or OV Services.
Common characteristics of these applications are as follows:
❏ they are already integrated into HP OpenView windows
❏ their functions are defined in their Application Registration File
(ARF), and not in the VPO Add/Modify OV Application window or
the VPO Add/Modify OV Service window
❏ they are the only means of integrating map applications
❏ they are always started on the VPO management server, and rely on
standard UNIX remote commands (e.g., remsh) to be started on
systems other than the server
❏ they are restricted to startup on Customized OV Application Call
Window and to the functionality defined by the window. (In
particular, only objects passed to the OpenView application can be
modified.)
❏ they allow the retrieval of the list of selected objects by using
$OVwSelection, $OVwSelection1 and so on. The selection name of
the object is passed to the OpenView application. Exceptions are the
following objects, which may not be passed:
• VPO Message Groups
• VPO Applications and Application Groups
• VPO Operators
• VPO External Nodes
After configuration, the administrator must normally restart the VPO
GUI before invoking an OpenView application. This is true whether the
application is integrated as an OV Application or as an OV Service.
VPO does not provide a window for OpenView applications. The
application itself is responsible for establishing its own output methods.