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.
| Button | Description |
|---|---|
 |
Opens advanced edit mode. |
 Compile |
Checks the script's syntax.
|
 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. |
Script was compiled without errors.
Script contains syntax errors.Compile
To verify the script code's syntax
- Open the script in the Synchronization Editor
One Identity Manager tool for configuring target system synchronization..
- Click Compile.
Compiler errors are shown immediately and written to in the Synchronization
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:
- Schema
- Script variabled
- Data operations for system connections through the native database connector.
- Schema
To debug a script
- Open the script in the Synchronization Editor.
- Click Debug.
- Confirm the prompt with OK.
- Start debugging in the Visual Studio project.
- If necessary, correct the script code in the Synchronization Editor's default mode.
- 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 Editor
To start synchronization manually
- Select the category Configuration | Start up configurations.
- Select a start up configuration in the document view and click Execute.
- 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_Synchronization
To create a downstream process for synchronization
- Select the category Process Orchestration in the Designer.
- 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.
- Edit at least the following process properties.
Table: Table which supplies the synchronization base object, for example ADSDomain. Event: PostSync - Create the required process steps.
For more information, see the One Identity Manager Configuration Guide.
- 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:
- 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.
- 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.
- 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. - 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.
