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

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

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

Schema editor

A schema editor is integrated into the schema browser. It is only available in expert mode and allows you to edit customClosed virtual schema properties.

To open the schema editor

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

    - OR -

    Select the Configuration > Target systemClosed category.

  2. Open the Schema browserClosed view.

  3. In the schema browser menu bar, click .

To add a custom schema property

  1. Select the schema in the SchemaClosed view to which you want to add a new virtual schema property.

  2. Click Add schema property in the Action pane.

  3. Select the schema property type and edit its details.

  4. Click Create.

  5. Click Commit to database to save the changes.

To edit a custom schema property

  1. Select the schema property in the Schema view.

  2. Edit the schema property details.

  3. Click Apply changes.

  4. Click Commit to database to save the changes.

To delete a custom schema property

  1. Select the schema property in the Schema view.

  2. Click Delete schema property in the Action bar.

  3. Confirm the security prompt with Yes.
  4. Click Commit to database to save the changes.

Detailed information about this topic

Using custom project templates

You can make your own project templatesClosed based on existing synchronization projectsClosed. This is particularly useful if you want to use customizedClosed mappings or synchronization workflowsClosed in synchronization projects for other target systems. If you base a synchronization project on a custom project template, it includes all settings of the underlying synchronization project. To use the new project, you merely change the target system specific settings.

Script language and supported scripts

A script language and the script languages, which are supported, are specified for the project template. These properties have different functions and can therefore, have different values.

Script language

Language that is used to write the project template's script.

Only change a project template's script language if the script needs to be modified manually and a specific script language should be used to do this.

Supported script languages

Script languages to be used for scripts in synchronization projects created with this project template.

  • If a project template supports more than one script language, select the script language to use when you set up the synchronization project (only in expert mode).

  • If you create a project template from an existing synchronization project, it only supports the script language of the underlying synchronization project.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択