Applies To:

Show Versions Show Versions

Manual Chapter: Invalidating Cached Content
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Overview: Invalidating cached content for an application

You typically use invalidations rules to expire specific content stored in cache. When you invalidate content, that content is immediately expired but not removed from the disk.

Invalidating cached content for an application

You can invalidate cached content for one or more applications, which expires, but does not clear, the cached content for the specified applications.
Note: Invalidating the cached content on the WebAccelerator™ system temporarily increases traffic to the origin web servers until the WebAccelerator system repopulates the cache.
  1. On the Main tab, click WebAccelerator > Invalidate Content. The Invalidate Content screen opens.
  2. Select the check box for the application with cached content that you want to invalidate.
  3. Click Invalidate.
The cached content for the specified applications is invalidated.

Clearing cached content from the command line

There may be occasions, such as when troubleshooting cache issues, when you want to clear cache and remove content that the WebAccelerator™ system has stored.
Note: Clearing cached content temporarily increases traffic to the origin web servers until the WebAccelerator system repopulates the cache.
  1. Log on to tmsh.
  2. Type tmsh delete ltm profile wa-cache wa_profile_name at the command line, where wa_profile_name is the name of the Web Acceleration profile.
The content cached by the WebAccelerator system is cleared.

About invalidations rules examples

For the invalidations rules examples, you have four top-level nodes on the Policy Tree as follows:

  • Home. This branch node specifies the rules related to the home page.
  • Applications. This branch node specifies the rules related to the applications for the site, with the following leaf nodes:
    • Default. This leaf node specifies the rules related to non-search related applications.
    • Search. This leaf node specifies the rules related to your site’s search application.
  • Images. This branch node specifies the rules related to graphics images.
  • Blog. This branch node specifies the rules related to the blog, with the following leaf nodes:
    • View. This leaf node specifies the rules related to viewing posts to the blog.
    • Post. This leaf node specifies the rules related to posting to the blog.

Search invalidations rule example

For this example, any request for the /apps/doSomething.jsp application changes content returned by /srch/doSimpleSearch.jsp. However, you want requests for doSimpleSearch.jsp to be updated only if its producttype query parameter matches the value set for the group query parameter on doSomething.jsp.

For example, consider the following request:

http://www.somesite.com/apps/doSomething.jsp?group=Doors&....

The WebAccelerator™ system should send, to the origin web server, any subsequent requests that appear as follows:

http://www.somesite.com/srch/doSimpleSearch.jsp?producttype=Doors&....

To accomplish this, you create an invalidations rule for the Default leaf node, because you know that all requests for the path, /apps/doSomething.jsp, match to that node. The target, requests for doSimpleSearch.jsp, always match to the Search node and should include a producttype query parameter when a value matches the value of group in the triggering request for /apps/doSomething.jsp. Therefore, the Cached Content to Invalidate setting should specify doSimpleSearch.jsp for the path, and producttype for the query parameter.

Creating leaf nodes for the blog example invalidations rule

In this task, you create View and Post leaf nodes in the Policy Tree for the example blog invalidations rule.
  1. On the Main tab, click WebAccelerator > Policies. The Policies screen displays a list of existing acceleration policies.
  2. Click the name of a user-defined acceleration policy.
  3. Click the Blog branch node in the Policy Tree.
  4. From the Matching Rules menu, choose Acceleration Rules.
  5. Click Invalidations.
  6. Create a leaf node named View.
    1. Click Add on the Policy Tree function bar.
    2. Name the node View.
    3. Type a description.
    4. Click Create.
  7. Create a leaf node named Post.
    1. Click Add on the Policy Tree function bar.
    2. Name the node Post.
    3. Type a description.
    4. Click Create.
The View and Post nodes appear in the Policy Tree.

Specifying matching rules for the invalidations example View node

A View and Post leaf node have been created.
This task configures matching rules for the invalidations example View node.
  1. Click the View node.
  2. For Matching Rules, specify the Path settings.
    1. In the Add Parameter list, select Path.
    2. Click Add.
    3. In the Value field, type /.
    4. Click Save.
  3. For Matching Rules, specify the view settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type view.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type topic.
    6. Click Save.
  4. For Matching Rules, specify the Content Type settings.
    1. In the Add Parameter list, select Content Type.
    2. Click Add.
    3. Select the check box beside the Value matches list.
    4. In the Enter a regular expression field, type pages.html.
    5. Select the Match if not yet classified check box.
    6. Click Save.
The matching rules for the invalidations example View node are configured.

Specifying matching rules for the invalidations example Post node

A View and Post leaf node have been created.
This task configures matching rules for the invalidations example Post node.
  1. Click the Post node.
  2. For Matching Rules, specify the Path settings.
    1. In the Add Parameter list, select Path.
    2. Click Add.
    3. In the Value field, type /.
    4. Click Save.
  3. For Matching Rules, specify the forumid settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type forumid.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type *.
    6. Click Save.
  4. For Matching Rules, specify the view settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type view.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type post.
    6. Click Save.
  5. For Matching Rules, specify the Content Type settings.
    1. In the Matching Rules Add Parameter list, select Content Type.
    2. Click Add.
    3. Select the check box beside the Value matches list.
    4. In the Enter a regular expression field, type pages.html.
    5. Select the Match if not yet classified check box.
    6. Click Save.
The matching rules for the invalidations example Post node are configured.

Task summary for specifying invalidations rules for the invalidations example Post node

Perform these tasks to configure the invalidations blog example Post node.

Configuring blog example Path settings for the Post node invalidations rules

A View and Post leaf node have been created.
In this task for configuring blog invalidations rules, you specify Path settings for the Post node invalidations rules.
  1. Click the Post node.
  2. In the Matching Rules list, select Acceleration Rules.
  3. Click Invalidations.
  4. Click Create.
  5. In the Description field, type a description.
  6. For Request Header Matching Criteria, specify the Path settings.
    1. In the Add Parameter list, select Path.
    2. Click Add.
    3. In the Value(s) field, type /.
    4. Click Save.
  7. For Cached Content to Invalidate, specify the Path settings.
    1. In the Add Parameter list, select Path.
    2. Click Add.
    3. In the Value Group field, type /.
    4. Click Save.
The Path settings for the Post node are configured for the example blog invalidations rules.

Configuring blog example view settings for the Post node invalidations rules

A View and Post leaf node have been created.
In this task for configuring blog invalidations rules, you specify view settings for the Post node invalidations rules.
  1. Click the Post node.
  2. In the Matching Rules list, select Acceleration Rules.
  3. Click Invalidations.
  4. Click Create.
  5. In the Description field, type a description.
  6. For Request Header Matching Criteria, specify the view settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type view.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type post.
    6. Click Save.
  7. For Cached Content to Invalidate, specify the view settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type view.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type topic.
    6. Click Save.
The view settings for the Post node are configured for the example blog invalidations rules.

Configuring blog example forumid settings for the Post node invalidations rules

A View and Post leaf node have been created.
In this task for configuring blog invalidations rules, you specify forumid settings for the Post node invalidations rules.
  1. Click the Post node.
  2. In the Matching Rules list, select Acceleration Rules.
  3. Click Invalidations.
  4. Click Create.
  5. In the Description field, type a description.
  6. For Request Header Matching Criteria, specify the forumid settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type forumid.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type *.
    6. Click Save.
  7. For Cached Content to Invalidate, specify the forumid settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type forumid.
    4. In the Type list, select Query Parameter from Request.
    5. In the Name field, type forumid.
    6. Click Save.
The forumid settings for the Post node invalidations rules are configured for the example blog invalidations rules.

Configuring blog example postid settings for the Post node invalidations rules

A View and Post leaf node have been created.
In this task for configuring blog invalidations rules, you specify postid settings for the Post node invalidations rules.
  1. Click the Post node.
  2. In the Matching Rules list, select Acceleration Rules.
  3. Click Invalidations.
  4. Click Create.
  5. In the Description field, type a description.
  6. For Request Header Matching Criteria, specify the postid settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type postid.
    4. Select the check box beside the Value matches list.
    5. In the Enter a regular expression field, type *.
    6. Click Save.
  7. For Cached Content to Invalidate, specify the postid settings.
    1. In the Add Parameter list, select Query Parameter.
    2. Click Add.
    3. In the Name field, type postid.
    4. In the Type list, select Query Parameter from Request.
    5. In the Name field, type postid.
    6. Click Save.
The postid settings for the Post node invalidations rules are configured for the example blog invalidations rules.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)