Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the One Identity Manager Extending the Launchpad Task Definitions for the User Interface Applications for Configuring the User Interface Icons and Images for Configuring the User Interface Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Reactivating DBQueue Processor Tasks

Reactivating DBQueue Processor Tasks

If a task has to be deferred, for example due to an error or if synchronization is running, the process sets the slot number in the table QBMDBQueueCurrent to "-1" on its own. These tasks are re-enabled if there are no more tasks in the DBQueue. At the very latest, these deferred tasks are reinstated into the DBQueue the next time the central dispatcher runs. This means deferred tasks are re-enabled at the latest once the maximum runtime has elapsed.

NOTE: Deferring DBQueue tasks is recorded in the system log.

Related Topics

Bulk Processing in DBQueue Processor

Bulk Processing in DBQueue Processor

Table 369: Configuration Parameter for Bulk Processing in the DBQueue Processor
Configuration parameter Meaning

The configuration parameter species how the length of the DBQueue Processor run. The default value is 90 seconds.

Some DBQueue Processor procedures are marked for bulk processing to reduce the total time required for processing DBQueue tasks. If a lot of entries are marked for bulk processing in the DBQueue, the DBQueue Processor switches from single to bulk processing.

There is a mechanism implemented that is used to decide whether switching to bulk processing as opposed to single processing would result in time savings. To do this, 25 single task processes are run and the processing time is recorded. All other entries for the task are processed in bulk and the minimum and maximum load time required for advantageous bulk processing is defined. A self optimizing calculation procedure updates the load times. As a result of this method, the DBQueue Processor needs to "kick in" after initial schema installation or after system changes, such as increased database memory. You can specify how long the DBQueue Processor runtime interval should be with the configuration parameter "Common\DBQueue\DefaultRuntime". The default value is 90 seconds. This corresponds to the time period that achieves the best load for the calculation procedure.

How the Central Dispatcher Communicates with Individual Slots

The table QBMDBQueueSlot is responsible for communication of the central dispatcher with individual slots. The maximum number of slots available is determined during DBQueue Processor initialization. One entry per slot is created in the table QBMDBQueueSlot. The table contains information about each slot and its status as well as currently running tasks.

Table 370: Meaning of Status in Table QBMDBQueueSlot
Status Meaning
0 No activity required. Initial state (through initialization) or end state (set by process).
1 The process is triggered to prepared central temporary tables, for example.
2 Ready for operation. The process has started but the currently no tasks exist. This is the state in which tasks can be queued.
3 Transfer to table QBMDBQueueCurrent. The process has received tasks for processing and needs to begin.
4 The process has recognized the tasks and added them.
5 The process is handling the tasks.
-1 The process was prompted to quit. Stop behavior by maximum timeout or abort on process error.
Related Topics

Communication during Processing

The following example show the entries in the table QBMDBQueueSlotduring processing.

  • Slot initialization
    Slot number Status Task name
    001 0  
  • Starts the process using the central dispatcher.
    Slot number Status Task name
    001 1  
  • The process is operational. Preparations, for example, for temporary tables, are complete. The slot status is regularly tested.
    Slot number Status Task name
    001 2  
  • The central dispatcher distributes tasks. The central dispatcher checks slots for readiness and enters the task from table DialogDBQueue in the table QBMDBQueueCurrent with the slot number. The status of each slots is updated once the table QBMDBQueueCurrent has taken over.
    Slot number Status Name of task
    001 3 OrgRoot
  • The process recognizes a task on the basis of the status, starts processing and updates its slots' status.
    Slot number Status Task name
    001 4 OrgRoot
  • The process has completed processing and set the slot number in the table DialogDBQueueCurrent to "0". The process changes the status of its slots to operational.
    Slot number Status Name of task
    001 2  
Stop behavior by maximum timeout

Once the maximum runtime has expired, the tasks of slots in the table QBMDBQueueCurrent currently in use are still processed. No new tasks are added from the table QBMDBQueue. All slots with a slot status of "2" are set to "-1" in the table QBMDBQueueSlot. This prompts the processes to finish and stop themselves. The central dispatcher checks whether all processes have completed and have stopped.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating