Search

Page tree
Skip to end of metadata
Go to start of metadata

By default, Queue Processor is enabled. To disable it, change the value of the property abpm.queue.processor.enable from yes to no. To know how to change the property, refer to Updating Adeptia Suite Properties.

When Queue Processor is enabled, you need to specify the following properties:

abpm.queue.processor.Concurrent.processes 

Concurrent Process Size is the maximum number of process flows, queue processor allows to be executed simultaneously. However, this property is bypassed in case of a process flow associated with web service provider.

abpm.queue.processor.reload.factor

Reload Factor specifies the threshold of a number of process flows that can be queued into Queue Processor memory. Once the number of process flows queued into Queue Processor memory becomes less than Reload Factor, the Queue Processor looks for other process flows from the database.
 
abpm.queue.processor.reload.count 

Reload Count specifies the number of process flow that is loaded in the Queue Process memory when the number of process flows queued in the Queue Processor memory becomes less than the Reload Factor.  

By default, Concurrent Processes Size is set to 5 and Reload Factor is set to 20. To change the Concurrent Processes Size and Reload Factor, refer to Updating Adeptia Suite Properties.

If the expected files to be processed are relatively small (say < 2MB) then set the Queue Processor concurrency to 50 if 12GB assigned to Kernel Heap size.

Typical formula for concurrent value = Kernel memory / (expected file size * 100) = 12GB / (2MB x 100) = 12GB / 200MB = 60.

Therefore, a value of 50 is relatively safe.

This assumes mapping rules that are of medium complexity with no external lookups, and more. If the mapping rules are complex then half the concurrent value.

  • No labels