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 Oracle Fusion Middleware Release Notes for any additional installation and deployment considerations before starting the setup process.
This chapter contains the following topics:
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:
Change the directory to the location of the Oracle Fusion Middleware Configuration Wizard:
WEBHOSTn> cd ORACLE_HOME/bin
Start the Configuration Wizard:
In the Welcome screen, click Next.
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.
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.)
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:
[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.
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.
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.
Multiple configuration assistants are launched in succession; this process can be lengthy. When it completes, click Next, and the Installation Complete screen appears.
In the Installation Complete screen, click Finish to exit.
After the installation is complete, check that it is possible to access the Oracle HTTP Server home page using the following URLs:
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.
For Oracle Business Intelligence to work with the load balancer, a virtual host must 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 virtual host sections:
NameVirtualHost *:7777 <VirtualHost *:7777> ServerName https://bi.mycompany.com:443 RewriteEngine On RewriteOptions inherit </VirtualHost> NameVirtualHost *:7777 <VirtualHost *:7777> ServerName admin.mycompany.com:80 ServerAdmin email@example.com RewriteEngine On RewriteOptions inherit </VirtualHost> NameVirtualHost *:7777 <VirtualHost *:7777> ServerName biinternal.mycompany.com:80 ServerAdmin firstname.lastname@example.org RewriteEngine On RewriteOptions inherit </VirtualHost>
Note:Perform this step for both WEBHOST1 and WEBHOST2.
After modifying the httpd.conf file, you must restart both Oracle HTTP Servers, as follows:
WEBHOST> cd ORACLE_BASE/admin/instance_name/bin WEBHOST> opmnctl stopall WEBHOST> opmnctl startall
Access the following URLs to ensure that your load balancer and Oracle HTTP Server are configured properly: