Managing Content Manager Synchronization

If your installation includes standby Content Manager computers, you can set parameters that specify Content Manager standby activities.

You can specify how often checks occur to ensure that the active dispatcher has not failed, how long it takes to determine which Content Manager is active when failover occurs and at startup, how often an active Content Manager sends a response when it is busy, and how long a short network interruption can be without causing a failover.

The following parameters are available:

CM.CMSync_NegotiationTime
Specifies in milliseconds the length of time that it takes to determine the active Content Manager when a failover occurs.

The valid settings are 1 to 9223372036854775807. The default is 2000.

CM.CMSync_NegotiationTimeForStartUp
Specifies in milliseconds the length of time that it takes to determine the active Content Manager at startup.

The valid settings are 1 to 9223372036854775807. The default is 60000.

CM.CMSync_CheckActive Time
Specifies in milliseconds the length of time that it takes for an active Content Manager to become standby when another Content Manager becomes active.

The default is 10000.

CM.CMSync_PingTimeout
Specifies in milliseconds the length of time that it takes for a busy Content Manager to send a response if it is running.

The valid settings are 1 to 9223372036854775807. The default is 120000.

CM.CMSync_ShortNetworkInterruptionTime
Specifies in milliseconds the length of time that a short network interruption can occur without causing a failover.

The valid settings are 1 to 9223372036854775807. The default is 3000.