Oracle Web Cache Solely as a Software Load Balancer or Reverse Proxy

Configuring High Availability Solutions 3-11 To configure session binding, you specify a set of session binding rules, and then apply them to the sites. By default, sites are configured to use a default rule. You can use the default rule or select another rule customized for the site. If you decide to change the value of the default session binding rule, ensure all named sites currently configured with this rule require session binding. If some sites do not require session binding, leave the value of default rule, and instead specify session binding settings for the site. To configure session binding: 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 select Session

Configuration . The Session Configuration page displays.

3. From the Site list, select the site to create customized session-bindings.

Select Global to specify default settings for requests which do not match any defined site. If you do not specify customized session-binding settings for a site, then you can click the Use global settings option to apply the settings you specify for Global. The default selection for the Global selection is the Disable session binding . You change the default setting by selecting Global from the Site list and selecting on of the other session-binding selections.

4. Create a session definition in the Session Definitions table. See

Section 2.12 . - Use global settings: Select this option to apply the session-binding settings you configured for the Global selection from the Site list. By default, Oracle Web Cache disables session binding for all requests. The default selection for Global is the Disable session binding option. When you first create a site, it is set by default to use the global session binding settings - Disable session binding: Select this option to disable session binding. This selection is the default for the Global site. You change the default setting by selecting Global from the Site list and selecting on of the other session-binding selections. - Cookie based session binding with any Set-Cookie: Select this option if the client supports cookies and your origin server uses one or more cookies for session state. Oracle Web Cache uses its own cookie to track a session. This cookie, which contains routing information, is maintained between Oracle Web Cache and the client browser. The clientserver binding is initiated by the first cookie that the application server sends to the client. - Bind using a session: Select this option to enable binding for a specific session, and then perform the following steps:

a. From the Session Name list, select a session to enable binding for a specific

session.

b. From the Session Binding Mechanism list, select a binding mechanism for the

selected session definition: - Cookie Based: Select if the client supports cookies. Oracle Web Cache uses its own cookie to track a session. This cookie, which contains routing information, is maintained between Oracle Web Cache and the client browser. 3-12 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache - Session Binding IAS: Select if the application is based on OC4J. Oracle Web Cache forwards routing information with each request to OC4J through Oracle HTTP Server. - Internal-Tracking: Select if the client does not support cookies and the application is not based on Oracle HTTP Server and OC4J. This option is intended for backward compatibility with earlier releases of Oracle Web Cache. Oracle Web Cache maintains an in-memory routing table, of which each entry maps a session ID to an origin server. The routing table is not shared among cluster nodes. If you select this option and you have a cache cluster configuration, then you must also bind at the load balancer layer.

5. Click Apply to submit changes.

6. Restart Oracle Web Cache. See Section 2.13 .

3.6 Configuring a Cache Cluster for Caches Using the Same Oracle WebLogic Server

To increase the availability and scalability of your Web site, you can configure multiple instances of Oracle Web Cache to run as members of a cache cluster. For more information about cache clusters, see Section 3.3 . To configure a cache cluster, you configure two or more Oracle Web Cache instances as cache cluster members, and specify properties for the cluster. A cache cluster uses one configuration that is synchronized from the current cache the cache to which your client browser is connected to all cluster members. The configuration contains settings that are the same for all cluster members as well as cache-specific settings for each cluster member. This section contains the following topics to aid you in configuring a cache cluster in a environment in which all the caches are associated with the same Oracle WebLogic Server. These instruction explain how to configure a cluster using Fusion Middleware Control, which requires all the cache members to use the same Oracle WebLogic Server: ■ Section 3.6.1, Configuration Prerequisites ■ Section 3.6.2, Understanding Failover Threshold and Capacity Settings ■ Section 3.6.3, Task 1: Add Caches to the Cluster and Configure Properties ■ Section 3.6.4, Task 2: Enable Tracking of Session Binding ■ Section 3.6.5, Task 3: Synchronize the Configuration to Cluster Members In addition, see the following information about configuring clusters: ■ Section 3.6.6, Removing a Cache Member from a Cluster ■ Section 3.6.7, Configuring Administration and Invalidation-Only Clusters If you have want to configure a cache cluster for a configuration in which the caches are associated with different Oracle WebLogic Servers, follow the instructions in Section 3.7 to use Oracle Web Cache Manager to configure the cluster.

3.6.1 Configuration Prerequisites

Because a cache cluster contains two or more instances of Oracle Web Cache, you must have two or more instances of Oracle Web Cache installed on one or more nodes before you configure a cache cluster. The instances must be the same version of Oracle