Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Creating and modifying Execution Tasks for managing job runs

An Execution Task is a job-management object that you can associate with an individual job to keep track of its multiple job runs. The Execution Task grants you control over the execution schedule, the choice of target servers, and the values of job properties for the relevant job runs without modifying the definitions of the original job.

An Execution Task is especially useful when you want to:

  • Keep track of job runs while you iteratively execute the job on failed targets until the successful completion of the job on all target servers
  • Define separate job schedules for different target servers and coordinate job schedules with upcoming maintenance windows on the various servers
  • Override certain job properties with different values, without having to change the properties of the original job

Note

Execution Tasks are not relevant and are not available for the following types of jobs: Atrium Import Job, Upgrade Model Objects Job, and Virtual Infrastructure Discovery Job. Advanced Deploy Jobs are also not supported by Execution Tasks.

You can create an Execution Task manually or you can request the creation of the Execution Task while executing a job against failed targets. After the Execution Task is created, you can execute the associated job and view job run information through the Execution Task.

The following topics describe how to use Execution Tasks:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*