Jan. 28, 2011, 2:32 a.m.
posted by trystan
Creating a Run Profile for Provisioning
You need to synchronize data using the management agent to provision new accounts in the AD connector space. Before you can run the MA, you have to create a run profile that will synchronize the MA's connector space with the metaverse.
There are two types of synchronization run profile: full and delta. A full synchronization will process every object in the connector space. This is obviously necessary when it is the very first synchronization on the data. But in normal daily operations you would only want to perform delta synchronization steps because they only process objects that have changed since the last synchronization.
Dialog showing a Full Synchronization run profile added to the HR Database MA
Full synchronization is also used when you have made a change to management agent configuration, e.g., you have added a new attribute flow. Usually you will want to run the reconfigured MA against all of the objects in the connector space. A delta synchronization would only apply the rule to objects that had changed since the last synchronization.
Recipe 23.13 for setting up the HR Database MA to project objects to the metaverse, Recipe 23.14 for writing a rules extension to provision user objects to the ADMA from objects in the HR Database MA, and Recipe 23.16 for executing the run profile created in this recipe.