12.2 THE OVO OPERATORThe OVO operator is the user responsible for monitoring the environment. The message browser provides the operator with a view of messages and is the focal point of an operator account. The messages in the message browser indicate to the operator that an event has occurred. An event typically indicates that something in the managed enterprise has gone wrong. The message browser contains ten columns, as shown in Figure 12-4. Each column provides indicators to the operator. At a glance, the operator can determine where the event originated, the severity of the event, and the type of event that occurred. Figure 12-4. The message browser is the focal point of OVO. The message browser contains events that indicate to the operator that something has happened. At a glance, an operator can determine the severity of the event, the event message, and node on which the event occurred.The operator login provides a toolset enabling the operator to perform a job. The job entails attempting to resolve problems listed by the events in the message browser. The operator login consists of five windows, described briefly in the following list:
OVO provides a Java-based GUI similar to that shown in Figure 12-5. The java client can be installed on Windows and Unix systems and configured to access the OVO server. The necessary components of OVO are available from the Java-based GUI for an operator to monitor messages and perform routine tasks. Figure 12-5. The left pane of the Java-based GUI consists of an Explorer-like tree view of managed nodes, node groups, message groups, and applications. The right pane consists of the message browser.The operator has the ability to limit the messages in the view by setting the filter as shown in Figure 12-5. An additional feature available with the Java-based GUI is the ability to click on a column to sort messages. By default, messages are sorted according to the timestamp. If you were to click the [Node] button at the top of the Node column, the messages would be sorted alphabetically by node name. |