Chat now with support
Chat with Support

Identity Manager 8.0 - Target System Synchronization Reference Guide

Target Synchronization with the Synchronization Editor Basics of Target System Synchronization Setting up Synchronization
Starting the Synchronization Editor Creating a Synchronization Project How to Configure Synchronization
Setting Up Mappings Setting up Synchronization Workflows Connecting Systems Editing the Scope Using Variables and Variable Sets Setting up Start up Configurations Setting up Base Objects
Overview of schema Classes Customizing Synchronization Configuration Checking Synchronization Configuration Consistency Activating the Synchronization Project
Running Synchronization Synchronization Analysis Setting up Synchronization with Default Connectors Updating Existing Synchronization Projects Additional Information for Experts Error Handling Appendix: Example of a Configuration File

How to Delete a Mapping

To delete a mapping

  1. Select the category Mappings.
  2. Select a mapping in the navigation view.
  3. Click in the navigation view.
  4. Confirm the security prompt with Yes.
  5. Save the changes.

Properties of a Mapping

Properties of a Mapping

Enter the following properties for a mapping.

Table 37: Properties of a Mapping
Property Meaning
MappingClosed name Display name for the mapping. The name must be unique withing a synchronization project. Mapping name is used as key. It cannot be changed after saving.
Mapping directionClosed Mapping direction permitted for all property mapping rules.
Both directions Property mapping rules are applied for both synchronization in the direction of the target system and synchronization direction One Identity Manager.
Direction target system Property mapping rules are only used for synchronizing in the direction of the target system.
Direction One Identity Manager Property mapping rules are only used for synchronizing in the direction of the One Identity Manager.
Description Spare text box for additional explanation.
Hierarchy synchronization Specifies whether the mapping is part of the hierarchy. This option is important for optimizing synchronization.

Example:

In Active Directory, all the objects in one container are subordinate. Therefore, the containers map a part of the object hierarchy. Set the option Hierarchy synchronization on the container mapping.

Only suitable for updates Specifies whether schema class objects are never added during synchronization but only updated or deleted.

This option can be used, for example, if not all target system type mandatory properties in One Identity Manager are editable. Example: Active Directory domains.

Can map through multiply referenced objects Specifies whether mapping by multi-reference rule should be used to mapped referenced objects.

This option must be set, if more than one mapping is set up for a schema type and the schema type is used as a member in a multiple reference rule. You must decide which of these mappings is going to used to map schema properties and to identify the system objects, Normally, the schema type's default mapping is used.

The option can only be set on one mapping of each schema type.

If more than one mapping is defined for a schema type and the option is not set on any mapping, a message appears on all property mapping rules that the schema type uses.

Schema classClosed in One Identity Manager One Identity Manager schema class valid for this mapping. Displays all schema classes with a configured mapping, in the menu.
  • Click to edit schema class properties.

Create a new schema class to set up a mapping for another schema type.

  • Click to create a new schema class.
SchemaClosed class in the target system Target system schemaClosed class valid for this mapping. Displays all schema classes with a configured mapping, in the menu.
  • Click to edit schema class properties.

Create a new schema class to set up a mapping for another schema type.

  • Click to create a new schema class.
Detailed information about this topic

Schema Class Properties

Schema Class Properties

Enter the following properties for a schema class:

Table 38: SchemaClosed Class Properties
Property Meaning
Schema typeClosed Select the schema type for which you want to create a schema class.
Display name Schema classClosed display name.
Class name Unique schema class identifier By default, the class name is based on the schema type. The class name must be unique within a schema type.
Description Spare text box for additional explanation.
System filterClosed

FilterClosed that immediately affects the connection system.

Enter the filter in system specific notation, for example, as Where clause for a database system or as LDAP filter for an LDAP system.

NOTE:The system filter does not work, if changes are being provisioned. Therefore, it may not filter more objects than the object selection.
Object selectionClosed

Filter that affects loaded objects.

Condition Formulate a query for loaded objects. Use the wizard for entering filter.
Script You can also store a script which determines system objects. The script must be written in the script language specified in the synchronization project.

Note: Object selection must include the filter criteria of the system filter so that One Identity Manager can also assign schema class object when provisioning.
Related Topics

Edit Schema Properties

Edit Schema Properties

Important: SchemaClosed properties should only be added, modified or deleted by experienced Synchronization EditorClosed 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 propertiesClosed,
    • added by the system connector to extend the target system schema or 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 step 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 project. You can create user specific schema properties. You can use these, for example, to include custom One Identity Manager database schema extensions in the mapping.

Note: Virtual schema properties are only saved in the synchronization project. They do not modify basic One Identity Manager schema or target system schema.

NOTE You can use variables with fixed values in schema properties. In this case, variable names with dollar signed are included. If the schema property value contains a dollar sign, which is not used to label a variable, it must be masked with $.

Example: Enter the value '300 $$' for a variable with the value '300 $$'.

Related Documents