Sun Java System Access Manager 7.1 Performance Tuning and Troubleshooting Guide

Related Systems Tuning

In this phase, you manually tune Directory Server, any Web Servers that host Web Policy Agents, and any Application Servers that host J2EE Policy Agents. The typical tuning steps are as follows:

  1. Run amtune to tune the Access Manager system. For more detailed information, see Chapter 2, Access Manager Tuning Scripts.

  2. Follow the amtune onscreen prompts to tune the related Directory Server configuration instances. The following is an overview of the primary tuning steps you must complete:

    1. Increase the nsslapd-dbcachesize value.

    2. Relocate nsslapd-db-home-directory to the /tmp directory.

    For detailed information, see the Directory Server documentation.

  3. Manually tune the user Directory Server user database instance if one is used. The following is an overview of the primary tuning steps you must complete:

    1. Increase the nsslapd-dbcachesize value.

    2. Relocate the nsslapd-db-home-directoryto the /tmp directory.

  4. If the Access Manager sub-realm is pointing to an external Directory Server user database, then manually tune the sub-realm LDAP connection pool.

    The amtune script tunes only the LDAP connection pools of the root realm. See Tuning the LDAP Connection Pool and LDAP Configurations. You can configure the following parameters on LDAPv3IDRpo:

    1. LDAP Connection Pool Minimum Size

    2. LDAP Connection Pool Maximum Size

  5. If you have installed a Web Policy Agent on a Sun Web Server, then manually tune the Web Server. You must configure the following parameters in the magnus.conf:

    • RqThrottle

    • RqThrottleMin

    • RqThrottleIncrement

    • ConnQueueSize

    If Access Manager is deployed on a Sun Web Server, the amtune script will modify the Web Server magnus.conf file. You can copy the changes and use the changed values in the Web Policy Agent Web Server.

  6. If you have installed a J2EE Policy Agent on an application server, seeThird-Party Web Containers for instructions on manually tune both the J2EE Policy Agent and the application server. You must configure settings for heap sizes and for garbage collection (GC) behaviors.