10g (9.0.4)
Part Number B10401-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle Application Server Web Cache Administrator's Guide 10g (9.0.4) Part Number B10401-01 |
|
This section describes the new features of OracleAS Web Cache 10g (9.0.4) and provides pointers to additional information. New features information from previous releases is also retained to help those users migrating to the current release.
The following sections describe the new features:
The new features for OracleAS Web Cache in 10g (9.0.4) include:
You can base invalidation on search keys used in the Surrogate-Key response-header field of objects in the cache.
In previous releases, the URL-based cache key was the only identifier for a cached document. Invalidation requests needed to specify either exact URLs or a set of URLs and headers matching a regular expression in order to invalidate cached objects. Because it can be difficult for applications to map URLs to the underlying data used to generate those URLs, OracleAS Web Cache invalidation has been extended in 9.0.4 to support search keys. Cached objects can now be associated with multiple application-specified search keys, with the URL-based key being the primary key.
<esi:invalidate> Tag
This release introduces an inline invalidation mechanism as an additional means of managing content freshness. This inline invalidation model supplements the out-of-band invalidation model pioneered by Oracle in the very first release of OracleAS Web Cache. Inline invalidation is implemented as part of Edge Side Includes (ESI). The ability to send invalidation message inline reduces the connection overhead associated with sending out-of-band invalidations and is a useful tool for ESI developers.
Rollover policies for access and event logs are more flexible than in previous releases, and on-demand rollover has been added. Access log formats are now easier and more flexible to define. Administrators can also configure different access logs and logging formats for different virtual hosts serviced by the cache. New access log fields have been introduced that provide low-level request-timing diagnostics. With 9.0.4, OracleAS Web Cache provides event log support for four levels of verbosity instead of two, and many of the error messages have been improved (especially for ESI errors), both of which accelerate problem diagnosis and resolution. Finally, remote diagnostic tools have been enhanced to provide more information about response failures.
Administrators can now use the browser-based OracleAS Web Cache Manager utility to get information about the most popular cache miss requests. This supplements reporting functionality in prior releases on the most popular objects in cache.
In addition to managing Oracle HTTP Server and OC4J processes, OPMN now manages the admin server process and cache server process for OracleAS Web Cache, including the start, stop and auto-restart operations. For standalone OracleAS Web Cache deployments, administrators continue to use the webcachectl utility.
In 9.0.4, you can better control the granularity of multiple-version caching rules based on User-Agent request headers (browser types). You can now configure a single cache entry for each browser type (Internet Explorer, Netscape, or Mozilla), as opposed to multiple entries for each browser variant (browser version, or operating system).
In addition to using regular expressions, you can now apply caching rules to objects based on file extension or path prefix.
To conserve resources, you can now configure the maximum size of documents to be cached.
OracleAS Web Cache now supports applications that require client-side SSL certificates for PKI-based authentication. For HTTPS protocol requests that require client-side certificates, the client browser sends its certificate to Web Cache during the SSL handshake. The cache forwards the request to Oracle HTTP Server along with the client's certificate information inserted in special HTTP request headers. Oracle HTTP Server recognizes the headers and is able to pass user credentials to Oracle Application Server Single Sign-On for authentication purposes.
In addition to offboard SSL acceleration solutions, Oracle Application Server now supports nCipher's BHAPI-compliant hardware for deployment on servers running OracleAS Web Cache and Oracle HTTP Server.
OracleAS Web Cache provides a mechanism to ensure that all cache cluster members can determine which origin server established the session, although the request was routed originally through only one cache cluster member. As a result, subsequent requests are bound to the origin server that established the session.
Using OracleAS Web Cache Manager, you can monitor the response time of your applications by viewing information about how quickly the responses are delivered to the end users.
The Surrogate-Control response header now supports a compress control directive for enabling compression. This feature adds flexibility by enabling developers to express compression policies in the content itself, as opposed to relying on administrators to configure compression policies using the OracleAS Web Cache Manager.
OracleAS Web Cache now compresses documents containing session-encoded URLs, ESI tags, or <!--WEBCACHETAG--> and <!-- WEBCACHEEND--> tags.
This release of ESI provides the following enhancements:
alt attribute of the <esi:include> tag for specifying an alternate URL if the src fragment is not found
try |attempt |except support for specific errors
To help ease configuration, OracleAS Web Cache Manager supports a new navigation structure that resembles the order in which you perform configuration tasks. In addition, pages have been enhanced with purpose descriptions.
A number of the configuration parameters in the browser-based OracleAS Web Cache Manager administration utility can now be changed on the fly, without requiring a restart of the cache.
OracleAS Web Cache Manager now provides support for discovering site and alias information from Oracle HTTP Server.
During installation, OracleAS Web Cache defines a default site, using the host name and listening port of the computer on which the Oracle Application Server was installed.
The new features for OracleAS Web Cache in release 2 (9.0.3 and 9.0.2) include:
The auto-restart checks that the cache server process is running and automatically restarts it if it is not running.
You can deploy OracleAS Web Cache in a cache hierarchy so that an OracleAS Web Cache server caches content from another OracleAS Web Cache.
You can configure multiple instances of OracleAS Web Cache to run as members of a cache cluster. Cache clusters provide failure detection and failover of Web caches, increasing the availability of your Web site.
This release of ESI provides support for the following:
<esi:inline> tag
<esi:environment> tag
<esi:include> tag support that provides attributes for specifying expiration, fragment time out, and the HTTP request method. In addition, new elements enable you to specify the HTTP request body of a fragment and the HTTP request header field and value for OracleAS Web Cache to use.
In addition to HTTPS protocol support between browsers and OracleAS Web Cache, you can configure OracleAS Web Cache for HTTPS support between OracleAS Web Cache and origin servers.
Invalidation messages are propagated in a cache hierarchy whereby one OracleAS Web Cache server acts as an origin server for another OracleAS Web Cache server. They are also propagated in a cache cluster with multiple OracleAS Web Cache servers.
You can preview the list of documents to be invalidated.
You can generate a list of the URLs of the most popular documents stored in the cache and a list of the URLs of all of the objects currently in the cache.
You can use Oracle Enterprise Manager for monitoring OracleAS Web Cache. Oracle Enterprise Manager provides a Web-based tool that enables you to view OracleAS Web Cache status and performance metrics.
In addition to application Web servers for internal sites, you can configure OracleAS Web Cache to send cache misses to proxy servers for external sites protected by a firewall.
You can configure OracleAS Web Cache to cache and assemble dynamic content for one or more Web sites.
The webcachectl utility provides commands for finer-grain control of the auto-restart process, cache server process, and admin server process.
|
Note: If you are running OracleAS Web Cache in an environment where you have installed OracleAS Web Cache as part of an Oracle Application Server installation, you must use Oracle Process Manager and Notification (OPMN) Server to administer the OracleAS Web Cache processes.
If you invoke the See "OPMN for Process Administration" for information about OPMN. |
|
 Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|