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

Help for Analyzing Synchronization Issues

Help for Analyzing Synchronization Issues

You can generate a report for analyzing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:

  • Consistency check results
  • Revision filterClosed settings
  • ScopeClosed applied
  • Analysis of the synchronization buffer
  • Object access times in the One Identity Manager database and in the target system

To generate a synchronization analysis report

  1. Select the menu Help | Generate synchronization analysis report and answer the security prompt with Yes.

    The report may take a few minutes to generate. It is displayed in a separate window.

  2. Print the report or save it in one of the available output formats.

Setting up Synchronization with Default Connectors

Setting up Synchronization with Default Connectors

One Identity Manager provides connectors for synchronizing with the following target systems:

  • Natively supported target systems

    Separate modules are provided for mapping and processing target system objects. Each target system has its own connector. This includes, for example, the following target systems:

    • Active Directory
    • SharePoint
    • SAP R/3

    Connectors for natively supported target system are described in the respective administration guide.

  • Cloud applications

    Cloud applications can be connected to the One Identity Manager's Universal Cloud Interface Module using the SCIM connector. Cloud objects are transferred to the Cloud Systems Management Module over the Universal Cloud Interface and can be linked there to employees.

    Detailed information see the following guides:

    • One Identity Manager Administration Guide for Connecting to Cloud Applications
    • One Identity Manager Administration Guide for Connecting to the Universal Cloud Interface
  • CSV files

    The CSV connectorClosed can transfer data between CSV files and the One Identity Manager database. In this context, the CSV files map the target system.

    For more detailed information, see the .One Identity Manager CSV Connector User Guide

  • One Identity Manager databases

    Use the One Identity Manager connector to synchronize One Identity Manager databases with the same product version.

    For more detailed information, see the (Nicht definierte Variable:DocumentNameVarSet.DPR1IMUserGuide).

  • Non-natively supported target systems

    You can use the Windows PowerShell connector to connect target systems to One Identity Manager that do not have native support in One Identity Manager. Windows PowerShell cmdlets are used to execute read/write operations in the target system.

    For more detailed information, see the .One Identity Manager Windows PowerShell Connector User Guide

  • Native database system

    With this native database connector, you can synchronize external databases with the One Identity Manager database.

    For detailed information see the following guides:

    • One Identity Manager Native Database Connector User Guide for Connecting DB2 (LUW) Databases
    • One Identity Manager Native Database Connector User Guide for Connecting MySQL Databases
    • One Identity Manager Native Database Connector User Guide for Connecting Oracle Databases
    • One Identity Manager Native Database Connector User Guide for Connecting SQLite Databases
    • One Identity Manager Native Database Connector User Guide for Connecting SQL Server Databases
    • One Identity Manager Native Database Connector User Guide for the CData ADO.NET Provider
    • One Identity Manager Native Database Connector User Guide for the generic ADO.NET Provider
    • One Identity Manager Native Database Connector User Guide for Connecting SAP HANA Databases

Updating Existing Synchronization Projects

Any required changes to system connectors or the synchronization engine are made available when you update One Identity Manager. These changes must be applied to existing synchronization projects to prevent target system synchronizations that are already set up, from failing. There are two way to do this:

  • Apply the patches required to the existing synchronization projects.

    Patches for features and solved issues in One Identity Manager can be installed through hotfix packages and migration packages. You must apply these patches manually for the changes to take effect in existing synchronization projects. The default configuration of these synchronization projects is update in the process. Custom modifications are not effected by the patches.

    This method is recommended if the synchronization projects conform to the default configuration and have either not or only slightly been customized.

  • Delete existing synchronization projects and create them again.

    This method is recommended if your synchronization projects contain extensive customizations that might conflict with the modifications in the patches.

Detailed information about this topic

For more detailed information about setting up synchronization projects, see the administration guides for connecting target systems.

Applying Patches

Applying Patches

CAUTION: Patches do not change customizations in synchronization projects. This mean that conflicts may occur if patches are applied to synchronization projects, which have been customized. This may cause loss of data.

Before you apply a patch

  1. Read the patch description to decide whether it provides necessary improvements for the synchronization project.
  2. Check whether conflict with customizations could occur.
  3. Create a backup of the database so that you can restore the original state if necessary.
  4. Deactivate the synchronization project.

One Identity Manager has three patch types. All patches that are applied are displayed in the synchronization project's migration details. Once a milestone has been applied, the associated patches are not listed separately in the migration details anymore.

Table 68: Patch Types
Patch type Description
Feature Patch for a new feature.
Fix Patch for solved issues.
Mile stone Milestones are provided with each new version of One Identity Manager. A milestone is provided for each context, which includes all the solved issues of the previous version. It can also include new features of the previous version.

Patches can be dependent on each other. These dependencies determine the order in which the patches are applied. When a patch is applied, the patches that are dependent on it are also applied. If a new version of One Identity Manager is installed, all patches for the version are consolidated into one milestone. If patches are available for different version of the program, the older patches must always be applied first. Therefore, One Identity Manager automatically applies all previous milestone once a patch for a later version is selected.

Patches and their dependencies are displayed in the patch view. The left side shows the patches that are available. The newest patches are at the top. Dependent patches are displayed below. In this area, select the patches that you want to apply to the current synchronization project. Then the patches are displayed on the right-hand side, with all their predecessor in the order in which they will be applied.

Table 69: Meaning of Icons in the Rule Tool Bar
Icon Meaning
Fixes Shows patches with fixes.
Features Shows all patches for new features.
Shows all patches that are cannot be applied to the synchronization project.
Shows all patches that are already applied to the synchronization project.

Some patches required user input during installation, for example, to confirm that you really want a particular change to be executed.

To apply patches

  1. Open the synchronization project in the Synchronization EditorClosed.
  2. Select Edit | Update synchronization project... from the menu.
  3. Select the patches to apply in Available patches. Multi-select is possible.

    In the patch detail view, patches are listed in the order in which they will be applied.

  4. Click Apply selected patches.
  5. Enter any user input as prompted.
  6. If necessary, use the patch log to check whether customization need to be reworked.
  7. If required, rework customizations in the synchronization configuration.
  8. Run a consistency check.

  9. Simulate the synchronization.
  10. Activate the synchronization project.

  11. Save the changes.

NOTE: A patch does not take effect until the changes associated with it are saved in the database. If consistency check or simulation errors occur that cannot be corrected, you can dismiss the patch changes by reloading the synchronization project without saving the changes.

Related Topics
Related Documents