Scheduling the execution of a Job - 6.3

Talend Administration Center User Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend Real-Time Big Data Platform
task
Administration and Monitoring
Deployment
EnrichPlatform
Talend Administration Center

To schedule the execution of a Job you have created from Talend Studio, you have to create an execution task based on this Job on the Job Conductor page. This task will then be scheduled to be generated, deployed and executed at a certain time.

How to add a task on a Job

  1. On the top toolbar of the Job Conductor page, click Add to display the configuration panel of the task.

  2. In the Label field of the panel, type in the name of the task, here it is load_california_clients_to_mysql.

  3. Click the icon and select the Job you created in the Talend Studio, here it is California1.

  4. In the Execution server field, select the server you registered on the Servers page.

  5. In the Timeout (s) field, type in how long to wait, in seconds, before the task is being killed, here it is 240 (4 minutes).

  6. Fill in other fields if needed then save your task. The load_california_clients_to_mysql task is created.

    To perform this action via the MetaServlet application, use the createTask command. For more information about the MetaServlet parameters, see Parameters and actions in metaServlet.

How to add a trigger on a task

  1. In the task list of the Job Conductor, select the task to which you want to add a trigger, here it is load_california_clients_to_mysql.

  2. Click the Triggers button at the bottom of the page. The corresponding panel opens.

  3. Click Add trigger, then select Add simple trigger in the list to add a time-based trigger on the task.

  4. In the [Add simple trigger] panel that opens on the right, fill in the relevant information:

    In the Label field, type in the name of your trigger, here it is trigger_california_job.

    Fill in a description in needed.

    Select the time at which the triggering takes place and is ended in the Start time and End time fields.

    In the Number of repetitions field, type in the number of executions that should occur in addition to the first execution. Type in 3 in order to trigger three executions: one to generate the code of your Job, one to deploy your Job and one to run your Job.

    In the Time interval (s) field, type in (in seconds) the time interval between triggerings, here it is 240 (4 minutes).

  5. Save your changes. In the Trigger status column, you can see that the trigger is added and is ready to be launched at the specified time.

How to generate, deploy and run your Job manually

Alternatively, if you did not add a trigger to your execution task, you can execute it manually.

  1. In the task list of the Job Conductor, select the task you want to execute, here it is load_california_clients_to_mysql.

  2. Click Generate on the top toolbar and wait a few seconds. The code of your Job is generated with the CommandLine application and the task status changes from Ready to generate to Ready to deploy.

    To perform this action via the MetaServlet application, use the requestGenerate command. For more information on the MetaServlet parameters, see Parameters and actions in metaServlet.

  3. Click Deploy on the top toolbar and wait a few seconds. The Job is deployed and the task status changes from Ready to deploy to Ready to run.

    To perform this action via the MetaServlet application, use the requestDeploy command. For more information on the MetaServlet parameters, see Parameters and actions in metaServlet.

  4. Click Run on the top toolbar and wait a few seconds. The Job is executed on the server that you registered on the Servers page.

    To perform this action via the MetaServlet application, use the runTask command. For more information on the MetaServlet parameters, see Parameters and actions in metaServlet.

For more information on how to monitor the executions of your Job, see Monitoring the execution of a Job.