Using Oracle Web Cache in a Common Deployment

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. 10-4 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache Figure 10–2 Deploying an Oracle Web Cache Hierarchy 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

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

3. Configure Oracle Web Cache servers us.webche1-host and

us.webche1-host 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 Application Servers us.webche1-host Central Oracle Web Cache Servers Sites: www.appl.company.com www.app2.company.com us.webche2-host appl-host1 appl-host2 Application Servers app2-host Remote Oracle Web Cache Server jp.webche-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-5 ■ 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 4. Configure Oracle Web Cache server jp.webche-host with the following: ■ Receive HTTP and HTTPS requests on designated listening ports ■ Send HTTP and HTTPS requests to application Web servers us.webche1-host and us.webche2-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 5. Enable propagation of invalidation messages for each of the caches in the cache hierarchy: 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 INTERCACHE element, a sub-element of the SECURITY element. 3. Modify the ENABLEINBOUNDICC and ENABLEOUTBOUNDICC attributes to YES. For example: ?xml version=1.0 encoding=ISO-8859-1? CALYPSO ... VERSION DTD_VERSION=11.1.1.0.0 GENERAL CLUSTER NAME=WebCacheCluster ... SECURITY SSLSESSIONTIMEOUT=3600 ... USER TYPE=INVALIDATION ... USER TYPE=MONITORING ... SECURESUBNET ALLOW=ALL DEBUGINFO HEADER=YES ... HTTPREQUEST MAXTOTALHEADERSIZE=819000 ... INTERCACHE ENABLEINBOUNDICC=YES ENABLEOUTBOUNDICC=YES SECURITY ... 4. Save webcache.xml. 6. Restart the caches in the hierarchy 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 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