SynchronizationThe process 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 scheduled process plans. A scheduled process plan is added once a start up configuration is assigned to a schedule. Use schedules to define executing times for synchronization.
|
NOTES: Synchronization can only be started if the synchronization project is enabled. |
|
IMPORTANT: As long as synchronization is running, you must not start another synchronization for the same target system. This applies especially, if the same synchronization objects would be processed. If another synchronization is started with another start up configuration, that addresses same target system, it may lead to synchronization error or loss of data. Plan your start times carefully. If possible, specify your start times so that synchronization does not overlap. |
To assign an existing schedule to a start up configuration
All active schedules assigned to the table JobAutoStart are available for selection.
One Identity Manager specifies a process plan when changes are committed to the One Identity Manager database. This process plan starts the synchronizing process.
|
NOTE: You can manage existing schedules with Designer. |
To create a schedule
One Identity Manager specifies a process plan when changes are committed to the One Identity Manager database. This process plan starts the synchronizing process.
To edit a schedule
Enter the following properties for a schedule.
Property | Meaning | ||
---|---|---|---|
Name |
Schedule ID. Translate the given text using the | ||
Description |
Detailed description of the schedule. Translate the given text using the | ||
Enabled |
Specifies whether the schedule is enabled or not.
| ||
Time zones |
Unique identifier for the time zone that is used for executing the schedule. Select either "Universal Time Code" or one of the time zones.
| ||
Start (date) |
The day on which the schedule should be run for the first time. | ||
Validity period |
Period within which the schedule is executed.
| ||
Occurs |
Interval in which the task is executed. Valid interval types are "Hourly", "Daily", "Weekly", "Monthly" and "Yearly". Specify the exact weekday for the interval type "Weekly". Specify the day of the month (1st - 31st) for the interval type "Monthly". Specify the day of the year (1 - 366) for the interval type "Yearly".
| ||
Start time |
Fixed start time for the interval types "daily", "weekly", "monthly" and "yearly". Enter the time in local format for the chosen time zone. The start time for | ||
Repeat every |
Rate of occurrence for executing the schedule within the selected time interval. Select at least one weekday for the interval type "Weekly". |
Base objects contain data about the target system to be synchronized, its system connection and the synchronization server. Base objectBase objects contain data about the target system to be synchronized, its system connection and the synchronization server. form a basis for provisioning changes in the target system. A base object is, for example, a concrete Active Directory domain from the One Identity Manager database. The connection parameters for logging into a target system are assigned through a variable set. In addition, the synchronization server is declared in the base object.
Base objects are required for provisioning processes of all target systems that are connected by default to One Identity Manager. You cannot normally specify a base object for provisioning with database connectors and the CSV connectorSystem connector which allow data to be imported from CSV files.. In this case, assignment of one base table and the synchronization server is sufficient. Only one synchronization project can be set up in the One Identity Manager database per base object.
If the synchronization project was creating using a default project template, a base object is added. You can edit this base object and create more base objects. If the synchronization project was created without a project template, no base object is set up.
|
NOTE: You cannot add base objects until the synchronization project has been permanently saved in the database. |
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy