HP OpenView Operations Administrator's Reference - filibeto.org

About the OVO Java-based Operator GUI
Accessing NNM from the Java GUI
342
Accessing NNM from the Java GUI
By default, the OVO Java GUI integrates Network Node Manager
(NNM). This NNM integration enables users to highlight nodes in the IP
Map of NNM systems, and to see and execute OV applications and
services directly from the OVO Java GUI.
You can use NNM integration in the following two situations:
❏ Locally (Java GUI only)
Where NNM is installed locally on the management server. This
integration is carried out automatically with the OVO installation.
❏ Remotely (Motif and Java GUIs)
Where NNM is installed remotely on another system. A separate
package must be manually installed on the NNM system. To find out
how to install NNM remotely on another system, see the OVO
Installation Guide for the Management Server.
Accessing NNM on a Local System (Java GUI only)
Accessing NNM on a local system enables you to view and start OV
services and applications locally from the OVO Java GUI. No additional
installation steps are necessary for this integration solution. If NNM is
running on the OVO management server, the user’s assigned OV
applications and OV services are used at startup to configure the NNM
GUI.
NOTE To access NNM locally through the Javan GUI, an OVO agent must be
installed and running on the OVO management server.
When an operator logs into a new OVO Java GUI session, the Java GUI
server process opcuiwww updates the operator’s specific registration
directory, based on the operator’s assigned OV services and OV
applications. The user can then view and execute OV applications from
the Java GUI, provided an X Window system is running on the Java GUI
client system.
Chapter 9