Alarm a distributed local network topology

In a distributed local network topology, the nodes that serve data (Application Object Servers) are not separated from the clients that consume data (Visualization nodes). That is, these workstation nodes combine Application Object Server functionality with Visualization node functionality, and each node hosts both components locally. A platform is deployed to each workstation node,.

It is more likely that every platform in this topology is configured as an alarm provider, and each of the alarm consumers queries the local platforms for alarms.

Consider the scope of interest of each platform. when configured as an alarm provider, the platform requests all alarms in the galaxy by default. If a workstation does not need to view all of the alarms in the galaxy, the platform on that computer should be configured to only subscribe to alarms that are within the scope of interest.

Best Practice

The following list summarizes the key points in setting up an optimized alarm distribution system in a distributed local network topology:

• All of the platforms on workstations will be alarm providers.

• If operators at a workstation will need to view all alarms in an application, you use the default scope for the platform alarm provider on that node, which is to subscribe to all alarms in the galaxy.

• If operators at a workstation do not need to view all alarms in the galaxy, configure the platform alarm provider scope of that node to subscribe only to alarms that are of interest to the operators at that node.