Bookshelf v7.5: Enabling HTTP Compression for Siebel Web Applications

Siebel Server Installation Guide for UNIX > Installing Siebel Web Server Extension > Post-Installation Tasks for Siebel Web Server Extension >

Enabling HTTP Compression for Siebel Web Applications

The use of HTTP compression between the browser and the Web server can improve the performance of Siebel eBusiness Applications over a wide-area network (WAN). Typically, you should consider enabling HTTP compression if a significant number of users access applications over a WAN for which network bandwidth may be a constraint.

The benefit of compression is even greater for users who access applications using standard interactivity, rather than high interactivity, because the latter is already optimized for network use.

However, if your users access applications mostly over a local-area network (LAN), turning on HTTP compression does not improve performance. Instead, it might create performance overhead related to the extra processing needed on both the client and the server sides to compress and decompress data.

HTTP compression is available for all supported Web server platforms without any additional installation. HTTP compression functionality is built into the Siebel Web Server Extension plug-in.

To make HTTP compression active, you must enable HTTP compression by setting the DoCompression parameter in the eapps.cfg file. The following section describes the steps involved for this procedure.

You can enable or disable HTTP compression as default functionality for all applications or selectively for individual applications. By default, HTTP compression is enabled for all applications.

To enable HTTP compression

Open the eapps.cfg file, located in the $SIEBEL_ROOT/SWEAPP_ROOT/bin, in a text editor. Do one or both of the following:

To enable HTTP compression as default functionality, set the DoCompression parameter to TRUE in the [defaults] section. If the DoCompression parameter is not present, add it.

To enable HTTP compression for an individual application, set the DoCompression parameter to TRUE in the section for that application. For example, in [/callcenter] set DoCompression = TRUE. If the DoCompression parameter is not present, add it.

NOTE: Setting a parameter for an individual application overrides the default setting that may appear in the [defaults] section. If a parameter is set as a default, then its value applies to all applications for which it is not overridden at the individual application level.

Save and close the eapps.cfg file.

Restart the Web server.

NOTE: Changes to the eapps.cfg file are not active until you restart the Web server.

To disable HTTP compression as a default or for an individual application, set DoCompression to FALSE in the appropriate section of the eapps.cfg file.