Oracle Web Cache Administration and Deployment Guide

Part Number A86722-03





Go to previous page Go to next page


Oracle Web Cache Administration and Deployment Guide describes how to use Oracle Web Cache to cache both static and dynamically generated content from one or more application Web servers.

This preface contains these topics:


Oracle Web Cache Administration and Deployment Guide is intended for Web site administrators who perform the following tasks:

To use this document, you need to be familiar with release 1.0 and 1.1 of the HTTP protocol, as well as application Web server and DNS administration.


This document contains:

Chapter 1, "Introduction to Oracle Web Cache"

This chapter introduces the architecture, benefits, and main features of Oracle Web Cache.

Chapter 2, "Oracle Web Cache Concepts"

This chapter explains how Oracle Web Cache is populated with content, how that content maintains consistency, and how dynamically generated content is cached.

Chapter 3, "Deploying Oracle Web Cache"

This chapter presents several scenarios for deploying Oracle Web Cache.

Chapter 4, "Configuration and Administration Tools Overview"

This chapter introduces the various administration tools of Oracle Web Cache. It discusses the main administration application and tells you how to launch it and navigate through it.

Chapter 5, "Initial Setup and Configuration"

This chapter describes the steps to initially configure Oracle Web Cache to begin caching application Web server content after installation.

Chapter 6, "Creating Rules for Cached Content"

This chapter explains how to configure cacheability rules.

Chapter 7, "Configuration Considerations for Web Sites with Multiple Application Web Servers"

This chapter describes load balancing, failover, and session binding configuration options available for deployments with two more application Web servers.

Chapter 8, "Administering Oracle Web Cache"

This chapter describes how to start and stop Oracle Web Cache, invalidate documents in the cache, and evaluate event and access log files.

Chapter 9, "Monitoring Performance"

This chapter describes how to gather performance statistics and how to interpret them.

Appendix A, "Oracle Web Cache Directory Structure"

This appendix describes the installed Oracle Web Cache directory structure.

Appendix B, "Oracle Web Cache Default Settings"

This appendix describes the default settings for Oracle Web Cache.

Appendix C, "Invalidation Document Type Declaration"

This appendix describes the Document Type Declaration (DTD), or grammar, of invalidation requests and responses.

Appendix D, "Event Log Messages"

This appendix describes the most common event log messages.

Appendix E, "Troubleshooting Oracle Web Cache Configuration"

This appendix describes common configuration problems and debugging techniques for resolving them.


Related Documentation

For more information, see these Oracle resources:

In North America, printed documentation is available for sale in the Oracle Store at

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from

Other customers can contact their Oracle representative to purchase printed documentation.

To download patches, please visit the Oracle Technology Network at 

For additional information, see:


This section describes the conventions used in the text and code examples of the Oracle Internet Application Server documentation set. It describes:

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention  Meaning  Example 


Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. 

The C datatypes such as ub4, sword, or OCINumber are valid.

When you specify this clause, you create an index-organized table.  


Italic typeface indicates book titles or emphasis. 

Oracle8i Concepts

Ensure that the recovery catalog and target database do not reside on the same disk. 

UPPERCASE monospace (fixed-width font) 

Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles. 

You can specify this clause only for a NUMBER column.

You can back up the database by using the BACKUP command.

Query the TABLE_NAME column in the USER_TABLES data dictionary view.


lowercase monospace (fixed-width font) 

Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. 

Enter sqlplus to open SQL*Plus.

The password is specified in the orapwd file.

Back up the datafiles and control files in the /disk1/oracle/dbs directory.

The department_id, department_name, and location_id columns are in the hr.departments table.

Set the QUERY_REWRITE_ENABLED initialization parameter to true.

Connect as oe user.

The JRepUtil class implements these methods. 

lowercase monospace (fixed-width font) italic 

Lowercase monospace italic font represents placeholders or variables. 

You can specify the parallel_clause.

Run Uold_release.SQL where old_release refers to the release you installed prior to upgrading. 

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention  Meaning  Example 

[ ] 

Brackets enclose one or more optional items. Do not enter the brackets. 

DECIMAL (digits [ , precision ]) 

{ } 

Braces enclose two or more items, one of which is required. Do not enter the braces. 


A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar. 




Horizontal ellipsis points indicate either:

  • That we have omitted parts of the code that are not directly related to the example

  • That you can repeat a portion of the code


CREATE TABLE ... AS subquery;

SELECT col1, col2, ... , coln FROM employees; 



Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. 


Other notation 

You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown. 

acctbal NUMBER(11,2);

acct CONSTANT NUMBER(4) := 3; 


Italicized text indicates placeholders or variables for which you must supply particular values. 

CONNECT SYSTEM/system_password

DB_NAME = database_name 


Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase. 

SELECT last_name, employee_id FROM employees;


DROP TABLE hr.employees; 


Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files.

Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. 

SELECT last_name, employee_id FROM employees;

sqlplus hr/hr


Go to previous page Go to next page
Copyright © 1996-2001 Oracle Corporation.

All Rights Reserved.