Configuring Partitioning Request Objects

Partitioning is also maintained using RequestDefinition objects that are defined for each request type. These objects control how each request-type is processed. For example, these objects define the number of threads that run for each request on the instances of IdentityIQ running on a specific machine. The RequestDefinition objects must be defined on each machine, host, in a cluster.

Note: By default the maximum number of threads to run on each host is set to 1. This number can be changed to maximize performance in your environment, but should be done with caution and only after testing and tuning for your environment.

The following RequestDefinition objects are available:

• Aggregation Partition – define the maximum number of threads to run on each host during account aggregations

• Identity Refresh Partition – define the maximum number of threads to run on each host during identity refresh

• Manager Certification Generation Partition – define the maximum number of threads, the error action, and orphan action for partitioned manager certification requests

• Role Propagation Partition – define the maximum number of threads to run on each host during role propagation

To work with the RequestDefinition objects, go to the IdentityIQ Debug page and select RequestDefinition from the Select an Object dropdown list.