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.
By default, are started using scheduled . In the , it is also possible to start a start up sequence manually.
To start a start up sequence manually
- In the Synchronization Editor, 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
.
Related topics
Once a is running, an instance of the start up sequence in added in the DPRStartSequence table. This instance contains information about the runtime status and errors of the entire start up sequence. A DPRStartSequenceHasProjection table is also saved for every start up configuration that is run. This instance contains information about the runtime status and errors of the current .
Instances can be shown and monitored in the . The following instances are shown:
- Start up sequences that are still running.
- Start up sequences that quit on error assuming at least one start up configuration has the Sequence quits on error option set.
To display a start sequence instance
-
In the Synchronization Editor, select the Database > Manage start up sequences menu item.
-
In the Sequences pane, click 
.
This displays the and their runtimes.
-
Double-click on the start up sequence instance.
In the Included startup information view, you can see the runtime status of all the associated start up configurations.
-
To update the view, in the Sequences toolbar, click 
.
Table 70: Runtime status of an instance
|
White |
The instance is created. |
Created |
|
Green |
The start up configuration is waiting to run. |
Pending |
|
Yellow |
Synchronization is running. |
Running |
|
Gray |
Synchronization has successfully completed |
Processed |
|
Red |
Synchronization ended with an error. |
Error |
Instances of completed start up sequences are deleted after a specified time period. The DPRStartSequence and DPRStartSequenceHasProjection tables are cleaned up in the process. By default, completed instances are kept for seven days.
To change the retention period for completed instances
- In the , set the DPR | StartSequnce | LifeTime and enter the maximum retention period.
To restart a sequence if it was unexpectedly stopped, you can delete the start up sequence's instance in the Synchronization Editor.
To delete the instance of a start up sequence
-
In the Synchronization Editor, select the Database > Manage start up sequences menu item.
-
In the Start up sequences pane, click .
-
Double-click on the start up sequence instance.
-
In the Included start up configurations pane, click 
.
Related topics
