optimize

PRODUCT CENTERS

Legal | Privacy

Printer View

E-mail this page

Bookmark

Optimizing OracleAS Web Cache

Purpose

This tutorial introduces one of the tuning techniques for increasing cache hits.

Time to Complete

Approximately 15 minutes

Topics

This tutorial covers the following topics:

	Overview
	Prerequisites
	Checking for Popular Pages That Are Not Cached
	Adding a Caching Rule
	Summary
	Related Information

Viewing Screenshots

Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: Because this action loads all screenshots simultaneously, response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

Overview

Back to Topic List

OracleAS Web Cache is preset with default caching rules and system settings that are useful for most basic applications. In addition, system administrators may use the diagnostic and monitoring tools to optimize OracleAS Web Cache. This lesson introduces one set of statistics called Popular Pages, which is useful for identifying the most frequently requested URL and its associated cacheability.

Prerequisites

Back to Topic List

Before starting this tutorial, you should:

1.	Have completed the OBE titled "Configuring OracleAS Web Cache for Caching a J2EE Application"
2.	Have completed the OBE titled "Configuring OracleAS Web Cache for Session Binding and Load Balancing"
3.	Have completed the OBE titled "Configuring OracleAS Web Cache Cluster for Scalability and Failover"

Checking for Popular Pages That Are Not Cached

Back to Topic List

Browse the Web pages by accessing http://localhost:7777/hrapp. The username and password for hrapp is Guest and welcome.

On the Oracle Enterprise Manager 10g Application Server Control Console, go to the OracleAS Web Cache Home page. Click the Performance tab.

Click Popular Requests.

Observe that /localhost:7777/hrapp is not cached. You have noticed this in the OBE titled "Configuring OracleAS Web Cache for Caching a J2EE Application." The page at /localhost:7777/hrapp is a redirect header from the origin server. Because it is the opening page of the site, it is accessed frequently. You will now learn how to cache this page.

Adding a Caching Rule

Back to Topic List

1.	Click Web Cache in the breadcrumbs to return to OracleAS Web Cache Home page. Click the Administration tab and then click Rules under Properties.
2.	Click Create to create a new rule.
3.	Enter the following: Name: caching_hrapp (anything you want) Description: caching (anything you want) Match URL by Regular Expression ^/hrapp$ ('^' and '$' are used to specify the beginning and end of the URL, respectively) Expand Show HTTP Methods and Parameters.
4.	Select GET and GET with query string.
5.	Because this URL never changes and has no content for compression, set the following: Expiration of Cached Response: Never Compression: Do not compress Click the Advanced Caching Instructions tab. This page is to instruct OracleAS Web Cache how to handle special cases, such as responses that do not result in 200 HTTP code.
6.	Scroll down and look for Cache Error Responses. In the Additional Error Responses to Cache field, enter 301. Click OK. 301 is the error code from the origin server. OracleAS Web Cache logs all the HTTP code from the origin server in the access logs. To access the logs, go to <oracle_home>/webcache/logs.
7.	Click Restart Web Cache to restart Web Cache. Click Yes when prompted for confirmation.
8.	You have already learned that you must propagate the configuration and restart the cache server process of cluster members when you make some changes. You will now propagate changes. Click the Go to cluster operations page link.
9.	Select SecondWebCache, and click Propagate to. Click Yes when prompted for confirmation.
10.	Select both the Web Cache instances and click Restart to restart the instances.
11.	Open another browser window and browse the Web pages by accessing http://localhost:7777/hrapp.
12.	Switch back to the Application Server Control browser window. Click Web Cache in the breadcrumbs to return to OracleAS Web Cache Home page.
13.	Click the Performance tab and then click Popular Requests.
14.	Observe that /localhost:7777/hrapp is cached.
15.	Optionally, try to cache /localhost:7777/hrapp/. If you have trouble doing this, call one of the staff members for assistance.