Portal Server performs best when the web container in which it runs is tuned to optimize Portal Server performance. So, you must tune the Application Server instances that host Portal Server. For this module, Portal Server runs in the Application Server instances in the pstest cluster.
In the portal service reference configuration, no other component or application besides Portal Server runs in the Application Server 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 Portal Server might negatively impact the performance of other components.
This section consists of the following procedures:
Tuning the Application Server instances that host Portal Server is performed by using the perftune utility. This utility runs the amtune utility and also performs some tuning of Portal Server thread usage. For additional information about amtune, see Part I, Basic Performance Tuning, in Sun Java System Access Manager 7.1 Performance Tuning and Troubleshooting Guide.
On ps1, 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_TUNE_WEB_CONTAINER=false AMTUNE_MODE=REVIEW
Also, change all variables that are named CONTAINER_* to point to the as-cluster-inst-ps1 instance:
In a Solaris zones deployment, also set AMTUNE_TUNE_OS=false.
Run the perftune utility.
# /opt/SUNWportal/bin/perftune directory-manager-password app-server-admin-password
The utility proposes suggested changes.
Review the 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 changes.
Repeat Step 4.
The utility will make all the changes proposed in Step 4.
Restart the computer.
Restarting the computer will affect changes to the operating system.
Start the Portal Server instance.
Starting Portal Server will affect changes made to the web container. You start Portal Server by starting the Application Server instance in which it is deployed.
# /opt/SUNWappserver/sbin/asadmin start-instance --user admin as-cluster-inst-ps1
When prompted, type the app-server-admin-password.
The response should indicate that you successfully started the instance:
Command start-instance executed successfully.
Repeat the procedure in To Tune the Application Server Instance for Portal Server on ps2, except for the following:
Replace all occurrences of ps1 with ps2.