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

Verifying Scripts

Verifying Scripts

You can apply scripts at various points in the synchronization project; for example, when defining the schema properties or when you define data operations for system connection through the native database connector. You can enter scripts in C# or Visual Basic .NET depending on script's language, which was specified for the synchronization project.

Compiling and debugging are available to you for trouble shooting script code.

Table 73: Edit Box Buttons
Button Description
Opens advanced edit mode.
Compile Checks the script's syntax.

Script was compiled without errors.

Script contains syntax errors.

Debug Export the current script code to a Visual Studio project.

This button is only available in the dialog box "Edit schema properties..." and in the system connection wizard for the native database connector.

Compile

To verify the script code's syntax

  1. Open the script in the Synchronization EditorClosed.
  2. Click Compile.

Compiler errors are shown immediately and written to in the SynchronizationClosed Editor's error log.

Debug

The script code is export to a Visual Studio project for debugging. Once the project is run, the Synchronization Editor starts in debug mode and the script is tested.

Prerequisites
  • Visual Studio is installed on the workstation on which the Synchronization Editor is running.
  • All changes to the synchronization project are saved.
  • The debugger can be used in scripts that are used in:
    • SchemaClosed properties
    • Script variabled
    • Data operations for system connections through the native database connector.

To debug a script

  1. Open the script in the Synchronization Editor.
  2. Click Debug.
  3. Confirm the prompt with OK.
  4. Start debugging in the Visual Studio project.
  5. If necessary, correct the script code in the Synchronization Editor's default mode.
  6. Save the changes.
Related Topics

Starting Synchronization

You can also start synchronization manually by either running it on your workstation or from the synchronization server. If you run synchronization from your workstation, you cannot work with the Synchronization EditorClosed until synchronization is complete. To be able to continue working with the SynchronizationClosed Editor during synchronization, run synchronization from the synchronization server.

To start synchronization manually

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

Defining Downstream Processes

Certain actions must be executed in the One Identity Manager database after synchronization has finished. For this, you can define additional processes in the tables, which return base objects. These additional processes are executed through the "PostSync" event, which is triggered in the process DPR_DPRProjectionStartInfo_Run_SynchronizationClosed.

To create a downstream process for synchronization

  1. Select the category Process Orchestration in the Designer.
  2. Start the Process Editor using the task Create a new process.

    This makes a new element for the process and opens it in the Process Editor.

  1. Edit at least the following process properties.
    Table: Table which supplies the synchronization base object, for example ADSDomain.
    Event: PostSync
  2. Create the required process steps.

    For more information, see the One Identity Manager Configuration Guide.

  3. Save the changes.
Example
  • There is a process ADS_ADSDomain_SearchAndCreate_FullSync set in the table ADSDomain to automatically assign employees to Active Directory user accounts. The process is triggered by the event "PostSync".
  • If group memberships cannot be resolved when an Active Directory domain is synchronized, the One Identity Manager finds the Active Directory SIDs of the user accounts. For this, there is the process ADS_ADSDomain_PostSync set on the table ADSDomain. The process is triggered by the event "PostSync".

Processing Synchronization Steps

When a synchronization step is processed in a process plan, synchronization objects are determined and processed as follows:

  1. Load slim list of object to be synchronized

    Objects to be synchronized are loaded according to the object matching rules from the target system and the One Identity Manager database. Only key properties, the revision property (if exists) and individually specified schema properties in the system connector are loaded in this case.

    TIP: Systems, which only have a few schema properties can have all their schema properties pre-loaded into this list. This can accelerate synchronization.

    You can configure the appropriate behavior in the start up configuration when in expert mode. Modify the reload threshold to do this For more information, see Extended Properties for Start Up Configuration.

  2. Use revision filter

    Modified object pairs are filtered, if revision filtering is permitted and the target system supports revision filtering The revision filter is applied to slim list, which means objects that are already loaded.

  3. Load lists of object pairs with all schema properties

    One Identity Manager loads list of object and object pairs to be synchronized with all mapped schema properties. The lists are loaded in partitions with a fixed size. Once a partition (for example 1000 object pairs) has been loaded, they are processed asynchronously and at the same time the next partition is being loaded. Therefore, a maximum of two partitions are located in main memory at any time.

    TIP: You can specify the partition size in the start up configuration in expert mode. For more information, see Extended Properties for Start Up Configuration.
  4. Use mapping

    The moment a partition (for example, 1000 list pairs) have been loaded, the mapping is used for all objects and object pairs. Processing methods are subsequently executed according to the given condition.

Detailed information about this topic
Related Documents