NOTE: The following functions should only be carried out by experienced users and system administrators.
The properties and processes described here are only available in expert mode.
IMPORTANT: Changes to properties described here may affect system performance.
Check the effects on system performance of you environment before you change properties in expert mode.
To enable export mode
- Select the Database > Settings... menu item.
- EnableEnable expert mode.
- Click OK.
Topics:
Enter the following additional property for a when you are in expert mode.
Table 79: Properties of a mapping
| |
Property mapping rules can be inherited from a existing mapping. Select a mapping from the menu for this. Inherited property mapping rules can only be editing in the base mapping. Other property mapping rules can be added.
This is only visible in expert mode. |
Related topics
In expert mode, the tab Advanced is displayed in the start up configuration dialog.
Table 80: Extended properties for start up configuration
| Failure handling mode |
Specifies how failed objects are handled during .
- Repeat (default)
Synchronization is repeated until the failed objects do not yield any changes.
Advantage: This results in a full synchronization. Certain, highly complex hierarchical structures cannot only be synchronized in this mode.
Disadvantage: Synchronization in this mode takes considerably longer if a failed object arises.
- Ignore
The synchronization ignores failed objects.
Advantage: Synchronization does not take longer because of failed objects that cannot be corrected by repeating (data error).
Disadvantage: Errors, which can occur through complex data dependencies, are no longer corrected. The synchronization results may therefore not be complete.
NOTE: Repetitions of failed objects means a reduced synchronization.
It makes sense to ignore failed objects if synchronization with this start up configuration is run frequently because the failed objects are processed again by the next synchronization. This also achieves full synchronization results and at the same time reduces the runtime of each synchronization. |
|
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 reload threshold can be specified separately for each . |
| Partition size |
Specifies the number of objects and object pairs the can be processed at the same time. To prevent frequent reloading and to speed up synchronization, you can increase the size of the partition. However, more memory is required. |
| Bulk level |
Controls internal bulk processing of data For example, this is used to calculate how much object data is buffered in main memory. Depending on the operations to be run, a multiple of the value maybe applied.
Higher values speed up processing but require more memory. Smaller value reduce memory usage. This value should only be reduced if synchronizing causes memory problems. |
| Debug mode |
Sets debug mode. are handled sequentially in debug mode. This makes it much easier to find errors. Only set this option for finding errors! |
TIP: If memory problems occur, you should examine the reload threshold, partition size, and bulk level together and adjust them.
The reload threshold, partition size, and the bulk level also depend on how the performance/memory factor is configured in the synchronization steps. The performance/memory factor specifies the percentage with which the reload threshold, partition size, and bulk level are applied to an object type.
Detailed information about this topic
Related topics
Some connectors support the use of local cache. If you enable this cache, the connector loads all the necessary data into a local database after the connection has been established with the target system. The data is loaded for each schema type. The data required for are then supplied by the local database.
The aim is, to replace numerous small single read accesses to the target system by one large one. This can significantly increase the performance of where individual accesses need a lot of time but list access can be relatively quickly handled. This is generally the case for cloud-based target systems. Apart from that, the cache reduces the number of queries to the target system. The cache should, therefore, be used for target systems where the number of queries is limited through .
It does not always make sense to use the cache. When synchronizing with revision filtering, which is run at short intervals, you can expect few accesses to the target system. Filling the cache in this case, might cost more time than the sum of all system accesses without caching.
TIP: Use the cache for initial and the next synchronization after that as well as synchronization without revision filtering.
Cache is only used for synchronization.
The cache database is added in the user's 'temp' directory and deleted after the system is disconnected. contents with sensitive data (if known) are encrypted with the "Data Protection API" with the current user's key.
You specify whether the local is used in the target system connection settings. For more information, see the One Identity Manager administration guides for connecting to target systems that support local caching.
One Identity Manager tool for configuring target system synchronization