After the synchronization of data from the target system into the One Identity Manager database, rework may be necessary. Check the following tasks:
After the synchronization of data from the target system into the One Identity Manager database, rework may be necessary. Check the following tasks:
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 synchronizations.
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 the Manager, select the Oracle E-Business Suite | Target system synchronization: Oracle E-Business Suite category.
All the synchronization tables assigned to the Oracle E-Business Suite target system type are displayed in the navigation view.
On the Target system synchronization form, in the Table / object column, open the node of the table for which you want to post-process outstanding objects.
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 executed. 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 from the target system.
The base object of the assignment was 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.
An object that contains a member list has been deleted from the target system.
During synchronization, the object and all corresponding entries in the assignment tables are marked as outstanding. However, an entry in the synchronization log appears only for the deleted object.
TIP:
To display object properties of an outstanding object
Select the objects you want to rework. Multi-select is possible.
Click on one of the following icons in the form toolbar to execute the respective method.
Icon |
Method |
Description |
---|---|---|
|
Delete |
The object is immediately deleted from the One Identity Manager database. Deferred deletion is not taken into account. The Outstanding label is removed from the object. Indirect memberships cannot be deleted. |
|
Publish |
The object is added to the target system. The Outstanding label is removed from the object. The method triggers the HandleOutstanding event. This runs a target system specific process that triggers the provisioning process for the object. Prerequisites:
|
|
Reset |
The Outstanding label is removed for the object. |
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
In the form's toolbar, click to disable bulk processing.
You must customize your target system synchronization to synchronize custom tables.
To add tables to target system synchronization
In the Manager, select the Oracle E-Business Suite | Basic configuration data | Target system types category.
In the result list, select the
Select the Assign synchronization tables task.
In the
Select the Configure tables for publishing task.
Select the
Synchronization Editor helps you to analyze and eliminate synchronization errors.
Simulating synchronization
The simulation allows you to estimate the result of synchronization. This means you can, for example, recognize potential errors in the synchronization configuration.
Analyzing synchronization
You can generate the synchronization analysis report for analyzing problems which occur during synchronization, for example, insufficient performance.
Logging messages
One Identity Manager offers different options for logging errors. These include the synchronization log, the log file for One Identity Manager Service, the logging of messages with NLOG, and similar.
Reset start information
If synchronization was terminated unexpectedly, for example, because a server was not available, the start information must be reset manually. Only then can the synchronization be restarted.
Resetting revisions
It may also be necessary to process those objects during synchronization, whose change information has not been updated since the last synchronization. This might be required if changes to data were made without the change information for the object being updated, for example. This means, the change information for objects becomes older than that saved in the synchronization project. In such cases, the revision for a start up configuration can be reset.
For more information about these topics, see the One Identity Manager Target System Synchronization Reference Guide.
© ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center