Skip Headers
Oracle® Application Server Web Cache Administrator's Guide
10g Release 2 (10.1.2)
  Go To Documentation Library
Go To Product List
Solution Area
Go To Table Of Contents
Go To Index


What's New in OracleAS Web Cache?

This section describes the new features of OracleAS Web Cache and provides pointers to additional information. This information is mostly useful to users who have managed Oracle Application Server 10g Release 2 (

The following sections describe the new features in OracleAS Web Cache:

New Features in 10g Release 2 (

The new administrative features of OracleAS Web Cache 10g Release 2 (10.1.2) include:

Enhanced Support for Configuring OracleAS Web Cache Solely as a Software Load Balancer or Reverse Proxy

In previous releases, you could configure OracleAS Web Cache solely as a software load balancer or reverse proxy in place of hardware load balancers.

In this release, support for this mode has been enhanced. You can now configure OracleAS Web Cache as software load balancer or reverse proxy even in front of an application using Edge Side Includes (ESI) or in front of another OracleAS Web Cache forming a cache hierarchy. A typical OracleAS Portal deployment, for example, has a built-in OracleAS Web Cache used for ESI assembly.

If you require other OracleAS Web Cache features, such as caching or compression support, do not configure this mode. Instead, configure a hardware load balancer or operating system load balancing support, and use OracleAS Web Cache's load balancing feature to manage requests to origin servers.

New Port Numbers for Some Components

To guard against conflicts with Windows ephemeral port number assignments, default port numbers and ranges have been changed for the OracleAS Web Cache operations ports.

New Features in 10g Release 2 (

The new features for OracleAS Web Cache in 10g Release 2 ( include:

Oracle Enterprise Manager 10g Application Server Control Support

In previous releases, you had to use OracleAS Web Cache Manager to configure OracleAS Web Cache. In this release, you have two choices:

URL Path Prefix in Site Definitions

When configuring a site definition, you can specify a URL path prefix for those sites that share the same host name. For example, to treat and as two distinct sites, you specify /employee and /customer as prefixes.

Caching Rule Enhancements

Improved Diagnostics

See Also: