HP (Hewlett-Packard) HP OpenView Vantagepoint – Operation Manual for UNIX User Manual
Using the Integration Capabilities of the VPO Motif-based GUI
Integrating External Applications into the VPO GUI
Chapter 3
154
HP OpenView Applications
HP OpenView applications integrated as OV Applications present the
related application as an icon in the Application Desktop.
Double-clicking on the icon starts that action as described in the ARF.
related application as an icon in the Application Desktop.
Double-clicking on the icon starts that action as described in the ARF.
Note that OV Applications do not present the related menu items in the
VPO submaps, even if the corresponding ARF contains menu items.
Typical OV Applications are MIB Browser for SNMP, or HP OpenView
OmniBack II.
VPO submaps, even if the corresponding ARF contains menu items.
Typical OV Applications are MIB Browser for SNMP, or HP OpenView
OmniBack II.
Each action defined in the ARF must be integrated as a separate OV
Application. This allows you to tailor and customize complex OV
applications to the specific requirements of a user. You can specify a
different bitmap/symbol for each action.
Application. This allows you to tailor and customize complex OV
applications to the specific requirements of a user. You can specify a
different bitmap/symbol for each action.
When the operator starts an application from the Application Desktop,
the call is passed to the user’s ovw session, which always runs under the
UNIX user ID of the operator who started the VPO GUI.
the call is passed to the user’s ovw session, which always runs under the
UNIX user ID of the operator who started the VPO GUI.
HP OpenView Services
For HP OpenView Services, the integration procedure is very similar to
OV Applications but the operator does not see an icon on the Application
Desktop. This means that the OV Service is either started automatically
when the operator logs in to VPO, or it is started on demand from a
menu or toolbar.
OV Applications but the operator does not see an icon on the Application
Desktop. This means that the OV Service is either started automatically
when the operator logs in to VPO, or it is started on demand from a
menu or toolbar.
In the administrator’s Application Desktop, OV Services are represented
by icons, however, unlike OV applications, they cannot be invoked by
double-clicking. If required, you can invoke and access services from the
menu bar. Although services cannot be invoked by clicking on an icon,
they do appear as icons in the administrator’s Application Desktop, and
may be distributed to operators by copying as usual.
by icons, however, unlike OV applications, they cannot be invoked by
double-clicking. If required, you can invoke and access services from the
menu bar. Although services cannot be invoked by clicking on an icon,
they do appear as icons in the administrator’s Application Desktop, and
may be distributed to operators by copying as usual.
An OV Service allows you to integrate OpenView applications which
start daemons and/or should be integrated in the menu bar. This means
that VPO operators have no graphical representation of their assigned
services, but they might see or access additional submaps if the OV
Service corresponds to an OpenView map application.
start daemons and/or should be integrated in the menu bar. This means
that VPO operators have no graphical representation of their assigned
services, but they might see or access additional submaps if the OV
Service corresponds to an OpenView map application.
If menus are defined in the OV Application Registration File (ARF),
these menu items will be integrated in the menubar of the VPO submaps
for the operator.
these menu items will be integrated in the menubar of the VPO submaps
for the operator.