Table of Contents

Synchronization - tree nodes

An example of organizational structure synchronization can be found in the admin guide.

Basic algorithm

Situation The account does not exist , it is solely based on a comparison of the existence of accounts on the target system against the existence of IDM accounts.

Finding tree roots

The roots of the tree are searched over the set of all accounts obtained from the target system. The reason why roots are not found using the search method on the end system is that their definition is in some cases too complex (the search criteria in the IC module are inadequate). Such a case is, for example, a situation where roots are all the elements (accounts) whose parent attribute are shown to themselves.

Root search is performed using the Groovy script in the synchronization configuration tree root / tree definition . This script runs over all system elements. If Boolean.TRUE returns, then the element is root. If it returns Boolean.FALSE , it is not the root. The entry of this script is account (IcObject), an object of the element received from the IC module.

If the root trace script is not filled, then every element whose parent attribute is null is considered to be root.

Example of a script addressing the situation described above : 

if(account){
 // Get value from parent attribute
 def parentValue = account.getAttributeByName("parent").getValue();
 // Get value from ID attribute
 def uidValue = account.getAttributeByName("id").getValue();
 
 // Root is account, where is parent value equals with ID (externalId) value.
 if(parentValue != null && parentValue.equals(uidValue)){
     // We need clear value of parent attribute. In IDM has roots always parent = null.
     account.getAttributeByName("id_nadraz_prac_mista").setValues(null);
     return Boolean.TRUE;
 }
}
 
return Boolean.FALSE;

How to synchronize all nodes under one already existing?

Sometime we need synchronize all nodes from the source system under one node wich exists in the IdM.

For definition of that 'Super parent' node we cannot using:

Super parent node can be defined in the transformation searching roots. This script is defined on the sync configuration and we can set ID of super parent node to parent attribute.

Using an ID instead of a node's code is an intent for optimization reasons. When searching for a super parent, first verify that it is a UUID value, which is much faster than searching the node by code. 
if(account){
 // Get value from parent attribute
 def parentValue = account.getAttributeByName("parent").getValue();
 // Get value from ID attribute
 def uidValue = account.getAttributeByName("id").getValue();
 
 // Root is account, where is parent value is null
 if(parentValue == null){
     // Set default node
     account.getAttributeByName("parent").setValues(["00a8aa04-667a-412e-bf3c-d892f2d9ca18"]);
     return Boolean.TRUE;
 }
}
 
return Boolean.FALSE;

All roots in IDM, must have parent attribute = null. In case when is roots define different (for example parent points on itself), then is important do transformation for each root (how looks script above).
Leaving uid attribute and parent reference equal makes the synchronization loop infinitely - take care while setting the root computation script.