Chatee ahora con Soporte
Chat con el soporte

Identity Manager 9.1.2 - Target System Synchronization Reference Guide

Target system synchronization with the Synchronization Editor Working with the Synchronization Editor Basics of target system synchronization Setting up synchronization
Starting the Synchronization Editor Creating a synchronization project Configuring 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 the synchronization configuration Checking the consistency of the synchronization configuration Activating the synchronization project Defining start up sequences
Running synchronization Synchronization analysis Setting up synchronization with default connectors Updating existing synchronization projects Script library for synchronization projects Additional information for experts Troubleshooting errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples

Use cases for class types

You want to import employee and organizationClosed 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 CSV connectorClosed in the One Identity Manager database.

Table 38: Example of a CSV file

 

Lastname

FirstName

Department

Location

1

Name1

User1

Marketing

London

2

Name2

User2

Marketing

Berlin

3

Name3

User3

Marketing

London

4

Name4

User4

Sales

Berlin

5

Name5

User5

Sales

London

6

Name6

User6

Sales

Berlin

Employee objects, departments, and location will be added to the One Identity Manager database from this data. The CSV synchronizationClosed 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?

  1. Employees with the LastName and FirstName properties. Object can be uniquely identified through these two properties. The file contain six different objects.

  2. Departments with the Department and Location properties. The file contains four different objects.

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

  1. Create a mapping for employees.

    • Create a new schema class in the target system.

      Select the Generic schema class class type and enter the mandatory data.

  2. Create a mapping for the department.

    • Create a new schema class in the target system.

      1. Select the Unique objects class type and enter the mandatory data.

      2. Enable Department and Location on the Distinction tab.

        The schema class filters exactly those objects from the CSV file that are unique identifiable by the combination of Department and Location.

  3. Create a mapping for the location.

    • Create a new schema class in the target system.

      1. Select the Unique objects class type and enter the mandatory data.

      2. Enable Location on the Distinction tab.

        The schema class filters exactly those objects from the CSV file that are unique identifiable by the Location property.

  4. Check the filter results in the target system browser.

    Table 39: SchemaClosed class definition results

    Schema classClosed

    Filtered Objects

    Employees

    Name1; User1

    Name2; User2

    Name3; User3

    Name4; User4

    Name5; User5

    Name6; User6

    Departments

    Marketing; London

    Marketing; Berlin

    Sales; London

    Sales; Berlin

    Locations

    London

    Berlin

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 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 stepClosed 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 projectClosed. You can create user specific schema properties. You can use these, for example, to include customClosed 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

How to add virtual schema properties

Important: SchemaClosed properties should only be added, modified, or deleted by experienced Synchronization EditorClosed users and system administrators.

To add a virtual schema property

  1. Select the Mappings category.
  2. Select a mapping in the navigation view.
  3. Click in the schema view menu bar.
  4. Enter details for the virtual schema property.
  5. Click OK.

    The icon marks customClosed virtual schema properties in the schema view.

How to display and edit schema properties

Important: SchemaClosed properties should only be added, modified, or deleted by experienced Synchronization EditorClosed users and system administrators.

To edit a virtual schema property

NOTE: Only user specific virtual schema properties can be edited.
  1. Select the Mappings category.
  2. Select a mapping in the navigation view.
  3. Double-click on the schema property in the schema view.
  4. Edit the schema property details.
  5. Click OK.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación