Page Comparison

The Queue Processor manages the process flow executions, e.g., managing the allowed number of process flows at a time. This reduces the chances of resource contention when there are multiple, simultaneous execution processes.

The Queue processor 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 
  
  

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:

1. High
2. Medium
3. 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. 

Viewing information about process flows

Anchor
Viewing process flows Viewing process flows

The Queue Processor page displays the number of Running, Ready, and /or Queued Queued process flows with their details (Process Flow Name, Job ID, Time, Priority, and Status). You may easily filter huge records using the Quick and Advance filters (displayed at the top right of the page).

The Queue Processor does not display process flows with following conditions, because the process flow with these conditions will bypass the queue processor:

• Process Flow executed with an immediate priority
• Process Flow executed by the Web Service provider
• Process Flow executed with the Event that has Trigger in Sequence as checked
• Process Flow executed as Child Flow

Image Removed

 Follow the steps below to go to the page:

1. Click Configure.
2. Select Developer Studio from the left pane and then click Proceed.
3. Go to Administer tab and click Maintenance.
4. Select Queue Processor to open the page.
   
   Image Added

Setting up the number of concurrent process flows execution

Anchor
Setting up the value for concurrent execution Setting up the value for concurrent 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:

1. Click Configure icon.
2. Select Developer Studio from the left pane and then click Proceed.
3. Go to Administer tab and click Setup drop-down menu.
4. Select Application Settings and then Update System Properties.
5. Expand Load Management and then Cluster and Queue Processor Configuration.

6. Enter a number in the Value field for the property abpm.queue.processor.concurrent.processes.
   
   Image Added
   
   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.

   
   

7. Click Save.
   
   

See also

Cleaning up Queue Processor

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

...