Populating the Oracle BI Server Event Polling Table

Managing Performance Tuning and Query Caching 7-35

7.10 Improving Oracle BI Web Client Performance

You can improve the performance of the Oracle BI Web client by configuring your Web server to serve up all static files, as well as enabling compression for both static and dynamic resources. By enabling caching and content expiration on the Web server, Web browsers can determine how often to reload the static files from the server. In Oracle BI EE, static files are located in ORACLE_HOMEbifoundationwebapp. Follow the instructions for your Web server to set up static file caching and compression for the files located in this directory. The following sections provide example configurations: ■ Section 7.10.1, Configuring Apache HTTP Server for Static File Caching ■ Section 7.10.2, Configuring Oracle HTTP Server for Static File Caching

7.10.1 Configuring Apache HTTP Server for Static File Caching

This example configuration assumes that you have installed the Web server plug-in that allows Apache HTTP Server to proxy requests to Oracle WebLogic Server. Make sure that the PLUGIN_HOMElib directory is added to LD_LIBRARY_PATH, or equivalent for your operating system. The steps in this section show an example configuration only. You can adjust your configuration as needed. See Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server for full information. To add configuration directives for the plug-in: 1. Locate the httpd.conf file for your Apache HTTP Server.

2. Open the file for editing and add directives similar to the following:

LoadModule weblogic_module modulesmod_wl.so IfModule mod_weblogic.c WebLogicPort 9704 Debug OFF WebLogicHost localhost WLLogFile tmpwl-proxy.log IfModule LocationMatch analyticssaw\.dll. SetOutputFilter DEFLATE SetHandler weblogic-handler LocationMatch LocationMatch analytics.\.jsp. SetOutputFilter DEFLATE SetHandler weblogic-handler Note: See the following documents for full information about how to configure Oracle WebLogic Server to work with Web servers like Apache HTTP Server, Microsoft Internet Information Server Microsoft IIS, and Oracle HTTP Server: Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server 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