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 or Queued). 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

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 associated with Web Services
Process flows with an Event that has Trigger in Sequence as checked
Child process flows (except for Spawn action with 'Wait For Child as False')

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.

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.

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.

Viewing information about process flows

The Queue Processor page displays the number of Running, Ready, and Queued process flows with their details (Process Flow Name, Job ID, Time, Priority, and Status). Follow the steps below to go to the page:

Click Configure.
Select Developer Studio from the left pane and then click Proceed.
Go to Administer tab and click Maintenance.
Select Queue Processor to open the page.

Setting up the number of concurrent process flows execution

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:

Click Configure icon.
Select Developer Studio from the left pane and then click Proceed.
Go to Administer tab and click Setup drop-down menu.
Select Application Settings and then Update System Properties.
Expand Load Management and then Cluster and Queue Processor Configuration.
Enter a number in the Value field for the property abpm.queue.processor.concurrent.processes.

This defines the number of process flows for concurrent execution.

After you update and save this property, you need to restart the server to see the change in action.
Click Save.

At any point you may choose to clean-up the Ready and Queued processes. Perform the following steps to clean-up the queued processes:

On the Administer tab, click Maintenance.
From the Maintenance list, click Queue Processor.
Click Cleanup Now.
Confirm your action.

This will pause the kernel, remove all the ready and queued process flows, and then resume the Kernel. You may also view KernelApplication.log and WebrunnerApplication.log files for clean up details. These files are located at the following path:

ServerKernel > logs > applicationlog

Browser not supported