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 . 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.
To shrink the system connection schema
- Select Configuration | .
- OR -
Select Configuration | One Identity Manager connection.
- Click Shrink schema... in the General view.
- Mark all the schema types that should not be removed.
These schema types remain there and can still be used in the synchronization configuration.
- Click OK.
You can add the deleted schema data back into the synchronization project again later. To do this you must update the respective schema.
Related topics
To include schema data that have been deleted through compression and schema modifications in the , update each schema in the synchronization project. This may be necessary if:
To update a system connection schema
-
Select the Configuration > 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.
Then you can add the changes to the schema property mapping.
NOTE: The synchronization is deactivated if the schema of an activated synchronization project is updated. Reactivate the synchronization project to synchronize.
Related topics
Memberships, such as user accounts in groups, are saved in in the One Identity Manager database. Membership lists are commonly maintained as an in the target system. If a membership is modified in One Identity Manager, the object must be updated.
To label whether a membership was changed, a base table assignment is maintained, which maintains information about the last change of membership in the Dependencies modification date column (XDateSubItem). During provisioning of modified memberships, One Identity Manager decided which objects must be updated based on this date. In the case of with revision filtering, the highest value from XDateSubItem and XDateUpdated is used as a for the database objects.
If a membership is changed in One Identity Manager, the change date for dependencies must updated so that the modification can be provisioned.
Prerequisites
-
The base table has the XDateSubItem column.
-
The Update dependencies modification date property is true in the table relation between assignment and base table (QBMRelation.IsForUpdateXDateSubItem = TRUE).
Figure 13: Memberships in the One Identity Manager database
If a membership changes (through insertion, deletion, or resetting of status "Outstanding") a task for updating the XDateSubItem column of the base table is queued in the (QBM-K-XDateSubItemUpdate). If necessary, more , for example, calculating inheritance, are queued in the DBQueue. These tasks are handled first. The QBM-K-XDateSubItemUpdate task is deferred until all the processing tasks for the modified object and the module to which it belongs, have been handled. If other memberships in this module are changed in the meantime, these changes are collected by the existing task for updating the XDateSubItem column and subsequently handled together. Once the QBM-K-XDateSubItemUpdate task is run, an update task for the XDateSubItem column is queued in the . The column value is updated. The task for provisioning changed memberships is then placed in the Job queue.
Figure 14: Processing a membership change in One Identity Manager
Example
Active Directory user account membership in an Active Directory group is deleted in One Identity Manager (ADSAccountInADSGroup table). The change date for dependencies is updated on the Active Directory group (ADSGroup.XDateSubItem). The change to the membership for this Active Directory group is provisioned in the target system. The next time synchronization with revision filtering is run, XDateSubItem is taken as the highest change date for the revision counter and is compared to the schema type's revision in the target system schema.
Related topics
