All the information, tips, warnings, and errors that occur during synchronization are recorded in the synchronization log. You can configure the type of information to record separately for each system connection.
To configure the content of the synchronization log
To configure the synchronization log for target system connection, select the Configuration > Target system category in the Synchronization Editor.
- OR -
To configure the synchronization log for the database connection, select the Configuration > One Identity Manager connection category in the Synchronization Editor.
Select the General view and click Configure.
Select the Synchronization log view and set Create synchronization log.
Enable the data to be logged.
NOTE: Some content generates a particularly large volume of log data. The synchronization log should only contain data required for error analysis and other analyzes.
- Click OK.
Synchronization logs are stored for a fixed length of time.
To modify the retention period for synchronization logs
Having used the Synchronization Editor to set up a synchronization project for initial synchronization of an E-Business Suite system, you can use the synchronization project to load Oracle E-Business Suite objects into the One Identity Manager database. If you manage user accounts and their authorizations with One Identity Manager, changes are provisioned in the Oracle E-Business Suite.
You must customize the synchronization configuration in order to compare the database with the Oracle E-Business Suite regularly and to synchronize changes.
To use One Identity Manager as the primary system during synchronization, create a workflow with synchronization in the direction of the Target system.
To specify which Oracle E-Business Suite objects and One Identity Manager database objects are included in the synchronization, edit the scope of the target system connection and the One Identity Manager database connection. To prevent data inconsistencies, define the same scope in both systems. If no scope is defined, all objects will be synchronized.
You can use variables to create generally applicable synchronization configurations that contain the necessary information about the synchronization objects when synchronization starts. Variables can be implemented in base objects, schema classes, or processing method, for example.
Use variables to set up a synchronization project for synchronizing different E-Business Suite systems. Store a connection parameter as a variable for logging in to the respective system.
Update the schema in the synchronization project if the One Identity Manager schema or target system schema has changed. Then you can add the changes to the mapping.
To synchronize additional schema properties, update the schema in the synchronization project. Include the schema extensions in the mapping.
- To define additional instructions for initializing the database connection, edit the target system connection.
Add your own schema types if you want to synchronize data, which does not have schema types in the connector schema. Include the schema extensions in the mapping.
For more information about configuring synchronization, see the One Identity Manager Target System Synchronization Reference Guide.
Detailed information about this topic
If you want to change the configuration of existing synchronization projects, check the possible effects of these changes on the data that has already been synchronized. Note the following information in particular.
Notes for the synchronization of E-Business Suite employee data
If you change the mappings for synchronization of employee data for a specific company, check whether you also need to change which columns are locked in the Employee or Locality table. To lock additional columns for editing in One Identity Manager, define custom scripts (OnLoaded) in the Employee or Locality table.
For more information about table scripts, see the One Identity Manager Configuration Guide.
Changing the connection parameters to Oracle E-Business Suite
The connection parameters to the target system can be subsequently changed by the system connection wizard.
The unique name of the DN is used to generate a unique defined name for all objects in the system. If this name is changed after the initial synchronization, the objects will no longer be uniquely identifiable in the next synchronization. This means that all objects will be created again in the One Identity Manager database.
The unique name for the DN should not be changed after the initial synchronization.
If the unique name for the DN must be changed before the initial synchronization, this change must also be transferred to the variable CP_EBSSystemDN. This variable is used in the filter condition for the scope.
For more information about adjusting the connection parameters and editing variables, see One Identity Manager Target System Synchronization Reference Guide.
The synchronization project for initial synchronization provides a workflow for initial loading of target system objects (initial synchronization) and one for provisioning object modifications from the One Identity Manager database to the target system (provisioning). To use One Identity Manager as the primary system during synchronization, you also require a workflow with synchronization in the direction of the Target system.
NOTE: Only synchronization projects created with the Oracle E-Business Suite Synchronization project template contain a provisioning workflow
To create a synchronization configuration for synchronizing Oracle E-Business Suite
In the Synchronization Editor, open the synchronization project.
Check whether the existing mappings can be used to synchronize into the target system. Create new maps if required.
Create a new workflow with the workflow wizard.
This creates a workflow with Target system as its direction of synchronization.
Create a new start up configuration. Use the new workflow to do this.
- Save the changes.
Run a consistency check.