Starting synchronization
Synchronization is started using scheduled process plans. A scheduled process plan is added once a start up configuration is assigned to a schedule. Use schedules to define running times for synchronization.
NOTE: Synchronization can only be started if the synchronization project is enabled.
To run synchronization regularly, configure, and activate the a schedule. You can also start synchronization manually if there is no active schedule.
IMPORTANT: As long as a synchronization process is running, you must not start another synchronization process for the same target system. This especially applies, if the same synchronization objects would be processed.
-
If another synchronization process is started with the same start up configuration, the process is stopped and is assigned Frozen status. An error message is written to the One Identity Manager Service log file.
-
Starting another synchronization process with different start up configuration that addresses same target system may lead to synchronization errors or loss of data. Specify One Identity Manager behavior in this case, in the start up configuration.
If you want to specify the order in which target systems are synchronized, use the start up sequence to run synchronization. In a start up sequence, you can combine start up configurations from different synchronization projects and specify the order in which they are run. For more information about start up sequences, see the One Identity Manager Target System Synchronization Reference Guide.
Analyzing synchronization
Synchronization results are summarized in the synchronization log. You can specify the extent of the synchronization log for each system connection individually. One Identity Manager provides several reports in which the synchronization results are organized under different criteria.
To display a synchronization log
-
In the Synchronization Editor, open the synchronization project.
-
Select the Logs category.
-
Click 
in the navigation view toolbar.
Logs for all completed synchronization runs are displayed in the navigation view.
-
Select a log by double-clicking it.
An analysis of the synchronization is shown as a report. You can save the report.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
Post-processing outstanding objects
Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizing. This prevents objects being deleted because of an incorrect data situation or an incorrect synchronization configuration.
Outstanding objects:
-
Cannot be edited in One Identity Manager.
-
Are ignored by subsequent synchronizations.
-
Are ignored by inheritance calculations.
This means, all memberships and assignments remain intact until the outstanding objects have been processed.
Start target system synchronization to do this.
To allow post-processing of outstanding objects
Related topics
Configuring target system synchronization
Create a target system for post-processing outstanding objects. Assign tables you want to be populated by synchronization, to this target system type. Specify the tables for which outstanding objects can be published in the target system during post-processing. Define a process for publishing the objects.
To create a target system type
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
Click 
in the result list.
-
Edit the target system type main data.
- Save the changes.
Enter the following data for a target system type.
Table 16: main data for a target system type
|
Target system type |
Target system type description. |
|
Description |
Text field for additional explanation. |
|
Display name |
Name of the target system type as displayed in One Identity Manager tools. |
|
Cross-boundary inheritance |
Specifies how user accounts are assigned to or inherit groups and system entitlements if they belong to different custom target systems.
-
If the option is set, groups and system entitlements can be assigned to user accounts that belong to the same target system or to different target systems. The target systems must have the same target system type.
For all target systems of a target system type, the settings for the User Account Contains Memberships column(UNSRootB.UserContainsGroupList) must be identical.
-
If the option is not set, groups and system entitlements can only be assigned to the same target system.
NOTE: If the option is not set, the target system type is used to simplify grouping of the target systems. |
|
Show in compliance rule wizard |
Specifies whether the target system type for compliance rule wizard can be selected when rule conditions are being set up. |
|
Text snippet |
Text snippets used for linking text in the compliance rule wizard. |
|
Alternative connectors |
List of connector that can process this type of target system. |
To add tables to target system synchronization
-
In the Manager, select the Data Synchronization > Basic configuration data > Target system types category.
-
In the result list, select the target system type.
-
Select the Assign synchronization tables task.
-
In the pane, assign custom tables to the outstanding objects you want to handle.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the tables that contain the outstanding objects that can be published in the target system and set the Publishable option.
- Save the changes.
NOTE: The connector must have write access to the target system in order to publish outstanding objects that are being post-processed. That means, the Connection is read-only option must not be set for the target system connection.
To publish outstanding objects
-
For each table for which you want to publish outstanding objects, create a process, which is triggered by the event HandleOutstanding and which runs the provisioning of the objects. Use the AdHocProjection process task of the ProjectorComponent process component.
For more information about defining processes, see the One Identity Manager Configuration Guide.
