Updating Schemas
All the schema data (schema types and schema properties) of the target system schema and the One Identity Manager schema are available when you are editing a synchronization project. Only a part of this data is really needed for configuring synchronization. If a synchronization project is finished, the schema is compressed to remove unnecessary data from the synchronization project. This can speed up loading the synchronization project. Deleted schema data can be added to the synchronization configuration again at a later point. If the target system schema or the One Identity Manager schema has changed, these changes must also be added to the synchronization configuration. Then the changes can be added to the schema property mapping.
To include schema data that have been deleted through compressing and schema modifications in the synchronization project, update each schema in the synchronization project.
This may be necessary if
- A schema was changed by
- Changes to a target system schema
- Customizations to the One Identity Manager schema
- A One Identity Manager update migration
- A schema in the synchronization project was shrunk by
- Enabling the synchronization project
- Saving the synchronization project for the first time
- Compressing a schema
To update a system connection schema
- Open the synchronization project in the Synchronization Editor.
-
Select the category Configuration | Target systems.
- OR -
Select the category Configuration | One Identity Manager connection.
- Select the view General and click Update schema.
- Confirm the security prompt with Yes.
This reloads the schema data.
To edit a mapping
- Open the synchronization project in the Synchronization Editor.
- Select the category Mappings.
- Select a mapping in the navigation view.
The Mapping Editor is displayed.
For more detailed information about mappings, see the One Identity Manager Target System Synchronization Reference Guide.
NOTE: The synchronization is deactivated if the schema of an activated synchronization project is updated. Reactivate the synchronization project to synchronize.
Post-processing outstanding objects
Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizing. This prevents objects being deleted because of an incorrect data situation or an incorrect synchronization configuration.
Outstanding objects
- Cannot be edited in One Identity Manager
- Are ignored by subsequent synchronization
- Are ignored by inheritance calculations
This means, all memberships and assignments remain intact until the outstanding objects have been processed. Start target system synchronization to do this.
To post-process outstanding objects
- In One Identity Manager, select the Epic health care | Target system synchronization: Epic category.
All tables assigned to the target system type Epic as synchronization tables are displayed in the navigation view.
All objects that are marked as outstanding are shown. The Last log entry and Last method run columns display the time at which the last entry was made in the synchronization log and which processing method was run.
The No log available entry can mean the following
- The synchronization log has already been deleted.
- OR -
- An assignment from a member list has been deleted in the target system.
The base object of the assignment has been updated during the
synchronization. A corresponding entry appears in the synchronization log. The
entry in the assignment table is marked as outstanding, but there is no entry in
the synchronization log.
NOTE:
To display object properties of an outstanding object
- Select the object on the target system synchronization form.
- Open the context menu and click Show object.
- Select the objects you want to rework. Multi-select is possible.
-
Click one of the following icons in the form toolbar to run the respective method.
Table 6: Methods for handling outstanding objects
|
Icon |
Method |
Description |
|
|
Delete |
The object is immediately deleted in the One Identity Manager database. Deferred deletion is not taken into account. The Outstanding label is removed for the object. Indirect memberships cannot be deleted. |
|
|
Publish |
The object is added in the target system. The Outstanding label is removed for the object. The method triggers the HandleOutstanding event. This runs a target system specific process that triggers the provisioning process for the object. Prerequisites
- The table containing the object can be published.
- The target system connector has write access to the target system.
|
|
|
Reset |
The Outstanding label is removed for the object. |
- Confirm the security prompt with Yes.
NOTE:
- By default, the selected objects are processed in parallel, which speeds up execution of the selected method. If an error occurs during processing, the action is stopped and all changes are discarded.
- Bulk processing of objects must be disabled if errors are to be localized, which means the objects are processed sequentially. Failed objects are named in the error message. All changes that were made up until the error occurred are saved.
To disable bulk processing
To add custom tables to the target system synchronization
- In the result list, select the target system type Epic.
- Select Assign synchronization tables.
- Assign custom tables whose outstanding objects you want to handle in Add assignments.
- Save the changes.
- Select Configure tables for publishing.
- Select custom tables whose outstanding objects can be published in the target system and set Publishable.
- Save the changes.
NOTE: The target system connector must have write access to the target system in order to publish outstanding objects that are being post-processed. This means that the Connection is read only option is not set in the target system connection.
Help for the analysis of 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 filter settings
- Scope 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
- Open the synchronization project in the Synchronization Editor.
- 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.
- Print the report or save it in one of the available output formats.
Deactivating synchronization
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
- Open the synchronization project in the Synchronization Editor.
- Select the start up configuration and deactivate the configured schedule.
Now you can only start synchronization manually.
An activated synchronization project can only be edited to a limited extent. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again. Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the synchronization project
- Open the synchronization project in the Synchronization Editor.
- Select General on the start page.
- Click Deactivate project.
Related Topics
