7 Configuring the Web Tier for an Enterprise Deployment

This chapter describes how to configure the Oracle Web tier to support the Oracle Business Intelligence enterprise deployment.


Oracle strongly recommends that you read the Oracle Fusion Middleware Release Notes for any additional installation and deployment considerations before starting the setup process.

This chapter contains the following topics:

7.1 Overview of Configuring the Web Tier

This chapter describes how to associate the Oracle Web Tier with the WebLogic Server domain. Once the Web tier is associated with the WebLogic Server, you can monitor it using Oracle Enterprise Manager Fusion Middleware Control.

You then configure the load balancer to route all HTTP requests to WEBHOST1 and WEBHOST2.

The last section describes how to define the directives of the <VirtualHost> section of the httpd.conf file on both OHS servers. You created these virtual host names when you configured the load balancer in Section 3.3, "Configuring the Load Balancer."

7.2 Running the Configuration Wizard to Configure Oracle HTTP Server

The steps for configuring the Oracle Web tier are the same for both WEBHOST1 and WEBHOST2.


Before configuring the Oracle Web Tier software, you must install it on WEBHOST1 and WEBHOST2, as described in Section 6.2, "Installing Oracle HTTP Server."

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:

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

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

    Click Next.

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

    • Instance Home Location: ORACLE_BASE/admin/webn

    • 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.

    Note: Oracle HTTP Server instance names on WEBHOST1 and WEBHOST2 must be different.

  6. In high-availability implementations, although it is not mandatory, it is simpler if all ports used by the various components are synchronized across hosts. You can bypass automatic port configuration by specifying the ports you want to use in a file.

    In the Configure Ports screen, select a file name and then click View/Edit. The file looks similar to the following:

    #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 in the /Disk1/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 Configure.

  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 Complete screen, click Finish to exit.

7.3 Validating the Configuration

After the configuration is complete, check that it is possible to access the Oracle HTTP Server home page using the following URLs:



7.4 Configuring the Load Balancer to Route HTTP Requests

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.

The instructions for this configuration will vary depending on which load balancer you use. See your load balancer documentation for specific instructions.

7.5 Configuring Virtual Hosts

To configure the virtual hosts, complete the tasks described in the following sections:

7.5.1 Editing the httpd.conf File

For Oracle Business Intelligence to work with the load balancer, a virtual host must be created in the Oracle HTTP Server configuration. Define the directives of the <VirtualHost> section of the httpd.conf file on both Oracle HTTP Servers. This file is located in the following directory:


Add the following entries to the file:

NameVirtualHost *:7777
<VirtualHost *:7777>
   ServerName https://bi.mycompany.com:443
   ServerAdmin you@your.address
   RewriteEngine On
   RewriteOptions inherit

NameVirtualHost *:7777
<VirtualHost *:7777>
   ServerName admin.mycompany.com:80
   ServerAdmin you@your.address
   RewriteEngine On
   RewriteOptions inherit
NameVirtualHost *:7777
<VirtualHost *:7777>
   ServerName biinternal.mycompany.com:80
   ServerAdmin you@your.address
   RewriteEngine On
   RewriteOptions inherit


Make sure to perform this step for both WEBHOST1 and WEBHOST2.

7.5.2 Restarting Both Oracle HTTP Servers

After modifying the httpd.conf files, you must restart both Oracle HTTP Servers, as follows:

WEBHOSTn> cd ORACLE_BASE/admin/instance_name/bin
WEBHOSTn> opmnctl stopall
WEBHOSTn> opmnctl startall

7.5.3 Validating the Configuration

Access the following URLs to ensure that your load balancer and Oracle HTTP Server are configured properly:

  • http://bi.mycompany.com/index.html

  • http://admin.mycompany.com/index.html

  • http://biinternal.mycompany.com/index.html

If you cannot access these URLs, check to ensure that you completed the procedure in Section 3.3, "Configuring the Load Balancer" correctly.