Job directives control various aspects of how jobs run. Job directives can be provided through the Transformation Services, FME Flow REST API, and FME Flow Console (Deprecated).
Job directives are also available through Automations workflows that contain a Run a Workspace action or Schedule trigger.
|
Directive |
Description |
|---|---|
| tm_tag | The queue in which to run the job. The specified queue overrides the queue that would otherwise be assigned based on Queue Control job routing rules. If not specified, job routing rules apply. Tip To control the priority of job requests, set the priority of the queue. |
| tm_ttc | The time, in seconds, a job will remain in the running state. This directive is used to ensure that a job does not hang and block an FME Engine indefinitely. |
| tm_ttl | The "time to live" in the job queue in seconds. This is used in cases where jobs are time-sensitive and can become invalid or stale while waiting in the job queue. If a job is queued longer than "time to live", it is removed from the queue instead of redirecting to an engine. Note This directive is enforced only during periods when FME Engines are free, which comprises the time between completion of a job and the start of the next queued job. |
Examples
Transformation Services Example
Specify job directives as query string arguments in a URL.
This example specifies job queue high:
http://localhost/fmejobsubmitter/Samples/austinDownload.fmw&tm_tag=high
REST API Example
You can specify job directives in the body of these FME Flow REST API V3 endpoints:
/transformations/submit/< repository >/< workspace >
/transformations/transact/< repository >/< workspace >
For example:
"TMDirectives": {
"description": "This is my description",
"tag": "linux",
},
Alternatively, in the /transformations/transactdata/< repository >/< workspace > endpoint, specify job directives as individual URL arguments.
See Also
Tags maximum time for job, job timeout, job time limit, hanging job, stop job, tag, ttc, ttl