Scheduling the Data Replication task
We recommend scheduling the Data Replication task to run every 60 minutes. After the initial data replication, the task will include any changes since the last time the task ran, plus the time period covered by the value of the COMMIT_ROLLBACK_SEGMENT_TIMEOUT registry parameter .If the COMMIT_ROLLBACK_SEGMENT_TIMEOUT registry parameter must be set to a value higher than 300 seconds, consider running the task less frequently.
Note:
- Since the employee time zone is used to calculate the UTC date-time values, ensure that all employees have an accurate time zone assigned in WFM before the Data Replication task is first enabled.
- If the delete history purge task was already enabled as part of BOD publishing, the task should be paused until after the initial replication has completed. See Purging delete history records for BOD publishing.
- A large amount of memory is used by the Job Scheduler during initial replication. Therefore, the memory on a production instance should be at least 16GB. For incremental replication, the memory and CPU usage will be much less. For information on recommended heap sizes, see "Configuring the Heap Size" in the Infor Workforce Management Installation and Configuration Guide.
- If a large volume of data is
being replicated, you may need to increase the value of the TASK_TIMEOUT
registry parameter to prevent the task monitor from terminating the Data
Replication task during initial replication. For the initial replication,
increase the value of the parameter to 3-24 hours, depending on the total
number of records to be replicated. After the initial replication is
complete, you can set the parameter back to its default value for
incremental replication. See the Infor Workforce Management Registry
Parameter Reference Guide for more information.
If the task still cannot be completed, you need to upgrade the Job Scheduler EC2 instance or run the task in a different affinity, or both. Consult with Infor Support on the changes.
If the Data Replication task is interrupted, or fails for
any reason, the task will continue from where it left off when the task restarts.