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.

  1. In Workforce Management, select Maintenance > System Administration > Job Scheduler.
  2. Click Add Schedule.
  3. Specify Data Replication in the Task Description field.
  4. Select Java Task in the Task Type field.
  5. Select Data Replication Task from the drop-down list.
  6. In the Scheduling Time section, select the Daily option and specify 3600 in the Interval field to run the task every 60 minutes.
  7. Click Submit and click OK at the confirmation prompt.
    Your Data Replication task is added to the list of scheduled tasks in the Task Schedules page.
  8. For your Data Replication task, click Parameters to specify job parameters. The Schedule Settings page is displayed.
  9. Specify this information:
    Number of Threads
    Specify the number of threads used by the Data Replication task. By default, this parameter is set to 4. The minimum number of threads is 1. The maximum number of threads is 10. If a number below 1 is specified, then 1 will be used. If a number above 10 is specified, then 10 will be used.
    Batch Size per Thread
    Specify how many table records can be fetched and processed at one time in a thread. By default, this parameter is set to 1000, as recommended by IMS. The maximum batch size is 5000.
  10. Click Submit to save the task parameters and click OK to confirm.
  11. Check the schedule. If the task is Disabled, click Resume to resume the task.
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.