An Oracle White Paper October Oracle HTTP Server 12cR1 - Technical Overview

Transcription

1 An Oracle White Paper Octber 2014 Oracle HTTP Server 12cR1 - Technical Overview 1

2 Table f Cntents Intrductin... 3 Oracle HTTP Server Capability Overview... 3 Oracle HTTP Server Architecture Overview... 5 Oracle HTTP Server Mdules... 6 Oracle HTTP Server 12c Administratin Overview... 8 WebLgic Management Framewrk... 8 Managing OHS 12c with WebLgic Server Dmain... 9 Managing OHS 12c with Standalne Dmain Cnfiguring OHS 12c with WebLgic Server Dmain Develpment and Testing Scenari Prductin Scenari Cnfiguring OHS 12c with Standalne Dmain Administering OHS 12c with WebLgic Server Dmain Starting WebLgic Admin Server Starting WebLgic Nde Manager Starting Oracle HTTP Server Instance 12c Administering OHS 12c thrugh WebLgic Scripting Tl Oracle HTTP Server 12c (Standalne Dmain) Oracle HTTP Server 12c (WebLgic Server Dmain) Creating OHS 12c Instance Deleting OHS 12c Instance Starting OHS 12c Instance Stpping OHS 12c Instance Sft Restart f OHS 12c Instance Retrieve OHS 12c Instance Status Retrieve OHS 12c Mnitring Statistics Accessing the OHS cnfiguratin prperties Appendix Installing WebLgic JRF 12cR Installing Oracle HTTP Server 12cR1 (12.1.x) (Cllcated) Installing Oracle HTTP Server 12cR1 (12.1.x) (Standalne) Cnclusin

3 Intrductin Oracle HTTP Server 12c prvides the key infrastructure fr serving the Internet s HTTP(s) prtcl and handles the Web Tier respnsibilities with rbust cntent serving and reverse prxy capabilities. The key aspects f Oracle HTTP Server (OHS) are: Technlgy: OHS is based n the prven, pen surce technlgy - Apache HTTP Server. OHS 11g ( x) and 12cR1 (12.1.2/12.1.3) release is based n the latest versins f the Apache 2.2 release. Oracle HTTP Server als includes additinal capabilities that are very relevant t the Fusin Middleware deplyment and are typically nt available within the pen surce Apache HTTP Server. Cntent Serving: OHS prvides the ability t serve static web cntent (like HTML5, images etc.) t the end-user and als t cache this static web cntent in memry fr better thrughput. In additin, OHS includes the ability t serve dynamic web cntent that are based n web scripting technlgies like PHP, Pythn, Ruby etc. thrugh its built-in CGI/FastCGI mdules. Reverse Prxy: Act as a Reverse Prxy and transparently pass thrugh the incming HTTP(s) requests t the back-end cntent (applicatin r simply rigin ) server. This allws administratrs t cnfigure rules within OHS t authenticate and authrize the incming HTTP(s) requests befre efficiently ruting t ne r mre cntent (applicatin r simply rigin ) servers. Integratin: Oracle HTTP Server 12c includes end-t-end integratin with the Fusin Middleware Applicatins allwing administratrs t prvisin, cnfigure, administer, and mnitr the entire Fusin Middleware Applicatin deplyment. In additin, Oracle HTTP Server als supprts stand-alne deplyment scenari and supprts frnt-ending nn-oracle HTTP servers thrugh its built-in reverse prxy md_prxy mdule. Oracle HTTP Server 12c and abve leverages the WebLgic Management Framewrk t deliver cnsistent administratin within Oracle HTTP Server, Oracle Web Lgic Server and the rest f the Fusin Middleware applicatins. This dcument prvides a technical verview f Oracle HTTP Server and the new administratin related capabilities available within the Oracle HTTP Server 12cR1 (12.1.x) release. Oracle HTTP Server Capability Overview Oracle HTTP Server is the latest release within the Oracle HTTP Server 12cR1. Here is the high level summary f all the capabilities included within the latest Oracle HTTP Server (OHS) release. Prtcl: OHS is capable f handling and respnding t simultaneus HTTP 1.0/1.1 and HTTPS (SSL 3.0 and TLS 1.2) traffic frm multiple users. Mass Virtual Hsting: Enables custmers (large enterprises r ISPs) t hst several web sites with different name within a single OHS instance. This allws administratrs t cnslidate multiple web 3

4 sites and its assciated business applicatins within a single OHS instance. This capability is typically achieved by cnfiguring multiple Virtual Hsts within Apache HTTP Server based OHS. Fr mre infrmatin, please see Virtual Hsts sectin within Apache HTTP Server dcumentatin. URL Rewriting: This capability allws administratrs t quickly rerganize their web sites withut any impact n externally visible URLs. Fr mre infrmatin, please see URL Rewrite sectin within Apache HTTP Server dcumentatin. Cntent Serving: OHS typically serves the client requested cntent thrugh ne f these ways send the cntent frm the disk, send the utput generated frm executing the CGI/FastCGI scripts, send the utput generated by the back-end applicatin server (reverse prxy). Cntent Caching: Administratrs can leverage the built-in caching capabilities f the Apache HTTP Server t cache the cntents either t the disk r t the memry thereby imprving the web site thrughput and respnse time. Fr mre infrmatin, please see Cntent Caching sectin within Apache HTTP Server dcumentatin. Reverse Prxy: OHS includes the Apache HTTP Server prvided built-in reverse prxy mdules like md_prxy t frnt-end the incming request t the back-end applicatin server and send the respnse back t the client. This setup allws administratrs t leverage OHS t implement their crprate plicies (like authenticatin, authrizatin etc.) befre the request is sent t the back-end HTTP cmpliant applicatin server(s). WebLgic Prxy Plug-In: OHS bundles WebLgic Web Server Prxy Plug-In fr Apache. This capability allws OHS t efficiently lad balance the incming traffic t the back-end WebLgic managed servers r clusters. In additin, management cnsle accessible within OHS 12c als prvides the administratin capability fr this mdule. Authenticatin/Authrizatin: OHS bundles Apache HTTP Server prvided mdules related t implementing the authenticatin and authrizatin plicies. Fr mre infrmatin n hw t implement the varius authenticatin / authrizatin plicies, please refer t Authenticatin and Authrizatin sectin within Apache HTTP Server dcumentatin. Single Sign-On: Emplyees and Crprate IT teams prefer that the emplyee authenticatin (username / passwrd) infrmatin is shared and accessible between multiple web applicatins deplyed within their crprate Intranet. Administratrs can leverage the Web Gate mdule (md_webgate) bundled within OHS t enable single sign-n with Oracle Access Management (OAM). This capability allws administratrs t prvisin cnfigure and administer the Oracle Single Sign-On slutin. SSL: OHS is designed t handle and terminate SSL cnnectins while prcessing the HTTPS traffic. Unlike the pen surce versin f the Apache HTTP Server, OHS handles such SSL traffic thrugh its wn SSL libraries (md_ssl mdule) t meet the strict crprate security requirements. These SSL libraries supprt the latest versin f the SSL prtcls including TLS 1.0/1.1 prtcls. Accrdingly, administratrs can leverage OHS 12c t prcess HTTPS traffic n their web sites with either SSL v3 r TLS 1.0/1.1 prtcls. Fr mre infrmatin, please see SSL Cipher prduct dcumentatin. OHS 12c includes the fllwing additinal capabilities: 4

5 Hardware Offlading Supprt Offlad AES crypt transactins t the hardware crypt n Intel x86 and SPARC T4/T5 prcessrs and thereby significantly imprve the verall HTTPs traffic thrughput. FIPS Level 1 - FIPS certified runtime libraries. This capability allws administratrs t cmply with FIPS (Level 1) certificatin by using Oracle HTTP Server based Web Tier slutin. Fr mre infrmatin hw t enable this FIPS certified runtime libraries within OHS, please refer t SSL cnfiguratin sectin within Oracle HTTP Server dcumentatin. Variable Security per Resurce - This feature allws different web resurces (like Directries that hsts web cntents) t be prtected by different strength encryptin. SSL in Reverse prxy scenari - OHS nt nly supprts terminating incming SSL cnnectins but als supprts initiating a SSL cnnectin, when OHS is deplyed in a Reverse Prxy mde (either using the built-in md_prxy r using WebLgic Web Server Plug-In - md_wl_hs), with the back-end rigin server. Management: OHS 12c administratin leverages the WebLgic Management Framewrk t prvide a cnsistent administratin experience with the rest f the Fusin Middleware applicatins. The OHS 12c administratin nw supprts administering ne r mre OHS instances running n ne r mre hsts (machines). Users can administer OHS using the management cnsle cmmnly referred as Fusin Middleware Cntrl. T leverage this cnsle, user will need t chse t install OHS in a WebLgic Server Dmain (r simply Cllcated ) scenari. Fr mre infrmatin, please refer t sectin - Administering OHS 12c with WebLgic Server Dmain. Oracle HTTP Server Architecture Overview Oracle HTTP Server (OHS) 12cR1 (12.1.2/12.1.3) is based n the Apache HTTP Server 2.2 architecture and accrdingly leverages the highly mdular architecture within the Apache HTTP Server 2.2. The Apache HTTP Server architecture can be simplified as an architecture that uses ne f the Multi- Prcessing Mdules (MPM) at its cre and all ther capabilities including the ability t serve HTTP traffic is designed as mdules. Oracle HTTP Server (OHS), unlike Apache HTTP Server, uses nly the Wrker MPM as its cre architecture fr handling the HTTP traffic. This architecture allws OHS t seamlessly handle the cntent serving as well as the reverse prxy use cases. When Apache HTTP Server is prcessing an incming HTTP request, varius mdules (and its APIs) are apprpriately invked at the apprpriate request / respnse lifecycle. 5

6 Figure HTTP Request Respnse Cycle Custmers can leverage this mdular architecture and develp their wn custm Apache HTTP Server 2.x cmpatible mdules t supplement the functinality prvided by OHS. Hwever, Oracle Supprt may request that these custm mdules are remved frm the OHS cnfiguratin if there is a sufficient reasn t believe that these mdules can interfere, while trubleshting, with the custmer reprted OHS related issues. Oracle HTTP Server Mdules Apache HTTP Server mdules are the plug-in mdules t the cre t allw the administratrs t extend the basic functinality f Apache HTTP Server either as cntent server r as a (reverse) prxy server. Oracle HTTP Server (OHS) includes mst f the standard mdules included within the standard Apache 2.2 release. In additin, OHS carries these additinal mdules t prvide a seamless integratin with the Fusin Middleware Architecture: Fr mre infrmatin, please visit Oracle HTTP Server 12c mdules dcumentatin. Table- Additinal Mdules available within OHS 12cR1 Mdule Name Mdule Versin Mdule Descriptin Md_wl_hs 12.1.x.0.0 WebLgic Web Server Prxy Plug-In fr Oracle HTTP Server This mdule allws OHS t effectively frnt-end the HTTP traffic t the back-end WebLgic managed server r clusters. This mdule replaces the functinality f the traditinal md_prxy mdule while frnt-ending WebLgic Server applicatins. Md_ssl 12.1.x.0.0 Oracle SSL mdule that intercepts the SSL traffic cming t OHS t handle SSL handshake and then t apprpriately terminate the SSL traffic. 6

7 This mdule replaces the traditinal md_ssl mdule while handling SSL traffic. This mdule leverages the RSA prvided cypt libraries and accrdingly ffers FIPS (Level 1) certificatin. Fr mre infrmatin, please refer t prduct dcumentatin. Md_Perl This mdule allws custmers t run their Perl scripts within OHS. This mdule is nw marked as Deprecated and will be remved in future releases. Md_plsql This mdule allws administratrs t cnnect t the Oracle Database frm the OHS and thereby create web applicatins using the stred prcedures capabilities available within the Oracle Database. This mdule is nw marked as Deprecated and will be remved in future releases. Md_fastcgi This mdule supprts the FastCGI prtcl t allw users t efficiently run the traditinal CGI applicatins thereby eliminating the startup and initializatin verhead. This mdule is nw marked as Deprecated and will be either remved r replaced with anther mdule in future releases. Md_security 2.6 Web Applicatin Firewall mdule, based n pen surce Md Security mdule. Administratrs can leverage the Md Security rule capabilities t develp and deply apprpriate rules t prtect their web applicatins frm knwn security vulnerabilities like SQL Injectin, Crss Site Scripting Request Frgery (CSRF), Cmmand Injectin etc. Administratrs can als leverage the pen surce OWASP Cre Rule Set - a set f pre-built rules - as a fundatin t prtect their applicatin frm these well knwn security vulnerabilities. Md_dms 12.1.x.0.0 Prvides Mnitring infrmatin frm every OHS server instances t the Oracle Fusin Middleware Cntrl Cnsle r Oracle Enterprise Manager Clud Cntrl t prvide a unified mnitring infrmatin acrss the entire farm. 7

8 Oracle HTTP Server 12c Administratin Overview This sectin prvides an verview f Oracle HTTP Server 12c Administratin and intrduces the different scenaris and steps in administering Oracle HTTP Server 12c thrugh the WebLgic Management Framewrk. Oracle HTTP Server (OHS) 12c ffers the ability t administer OHS and the rest f the Clud Applicatin Fundatin 12c infrastructure using the WebLgic Management framewrk. This integrated administratin apprach allws administratrs t manage their entire infrastructure thrugh a cnsistent interface. WebLgic Management Framewrk WebLgic Management Framewrk 12c is the framewrk designed t administer system cmpnents like Oracle HTTP Server and the rest f the Fusin Middleware applicatins including WebLgic Server and prvides tw ways f administering Oracle HTTP Server: WebLgic Server Dmain Cntains a WebLgic Administratin Server, zer r mre WebLgic Managed Servers, and zer r mre System Cmpnent Instances (fr example, an Oracle HTTP Server instance). A WebLgic Server Dmain can span multiple physical machines, and the administratin server centrally manages these instances and machines. Because f these prperties, a WebLgic Server Dmain prvides the best integratin between yur System Cmpnents (like OHS) and Java EE Cmpnents (like FMW applicatins). The primary use cases fr chsing t administer OHS using Standalne Dmain are: Yu d want OHS t frnt-end Fusin Middleware dmain (like SOA applicatins) Yu d need the management and mnitring functinality prvided by the brwser based Fusin Middleware Cntrl cnsle. Yu are cmfrtable with installing WebLgic / JRF libraries and OHS in the same installatin lcatin (Cllcated). Standalne Dmain - Cntainer fr ne r mre system cmpnents, such as Oracle HTTP Server. It has a directry structure similar t an Oracle WebLgic Server Dmain, but it des NOT cntain an Administratin Server r Managed Servers. Fr standalne dmains, the WebLgic Management Framewrk supprts these WebLgic administratin tls Nde Manager, WebLgic Scripting Tl (WLST), Cnfig Wizard, and Pack/Unpack. The primary use cases fr chsing t administer OHS using Standalne Dmain are: Yu d NOT want OHS t frnt-end Fusin Middleware dmain. Hwever, yu can still frnt-end WebLgic Managed Server(s)/Cluster(s) by manually cnfiguring the WebLgic Plug-In cnfiguratin file. Yu d NOT need the management and mnitring functinality prvided by Fusin Middleware Cntrl. Hwever, administratrs can still leverage WebLgic Scripting 8

9 Tl (WLST) t administer OHS and mnitr the OHS perfrmance using the Apache HTTP Server prvided tls like md_status mdules. Yu want t prvisin OHS in a "demilitarized zne" (DMZ; that is, the zne between the internal and external firewalls). Accrdingly, yu want t minimize the installatin ftprints and the dependencies and d NOT want t pen additinal management prts (typically used by the WebLgic Nde Manager within the Management Framewrk). Managing OHS 12c with WebLgic Server Dmain In this scenari, users can administer the OHS cnfiguratin and server lifecycle thrugh either the Fusin Middleware Cntrl cnsle r the WLST. Figure - OHS Administratin with WebLgic Server Dmain This scenari is applicable when users chse t install OHS, WebLgic and JRF in the same installatin lcatin t be able t manage their Oracle HTTP Server thrugh a brwser based administratin cnsle (Fusin Middleware Cntrl Cnsle) r thrugh a cmmand line based WebLgic Scripting Tl (WLST). T implement this scenari, users need t implement the fllwing sequence f steps t administer OHS: 9

10 If yur system des NOT have JDK7, then users will need t dwnlad and Install Java SE 7 Develpment Kit in yur machine. Yu can dwnlad Java SE 7 frm here. If yur installatin lcatin (say Oracle Middleware Hme) des NOT include JRF enabled WebLgic , then yu can dwnlad JRF enabled WebLgic Fusin Middleware Infrastructure frm here. Fr mre infrmatin, please refer t sectin Cnfiguring Fusin Middleware Infrastructure dmain. Install Oracle HTTP Server 12c (12.1.3) in the same lcatin as abve WLS + JRF enabled installatin lcatin (the same Oracle Middleware Hme). Fr mre infrmatin n OHS installatin, please refer t sectin Installing Oracle HTTP Server 12cR1. Cnfigure Oracle HTTP Server 12c dmain as mentined within Cnfiguring Fusin Middleware Infrastructure dmain. Fr mre infrmatin, please refer t sectin Installing Oracle HTTP Server 12cR1 (12.1.x) (Cllcated) Start WebLgic Administratin Server and launch Fusin middleware cnsle thrugh Users shuld be nw able t administer OHS using the Fusin Middleware Cntrl cnsle. Fr mre infrmatin, please see sectin. Managing OHS 12c with Standalne Dmain In this scenari, users can prvisin Oracle HTTP Server with minimal dependency and administer the server lifecycle using the integrated WebLgic Nde Manager interface. Figure - OHS Administratin with Standalne Dmain This scenari is applicable when users (develpers and system administratrs) like t install OHS with a minimum ftprint and dependencies and des nt really need t administer OHS (lcally r remtely) thrugh a brwser based administratin cnsle. In additin, system administratrs will prefer this scenari, when OHS is installed and prvisined as a prxy in a De-Militarized zne (DMZ). T implement this scenari, users need t implement the fllwing sequence f steps t administer OHS: 10

11 If yur system des NOT have JDK7, then users will need t dwnlad and Install Java SE 7 Develpment Kit in yur machine. Yu can dwnlad Java SE 7 frm here. Yu can dwnlad Oracle HTTP Server 12cR1 binaries frm here and install Oracle HTTP Server (using Standalne as the ptin) in a given lcatin (say Oracle Middleware Hme). Fr mre infrmatin n OHS installatin, please refer t sectin nstalling Oracle HTTP Server 12cR1 (12.1.x) (Standalne) Cnfigure Oracle HTTP Server using Fusin Middleware Cnfig Wizard. Fr mre infrmatin, please see sectin Cnfiguring OHS 12c with Standalne. Start WebLgic Nde Manager and leverage WebLgic Administratin Framewrk cmmand line interface (WLST) t prvisin ne r mre OHS instances and start / stp these OHS server instances. Fr mre infrmatin, please refer t sectin. Cnfiguring OHS 12c with WebLgic Server Dmain This sectin walks thrugh the steps invlved in cnfiguring Oracle HTTP Server 12c within WebLgic Server dmain fr bth develpment and prductin scenari s that administratrs can leverage the WebLgic Management Framewrk t administer OHS and the rest f the Fusin Middleware applicatins. Users can als visit the Cnfiguring OHS 12cR1 in a WebLgic Server Dmain prduct dcumentatin fr mre infrmatin. This sectin assumes that users have successfully cmpleted these steps: Installing JRF enabled WebLgic (aka Fusin Middleware Infrastructure ) Installing OHS (as Cllcated with JRF enabled WLS ) Once WLS and OHS is installed successfully, then users can leverage the WebLgic cnfiguratr t setup a dmain and a WLS Nde Manager t manage ne r mre OHS instances. Nw, users can cnfigure OHS within WebLgic Server Dmain thrugh ne f these methds: Invke Fusin Middleware Cnfig Wizard 12c and prvisin WebLgic with Expanded Dmain and select Oracle HTTP Server template. Fr mre infrmatin, please see Cnfiguring OHS in WebLgic Server Dmain sectin. This ptin is supprted fr prductin deplyments and requires a database. Use the WebLgic Scripting Tl (WLST) t create a OHS Test Dmain. This ptin des nt have any dependency n a database. This ptin is designed fr develpment and staging envirnment nly. Accrdingly, this ptin is nt prductin certified deplyment cnfiguratin. This sectin will walk thrugh the step-by-step prcess f cnfiguring OHS in bth these scenaris. 11

12 Develpment and Testing Scenari At the end f installing WebLgic (JRF enabled) Server and Oracle HTTP Server , users will need t prvisin a WebLgic dmain t create and administer a Oracle HTTP Server instance. Fr develpment and testing scenaris, users can leverage the OHS prvided cmmand line interface fr WebLgic Scripting Tl (WLST) and prvisin a OHS dmain and the crrespnding server instance within WebLgic Administratin Server. This is dne in tw steps. Prvisin OHS Dmain The first step is t prvisin the OHS dmain within WebLgic. Users can run the fllwing cmmand thrugh the cmmand line terminal windw t prvisin a OHS dmain (as Base Dmain within WebLgic Administratin Server) (On Linux) <ORACLE_MIDDLEWARE_HOME>/hs/cmmn/bin/wlst.sh (On Windws) <ORACLE_MIDDLEWARE_HOME>\hs\cmmn\bin\wlst.cmd And run the fllwing cmmands: wls:/ffline> createohstestdmain(adminaccuntpass= welcme1,,nmaccuntname= nm, nmaccuntpass= welcme1 ) wls:/ffline> exit() where adminaccuntpass -> cntains the passwrd t use t lgin t WebLgic Administratin Server nmaccuntname -> cntains the user name t use within WebLgic Nde Manager nmaccuntpass -> cntains the passwrd t use fr this WebLgic Nde Manager. This abve cmmand cnfigures a WebLgic Administratin Server with a Base Dmain. As a next step, we will need t create the OHS instance that can be managed using this WebLgic Administratin Server. This step requires the WebLgic Nde Manager and Administratin Server services, assciated within this Base Dmain, enabled and running. T d s, users will need t first the start the WebLgic Nde Manager and WebLgic Administratin Server by running the fllwing cmmands: 12

13 Start Web Lgic Nde Manager (On Linux) <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/base_dmain/bin/startNdeManager.sh & (On Windws) <ORACLE_MIDDLEWARE_HOME>\user_prjects\dmains\base_dmain\bin\startNdeManager.cmd & Start Web Lgic Administratin Server (On Linux) <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/base_dmain/bin/startWebLgic.sh & (On Windws) <ORACLE_MIDDLEWARE_HOME>\user_prjects\dmains\base_dmain\bin\startWebLgic.cmd & Prvisin OHS Instance The secnd step is t prvisin the OHS instance. This step requires WebLgic Administratin Server and WebLgic Nde Manager t be running. Fr mre infrmatin n hw t start WebLgic Administratin Server and Nde Manager, refer t the abve sectin. Once WebLgic Administratin Server and the Nde Manager are running successfully, users can leverage the OHS prvided cmmand line interface t WebLgic Scripting Tl (WLST) t create an OHS instance by running the fllwing cmmand: (On Linux) <ORACLE_MIDDLEWARE_HOME>/hs/cmmn/bin/wlst.sh (On Windws) <ORACLE_MIDDLEWARE_HOME>\hs\cmmn\bin\wlst.cmd And run the fllwing cmmands: wls:/ffline> cnnect() wls:/base_dmain/servercnfig> createohsinstance(instancename= hs1, machine= lcalmachine, listenprt= 7777, sslprt= 4443, adminprt= 9999 ) where instancename -> <hs-instance-name> (this creates the OHS instance with this name) machine -> <cnfigured-machine-name> (this uses the machine name that was used t create the OHS Test Dmain in the previus cmmand) 13

14 This cmmand des a basic errr checking f instance name, machine name and the prt infrmatin befre cnfiguring the OHS instance. Here-frth, the OHS instance hme lcatin is referred as OHS_INSTANCE_HOME where this lcatin translates t <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/base_dmain In this abve cmmand, instancename and machine are the nly required ptins and the rest are ptinal. If the ther ptins like listenprt, sslprt r adminprt are nt prvided, then the createohsinstance will make a best effrt t create the OHS instance using the default prts fr these. If in case, users d NOT remember the assciated machine infrmatin with this Base Dmain, then they can find the machine name infrmatin used within this dmain cnfiguratin by running the fllwing cmmands: Lk fr <machine> element within the <OHS_INSTANCE_HOME>/cnfig/cnfig.xml OR Within WLST, run the fllwing: cnnect() ServerCnfig() cd( Machines ) ls() This cmmand will create OHS instance cnfiguratins under <ORACLE_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/hs1 -> this acts as a cnfiguratin repsitry fr WLS Admin Server running n this dmain. This cnfiguratin repsitry is used t replicate the OHS cnfiguratin n mre than ne machine (clustered deplyment). <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/instances/hs1 -> this is where WLS Nde Manager manages the cnfiguratin n the current machine and is typically created n every machine in a clustered deplyment. The OHS HTTPd server prcesses als use this cnfig directry. Nte: If the WLS Nde Manager is unavailable, then the create peratin will cmplete nly partially. In this case, nly the files under <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/hs1 will be created. When the WLS Nde Manager cmes back up nline again, then the rest f the files under <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/instances/hs1 will be created apprpriately. Als, users can nw access the Fusin Middleware Cntrl cnsle a brwser based administratin cnsle t administer Oracle HTTP Server (OHS) server lifecycle and cnfiguratins by accessing the fllwing URL where this URI can be translated as where 14

15 <hstname> -> refers t the hstname f the machine where Oracle HTTP Server is installed <OHS-HTTP-LISTENER-PORT> -> refers t the http listener prt. By default, this is set t 7777 Fr next steps, users can refer t OHS prduct dcumentatin - Next Steps After Cnfiguring OHS in WebLgic Dmain and specifically refer t sectin - Next Steps fr OHS in WebLgic Dmain. Prductin Scenari At the end f installing WebLgic (JRF enabled) Server and Oracle HTTP Server , users will need t prvisin a WebLgic dmain t create and administer Oracle HTTP Server instance. Fr prductin scenaris, users will need t leverage the Fusin Middleware Cnfig Wizard t cnfigure a OHS dmain within WebLgic and the crrespnding OHS instance within this dmain. This step has a dependency n a database. The step-by-step installatin steps are cvered within ur prduct dcumentatin - Cnfiguring OHS in a WebLgic Server Dmain. Once OHS dmain and the instance has been prvisined, users can nw administer the server instance using the WebLgic Management framewrk. Als, users can nw access the Fusin Middleware Cntrl cnsle a brwser based administratin cnsle t administer Oracle HTTP Server (OHS) server lifecycle and cnfiguratins by accessing the fllwing URL where this URI can be translated as where <hstname> -> refers t the hstname f the machine where Oracle HTTP Server is installed <OHS-HTTP-LISTENER-PORT> -> refers t the http listener prt. By default, this is set t 7777 Fr next steps, users can refer t OHS prduct dcumentatin - Next Steps After Cnfiguring OHS in WebLgic Dmain and specifically refer t sectin - Next Steps fr OHS in WebLgic Dmain. Cnfiguring OHS 12c with Standalne Dmain This sectin walks thrugh the steps invlved in administering Oracle HTTP Server with minimal dependency n the WebLgic Management framewrk and the accmpany database. This use case is useful fr administering OHS when deplyed within the DMZ envirnment. T administer OHS in this envirnment, users need t successfully install Oracle HTTP Server (say under Oracle Middleware Hme). Fr mre infrmatin n installing OHS, refer t sectin - nstalling Oracle HTTP Server 12cR1 (12.1.x) (. After installing OHS , users can nw cnfigure OHS using the Oracle Fusin Middleware Cnfig Wizard and chse the Standalne ptin. 15

16 Users can invke the Fusin Middleware Cnfig Wizard as fllws (On Linux) <ORACLE_MIDDLEWARE_HOME>/racle_cmmn/cmmn/bin/cnfig.sh (On Windws) <ORACLE_MIDDLEWARE_HOME>\racle_cmmn\cmmn\bin\cnfig.cmd Nte: On Linux machines, the cnfiguratr wizard will require a valid X11 display t be available fr the GUI t appear. This wizard prvisins Web Lgic Nde Manager and Oracle HTTP Server (OHS) instance. Web Lgic Nde Manager will be used t administer the OHS server life cycle. Fr mre infrmatin n hw t cnfigure OHS using this Fusin Middleware Cnfig wizard, please refer t dcumentatin - Cnfiguring Oracle HTTP Server 12c in a Standalne Dmain Fr next steps, users can refer t OHS prduct dcumentatin - Next Steps fr OHS 12c in Standalne Dmain. Administering OHS 12c with WebLgic Server Dmain T administer OHS instances using the WebLgic Management framewrk, users will need t start the WebLgic Administratin Server and the WebLgic Nde Manager and leverage either Fusin Middleware Cntrl cnsle r WebLgic Scripting Tl (WLST) t manage the OHS instance lifecycle. As a first step, users will need t the start the WebLgic Nde Manager and Administratin Server. Starting WebLgic Admin Server This is typically accmplished as fllws: Set up JAVA_HOME envirnment variable t reflect the lcatin f JDK/JRE6 r JDK/JRE7 n yur machine. JAVA_HOME=<jdk-install>; exprt JAVA_HOME Set up ORACLE_ MIDDLEWARE_HOME envirnment variable t reflect the installatin lcatin where OHS and WLS are cllcated tgether. ORACLE_MIDDLEWARE_HOME=<hs installatin>; exprt ORACLE_HOME Set up JAVA_OPTIONS envirnment variable t allw ignring the SSL hst name verificatin JAVA_OPTIONS= -Dweblgic.security.SSL.ignreHstnameVerificatin=true ; exprt JAVA_OPTIONS 16

17 Nte: On Windws, users will need t apprpriately set this envirnment variable frm the cmmand line windw using the set cmmand and then start the WebLgic server frm the same cmmand line terminal windw. Finally, users can nw start the WLS Admin Server as fllws: Where: <OHS_INSTANCE_HOME>/bin/startWebLgic.sh (On Linux) <OHS_INSTANCE_HOME>\bin\startWebLgic.cmd (On Windws) <OHS_INSTANCE_HOME> -> <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/<hs-dmain> The WebLgic Admin server lgs are typically lcated at <OHS_INSTANCE_HOME>/servers/AdminServer/lgs directry. Nte: WLS cnfiguratr wizard defaults t 7001 as the default prt fr running the WLS Admin Server. Hwever, if the cnfiguratr wizard determines that this prt is being used by anther applicatin, then a randm prt will be allcated and this infrmatin shuld have been available in the cnfiguratin summary at the end f the WLS cnfiguratr wizard. Starting WebLgic Nde Manager This is typically accmplished as fllws: Set up JAVA_HOME envirnment variable t reflect the lcatin f JDK/JRE6 r JDK/JRE7 n yur system. JAVA_HOME=<jdk-install>; exprt JAVA_HOME Set up ORACLE_MIDDLEWARE_HOME envirnment variable t reflect the installatin lcatin where OHS and WLS are cllcated tgether. ORACLE MIDDLEWARE_HOME=<hs installatin> ; exprt ORACLE_HOME Set up JAVA_OPTIONS envirnment variable t allw ignring the SSL hst name verificatin JAVA_OPTIONS= -Dweblgic.security.SSL.ignreHstnameVerificatin=true ; exprt JAVA_OPTIONS Nte: On Windws, users will need t apprpriately set this envirnment variable frm the cmmand line windw set JAVA_HOME etc and then start the WebLgic Nde Manager frm the same cmmand line terminal windw. Finally, users can nw start the WLS Nde Manager as fllws Where: <OHS_INSTANCE_HOME>/bin/startNdeManager.sh (On Linux) <OHS_INSTANCE_HOME>\bin\startNdeManager.cmd (On Windws) 17

18 <OHS_INSTANCE_HOME> refers t <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/<hsdmain> The WLS Nde Manager is typically lcated at <OHS_INSTANCE_HOME>/ndemanager/ndemanager.lg. Users are hereby advised t refer t these lg files t ensure that WLS Admin Server and WLS Nde Manager is running successfully. Nte: WLS cnfiguratr wizard defaults t 5556 as the default prt fr running the WLS Nde Manager. Users can chse an apprpriate prt within the WLS cnfiguratr wizard. Starting Oracle HTTP Server Instance 12c The last step in administering the OHS instance is t start the OHS instance. This is typically accmplished by starting the Oracle HTTP Server directly frm a cmmand line that is, withut launching WLST by entering the fllwing cmmand: Linux: <ORACLE_MIDDLEWARE_HOME>/user_prjects/dmains/base_dmain/bin/startCmpnent.s h <cmpnentname> Windws: <ORACLE_MIDDLEWARE_HOME>\user_prjects\dmains\base_dmain\bin\startCmpne nt.cmd <cmpnentname> Where cmpnentname is the name f the OHS instance like hs1 etc. Fr mre infrmatin, please refer t OHS dcumentatin n Perfrming Basic OHS Tasks. Administering OHS 12c thrugh WebLgic Scripting Tl Oracle HTTP Server 12c leverages WebLgic Scripting tl (WLST) a scriptable cmmand line administratin interface fr its administratin tasks. This allws users t administer FMW infrastructure cmpnents like Oracle HTTP Server and WebLgic Server in a cnsistent and seamless manner. Fr mre infrmatin, please refer t WLST syntax reference. And specifically the custm OHS 12c administratin interface within WLST. The administratin capabilities f WLST depend n hw Oracle HTTP Server (OHS) is prvisined. This sectin will fcus n the limitatins and the steps t accmplish cmmn administratin tasks within Oracle HTTP Server using the WLST cmmand interface. 18

19 Oracle HTTP Server 12c (Standalne Dmain) When Oracle HTTP Server is prvisined in standalne dmain, WebLgic Administratin Server is nt available in this cnfiguratin. Hence, WebLgic Scripting Tl (WLST) can be used t nly mnitr and administer OHS server lifecycle peratins (like start, stp and sft restart). Oracle HTTP Server 12c (WebLgic Server Dmain) When Oracle HTTP Server is prvisined in WebLgic Server dmain, WebLgic Administratin Server is available in this cnfiguratin. Hence, WebLgic Scripting Tl (WLST) can be used t perfrm all the Oracle HTTP Server (OHS) administratin tasks including server lifecycle peratins (like start, stp and sft restart), managing cnfiguratins and mnitring the server instances. T launch the WLST cmmand fr administering OHS server life cycle, users will need t run as fllws: $ORACLE_HOME/racle_cmmn/cmmn/bin/wlst.sh (On Linux) $ORACLE_HOME\racle_cmmn\cmmn\bin\wlst.cmd (On Windws) And then subsequently cnnect t OHS dmain : cnnect( <weblgic-admin-username>, <weblgic-admin-passwrd>, <hst:prt> ) Fr example, cnnect( weblgic, welcme1, adc :7001 ) T successfully manage OHS server instances, users will need t cnnect t either WebLgic Nde Manager (in the case f OHS Standalne dmain) r t WebLgic Administratin Server (in the case f OHS WebLgic Server dmain). This shuld be the first step in any f the belw WLST cmmands. Creating OHS 12c Instance Users can leverage WLST t perfrm this task nly when OHS is prvisined in WebLgic Server Dmain. Within WLST interface, users will need t run the belw cmmand t create a new OHS instance: createohsinstance(instancename= hs1, machine= new_machine_1, listenprt= 7777, sslprt= 4443, adminprt= 9999 ) r createohsinstance(instancename= <hs-instance-name>,machine= <cnfigured-machine-name> ) -> where this cmmand will make the best effrt t cnfigure the OHS instance with the default HTTP, HTTPS and Admin prt (thugh nt guaranteed). Fr example: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') 19

20 wls:/hs_dmain> createohsinstance(instancename= hs1,machine= new_machine_1 ) -> where hs1 is the apprpriate <hs-instance-name> and new_machine_1 is the apprpriate name used within the Machines during WLS cnfiguratin wizard. Here, in this abve cmmand, instancename and machine are the required ptins and the rest are ptinal. If the ther ptins like listenprt, sslprt r adminprt is nt prvided, then the createohsinstance will make a best effrt t create the OHS instance using the default prts fr these. If in case, users d nt remember the machine infrmatin that yu used during the WebLgic cnfiguratin wizard, then they can find machine name infrmatin used within the OHS Dmain cnfiguratin as fllws: Lk fr <machine> element within the <OHS_INSTANCE_HOME>/cnfig/cnfig.xml OR Within WLST, run the fllwing: cnnect() ServerCnfig() cd( Machines ) ls() Nte: This cmmand des prvide basic errr checking f instance name, machine name and the prt infrmatin. This cmmand will als create OHS cnfiguratins under - <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/hs1 -> this acts as a cnfiguratin repsitry fr WLS Admin Server running n this dmain. This cnfiguratin repsitry is used t replicate the OHS cnfiguratin n mre than ne machine (clustered deplyment). <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/instances/hs1 -> this is where WLS Nde Manager manages the cnfiguratin n the current machine and is typically created n every machine in a clustered deplyment. The OHS HTTPd server prcess als uses this cnfig directry. Nte: If the WLS Nde Manager is unavailable, then the create peratin will cmplete nly partially. Accrdingly, nly the files under <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/hs1 will be created. When the WLS Nde Manager cmes back up nline again, then the rest f the files under <OHS_INSTANCE_HOME>/cnfig/fmwcnfig/cmpnents/OHS/instances/hs1 will be created apprpriately. 20

21 Deleting OHS 12c Instance Users can leverage WLST t perfrm this task nly when OHS is prvisined in WebLgic Server Dmain. T delete the OHS instance, users will need t run the belw cmmand within the WLST: deleteohsinstance(instancename= <hs-instance-name> ) Fr example: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> deleteohsinstance(instancename= hs1 ) -> where hs1 is apprpriate <hs-instance-name> Nte: This cmmand requires WLS Nde Manager t be running and OHS applicatin t be already stpped. Starting OHS 12c Instance Users can leverage WLST t perfrm this task when OHS is prvisined in WebLgic Server Dmain as well as in Standalne dmain. Users can als simply use the startcmpnent.sh (On Linux) and startcmpnent.cmd (On Windws) cmmands t start the OHS instance frm the cmmand line. Fr mre infrmatin, please refer t sectin - OHS 12c WLST Administratin Interface. T start a give the OHS instance thrugh WLST, users will need t run the belw cmmand within the WLST: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> start( hs1 ) -> where start( <hs-instance-name> ) 21

22 Als, users can run the state(hs1) cmmand within the WLST t retrieve the current status f OHS applicatin. Once OHS instance started successfully, OHS lg files fr the instance will be available at <OHS_INSTANCE_HOME>/servers/hs1/lgs. OHS Audit lgs are at <OHS_INSTANCE_HOME>/auditlgs/OHS/hs1 OHS instance state infrmatin will be lgged by Nde Manager at <OHS_INSTANCE_HOME>/system_cmpnents/OHS/hs1/ Here hs1 is the name f OHS instance used while creating this OHS instance. Nw, users shuld be able t access this OHS instance thrugh the brwser by accessing r Nte: If the WLS Nde Manager fr OHS Dmain is nt available, then this OHS instance cannt be started until the Nde Manager cmes nline again. Stpping OHS 12c Instance Users can leverage WLST t perfrm this task when OHS is prvisined in WebLgic Server Dmain as well as Standalne dmain. Users can simply use the startcmpnent.sh (On Linux) and startcmpnent.cmd (On Windws) cmmands t start the OHS instance frm the cmmand line. Fr mre infrmatin, please refer t prduct dcumentatin Stpping OHS Instances. T stp a give OHS instance within WLST, users will need t run the fllwing cmmand within WLST: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> shutdwn( hs1 ) -> where shutdwn( <hs-instance-name> ) WARNING: Invking shutdwn() withut any parameter shuts dwn WLS Admin Server within OHS Dmain and als quits WLST shell. Hwever, this des NOT shut dwn the OHS httpd prcess. Nte: If the WLS Nde Manager fr OHS Dmain is nt available, then this OHS instance cannt be started until the Nde Manager cmes nline again. 22

23 Sft Restart f OHS 12c Instance Users can leverage WLST t perfrm this task when OHS is prvisined in WebLgic Server Dmain as well as Standalne dmain. T perfrm a sft bunce f OHS instance, users will need t run the fllwing cmmand within WLST: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> sftrestart( hs1 ) -> where sftrestart( <hs-instance-name> ) Nte: If the WLS Nde Manager fr OHS Dmain is nt available, then this OHS instance cannt be started until the Nde Manager cmes nline again. Retrieve OHS 12c Instance Status Users can leverage WLST t perfrm this task when OHS is prvisined in WebLgic Server Dmain as well as Standalne dmain. T get the status f the OHS instance, users will need t run the belw cmmand within the WLST: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> state( hs1 ) -> where state( <hs-instance-name> ) If the HTTPd prcess is running, then the abve cmmand will reprt as RUNNING. Retrieve OHS 12c Mnitring Statistics Users can leverage WLST t perfrm this task when OHS is prvisined in WebLgic Server Dmain as well as Standalne dmain. T retrieve the perfrmance mnitring statistics, administratrs can leverage the WLST as fllws: 23

24 On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/base_dmain/servercnfig> displaymetrictables('hs_*') Accessing the OHS cnfiguratin prperties Users can leverage WLST t perfrm this task with OHS prvisined in WebLgic Server Dmain nly. T retrieve the list f editable prperties within the OHS cnfiguratin, users can leverage WLST cmmand and run the fllwing cmmands: On Linux: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.sh On Windws: <ORACLE_HOME>/racle_cmmn/cmmn/bin/wlst.cmd wls:/ffline> cnnect( weblgic, welcme1, <hst>:7001 ) -> where cnnect('<user-name>', '<passwrd>', '<hst>:<prt>') wls:/hs_dmain/servercnfig> editcustm() wls:/hs_dmain/servercnfig> cd( racle.hs ) wls:/hs_dmain/servercnfig> cd( racle.hs:type=ohsinstance,name=hs1 ) wls:/hs_dmain/servercnfig> ls() Appendix Installing WebLgic JRF 12cR1 T manage OHS 12c thrugh WebLgic Management Framewrk, users will need t install JRF enabled WebLgic and OHS in the same installatin lcatin (say Oracle Middleware Hme). This sectin will walk thrugh the steps invlved in installing JRF enabled WebLgic 12.1.x Yu can dwnlad JRF enabled WebLgic frm here. 24

25 Users are advised t set JDK/JRE7 in their JAVA_HOME envirnment and begin installing WLS by running the fllwing cmmand: $JAVA_HOME/bin/java jar wls_jrf_generic.jar Chse the apprpriate ptins t specify the inventry directry. The default ptin will wrk fine as well. In the Next screen, select Skip Sftware Updates and prceed t finish the pre-requisite checks. In the Oracle Hme installatin lcatin, chse a new installatin lcatin that will hst bth WebLgic server and OHS server(s) and click n Next. Users can safely chse t nt get the security updates and allw the installer t start laying ut the binaries Fr mre infrmatin, refer t prduct dcumentatin - Installing WebLgic Installing Oracle HTTP Server 12cR1 (12.1.x) (Cllcated) This sectin will walk thrugh the steps invlved in installing Oracle HTTP Server (OHS) 12cR1 in a cllcated (same installatin lcatin) with JRF enabled WebLgic. Users will need t cmplete WebLgic JRF enabled (Fusin Middleware Infrastructure) in a specific Oracle Hme as captured in sectin - Installing WebLgic JRF 12cR1 Users can dwnlad Oracle HTTP Server 12cR1 either frm E-Delivery (recmmended fr prductin) r frm Oracle Technlgy Netwrk (fr evaluatin and develpment) and install in the same Oracle Hme where yu installed WebLgic JRF (Fusin Middleware Infrastructure). Users can install OHS by running the fllwing cmmand: hs_linux64.bin (frm a terminal n Linux 64-bit) setup_hs_win64.exe (frm a cmmand line windw n Windws 64-bit) Chse the default ptins fr the inventry directry. In the Next screen, select Skip Sftware Updates and prceed t finish the pre-requisite checks. In the Next screen, chse fr the OHS managed thrugh a pre-installed WebLgic server ptin. 25

26 Figure - Installing OHS Cllcated In the Oracle Hme installatin lcatin, chse the same installatin lcatin that was used t install WebLgic earlier and click n Next. Nw, yu can safely chse t nt get the security updates and allw the installer t start laying ut the binaries. This installatin lcatin will here frth be simply referred as the ORACLE_MIDDLEWARE_HOME. Fr mre infrmatin, please refer t prduct dcumentatin Installing Oracle HTTP Server 12cR1 Installing Oracle HTTP Server 12cR1 (12.1.x) (Standalne) This sectin will walk thrugh the steps invlved in installing Oracle HTTP Server (OHS) in a standalne scenari. Users can dwnlad Oracle HTTP Server 12cR1 either frm E-Delivery (recmmended fr prductin) r frm Oracle Technlgy Netwrk (fr evaluatin and develpment) Users can install OHS by running the fllwing cmmand: hs_linux64.bin (frm a terminal n Linux 64-bit) setup_hs_win64.exe (frm a cmmand line windw n Windws 64-bit) Chse the default ptins fr the inventry directry. In the Next screen, select Skip Sftware Updates and prceed t finish the pre-requisite checks. In the Next screen, chse fr the OHS standalne ptin. Fr mre infrmatin, please refer t prduct dcumentatin Installing Oracle HTTP Server 12cR1 26

27 Cnclusin Oracle HTTP Server 12cR x - is based n the ppular Apache HTTP Server infrastructure and can reliably serve the Web Tier respnsibilities by reliably and securely frnt-ending the HTTP(s) traffic t the applicatins hsted within the Fusin Middleware. The fllwing capabilities distinguish Oracle HTTP Server frm the rest f the nn-oracle Web Tier fferings: Integrated management and mnitring capabilities cnsistent with the rest f the Fusin Middleware Applicatins. Multiple prvisining mdels WebLgic Server Dmain fr integrated administratin and Standalne Dmain fr lean and simplified prvisining with remte management capability. Ability t administer a farm f Oracle HTTP Server running n multiple machines thrugh the WebLgic Dmain These capabilities allw Oracle HTTP Server t serve the static cntent and reverse prxy the HTTP(s) requests t the WebLgic Managed Server(s)/Cluster(s). In additin, custmers can als administer the Web Tier and the Applicatin Tier within the WebLgic dmain thereby simplifying the cmmn administratin tasks like prvisining and server lifecycle administratin. 27

28 White Paper Title July 2013 Authr: Sriram Natarajan Cntributing Authrs: Frances Zha Oracle Crpratin Wrld Headquarters 500 Oracle Parkway Redwd Shres, CA U.S.A. Wrldwide Inquiries: Phne: Fax: racle.cm Cpyright 2013, Oracle and/r its affiliates. All rights reserved. This dcument is prvided fr infrmatin purpses nly, and the cntents heref are subject t change withut ntice. This dcument is nt warranted t be errr-free, nr subject t any ther warranties r cnditins, whether expressed rally r implied in law, including implied warranties and cnditins f merchantability r fitness fr a particular purpse. We specifically disclaim any liability with respect t this dcument, and n cntractual bligatins are frmed either directly r indirectly by this dcument. This dcument may nt be reprduced r transmitted in any frm r by any means, electrnic r mechanical, fr any purpse, withut ur prir written permissin. Oracle and Java are registered trademarks f Oracle and/r its affiliates. Other names may be trademarks f their respective wners. Intel and Intel Xen are trademarks r registered trademarks f Intel Crpratin. All SPARC trademarks are used under license and are trademarks r registered trademarks f SPARC Internatinal, Inc. AMD, Optern, the AMD lg, and the AMD Optern lg are trademarks r registered trademarks f Advanced Micr Devices. UNIX is a registered trademark f The Open Grup. 0113