Chat now with support
Chat with Support

Identity Manager 8.0 - Target System Synchronization Reference Guide

Target Synchronization with the Synchronization Editor Basics of Target System Synchronization Setting up Synchronization
Starting the Synchronization Editor Creating a Synchronization Project How to Configure 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 Synchronization Configuration Checking Synchronization Configuration Consistency Activating the Synchronization Project
Running Synchronization Synchronization Analysis Setting up Synchronization with Default Connectors Updating Existing Synchronization Projects Additional Information for Experts Error Handling Appendix: Example of a Configuration File

Simulating Synchronization

You can simulate synchronization before using a start up configuration to execute it. The simulation allows you to estimate the result of synchronization. This means you can, for example, recognize potential errors in the synchronization configuration. Reactions from the connected system and it consequences cannot be incorporated because simulation cannot modify data.

Simulation executes the following actions:

  • Creates execution plan
  • Connects One Identity Manager database and target system
  • Loads system objects
  • Logs write operations but do not execute

Dependent object and schema properties cannot be resolved if the objects already exist in the connected system. Unresolvable dependencies are logged.

IMPORTANT: Simulation changes data in neither One Identity Manager nor the target system. However, large amounts of data are read from both systems. This can affect system performance and processing.

To start simulation

  1. Select the category Configuration | Start up configurations.
  2. Select a start up configuration in the document view and click Simulate....
  3. Specify missing properties.
  4. Click Start simulation.
  5. Confirm the security prompt with Yes.

    A report is displayed after simulation has completed. You can save this report.

Handling Unexpected Termination of Synchronization

Handling Unexpected Termination of Synchronization

If synchronization is executed with a start up configuration, some One Identity Manager processes are stopped. It is not possible to start this start up configuration again. The One Identity Manager saves start information of the current synchronization in the database. This start information is reset once synchronization is completely normally.

If synchronization was terminated unexpectedly, for example, a server was no available, you must manually reset the start information. You can only restart synchronization after this.

IMPORTANT: Start information may not be reset if synchronization is running normally.

Before you reset the start information, ensure that synchronization has really been aborted.

To reset synchronization start information

  1. Select the category Configuration | Start up configurations.
  2. Select a start up configuration in the document view and click Reset.
  3. Confirm the security prompt with Yes.

    The status "Broken" is entered in the synchronization log.

NOTE: If necessary, start information can be reset automatically. To do this, customize the process DPR_DPRProjectionStartInfo_Run_SynchronizationClosed. Changes to the process applies to all the target system connected to the One Identity Manager database when synchronized.

Resetting Revisions

SynchronizationClosed with revision filtering involves finding object pairs where one has newer change information than the last time it was synchronized. It may also be necessary to process those objects during synchronization, whose change information has not be updated since the last synchronization. This might be required if changes to data were made without the change information for the object being updated, for example. It is possible that data in one of the connected systems was restored from a backup. This means the change information for the objects is now older than before the last synchronization. Such objects are not processed by synchronization with revision filtering.

One Identity Manager provides an option to reset revision numbers in a start up configuration. The revision can be reset for one schema type or for all of a schema's types. The next time synchronization is run with this start up configuration, all affected objects are seen as changed.

To reset the revision number

  1. Select the category Configuration | Start up configurationss.
  2. Select a start up configuration in the document view and click Revisions...

    This opens the dialog box Manage revisions..., which displays all the schema types with their respective revision numbers. SchemaClosed types without a revision number, are not displayed.

  3. Select the schema whose revision number you want to reset.

    - OR -

    Select the schema type from the target system or One Identity Manager schema, whose revision you want to reset.

  4. Click Reset.
  5. Select another schema type if required.
  6. Click Apply.
  7. Confirm the security prompt with Yes.

    The revisions of the selected schema types are deleted from the start up configuration.

Related Topics

Synchronization Analysis

Synchronization Analysis

SynchronizationClosed results are summarized in the synchronization log. You can specify the extent of the synchronization log for each system connection individually. One Identity Manager provides several reports in which the synchronization results are organized under different criteria.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating