Performance Tuning Guide

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

Tuning Your Portal Domain

Key aspects of portal performance are managed at the domain level. These include:

 

Tuning Your Domain Configuration

Optimally, when you deploy, you need to create a new domain that is configured for your production environment. However, if you have deployed a development domain and want to use it for production, you must change your domain environment settings to optimize performance.

Note: It is not recommended to use a development domain for production, see Creating WebLogic Domains Using the Configuration Wizard for more information.

The domain settings are managed by the setDomainEnv.cmd (or setDomainEnv.sh) script which is found in your domain directory. By default, the script is found in: <BEA_HOME>/user_projects/domain_name/bin/setDomainEnv.cmd/sh.

To edit this file, open it in a text editor.

Table 2-1 lists the start script settings and their appropriate values for a production domain. Remember if you are using a domain that was created for production mode, you do not need to modify the configuration.

Table 2-1 setDomainEnv Settings  
Flag Name
Production Mode Setting
Notes
DOMAIN_PRODUCTION_MODE
true
  • Indicates whether you are in a production mode or a development mode. Default is false for domains created in development mode and true for domains created in production mode.
iterativeDevFlag
false
  • Checks for updated files and if found, rebuilds and redeploys the application. Disable this option to prevent checking for changed Workshop for WebLogic files. Default is true for domains created in development mode and false for domains created in production mode.
debugFlag
false
  • Used in start scripts to set debugging options and indicate if the Workshop for WebLogic Debugger should be started. When switched to false, you save the resource overhead used for debugging.
  • Default is debugFlag=true for domains created in development mode and debugFlag=false for domains created in production mode.
testConsoleFlag
false
  • Enables the JWS test view.
  • Verify by checking the log for: wlw. testConsole = false.
  • Default is true for domains created in development mode and false for domains created in production mode.
logErrorsToConsoleFlag
false
  • Controls logging functionality.
  • Verify by checking the log for: wlw.logErrorsToConsole = false
  • Saves you additional logging. The trade-off is that you may see exceptions more easily when this is set to true (without checking the log).
  • Default is true for domains created in development mode and false for domains created in production mode.
verboseLoggingFlag
false
  • If true, override the default LOG4J_CONFIG_FILE (workshopLogCfg.xml) with workshopLogCfgVerbose.xml.
  • Priority value in the default file is warn; in the verbose version it is debug.
  • Verify by checking the log for: log4j.configuration = workshopLogCfg.xml instead of workshopLogCfgVerbose.xml
  • You can also start in verbose mode using startWebLogic.cmd verbose.
  • Saves you debugging overhead.
  • Default is false for both domains created in development mode and in production mode.
pointbaseFlag=
false
  • Indicates whether Pointbase should be started.
  • Verify by checking for a running Pointbase process.
  • Saves you the resource overhead of starting Pointbase when it is not needed.
  • Default is true for domains created with Pointbase as the database.

 

Removing Debugging Tools from Your Domain

When deploying a domain, you should remove the debug.properties file from the domain directory. Although this file is helpful during development, debugging should not be done in production environments.

 

Tuning Log Levels

WebLogic Server has several logging features available. When using the WebLogic logging infrastructure, make sure that the server logs at an appropriate level and to the correct location. For example, a production system logging at DEBUG or TRACE levels can produce gigabytes of log data fairly quickly when writing to a log file. A production system should have logging set to the INFO level or higher. This can be done from the command line, from MBeans, or from the console. See the WebLogic Server document Configuring Log Files and Filtering Log Messages for more detailed information on WebLogic Server logging.

Additionally, WebLogic server internally processes all log messages before writing these messages to the logging infrastructure. In a production system where the logging level has been set to INFO or NOTICE, having the server process all DEBUG messages, for example, can add significant overhead. It is a good idea to match the internal WebLogic Server log processing level to the logging framework level. Do this by specifying the -Dweblogic.log.LoggerSeverity flag to the server at startup.


  Back to Top       Previous  Next