Starting Jobs and Job Templates

When you start a job that contains a standalone or cluster pipeline, Control Hub sends an instance of the pipeline to a Data Collector assigned all labels tagged to the job. The Data Collector remotely runs the pipeline instance.

When you start a job that contains an edge pipeline, Control Hub sends an instance of the pipeline to an SDC Edge assigned all labels tagged to the job. The SDC Edge remotely runs the pipeline instance.

When you start a job template, you create and start one or more job instances from the template. Control Hub sends an instance of the pipeline to a Data Collector or SDC Edge for each job instance that you create.

Tip: You can also start a job from a topology. Or, instead of manually starting jobs, you can also use the Control Hub scheduler to schedule jobs to start on a regular basis.

Starting Jobs

When you start a job, you start a single job instance. Each job instance can run multiple pipeline instances, based on the number of pipeline instances configured for the job.

  1. In the Navigation panel, click Jobs.
  2. To start a single job, hover over the inactive job and then click the Start Job icon: .
  3. To start multiple jobs, select inactive jobs in the list and then click the Start Job icon above the job list.

Starting Job Templates

When you start a job template, you create and start one or more job instances from the template. You specify a suffix to uniquely name each job instance, the number of job instances to create from the template, and the parameter values to use for each job instance.

Each job instance can run multiple pipeline instances, based on the number of pipeline instances configured for the job template.

  1. In the Navigation panel, click Jobs.
  2. Hover over the job template and then click the Start Job icon: .
  3. On the Create and Start Job Instances window, configure the following properties:
    Job Instances Property Description
    Instance Name Suffix Suffix used to uniquely name each job instance:
    • Counter
    • Timestamp
    • Parameter Value
    The suffix is added to the job template name after a hyphen, as follows:
    <job template name> - <suffix>
    Runtime Parameters for Each Instance Runtime parameter values for each job instance. Overrides the default parameter values defined for the pipeline.

    Define the parameter values in bulk edit mode in JSON format. Or, define them in a file in JSON format and upload the file.

    Add Another Instance When using bulk edit mode to define parameter values, click Add Another Instance to create another job instance.

    Control Hub adds another group of runtime parameters and values to the list of runtime parameters.

    For example, the following image shows a job template that creates and starts two job instances using a counter for the suffix name:

  4. Click Create and Start.