Performance Tuning Guide

Performance Tuning Checklists

Portal Framework Guidelines

Table A-1 Portal Framework Guidelines

Guideline Question	How to Verify
Is the `portalControlTreeCache MaxSize` set to the correct size for your portal?	See portletControlTreeCache on page B-2.
Are entitlements enabled? If yes, is `control-resource-cache` size is set correctly?	See Tuning for Entitlements on page 3-5.
If you do not need to support multiple locales, is localization disabled?	See Disabling Unused Services on page 3-2.
Is `jspPageCheckSecs` in `weblogic.xml` is set to -1?	See Modifying WebLogic Server Settings on page 4-4.
Is `servletReloadCheckSecs` in `config.xml` is set to -1?	See Modifying WebLogic Server Settings on page 4-4.
Is validation turned off?	See Modifying Portal Framework Settings on page 4-2.

Administration Portal Guidelines

You can improve the performance of the Administration Portal by making adjustments. You can decrease the time it takes to create a new desktop and also decrease the amount of time to search for existing desktops using the Administration Portal.

Decreasing the Amount of Time It Takes to Create a Desktop

When you create a new desktop in the Administration Portal, a list of .portal files is used to populate the templates drop-down list. If all .portal files reside under the same directory under the web application directory, this drop-down list can be created quickly.

To take advantage of higher performance in building the drop-down list, you must define the portalFileDirectory in the web application's web.xml file.

Note: After making any changes, you must redeploy your web application for the changes to take effect. For more information about modifying web descriptor files, see Preparing The EAR File for Deployment in the Production Operations User Guide.

Navigate to the respective web.xml file. It is located in the WEB-INF subdirectory of your portal application directory. For example, if you are using the sample portal web application, the corresponding web.xml file is located at:

<BEA home>/weblogic81/samples/portal/portalApp/sampleportal/WEB-INF/web.xml.

Open the web.xml file in a text editor.

Add the following lines

<context-param>

	<param-name>portalFileDirectory</param-name>

	<param-value>/</param-value>

</context-param>

Save the new web.xml file.

Redeploy your web application.

Increasing Performance When Browsing Portal Resources

When browsing portal resources within the Administration Tools, you can increase the performance by using a system property.

To increase the performance of browsing the Administration Tools, set the following system property at runtime:

-Dwlp.enable.portal.tree.perf=true

After you set this property, the Administration Portal allows you to browse portal resources more quickly. However, when you add or delete a page or portlet, you need to close and re-open the parent node to reflect the change. This is because the portal resources tree is kept in memory and needs to be refreshed when you add or delete items.

Note: If this property is set to true, searching for desktops behaves differently. When you search for desktops within the Administration Portal you cannot navigate within the Administration Portal until the search is complete.

Content Management Guidelines

Review Tuning for Content Management on page 3-7.