When you have completed adding members to the cache cluster, click Apply

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 3-22 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache 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.7.1 and Section 3.7.2 , with the exception noted in the following step.

2. For each cluster member, set the capacity to 0. Select Properties Clustering.

Then, select a cluster member and click Edit. In the Edit Cluster Member dialog box, set the Capacity to 0. 3. Synchronize the configuration to all cluster members, as described in Section 3.7.4 .

3.8 Configuring Oracle Web Cache as a Software Load Balancer

For an overview of high availability without a hardware load balancer, see Section 3.4 . To configure a single Oracle Web Cache server as a software load balancer: 1. Use a text editor to open webcache.xml, located in: UNIX ORACLE_INSTANCEinstance_nameconfigWebCachewebcache_name Windows ORACLE_INSTANCE\instance_name\config\WebCache\webcache_name 2. Locate the CACHE element. 3. Add the ROUTINGONLY attribute to the CACHE element. For example: ... CACHE WCDEBUGON=NO CHRONOSONPERNODE=NO CAPACITY=301 VOTES=1 INSTANCENAME=instance_name COMPONENTNAME=component_name ORACLEINSTANCE=instance HOSTNAME=web_cache_host_name ORACLEHOME=directory NAME=web_cache_name ROUTINGONLY=YES ... 4. Save webcache.xml. 5. Restart Oracle Web Cache with the following command: opmnctl restartproc ias-component=component_name This executable is found in the following directory: UNIX ORACLE_INSTANCEbin Windows ORACLE_INSTANCE\bin 6. Verify Oracle Web Cache is running in the load balancer mode from the Oracle Web Cache Manager by verifying the following status message displays beneath the Apply Changes and Cancel Changes buttons: Web Cache running in Routing Only Mode with current configuration Fusion Middleware Control does not provide an equivalent verification status. 7. Configure origin servers, as described in Section 2.11.2 . 8. Create site definitions and map them to the origin servers, as described in Section 2.11.3 and Section 2.11.4 .