Task Queue Service
The task queue service plays a central role in a load-balancing environment.
Applications that run on the servers in this environment can place tasks in a task queue. Other applications, which are responsible for processing these tasks, read them and carry them out. These applications can run on the same server or on a separate server.
An instance of the service runs on each server in a load-balancing environment. The configuration is globally valid.
Parameters of the Task Queue Service
| Parameters | Required | Description |
|---|---|---|
|
Root Directory |
No |
Path to the file system where the tasks are stored. Only relevant for file system persistence (see Persistence Layer). The path /etc/taskqueue is predefined. |
|
Persistence Layer |
No |
Selection of persistence layer. A file system is not transaction-safe as a persistence layer, and should not be used in distributed systems. RAM memory is only suitable to be used as a persistence layer for test systems. For productive systems, choose database persistence. |
|
Size Limit for Task History |
No |
Maximum number of tasks to be stored in a history after execution. The history allows programmers to check whether tasks in the task queue have been executed. If the specified value is exceeded, old entries are lost. This prevents the system from slowing down and the database growing out of control. Default setting: 5000 |
The task queue service is preconfigured and activated in the KM standard configuration. Normally, you do not need to change its configuration.
Do not deactivate the service, since it is used by the index management service.
To check the configuration of the task queue service, choose Content Management → Global Services → Task Queue Service.