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 the loading of 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 compression and schema modifications in the synchronization project, update each schema in the synchronization project. This may be necessary if:
To update a system connection schema
-
In the Synchronization Editor, open the synchronization project.
-
Select the Configuration > Target system category.
- OR -
Select the Configuration > One Identity Manager connection category.
-
Select the General view and click Update schema.
- Confirm the security prompt with Yes.
This reloads the schema data.
To edit a mapping
-
In the Synchronization Editor, open the synchronization project.
-
Select the Mappings category.
-
Select a mapping in the navigation view.
Opens the Mapping Editor. For more 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.
Configuring department synchronization
To synchronize departments and department memberships, data from the schema types HROrganization and HRPersonInOrganization is loaded. You must filter required objects to synchronize this data, otherwise performance may be seriously affected if all departments are being synchronized.
If you use default mapping for these schema types, you can select the required departments from the organization hierarchy. To do this, edit the synchronization project's scope and create the hierarchy filter.
Departments can also be differentiated from other organization by their type. Since you can customize these types in Oracle E-Business Suite, departments are not filtered by type in the default maps. To filter departments by type, define your own schema classes.
If you use custom mapping for synchronizing departments, define the filter beforehand in the schema class. In addition, you can use hierarchy filters to limit further the number of synchronization objects.
Related topics
Speeding up synchronization with revision filtering
When you start synchronization, all synchronization objects are loaded. Some of these objects have not be modified since the last synchronization and, therefore, must not be processed. Synchronization is accelerated by only loading those object pairs that have changed since the last synchronization. One Identity Manager uses revision filtering to accelerate synchronization.
Oracle E-Business Suite supports revision filtering. The E-Business Suite objects' date of last change is used as a revision counter. Each synchronization saves the last date is was run as a revision in the One Identity Manager database (DPRRevisionStore table, Value column). This value is used as a comparison for revision filtering when the same workflow is synchronized the next time. When this workflow is synchronized the next time, the E-Business Suite objects' change date is compared with the revision saved in the One Identity Manager database. Only those objects that have been changed since this date are loaded from the target system.
Optimized revision filtering is supported because objects are not deleted in the target system by synchronization and Oracle E-Business Suite makes it possible to find out about the last change to a schema type. If the objects of a schema type were neither added nor changed, the synchronization step can be skipped. Objects must not be loaded for comparison. The Oracle E-Business Suite connector provides all the relevant information.
To use optimized revision filtering
-
In the Designer, set the Common | TableRevision configuration parameter.
Now each time a table changes, the table's revision date updates. This information is stored in the QBMTableRevision table, RevisionDate column. In this way, One Identity Manager identifies whether a table object has been added, changed, or deleted.
Synchronization with revision filtering compares a table's revision date and the schema type's change information against the revision saved in the One Identity Manager database. If the revision date is older, no objects have been changed in this table since the previous synchronization. If the change information of the schema type is also older, no objects in this schema type have been changed since the previous synchronization. Therefore, synchronization does not carry out this step for the affected table. If the revision date or change information is newer, synchronization does carry out this step and the changed objects are determined as described above.
The revision is found at start of synchronization. Objects modified by synchronization are loaded and checked by the next synchronization. This means that the second synchronization after initial synchronization is not significantly faster.
Revision filtering can be applied to workflows and start up configuration.
To permit revision filtering on a workflow
To permit revision filtering for a start up configuration
NOTE: If the Common | TableRevision is not set, all revision data in the QBMTableRevision table is deleted.
For more information about revision filtering, see the One Identity Manager Target System Synchronization Reference Guide.
Using specific statements for database initialization
You can make various additional settings on the target system connection, if required due to the configuration of the target system. For example, the default language and time formatting can be overwritten by an SQL statement that is run every time a connection is established.
To use additional statements for database initialization:
-
In the Synchronization Editor, open the synchronization project.
-
Enable expert mode.
-
Edit the target system connection.
-
Select the Configuration > Target system category.
-
Click Edit connection.
This starts the system connection wizard.
-
Select Database connection startup sequence page and enter the SQL statements to be run every time a connection is established.
NOTE: Only single instructions are supported. In a multi-line statement, each line is processed individually.
Example of a multi-line statement
alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS' |
alter session set nls_language = 'AMERICAN' |
-
Click Test.
-
End the system connection wizard.
This updates the connection parameters.
- Save the changes.
If you are running Synchronization Editor in expert mode, SQL statements can be entered when a synchronization project is set up.
