Identity Manager 9.2 - Target System Synchronization Reference Guide

Workflow display name.

Select the direction in which synchronization should take place.

• Defined when run: The synchronization direction is defined in the start up configuration.

  For more information, see Start up configuration properties.

• Target systemAn instance of a target system in which the identities managed by One 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 have access to network resourcesEquipment that is necessary for an identity's work efficiency, for example, mobile phones, desks, company cars, or keys. Resources can be any equipment that is not system entitlements, devices, or software.. Example: An Active Directory domain X for target system type "Active Directory", a directory Y for target system type "LDAP", a client Z for target system type "SAP R/3".: One Identity Manager is the primary system for synchronization.

• One Identity Manager The target system is the primary system for synchronization.

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?.

• Defined when run: The required behavior is defined in the start up configuration.

• Use revision filter: Only modified objects are synchronized.

• Do not use revision filter: All objects are synchronized.

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.

• Continue on error: Processing continues with the next object. Errors are logged.

  This option should be used for productive systems.

• Break on error: Synchronization is stopped.

  This option should only be used to find errors, for example in going live processes.

Specify how dependencies between synchronization step are resolved.

For more information, see How does dependency resolution work?.

• Automatic: Dependencies are resolved automatically.

  One Identity Manager determines the sequence of the synchronization steps automatically. It takes into account dependencies between schema classes to synchronize and schema properties.

• Manual: Dependencies are not resolved.

  The synchronization steps are processed sequentially in the order listed in the workflow view. Dependencies between the schema classes and the schema properties must be taken into account when compiling the synchronization steps.

Specifies the strategy for checking conflicts when new objects are added to the target system.

• Optimistic: Drops additional verification. For example, select this value if conflicts are unlikely because data in the target system is changed only by One Identity Manager.

• Pessimistic: Additional verification is carried out to identify conflicts. For example, select this value if conflicts are likely because data in the target system is changed at the same time by other systems.