Install Oracle HTTP Server on WEBHOST2

9-12 Oracle Fusion Middleware High Availability Guide These examples show two different ways of routing requests to Oracle WebLogic managed servers: ■ The ifModule block sends any requests ending in .jsp to the WebLogic managed server cluster located on Apphost1 and Apphost2. ■ The Location block sends any requests with URLs prefixed by weblogic to the WebLogic managed server cluster located on Apphost1 and Apphost2.

9.2.9.2.3 Restart Oracle HTTP Server Restart the Oracle HTTP Server using the following

commands: opmnctl restartproc process-type=OHS

9.2.9.2.4 Validate the Oracle HTTP Server Configuration Validate the configuration using

the following URLs: http:myapp.mycompany.com:7777weblogic http:myapp.mycompany.com:7777weblogic

9.2.9.3 Install Oracle HTTP Server on WEBHOST2

On WEBHOST2, perform the steps from Section 9.2.9.2, Install Oracle HTTP Server on WEBHOST1. Validate the Installation Validate the installation using the following URL to access the Oracle HTTP Server home page: http:webhost2:7777 Note: If using SSL termination AND routing requests to WebLogic then the following additional configuration is required. In the WebLogic console, WebLogic Plugin Enabled must be set to true, either at the domain, cluster or managed server level. In the Location block which directs requests to the WebLogic managed servers, the following lines also need to be added. WLProxySSL ON WLProxySSLPassThrough ON For example: Location weblogic SetHandler weblogic-handler WebLogicCluster apphost1.mycompany.com:7050,apphost2.com:7050 WLProxySSL On WLProxySSLPassThrough ON Debug ERR WLLogFile u01apporacleadminWL1logsmod_wl_ohs.log DefaultFileName index.jsp Location After enabling the WebLogic plugin, restart the Administration Server. Configuring High Availability for Web Tier Components 9-13

9.2.9.3.1 Configure Virtual Hosts Add an entry for each virtual host or site name to the

Oracle HTTP Server configuration. Copy the file virtual_hosts.conf from WEBHOST1 to WEBHOST2. This is located in the ORACLE_INSTANCEconfigOHSohs_ component_namemoduleconf directory.

9.2.9.3.2 Configure mod_wl_ohs After installing and configuring the Oracle HTTP

Server, link it to any defined WebLogic Server instances by copying the file mod_wl_ ohs.conf file located in the ORACLE_INSTANCEconfigOHSohs_component_name directory from WEBHOST1.

9.2.9.3.3 Restart Oracle HTTP Server Restart the HTTP Server using the following

commands: opmnctl restartproc process-type=OHS

9.2.9.3.4 Validate the Oracle HTTP Server Configuration Validate the configuration using

the following URLs: http:myapp.mycompany.com https:myapp.mycompany.com if using SSLSSL termination http:myapp.mycompany.com:7777weblogic

9.3 Oracle Web Cache and High Availability Concepts

Oracle Web Cache is a content-aware server accelerator, or reverse proxy, for the Web tier that improves the performance, scalability, and availability of Web sites that run on Oracle HTTP Server. Oracle Web Cache is the primary caching mechanism provided with Oracle Fusion Middleware. Caching improves the performance, scalability, and availability of Web sites that run on Oracle Application Server by storing frequently accessed URLs in memory. By storing frequently accessed URLs in memory, Oracle Web Cache eliminates the need to repeatedly process requests for those URLs on the application Web server and database tiers. Unlike legacy proxies that handle only static objects, Oracle Web Cache caches both static and dynamically generated content from one or more application Web servers. Because Oracle Web Cache is able to cache more content than legacy proxies, it provides optimal performance by greatly reducing the load on application Web server and database tiers. As an external cache, Oracle Web Cache is also an order of magnitude faster than object caches that run within the application tier.

9.3.1 Oracle Web Cache Single-Node Characteristics

Oracle Web Cache is fully compliant with HTTP 1.0 and 1.1 specifications. Therefore, it can accelerate Web sites that are hosted by any standard web servers, such as Apache and IIS. In Oracle Fusion Middleware, Oracle Web Cache resides in front of one or more instances of Oracle HTTP Server. Responses to browser based HTTP requests are directed to the Oracle HTTP Server instance and transmitted through Oracle Web Cache. The Oracle Web Cache instance can handle any Web content transmitted with standard HTTP protocol. A reverse proxy appears to be the content server to clients but internally retrieves its objects from other backend origin servers as a proxy. A reverse proxy acts as a gateway to the origin servers. It relays requests from outside the firewall to origin servers behind the firewall, and delivers retrieved content back to the client.