Performance Tuning Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Performance Tuning Checklistst

This appendix provides checklists and tips for the following components of WebLogic Portal:

 

Portal Framework Guidelines

Table A-1 Portal Framework Guidelines
Guideline Question
How to Verify
Is the WebLogic Server well tuned?
See Tuning Your WebLogic Server
Is the JVM properly tuned?
See Tuning Your JVM
Is the WebLogic Portal database tuned?
See Tuning Your Database
Is the Domain running in Production mode?
SeeTuning Your Domain Configuration
If you do not need to support multiple locales, is localization disabled?
See Disabling Unused Services.
Are Campaigns tuned properly?
See Tuning for Campaigns
Are Entitlements enabled?
If yes, is control-resource-cache size is set correctly?
See Tuning for Entitlements
Is the Content Management System optimal?
See Tuning for Content Management
How many visible PageFlow portlets are in the portal?
See Tuning for PageFlow Portlets
Is the portalControlTreeCache MaxSize set to the correct size for your portal?
See Optimizing Your Portal Control Tree
Is validation turned off?
See Modifying Portal Framework Settings.
Is jspPageCheckSecs in weblogic.xml is set to -1?
See Modifying WebLogic Server Settings.
Is servletReloadCheckSecs in weblogic.xml is set to -1?
See Modifying WebLogic Server Settings.
Are sessions replicated? If so what persistent-store-type is used?
See Modifying WebLogic Server Settings
Has the application been performance tested?
See Approaches to Performance Testing on the Oracle Technology Network web site.

 

Portal Administration Console Guidelines

You can improve the performance of the Portal Administration Console. Specifically, you can decrease the time it takes to work with desktops and to browse portal resources.

This section includes the following topics:

Creating Desktops

When you create a new desktop in the Administration Console, 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 “Portal Web Application Deployment Descriptors” in the Production Operations Guide.
  1. Navigate to the respective web.xml file. It is located in the WEB-INF subdirectory of your portal application directory.
  2. Open the web.xml file in a text editor.
  3. Add the following lines
    4. <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.

  Back to Top       Previous  Next