MappingsList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. group together the rules used to map the schema properties of two connected systemsSystem the objects and their properties are transferred to during synchronizationThe processSequence of process steps for mapping 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.. For this, a schema class is created for every schema type which requires mapping. A schema class limits the result list of a schema type through defined filer criteria. A mapping maps schema properties from exactly one target system schema class to the schema properties of exactly one schema class in the One Identity Manager schema. A schema class without a filter condition represents the schema type.
Property mapping rules describe how the target system schema properties are mapped in the One Identity Manager schema. Object matching rules assign schema properties through which system objects can be uniquely identified. For example, Active Directory groups can be uniquely identified by the schema properties DistinguishedName and ObjectGUID.
You specify in the mapping, which mapping directionDirection in which schema property data is transferred. The mapping direction determines the primary system for the schema property. is permitted for the connected schema classes. Furthermore, you can also specify the permitted mapping direction for individual property mapping rules.
Default mappings for target system synchronizationPost processing of objects that were marked as outstanding by synchronization. are added if 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. was created with a default project templateTemplateRule for mapping object properties. Templates can be applied to an object and also have a cross-object effect. used by the project wizard to create a preconfigured synchronization project.. You can edit or delete these mappings or create new mappings. If the synchronization project was created without a project template, no mappings are set up.
The schema property mapping is edited with the mapping editor.