These settings determine how CA DataMinder servers collect diagnostic data from child machines and how often replication checkpoints are sent to child machines. They allow you to configure operations to minimize network impact.
These settings determine when and how often CA DataMinder generates replication checkpoints. These are sent to all child machines.Each child machine then returns a checkpoint acknowledgment. This is a confirmation that the child machine has received all infrastructure updates sent prior to this latest checkpoint.
You can specify when checkpoints are generated or how often they are generated.
You can specify the number of infrastructure updates that trigger a new checkpoint.
You can specify how many days checkpoints and their acknowledgments are retained on the CMS.
You can specify when, or how often, diagnostic data is collected.
This setting specifies how long the CMS or gateway spends collecting diagnostic data. This enables you to limit the network impact.
To minimize network impact, diagnostic data is collected as part of the normal communications between a parent and its child machines. But if there has been no communication between these machines during the collection period, this setting creates additional threads to actively collect this diagnostic data.
This setting is used to rectify inaccurate session records identified when processing the diagnostic data. If diagnostic data indicates a machine has not been running for longer than this expiry period, all open machine and user sessions for this machine are updated to the Logged Out state.
Copyright © 2014 CA.
All rights reserved.
|
|