Each mapping rule applies to a scope of objects. By default, this scope includes all objects that belong to the object types specified in the mapping rule. If necessary, you can narrow the scope specified for a particular mapping rule or you can revert to the default scope.
To change the scope of a mapping rule
- Go to the mapping pair that includes the mapping rule whose scope you want to change:
- In the Synchronization Service Administration Console, open the Mapping tab.
- Click the name of the appropriate connection.
- Click the appropriate mapping pair entry.
- Locate the mapping rule whose scope you want to change. Use the following elements provided for each mapping rule entry:
- Mapping scope for system 1. Shows the mapping rule scope applicable to the data system shown on the left part of the mapping pair entry.
- Mapping scope for system 2. Shows the mapping rule scope applicable to the data system shown on the right part of the mapping pair entry.
These elements can take one of the following values:
- Default. Indicates that the mapping rule applies to all objects of the specified type.
- Custom. Indicates that the mapping rule scope is narrowed down and only applies to some objects of the specified type.
- Change the mapping rule scope as necessary:
- Click the value displayed next to Mapping scope for system 1 or Mapping scope for system 2, and then specify the scope you want to use.
- When you are finished, click OK.
Once you have created mapping rules for a mapping pair, you need to run the map operation in order to apply these rules and map objects that belong to the mapping pair. There are two methods to run the map operation: you can manually run the map operation once or you can create a recurring schedule to automatically run the map operation on a regular basis.
The latter method is recommended when you want to use Synchronization Service to synchronize passwords from an Active Directory domain to other connected systems.
Running mapping rules on a recurring schedule allows you to properly map newly-created Active Directory user objects to their counterparts in the connected systems where you automatically synchronize passwords with the Active Directory domain. If you do not run mapping rules on a regular basis, some passwords may become out of sync because of the changes that inevitably occur to your environment.
For example, new user objects are created, some user objects are deleted, but Synchronization Service cannot detect these changes and synchronize passwords for the newly-created users before you apply the mapping rules. In this scenario, the best way to ensure Synchronization Service synchronizes all passwords is to apply your mapping rules on a regular basis. You can accomplish this task by creating a recurring schedule for applying your mapping rules.
To run the map operation once
- In the Synchronization Service Administration Console, open the Mapping tab.
- Click the name of the connection for which you want to run the map operation.
- Click the mapping pair for which you want to run the map operation.
- Click Map now.
- In the dialog box that opens, click one of the following:
- Full Map. With this option, Synchronization Service retrieves the data required to map objects from the connected data systems.
- Quick Map. With this option, Synchronization Service first tries to map objects by using the data that is available in the local cache. If the local cache is missing or cannot be used to map objects, then Synchronization Service retrieves the required data from the connected data systems.
Wait for the map operation to complete.
After the map operation completes, the Synchronization Service Administration Console displays a report that provides information about the objects that participated in the map operation. At this stage, the application does not map the objects. To map the objects, you need to commit the map operation result.
You can click the number that is provided next to an object category name in the report to view the details of objects that belong to that category.
- Review the report about the objects that participated in the map operation, and then click Commit to map the objects.
To automatically run the map operation on a recurring schedule
- In the Synchronization Service Administration Console, open the Mapping tab.
- Click the name of the connection for which you want to create a recurring mapping schedule.
- Click the mapping pair for which you want to run the map operation on a recurring schedule.
- Click Schedule mapping.
- In the dialog box that opens, select the Schedule the task to run check box, and then specify a schedule for the map operation.
It is recommended to schedule the map operation to run once in every 6 hours.
- If several Synchronization Service instances are installed in your environment, under Run the task on, select the computer that hosts the instance you want to use for running the map operation.
- Click OK to activate the schedule.
The results of a scheduled map operation always apply automatically, you do not need to commit the changes.
When performing a scheduled map operation, Synchronization Service always retrieves the required data from the connected data systems and never uses the data available in the local cache.
You can unmap the objects that were mapped earlier.
To unmap objects
- In the Synchronization Service Administration Console, open the Mapping tab.
- Click the name of the connection for which you want to unmap objects.
- Click the mapping pair that specifies the objects types you want to unmap.
- Click Unmap now and wait until the unmap operation completes.
After the unmap operation completes, the Synchronization Service Administration Console displays a report which provides information about the objects that participated in the unmap operation. At this stage, the application does not unmap the objects. To unmap them, you need to commit the result of the unmap operation.
You can click the number provided next to an object category name in the report to view the details of objects that belong to that category.
- Review the report on the objects that participated in the unmap operation, and then click Commit to unmap the objects.
