Access Manager performs best when the web container in which it runs is tuned to optimize Access Manager performance. So, you should tune the Application Server instances that host Access Manager. In this module, Access Manager runs in the Application Server's DAS instance.
In the portal service reference configuration, no other component or application besides Access Manager runs in the Application Server's DAS instance. However, if you run other components or applications in the same Application Server instance, then be aware that optimizing the Application Server instance for Access Manager might negatively impact the performance of other components.
Tuning the Application Server instances that host Access Manager is performed by using the amtune utility. For additional information about amtune, see Part I, Basic Performance Tuning, in Sun Java System Access Manager 7.1 Performance Tuning and Troubleshooting Guide.
Perform the following procedure on both am1 and am2..
Change to the following directory:
# cd /opt/SUNWam/bin/amtune
Open the amtune-env file in a text editor.
Confirm, or if necessary, modify the following values and save the changes.
WEB_CONTAINER=AS8 ASADMIN_PORT=80 DOMAIN_NAME=pstest.com AMTUNE_PCT_MEMORY_TO_USE=100 AMTUNEAMTU_MIN_PERM_SIZE_AS8=128 AMTUNE_MODE=REVIEW
In a Solaris zones deployment, also set AMTUNE_TUNE_OS=false.
Run the amtune utility.
# ./amtune directory-manager-password app-server-admin-password
The utility proposes changes to optimize Access Manager performance.
Review any suggested changes.
If no undesired changes are proposed, continue to the next step.
Modify the amtune-env file with the following value and save the change.
Repeat Step 4.
The utility runs a second time, but makes all the changes proposed in Step 4.
Restart the computer.
Restarting the computer will affect changes to the operating system.
Start the Access Manager instance.
# /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
When prompted, type the app-server-admin-password.