test

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

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