Identity Manager 9.1.1 - Target System Synchronization Reference Guide

Apart from a connector’s default and additional processingSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. methods, the Synchronization EditorOne Identity Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by 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... can also use customRuns processing logic which would normally be implemented in the object code, such as mutual exclusion of properties. The Customizer contains special methods and has side effects on the table columns. Several customizers can be defined for one table. processing methods. This is done using custom scripts.

To set up and use a custom processing method

1. In the DesignerTool for configuring the One Identity Manager., create a script to make the necessary modifications to the loaded objects.

   Script structure:

   References VI.Projector.Database.dll
   <Tag("Projector")>
   <BaseObjectType("Table")>
   Public Sub CCC_ScriptName(unit As IUnitOfWork, entity As IEntity(), args As VI.Projector.Database.ScriptMethodArgs)
      'Steps to run
      ...
   End Sub

   • <Tag("Projector")>: Labels the script to use as a processing method. This enables the Synchronization Editor to identify the scripts to use as processing methods.

   • <BaseObjectType("Table")>: Defines the type of objects the script will be applied to. Enter the table that contains the objects to be handled.

     If the script can be applied to several object types, define a separate object type for each table.

   • CCC_ScriptName: Script name. In the Synchronization Editor, you can select the script as the processing method under this name. Enter a name that uniquely describes the processing method.

   For more information about creating scripts with the Script Editor, see the One Identity Manager Configuration Guide.

2. Compile the script.

3. In the Synchronization Editor, open the synchronization projectA collection of all data required for synchronizing and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this..

4. Select the Configuration > One Identity Manager connection category and update the One Identity Manager schema.

5. In the Workflows category, select the synchronization workflowSpecifies the order of all the synchronization stepsSpecific rule for processing exactly two schema classes. to be run during synchronization. in which you want to use the new processing method.

6. Find the synchronization step and click Edit.

   The synchronization step must handle the object type defined in the script.

7. On the Processing tab, you can select processing methods under the script name.

References VI.Projector.Database.dll
<Tag("Projector")>
<BaseObjectType("Department")>
<BaseObjectType("Locality")>
Public Sub CCC_Department_RemoveManager(unit As IUnitOfWork, entities As IEntity(), args As VI.Projector.Database.ScriptMethodArgs)
   For Each currEntity As IEntity In entities
      If Not String.IsNullOrEmpty(currEntity.GetValue("UIDArtificial primary key generated by One Identity Manager as soon as the object is inserted into the One Identity Manager database. The UID is a unique value, which does not change even if the properties of an object change. An object is identified by a UID and can be uniquely referenced by it._PersonHead").ToString()) Then
         currEntity.PutValue("UID_PersonHead","")
         unit.Put(currEntity)
      End If 
   Next
End Sub

References VI.Projector.Database.dll
<Tag("Projector")>
<BaseObjectType("ADSAccount")>
Public Sub CCC_SpecialCommit(unit As IUnitOfWork, entities As IEntity(), args As VI.Projector.Database.ScriptMethodArgs)
   For Each entity In entities
      For Each kvp In args.Changes
         entity.PutValue(kvp.Key, kvp.Value)
      Next
      unit.Put(entity)
   Next 
End Sub

Related topics

• Specifying processing methods