Creating and defining an Execution Task manually

Creation of an Execution Task separately from the execution of its associated job enables you to define all Execution Task settings before execution. This method of creating an Execution Task is especially useful if you want to define schedules, choose target servers, or set job property values for the Execution Task that differ from the original job settings.

During the creation of the Execution Task, you can define separate job schedules for different target servers and coordinate job schedules with upcoming maintenance windows on the various servers. You can also use recurring schedules to execute the job repeatedly on targets where it failed until its successful completion on all targets.

Before you begin

Ensure that you have, at minimum, the ExecutionTask.Create authorization.

To create an Execution Task manually

  1. Do one of the following:
    • Right-click the job folder in which you want to store the Execution Task and select New > Execution Task.
    • Right-click the job with which you want to associate the Execution Task and select Create Execution Task.
  2. Define the Execution Task, as described in the following topics:


    If the Execution Task is associated with a Workflow Job, a Virtual Guest Job, a Provision Job, or a UCS Provision Job, target selection is not relevant and the Targets panel is not displayed.

    The NSH Script Parameters panel is displayed only if you associate the Execution Task with an NSH Script Job that contains parameters.

    The Override BLPackage Properties panel is displayed only if you associate the Execution Task with a Deploy Job that contains local properties.

  3. When you have finished defining all Execution Task settings, click Finish. The Execution Task is added to the Jobs tree under the job with which it was associated.
Was this page helpful? Yes No Submitting... Thank you