지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Additional properties of a mapping

Enter the following additional property for a mappingClosed when you are in expert mode.

Table 76: Properties of a mapping
Properties Meaning
Base mappingClosed

Property mapping rules can be inherited from a existing mapping. Select a mapping from the menu for this. Inherited property mapping rules can only be editing in the base mapping. Other property mapping rules can be added.

This is only visible in expert mode.

Related topics

Extended properties for start up configuration

In expert mode, the tab Advanced is displayed in the start up configuration dialog.

Table 77: Extended properties for start up configuration

Property

Description

Failure handling mode

Specifies how failed objects are handled during synchronizationClosed.

  • Repeat (default): Synchronization is repeated until the failed objects do not yield any changes.

    Advantage: This results in a full synchronization. Certain, highly complex hierarchical structures cannot only be synchronized in this mode.

    Disadvantage: Synchronization in this mode takes considerably longer once an object fails.

  • Ignore: Synchronization ignores failed objects.

    Advantage: Synchronization does not take longer because of failed objects that cannot be corrected by repeating (data error).

    Disadvantage: Errors, which can occur through complex data dependencies, are no longer corrected. The synchronization results may therefore not be complete.

NOTE: Repetitions of failed objects means a reduced synchronization.

It makes sense to ignore failed objects if synchronization with this start up configuration is run frequently because the failed objects are processed again by the next synchronization. This also achieves full synchronization results and at the same time reduces the runtime of each synchronization.

Max. retries

Maximum number of retries for synchronizing failed objects.

Collision detection

Mode for checking processing conflicts during synchronization. Select when One IdentityClosed Manager checks whether synchronization objects have already been processed by another system process (provisioning, for example).

  • Before processing (default): Checks synchronization objects for possible collision conflicts immediate after they are loaded.

    Advantage: Detected objects are not processed.

    Disadvantage: Conflicts are not detected if synchronization objects are then processed by other system processes during synchronization. Conflicts can still occur due to the time delay before the objects are saved.

  • Before committing: Synchronization objects are checked for possible concurrency conflicts before committing.

    Advantage: Conflicts are detected immediately before committing. This increases the detection rate.

    Disadvantage: Objects are processed unnecessarily if their processing conflicts could already have been detected after loading.

  • Multiple: Synchronization objects are checked for possible concurrency conflicts before processing starts and before saving.

    Advantage: High detection rate.

    Disadvantage: Multiple checks can reduce synchronization performance.

Cached data retention time

Specifies how many seconds data is cached while processing conflicts are being checked during synchronization.

Reload threshold

Specifies the maximum number of properties that can be loaded by synchronization to prevent partitioned reloading. You can increase this value to accelerate synchronization of target systems with small mappings. However, more memory is required.

The reload threshold can be specified separately for each synchronization stepClosed.

Partition size

Specifies the number of objects and object pairs the can be processed at the same time. To prevent frequent reloading and to speed up synchronization, you can increase the size of the partition. However, more memory is required.

Bulk level

Controls internal bulk processing of data For example, this is used to calculate how much object data is buffered in main memory. Depending on the operations to be run, a multiple of the value maybe applied.

Higher values speed up processing but require more memory. Smaller value reduce memory usage. This value should only be reduced if synchronizing causes memory problems.

Debug mode

Sets debug mode. Processing stepsClosed are handled sequentially in debug mode. This makes it much easier to find errors. Only set this option for finding errors!

TIP: If memory problems occur, you should examine the reload threshold, partition size, and bulk level together and adjust them.

The reload threshold, partition size, and the bulk level also depend on how the performance/memory factor is configured in the synchronization steps. The performance/memory factor specifies the percentage with which the reload threshold, partition size, and bulk level are applied to an object type.

Detailed information about this topic
Related topics

Using the local cache

Some connectors support the use of local cache. If you enable this cache, the connector loads all the necessary data into a local database after the connection has been established with the target system. The data is loaded for each schema type. The data required for synchronizationClosed are then supplied by the local database.

The aim is, to replace numerous small single read accesses to the target system by one large one. This can significantly increase the performance of target system synchronizationClosed where individual accesses need a lot of time but list access can be relatively quickly handled. This is generally the case for cloud-based target systems. Apart from that, the cache reduces the number of queries to the target system. The cache should, therefore, be used for target systems where the number of queries is limited through quotasClosed.

It does not always make sense to use the cache. When synchronizing with revision filtering, which is run at short intervals, you can expect few accesses to the target system. Filling the cache in this case, might cost more time than the sum of all system accesses without caching.

TIP: Use the cache for initial and the next synchronization after that as well as synchronization without revision filtering.

Cache is only used for synchronization.

The cache database is added in the user's 'temp' directory and deleted after the system is disconnected. Schema typeClosed contents with sensitive data (if known) are encrypted with the "Data Protection API" with the current user's key.

You specify whether the local is used in the target system connection settings. For more information, see the One IdentityClosed Manager administration guides for connecting to target systems that support local caching.

Schema browser

In addition to the schema overview, the Synchronization EditorClosed provides a schema browser in expert mode. The details of the connected target system's entire schema and the details of the entire One Identity Manager schema are shown in the schema browser. SchemaClosed types, schema properties, and the processing methods available are displayed in a hierarchical structure. The schema can be saved as XML for error analysis.

To save a schema

  1. Select the Configuration > One Identity Manager connection category.

    - OR -

    Select Configuration > Target systemClosed category.

  2. Open the Schema browserClosed view.

    This display the entire schema of the connected system in a hierarchical structure.

  3. In the schema browser menu bar, click .

  4. Enter a file name and repository.

  5. Click Save.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택