You can generate a report for analyzing problems that arise during , inadequate performance for example. The report contains information such as:
-
Consistency check results
-
settings
-
applied
-
Analysis of the data store
-
Object access times in the One Identity Manager database and in the target system
To generate a synchronization analysis report
-
Select the Help > Generate synchronization analysis report menu item and click Yes in the security prompt.
The report may take a few minutes to generate. It is displayed in a separate window.
-
Print the report or save it in one of the available output formats.
One Identity Manager provides connectors for with the following target systems:
- Directly supported target systems
Separate modules are provided for mapping and processing target system objects. Each target system has its own connector. This includes target systems such as:
- Active Directory
- SharePoint
- SAP R/3
Connectors for directly supported target systems are described in the administration guides for the relevant modules.
- Cloud applications
Using the SCIM connector, Cloud applications can be connected to the Universal Cloud Interface of the One Identity Manager. Cloud objects are transferred to the Universal Cloud Interface over the Cloud Systems Management Module and can be linked there to employees.
For 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 can transfer data between CSV files and the One Identity Manager database. In this context, the CSV files map the target system.
For more 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 information, see the One Identity Manager User Guide for the One Identity Manager Connector.
- Target systems that are not directly supported
You can use the Windows PowerShell connector to connect target systems to One Identity Manager that are not directly supported in One Identity Manager. Windows PowerShell cmdlets are used to run read and write operations in the target system.
For more detailed information, see the One Identity Manager Windows PowerShell Connector User Guide.
- Other database systems
With this , you can synchronize external databases with the One Identity Manager database.
For detailed information, see the following guides:
- One Identity Manager Generic Database Connector User Guide for Connecting DB2 (LUW) Databases
- One Identity Manager Generic Database Connector User Guide for Connecting MySQL Databases
- One Identity Manager Generic Database Connector User Guide for Connecting Oracle Databases
- One Identity Manager Generic Database Connector User Guide for Connecting SQLite Databases
- One Identity Manager Generic Database Connector User Guide for Connecting SQL Server Databases
- One Identity Manager Generic Database Connector User Guide for the CData ADO.NET Provider
- One Identity Manager Generic Database Connector User Guide for the generic ADO.NET Provider
- One Identity Manager Generic Database Connector User Guide for Connecting SAP HANA Databases
- One Identity Manager Generic Database Connector User Guide for Connecting PostgreSQL Databases
Any required changes to system connectors or the engine are made available when you update One Identity Manager. These changes must be applied to existing to prevent that are already set up, from failing. There are two way to do this:
- Apply the required patches to the existing synchronization projects.
Patches for new functions and resolved issues in One Identity Manager are installed by 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. modifications are not effected by the patches.
This method is recommended if the synchronization projects conform to the default configuration and contain no, or only very little, customization.
Checks are made during daily to find out if there are patches available for the existing synchronization projects. This information is displayed on the 's start page. If there are patches, the 
icon and the number of patches are displayed next to the synchronization project's name. This display is updated each time a synchronization project is saved.
- 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 information about setting up synchronization projects, see the administration guides for connecting target systems.
One Identity Manager has three patch types. All patches that are applied are displayed in the 's migration details. Once a milestone has been applied, the associated patches are not listed separately in the migration details anymore.
Table 74: Patch types
| Optional features |
Patch for optional functionality |
| Fix |
Patch for solved problems. |
| Mile stone |
Milestones are provided with every new One Identity Manager version. A milestone is provided for each context, which includes all the solved issues of the previous version. It does not contain the optional 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.
Each patch contains a script which checks if the patch can be applied to the synchronization project. Whether or not a patch can be applied depends on the concrete synchronization configuration.
Table 75: Meaning of icons in the rule tool bar
|
 Fixes
|
Shows patches with fixes. |
|
 Optional features
|
Shows all patches for optional features. |
|
|
Shows all patches that are cannot be applied to the synchronization project. |
|
|
Shows all patches that are already applied to the synchronization project. |
Related topics
