Enter the following properties for a .
Table 37: Properties of a mapping
|
Mapping name |
Display name for the mapping. The name must be unique within a . Mapping name is used as key. It cannot be changed after saving. |
|
|
Mapping direction permitted for all property mapping rules.
|
Both directions |
Property mapping rules are applied to synchronization in both the direction of the target system and One Identity Manager. |
|
|
Property mapping rules are only used for synchronizing in the direction of the target system. |
|
One Identity Manager |
Property mapping rules are only used for synchronizing in the direction of One Identity Manager. | |
|
Description |
Text field 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 Hierarchy synchronization option in 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. |
|
in One Identity Manager |
One Identity Manager schema class valid for this mapping. Displays all schema classes with a configured mapping, in the menu.
Create a new schema class to set up a mapping for another schema type.
|
|
class in the target system |
class valid for this mapping. Displays all schema classes with a configured mapping, in the menu.
Create a new schema class to set up a mapping for another schema type.
|
Detailed information about this topic
Enter the following properties for a schema class:
Table 38: Schema class properties
|
Class types |
Types of schema classes. The class type can only be specified when a new schema class is added.
|
Generic schema class |
without a filter function. |
|
Unique objects |
classes, which filter objects based on unique values from different properties. Only distinct objects are filtered. This prevents the system connector from trying to add objects that already exist. | |
|
|
Select the schema type for which you want to create a schema class. |
|
Display name |
Schema class 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 |
Text field for additional explanation. |
|
Distinction |
Schema properties, which form a unique value when combined.
This only applies to schema classes with the class type "Unique objects"
|
|
CAUTION: The schema class filters objects in an undefined order. Therefore, the result may not be the same each time the filter is used.
Only use this class type for mapping in the direct of One Identity Manager. Otherwise, you cannot guarantee that the same object is updated every time the CSV file is written. | |
|
|
|
|
Filter 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.
If tested against a fixed value that contains at least two dollar characters, the dollar characters must be masked.
NOTE: The system filter does not work, if changes are being provisioned. Therefore, it may not filter more objects than the object selection. |
|
|
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 . |
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
You want to import employee and data from an external personnel management system into One Identity Manager. All the data is provided in a CSV file and transferred to the database through the in the One Identity Manager database.
Table 39: Example of a CSV file
|
1 |
Harris |
Clara |
Marketing |
London |
|
2 |
Bloggs |
Jan |
Marketing |
Berlin |
|
3 |
King |
Jenny |
Marketing |
London |
|
4 |
Basset |
Jenny |
Sales |
Berlin |
|
5 |
King |
Ben |
Sales |
London |
|
6 |
Harris |
Ben |
Sales |
Berlin |
Employee objects, departments, and location will be added to the One Identity Manager database from this data. The CSV exits with an error when a second object with the same name is added because the names of the departments and location are not unique. This can be prevented.
Which objects should be created?
-
Employees with the LastName and FirstName properties. Object can be uniquely identified through these two properties. The file contain six different objects.
-
Departments with the Department and Location properties. The file contains four different objects.
-
Location with the Location property. The file contains two different objects.
For 2. and 3. distinct objects must be supplied Therefore, schema classes with the class type "Unique objects" are created in the mapping.
To set up the mappings
-
Create a mapping for employees.
-
Create a mapping for the department.
-
Create a mapping for the location.
-
Check the filter results in the target system browser.
Table 40: class definition results
|
Employees |
Harris; Clara
Bloggs; Jan
King; Jenny
Basset; Jenny
King; Ben
Harris; Ben |
|
Departments |
Marketing; London
Marketing; Berlin
Sales; London
Sales; Berlin |
|
Locations |
London
Berlin |
Important: properties should only be added, modified, or deleted by experienced 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:
You can use virtual schema properties to represent combinations of schema properties as well as 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 . You can create user specific schema properties. You can use these, for example, to include 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 topics
to edit schema class properties.
to create a new schema class.