Tuning IBM Content Cortex directory servers

The performance tuning topics in this section apply to all IBM Content Cortex components and all supported directory servers unless otherwise specified.

Tuning Lightweight Directory Access Protocol (LDAP) single entity lookup behavior

You can adjust the behavior of LDAP single entity lookup returns to best match your LDAP environment configuration.

When multiple LDAP directories are configured, the default setting for single entity lookup is to search across all directories, return the first match, and log a warning if more than one match is found.

This default behavior might not be the most appropriate for your environment. For example, if your system is configured with guaranteed unique shortname or login names, the continued search is an unnecessary performance hit. In this case, you might want the returns to stop after the first hit.

However, if your system has duplicate login instances, the single first hit return might not be the search result you are looking for. In that case, a warning in the log might be easily missed, and you might prefer to see an exception message.

You can change the way your searches handle duplicate returns by adjusting the com.filenet.engine.directory.DuplicateHandling JVM argument. The following settings for com.filenet.engine.directory.DuplicateHandling control the search return behavior:
  • 0 - Stop on first hit
  • 1 - Check for duplicates but log an error only (default behavior)
  • 2 - Check for duplicates and report an exception if found

Tuning Lightweight Directory Access Protocol (LDAP) provider cache

By default, the WebLogic Lightweight Directory Access Protocol (LDAP) provider cache TTL parameter setting is 60 seconds. However, frequent LDAP searches can degrade the performance of FileNet® P8 components.

Consider increasing this value to reduce the frequency of LDAP searches for authentication.

Optimizing the Security Directory Server database for IBM Content Cortex components

To improve performance and query speeds of IBM Content Cortex components, optimize the Security Directory Server database on a regular basis and after significant database updates.

To optimize the Security Directory Server database, use the Optimize Database task in the Security Directory Server Configuration tool. This tool uses the DB2® runstats command and updates statistical information that is used by the query optimizer for all the directory server tables.