立即与支持人员聊天
与支持团队交流

Identity Manager 9.1.3 - 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 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
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

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 69: 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

Handling unexpected interruption of synchronization

If synchronizationClosed is run with a start up configuration, some One Identity Manager processes are stopped. It is not possible to start this start up configuration again. The One Identity Manager saves start information of the current synchronization in the database. This start information is reset once synchronization is completely normally.

If synchronization stopped unexpectedly because a server was not available, for example, you must manually reset the start information. You can only restart synchronization after this.

IMPORTANT: Start information may not be reset if synchronization is running normally.

Before you reset the start information, ensure that synchronization has really been stopped.

To reset synchronization start information

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

    The status "Broken" is entered in the synchronization log.

NOTE: If necessary, start information can be reset automatically. To do this, customizeClosed the process DPR_DPRProjectionStartInfo_Run_Synchronization. Changes made to the process are applied to all target systems connected to the One Identity Manager database when synchronization takes place.

Resetting revisions

SynchronizationClosed with revision filtering involves finding object pairs where one has newer change information than the last time it was synchronized. It may also be necessary to process those objects during synchronization, whose change information has not be updated since the last synchronization. This might be required if changes to data were made without the change information for the object being updated, for example. It is possible that data in one of the connected systemsClosed was restored from a backup. This means the change information for the objects is now older than before the last synchronization. Such objects are not processed by synchronization with revision filtering.

One Identity Manager provides an option to reset revision numbers in a start up configuration. The revision can be reset for one schema type or for all of a schema's types. The next time synchronization is run with this start up configuration, all affected objects are seen as changed.

To reset the revision number

  1. Select the category Configuration > Start up configurations.
  2. Select a start up-configuration in the document view and click Revisions...

    This opens the Manage revisions... dialog window. which displays all the schema types with their respective revision numbers. SchemaClosed types without a revision number, are not displayed.

  3. Select the schema for which you want to reset the revision number.

    - OR -

    From the target system schema or the One Identity Manager schema, select the schema type for which you want to reset the revision.

  4. Click Reset.
  5. Select another schema type if required.
  6. Click Apply.
  7. Confirm the security prompt with Yes.

    The revisions of the selected schema types are deleted from the start up configuration.

Related topics
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级