Job queues are used for prioritizing and grouping batch jobs that are waiting to be executed by
Managed File Transfer
. By defining multiple Job Queues in the system, each queue can be used to execute Jobs that share common characteristics or service level agreements (SLAs). For example, you can create a Job Queue to run Jobs for a certain application or customer which may have a higher priority than other jobs. You could also create a single-threaded Job Queue for Jobs that need to run in sequential order. In a clustered environment, you can create a Job Queue to only execute Jobs on a specific
Managed File Transfer
system.
Projects can be submitted to a Job Queue through several methods. You can specify a Job Queue on the Project's Control Tab, from the Job Scheduler, Execute Remote Project, or the RunProject command in
Managed File Transfer
Command. When no Job Queue is specified, the Project will be executed in the Default Job Queue.
Each Job Queue can have a Priority to indicate the order in which the queue will be considered for job execution. The Job Queue priority will be a value from 1 to 10, in which Job Queues in a higher queue priority will be executed before Job Queues with a lower queue priority. For instance, a Job Queue with a queue priority of 6 will execute jobs before a Job Queue with a queue priority of 5. Jobs within a Job Queue that have the same queue priority will be processed on a first in/first out basis.
You can specify the number of Jobs which can be executed at one time within each Job Queue. The Max Active Jobs setting is limited to the maximum concurrent batch jobs specified in the Global Settings of
Managed File Transfer
.
As a Product Administrator, you can use the Job Queues Manager page to create and work with Job Queues in
Managed File Transfer
.
To view the Job Queue Manager, log in as a user with the Job Manager or Product Administrator role.