4 Configuring the Web Tier

This chapter describes how to configure the Oracle Web Tier to support the Oracle Fusion Middleware SOA Suite implementation.

This chapter contains the following sections:

4.1 Configuring the Oracle Web Tier

Prior to configuration, the Oracle web tier software must be installed on WEBHOST1 and WEBHOST2, as described in Section 3.2, "Installing Oracle HTTP Server." The steps for configuring the Oracle web tier are the same for both WEBHOST1 and WEBHOST2.

Perform these steps to configure the Oracle web tier:

  1. Change the directory to the location of the Oracle Fusion Middleware Configuration Wizard:

  2. Start the Configuration Wizard:

    WEBHOST1> ./config.sh
  3. In the Welcome screen, click Next.

  4. In the Configure Components screen, select Oracle HTTP Server and unselect Associate Selected Components with WebLogic Domain. Make sure that Oracle Web Cache is not selected.

    Click Next.

  5. In the Specify Component Details screen, specify the following values:

    • Instance Home Location: /u01/app/oracle/admin/webn

    • AS Instance Name: webn

    • OHS Component Name: ohsn

    (where n is a sequential number for your installation; for example, 1 for WEBHOST1, 2 for WEBHOST2, and so on.)

    Click Next.

  6. In high-availability implementations, whilst not mandatory, it makes life simpler if all of the ports used by the various components are synchronized across hosts. Oracle allows automatic port configuration to be bypassed by specifying ports to be used in a file.

    In the Configure Ports screen, select a file name and then click View/Edit. The file will look like this:

    #Listen port for OHS component
    OHS Port = 7777
    #Process Manager Local port no
    OPMN Local Port = 1880

    You can find a sample staticports.ini file on installation disk 1 in the stage/Response directory.

    Click Next.

  7. In the Specify Security Updates screen, choose whether you want to receive security updates from Oracle support and if you do, enter your e-mail address.

  8. In the Installation Summary screen, review the selections to ensure they are correct. If they are not, click Back to modify selections on previous screens. When you are ready, click Install.

  9. Multiple configuration assistants are launched in succession; this process can be lengthy. When it completes, click Next, and the Installation Complete screen appears.

  10. In the Installation Completed screen, click Finish to exit.

4.2 Validating the Installation

Once the installation is completed, check that it is possible to access the Oracle HTTP Server home page using the following URL:


4.3 Associating the Oracle Web Tier with the Oracle WebLogic Domain

Once an Oracle WebLogic domain has been created, the Oracle web tier can be linked to the domain. The advantages of doing this are that the Oracle web tier can be managed and monitored via the Oracle Fusion Middleware console.

To associate the Oracle web tier with the WebLogic domain, execute the following commands on both WEBHOST1 and WEBHOST2:

WEBHOSTn> cd ORACLE_BASE/admin/instance_name/bin
WEBHOSTn> ./opmnctl registerinstance -adminHost ADMINVHN  -adminPort 7001 -adminUsername weblogic

4.4 Configuring Oracle HTTP Server with the Load Balancer

Configure your load balancer to route all HTTP requests to the hosts running Oracle HTTP Server (WEBHOST1, WEBHOST2). You do not need to enable sticky sessions (insert cookie) on the load balancer when Oracle HTTP Server is front-ending Oracle WebLogic Server. You need sticky sessions if you are going directly from the load balancer to Oracle WebLogic Server, which is not the case in the topology described in this guide. Also, you should set monitors for HTTP.

4.5 Configuring Virtual Hosts

In order for Oracle Enterprise Content Management Suite to work with the load balancer, a virtual host needs to be created in the Oracle HTTP Server configuration. Edit the httpd.conf file located at ORACLE_INSTANCE/config/OHS/component_name and add the following to the virtual host section:

NameVirtualHost *:7777
<VirtualHost *:7777>
   ServerName https://ecm.mycompany.com:443
   RewriteEngine On
   RewriteOptions inherit
   UseCanonicalName On


Do do this both for WEBHOST1 and WEBHOST2.