サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.2.1 - Target System Synchronization Reference Guide

Target system synchronization with the Synchronization Editor Working with the Synchronization Editor Basics of target system synchronization Setting up synchronization
Starting the Synchronization Editor Creating a synchronization project Configuring synchronization
Setting up mappings Setting up synchronization workflows Connecting systems Configuring the synchronization log Editing the scope Using variables and variable sets Setting up start up configurations Setting up base objects
Overview of schema classes Customizing the synchronization configuration Checking the consistency of the synchronization configuration Activating the synchronization project Defining start up sequences Copying synchronization projects
Running synchronization Synchronization analysis Setting up synchronization with default connectors Updating existing synchronization projects Script library for synchronization projects Additional information for experts Troubleshooting errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples

Simulating synchronization

You can simulate synchronizationClosed 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 connected systemClosed 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 IdentityClosed 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

  1. Select the Configuration > Start up configurations category.
  2. Select a start up configuration in the document view and click Simulate....
  3. Click Start simulation.
  4. Confirm the security prompt with Yes.

    A report is displayed after simulation has completed. You can save the report.

Starting synchronization manually

To start synchronizationClosed manually

  1. In the Synchronization EditorClosed, open the synchronization projectClosed.

  2. Select the Configuration > Start up configurations category.

  3. Select a start up configuration in the document view and click Run.

  4. Confirm the security prompt with Yes.
Related topics

Running start up sequences

By default, start up sequencesClosed are started using scheduled process plansClosed. In the Synchronization EditorClosed, it is also possible to start a start up sequence manually.

To start a start up sequence manually

  1. In the Synchronization Editor, select the Database > Manage start up sequences menu item.
  2. In the Sequences pane, double-click the start up sequence.
  3. In the Included start up information, click .
Related topics

Monitoring start up sequences

Once a start up sequenceClosed 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 synchronizationClosed.

Instances can be shown and monitored in the Synchronization EditorClosed. 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

  1. In the Synchronization Editor, select the Database > Manage start up sequences menu item.

  2. In the Sequences pane, click .

    This displays the start up sequence instancesClosed and their runtimes.

  3. 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.

  4. To update the view, in the Sequences toolbar, click .

Table 67: Runtime status of an instance

Color

Description

Progress state

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 DesignerClosed, set the DPR | StartSequnce | LifeTime configuration parameterClosed 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

  1. In the Synchronization Editor, select the Database > Manage start up sequences menu item.

  2. In the Start up sequences pane, click .

  3. Double-click on the start up sequence instance.

  4. In the Included start up configurations pane, click .

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択