Enter the following properties for a .
Table 67: 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. |
|
Description |
Text field for additional explanation. |
You can set the properties of each the selected start up configurations.
Table 68: 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
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
You can simulate before using a start up configuration to run it. Simulation allows you to estimate the result of synchronization. This means you can recognize potential errors in the synchronization configuration, for example. Reactions from the and it consequences cannot be incorporated because simulation cannot modify data.
Simulation runs the following actions:
- Show implementation plan
- Connects to the target system and One Identity Manager database
- Loads system objects
- Logs write operations for objects and their properties but does not run
Dependent objects and schema properties cannot be resolved if the objects already exist in the connected system. Unresolvable dependencies are logged.
IMPORTANT: Simulation changes data in neither One Identity Manager nor the target system. However, large amounts of data are read from both systems. This can affect system performance and processing.
All the data to be processed remains in the memory of the workstation running the simulation until the simulation is complete. Demands on memory may be heavy depending on the amount of data.
To start simulation
- Select the Configuration > Start up configurations category.
- Select a start up configuration in the document view and click Simulate....
- Click Start simulation.
- Confirm the security prompt with Yes.
A report is displayed after simulation has completed. You can save the report.
