Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
11g Release 1 (11.1.1)

Part Number E15722-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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.

Important:

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.

Note:

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 the following steps to configure the Oracle Web tier:

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

    WEBHOSTn> cd ORACLE_BASE/product/fmw/Oracle_WT1/bin
    
  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 the 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 that you want to use in a file.

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

    [OHS]
    #Listen port for OHS component
    OHS Port = 7777
    
    [OPMN]
    #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, specify 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 that they are correct. If they are not, then 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 the process completes, click Next, and the Installation Complete screen is displayed.

  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:

http://webhost1.mycompany.com:7777/

http://webhost2.mycompany.com:7777/

7.4 Configuring the Load Balancer to Route HTTP Requests

Configure the load balancer to route all HTTP requests to the hosts that are 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 requests are routed directly from the load balancer to Oracle WebLogic Server, which is not the case in the topology described in this guide. Also, set monitors for HTTP.

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

7.5 Defining Virtual Hosts

The reference topology in this guide requires that you define a set of virtual hosts for the Oracle HTTP Server. For each virtual host, you later define a set of specific URLs that route requests to the proper Administration Server or Managed Server in the WebLogic Server domain.

This section contains the following topics:

7.5.1 Defining the IP Address and Port in the httpd.conf File

You define name-based virtual servers. That means you must define the IP address and port to be used for each virtual host that you define. You define the IP address and port once, in the httpd.conf file, then you can define the actual virtual host names (and their specific URLs) in the virtual host-specific .conf files.

You can find the httpd.conf file in the following directory:

ORACLE_INSTANCE/config/OHS/ohsn

To define the IP address and port, add the following entry in the httpd.conf file for both Oracle HTTP Servers:

NameVirtualHost *:7777

Note that the value for the NameVirtualHost parameter depends on how the virtual host for the load balancer was configured. You might need to use a different value than the one shown, such as 80.

7.5.2 Creating .conf Files to Define <VirtualHost> Directives

Define each virtual host in its own .conf file. This definition makes it easy to manage the URLs for each virtual host that you define.

Create the following new files to define the <VirtualHost> directives:

  • bi_vh.conf

  • biinternal_vh.conf

  • admin_vh.conf

Create the new files in the following directory:

ORACLE_BASE/admin/instance_name/config/OHS/component_name/moduleconf

Note:

ensure that you perform the following steps for both WEBHOST1 and WEBHOST2.

Perform the following steps to define each virtual host in its own .conf file:

  1. Create the bi_vh.conf file and add the following directive:

    <VirtualHost *:7777>
       ServerName https://bi.mycompany.com:443
       ServerAdmin you@your.address
       RewriteEngine On
       RewriteOptions inherit
    </VirtualHost>
    
  2. Create the biinternal_vh.conf file and add the following directive:

    <VirtualHost *:7777>
       ServerName biinternal.mycompany.com:80
       ServerAdmin you@your.address
       RewriteEngine On
       RewriteOptions inherit
    </VirtualHost>
    
  3. Create the admin_vh.conf file and add the following directive:

    <VirtualHost *:7777>
       ServerName admin.mycompany.com:80
       ServerAdmin you@your.address
       RewriteEngine On
       RewriteOptions inherit
       RewriteRule ^/console/jsp/common/logout.jsp "/oamsso/logout.html?end_url=/console" [R]
    </VirtualHost>
    

    If the steps in Chapter 12, "Integrating an Enterprise Deployment with Oracle Identity Management" have not been completed, then comment out the RewriteRule lines until the integration has been completed.

  4. 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 the load balancer and Oracle HTTP Server are configured properly:

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

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

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

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