Setting Up Job Queue and Scope for an Orchestration (Release 9.2.4.4)

You can specify how you want to process an orchestration: in a single-threaded queue, in a fire-and-forget multithreaded queue, or in the default queue. Using this feature, you can have more control over the runtime processing of orchestrations.

The orchestrations are executed in one of these queues:

Queue Name	Job Queue	Job Queue Scope	Description
JDE_DEFAULT	Default	System	This is the default queue for all the requests entering the system. The orchestration is run synchronously, and therefore the caller receives a response after the orchestration is processed. This queue can run the number of jobs that is specified in MaxConcurrentJobs in the rest.ini file. See Maximum Concurrent Job Limit.
JDE_ASYNC	Fire and Forget	System	This queue is used for asynchronous orchestration requests. For orchestrations sent to this queue, a caller receives an immediate response with a 202-Accepted status and the orchestration then continues to be processed on the server until completion. This queue is also restricted by the MaxConcurrentJobs limit. See Maximum Concurrent Job Limit.
JDE_SINGLE	Single Threaded	System	In this queue, one job is executed at a time based on the First In First Out (FIFO) method. Use this queue if you want the request to be processed in the order that it is received on the server.
JDE_USER_SINGLE	Single Threaded	User	This queue is started only if a user requests to run an orchestration on this queue. It allows requests from each user to be processed on a FIFO basis without any dependency on the completion of the orchestrations being processed on the system in a single threaded queue.
JDE_USER_ASYNC	Fire and Forget	User	This queue is started only if a user requests to run an orchestration on this queue. This queue allows user-specific asynchronous execution, and therefore the processing of these requests is not dependent on the completion of the orchestrations being processed on the system in a fire and forget queue.