To run a tuning script, use the following syntax:
amtune-script admin_password dirmanager_password [ as8_admin_password ] |
The tuning script parameters are:
amtune-script is one of the tuning scripts: amtune, amtune-identity, amtune-os, amtune-ws61, amtune-as7, amtune-as8, or amtune-prepareDSTuner.
admin_password is the Access Manager Administrator password.
dirmanager_password is the Directory Manager (cn=Directory Manager) password.
as8_admin_password is the Administrator password that is required if you are tuning Application Server (WEB_CONTAINER is set to AS8).
This section describes the basic steps to run an Access Manager Tuning script.
If you have not run the scripts in REVIEW mode, ensure that AMTUNE_MODE is set to REVIEW (default value) in the amtune-env file.
Edit other parameters in the amtune-env file, depending on the components you want to tune:
Access Manager amtune-env file parameters
Installation environment tuning parameters
Application Server 8 Tuning Parameters (if Application Server 8 is the web container)
To tune the Directory Server that supports Access Manager, see Chapter 3, Directory Server Tuning.
In REVIEW mode, run either the amtune script or one of the component scripts.
Review the tuning recommendations in the debug log file. If needed, make changes to the amtune-env file based on this run.
If you are satisfied with the tuning recommendations from the REVIEW mode run, set AMTUNE_MODE to CHANGE in the amtune-env file.
In CHANGE mode, run either the amtune script or one of the component scripts. For example, to tune the Solaris OS, run amtune-os, as follows:
# ./amtune-os admin_password dirmanager_password |
Check the debug log file for the results of the run.
In CHANGE mode, the amtune script might need to restart the Web container and Access Manager. In some instances, amtune might also recommend a system restart.