Chat now with support
Chat with Support

Identity Manager 8.0 - Target System Synchronization Reference Guide

Target Synchronization with the Synchronization Editor Basics of Target System Synchronization Setting up Synchronization
Starting the Synchronization Editor Creating a Synchronization Project How to Configure 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 Synchronization Configuration Checking Synchronization Configuration Consistency Activating the Synchronization Project
Running Synchronization Synchronization Analysis Setting up Synchronization with Default Connectors Updating Existing Synchronization Projects Additional Information for Experts Error Handling Appendix: Example of a Configuration File

Using Local Cache

Using 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 synchronization 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 synchronization 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 quotas.

It does not always make sense to use the cache. When synchronizing with revision filtering, which is executed 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

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 category Configuration | One Identity Manager connection.

    - OR -

    Select the category Configuration | Target system.

  2. Open the Schema browser view.

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

  3. Click in the schema browser menu bar.
  4. Enter a file name and repository.
  5. Click Save.

Creating Project Templates

Creating Project Templates

Project templates can be created in expert mode from existing synchronization projects. You can use these to create new synchronization projects with the project wizard.

NOTE: The script language of the underlying synchronization project is the only script language which is supported by the project template (DPRTemplate.SupportedScriptLanguages).

When you create a synchronization project, the project wizard displays all the project templates for which the following applies:

  • The script language of the synchronization project you want to set up, supports the project template script language.

To create a project template

  1. Select Edit | Create template....
  2. Enter the template properties.

    The values are preset with the properties of the open synchronization project.

  3. Click OK.
Table 72: Project Template Properties
Property Description
Display name Name of the project template to display in the project wizard.
Script language Script language in which the template is created.
Description Spare text box for additional explanation.

How can Custom Tables be Included in Synchronization

Custom schema extensions can be included in the synchronization configuration. Custom columns are automatically assigned to additional schema properties which can be included in the mapping. The following settings are required to include custom tables in synchronization.

To prepare a custom table for synchronization

  1. Assign a target system type to the custom table.
  2. Specify whether outstanding objects can be published in post-processing.
  3. Create a schema class in the One Identity Manager schema for the custom table.
Detailed information about this topic

For detailed information about target system types and post-processing outstanding object, see the target system connection guides.

Related Topics
Related Documents