| Oracle Argus Safety Installation Guide Release 7.0.3 E40575-02 |
|
 Previous |
 Next |
This chapter describes how to enable IIS HTTP Compression on a Windows 2008 Server.
This feature is required when the pipeline between the Web Server and the IIS Client have low bandwidth or have high amounts of data usage.
This chapter includes discussions of the following:
This section includes the following sections:
By default, HTTP compression is disabled in Windows 2008 but can be enabled as necessary. Reasons for enabling compression include the following:
The bandwidth between the IIS Web Server and the IE Client(s) is of a low speed.
The bandwidth between the IIS Web Server and the IE Client(s) is high speed but has high utilization.
Reducing overall traffic between the IIS Web Server and the IE Client(s).
Although implementing IIS Compression proves to be of value to the customer, there is a increase in CPU usage on the Web Server. When compression is enabled, every time a non static page (ASP, ASPX) is requested, the page is compressed on the fly before sending to the client. This puts some overhead on the Web Server CPU however, based on internal testing web server load is usually very minimum. Static Pages such as HTML, JS, HTM pages are compressed only once and then stored in a cache on the Web Server for later requests.
Due to the above, the Web Servers should be monitored to prevent a CPU bottleneck from occurring which would decrease performance rather than increasing it.
Use the following procedure to enabled HTTP Compression in IIS 7:
Open ”Internet Information Services (IIS) manager” from Control Panel -> Administrator Tools.
Browse to the ”Argus Safety Web” web site.
Double click ”Compression” in the Features View.
Check both options:
Enable dynamic content compression
Enable static content compression
|
Note: To enable compression, the feature option must be installed as part of the Windows installation. |
This section includes discussions on the following:
IIS Caching is supported in Windows 2008. IIS Caching is required to prevent the web server from having to re-serve certain files to the IE Client when the file has not changed. In other words, files such as Images do not change on a day-to-day basis and once they are sent to the IE client they should not be sent again each time the client requests the file. The local IE client should keep a local cache copy of the file and use the local file instead.
Before IIS Caching will function properly:
IIS must be set up properly
The local IE client settings must be set up correctly
Currently, there are currently no known effects of enabling caching on the Web Server. However, enabling cache should only be used on files / folders where the files are not dynamic or do not change daily. Certain files, such as .ASP and .ASPX files, should never be cached.
Use the following procedure to enable / verify IIS caching (Default is turned on from Argus Installation):
Open ”Internet Information Services (IIS) manager” from Control Panel -> Administrator Tools.
Browse to the ”Argus Safety Web” website.
Double click the ”HTTP Response Headers” option.
Ensure ”Cache Control” header with value of ”no-cache” exists.
Click the ”Set Common Headers” option.
Ensure that ”Expire Web Content” is checked and the option ”Immediately” is selected.
Apply and changes.
Click on the ”PDFReports” Folder.
Double click the ”HTTP Response Headers” option.
Ensure ”Cache Control” header does not exist.
Click the ”Set Common Headers” option.
Ensure that ”Expire Web Content” is unchecked.
Repeat the same steps for ”UploadedLetters” (Steps 9-12)
For each of the following folders, the same settings exist (Steps 9-12). In addition, verify on the ”Set Common Headers”, the ”After” option is selected and configured for the specified number of days as seen next to each folder below:
Css – 15 Days Expiration
Js – 1 Day Expiration
Img – 15 Days Expiration
This section includes information about the following:
IE Caching works directly with IIS Caching. If IIS Caching is used, you must turn on IE Client Caching otherwise caching will not occur.
In IE Client, there are some options on the caching tab that you should be aware of. The following table lists and describes IE Caching Tab Options.
| Option | Description |
|---|---|
| Every Time I visit the Web Page | Selecting this option will not cache a single file. Every time a file is requested, IE will request the Server to re-send all files. This option should never be used as performance will suffer severely |
| Every Time I Start Internet Explorer | Selecting this option will cache files only until the browser is closed. Upon closing the IE window, all cache will be expired. This option will provide some performance enhancement when a user visits the same page multiple times within a single browser session |
| Automatically | Selecting this option will allow IE to make a decision if a file should be cached or not. This option automatically performs the same function as "Every Time I Start Internet Explorer". In addition, after a file has been request so many time, IE will automatically cache the file even after the browser is closed. If the file has been cached and a new version of the file exists on the Web Server, the new version will be downloaded to the client. This is the option that should be used for best performance. |
| Never | Selecting this option will cause IE to always cache every file which can cause problem with sites that have dynamic data and so this should not be used. Also, if a file has been updated on the server due to an upgrade, the new file will not be sent to the client. |
Use the following procedure to enable IE caching:
Open Internet Explorer.
Select Tools=> Internet Options.
When the Internet Options dialog box opens:
Select the "General" Tab.
Locate the Browsing history section and click Settings.
When the Temporary Internet Files and History Settings dialog box opens:
Select Automatically.
Click OK.
Close the Internet Explorer browser and restart it to begin caching.
|
 Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|