Set up Fast Response Cache Accelerator (AFPA): IBM HTTP Server
System Administration IBM HTTP Server documentation

Setting up the Fast Response Cache Accelerator

This section describes tuning tips to help improve the performance of your server. Not all tips have been tested, nor will all tips have the same impact in all environments. Use your judgment when deciding which tips to implement on your server. Make a backup copy of your server configuration file, before making any modifications. You can also see the Fast Response Cache Accelerator (FRCA) referred to as the Cache Accelerator. Links to related topics appear at the end of this section.
Pertains to Windows NT users Pertains to Windows 2000 users
Pertains to Windows NT users Pertains to Windows 2000 users

Customizing cache management with the Cache Accelerator

The Cache Accelerator can improve the performance of the IBM HTTP Server when serving static content, such as text and image files.

Because the Cache Accelerator cache automatically loads during server operation, you do not have to list the files to cache in your server configuration file. The server automatically caches changed pages again and removes outdated pages from the cache.

The Cache Accelerator supports servers with multiple IP addresses. Currently, support is not available for running the Cache Accelerator on a proxy server.

Enabling and configuring the Cache Accelerator

By default, the IBM HTTP Server enables the Cache Accelerator. To disable the Cache Accelerator, remove or comment out the AfpaEnable and AfpaCache directives using the Administration Server.

Customizing logging for the Cache Accelerator

  1. Set the following directives from the Administration Server:
    • AfpaEnable - Go to Performance > Server Settings and click Yes, by Enable Fast Response Caching.
    • AfpaCache - Go to Performance > Set Cache and click Turn on Fast Response Caching within this scope.
    • AfpaLogFile file_path_and_name - Go to Performance > Server Settings and fill in the Fast Response Cache Log file name.
  2. Click Submit.
  3. Restart the server.

By default, the IBM HTTP Server records that a Web browser has accessed a file in a server disk log. If you do not need this access logging, turn the logging off for better server performance. To set logging off, edit the httpd.conf configuration file and insert a comment character (#) at the beginning of the AccessLog line.

Enabling high speed caching of servlets and JavaServer Pages files

You can use the IBM HTTP Server Cache Accelerator in conjunction with WebSphere Application Server to cache certain dynamically generated servlet and JavaServer Pages (JSP) files. For details on how to enable this capability, see the External Caching description in the WebSphere Application Server InfoCenter documentation. From the WebSphere Application Server InfoCenter V4.0, click Developing applications > 4.5.2: External caching > Enabling high speed caching of servlets and JSP files with IBM HTTP Server for Windows 2000/NT.

 
Finding related information
     (Back to the top)