Customizing the configuration for DBQueue Processor task processing
The default configuration settings for processing DBQueue Processor tasks are configured for normal operation and usually do not need to be modified. If required, you can control processing using different configuration settings.
-
QBM | DBQueue | MaxSlotsPerTask: The configuration parameter defines the maximum number of slots that a DBQueue Processor task can use. The default value is 16.
For example, if 64 slots are available, this DBQueue Processor task can only use up to 16 slots. The remaining slots are available for processing other DBQueue Processor tasks.
-
QBM | DBQueue | CountSlotsMax: Maximum number of slots to be used. Use this configuration parameter to reduce the number of slots if required. Values lower than 5 are not permitted.
Exception: Enter a value of 0 for using the maximum number of slots available based on the hardware configuration.
-
QBM | DBQueue | KeepAlive: Maximum runtime of the central dispatcher. Tasks on slots currently in use are still processed when the timeout expires. Then the slot are stopped and the central dispatcher restarts.
Default value is 20 minutes. The lowest permitted value for runtime is 5 minutes; the maximum permitted value is 720 minutes.
Bulk processing in the DBQueue Processor
Some DBQueue Processor procedures are marked for bulk processing to reduce the total time required for processing DBQueue Processor tasks. If there are a lot of entries marked like this in the DBQueue, the DBQueue Processor switches from single to bulk processing.
-
You can use the QBM | DBQueue | DefaultRuntime configuration parameter to specify the length of the DBQueue Processor run. The default value is 90 seconds. This is the optimal time period for achieving a good workload for bulk processing.
-
Use the QBM | DBQueue | MaxBulkFactor configuration parameter to specify the maximum number of tasks that can be processed in parallel. This is the upper limit for bulk processing. The default value is 15000 entries.
Limits can be defined ( procedure) to protect against overloading in the event of excessive data volumes.
-
The QBM | DBQueue | ChangeLimitDefault configuration parameter defines the limit for modifications (add, change, or delete) within a single task. The value is used if no separate limit is defined for a DBQueue Processor task. The default value is 3000 entries.
Database Agent Service functionality
The Database Agent Service carries out the following tasks:
-
Controls processing and distribution of the DBQueue tasks to the individual slots (central dispatcher))
-
Checks and starts scheduled tasks
-
Removes already processed tasks
-
Starts maintenance work
-
Populates and updates the Job queue overview
-
Archives or deletes handled processes from the Job queue
-
Archives or deletes process handling logs
To process DBQueue Processor tasks, ensure that the Database Agent Service is installed and configured. The Database Agent Service is deployed via the One Identity Manager Service plugin. The plugin should be configured on the Job server that performs the Update server server function. An administrative user must be used for the database connection in the Job provider.
Alternatively, the Database Agent Service can be run from the DatabaseAgentServiceCmd.exe command line program.
For more information, see the One Identity Manager Installation Guide and the One Identity Manager Operational Guide.
NOTE: If the Database Agent Service is not working, a message is displayed in the status bar in all the administration tools. To see this message, users must have at least the configuration user access level.
Influencing processing sequence of DBQueue Processor tasks
When the Database Agent Service starts, a graph is created from DBQueue Processor task data (QBMDBQueueTask table) and the predecessor/successor relationships of the tasks (QBMDBQueueTaskDepend table). This derives the processing sequence. The processing sequence is determined by the dependencies in the graph and the path length of a task to the graph's root node.
You have the option of prioritizing individual tasks using the QBMDBQueueTask.CustomWeight column, which allows you to control the processing sequence. Possible incorrect weightings are logged in the Database Agent Service NLog logfile.
To change the weighting of a DBQueue Processor task
-
In the Designer, select the One Identity Manager Schema > DBQueue Processor tasks category.
-
Select the DBQueue Processor task.
-
In the Properties view, change the Weighting value.
The value must be between 0 and 1. The higher the value, the higher the priority for processing the task. The default value is 0.
-
Select the Database > Save to database and click Save.
