Identity Manager 9.1 - Target System Synchronization Reference Guide

Important: SchemaData model of a connected systemSystem the objects and their properties are transferred to during 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.. 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.. The schema describes all the main data from the connected system. see target system schema; see One Identity Manager schema; see connector schema; see extended schema properties should only be added, modified, or deleted by experienced Synchronization EditorOne Identity Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by synchronization.. users and system administrators.

All schema properties of a schema class are displayed in the mapping editor's schema view. There are two different sorts of schema property:

• Schema properties of schema types from the target system and One Identity Manager schema.

• Virtual schema propertiesSchema classSubset of a schema type. The result list of a schema type is filtered by defined criteria. Example: Active Directory contacts are Active Directory user accounts with the property objectclass = "CONTACT". property added by the system connector or the user.,

  • Added by the system connector to extend the target system schema or the One Identity Manager schema

  • Added by the user to extend the connector schema or the One Identity Manager schema

You can use virtual schema properties to represent combinations of schema properties as well as processing stepRepresents one processing task in a process. results as schema properties. They are used amongst other things to map lists of members to One Identity Manager database auxiliary tables. Some virtual schema properties are added by the system connector when you set up the synchronization projectA collection of all data required for synchronizing and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this.. You can create user specific schema properties. You can use these, for example, to include customRuns processing logic which would normally be implemented in the object code, such as mutual exclusion of properties. The Customizer contains special methods and has side effects on the table columns. Several customizers can be defined for one table. One Identity Manager database schema extensions in the mapping.

Related topics

• Schema editor