Skip navigation.

Performance Tuning Guide

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

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

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.

  1. 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.
  1. Open the web.xml file in a text editor.
  2. Add the following lines
  3. <context-param>
    	<param-name>portalFileDirectory</param-name>
    	<param-value>/</param-value>
    </context-param>
  4. Save the new web.xml file.
  5. Redeploy your web application.

 


Content Management Guidelines

Review Tuning for Content Management on page 3-7.

 

Skip navigation bar  Back to Top Previous Next