You can optimize memory usage for processingSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. synchronization stepSpecific rule for processing exactly two schema classes. data on the Extended tab.
Property |
Description |
---|---|
Performance/memory factorPercentage with which the reload threshold, partition size and bulk level are applied to an object type. |
This controls the behavior of memory and performance in the synchronizationThe process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. 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.
|
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
|
Commit 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.
|
Do not filter outstanding objects |
Specifies whether default handling of objects that are marked as outstanding is disabled. By default, objects marked as outstanding are filtered out of the synchronization objects and thus ignored during synchronization. When two One IdentityAn identity usually represents a real person. In addition, identities that do not represent real people, such as machine identities or service identities, can be mapped in One Identity Manager. (see also virtual identity; see also main identity/subidentity) Manager databases are synchronized, outstanding objects are always matched so that the objects are mapped identically. |
TIP: You can adjust the memory requirements for all the data to be processed in the start-up configuration. You can set the reload threshold, partition size, and bulk level here. These setting are only possible in expert mode. For more information, see Extended properties for start up configuration.