Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Dynamic caching > Administer the dynamic cache service > Use the dynamic cache service > Configure external cache groups


Configure high-speed external caching through the web server

IBM HTTP Server for Windows 2003 operating systems contains a high-speed cache referred to as the Fast Response Cache Accelerator, or cache accelerator. The Fast Response Cache Accelerator is available on Windows 2003 operating systems and AIX platforms. However, support to cache dynamic content is only available on Windows 2003 operating systems. We can enable cache accelerator to cache static and dynamic content.

Restriction on using the fast response cache accelerator (FRCA) : The FRCA, which is based on the IBM Advanced Fast Path Architecture (AFPA), is not supported on the Microsoft Windows Vista , Windows 2008, or any later Windows operating systems. IBM HTTP Server will fail to start if the FRCA is enabled in the configuration file. This is a permanent restriction.

Enable cache accelerator for caching static content by adding the following directives to the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf configuration file, located in the IBM HTTP Server conf directory:

To enable cache accelerator for caching dynamic content, such as servlets and JSP files, configure WAS and IBM HTTP Server for distributed platforms:


Procedure

  1. Configure WAS to enable Fast Response Cache Accelerator. It is important to follow all of the steps for every application server in the cluster.

    1. Turn on servlet caching for each application server that uses the cache accelerator.

    2. Configure an external cache group on the application server:

      1. Click Servers > Server Types > WebSphere application servers > server_name

        > Container services > Dynamic cache service > External cache groups.

      2. Click New on the External cache group administrative console page to define an external cache group named afpa for each application server that uses the cache accelerator.

      3. In the External cache group field, type afpa and apply the changes.

    3. Add a member to the group with an adapter bean name of com.ibm.ws.cache.servlet.Afpa.

      1. Click Afpa > External cache group members.

      2. Click New on the External cache group members admin console page.

      3. In the AdapterBean name field, type com.ibm.ws.cache.servlet.Afpa.

      4. In the Address field, enter an unused port number.

    4. Add a cache policy in the cachespec.xml file for the servlet or JSP file to cache. Add the following property to the cache policy: 
      <property name="ExternalCache">afpa
</property>

  2. Enable cache accelerator on IBM HTTP Server for distributed platforms:

    1. Add the following directives to the end of the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf file:

      • AfpaEnable
      • AfpaCache on
      • AfpaLogFile "WAS_HOME\IBMHttpServer\logs\afpalog" V-ECLF

      • Deprecated feature: IBM HTTP Server 1.3.x - LoadModule afpaplugin_module WAS_HOME\bin\afpaplugin.dlldepfeat

      • IBM HTTP Server 2.0 - LoadModule afpaplugin_20_module WAS_HOME\bin\afpaplugin_20.dll
      • AfpaPluginHost WAS_Hostname:port, where WAS_Hostname is the host name of the application server and port is the port you specified in the Address field while configuring the external cache group member

    The LoadModule directive loads the IBM HTTP Server plug-in that connects the Fast Response Cache Accelerator to the WAS fragment cache. If multiple IBM HTTP Servers are routing requests to a single application server, add the directives above to the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf file of each of these IBM HTTP Servers for distributed platforms. If one IBM HTTP Server is routing requests to a cluster of application servers, add the AfpaPluginHost WAS_Hostname:port directive to the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf file for each application server in the cluster. For example, if there are three application servers in the cluster, add the following directives to the //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ d.conf file:

    • LoadModule afpaplugin_module WAS_HOME/bin/afpaplugin.dll
    • AfpaPluginHost WAS1_Hostname:port1
    • AfpaPluginHost WAS2_Hostname:port2
    • AfpaPluginHost WAS3_Hostname:port3


Related


Configure fast response cache accelerator cache size through a distributed platforms web server
Implement a web server plug-in
Use the dynamic cache service
Configure servlet caching


Related


cachespec.xml file

+

Search Tips   |   Advanced Search