Configuring the Log Assertion to Record SOAP Messages

26-4 Oracle Fusion Middleware Performance and Tuning Guide AddOutputFilterByType DEFLATE applicationxhtml+xml AddOutputFilterByType DEFLATE textcss AddOutputFilterByType DEFLATE applicationxml AddOutputFilterByType DEFLATE imagesvg+xml AddOutputFilterByType DEFLATE applicationrss+xml AddOutputFilterByType DEFLATE applicationatom+xml AddOutputFilterByType DEFLATE applicationx-javascript AddOutputFilterByType DEFLATE texthtml SetEnvIfNoCase Request_URI \.?:gif|jpe?g|png no-gzip dont-vary SetEnvIfNoCase Request_URI \.?:exe|t?gz|zip|bz2|sit|rar no-gzip dont-vary SetEnvIfNoCase Request_URI \.?:pdf|doc?x|ppt?x|xls?x no-gzip dont-vary SetEnvIfNoCase Request_URI \.avi no-gzip dont-vary SetEnvIfNoCase Request_URI \.mov no-gzip dont-vary SetEnvIfNoCase Request_URI \.mp3 no-gzip dont-vary SetEnvIfNoCase Request_URI \.mp4 no-gzip dont-vary IfModule For more information about mod_deflate, refer to: http:httpd.apache.orgdocs2.0modmod_deflate.html

26.3 Tuning WebCenter Application Configuration

This section describes parameters that enable administrators to tune performance of WebCenter applications. This section includes the following: ■ Setting HTTP Session Timeout ■ Setting JSP Page Timeout ■ Setting ADF Client State Token ■ Setting ADF View State Compression ■ Setting MDS Cache Size and Purge Rate ■ Configuring Concurrency Management

26.3.1 Setting HTTP Session Timeout

To manage overall resource usage, adjust the applications http session timeout value, in minutes, in the web.xml file. In general, shorter session timeout values correspond to less memory and CPU usage on the server. If you must modify this property, post deployment, you must edit web.xml manually. See Editing web.xml Properties in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. The following is a sample snippet of web.xml: session-config session-timeout 45 session-timeout session-config

26.3.2 Setting JSP Page Timeout

You can specify an integer value, in seconds, after which any JSP page will be removed from memory if it has not been requested in the web.xml file. This frees up resources in situations where some pages are called infrequently.