ViewPoint Manual

Functional Description
ViewPoint Manual—426801-001
5-29
Event Display Operations
Operator A and Operator B are logged on at Node 0, and Operator C is logged on at
Node 1. Note that Operator A and Operator B read from the same events cache, which
gets current event messages from the NCN event log through the event collection server.
Multiple Collectors
Up to five remote collectors can be specified as the source of events for each of the
event screens (primary, alternate, or last events). The events from these collectors are
sent directly to the event collection servers on the node where they are to be displayed.
The operator at an Alternate Events screen can specify from 1 to 5 collector names as
the source of events displayed on his or her screen.
The operator at a Primary Events or Last Events screen has no control over the
collectors. For these screens, multiple collector names must be specified at
configuration time. Two PATHCOM assigns determine the collector names for the
Primary or Last Events displays. (Refer to the description of the PRIMARY-
COLLECTOR and LAST-EVENT-COLLECTOR assigns in Appendix A, “Server
Assigns and Parameters.”)
When events are sent directly from named collectors at remote nodes, the events are not
filtered. Sending unfiltered events can increase network traffic. As a general rule, it is
more efficient to send events through forwarding distributors that use filters to reduce
the number and size of events sent over the network.
Remote Distributors
If only one collector is specified and that collector is at a remote node, ViewPoint starts
a remote consumer distributor at that node. In this case, filters can be associated with
the distributor so that filtered events are sent over the network.
At configuration time, the person managing the system or ViewPoint application can
include a DISTRIBUTOR assign in the Pathway configuration for ViewPoint to alter the
distributor program file. When this assign is used, ViewPoint always starts the
distributor using the specified program file, which can be either local or remote.
Event Display Operations
Figure 5-21 shows how primary-events and alternate-events displays are managed for
multiple operators at the same NCN. Operator A and Operator B are served by separate
tasks in the event collection server, which manages each operator’s primary-events and
alternate-events caches. (Figure 5-21 and succeeding figures assume a single network
control node.)
Note that alternate events are obtained directly from an alternate-events distributor, and
that this distributor is located on the remote node, if it is reading events from a remote
log. Each operator views only those events they want by having their own filter
installed in their own alternate-events distributor.