-
Sync times and configuration needs to be node specific. (Expectations would be defined during business requirements gathering)
-
Ability to control data updates by database in a replicating environment.
-
Solution should allow for the direct manipulation of database records for the purpose of mass data correction without affecting replication function.
-
Solution should provide capability to start and stop replication from the application directly by users with extended permissions.
-
Replication scheduling must be configurable, ideally in both directions (staggered timing inbound\outbound) per node.
-
Replication must be configurable to be triggered by application events (e.g. hot order requisition approval).
-
Solution must provide a data synchronization capability that synchronizes all application, configuration, and security data.
-
Solution must provide a data synchronization capability that synchronizes documents in both directions
-
Replication solution must work efficiently over poor connections (512k and 1.5 sec latency) and recover automatically from communication service outages (timeout recoverability).
-
Solution should provide a full and clear view of replication status in both directions to all remote locations/nodes.
-
Synchronization solution must provide facilities to perform automated conflict resolution, including post-processing capabilities.
-
Application must synchronize only instance-specific transitional data to remote locations/nodes (with the exception of the inventory pinging requirements).
-
Solution must have the capability to throttle bandwidth usage by the synchronization solutions for data, documents, and training.
-
Solution must have the ability to synchronize a remote instance after 3 months of inactivity (accounting for node relocation).
-
A supported process exists to correct rule- or conflict related replication failures.