Page History
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 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 model Priority Algorithms which presents the tasks to the users in the correct order of the urgency of the task. To make these functionalities are correctly processed, a scheduling mechanism lies at the heart of the Blueriq Process Engine.
We distinguish two types of schedulers namely Basic and Advanced. Choosing the right scheduler that suits your needs depends on the business demands and the number of cases and tasks being processed. The paragraphs below describe the workings of both schedulers and the considerations when choosing the appropriate one.
Basic scheduling (default)
By default Blueriq uses the basic scheduler for handling tasks and
Advanced scheduling
| Note |
|---|
When upgrading from the basic to the advanced scheduler, please refer to the Scheduler migration guide |
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.
...
Overview
Content Tools