Rule filters
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
Extended synchronization step properties
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
Showing implementation plans
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
Connecting systems
You connect to the One Identity Manager database when you log into the . You connect to the target system with the project wizard. The system connection is automatically set up once One Identity Manager accesses the target system. The icon Synchronization Editor is displayed in the 
status bar if a target system is connected.
Other system connection properties are saved in the . You can edit these properties in Synchronization Editor.
