When you configure the web tier, you have the option of using Oracle HTTP Server or Oracle Traffic Director. If you choose to use Oracle HTTP Server, then you must install Oracle HTTP Server on each of the web tier hosts and configure Oracle HTTP standalone domains on each host.
The Oracle HTTP Server instances on the web tier direct HTTP requests from the hardware load balancer to specific Managed Servers in the application tier.
Before you configure Oracle HTTP Server, be sure to review Understanding the Web Tier.
Note:
If you plan to configure Oracle Managed File Transfer, then you must configure Oracle Traffic Director to route FTP and SFTP requests over TCP.
Parent topic: Configuring the Enterprise Deployment
As you perform the tasks in this chapter, you reference the directory variables that are listed in this topic.
The values for several directory variables are defined in File System and Directory Variables Used in This Guide.
WEB_ORACLE_HOME
WEB_DOMAIN_HOME
JAVA _HOME
In addition, you reference the following virtual IP (VIP) address and host names:
ADMINVHN
WEBHOST1
WEBHOST2
In an enterprise deployment, each Oracle HTTP Server instance is configured on a separate host and in its own standalone domain. This allows for a simple configuration that requires a minimum amount of configuration and a minimum amount of resources to run and maintain.
Note:
Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system and JAVA_HOME is set on the web tier hosts.
For more information about the role and configuration of the Oracle HTTP Server instances in the web tier, see Understanding the Web Tier.
Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system.
To find a certified JDK, see the certification document for your release on the Oracle Fusion Middleware Supported System Configurations page.
After you identify the Oracle JDK for the current Oracle Fusion Middleware release, you can download an Oracle JDK from the following location on Oracle Technology Network:
http://www.oracle.com/technetwork/java/index.html
Be sure to navigate to the download for the Java SE JDK.
Parent topic: Installing a Supported JDK
Oracle Fusion Middleware requires you to install a certified Java Development Kit (JDK) on your system.
You must install the JDK in the following locations:
On the local storage device for each of the Web tier host computers. The Web tier host computers, which reside in the DMZ, do not necessarily have access to the shared storage on the application tier.
Parent topic: Installing a Supported JDK
It is important to understand the procedure for installing the Oracle HTTP Server software on the web tier.
To start the installation program, perform the following steps.
Parent topic: Installing Oracle HTTP Server on WEBHOST1
The following table lists the screens in the order that the installation program displays them.
If you need additional help with any of the installation screens, click the screen name.
Table 11-1 Oracle HTTP Server Installation Screens
Screen | Description |
---|---|
On UNIX operating systems, this screen appears if you install any Oracle product on this host for the first time. Specify the location where you want to create your central inventory. Ensure that the operating system group name selected on this screen has write permissions to the central inventory location. See Understanding the Oracle Central Inventory in Installing Software with the Oracle Universal Installer. Note: Oracle recommends that you configure the central inventory directory within the products directory. Example: You may also need to execute the |
|
This screen introduces you to the product installer. |
|
Use this screen to automatically search My Oracle Support for available patches or automatically search the local directory for patches that you have already downloaded for your organization. |
|
Use this screen to specify the location of your Oracle home directory. For the purposes of an enterprise deployment, enter the value of the WEB_ORACLE_HOME variable listed in Table 7-3. |
|
Select Standalone HTTP Server (Managed independently of WebLogic server). This installation type allows you to configure the Oracle HTTP Server instances independently from any other existing Oracle WebLogic Server domains. |
|
For the value of JDK Home, enter the value of JAVA_HOME that you set when installing the JDK software. |
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, verify that your host computers and the required software meet the system requirements and certification information described in Host Computer Hardware Requirements and Operating System Requirements for the Enterprise Deployment Topology. |
|
Use this screen to verify the installation options that you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation. See Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer. |
|
This screen allows you to see the progress of the installation. |
|
This screen appears when the installation is complete. Review the information on this screen, then click Finish to close the installer. |
Parent topic: Installing Oracle HTTP Server on WEBHOST1
Verify that the Oracle HTTP Server installation completed successfully by validating the WEB_ORACLE_HOME
folder contents.
Run the following command to compare the installed folder structure with the following list:
ls --format=single-column WEB_ORACLE_HOME
The following files and directories are listed in theOracle HTTP Server Oracle Home:
bin cdata cfgtoollogs crs css cv has install inventory jlib ldap lib network nls ohs OPatch oracle_common oracore oraInst.loc oui perl plsql plugins precomp QOpatch racg rdbms slax sqlplus srvm webgate wlserver xdk
Parent topic: Installing Oracle HTTP Server on WEBHOST1
The following topics describe how to create a new Oracle HTTP Server standalone domain on the first web tier host.
To start the Configuration Wizard, navigate to the following directory and start the WebLogic Server Configuration Wizard, as follows:
cd WEB_ORACLE_HOME/oracle_common/common/bin
./config.sh
Parent topic: Creating an Oracle HTTP Server Domain on WEBHOST1
Oracle recommends that you create a standalone domain for the Oracle HTTP Server instances on each web tier host.
The following topics describe how to create a new standalone Oracle HTTP Server domain:
Task 1, "Selecting the Domain Type and Domain Home Location"
Task 7, "Reviewing Your Configuration Specifications and Configuring the Domain"
On the Configuration Type screen, select Create a new domain.
In the Domain Location field, enter the value assigned to the WEB_DOMAIN_HOME variable.
Note the following:
The Configuration Wizard creates the new directory that you specify here.
Create the directory on local storage, so the web servers do not have any dependencies on storage devices outside the DMZ.
Note:
More information about the Domain home directory can be found in About the Domain Home Directory in Planning an Installation of Oracle Fusion Middleware.
More information about the other options on this screen can be found in Configuration Type in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
For more information about the web tier and the DMZ, see Understanding the Firewalls and Zones of a Typical Enterprise Deployment.
For more information about the WEB_DOMAIN_HOME directory variable, see File System and Directory Variables Used in This Guide.
On the Templates screen, select Oracle HTTP Server (Standalone) - 12.2.1.3.0 [ohs].
Tip:
More information about the options on this screen can be found in Templates in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Select the Oracle HotSpot JDK installed in the /u02/oracle/products/jdk
directory prior to the Oracle HTTP Server installation.
On the System Components screen, configure one Oracle HTTP Server instance. The screen should, by default, have a single instance defined. This is the only instance that you need to create.
The default instance name in the System Component field is ohs1
. Use this default name when you configure WEBHOST1
.
Make sure that OHS
is selected in the Component Type field.
If an application is not responding, use the Restart Interval Seconds field to specify the number of seconds to wait before you attempt a restart if an application is not responding.
Use the Restart Delay Seconds field to specify the number of seconds to wait between restart attempts.
Use the OHS Server screen to configure the OHS servers in your domain:
Select ohs1 from the System Component drop-down menu.
In the Listen Address field, enter WEBHOST1
.
All the remaining fields are prepopulated, but you can change the values as required for your organization. See OHS Server in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
In the Server Name field, verify the value of the listen address and listen port.
It should appear as follows:
http://WEBHOST1:7777
Select Per Domain Default Location as the Node Manager type, and specify the user name and password for the Node Manager.
Note:
For more information about the options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.
For information about Node Manager configuration, see Configuring Node Manager on Multiple Machines in Administering Node Manager for Oracle WebLogic Server.
The Configuration Summary screen contains detailed configuration information for the domain that you are about to create. Review the details of each item on the screen and verify that the information is correct.
If you need to make any changes, you can go back to any previous screen either by using the Back button or by selecting the screen in the navigation pane.
Domain creation does not begin until you click Create.
In the Configuration Progress screen, click Next when it finishes.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen shows the domain home location.
Make a note of the information provided here, as you need it to start the servers and access the Administration Server.
Click Finish to close the Configuration Wizard.
Parent topic: Creating an Oracle HTTP Server Domain on WEBHOST1
After you install Oracle HTTP Server and configure a domain on WEBHOST1, then you must also perform the same tasks on WEBHOST2.
Log in to WEBHOST2 and install Oracle HTTP Server by using the instructions in Installing Oracle HTTP Server on WEBHOST1.
Configure a new standalone domain on WEBHOST2 by using the instructions in Creating a Web Tier Domain on WEBHOST1.
Use the name ohs2
for the instance on WEBHOST2, and be sure to replace all occurrences of WEBHOST1 with WEBHOST2 and all occurrences of ohs1
with ohs2
in each of the examples.
It is important to understand how to start the Oracle HTTP Server instances on WEBHOST1 and WEBHOST2.
Before you can start the Oracle HTTP Server instances, you must start the Node Manager on WEBHOST1 and WEBHOST2:
See Advanced Node Manager Configuration in Administering Node Manager for Oracle WebLogic Server.
It is important to understand how to update the Oracle HTTP Server configuration files so that the web server instances route requests to the servers in the domain.
The following topics provide overview information about the changes that are required to the Oracle HTTP Server configuration files in an enterprise deployment.
The reference topologies in this guide require that you define a set of virtual servers on the hardware load balancer. You can then configure Oracle HTTP Server to recognize requests to specific virtual hosts (that map to the load balancer virtual servers) by adding <VirtualHost>
directives to the Oracle HTTP Server instance configuration files.
For each Oracle HTTP Server virtual host, you define a set of specific URLs (or context strings) that route requests from the load balancer through the Oracle HTTP Server instances to the appropriate Administration Server or Managed Server in the Oracle WebLogic Server domain.
Rather than adding multiple virtual host definitions to the httpd.conf
file, Oracle recommends that you create separate, smaller, and more specific configuration files for each of the virtual servers required for the products that you are deploying. This avoids populating an already large httpd.conf
file with additional content, and it can make troubleshooting configuration problems easier.
For example, in a typical Oracle Fusion Middleware Infrastructure domain, you can add a specific configuration file called admin_vh.conf
that contains the virtual host definition for the Administration Server virtual host (ADMINVHN).
Perform the following tasks to prepare the httpd.conf
file for the additional virtual hosts required for an enterprise topology:
Log in to WEBHOST1.
Locate the httpd.conf
file for the first Oracle HTTP Server instance (ohs1
) in the domain directory:
cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/
Verify if the httpd.conf
file has the appropriate configuration as follows:
Run the following command to verify the ServerName
parameter, be sure that it is set correctly, substituting the correct value for the current WEBHOSTn:
grep "ServerName http" httpd.conf ServerName http://WEBHOST1:7777
Run the following command to verify there is an include statement that includes all *.conf
files from the moduleconf subdirectory:
grep moduleconf httpd.conf IncludeOptional "moduleconf/*.conf"
If either validation fails to return results, or returns results that are commented out, open the httpd.conf
file in a text editor and make the required changes in the appropriate locations.
# # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # ServerName http://WEBHOST1:7777 # and at the end of the file: # Include the admin virtual host (Proxy Virtual Host) related configuration include "admin.conf" IncludeOptional "moduleconf/*.conf"
Save the httpd.conf
file.
Log in to WEBHOST2
and perform steps 2 and 3 for the httpd.conf
file, replacing any occurrences of WEBHOST1
or ohs1
with WEBHOST2
or ohs2
in the instructions as necessary.
Note:
Do not update the host entries in the virtual host configuration files mentioned in this topic if you have not planned to scale out the BI deployment to that host. For example, if you do not plan to extend the BI domain to HOST2 (BIHOST2 for WSM setup), do not specify "BIHOST2" in the directives while creating the virtual host configuration files.Note:
Before you create the virtual host configuration files, be sure you have configured the virtual servers on the load balancer, as described in Purpose of the Oracle HTTP Server Virtual Hosts.To create the virtual host configuration files:
Before you can validate that requests are routed correctly through the Oracle HTTP Server instances, you must set the WebLogic Plug-In Enabled
parameter. It is recommended to set the WebLogic Plug-In Enabled
parameter at the domain level. Any clusters or servers not using the plugin via the web-tier can have their WebLogic Plug-In Enabled
parameter value set to no
on an exception basis as needed.
From the load balancer, access the following URLs to ensure that your load balancer and Oracle HTTP Server are configured properly. These URLs should show the initial Oracle HTTP Server 12c web page.
http://admin.example.com/index.html
http://
biinternal.example.com
/index.html
https://
bi.example.com
/index.html
To verify the changes that you have made in this chapter:
Use the following URL to the hardware load balancer to display the Oracle WebLogic Server Administration Console, and log in by using the Oracle WebLogic Server administrator credentials:
http://admin.example.com/console
This validates that the admin.example.com
virtual host on the load balancer is able to route requests to the Oracle HTTP Server instances on the web tier, which in turn can route requests for the Oracle WebLogic Server Administration Console to the Administration Server in the application tier.
Similarly, you should be able to access the Fusion Middleware Control by using a similar URL:
http://admin.example.com/em
After you configure the Oracle HTTP Server instances, you can validate your work by accessing key Oracle Business Intelligence URLs. If these URLs display the proper content, then you can be assured the Web tier components are configured correctly.
To validate HTTP access to the Oracle Business Intelligence components, enter each of the following URLs in your Web browser and make sure the proper content displays:
https://bi.example.com/analytics
https://bi.example.com/mapviewer
https://bi.example.com/xmlpserver
http://biinternal.example.com/wsm-pm
http://bi.example.com/bicomposer
http://bi.example.com/aps/Essbase
http://bi.example.com/aps/SmartView
It is an Oracle best practices recommendation to create a backup after you successfully configure a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process. See Performing Backups and Recoveries for an Enterprise Deployment.