When you start synchronization, all synchronization objects are loaded. Some of these objects have not be modified since the last synchronization and, therefore, must not be processed. Synchronization is accelerated by only loading those object pairs that have changed since the last synchronization. One Identity Manager uses revision filtering to accelerate synchronization.
One Identity Manager supports revision filtering. The date of the last target system object change (XDateUpdated) is used as revision counter. Each synchronization saves the last date is was run as a revision in the One Identity Manager database (DPRRevisionStore table, Value column). This value is used as a comparison for revision filtering when the same workflow is synchronized the next time. When this workflow is synchronized the next time, the target system objects' change date is compared with the revision saved in the One Identity Manager database. Only those objects that have been changed since this date are loaded from the target system.
Synchronization is even faster if the change information on the schema type also takes deleted objects into account. If a schema type's objects were neither added, changed nor deleted, the synchronization step can be skipped. Objects must not be loaded for comparison. To take advantage of this optimization, the revision data for tables must be saved in both of the connected databases.
To use optimized revision filtering
-
Start the Designer and connect to the central database.
-
Set the Common | TableRevision configuration parameter.
- Save the changes.
-
Connect the Designer to the work database.
-
Set the Common | TableRevision configuration parameter.
- Save the changes.
Now each time a table changes, the table's revision date updates. This information is stored in the QBMTableRevision table, RevisionDate column. In this way, One Identity Manager identifies whether objects in a table have been added, changed, or deleted.
Synchronization with revision filtering compares a table's revision date against the revision saved in the One Identity Manager database. If the revision date is older, no objects have been changed in this table since the previous synchronization. Therefore, synchronization does not carry out this step for the affected schema type. If the revision date is newer, synchronization carries out this step and the changed objects are determined as described above.
The revision is found at start of synchronization. Objects modified by synchronization are loaded and checked by the next synchronization. This means that the second synchronization after initial synchronization is not significantly faster.
Revision filtering can be applied to workflows and start up configuration.
To permit revision filtering on a workflow
-
In the Synchronization Editor, open the synchronization project.
- Edit the workflow properties. Select the Use revision filter item from Revision filtering menu.
To permit revision filtering for a start up configuration
-
In the Synchronization Editor, open the synchronization project.
- Edit the start up configuration properties. Select the Use revision filter item from the Revision filtering menu.
NOTE: If the Common | TableRevision is not set, all revision data in the QBMTableRevision table is deleted.
For more information about revision filtering, see the One Identity Manager Target System Synchronization Reference Guide.
in the navigation view toolbar.