By default, the Host Name field contains the host name of the node on which

3-20 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache

3.7.3 Task 3: Enable Tracking of Session Binding

In a cache cluster, all cache cluster members must be able to determine which origin server established the session, although the request was routed originally through only one cache cluster member. To configure session binding in a cache cluster, you select a session binding mechanism of Cookie-based. Setting this mechanism adds a cookie that tracks session information so that it can be read by all cluster members. Oracle Web Cache includes a Set-Cookie response-header in the response so that subsequent requests from the client include the cookie. The cookie provides information so that any of the cluster members can resolve the binding regardless of which cache handled the initial request. To configure session binding with the Cookie-based mechanism, see Section 3.5 .

3.7.4 Task 4: Synchronize the Configuration to Cluster Members

When you modify the cluster and apply changes, Oracle Web Cache adds the cache-specific information from the new cache cluster members to the configuration. For those changes to take affect in all cluster members, you must synchronize the configuration and restart the cache server process of the cluster members. To synchronize the configuration to new cluster members with Oracle Web Cache Manager:

1. In the navigator frame, select Operations Cache Operations.

The Cache Operations page appears. The Operation Needed column indicates the caches to which the configuration should be synchronized. 2. Synchronize the configuration to all cache cluster members:

a. Select All caches in the Operate On field.

b. Select an Interval of Immediate. No other interval is allowed for

synchronization.

c. Click Propagate.

Alternatively, you can synchronize the configuration to one cluster member at a time. Click Selected cache in the Operate On field, and then click Propagate. When the operation completes, the Operation Needed column in the Cache Operations page indicates the cluster members that must be restarted. 3. Stop and restart all cluster members:

a. Select All caches in the Operate On field.

b. Select an Interval to stagger the time that operation begins on the caches, and

then click Restart. Alternatively, you can restart one cluster member at a time. Choose Selected cache in the Operate On field and then click Restart. When the operation completes, the Operation Needed column in the Cache Operations page indicates that no operations are needed. The cache cluster is ready to use.

3.7.5 Removing Caches from a Cluster

To remove a cache from a cluster, you must not only ensure that remaining cluster members no longer include that cache in cluster, but that the removed cache no longer considers itself to be part of the cluster. Configuring High Availability Solutions 3-21 To remove a cache from a cluster with Oracle Web Cache Manager: 1. Enter the URL for the Oracle Web Cache Manager of a cache in cluster, but not the cache to remove from the cluster.

2. In the navigator frame, select Properties Clustering.

3. In the Cluster Members section of the Clustering page, select the cache you want to remove from the cluster and click Delete Selected.

4. In the Oracle Web Cache Manager main window, click Apply Changes.

5. Synchronize the change to the other remaining cache cluster members:

a. In the navigator frame, select Operations Cache Operations.

b. Select All caches in the Operate On field.

c. Select an Interval of Immediate.

d. Click Propagate.

The change is synchronized with all the remaining cluster members, but not to the removed cluster member. 6. Restart all cluster members:

a. In the Cache Operations page, select All caches in the Operate On field.

b. Select an Interval to stagger the time that operation begins on the caches, and

then click Restart. All remaining caches in the cluster no longer consider the removed cache to be part of the cluster. However, the removed cache still considers itself to be part of the cluster. To remedy that situation, take the next steps. 7. Enter the URL for the Oracle Web Cache Manager of the cache you removed from the cluster.

8. In the navigator frame, select Properties Clustering.

The Clustering page appears. The Cluster Members section still shows all members of the cluster. 9. In the Cluster Members section of the Clustering page, select each cache except the current one, and click Delete Selected. Repeat until only the current cache remains in the Cluster Members list.

10. In the Oracle Web Cache Manager main window, click Apply Changes.

11. In the navigator frame, select Operations Cache Operations.

12. Select the cache and click Restart.

3.7.6 Configuring Administration and Invalidation-Only Clusters

You can configure a cluster that supports synchronizing the configuration and invalidation requests across all cache cluster members, but that does not forward requests between cache cluster members. That is, in processing requests, each cluster member acts as an individual cache and does not request objects from its peer cluster members. However, configuration changes and invalidation requests can be synchronized among cluster members. You can use this configuration to simplify administration of many caches. It may be needed in a cluster where members are separated by a firewall. For example, you can have a cluster where two caches are located on either side of a firewall that separates