Oracle Fusion Middleware requires that a certified Java Development Kit (JDK) is installed on your system.

To start the installation program, perform the following steps.

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.

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 the Oracle HTTP Server Oracle Home:

assistants
bin
cfgtoollogs
clone
crs
crypto
css
cv
deinstall
drdaas
env.ora
has
hs
install
instantclient
inventory
javavm
jdbc
jlib
jpub
ldap
lib
network
nls
odbc
ohs
olap
OPatch
opmn
oracle_common
oracore
oraInst.loc
ord
oss
oui
perl
plsql
plugins
precomp
QOpatch
racg
rdbms
root.sh
schagent.conf
sdk
slax
sqlcl
sqlj
sqlplus
srvm
suptools
ucp
unixODBC
usm
utl
webgate
wlserver
xdk

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

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 2, "Selecting the Configuration Templates"

• Task 3, "Selecting the JDK for the Web Tier Domain."

• Task 4, "Configuring System Components"

• Task 5, "Configuring OHS Server"

• Task 7, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 8, "Writing Down Your Domain Home"

Task 1   Selecting the Domain Type and Domain Home Location

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.

Tip:

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

Task 2   Selecting the Configuration Templates

On the Templates screen, select Oracle HTTP Server (Standalone) - [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.

Task 3   Selecting the JDK for the Web Tier Domain.

Select the Oracle HotSpot JDK installed in the /u02/oracle/products/jdk directory prior to the Oracle HTTP Server installation.

Task 4   Configuring System Components

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.

1. The default instance name in the System Component field is ohs1. Use this default name when you configure WEBHOST1.

2. Make sure that OHS is selected in the Component Type field.

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

4. Use the Restart Delay Seconds field to specify the number of seconds to wait between restart attempts.

Task 5   Configuring OHS Server

Use the OHS Server screen to configure the OHS servers in your domain:

1. Select ohs1 from the System Component drop-down menu.

2. In the Listen Address field, enter the value of WEBHOST1.

   All the remaining fields are prepopulated, but you can change the values as required for your organization. The non-ssl listener will be disabled manually later in this guide. See OHS Server in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

3. In the Server Name field, verify the value of the listen address and listen port.

   It should appear as follows:

   http://WEBHOST1:7777

Task 6   Configuring Node Manager

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.

Task 7   Reviewing Your Configuration Specifications and Configuring the Domain

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.

Task 8   Writing Down Your Domain Home

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.

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.

To start the Oracle HTTP Server instances:

Perform the following tasks to prepare the httpd.conf file for the additional virtual hosts required for an enterprise topology:

1. Log in to WEBHOST1.

2. 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/
   

3. Verify if the httpd.conf file has the appropriate configuration as follows:

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

   2. 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"

   3. 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"

   4. Save the httpd.conf file.

4. Ensure ssl.conf is included in the httpd configuration.

   
   grep ssl.conf httpd.conf
   include "ssl.conf"

5. Copy the ssl.conf file to a different file name.

   Note:

   This is used as a template for other module conf files.

   cp $WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/ssl.conf $WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/moduleconf/ssl.template

6. Edit the ssl.conf file to include only the following lines (remove other content from the file):

   
   <IfModule ossl_module>
   #
   # Some MIME-types for downloading Certificates and CRLs
       AddType application/x-x509-ca-cert .crt
       AddType application/x-pkcs7-crl .crl
   
   # Inter-Process Session Cache:
   # Configure the SSL Session Cache: First the mechanism
   # to use, second the expiring timeout (in seconds) and third
   # the mutex to be used.
       SSLSessionCache "shmcb:${ORACLE_INSTANCE}/servers/${COMPONENT_NAME}/logs/ssl_scache(512000)"
       SSLSessionCacheTimeout 300
   
   </IfModule>

7. Modify the $WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/mod_wl_ohs.conf to include the appropriate WLSSWallet file (required to route on SSL to the WLS backends) as follows:

   
   # NOTE : This is a template to configure mod_weblogic.
   
   LoadModule weblogic_module   "${PRODUCT_HOME}/modules/mod_wl_ohs.so"
   
   # This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level
   <IfModule weblogic_module>
    
       WLIOTimeoutSecs 900
       KeepAliveSecs 290
       FileCaching OFF
       WLSocketTimeoutSecs 15
       ErrorPage http://www.oracle.com/splash/cloud/index.html
       WLRetryOnTimeout NONE
       WLForwardUriUnparsed On
       SecureProxy On
       WLSSLWallet "/u02/oracle/config/keystores/orapki/"
   </IfModule>

8. Log in to WEBHOST2 and perform steps from 2 to 7, replacing any occurrences of WEBHOST1 or ohs1 with WEBHOST2 or ohs2 in the instructions as necessary.

To create the virtual host configuration files:

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.

• https://admin.example.com:445/index.html

• https://soainternal.example.com:444/index.html

To verify the changes that you have made in this chapter:

1. Access the Fusion Middleware Control by using the following URL:

   https://admin.example.com:445/em