Errors in the configuration can cause system objects to be processed incorrectly. Errors in the data through incorrect configuration can be reduced. Often, it is known how many system objects are generally modified, added, or deleted in a . If this number is exceeded when a processing method is run, a warning appears and synchronization is stopped. The and mapping configurations can be checked and corrected before repeating synchronization.
To specify the maximum set of system objects that can be processed in a synchronization step, define for each processing method. A quota provides the maximum number of objects to process relative to the total number of all objects in the schema class to be synchronized. When a synchronization step is run, One Identity Manager calculates the number of objects to process for each processing method with a quota. If this number exceeds the quota, processing of objects in this schema class stops. Synchronization stops and writes an error message in the synchronization log.
You can define different quotas for synchronizing with the target system and synchronizing with One Identity Manager.
Table 54: Quotas for a synchronization step
|
No quota |
Specifies whether quotas are taken into account by synchronization. If this is set, quotas are not included. |
|
Use these settings |
Specifies which quotas the connected system and the processing method take into account.
- Select the connected system that you want to synchronize.
- Select the processing method and enter the quota in percent.
When you configure a new synchronization step for objects in One Identity Manager for the Delete , a quota of 10% is automatically set. Adjust the quota as required.
One Identity Manager specifies quotas for synchronization in the target system in workflows created with the workflow wizard, by default. Adjust the quota as required.
- Update processing method: 75%
- Delete processing method: 10% for single objects, 20% for many-to-many schema types.
|
Advice
-
Quotas can only be defined for processing methods which modify data (for example, Insert, Update, Delete).
-
When the number of object to process is being calculated, One Identity Manager takes the amount of objects loaded in the slim list. Conditions defined for processing methods are not taken into account!
Enter an higher quota for processing methods use a condition to limit the number of objects to synchronize.
-
To check whether the quota will be exceeded, all the objects to be processed are loaded first. Only then will the processing method be run. If there is a large amount of data, this can affect synchronization performance.
-
If the quota is exceeded by a single object, that object will still be processed.
For example, if a quota of 10% is defined for a schema class with only 8 objects and exactly one object has been changed, then this object will be processed even though the quota has already been exceeded.
In , quotas are ineffective because only single objects are ever processed.
-
Quotas affect membership synchronization only when M:N schema types are processed in a separate synchronization step. (Example: Synchronization of assignments of SAP to SAP user accounts. The quota refers to the set of UserInRole objects).
If memberships are stored as a base (member list), the quota only affects the base object and not the individual members. (Example: Synchronization of Active Directory groups. The quota refers only to the number of groups and not to the number of members).
Related topics
You can specify which Property rules must be applied to each . For example, dependencies between schema class objects can be resolved this way.
| Included rules: |
Select the property mapping rule to be applied during . |
| Excluded rules: |
Select the property mapping rules which should not be applied during synchronization. |
NOTE: Unmarked rules are included automatically.
Detailed information about this topic
You can optimize memory usage for data on the Extended tab.
Table 55: Extended synchronization step properties
| |
This controls the behavior of memory and performance in the step. If more memory is available, you can change the performance/memory factor in favor of performance. Reduce the performance/memory factor if there are memory problems.
The performance/memory factor specifies the percentage with which the reload threshold, partition size, and bulk level are applied to an object type.
Use the slider to set the performance/memory factor.
- Move the slider to the right to increase performance. This requires more memory.
- Move the slider to the left to reduce the memory requirement. This also reduces the performance.
|
|
Reload threshold |
Specifies the maximum number of properties that can be loaded by synchronization to prevent partitioned reloading. You can increase this value to accelerate synchronization of target systems with small mappings. However, more memory is required.
The default value for all data to be processed is fixed in the start up configuration. It can be specified separately for every synchronization step.
To specify the threshold for a synchronization step
- Disable Use start up configuration settings.
- Change the preset reload threshold.
|
|
Mode |
Specifies whether changes in the in-memory object are committed after the synchronization step has been run. This affects changes that are made through the property mapping rule’s Force mapping against direction of synchronization option.
This setting is required only for object-based synchronization, for example, provisioning, when the object must be handled by more than one synchronization step.
-
None: No changes are committed.
-
Automatic: It is decided automatically, which changes are committed.
-
UserDefined: Changes to the selected schema properties are committed.
Under Commit changes for, enable the schema properties whose changes are committed in the in-memory object. |
Detailed information about this topic
The implementation plan shows all of a workflow in the order in which they will be run. Dependencies between schema classes are resolved. Thus, additional steps that are added automatically are also displayed.
To display a workflow implementation plan
- Select the Workflows category.
- Select a workflow in the navigation view.
- In the workflow view, click
.
The implementation plan is displayed as a report. You can save the report.
Detailed information about this topic
