Managing the Oracle BI Presentation Services Cache Settings

7-36 System Administrators Guide for Oracle Business Intelligence Enterprise Edition LocationMatch Note the following: ■ Modify the LoadModule directive based on where and how you installed the plug-in. ■ The IfModule directive enables the connection to Oracle WebLogic Server. See Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server for more information about the connectivity options, including how to configure a cluster and SSL considerations. ■ The LocationMatch directives are used to route all dynamic requests to Oracle WebLogic Server. Be sure to include the SetOutputFilter DEFLATE directive, which enables GZip compression for all dynamic requests. 3. Save and close the file. To add configuration directives for handling static files: 1. Locate the httpd.conf file for your Apache HTTP Server. 2. Open the file for editing and add directives similar to the following: Alias analytics ORACLE_HOMEbifoundationwebapp Directory ORACLE_HOMEbifoundationwebapp Disable cross-server ETags FileETag none Enable compression for all files SetOutputFilter DEFLATE Dont compress images SetEnvIfNoCase Request_URI \.?:gif|jpe?g|png no-gzip dont-vary Enable future expiry of static files ExpiresActive on ExpiresDefault access plus 1 week DirectoryIndex default.jsp Directory Restrict access to WEB-INF Location analyticsWEB-INF Order Allow,Deny Deny from all Location Note the following: ■ You must ensure that Apache HTTP Server has access to the static files for the Oracle BI Web client in ORACLE_HOMEbifoundationwebapp. Ensure that the Web server is running and has read access to this location. ■ The Alias and Directory entries tell Apache HTTP Server to handle requests for static files rather than routing them to Oracle WebLogic Server. Note the following about the directives related to compression and static file expiry: – FileETag FileETag none This directive tells the Web server to disable generation of ETag headers in the response. Default ETag generation for Apache HTTP Server is tied to the file system for a single server, so generating ETags is not recom- mended. – Compression Related Directives Managing Performance Tuning and Query Caching 7-37 SetOutputFilter DEFLATE Dont compress images SetEnvIfNoCase Request_URI \.?:gif|jpe?g|png no-gzip dont-vary These directives ensure that Apache HTTP Server compresses all files except images. Typically, images are already compressed and do not bene- fit from additional compression. – Control of Expires Header Enable future expiry of static files ExpiresActive on ExpiresDefault access plus 1 week This fragment tells Apache HTTP Server to enable setting the Expires header. In this example, the default expiration is set to one week after the first time the file was accessed by the client. You can increase this time period, but ensure that static files are refreshed often enough to handle any patches or updates made on the static files. – Handling Default URLs DirectoryIndex default.jsp This directive provides a fallback handler when a user requests the ana- lytics URL without specifying any content under it. This URL is then routed to Oracle WebLogic Server for further processing. ■ The final directive restricts access to the WEB-INF folder. This folder is part of the J2EE containers deployment descriptor and must not be exposed to Web clients. 3. Save and close the file.

7.10.2 Configuring Oracle HTTP Server for Static File Caching

Configuration for Oracle HTTP Server is similar to configuration for Apache HTTP Server, except that you do not need to download and install the plug-in because the mod_wl_ohs.so module is installed by default with Oracle HTTP Server. Some configuration is performed in the mod_wl_ohs.so module directly, and some configuration is performed in httpd.conf. See Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server for full information. 7-38 System Administrators Guide for Oracle Business Intelligence Enterprise Edition