These settings determine how often CA DataMinder machines send notification of newly captured data or local infrastructure changes. These notification messages act as triggers for data replication between CA DataMinder machines. These settings also cover connection management on CMSs and gateways.
Available for CMSs and gateways only. These settings cover connection management on a CMS or gateway server. They determine the maximum number of simultaneous connections to client machines, and the maximum number of days that infrastructure changes intended for offline client machines are retained in the CMS cache (the 'cache timeout') before being purged.
Note: Any offline client machines that fail to reconnect to the CMS and retrieve the latest infrastructure changes before the cache timeout expires are flagged as 'out-of-sync'. When an out-of-sync machine next reconnects to the CMS or gateway, it automatically resynchronizes all of its infrastructure data.
You determine how often a client machine notifies the CMS about newly captured data. When the CMS receives this notification, it transfers the captured data from the client to the CMS and the client stops sending notifications.
You determine how often client machines and the CMS notify each other of new infrastructure changes such as policy edits or user account updates. When the recipient machine receives this notification, it determines if it needs the update; if so, it requests the details. As soon as the recipient machine has processed the notification, the sender machine stops sending notifications.
You can specify how soon CA DataMinder begins logging failures by a source machine to contact its target machine.
You can disable the replication of captured data when the connection to the CMS or Gateway is over a Wide Area Network or dial-up (modem) connection.
If required, you can compress policy data and captured data before transmitting it across the network between CA DataMinder machines.
When a child machine replicates captured data to its parent server, it sends events in batches in order to conserve network bandwidth. This setting specifies the maximum number of KBytes in each batch.
Note: It is very unlikely that you will ever need to change the default batch size.
When a parent server replicates infrastructure changes (for example, local policy changes) to a child machine, it sends data objects in batches in order to conserve network bandwidth. This setting specifies the maximum number of KBytes in each batch.
Note: It is very unlikely that you will ever need to change the default batch size.
You can set up scheduled operations to automatically move events out of the replication holding cache at regular intervals. For full details, see the Platform Deployment Guide; search for 'reset the replication holding cache'.
|
Copyright © 2014 CA.
All rights reserved.
|
|