Purpose
If there are processes with many system steps (system activities, decision steps, parallelization start and parallelization end) in a JobRouter installation and if some of these system steps have long execution times, the processing time of single instances can reach an unacceptable level. This is especially the case when there are many active instances in the system at the same time. To counter this, JobRouter offers the possibility to separate the processing of the steps into multiple processing pools, allowing a parallel processing of the steps. This shortens the processing time of individual instances.
How it works
The current supply of steps to be processed or send of processes are processed sequentially by the JobFlowExecute and JobFlowSend modules (components of JobServer) by default.
When activating the pooling, a definable number of processing pools is used for processing steps. A fixed processing pool can be assigned to individual process steps. This can also be set in a routing rule for the subsequent step. Alternatively, you can assign the pool dynamically instead of statically by using special JobRouter variables in routing rules.
Please note: .NET system actions (JobPDF, JobFerd, JobArchive's Export PDF and Check archive functions and JobMind's Create PDF file function) do not support pooling . These steps must always be configured for Pool 1, otherwise they will not be run.
