Chat now with support
Chat with Support

Identity Manager 9.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 Configuring the synchronization log 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 Copying synchronization projects
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

How to edit schema classes

NOTE:
  • You can only edit customizedClosed schema classes.
  • Modifications to schema classes in use can cause errors!

To edit a schema class

  1. Edit the system connection properties.

    For more information, see How to edit system connection properties.

  2. Open the SchemaClosed classes view.
  3. Double-click on a schema class in the schema overview.
  4. Edit the schema class properties.

    For more information, see Schema class properties.

  5. Save the changes.

How to delete schema classes

NOTE: CustomClosed schema classes, which are not in use, can be deleted.

To delete a schema class

  1. Remove the schema class from all mappingsClosed in which they are used.

    For more information, see Editing mappings.

  2. Edit the system connection properties.

    For more information, see How to edit system connection properties.

  3. Open the SchemaClosed classes view.
  4. Select the schema class in the schema overview and click in the toolbar.

    If the schema class is still in use, the location is displayed.

  5. Confirm the security prompt with Yes.
TIP: Compress the schema to remove unnecessary schema classes from the target schema or the One IdentityClosed Manager schema from the synchronization projectClosed. For more information, see How to remove unnecessary project data.

Customizing the synchronization configuration

Having used the project wizard to set up a synchronization projectClosed for initial synchronization of a target system, you can use the synchronization project to load target system objects into the One IdentityClosed Manager database. These objects can be edited with One Identity Manager tools. You must customizeClosed synchronization configuration in order to compare the database with the target system regularly and to synchronize changes. You can configure a synchronization project such that the necessary information about the direction of synchronization, objects to synchronize, and the property mapping rules to be applied, is made available when synchronization starts.

Edit the target system connection scope and the One Identity Manager database connection to specify which target system and database object are handled by synchronization. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.

  • You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.

    Use variables to set up a synchronization project for synchronizing different target systems. For this, connection parameters for logging onto target systems are stored as variables.

  • Checking the consistency of the synchronization configuration

    Before activating a synchronization projectClosed, check the consistency of the synchronization configuration. The consistency check detects configuration errors which would lead to errors during synchronization. The synchronization project cannot be activated until the configuration error are corrected.

    The consistency check amongst others whether:

    • All mandatory properties are mapped through property mapping rules.
    • Dependencies can be automatically resolved in workflows.
    • Different schema classes of a schema type are differentiated from one another by filters.

    To check consistency the loaded synchronization project

    1. Select the General view on the home page.

    2. Click on Verify project.

    Related Documents

    The document was helpful.

    Select Rating

    I easily found the information I needed.

    Select Rating