Service
All jobs being executed in TIF will be executed/served by one service.
A service can be configured to execute its jobs in sequence or allowing parallel execution. E.g. jobs that must be executed in a specific order should be configured to run within the same service, using sequential execution.
To increase the throughput of your jobs, you should create services that are logically grouping your jobs. And services that handle jobs that are not sensitive to the order of execution should be marked to allow parallel execution.
A service can be paused at any time to prevent further jobs from being processed. All ongoing jobs will complete and any awaiting job will be put on hold until the service is enabled again. This is a useful feature in case you experience some issues with a remote system or a remote system having a planned maintenance.
Multiple services can be grouped together in a service group. A service group is just a logical grouping of related services. To enable/disable (pause / resume) all services within a group, you can on the service group level itself toggle this flag.
The image below illustrates how services are grouped together and how services configured to run parallel jobs is working.

Depending on the environment, the number of jobs allowed in parallel will vary. Typically, 3 jobs maximum will be allowed. Environments of type trial will not be allowed to run more than 1 job at a time. |
REST Jobs invoked Synchronously
A custom REST job may be configured to execute synchronously, e.g., the caller expects the result of the request to be responded in the same call.
If such REST job is using a service that currently is paused, the client will receive a status message of 503 to indicate that the service is not available at the moment
Administration
Within the Administration UI, services are found in the main category on the left side.

From there, you can also create the Service Groups.
A service can also be configured with a set of job-tags. The tags are, if configured, added to all jobs processed by the service. That can be used to easier filter jobs in the Job view.