You can generate a report for analyzing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:
To generate a synchronization analysis report
The report may take a few minutes to generate. It is displayed in a separate window.
One Identity Manager provides connectors for synchronizing with the following 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:
Connectors for natively supported target system are described in the respective administration guide.
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:
The CSV connectorSystem connector which allow data to be imported from CSV files. 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
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).
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
With this native database connector, you can synchronize external databases with the One Identity Manager database.
For detailed information see the following guides:
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:
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.
This method is recommended if your synchronization projects contain extensive customizations that might conflict with the modifications in the patches.
For more detailed information about setting up synchronization projects, see the administration guides for connecting target systems.
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
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.
|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.
|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
In the patch detail view, patches are listed in the order in which they will be applied.
Run a consistency check.
Activate the synchronization project.
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.