SynchronizationThe 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. is started using scheduledTask to run on a cyclical basis. Schedules control regular running of processes, calculation tasks, and other scheduled tasks. You define the start and interval times for the scheduled tasks. The activation time can be given in local time or Universal Time Code. A schedule can be in control of several tasks. process plansContains the basic configuration for automatically running a process.. It is possible to start synchronization manually in the Synchronization EditorOne Identity Manager tool for configuring target system synchronizationPost processing of objects that were marked as outstanding by synchronization... You can simulate synchronization beforehand to estimate synchronization results and discover errors in the synchronization configuration. If synchronization stopped unexpectedly, you must reset the start information to be able to restart synchronization.
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 ServiceSystem service on servers that handle One Identity Manager processes. log file.
-
Ensure that start up configurations that are used in start up sequencesSequence of start up configurations that are automatically run one after the other. By default, a start up sequence is started by a schedule. are not started individually at the same time. Assign start up sequences and start up configurations different schedules.
-
-
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.
-
Use the schedule to ensure that the start up configurations are run in sequence.
-
Group start up configurations with the same start up behavior.
-
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 projectsA collection of all data required for synchronizing and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this. and specify the order in which they are run.