You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Current »

Scheduling is an important part when working with processes. When modelling a process it is possible to create all kinds of tasks such as timer tasks, automatic tasks and tasks that expire after a period of time. It is also possible to model Priority Algorithms which gives you the possibility to present the tasks to the users in the correct order of the urgency of the task. To make sure these functionalities are correctly processed, a scheduling mechanism lies at the heart of the Blueriq Process Engine.

Scheduling

Blueriq uses a  scheduler for evaluating tasks and priorities. The evaluation is executed according to the configuration of the blueriq.timer.interval. This can be set to hourly (default), each minute or never. Each time the interval expires, the process engine starts evaluating all projects present on the Runtime that are using the Process Engine. Per project all cases are retrieved that contain timer tasks, automatic tasks, tasks with a expiration date or Priority Algorithms. When the evaluation leads to a match (meaning when the current time matches the proposed execution time), the task is executed. 

As a result, in a single-node or multi-node (clustered) environment when the interval expires, one of the nodes will start evaluating all projects which in turn will cause a peak load due to the increase CPU and memory consumption of that specific node.  


  • No labels

Didn't find the answer you were looking for? Try the advanced search!