test

Sun Java System Reference Configuration Series: Portal Service on Application Server Cluster

Tuning Portal Server Instances

Consider the following issues when tuning Portal Server instances to maximize performance:

Impact of Java DB on Performance

The Portal Service on Application Server Cluster reference configuration includes an instance of Java DB running on ps1. Java DB is the default database used to store configuration and membership data for Portal Server's community feature. Java DB is also used by portlet applications such as wiki, fileshare, and survey.

However, the use of Java DB has an impact on the overall performance of Portal Server. If you do not need the community feature and are not using a portlet application that requires Java DB, you can improve portal service performance by disabling the use of Java DB by the portal desktop and then shutting down the database.

Caution – Caution –

Be careful not to shut down Java DB without disabling Java DB for the desktop, as this action seriously degrades performance.

This section consists of the following procedures:

ProcedureTo Disable the Use of Java DB by the Desktop

  1. On ps1, change to the following directory:

    # cd /var/opt/SUNWportal/portals/portal-ID/config

  2. Edit the communitymc.properties file.

    Remove the jdo entry from the manager.contributors list.

  3. Restart the Portal Server instance by restarting the Application Server instance in which it is deployed.

    1. Stop the Application Server instance.

      # /opt/SUNWappserver/sbin/asadmin stop-instance --user admin as-cluster-inst-ps1

      When prompted, type the app-server-admin-password.

      The response should indicate that you successfully stopped the instance:

      Command stop-instance executed successfully.

    2. Start the Application Server instance.

      # /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.

  4. Repeat Steps 1 through 3 on ps2, except for the following:

    Replace all occurrences of ps1 with ps2, including the instance ID (replacing ps-inst-ps1 with ps-inst-ps2).

ProcedureTo Shut Down Java DB

This procedure is performed only on ps1 where the Java DB instance is running (see Figure 6–1).

  1. Run the following command on ps1:

    # java -cp /opt/SUNWjavadb/lib/derbynet.jar org.apache.derby.drda.NetworkServerControl shutdown

Tuning Application Server Instances

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:

ProcedureTo Tune the Application Server Instance for Portal Server on ps1

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.

  1. On ps1, change to the following directory:

    # cd /opt/SUNWam/bin/amtune

  2. Open the amtune-env file in a text editor.

  3. 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:

    CONTAINER_*=/var/opt/SUNWappserver/nodeagents/ps1.pstest.com/as-cluster-inst-ps1

    Note –

    In a Solaris zones deployment, also set AMTUNE_TUNE_OS=false.

  4. Run the perftune utility.

    # /opt/SUNWportal/bin/perftune directory-manager-password app-server-admin-password

    The utility proposes suggested changes.

  5. Review the suggested changes.

    If no undesired changes are proposed, continue to the next step.

  6. Modify the amtune-env file with the following value and save the changes.


    AMTUNE_MODE=CHANGE

  7. Repeat Step 4.

    The utility will make all the changes proposed in Step 4.

  8. Restart the computer.

    Restarting the computer will affect changes to the operating system.

  9. 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.

ProcedureTo Tune the Application Server Instance for Portal Server on ps2

  1. 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.