Oracle^® Business Intelligence Enterprise Edition Deployment Guide > Other Deployment-Related Topics > Improving Oracle BI Web Client Performance >

Static File Caching

Performance of the Oracle BI web client can be improved by caching small frequently used static files such as .javascript, .gif and .css files. By enabling caching and content expiration on the web server, web browsers can be directed to how often they should reload the static files from the server.

NOTE:  Static file caching is enabled by default for Oracle HTTP Server when Oracle Business Intelligence is deployed using Oracle Application Server. The Oracle HTTP Server must be installed along with the J2EE Server for this automatic configuration to occur. The content expiry time is set to seven days by default.

The procedures shown are for the following web servers:

• Microsoft IIS Server
• Apache HTTP Server
• Oracle Containers for J2EE (OC4J)

As an example, static file content is set to expire after seven days.

Microsoft IIS Server

To set up static file caching for Microsoft IIS Server

1. On the Web Server machine, navigate to Start > Settings > Control Panel > Administrative Tools.
2. Run Internet Service Manager.
3. In Internet Service Manager, right-click on Default Web Site.

   NOTE:  You may specify content expiration at the individual web site folder level or virtual directory level or for a file.

4. In Default Web Site Properties, click the HTTP Headers tab.
5. Check the Enable Content Expiration check box.
6. Select Expire After, and specify the value of seven.

   NOTE:  This sets expiration for static files after seven days. Specify a value appropriate for your deployment.

7. Restart IIS

Apache HTTP Server

Use the procedure below to specify static file caching and content expiration when your HTTP Server is Apache based.

To set up static file caching for Apache HTTP Server

1. On the Web server machine, open the file httpd.conf for editing.

   This file is located in the Web server installation directory.

2. Verify that the following directive is included and not commented out:

   LoadModule expires_module modules/mod_expires.so

   NOTE:  For Apache versions prior to 1.3.15 on Windows, the directive is LoadModule expires_module modules/ApacheModuleExpires.dll

3. Add the following lines to the file below the directive specified in step 2:

   ExpiresActive On

   <IfModule mod_expires.c>
   ExpiresByType image/gif "access plus 7 days"
   ExpiresByType image/jpeg "access plus 7 days"
   ExpiresByType application/x-javascript "access plus 7 days"
   ExpiresByType text/css "access plus 7 days"
   </IfModule>

   NOTE:  As an example, content is set to expire in seven days. Set a value that is appropriate for your deployment.

4. Save the file.
5. Restart the HTTP Server.

Oracle Containers for J2EE (OC4J)

Oracle Containers for J2EE (OC4J) may be used as a standalone web server. OC4J can also be configured for static file caching. Use the following procedure to configure static file caching for OC4J.

Use the orion-web.xml file, located in one of the following directories:

• $ORACLE_HOME\ j2ee\home\application-deployments\analytics\analytics
• $ORACLE_HOME/ j2ee/home/application-deployments/analytics/analytics

To set up the static file Caching for OC4J

1. Open the BI application orion-web.xml file for editing.
2. Add the following lines into <orion-web-app> session:

   <expiration-setting expires="604800" url-pattern="*.css"/>
   <expiration-setting expires="604800" url-pattern="*.js"/>
   <expiration-setting expires="604800" url-pattern="*.gif"/>
   <expiration-setting expires="604800" url-pattern="*.jpg"/>
   <expiration-setting expires="604800" url-pattern="*.png"/>

   NOTE:  As an example, the content expiration is set to seven days where the time unit is seconds. Set this to a value that is appropriate for your deployment.

3. Restart OC4J.