Customizing the synchronization configuration
Having used the project wizard to set up a for initial synchronization of a target system, you can use the synchronization project to load target system objects into the One Identity Manager database. These objects can be edited with One Identity Manager tools. You must synchronization configuration in order to compare the database with the target system regularly and to synchronize changes. You can configure a synchronization project such that the necessary information about the direction of synchronization, objects to synchronize, and the property mapping rules to be applied, is made available when synchronization starts.
Edit the target system connection scope and the One Identity Manager database connection to specify which target system and database object are handled by synchronization. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.
Use variables to set up a synchronization project for synchronizing different target systems. For this, connection parameters for logging onto target systems are stored as variables.
Checking the consistency of the synchronization configuration
Before activating a , check the consistency of the synchronization configuration. The consistency check detects configuration errors which would lead to errors during synchronization. The synchronization project cannot be activated until the configuration error are corrected.
The consistency check amongst others whether:
- All mandatory properties are mapped through property mapping rules.
- Dependencies can be automatically resolved in workflows.
- Different schema classes of a schema type are differentiated from one another by filters.
To check consistency the loaded synchronization project
-
Select the General view on the home page.
-
Click on Verify project.
Activating the synchronization project
Once you have collected all the data in the you require for synchronizing from the One Identity Manager database to a target system, you must activate the project. This optimizes the size of the synchronization project. Data is removed which is not required, for example, unused schema types. Synchronization can be run after activating.
Table 67: Meaning of icons on the start page
 |
The synchronization project is activated. |
 |
The synchronization project is deactivated. |
To activate the loaded synchronization project
-
Select the General view on the home page.
-
Click Activate project.
NOTE: This runs a consistency check. If consistency errors occurs, a message appears. You can decide whether the project is activated or not.
Check the errors before you use the synchronization project. In the General view, click Verify project.
An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.
Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the synchronization project
-
In the , open the synchronization project.
-
Select the General view on the home page.
-
Click Deactivate project.
Related topics
Defining start up sequences
In the , you can define across for full synchronization. Start up sequences order start up configurations for different target systems into a sequence. The synchronization projects are run automatically in the given order.
Example
Shortly after synchronizing personnel planning data from an SAP HCM system, always synchronize the SAP R/3, Active Directory, Privileged Account Management, and Google Workspace systems. Personnel planning data should be synchronized daily.
To do this, the start up configuration for the SAP HCM system and the start up configuration for all other target system are group together in a start up sequence. The start up configuration for SAP HCM is positioned at the top. A schedule is assigned that starts the start up sequence daily.
Specify whether each start up configuration is allowed to start after the previous synchronization has completed or at the same time as the previous start up configuration.
Detailed information about this topic
