立即与支持人员聊天
与支持团队交流

Identity Manager 9.2.1 - 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

Error log

In expert mode, you can show the error log. In the error log, you can view all the errors that have occurred since the program started up. The error log is reinitialized when the Synchronization EditorClosed restarts.

To display items from error log

  • Enable expert mode.

    By default, the error log is displayed in the lower section of the Synchronization Editor.

For more information about functions in the error log, see the One Identity Manager Process Monitoring and Troubleshooting Guide.

Ignoring data error in synchronization

By default, objects with incorrect data are not synchronizedClosed. For example, a user account is not loaded in the One IdentityClosed Manager database if, in the user account table, the formatting script of a column contains an email address detects invalid data. These objects can be synchronized once the data has been corrected. In certain situations, however, it might be necessary to synchronize objects like these and ignore the data properties that have errors. This synchronization behavior can be configured in One Identity Manager.

To ignoring data errors during synchronization in One Identity Manager

  1. In the Synchronization EditorClosed, open the synchronization projectClosed.

  2. Select the Configuration > One Identity Manager connection category.

  3. In the General view, click Edit connection.

    This starts the system connection wizard.

  4. On the Additional options page, enable Try to ignore data errors.

    This option is only effective if Continue on error is set in the synchronization workflowClosed.

    Default columns, such as primary keys, UIDClosed columns, or mandatory input columns cannot be ignored.

  5. Save the changes.

IMPORTANT: If this option is set, One Identity Manager tries to ignore commit errors that could be related to data errors in a single column. This causes the data changed in the affected column to be discarded and the object is subsequently saved again. This effects performance and leads to loss of data.

Only set this option in the exceptional circumstance of not being able to correct the data before synchronization.

Troubleshooting errors when connecting target systems

Incorrect mapping of object hierarchy after synchronization

If objects, which mapClosed a hierarchy, are synchronizedClosed the following errors can occur:

  • Objects are mapped to the wrong position in the hierarchy.
  • Objects are not loaded.
Probable reason

The parent objects could not be referenced. If the parent object is a mandatory property, the child objects cannot be saved.

By default, objects are processed in blocks of 1024 each during synchronization. Objects are loaded in random order. Therefore, a child object might be processed before its parent object has been loaded. Thus the parent object cannot be assigned.

Example: Importing cost center with the CSV connector

Cost centers make up an object hierarchy. The respective parent object is assigned through the UIDClosed_ParentProfitCenter column. The complete hierarchy path is kept in the FullPath column.

During synchronization, a cost center might be loaded before its parent cost center. Therefore, the parent cost center cannot be referenced. Because the parent cost center is not a mandatory property, the object is loaded but appears at a strange place in the hierarchy. A different full name is formatted in the database as given in the CSV file. If the full name is the only matching criteria for identifying the object the objects cannot be assigned uniquely.

Solution

NOTE:

  • The solution approach only applies for resolving references of the same object type.
  • Synchronization can get slower if the amount of data is large.
  • The solution described is one way to prevent the error. There may be other solutions depending on the actual data situation.

To prevent the error

  • Label the column containing the hierarchy path as the sort criteria in the target system schema and set the partition size to "1".

    The objects are sorted by hierarchy path during synchronization and loaded one by one in the database in this order. This ensures that the parent object is already loaded and can be referenced.

  • Ensure manual dependency resolution is set in the synchronization workflowClosed.

    This can be necessary in certain situations, for example, when synchronizing cost centers. In this case, the full name is the only matching criteria. In the One IdentityClosed Manager database this is put together from the cost center name (AccountNumber column) and the full name of the parent object. In the case of automated dependency resolution, the parent objects are not assigned until the second synchronization step. Therefore, no parent objects are assigned after the first synchronization step. The full name is only formatted from the cost center name. All child objects therefore, have another full name in the database as in the target system. In the second synchronization step, there objects can no longer be identified. Thus parent objects cannot be assigned by it.

    In the case of manual dependency resolution, all property mapping rules are run in one synchronization step. The parent object assigned immediately. This way, the templateClosed finds the correct full names.

To mark a column as sort criterion

  1. Edit the target system schema in the Synchronization EditorClosed.
    1. Select the Configuration > Target systemClosed category.

    2. Click Edit connection.

      This starts the system connection wizard.

  2. Select the page where you can edit the Hierarchical sort order option.

    NOTE: The system connection wizards of the various target systems display different pages. For example, in the system connection wizard for CSV systems, select the Display information page.
  3. Select the column containing the hierarchy path.
  4. Enable the Hierarchical sort order option.
  5. Save the changes.

To adjust the partition size

  1. Enable expert mode in the Synchronization Editor.

    ClosedEnable expert mode

  2. Edit the start up configuration properties.

    ClosedEdit the start up configuration

  3. Select the Extended tab.

  4. In the Partition size field, enter the value 1.

    For more information, see Extended properties for start up configuration.

  5. Click OK.

  6. Disable expert mode

To set manual dependency resolution

  1. Edit the workflow properties.
    1. Select the Workflows category.
    2. Select the workflow in the navigation view.
    3. Select the General view in the WorkflowClosed Editor and click Edit.
  2. Select the value "Manual" in the Dependency resolution field.
  3. Click OK.
  4. Save the changes.

  5. Activate the synchronization projectClosed.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级