The replication settings that determine how and in what order content is uploaded to advanced storage devices, as set on ICmStorageDeviceConnection or ICmReplicaSynchronizationSiteSettings.

See Replication configuration

Namespace:  FileNet.Api.Constants
Assembly:  FileNet.Api (in FileNet.Api.dll)

ToggleSyntax

Visual Basic (Declaration)
Public Enumeration ReplicaSynchronizationType
C#
public enum ReplicaSynchronizationType
Visual C++
public enum class ReplicaSynchronizationType
JavaScript
FileNet.Api.Constants.ReplicaSynchronizationType = function();
FileNet.Api.Constants.ReplicaSynchronizationType.createEnum('FileNet.Api.Constants.ReplicaSynchronizationType', false);

ToggleMembers

TypeMember nameDescription
ASYNCHRONOUS
A ICmContentReplicationQueueSweep instance uploads the content to this replica. A slow storage device should always be defined as asynchronous. If this replica is in the same site as the Content Platform Engine instance, then the instance must be directly connected to the replica.
SECONDARY
A secondary replica is a candidate for synchronous content upload, and will be populated during upload if needed, depending on the number of required and desired replicas. If a secondary replica is not populated during upload, it will be populated asynchronously, by the replication queue sweep. Secondary replicas are lower priority than primary replicas, but the prioritization is site specific.

See Content upload priorities

PRIMARY
A primary replica is a candidate for synchronous content upload, and will be populated during upload if needed, depending on the number of required and desired replicas. If a primary replica is not populated during upload, it will be populated asynchronously, by the replication queue sweep. Primary replicas are higher priority than secondary replicas, but the prioritization is site specific.

See Content upload priorities

ToggleSee Also