In the Cluster Members section of the Clustering page, click Add.

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