About Resource Controls

Resource controls allow you to define how job groups and Agents use network traffic when transferring content. Job resource controls specify limits on 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, i.e. file transfers and commands, that can be run at a time on a specified Agent, and the aggregate bandwidth used by those components, per Agent.

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. This 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.

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 job groups or Agents, in order to be able to select them when creating the new resource control. For more information on access to resource controls, see Enabling Permissions.

Jobs and job components that are queued by the application of resource controls are displayed in job lists, job details panels and the View Job Queue dialog in the Queued state. Once they are allowed to run, they automatically transition to the Running state.

Managing Multiple Resource Controls

When multiple resource controls are connected to the same job, they are applied according to an order of priority:

  1. Manual override by an administrator
  2. Agent resource control
  3. Job resource control
  4. Initial job settings

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.

ScenarioRecommended Resource Control
Operator delivering files to another business partner (B2B) or trusted ManagerJob
Operator receiving files from another business partner (B2B)Agent
Operator controlling bandwidth associated with a load-balanced group of AgentsAgent
Operator controlling bandwidth associated with Agents in multiple locations that belong to the same ManagerJob