From the Web Cache menu, select Administration and then select Cluster.

Configuring High Availability Solutions 3-17

5. With the other caches still selected, 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. You remedy this situation in the next steps. 6. Navigate to the Web Cache Home page in Fusion Middleware Control of the cache you removed from the cluster.

7. From the Web Cache menu, select Administration and then select Cluster.

The Cluster page displays with all the member of the cache.

8. Select a cache except the current one, and click Delete. Repeat until only the

current cache remains in the Cluster Members list. 9. Click Restart.

3.6.7 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 the intranet from Internet. The network settings of such a setup—of sending Internet traffic to one cache and intranet traffic to another—is beyond the scope of this document. To manage these caches as a cluster and avoid sharing contents between the caches, take the following steps: 1. Create a cluster and add members to it as discussed in Section 3.6.3 and Section 3.6.4 , with the following exceptions: ■ For each cluster member, set the capacity to 0. ■ In the Cluster Properties section, select option Invalidation requests sent to any cluster member will be propagated to all cluster members . 2. Synchronize the configuration to all cluster members, as described in Section 3.6.5 . 3.7 Configuring a Cache Cluster for Unassociated Caches or Caches Using Different Oracle WebLogic Servers This section contains the following topics to help you in configuring a cache cluster in a configuration in which all unassociated caches are using different Oracle WebLogic Servers. These instruction explain how to configure a cluster using Oracle Web Cache Manager. ■ Section 3.7.1, Task 1: Configure Cache Cluster Settings ■ Section 3.7.2, Task 2: Add Caches to the Cluster ■ Section 3.7.3, Task 3: Enable Tracking of Session Binding ■ Section 3.7.4, Task 4: Synchronize the Configuration to Cluster Members