This tab defines additional settings for your configuration. Some fields are self explanatory and some should not be changed. This tab provides the following groups of settings:
Do not change the settings in this section except for the Default Locale, if needed.
These settings allow an administrator to tune the size of the record chunks that Identity Governance uses for the data collection and publication operations to achieve optimal performance in each environment.
Do not clear Clean DAAS Configuration post collection. The Max supported Depth of permission relations field prevents loops of relationship mappings in deeply nested permissions environments. The default setting should be best for most environments.
If you also have Identity Manager installed, these settings help you integrate Identity Governance with Identity Manager.
Requires the Identity Manager Driver for Identity Governance (Identity Governance Driver)
Specifies whether you want to integrate the permissions and permission assignment tasks in the Identity Governance catalog with the role and resource catalog in Identity Manager.
For more information, see Understanding Synchronization and Reflection
in the NetIQ Identity Governance Administrator Guide.
Specifies whether you want to review Identity Manager permissions that duplicate native permissions along with the native permissions in a review.
These settings allow an administrator to tune the timeout values for various data production operations to achieve optimal performance in each environment. The timeout values are expressed in milliseconds. The default values should suffice for the majority of installations.
The interval between heartbeat updates for data production jobs. The default is 2 minutes (120000 ms).
The amount of time, after the last heartbeat update, that a running job is deemed to be in an idle state where the data production processing has halted. The default is 6 hours (21600000 ms).
The additional amount of time, combined with the Job idle cutoff timeout, that will pass before a runtime instance can detect and clean up data production jobs with a different runtime identifier that have an idle state. The default is 1 hour (3600000 ms), which combined with the default cutoff timeout sets up an overall 7 hour default.