March 25, 2011, 9:29 p.m.
posted by trystan
Configuring a Run Profile to Load the telephoneNumber from AD
You need to get the AD telephoneNumber attribute into MIIS and synchronize it.
Dialog showing Delta Import and Delta Synchronization run profile added to the existing ADMA run profiles
Because a previous import step was completed in an earlier recipe, you can use the combined Delta Import and Delta Synchronization step so that MIIS imports and synchronizes changes that have occurred in AD since the last time it connected. You can use this run profile from now on since it keeps track of changes internally using the DirSync control.
The Delta Import (Stage Only) step in the AD Export run profile (the confirming import from Recipe 23.17) also imports changes, which suggests you could simply configure a delta synchronization run profile to process those changes in this recipe. Such an approach will work. The decision on which approach to use will depend on the service-level agreements you make. If it is two hours since the last AD import, your service-level agreement might force you to import and synchronize the changes that have occurred over the last two hours and feed them to the HR Database; however, you may only need to export to AD every four hours. If you only rely on the changes detected in the confirming import step, you will only be able to update the HR Database with changes every four hours.
Recipes 23.17 and 23.24 for how to use the run profile configured in this recipe