Having used the Synchronization Editor to set up a synchronization project for initial synchronization of a Unix host, you can use the synchronization project to load Unix objects into the One Identity Manager database. If you manage user accounts and their authorizations with One Identity Manager, changes are provisioned in the Unix-based target system.
You must customize the synchronization configuration in order to compare the database with the Unix-based target system regularly and to synchronize changes.
- To use One Identity Manager as the master system during synchronization, create a workflow with synchronization in the direction of the Target system.
- 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 methods, for example.
- Use variables to set up a synchronization project for synchronizing different hosts. Store a connection parameter as a variable for logging onto the hosts.
- To specify which Unix objects and database objects are included in synchronization, edit the scope of the target system connection and the One Identity Manager database connection. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
- Update the schema in the synchronization project if the One Identity Manager schema or target system schema has changed. Then you can add the changes to the mapping.
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.
Ensure that start up configurations that are used in start up sequences 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.
For more detailed information about configuring synchronization, see the One Identity Manager Target System Synchronization Reference Guide.