Resource controls define how job groups and Agents use network traffic when transferring content.
Job resource controls limit the number of concurrently running jobs and the aggregate bandwidth used by those jobs, per job group.
Agent resource controls limit the number of job components that can be run at a time on a specified Agent, and the aggregate bandwidth used by those components, per Agent. The job components controlled can be file transfers or commands.
Jobs or job components that exceed the allowable limits are queued in the job group or Agent and run after other jobs and commands have completed. Queuing ensures that the bandwidth used by a set of running jobs does not exceed the capacity of a network link, or that only one operation is processed at a time by a particular server.
Jobs and job components queued by the application of resource controls appear in the Queued state in job lists, on the job details page, and in the View Job Queue window. Once allowed to run, jobs and job components automatically transition to the Running state.
When the number of concurrent jobs or job components is set to 1, transfers are completed serially, with each using all allocated bandwidth.
When jobs or job components are set to run concurrently, multiple jobs begin simultaneously, with aggregate bandwidth shared equally. Any jobs or job components over the concurrency limit stay in the queue. When a transfer completes, queued jobs or job components move into the running state and the available bandwidth is reallocated.
Once you have created a resource control, you can specify which users or groups have access to it. Users only see the resource controls that are made available to them. Users who have access to resource controls must also have access to the related job groups or Agents to be able to select them when applying a new resource control.
To set resource permissions:
To remove permissions, select the user or group in the Current Permissions list and click Remove.
When multiple resource controls are connected to the same job, they are applied according to an order of priority:
On a single Manager, the highest priority resource takes effect. When multiple Managers have resource controls that affect the same job, the lowest bandwidth, belonging the highest priority control, takes effect.
For example, if an administrator at Site A attempts to increase of the bandwidth of a transfer to a level higher than configured at Site B, the lower bandwidth of Site B is maintained.
Note: Manual overrides can be added by opening a job or via API request. If you have manual override permissions, you can exceed resource control limits without impacting other running jobs. You can also reorder jobs queued by job resource controls.
|Scenario||Recommended Resource Control|
|Operator delivering files to another business partner (B2B) or trusted Manager||Job|
|Operator receiving files from another business partner (B2B)||Agent|
|Operator controlling bandwidth associated with a load-balanced group of Agents||Agent|
|Operator controlling bandwidth associated with Agents in multiple locations that belong to the same Manager||Job|