It is possible that synchronizationThe processSequence 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. 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. objects have been changed at the same time in both connected systemsSystem 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. or are being processed automatically that processing is not yet complete. These objects are excluded by default to avoid data conflict. If possible, synchronization of these objects is repeated by the next synchronization run. Excluded objects are recorded in the synchronization log.

By default, synchronization objects are checked for possible concurrency conflicts before processing starts. However, if provisioning processes are created afterward, conflicts may not be detected. Therefore, the start up configurations, it is possible to set when and how often the data should be checked for possible conflicts.

To protect synchronization performance as much as possible, the information about the object processing status is cached. By default, the data remains in the cache for 60 seconds. You can modify the retention time.

To set when to check for concurrency conflicts

1. In the Synchronization EditorOne IdentityAn identity usually represents a real person. In addition, identities that do not represent real people, such as machine identities or service identities, can be mapped in One Identity Manager. (see also virtual identity; see also main identity/subidentity) Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by synchronization.., enable expert mode.

   Enable expert mode

   1. In the Synchronization Editor, select the Database > Settings menu.

   2. Enable Enable expert mode.

   3. Click OK.

2. Edit the start up configuration properties.

   Edit the start up configuration

   1. In the Synchronization Editor, select the Configuration > Start up configurations category.

   2. Select a start up configuration in the document view and click Edit.

3. Select the Advanced tab.

4. In the Collision detection field, specify when to check for concurrency conflicts.

   • Before processing (default): Checks synchronization objects for possible collision conflicts immediate after they are loaded.

     Advantage: Detected objects are not processed.

     Disadvantage: Conflicts are not detected if synchronization objects are then processed by other system processes during synchronization. Conflicts can still occur due to the time delay before the objects are saved.

   • Before committing: Synchronization objects are checked for possible concurrency conflicts before committing.

     Advantage: Conflicts are detected immediately before committing. This increases the detection rate.

     Disadvantage: Objects are processed unnecessarily if their processing conflicts could already have been detected after loading.

   • Multiple: Synchronization objects are checked for possible concurrency conflicts before processing starts and before saving.

     Advantage: High detection rate.

     Disadvantage: Multiple checks can reduce synchronization performance.

5. In the Cached data retention time field, specify how long the data remains in the cache. This is given in seconds.

6. Click OK.

7. Disable expert mode

In rare cases, it could still be necessary to synchronize some properties of skipped objects immediately, to transfer safety-critical changes, for example. You can configure the behavior you require in the property mapping rules.

To force synchronization of individual schema properties

1. Edit the property mapping rule for this schema property.

   Edit property mapping rules

   1. In the Synchronization Editor, select the Mappings category.

   2. Select a mapping in the navigation view.

   3. Double-click on the property mapping rule you want to edit in the rule view.

2. In the Concurrence behavior field, set the value Apply rule.

   This applies the property mapping rule, overwriting any data changes in the connected system.

   IMPORTANT:

   • Only select this option in exceptional cases. Afterward, check the data modifications that might be overwritten by this.

   • The setting only takes effect if Pre-processing is selected for collision detection in the start up configuration. Only then can collisions can be detected before mapping takes place.

3. Click OK.

Related topics

• Extended properties for start up configuration
• Object matching rule details

• Editing property mapping rules