This chapter provides information on variables used when configuring the web tier and installing and configuring a web tier domain.
As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.
The values for several directory variables are defined in File System and Directory Variables Used in This Guide.
In addition, you'll be referencing the following virtual IP (VIP) address and host names:
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 resouces to run and maintain.
For more information about the role and configuration of the Oracle HTTP Server instances in the web tier, see Understanding the Web Tier.
The following sections describe how to install the Oracle HTTP Server software on the web tier.
To start the installation program, perform the following steps.
When the installation program appears, you are ready to begin the installation.
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.
This screen introduces you to the product installer.
Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve 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 OHS_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.
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.
If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates.
If you do not have an account, or if you are sure you want to skip this step, then clear the check box and verify your selection in the follow-up dialog box.
Use this screen to verify the installation options 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.
For more information about silent or command line installation, 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 dismiss the installer.
To verify that your Oracle HTTP Server installation completed successfully, list files that were installed in the new Oracle home directory. You should see the following directories in the Oracle HTTP Server Oracle home:
bin cfgtoollogs crs css has install inventory jlib ldap lib network nls ohs OPatch oracle_common oracore oraInst.loc oui perl plsql plugins precomp rdbms root.sh slax sqlplus srvm webgate wlserver xdk
The following sections 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 OHS_ORACLE_HOME/oracle_common/common/bin ./config.sh
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:
On the Configuration Type screen, select Create a new domain.
In the Domain Location field, enter the value assigned to the OHS_DOMAIN_HOME variable.
Note the following:
The Configuration Wizard will create the new directory that you specify here.
Create the directory on local storage, so the web servers do not have any dependencies on on storage devices outside the DMZ.
More information about the Domain home directory can be found in "Choosing a Domain Home" in Planning an Installation of Oracle Fusion Middleware.
More information about the other options on this screen can be found in "Configuration Type" in 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 OHS_DOMAIN_HOME directory variable, see File System and Directory Variables Used in This Guide.
On the Templates screen, select Oracle HTTP Server (Standalone) - 126.96.36.199 [ohs].
More information about the options on this screen can be found in "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
On the System Components screen, create one Oracle HTTP Server instance. The screen should by default have a single instance defined.
Note that the default instance name is
ohs1 in the System Component field. You use this default name.
OHS is selected in the Component Type field.
Use the Restart Interval Seconds field to specify the number of seconds to wait before attempting 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
All of the remaining fields are pre-populated, but you can change the values as required for your organization. For more information about the fields on this screen, see "OHS Server" in 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:
Select Per Domain Default Location as the Node Manager type, and specify the Node Manager credentials.
The Configuration Summary screen contains the detailed configuration information for the domain you are about to extend. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Create.
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 will show the updated domain home location.
Make a note of the information provided here, as you will need it to start the servers and access the Administration Server.
Click Finish to dismiss the configuration wizard.
After you install Oracle HTTP Server and configure a Web Tier domain on WEBHOST1, then you must also perform the same tasks on WEBHOST2.
Log in to WEBHOST2 and install Oracle HTTP Server, using the instructions in Installing Oracle HTTP Server on WEBHOST1.
Configure a new standalone domain on WEBHOST2, 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
ohs2 in each of the examples.
The following sections describe 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:
nodemanager.outas an example output file:
nohup OHS_DOMAIN_HOME/bin/startNodeManager.sh > OHS_DOMAIN_HOME/nodemanager/nodemanager.out 2>&1 &
For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
To start the Oracle HTTP Server instances:
For more information about the location of the OHS_DOMAIN_HOME directory, see File System and Directory Variables Used in This Guide.
ohs2instance on WEBHOST2.
For more information, see "Starting Oracle HTTP Server Instances" in Administering Oracle HTTP Server.
The following sections describe how to update the Oracle HTTP Server configuration files so the web server instances route requests to the servers in the domain.
The following topics provide overview information about the changes required to the Oracle HTTP Server configuration 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.
A key parameter of the Oracle HTTP Server
<VirtualHost> directive is the
WebLogicCluster parameter, which is part of the WebLogic Proxy Plug-In for Oracle HTTP Server. When configuring Oracle HTTP Server for an enterprise deployment, consider the following information when adding this parameter to the Oracle HTTP Server configuration files.
The servers specified in the
WebLogicCluster parameter are important only at startup time for the plug-in. The list needs to provide at least one running cluster member for the plug-in to discover other members of the cluster. The listed cluster member must be running when Oracle HTTP Server is started. Oracle WebLogic Server and the plug-in work together to update the server list automatically with new, failed, and recovered cluster members.
Some example scenarios:
Example 1: If you have a two-node cluster and then add a third member, you do not need to update the configuration to add the third member. The third member will be discovered on the fly at runtime.
Example 2: You have a three-node cluster but only two nodes are listed in the configuration. However, if both listed nodes are down when you start Oracle HTTP Server, then the plug-in would fail to route to the cluster. You must ensure that at least one of the listed nodes is running when you start Oracle HTTP Server.
If you list all members of the cluster, then you guarantee you can route to the cluster, assuming at least one member is running when Oracle HTTP Server is started.
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 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.
httpd.conf file for the first Oracle HTTP Server instance (
ohs1) in the domain directory:
httpd.conf file in a text editor and make the following changes:
NameVirtualHost entry as follows immediately below the comment: "# Use name-based virtual hosting" and before the "# VirtualHost example" comment:
In this example, replace WEBHOST1 with the value of the WEBHOST1 variable. For more information, see File System and Directory Variables Used in This Guide.
Verify that there is an
INCLUDE statement in the
httpd.conf that includes all
*.conf files in the
This statement makes it possible to create the separate virtual host files for each component, making it easier to update, maintain, and scale out the virtual host definitions.
Log in to WEBHOST2 and perform steps 2 through 4 to update the
httpd.conf file for the
On WEBHOST2, replace all instances of WEBHOST1 with WEBHOST2 and all instances of
To create 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.
admin_vh.conffile and add the following directive:
<VirtualHost WEBHOST1:7777> ServerName admin.example.com:80 ServerAdmin firstname.lastname@example.org RewriteEngine On RewriteOptions inherit </VirtualHost>
soainternal_vh.conffile and add the following directive:
<VirtualHost WEBHOST1:7777> ServerName soainternal.example.com:80 ServerAdmin email@example.com RewriteEngine On RewriteOptions inherit </VirtualHost>
./stopComponent.sh ohs1 ./startComponent.sh ohs1
admin_vh.conffile and the
soainternal_vh.conffile to the configuration directory for the second Oracle HTTP Server instance (
ohs2) on WEBHOST2:
soainternal_vh.conffiles and change any references from WEBHOST1 to WEBHOST2 in the
./stopComponent.sh ohs2 ./startComponent.sh ohs2
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.
To enable Oracle HTTP Server to route to the Administration Server and the WSM-PM_Cluster, which contain the WLS_WSM managed servers, you must add a set of
<Location> directives and add the
WebLogicCluster parameter to the list of nodes in the cluster.
To set the
admin_vh.conffile within the
# Admin Server and EM <Location /console> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location> <Location /consolehelp> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location> <Location /em> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location>
admin_vh.conf file should appear as it does in admin_vh.conf file.
soainternal_vh.conffile within the
# WSM-PM <Location /wsm-pm> WLSRequest ON WebLogicCluster SOAHOST1:7010,SOAHOST2:7010 WLProxySSL ON WLProxySSLPassThrough ON </Location>
soainternal_vh.conf file should appear as it does in soainternal_vh.conf file.
For more information about the WebLogicCluster parameter in this example, see About the WebLogicCluster Parameter of the <VirtualHost> Directive.
./stopComponent.sh ohs1 ./startComponent.sh ohs1
admin_vh.conffile and the
soainternal_vh.conffile to the configuration directory for the second Oracle HTTP Server instance (ohs2) on WEBHOST2:
soainternal_vh.conffiles and change any references to WEBHOST1 to WEBHOST2 in the
./stopComponent.sh ohs2 ./startComponent.sh ohs2
<VirtualHost WEBHOST1:7777> ServerName admin.example.com:7777 ServerAdmin firstname.lastname@example.org RewriteEngine On RewriteOptions inherit # Admin Server and EM <Location /console> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location> <Location /consolehelp> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location> <Location /em> WLSRequest ON WebLogicHost ADMINVHN WeblogicPort 7001 </Location> </VirtualHost>
Contents of this file:
<VirtualHost WEBHOST1:7777> ServerName soainternal.example.com:80 ServerAdmin email@example.com RewriteEngine On RewriteOptions inherit # WSM-PM <Location /wsm-pm> WLSRequest ON WebLogicCluster SOAHOST1:7010,SOAHOST2:7010 </Location> </VirtualHost>
To verify the changes 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 using the Oracle WebLogic Server administrator credentials:
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 using a similar URL: