Enter the following general properties for a start up configuration.
Table 61: General properties of a start up configuration
|
Display name |
Name of the start up configuration. |
|
|
Workflow processed by this start up configuration. |
|
Direction of synchronization |
Direction in which synchronization will be run.
Select a synchronization direction from the list when Defined when run and at least one Use workflow default synchronization step is saved with the workflow. Otherwise the direction of the synchronization workflow or synchronization step is used for synchronization.
|
To the target system |
One Identity Manager is the primary system for synchronization. |
|
To One Identity Manager |
The target system is the primary system for synchronization. | |
|
|
The revision filtering can be used to limit synchronization to just the objects that have been modified since the last synchronization.
Select a value from the list when Defined when run and at least one Use workflow default synchronization step is saved with the workflow. Otherwise the value of the workflow or synchronization step is used for synchronization.
|
Use revision filter |
Only modified object are synchronized. |
|
Do not use revision filter |
All objects are synchronized. | |
|
|
Schedule for starting synchronization. |
|
|
Assign the variable set with which to run synchronization.
If no variable set is given, the default variable is used. If a specialized variable set is assigned, a list of all variables with their values is displayed.
If changes are provisioned from One Identity Manager to the target system, each start up configuration must have a corresponding base object that uses the same variable set. |
|
Description |
Text field for additional explanation. |
Detailed information about this topic
Table 62: Configuration parameters for the delayed start of further
|
Common | Jobservice | RedoDelayMinutes |
This configuration parameter specifies the wait time (latency) in minutes before the attempts to run a again. |
You can group start up configurations logically on the Grouping tab. If you have several start up configurations, you can group them together into a start up group. Specify the start up behavior for each start up group. The same start up behavior applies to all start up configurations belonging to the same start up group.
Table 63: Grouping start up configurations
|
Name |
Name of the start up group.
|
|
Concurrence behavior |
One Identity Manager behavior if multiple start up configurations are run simultaneously.
|
Ignore |
Multiple synchronization can be run simultaneously.
NOTE: This behavior can cause synchronization errors or loss of data.
Plan your start times carefully. If possible, specify your start times so that synchronization does not overlap. |
|
Stop on error |
If synchronization is already running, each new synchronization attempt breaks off with an error. Check the log file for this. |
|
Postpone and wait |
If synchronization is already running, the each new synchronization is postponed until the first one has finished. You can adjust the wait time using the Common | Jobservice | RedoDelayMinutes configuration parameter.
This configuration parameter specifies the wait time in minutes before the Job server attempts to start synchronization again. If the first synchronization is still running, the start of a further synchronization is delayed for the specified length of time. This configuration parameter is only effective on grouped start up configurations whose concurrence behavior is configured with the Postpone and wait option. The default value is two minutes. | |
Related topics
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 data store buffer is cleaned up by maintenance.
Table 64: Start up configuration maintenance mode
| Mode |
Maintenance mode for cleaning up the data store.
| No maintenance |
There is no additional task of clearing up the data store. |
| 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 maps a hierarchy with several levels. |
Detailed information about this topic
is started using . A scheduled process plan is added once a start up configuration is assigned to a schedule. Use schedules to define running 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 . For more information, see the One Identity Manager Operational Guide.
