You set the mode for start up configuration on the Maintenance tab. Here, you can specify how data can be maintained that could not be saved during . Object references, which have not (yet) been loaded are included in this (for example, cross-domain references). Complex hierarchies loaded through a CSV import might also have to be reworked because reference objects could not be assigned to them. Unresolvable object references are written to a data store. The synchronization buffer is cleaned up by maintenance.
Table 63: Start up configuration maintenance mode
Mode |
Maintenance mode for cleaning up the synchronization buffer.
No maintenance |
There is no additional task of clearing up the synchronization buffer. |
Always synchronize affected objects |
The filter is removed on objects with unresolved references. |
Full maintenance after every synchronization |
One Identity Manager tries to resolve object references following synchronization. | |
Retries |
Number of retries resolving an object reference. It may be necessary to try several times to resolve an object if it a hierarchy with several levels. |
Detailed information about this topic
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.
NOTE: Synchronization can only be started if the 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
- Select the Configuration | Start up configurations category.
- Select a start up configuration in the document view and click Edit.
- Select a schedule from the Schedule menu.
All active schedules assigned to the table JobAutoStart are available for selection.
- Click OK.
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. For more detailed information, see the One Identity Manager Operational Guide.
To create a schedule
- Select the Configuration | Start up configurations category.
- Select a start up configuration in the document view and click Create schedule.
- Edit the schedule properties.
- Click OK.
One Identity Manager specifies a process plan when changes are committed to the One Identity Manager database. This process plan starts the process.
To edit a schedule
-
Open the in the .
- Select the Configuration | Start up configurations category.
- Select a start up configuration in the document view and click Edit schedule.
- Edit the schedule properties.
- To enable the schedule, click Activate.
- Click OK.
Related topics
Enter the following properties for a schedule.
Table 64: Schedule properties
Name |
Schedule ID. Translate the given text using the button. |
Description |
Detailed description of the schedule. Translate the given text using the button. |
Enabled |
Specifies whether the schedule is enabled or not.
NOTE: Only active schedules are run. |
Time zones |
Unique identifier for the time zone that is used for running the schedule. Choose between Universal Time Code or one of the time zones in the menu.
NOTE:
When you add a new schedule, the time zone is preset to that of the client from which you started the . |
Start (date) |
The day on which the schedule should be run for the first time. If this day conflicts with the defined interval type, the first run is on the next available day based on the start date. |
Validity period |
Period within which the schedule is run.
-
If the schedule will be run for an unlimited period, select the Unlimited duration option.
-
To set a validity period, select the Limited duration option and enter the day the schedule will be run for the last time in End (date). |
Occurs |
Interval in which the task is run. Permitted interval types are Hourly, Daily, Weekly, Monthly, and Yearly.
For the Weekly interval type, specify the precise weekday. For the Monthly interval type, specify the day of the month (1st to 31st day of the month). For the Yearly interval type, specify the day of the year (1st to 366th day of the year).
NOTE: If the schedule is not going to be run until next month because the interval type is Monthly with sub-interval 29, 30, or 31, the last day of the current month is used.
Example:
A schedule that is run on the 31st day of each month is run on 30th April. In February, the schedule is run on the 28th (or 29th in leap year).
Schedules with the interval type Yearly with sub interval 366 are only run in leap year. |
Start time |
Fixed start type for the Daily, Weekly, Monthly, and Yearly interval types. Enter the time in local format for the chosen time zone.
For the interval type Hourly, the start time is calculated from the rate of occurrence and the interval type. |
Repeat every |
Rate of occurrence for running the schedule within the selected time interval. For the Weekly interval type, select at least one weekday. |