立即与支持人员聊天
与支持团队交流

Identity Manager 9.2.1 - Configuration Guide

About this guide One Identity Manager software architecture Customizing the One Identity Manager default configuration Customizing the One Identity Manager base configuration One Identity Manager schema basics
Overview of the One Identity Manager schema Table types and default columns in the One Identity Manager data model Notes on editing table definitions and column definitions Table definitions Column definitions Table relations Dynamic foreign key Supporting file groups
Editing the user interface
Object definitions for the user interface User interface navigation Forms for the user interface Statistics in 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 Using predefined database queries
Localization in One Identity Manager Process orchestration in One Identity Manager
Mapping processes in One Identity Manager Setting up Job servers
The One Identity Manager Service functionality Tracking changes with process monitoring Conditional compilation using preprocessor conditions Scripts in One Identity Manager
Visual Basic .NET scripts usage Notes on message output Notes on using date values Tips for using PowerShell scripts Using dollar ($) notation Using base objects Calling functions Pre-scripts for use in processes and process steps Using session services Using #LD notation Script library Support for processing scripts in the Script Editor Creating and editing scripts in the Script Editor Copying scripts in the Script Editor Testing scripts in the Script Editor Testing script compilation in the Script Editor Overriding scripts Permissions for running scripts Editing and testing script code with the System Debugger Extended debugging in the Object Browser
One Identity Manager query language Reports in One Identity Manager Adding custom tables or columns to the One Identity Manager schema Web service integration One Identity Manager as SCIM 2.0 service provider Processing DBQueue tasks One Identity Manager Service configuration files

Processing DBQueue Processor tasks

The central dispatcher finds entries in the DBQueue (DialogDBQueue table) and moves the tasks into the QBMDBQueueCurrent table with the assignment tasks per slot.

Example of entries in the DialogDBQueue and QBMDBQueueCurrent tables
Table 187: Entries in the DialogDBQueue (extract) table
Task name Object

OrgRoot

A

OrgRoot

B

ADSAccountInADSGroup

X

ADSAccountInADSGroup

Y

ADSAccountInADSGroup

Z

Table 188: Entries in the QBMDBQueueCurrent (extract) table
Slot number Task name Object

001

OrgRoot

A

001

OrgRoot

B

002

ADSAccountInADSGroup

X

002

ADSAccountInADSGroup

Y

002

ADSAccountInADSGroup

Z

Each process processes tasks queued for its own slot in the QBMDBQueueCurrent table. Subsequent tasks resulting from processing are queued in the DialogDBQueue table.

If a process has processed its tasks and no other tasks are pending, the slot number in the QBMDBQueueCurrent table is set to 0 by the process itself. The entry initially remains in the QBMDBQueueCurrent table but is no longer taken into account (because slot 0 is not active).

All entries with the slot number 0 are deleted from the QBMDBQueueCurrent table at regular intervals.

Table 189: Meaning of slot numbers in the QBMDBQueueCurrent table
Slot number Meaning

001 - n

Number of slot to be processed by the task.

0

State after the task is completed correctly.

-1

An error occurred during task processing or processing was deferred, for example, because synchronization is running. The central dispatcher re-enables the task.

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

-2

An error occurred during task processing or processing was deferred, for example, because of blocking. The central dispatcher re-enables the task.

-3

An error occurred during task processing or processing was deferred, for example, because there are still entries in the Job queue. The central dispatcher re-enables the task.

Using the DBQueue buffer

To prevent blockages when processing DBQueue tasks by lengthy actions, for example, synchronization, a DBQueue buffer (QBMDBQueuePond table) is used. Synchronization initially writes DBQueue Processor tasks to the QBMDBQueuePond table. After synchronization is complete, the task are moved from the QBMDBQueuePond table to the DialogDBQueue table.

If a lengthy task does not queue anymore entries in the DBQueue tasks because, for example, synchronization did not end correctly, the remaining entries in the QBMDBQueuePond table are moved to the .DialogDBQueue table. The time period for this is defined in the QBM | DBQueue | BufferTimeout configuration parameter (default: 120 minutes). The transfer is carried out by the daily maintenance tasks.

How the central dispatcher communicates with individual slots

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

Table 190: Meaning of status in the QBMDBQueueSlot table
Status Meaning

0

No activity required. Initial state (set by initializing) 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 the QBMDBQueueCurrent table. 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 if the process timed out or errors occurred.

Stop behavior by maximum timeout

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

Related topics

Example of communication during processing

The following example show the entries in the QBMDBQueueSlot table during 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 ready for operation. 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 DialogDBQueue table in the QBMDBQueueCurrent table with the slot number. The status of each slots is updated once the QBMDBQueueCurrent table has taken over.

    Slot number Status Task name

    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 the processing and sets slot number in the DialogDBQueueCurrent table to 0. The process changes the status of its slots to operational.

    Slot number Status Task name

    001

    2

     

One Identity Manager Service configuration files

One Identity Manager Service is configured using a configuration file. The configuration file has to be in the same directory as the viNetworkService.exe. Two configuration files are supported:

Detailed information about this topic
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级