In the navigator frame, select Operations Cache Operations.

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 .