To delete a
- In the , select the Database > Manage start up sequences menu item.
- In the Sequences pane, double-click the start up sequence.
- In the Included start up information, click
.
- Confirm the security prompt with Yes.
This deletes all instances of the start up sequence.
Related topics
Enter the following properties for a .
Table 66: General start up sequence properties
|
Name |
Name of the start up sequence. |
|
Schedule |
Schedule for starting .
Ensure that start up configurations that are used in start up sequences are not started individually at the same time. Assign the start up sequence to a schedule that is not used in any of the start up configurations. |
|
Allow multiple starts |
Specifies whether this start up sequence can be started more than once. Ensure that no other synchronization is started for the same target system as long as synchronization is running.
Example: A start up sequence is triggered daily. Even if the start up sequence has not ended after 24 hours, it should be started again. If each start up configuration synchronizes another target system, you can set the Allow multiple starts option. If the option is not set, the start up sequence is not restarted until the current instance is finished. |
|
Quit with an error |
Specifies whether the start up sequence is canceled if it was repeated more than once and Allow multiple starts is disabled.
System synchronizations that start frequently should not have this set. If the start up sequence is restarted, a new synchronization cannot be run until the current synchronization finishes. |
|
Description |
Text field for additional explanation. |
You can set the properties of each the selected start up configurations.
Table 67: Start up configuration properties in a start up sequence
|
Runs simultaneously |
Specifies whether this start up configuration can be started at the same time as the previous start up configuration. Use this option to in parallel that are started from different synchronization servers.
Do not set this option if the start up configurations handle the same target system objects. |
|
Sequence quits on error |
Specifies whether the start up sequence is canceled if an error occurs running this start up configuration.
If the option is set, instances of the start up sequence are still displayed in the after synchronization has quit. |
Example
Shortly after synchronizing personnel planning data from an SAP HCM system, always synchronize the SAP R/3, Active Directory, Privileged Account Management, and Google Workspace systems. Personnel planning data should be synchronized daily.
Even if the start up sequence has not ended after 24 hours, it should be started again.
The target systems SAP R/3, Active Directory, Privileged Account Management, and Google Workspace can be synchronized in parallel. They cannot, however, be started before SAP HCM has finished synchronizing.
The start up sequence contains the following configuration:
- Schedule: daily
- Allow multiple starts: set
- Order of start up configurations:
-
SAP HCM System
Runs simultaneously: not set
-
SAP R/3 client
Runs simultaneously: not set
-
Active Directory domain
Runs simultaneously: set
-
One Identity Safeguard Appliance
Runs simultaneously: set
-
Google Workspace Domain
Runs simultaneously: set
Detailed information about this topic
To reuse existing configurations, you can copy . The copy is initially deactivated.
To copy a synchronization project
-
In the , open the synchronization project.
-
Select the Edit > Create copy menu item.
- Confirm the security prompt with Yes.
-
If you immediately want to edit the copy, confirm the prompt with Yes.
-
Edit the synchronization configuration and then activate it.
- Click Commit to database to save the new project.
Related topics
is started using . It is possible to start synchronization manually in the . 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 log file.
-
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.
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 and specify the order in which they are run.
Detailed information about this topic
