Synchronize derived tags and data log files, Monitoring network client and server connections, Synchronize derived tags and data log files – 31 – Rockwell Automation FactoryTalk View Site Edition Users Guide User Manual
Page 375
![background image](/manuals/581457/375/background.png)
14
•
S
ETTING
UP
F
ACTORY
T
ALK
SYSTEM
AVAILABILITY
14–31
•
•
•
• •
14
•
Pla
ceho
lde
r
Use an HMI server’s On Active and On Standby macros, to run the EventOn command
(starts event detection) when the HMI server becomes active, and to run the EventOff
command (stops event detection) when the HMI server goes on standby.
This will automatically ensure that event detection is only running on the Active (primary
or secondary) HMI server.
For information about On Active and On Standby macros, see page 14-18.
For information about creating macros, see Chapter 24, Adding logic and control.
Synchronize derived tags and data log files
To keep derived tags and data logs synchronized, ensure that the same derived tags
components and data log models are running on the primary and secondary computers.
You can also keep memory tags synchronized, if their values are the result of derived tags.
For information about replicating changes from the primary to the secondary HMI server,
see “Replicate changes to the secondary HMI server” on page 14-16.
Monitoring network client and server connections
The health monitoring system monitors network connections on all computers hosting
application clients and servers, in a network distributed application.
The system does the following connection monitoring:
The computer detection interval sets how often the system attempts to detect
whether a computer exists on the network. The default interval is two seconds.
The network failure detection interval sets how often the system attempts to
verify the health of the network connection to remote computers. The default interval
is 2 seconds.
The maximum network glitch sets the amount of time used to distinguish a
temporary network disruption from an actual communications failure. For more
information, see “About network glitches,” next.
The maximum delay before server is active sets the maximum amount of time
during a switch back to the primary server, that the server will wait for clients to
respond, before it becomes active. For more information, see “Notifying clients when
switching back to the primary” on page 14-23.
You can change the default settings, in the Health Monitoring Policy Settings dialog box.