About Resource Controls

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.

Enabling Permissions

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.

  • Edit - Users can modify the job queue to change job scheduling.
  • Delete - Users can delete the resource control.
  • Read - Users can view the resource control.

To set resource permissions:

  1. Navigate to Administration > Resource Controls > List.
  2. Select a resource and click Edit.
  3. On the Permissions tab, select users or user groups to add. Move users to the Current Permissions list by double-clicking or dragging them, or by clicking Select.
  4. Select the check boxes to set permissions.
  5. Click OK.

To remove permissions, select the user or group in the Current Permissions list and click Remove.

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
About Signiant

Signiant’s intelligent file movement software helps the world’s top content creators and distributors ensure fast, secure delivery of large files over public and private networks. Built on Signiant’s patented technology, the company’s on-premises software and SaaS solutions move petabytes of high-value data every day between users, applications and systems with proven ease.
LEARN MORE