Set up caching in the proxy server

This page provides information on caching static and dynamic content in the proxy server.

Complete the following steps to configure a proxy server such that it can cache static and dynamic content.

 

1. Set the object cache instance for size, disk offload location, and other such capabilities, in the admin console. Click Servers > Server Types > WebSphere proxy servers > proxy_server_name > HTTP proxy server settings > Proxy cache instance config.

   Repeat these steps on any nodes that have a proxy server.

2. Select the proxy cache store instance and enable configuration attributes such as cache size, disk offload, and cache replication.

   For disk offload, IBM recommends that the location be set to a dedicated disk partition.

3. Enable caching at the proxy server, in the admin console. Click Servers > Server Types > WebSphere proxy servers > proxy_server_name > HTTP proxy server settings > Proxy settings page in the admin console.

4. Select Enable caching and choose a cache instance from the drop-down box.

   1. To enable dynamic content to be cacheable with the proxy server, in the admin console ...

      Servers > Server Types > WebSphere proxy servers > proxy_server_name > HTTP proxy server settings > Proxy settings , and then select Cache dynamic content. You enable cacheablity and invalidation of dynamic content when you enable servlet caching on the appserver, and specifying the cache criteria in a cachespec.xml file that is associated with that application. Invalidations are received by connecting to the cache update URI that is associated with the invalidation servlet hosted on the appserver cluster.

      Dynamic content is content that an application, that is hosted on an appserver, generates. A proxy server caches dynamic content only if the content is identified as edge cacheable in the cachespec.xml file for the application. All of the information that describes the cache, such as the ID to use for the cache, dependency identifiers for invalidation, and expiration times, is also defined in the cachespec.xml file. Proxy Server uses the ESI protocol to obtain this information from the file.

      See Set cacheable objects with the cachespec.xml file for more information on how to set up a cachespec.xml file for an application.

      Cached dynamic content can be invalidated by events in the appserver. The ESI Invalidation Servlet, contained in the DynacacheEsi.ear application, propagates these invalidation events from the appserver to the proxy server. The DynacacheEsi.ear is shipped with WAS ND, and must be deployed in the cluster with the application that is generating the dynamic content for dynamic caching at the proxy server to function properly.

   2. Static caching is enabled by default when caching is enabled for the proxy server. Static content is Web content that is public and accompanied by HTTP response headers, such as EXPIRES and LAST_MODIFIED_TIME, that describe how long the response can be cached. The proxy server uses the HTTP 1.1 RFC (2616), which specifies how content should be treated and includes capabilities such as VARY header support for caching variants of the same resource URI.

Static cache rules collection
Static cache rule settings