Select a timeout type and click Edit Selected. For more information about the

Getting Started with Administering Oracle Web Cache 2-31 If you are using the default network_error.html page, leave the field as is.

5. In the Site Busy Page field, enter the file name of the error page delivered when a

Web site is saturated with requests. If you are using the default busy_error.html page, leave the field as is.

6. In the ESI Default Fragment field, enter the file name of the page delivered when

Oracle Web Cache cannot retrieve an HTML fragment for an esi:include tag. If you are not using esi:include tags for partial page caching or you want to use only ESI language elements for exceptions, do not enter a value.

7. Click Apply Changes.

If you selected Default Pages, Oracle Web Cache applies the new settings to all defined sites with the default page setting. However, Oracle Web Cache does not apply the new setting to undefined sites. If you selected a specific site in Step 3, Oracle Web Cache applies the new settings to the specific site.

2.11.7 Task 7: Restart Oracle Web Cache

See Section 2.13 for instructions on restarting Oracle Web Cache.

2.12 Creating Session Definitions

You create session definitions for the following features: ■ Specify how session requests are served by the cache ■ Enable session binding , whereby a user session for a particular site is bound to an origin server to maintain state for a period. ■ Substitute session information in session-encoded URLs When you enable these features, you must select a session definition. To create a session definition:

1. Navigate to the Web Cache Home page in Fusion Middleware Control. See

Section 2.6.2 .

2. From the Web Cache menu, select Administration, and then Session

Configuration . The Session Configuration page displays.

3. From the Site list, select the specific site for which you want to apply this session

definition. To create a global session definition that can be applied to any site, select Global. See Section 2.11.3 to specify additional sites.

4. In the Session Definitions section, click Create.

A new row in the table appears.

5. In the Session Name field, enter an easy-to-remember unique name for the

session.

6. Enter the cookie name in the Cookie Name field and the embedded URL

parameter in the URL Post Body Parameters field. 2-32 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache If you enter both a cookie name and an embedded URL parameter, keep in mind that both must be used to support the same session. If they support different sessions, create separate session definitions.

7. In the URL Post Body Parameters field, enter the embedded URL parameter or

POST body parameter containing the session information.

8. In the Default Value field, enter the default string for Oracle Web Cache to use for

the cookie or embedded URL parameter value. Oracle Web Cache uses the default string for those requests without the cookie or parameter information. For these requests, Oracle Web Cache substitutes the session ID information with the default string. The default string defaults to default.

9. Click Apply to apply changes

10. Restart Oracle Web Cache. See Section 2.13 . For more information about Oracle Web Cache properties requiring session definitions, see: ■ Section 3.5 to configure session binding ■ Section 6.8.6 to configure session caching rules ■ Section 6.8.7 to configure support for session-encoded URLs

2.13 Starting and Stopping Oracle Web Cache

Most configuration changes are static. When you apply static changes, you must restart Oracle Web Cache to apply changes. However, Oracle Web Cache recognizes some changes as dynamic. Oracle Web Cache Manager provides dynamic configuration for the following features: ■ Request filtering in both Fusion Middleware Control and Oracle Web Cache Manager ■ Setting buffering and verbosity detail level in the Event Logs page Logging and Diagnostics Event Logs in Oracle Web Cache Manager ■ Setting buffering in the Access Logs page Logging and Diagnostics Access Logs in Oracle Web Cache Manager ■ Enabling and disabling of diagnostics information in the HTML response body of an object in the Diagnostics page Logging and Diagnostics Diagnostics in Oracle Web Cache Manager ■ Setting routing to origin servers in the Origin Servers page Origin Servers, Sites, and Load Balancing Origin Servers in Fusion Middleware Control Anytime the Oracle Web Cache configuration is statically modified, you must stop and restart Oracle Web Cache processes: ■ The admin server process manages the administrative interface. ■ The cache server process manages the cache. Note: When a cookie expires, the client browser removes the cookie and subsequent requests for the object are directed to the origin server. To avoid pages from being served past the client session expiration time, ensure that the session cookie expires before the application Web server expires the client session.