Enter the following general properties for a synchronization stepSpecific rule for processingSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. exactly two schema classes..
Property | Meaning | ||||||
---|---|---|---|---|---|---|---|
Name | An arbitrary name for the synchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. step. The name must be unique within a synchronization workflowSpecifies the order of all the synchronization steps to be run during synchronization.. | ||||||
Mapping | Select the mapping to be processed by the synchronization step. | ||||||
Synchronization in directionDirection in which synchronization is run. The primary system is defined by the direction of synchronization. | Select the direction in which synchronization should take place.
| ||||||
Revision filteringMethod for accelerating synchronization. Only objects that have changed since the last synchronization are fully loaded and synchronized. RevisionHighest value of the revision countersInformation about the last change to a system object. The revision counter is used to determine the objects that have changed since the last synchronization. of all a schema type's objects that are synchronized during a synchronization run. This value is stored in the DPRRevisionStore table, in the Value column. It is used as a comparison value for revision filtering when the same workflow is synchronized the next time. filtering can only be used if the target system supports it. | The revision filtering can be used to limit synchronization to just the objects that have been modified since the last synchronization.
For more information, see How does revision filtering work?.
| ||||||
Exception handling |
Specify whether synchronization should be continued if an error occurs during processing of synchronization objects (adding, deleting, updating, and reloading objects). Object processing is continued using the next object; the error is logged. To optimize error localization, you can stop synchronization if an error occurs during the processing of synchronization objects. In this case, no further synchronization objects are processed. NOTE: This property does not affect configuration, network, or general synchronization errors (for example, if it is not possible to resolve a reference). The effectiveness of this property depends on the actual error, error position, the target system, and the implementation of the target system connectors.
| ||||||
Data import |
Set this option if the synchronization step synchronizes a secondary system and changes are immediately provisioned in the primary system. Do not set this option if the synchronization step synchronizes primarySystem that has data sovereignty during synchronization. The primary system is specified by the direction of synchronization. Example of synchronization direction "Target system" (One Identity Manager -> Active Directory): Here Active Directory is the connected systemSystem the objects and their properties are transferred to during synchronization. The connected system is defined by the synchronization direction. Example of synchronization direction "Target system" (One Identity Manager -> Active Directory): Here Active Directory is the connected system and One Identity Manager is the primary system of synchronization. and One Identity Manager is the primary system of synchronization.ry system. For more information, see Synchronizing user data with different systems. | ||||||
Description | Text field for additional explanation. | ||||||
Disabled | If this option is set, the synchronization step is not synchronized. |