You can create/edit/delete dedicated queues for partners, templates, transactions, and other activities. Based on creation or deletion, a new runtime pods are created or deletedservice is created. This service has its own runtime pods (HPA - horizontal pod autoscaling).
Write steps for creating/editing/deleting queues from Queue Management.
The Queue Processor in Adeptia Connect manages and regulates the execution of process flows. It regulates the execution by:
- Limiting the number (defined by the user) of process flows for concurrent execution. Refer to the section Setting up the number of concurrent process flow execution.
- Executing the process flows based on the priority information associated with each process flow.
- Keeping the user informed about how many process flows are in what state (Running, Ready, Queued, and Corrupt). Refer to the section Viewing information about process flows.
The Queue Processor executes process flows based on the priority information associated with each process flow. You have the following priority levels available to set for a process flow:
- Real Time Processing
- High
- Medium
- Low
| Info |
|---|
Any process flow with 'Real Time Processing' priority bypasses the Queue Processor and is executed immediately. The following types of process flows also qualify to be executed immediately bypassing the Queue Processor:
|
Process flows with High, Medium, and Low priority are executed by the Queue Processor. The order of execution of process flows based on the priority is as follows:
- High
- Medium
- Low
Process flows with same priority level are executed on first-in, first-out (FIFO) basis.
Refer to the section Defining Priorities for Process Flows to know how to set the priority. Adeptia recommends you to set the priority for your process flows in such a way that none of them remains in the queue for a long time. This is also to mitigate any risk of low or medium priority process flows not being executed at all.
| Info |
|---|
| The priority levels 'Immediate' and 'Normal' for process flows defined in the previous version of Connect will be considered as 'Real Time Processing' and 'Low' priorities respectively. |
The Queue Processor page displays the number of Running, Ready, Queued, and Corrupt process flows with their details (Process Flow Name, Job ID, Time, Priority, and Status). Follow the steps below to go to the page:
| Info |
|---|
| Only an Admin user can access Queue Processor page. |
To search for Process Flows for a specific time period, go to advanced search.
Click the arrow in the search box.
To know how to clean up the queued processes in Queue Processor, click /wiki/spaces/AC40/pages/3181249.
Setting up the number of concurrent process flows execution
| Anchor | ||||
|---|---|---|---|---|
|
You can limit the the number of process flows for concurrent execution by updating the system property abpm.queue.processor.concurrent.processes in Connect. Perform the following steps to set the value:
This defines the number of process flows for concurrent execution.
| Info |
|---|
After you update and save this property, you need to restart the server to see the change in action. |
See also
| Panel | ||||
|---|---|---|---|---|
| ||||
What's newBest practicesTraining guides/wiki/spaces/AC40/pages/3180519/wiki/spaces/AC40/pages/3181640Adeptia security report |