Viewing Event Logs and Access Logs Rolling Over Event and Access Logs Using Audit Logs

9-32 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache 10 Configuring Common Deployment Scenarios 10-1 10 Configuring Common Deployment Scenarios This chapter describes how to configure common deployment scenarios using Oracle Web Cache. It includes the following topics: ■ Section 10.1, Using Oracle Web Cache in a Common Deployment ■ Section 10.2, Using a Cache Hierarchy for a Global Intranet Application ■ Section 10.3, Using Oracle Web Cache for High Availability without a Hardware Load Balancer

10.1 Using Oracle Web Cache in a Common Deployment

Figure 10–1 shows Oracle Web Cache in a common Oracle Application Server configuration. A tier of Oracle Web Cache servers cache content for a tier of application Web servers. The application Web servers app1-host1 and app1-host2 provide content for site www.app1.company.com, and app2-host provides content for www.app2.company.com. The two Oracle Web Cache servers reside on dedicated, fast one or two-CPU computers. To increase the availability and capacity of a Web site, these servers are configured as either a cache cluster or a failover pair. Oracle recommends a hardware load balancer to ping each Oracle Web Cache server on a periodic basis to check the status of the cache. As a cache cluster, the two Oracle Web Cache servers provide failure detection and failover. If an Oracle Web Cache server fails, other members of the cache cluster detect the failure and take over ownership of the cached content of the failed cluster member and masks any cache failure. Oracle Web Cache maintains a virtual single cache of content despite a cache failure. The load balancer distributes the incoming requests among cache cluster members. The cache cluster members process the incoming requests. For requests that are not stored in the cache, Oracle Web Cache distributes the requests to an application Web server respective to the site. As a failover pair, both Oracle Web Cache servers are configured to cache the same content. When both Oracle Web Cache servers are running, a load balancer distributes the load among both servers. If one server fails, the other server receives and processes all incoming requests. 10-2 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache Figure 10–1 Deploying Oracle Web Cache In a Common Configuration To configure this topology: 1. Register the IP address of the load balancer with www.app1.company.com and www.app2.company.com.

2. Configure the load balancer with Oracle Web Cache server host names

webche1-host and webche2-host and configure it to ping each cache server periodically to check the status of the cache.

3. Configure the load balancer with to ping each Oracle Web Cache server on a

periodic basis with URL _oracle_http_server_webcache_static_.html, which is stored in the cache.

4. If configuring a cache cluster, specify webche1-host and webche2-host as

cluster members. See Section 3.6 for more information on configuring a cache cluster. Application Servers webche1-host Oracle Web Cache Servers Sites: www.appl.company.com www.app2.company.com webche2-host appl-host1 appl-host2 Application Servers app2-host Network www.appl.company.com www.app2.company.com Load Balancer HTTP and HTTPS HTTP and HTTPS Requests for www.app1.company.com and www.app2.company.com HTTP and HTTPS Database Configuring Common Deployment Scenarios 10-3 5. Configure the Oracle Web Cache servers with the following: ■ Receive HTTP and HTTPS requests on designated listening ports ■ Send HTTP and HTTPS requests to application Web servers app1-host1, app1-host2, and app2-host on designated listening ports ■ Site definition for www.app1.company.com mapped to app1-host1 and app1-host2 ■ Site definition for www.app2.company.com mapped to app2-host For more information, see: ■ Section 2.11.1 for instructions about configuring listening ports ■ Section 2.11.2 for instructions about configuring origin server settings ■ Section 2.11.3 for instructions on creating site definitions and site-to-server mappings

10.2 Using a Cache Hierarchy for a Global Intranet Application

Many Web sites have several data centers. For networks with a distributed topology, you can deploy Oracle Web Cache at each of the data centers in a distributed cache hierarchy . Figure 10–2 on page 10-4 shows a distributed topology in which Oracle Web Cache servers are distributed in offices in the United States and Japan. The application Web servers are located in the United States office, centralizing the data source to one geographic location. The central caches in the United States cache content for application Web servers app1-host1, app2-host2, and app2-host, and the remote cache in Japan caches content from the central caches. Clients make requests to local DNS servers to resolve www.app1.company.com and www.app2.company.com. The local DNS servers are routed to the authoritative DNS server for the respective sites. The authoritative DNS server uses the IP address of the client to pick the closest Oracle Web Cache server to satisfy the request. Then, it returns the IP address of the appropriate Oracle Web Cache server to the client.