Explanation behind how the Provisioning Server stores associations between objects internally in its Provisioning Repository.
Every object in the Provisioning Repository has a UUID stored in the eTID attribute. In some cases these eTID values are used as references to link objects together. As objects are deleted and re-created new UUID values are generated and stored in the eTID attributes. Moving data from one installation to another is problematic since the eTID values may not be correct.
All versions of Identity Suite (Identity Manager)
Non-Inclusion Object Associations
In some cases relationships between objects are stored directly on the object (i.e. done without inclusion objects). The list of such associations are:
Inclusion Object Associations
But in other cases the relationship between objects are stored in a third object called an Inclusion object. In this case the Inclusion Object will link a SuperiorClass object to a SubordinateClass object. The Inclusion object will store the SuperiorClass object's eTID in an attribute called eTPID and will store the SubordinateClass object's eTID in an attribute called eTCID. The Inclusion Object will be named in a format of [email protected]_Value and will have an eTID of its own. The list of such associations are:
In the Provisioning Repository the Inclusions container branch stores those inclusions in a DIT structure as shown below: