Synchronization process
The UMRA Service executes the synchronization process once a day, preferably during the night. The synchronization process takes the data from both systems, the phonebook database and Active Directory, compares the data, and according to a number of synchronization rules, executes a number of update actions. This principle applies to both this example scenario and more complex environments.
The following table lists the synchronization rules that apply:
| Condition
|
Synchronization action
|
Employee of phonebook database exists in Active Directory, phone numbers match.
|
None.
|
Employee of phonebook database exists in Active Directory, phone numbers differ.
|
Update phone number in Active Directory.
|
Employee of phonebook database does not exist in Active Directory.
|
Create user account in Active Directory and set phone number.
|
User account in Active Directory not found in phonebook database.
|
Delete user account from Active Directory.
|
Table 3: Synchronization rules
It is important to define all the synchronization rules before the UMRA application is implemented. In most cases, the synchronization actions correspond with UMRA projects. The UMRA framework application applies the synchronization rules.
| 
