A job is deployed to the Orchestration Server to automate processes, such as coordinating VM provisioning, high-performance computing, or general data center management. Jobs consist of Job Development Language (JDL) scripts and might have one or more policies associated with them. Policies define job arguments and other facts that are used by the job.
Usually a job has logic that runs on the Orchestration Server itself and schedules work to run on one or more managed resources that are running the Orchestration Agent. The logic that is dispatched and run on the managed resources is called a joblet. A job might or might not define one or more joblets.
A JDL script is partitioned into a Job section and one or more Joblet sections. The joblet sections of the script describe most of the work of a job. The Orchestration Server dispatches joblets to resources in the grid where the work is done.
A Job object represents an individual job in the Explorer tree of the Orchestration Console. This object contains facts with attributes that are used for job and joblet control. Policies associated with the job also control the job. The Orchestration Console has an administrative (“admin”) view in the Explorer Panel that lets you edit these objects.
This section includes information about a Job object that is visible in the Explorer view and the accompanying Admin view of the Orchestration Console: