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.
|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.
To verify the script code's syntax
Compiler errors are shown immediately and written to in the SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. Editor's error log.
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.
To debug a script
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 EditorOne Identity Manager tool for configuring target system synchronization. until synchronization is complete. To be able to continue working with the SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. Editor during synchronization, run synchronization from the synchronization server.
To start synchronization manually
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_SynchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database..
To create a downstream process for synchronization
This makes a new element for the process and opens it in the Process Editor.
|Table:||Table which supplies the synchronization base object, for example ADSDomain.|
For more information, see the One Identity Manager Configuration Guide.
When a synchronization step is processed in a process plan, synchronization objects are determined and processed as follows:
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.
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.
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.|
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.