This guide provides performance tuning information for Sun JavaTM System Access Manager, including how to run the Access Manager tuning scripts. You can run these scripts to tune Access Manager and its related components.
Before you use this guide, Access Manager and other Sun Java Enterprise System component products such as Directory Server, Web Server, and Application Server must be installed. For information about installing these products, see the one of the following books:
Tuning Access Manager and its related components is an iterative process that can vary for different deployments. The Access Manager tuning scripts try to apply the optimal tuning parameter settings. However, each deployment is unique and might require further customization to suit specific requirements.
You can run the Access Manager tuning scripts in two modes:
REVIEW mode (default): The scripts return tuning recommendations in the amtune debug log file, but they do not make any actual changes to the deployment.
CHANGE mode: The scripts make the tuning changes to the deployment that are defined in the amtune-env file.
Therefore, it is recommended that you first run a script in REVIEW mode and check the recommended changes in the debug log file. Run a script in CHANGE mode only after you have reviewed the recommended tuning changes that will be applied to your deployment.
This guide includes the following information:
Chapter 2, Access Manager Tuning Scripts describes how to run the Access Manager tuning scripts.
Chapter 3, Directory Server Tuning describes how to tune Sun Java System Directory Server.
Chapter 4, Distributed Authentication UI Server TuningChapter 4, Distributed Authentication UI Server Tuning describes tuning considerations for a Distributed Authentication UI server.
Chapter 5, Tuning Considerations provides considerations for the Solaris OS, Linux OS, and third-party web containers, including IBM WebSphere Application Server and BEA WebLogic Server.