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

Concurrency behavior of synchronization objects

It is possible that synchronizationClosed objects have been changed at the same time in both connected systemsClosed or are being processed automatically that processing is not yet complete. These objects are excluded by default to avoid data conflict. If possible, synchronization of these objects is repeated by the next synchronization run. Excluded objects are recorded in the synchronization log.

By default, synchronization objects are checked for possible concurrency conflicts before processing starts. However, if provisioning processes are created afterward, conflicts may not be detected. Therefore, the start up configurations, it is possible to set when and how often the data should be checked for possible conflicts.

To protect synchronization performance as much as possible, the information about the object processing status is cached. By default, the data remains in the cache for 60 seconds. You can modify the retention time.

To set when to check for concurrency conflicts

  1. In the Synchronization EditorClosed, enable expert mode.

  2. Edit the start up configuration properties.

  3. Select the Advanced tab.

  4. In the Collision detection field, specify when to check for concurrency conflicts.

    • Before processing (default): Checks synchronization objects for possible collision conflicts immediate after they are loaded.

      Advantage: Detected objects are not processed.

      Disadvantage: Conflicts are not detected if synchronization objects are then processed by other system processes during synchronization. Conflicts can still occur due to the time delay before the objects are saved.

    • Before committing: Synchronization objects are checked for possible concurrency conflicts before committing.

      Advantage: Conflicts are detected immediately before committing. This increases the detection rate.

      Disadvantage: Objects are processed unnecessarily if their processing conflicts could already have been detected after loading.

    • Multiple: Synchronization objects are checked for possible concurrency conflicts before processing starts and before saving.

      Advantage: High detection rate.

      Disadvantage: Multiple checks can reduce synchronization performance.

  5. In the Cached data retention time field, specify how long the data remains in the cache. This is given in seconds.

  6. Click OK.
  7. Disable expert mode

In rare cases, it could still be necessary to synchronize some properties of skipped objects immediately, to transfer safety-critical changes, for example. You can configure the behavior you require in the property mapping rules.

To force synchronization of individual schema properties

  1. Edit the property mapping rule for this schema property.

  2. In the Concurrence behavior field, set the value Apply rule.

    This applies the property mapping rule, overwriting any data changes in the connected system.

    IMPORTANT:

    • Only select this option in exceptional cases. Afterward, check the data modifications that might be overwritten by this.

    • The setting only takes effect if Pre-processing is selected for collision detection in the start up configuration. Only then can collisions can be detected before mapping takes place.

  3. Click OK.
Related topics

Setting up synchronization

Use the Synchronization EditorClosed to configure connections for different target system in One Identity Manager. The components of a synchronization configuration are used for both synchronization and for provisioning and synchronizing single objects. Synchronization can be configured so it can be used for connecting different target systems of the same target system type.

Table 28: Synchronization configuration components
Term Described in
base object Setting up base objects
Mapping Setting up mappings
Start configurationClosed Setting up start up configurations
Synchronization projectClosed Creating a synchronization project
Variable setClosed Using variables and variable sets
WorkflowClosed Setting up synchronization workflows

Starting the Synchronization Editor

There are different ways to start the Synchronization EditorClosed.

  • From the Windows start menu using the One Identity > One Identity Manager > Configuration > Synchronization Editor entry.

  • From the Launchpad.

  • In the Manager

  • From the command line.

Related topics

Creating a synchronization project

A synchronization projectClosed collects all the information required for synchronizing the One IdentityClosed Manager database with a target system. Connection data for target systems, schema types and properties, mapping, and synchronization workflowsClosed all belong to this.

Prerequisites

  • A synchronization serverClosed is set up and declared in the One Identity Manager database.

There is a wizard to assist you with setting up a synchronization project. This wizard takes you through all the steps you need to set up initial synchronization with a target system. The project wizard takes over the following tasks:

  • Connecting to the Target System
  • Connecting to the One Identity Manager database
  • Defining synchronization behavior

    The synchronization behavior can be configured based on target system-specific project templatesClosed. For certain target systems, One Identity Manager supplies a default project template. The project wizard copies the project template data. This can be modified with the project wizard to suit the new synchronization project. Just one synchronization project can be created per target system and default project template used.

After saving the synchronization project, you can alter the synchronization configuration.

To complete synchronization configuration

  1. Check the mappings, workflows, start up configuration, and system connection that the wizard has added.
  2. Assign a scheduleClosed to the start up configuration.
  3. If you want to use the synchronization project to synchronize different target systems, specify variables, and variable sets.
  4. Activate the synchronization project. The synchronization cannot be started until these are resolved.

NOTE: The current synchronization project is closed when you open another synchronization project.

Detailed information about this topic
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating