Skip to main content Skip to complementary content

Starting Replications Automatically

The objective is to start automatically the replications of selected distributions. They can also be restarted automatically in situations such as machine shutdown, network outage, or interruption in the SQL Server service.

About this task

For this purpose, Talend Change Data Capture integrates a program (NT service and AS/400 IBMi batch job: DDSCHEDULE) called the Scheduler. This program must be started in automatic mode.


  1. You can check the good operation of the Scheduler directly from the Manager, and start or stop it directly from your machine. To do so, choose the Services option from the Supervise main menu. The following dialog box is displayed:
    Click on one of the services to display a context-sensitive menu, and stop or start the service from your machine.
  2. Now that the Scheduler service is initiated (the installation starts it automatically), it is ready to take your replications into account.
    In the Manager, select the desired source and the properties of the distribution.
  3. Open the Planning tab and select Supervise by scheduler check box.
    The schedule is used to define the working hours. By default, for round-the-clock operation, keep all ranges in green. In the schedule, each box represents a one-hour bracket.
    Every five minutes, the Scheduler polls the processes installed on the machine, whose status must be compared against the status specified in the schedule. It stops or starts the replication so that the replication status complies with the status specified in the schedule.
    For example, in the case of an interruption – voluntary or due to a network outage exceeding five minutes (see the Window in case of communication error parameter in the environment properties described in Talend Change Data CaptureInstallation Guide), the Scheduler would restart the replication endlessly.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!