HP OpenView Operations Administrator's Reference - filibeto.org

About the OVO Java-based Operator GUI
Comparison of the Java and Motif GUIs
330
Comparison of the Java and Motif GUIs
In general, the OVO Java-based operator GUI offers the same
functionality as the Motif-based operator GUI. However, because of
differences in the implementation of Java and Motif, there are some
areas where the GUIs behave differently. These areas are described in
this section, and where appropriate, workarounds are given.
Comparison of Applications
The Java and Motif GUIs handle applications differently:
❏ Virtual Terminals
By default, virtual terminals are not available in the Java GUI. You
can set up virtual terminals by adding an OVO application of the
type Start on Local Client, which calls the application. When
executing the application in the Java GUI, OVO opens the
application on the managed node from which it was executed.
For Windows NT managed nodes, you can use the Telnet
application. If the Java GUI is running on UNIX, you can use xterm,
dtterm, or hpterm. You must set the parameter $OPC_NODES to get
the names of the nodes selected in the Java GUI. This parameter
tells your configured application on which node to start the terminal.
❏ NNM IP Map Application
By default, the NNM IP Map application, Jovw, is assigned to the
itop and netop operators. To find out how to access Jovw from the
Java GUI, see “Accessing Jovw” on page 350.
Comparison of Message Browsers
The Java and Motif GUIs handle message browsers differently:
❏ Customizing Message Columns
The OVO Java GUI lets you resize, move, hide, and change the order
of the columns in the message browsers. The Motif GUI does not let
you resize or move columns. With the Motif GUI, you can only hide
columns.
Chapter 9