Job queues
When creating a contract, Data Mover requires you to assign an execution queue. The selected queue determines how the jobs generated by the contract are scheduled and executed.
For step‑by‑step instructions, see Create an Input Contract in the Contracts section.
Queues are used to:
organize the jobs generated by a contract;
define the order in which jobs are processed;
control execution priority and system load.
The process works as follows:
Data Mover submits a job to the queue specified in the contract.
The submitted job remains in the queue until it is handled by the Job Manager.
The Job Manager analyzes each request and schedules it according to the parameters of the assigned queue.
When the conditions are met, the Job Manager schedules the job on the original component that requested execution and manages its lifecycle.
Queues determine when and in which order jobs are executed. If two jobs belong to different queues with different priority levels, jobs associated with the higher‑priority queue are executed before those associated with the lower‑priority queue.
By default, Data Mover automatically proposes a Default Queue when a contract is created but if needed you can assign a different queue with a different priority:
Open the Default Queue drop‑down menu during contract design.
Select one of the available queues from the list.
Only queues that have been previously defined in Setup → Job Queues are displayed in the drop‑down menu. See the Managing Job queues page for details.
A detailed explanation of jobs, their lifecycle, and how they are scheduled and managed by Data Mover is available on the Jobs pages.
Last updated