Configuring single object synchronization
Changes made to individual objects in the target system can be immediately applied in the One Identity Manager database without having to start a full synchronization of the target system environment. Individual objects can only be synchronized if the object is already present in the One Identity Manager database. The changes are applied to the mapped object properties. If the object is no longer present in the target system, then it is deleted from the One Identity Manager database.
Prerequisites
-
A synchronization step exists that can import the changes to the changed object into One Identity Manager.
-
The path to the base object of the synchronization is defined for the table that contains the changed object.
Single object synchronization is fully configured for synchronization projects created using the default project template. If you want to incorporate custom tables into this type of synchronization project, you must configure single object synchronization for these tables. For more information about this, see the One Identity Manager Target System Synchronization Reference Guide.
To define the path to the base object for synchronization for a custom table
-
In the Manager, select the SAP R/3 > Basic configuration data > Target system types category.
-
In the result list, select the SAP R/3 target system type.
-
Select the Assign synchronization tables task.
-
In the Add assignments pane, assign the custom table for which you want to use single object synchronization.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the custom table and enter the Root object path.
Enter the path to the base object in the ObjectWalker notation of the VI.DB.
Example: FK(UID_SAPMandant).XObjectKey
- Save the changes.
Related topics
Accelerating provisioning and single object synchronization
To smooth out spikes in data traffic, handling of processes for provisioning and single object synchronization can be distributed over several Job servers. This will also accelerate these processes.
NOTE: You should not implement load balancing for provisioning or single object synchronization on a permanent basis. Parallel processing of objects might result in dependencies not being resolved because referenced objects from another Job server have not been completely processed.
Once load balancing is no longer required, ensure that the synchronization server runs the provisioning processes and single object synchronization.
To configure load balancing
-
Configure the server and declare it as a Job server in One Identity Manager.
All Job servers must access the same SAP client as the synchronization server for the respective base object.
-
In the Synchronization Editor, assign a custom server function to the base object.
This server function is used to identify all the Job servers being used for load balancing.
If there is no custom server function for the base object, create a new one.
For more information about editing base objects, see the One Identity Manager Target System Synchronization Reference Guide.
-
In the Manager, assign this server function to all the Job servers that will be processing provisioning and single object synchronization for the base object.
Only select those Job servers that have the same configuration as the base object's synchronization server.
Once all the processes have been handled, the synchronization server takes over provisioning and single object synchronization again.
To use the synchronization server without load balancing.
For more information about load balancing, see the One Identity Manager Target System Synchronization Reference Guide.
Detailed information about this topic
Help for analyzing synchronization issues
You can generate a report for analyzing problems that arise during synchronization, inadequate performance for example. The report contains information such as:
-
Consistency check results
-
Revision filter settings
-
Scope 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
-
In the Synchronization Editor, open the synchronization project.
-
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.
Disabling synchronization
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
-
In the Synchronization Editor, open the synchronization project.
-
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 extend. 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
-
In the Synchronization Editor, open the synchronization project.
-
Select the General view on the home page.
-
Click Deactivate project.
Detailed information about this topic
