Having used the project wizard to set up a synchronization projectA collection of all data required for synchronizingThe processSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this. 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 customizeRuns processing logic which would normally be implemented in the object code, such as mutual exclusion of properties. The Customizer contains special methods and has side effects on the table columns. Several customizers can be defined for one table. 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.