11 Configuring the Web Tier for an Enterprise Deployment

This chapter describes how to install Oracle HTTP Server and extend the enterprise deployment domain with two Oracle HTTP Server instances.

This chapter contains the following sections:

11.1 Variables Used in This Chapter

As you perform the tasks in this chapter, you will be asked to enter the following values for several directory variables defined in Section 7.4, "File System and Directory Variables Used in This Guide".

  • ORACLE_HOME

  • ASERVER_HOME

  • MSERVER_HOME

  • APPLICATION_HOME

In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Section 5.2.3, "Physical and Virtual IP Addresses Required by the Enterprise Topology":

  • ADMINVHN

  • SOAHOST1

  • SOAHOST2

  • WEBHOST1

  • WEBHOST2

11.2 Installing Oracle HTTP Server in Preparation for an Enterprise Deployment

The following sections describe how to install the Oracle HTTP Server software in preparation for extending your existing domain with Oracle HTTP Server instances:

11.2.1 Starting the Installation Program on SOAHOST1

To start the installation program, perform the following steps.

  1. Log in to SOAHOST1.

  2. Go to the directory in which you downloaded the installation program.

  3. Launch the installation program by entering the following command:

    ./fmw_12.1.3.0.0_ohs_linux64.bin

    When the installation program appears, you are ready to begin the installation.

11.2.2 Navigating the Oracle HTTP Server Installation Screens

Table 11-1 lists the screens in the order that the installation program displays.

If you need additional help with any of the installation screens, click the screen name.

Note:

Oracle Fusion Middleware Infrastructure screens are used as sample screens and all screens are exactly the same with the exception of the Installation Type screen.

Table 11-1 Oracle HTTP Server Install Screens

Screen Description

Welcome

This screen introduces you to the product installer.

Installation Location

Use this screen to specify the location of your Oracle home directory.

For the purposes of an enterprise deployment, enter the value of the ORACLE_HOME variable listed in Table 7-3.

Installation Type

Select Collocated HTTP Server (Managed through WebLogic server).

This installation type allows you to configure the Oracle HTTP Server instances as part of the existing Oracle WebLogic Server domain.

Prerequisite Checks

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 Section 5.1.2, "Host Computer Hardware Requirements" and Section 5.1.3, "Operating System Requirements for the Enterprise Deployment Topology".

Installation Summary

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.

Installation Progress

This screen allows you to see the progress of the installation.

Installation Complete

This screen appears when the installation is complete. Review the information on this screen, then click Finish to dismiss the installer.

11.2.3 Verifying the Installation

To verify that your installation was completed successfully, you can compare the Oracle home directory structure to the one shown in Chapter 7, "Preparing the File System for an Enterprise Deployment".

The addition of Oracle HTTP Server adds the ohs product directory to the Oracle home.

11.2.4 Installing Oracle HTTP Server on the Other Host Computers

After you install the Oracle HTTP Server software on SOAHOST1, then you must also install it on the local storage device for WEBHOST1 and for WEBHOST2. The host computers in the Web tier reside in the DMZ, and do not necessarily have access to the shared storage device in the application tier, so the software must be installed locally.

In addition, if you have configured a separate shared storage volume for SOAHOST2, then you should also install the Infrastructure on SOAHOST2. For more information, see Section 7.2, "Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment".

Using the directory structure guidelines, install the Oracle Fusion Middleware Infrastructure on WEBHOST1and WEBHOST2.

11.3 Extending the Domain with Oracle HTTP Server

The following sections describe how to extend the initial enterprise deployment domain to include the required Oracle HTTP Server instances:

11.3.1 Starting the Configuration Wizard on SOAHOST1

Note:

If you added any customizations directly to the start scripts in the domain, those will be overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.sh and configure it, for example, add custom libraries to the WebLogic Server classpath, specify additional java command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

To start the Configuration Wizard:

  1. Shut down the Administration Server to prevent any configuration locks, saves, or activations from occurring during the configuration of the domain:

    To stop the Administration Server using the Node Manager:

    1. Start WLST:

      cd ORACLE_COMMON_HOME/common/bin
./wlst.sh

    2. Connect to Node Manager using the Node Manager credentials you defined in when you created the domain in the Configuration Wizard:

      wls:/offline>nmConnect('nodemanager_username','nodemanager_password',
            'ADMINVHN','5556','domain_name',
            'ASERVER_HOME')

      Note:

      This username and password are used only to authenticate connections between Node Manager and clients. They are independent of the server admin ID and password and are stored in the nm_password.properties file located in the following directory: 
      ASERVER_HOME/config/nodemanager

    3. Stop the Administration Server:

      nmKill('AdminServer')

    4. Exit WLST:

      exit()

  2. Navigate to the following directory and start the WebLogic Server Configuration Wizard.

    cd ORACLE_HOME/oracle_common/common/bin
./config.sh

11.3.2 Navigating the Configuration Wizard Screens to Extend the Domain

Follow the instructions in this section to update an existing Infrastructure domain with an Oracle HTTP Server instance.

Note:

When you are adding an Oracle HTTP Server instance to an existing domain, verify that the ports you are assigning to any new components are available. The Configuration Wizard does not perform automatic port allocation.
Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Update an existing domain.

In the Domain Location field, select the path represented by the ASERVER_HOME variable.

This is the same domain home location that you specified while configuring the Infrastructure domain in Chapter 10, and it is the domain home where the active Administration Server resides.

Tip:

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.

Task 2   Selecting the Configuration Templates

On the Templates screen, ensure that Update Domain Using Product Templates is selected, and then select Oracle HTTP Server (collocated). This automatically selects Oracle Enterprise Manager Plugin for WEBTIER - 12.1.3.0 [em].

Click Next.

Tip:

More information about the options on this screen can be found in "Templates" in Creating WebLogic Domains Using the Configuration Wizard.
Task 3   Specifying the Datasource Configuration Type

All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.

Click Next.

Task 4   Specifying JDBC Component Schema Information

Verify that the values on this screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

Task 5   Testing the JDBC Connections

Use this screen to test the existing data source connections.

Tip:

More information about the other options on this screen can be found in "Test Component Schema" in Creating WebLogic Domains Using the Configuration Wizard
Task 6   Selecting Advanced Configuration

To update the domain configuration for the topology, select System Components on the Advanced Configuration screen.

Task 7   Adding System Components

On the System Components screen, create two Oracle HTTP Server instances:

  1. Click Add to create the first Oracle HTTP Server instance.

  2. Specify OHS_1 in the System Component field.

  3. Specify OHS in the Component Type field.

  4. Restart Interval Seconds: Specify the number of seconds to wait before attempting a restart if an application is not responding.

  5. Restart Delay Seconds: Specify the number of seconds to wait between restart attempts.

  6. Click Add again to create a second Oracle HTTP Server instance

    For the second instance, enter OHS_2 in the System Component field.

Task 8   OHS Server screen

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

  1. Select the first Oracle HTTP Server instance (OHS_1) from the System Component drop-down menu

  2. In the Listen Address field, enter WEBHOST1.

    All of the remaining fields are pre-populated, but you can change the values as required for you organization. For more information about the fields on this screen, see "OHS Server" in Creating WebLogic Domains Using the Configuration Wizard.

  3. Select OHS_2 from the System Component drop-down menu.

  4. In the Listen Address field, enter WEHOST1.

    Set the Server Name field to the same value as the Listen Address.

Task 9   Creating Machines

Use the Machines screen to create two new machines in the domain. These two new machines will correspond to the WEBHOST1 and WEBHOST2 host computers where the Oracle HTTP Server instances reside:

  1. Select the Unix Machine tab.

  2. Click the Add button to create two new Unix machines.

    Use the values in Table 11-2 to define the Name and Node Manager Listen Address of each machine.

  3. Verify the port in the Node Manager Listen Port field.

    The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

Table 11-2 Values to Use When Creating Unix Machines for WEBHOST1 and WEBHOST2

Name Node Manager Listen Address Node Manager Listen Port

WEBHOST1

The value of the WEBHOST1 host name variable. For example, webhost1.example.com..

5556

WEBHOST2

The value of the WEBHOST2host name variable. For example, webhost2.example.com..

5556

Tip:

More information about the options on this screen can be found in Machines in Creating WebLogic Domains Using the Configuration Wizard.
Task 10   Assign System Components to Machines

Oracle HTTP Server instances are associated with a machine. Use this screen to assign system components to the appropriate WEBHOST machines.

  1. In the Machine list box, select WEBHOST1.

  2. Assign the OHS_1 instance to the WEBHOST1 machine:

    1. Select the WEBHOST1 in the Machines list box.

    2. Double-click OHS_1 in the System Components list box.

  3. Assign the OHS_2 instance to the WEBHOST2 machine:

    1. Select the WEBHOST2 in the Machines list box.

    2. Double-click OHS_2 in the System Components list box.

Tip:

You can associate an OHS machine to an existing machine or create a new machine. You typically create additional machines when you are planning to scale out the topology to multiple host computers. For more information, see "Scaling Out a Topology (Machine Scale Out)" in High Availability Guide.
Task 11   Reviewing Your Configuration Specifications and Configuring the Domain

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 update will not begin until you click Update.

Tip:

More information about the options on this screen can be found in "Configuration Summary" in Creating WebLogic Domains Using the Configuration Wizard.
Task 12   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the updated Domain home location and URL of the Administration Server.

You must make a note of both items as you will need them to start the servers and access the Administration Server.

Click Finish to dismiss the configuration wizard.

Task 13   Starting the Administration Server

After you exit the Configuration Wizard, start the Administration Server so the changes to the domain can be applied.

For more information, see Section 10.6.3, "Starting the Administration Server".

11.4 Propagating the Extended Domain to the Web Tier Host Computers

After you have extended the domain with the Oracle HTTP Server instances, and you have restarted the Administration Server on SOAHOST1, you can then perform the following tasks propagate the domain configuration to WEBHOST1 and WEBHOST2:

11.4.1 Packing Up the Extended Domain on SOAHOST1

Use the following steps to create a template jar file that contains the domain configuration information, which now includes configuration information about the Oracle HTTP Server instances:

  1. Log in to SOAHOST1 and run the pack command to create a template jar file as follows:

    cd ORACLE_COMMON_HOME/common/bin
 
./pack.sh -managed=true 
          -domain=ASERVER_HOME 
          -template=soadomaintemplateExtOHS.jar 
          -template_name=soadomaintemplateExtOHS

    In this example:

    • Replace ASERVER_HOME with the actual path to the domain directory you created on the shared storage device.

    • soadomaintemplateExtOHS.jar is a sample name for the jar file you are creating, which will contain the domain configuration files, including the confgiuration files for the Oracle HTTP Server instances.

    • soadomaintemplateExtOHS is the name assigned to the domain template file.

  2. Make a note of the location of the soadomaintemplateExtOHS.jar file you just created with the pack command.

    By default, the pack template file is created in the current directory where you ran the pack command. In this example, it would be created in the ORACLE_COMMON_HOME/common/bin directory, but you can specify a full path for the template jar file as part of the -template argument to the pack command.

    Tip:

    For more information about the pack and unpack commands, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

11.4.2 Unpacking the Domain on WEBHOST1

To create a directory containing the domain configuration information:

  1. Log in to WEBHOST1.

  2. Copy the template to the local storage on WEBHOST1.

    For example, log in to WEBHOST1 and run the following command:

    scp SOAHOST1:ORACLE_COMMON_HOME/common/bin/soadomaintemplateExtOHS.jar \
      ORACLE_COMMON_HOME/common/bin/

  3. If you haven't already, create the recommended directory structure for the Managed Server domain on the WEBHOST1 local storage device.

    Use the examples in Section 7.4, "File System and Directory Variables Used in This Guide" as a guide.

  4. Run the unpack command to unpack the template in the domain directory onto the local storage, as follows:

    cd ORACLE_COMMON_HOME/common/bin

./unpack.sh -domain=MSERVER_HOME
            -template=soadomaintemplateExtOHS.jar 
            -app_dir=APPLICATION_HOME
            -overwrite_domain=true

    In this example:

    • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

    • soadomaintemplateExtOHS.jar is the directory path and name of the template you created when you ran the pack command to pack up the domain on the shared storage device.

    Tip:

    For more information about the pack and unpack commands, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

  5. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the WEBHOST1 local storage device.

11.4.3 Unpacking the Domain on WEBHOST2

To create a directory containing the domain configuration information:

  1. Log in to WEBHOST2.

  2. If you haven't already, create the recommended directory structure for the Managed Server domain on the WEBHOST2 local storage device.

    Use the examples in Section 7.4, "File System and Directory Variables Used in This Guide" as a guide.

  3. Run the unpack command, as described in Section 11.4.2.

  4. Change directory to the newly created Managed Server domain directory (MSERVER_HOME) and verify that the domain configuration files were copied to the correct location on the WEBHOST2 local storage device.

11.5 Updating the OPSS JPS Configuration on the Web Tier Hosts

After you have propagated the domain configuration to both Web tier hosts (WEBHOST1 and WEBHOST2), update the OPSS configuration on both hosts, as follows.

This ensures that the Node Manager on the Web tier hosts does not attempt to access the database, which is in the data tier:

  1. Log in to WEBHOST1 and locate the following configuration file:

    MSERVER_HOME/config/fmwconfig/jps-config-jse.xml

  2. Open the file in a text editor and make the following change:

    Replace <jpsContexts default="default"> with <jpsContexts default="bootstrap_credstore_context">.

  3. Save the file.

  4. Make the same change to the jps-config-jse.xml file on WEBHOST2.

11.6 Starting the Node Manager and Oracle HTTP Server Instances on WEBHOST1 and WEBHOST2

The following sections describe how to start the Oracle HTTP Server instances on WEBHOST1 and WEBHOST2:

11.6.1 Starting the Node Manager on WEBHOST1 and WEBHOST2

Before you can start the Oracle HTTP Server instances, you must start the Node Manager on WEBHOST1 and WEBHOST2:

  1. Log in to WEBHOST1 and navigate to the following directory:

    MSERVER_HOME/bin

  2. Start the Node Manager as shown below, using nohup and nm.out as an example output file:

    nohup ./startNodeManager.sh > nm.out&

  3. Log in to WEBHOST2 and perform steps 1 and 2.

For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

11.6.2 Starting the Oracle HTTP Server Instances

To start the Oracle HTTP Server instance:

  1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:

    http://ADMINVHN:7001/em

    In this example:

  2. Log in to Fusion Middleware Control using the Administration Server credentials.

  3. Expand the HTTP Server folder in the navigation pane.

  4. Select the OHS instances you want to start (for example, OHS_1) and click Start Up from the top panel.

Tip:

More information about managing Oracle Fusion Middleware using Oracle Enterprise Manager Fusion Middleware Control can be found in Administering Oracle Fusion Middleware with Fusion Middleware Control.

For other tools and instructions, see "Starting Oracle HTTP Server Instances" in Administering Oracle HTTP Server.

11.7 Configuring Oracle HTTP Server for Administration and Oracle Web Services Manager

The following sections describe how to configure the Oracle HTTP Server instances to route requests to the Administration Server and to the Oracle Web Services Manager (WSM) Managed Servers:

11.7.1 About the Oracle HTTP Server Configuration for an Enterprise Deployment

The following sections provide overview information about the changes required to the Oracle HTTP Server configuration in an enterprise deployment:

11.7.1.1 Understanding Oracle HTTP Server 12c Configuration Files in a WebLogic Domain

When you configure Oracle HTTP Server 12c in a WebLogic Domain, the Oracle HTTP Server configuration files are managed by Oracle WebLogic Server.

As a result, you must modify the configuration of the Oracle HTTP Server instances by editing the configuration files in the Administration Server domain home. When you restart the Administration Server, Oracle WebLogic Server automatically propagates the configuration changes to the other domain machines.

11.7.1.2 Purpose of the Oracle HTTP Server Virtual Hosts

The reference topologies in this guide require that you define a set of virtual servers on the hardware load balancer. The load balancer virtual servers are described in Section 6.1.3, "Summary of the Virtual Servers Required for an Oracle SOA Suite Enterprise Deployment".

In this chapter, you 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 will later 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.

11.7.1.3 About the WebLogicCluster Parameter of the <VirtualHost> Directive

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.

11.7.1.4 Recommended Structure of the Oracle HTTP Server Configuration Files

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, which contains the virtual host definition for the Administration Server virtual host (ADMINVHN).

11.7.2 Modifying the httpd.conf File to Include Virtual Host Configuration Files

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

  1. Log in to SOAHOST1.

  2. Locate the httpd.conf file for the first Oracle HTTP Server instance (OHS_1) in the Administration Server domain directory:

    cd ASERVER_HOME/config/fmwconfig/components/OHS/OHS_1/

  3. Open the httpd.conf file in a text editor and make the following changes:

    1. Locate the following entry in the httpd.conf file:

      #NameVirtualHost *:80

    2. Remove the comment character (#) from the beginning of the line, and add WEBHOST1:7777 as the value for the NameVirtualHost directive:

      NameVirtualHost WEBHOST1:7777

    3. Verify that there is an INCLUDE statement in the httpd.conf that includes all *.conf files in the moduleconf subdirectory:

      include "moduleconf/*.conf"

      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.

  4. Save the httpd.conf file.

  5. Change directory to the following location so you can update the second Oracle HTTP Server instance (OHS_2) in the Administration Server domain directory:

    cd ASERVER_HOME/config/fmwconfig/components/OHS/OHS_2/

  6. Open the httpd.conf file in a text editor and make the same changes you made in Step 3.

11.7.3 Creating Configuration Files for the Administration Server and WLS_WSM Managed Servers

To create the virtual host configuration files for the Administration Server and WLS_WSM Managed Servers:

  1. Log in to SOAHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (OHS_1):

    cd OHS_ADMIN_CONF_DIR/moduleconf

  2. Create the admin_vh.conf file and add the following directive:

    <VirtualHost WEBHOST1:7777>
    ServerName admin.example.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
</VirtualHost>

  3. Create the soainternal_vh.conf file and add the following directive:

    <VirtualHost WEBHOST1:7777>
    ServerName soainternal.example.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit
</VirtualHost>

  4. Copy the admin_vh.conf file and the soainternal_vh.conf file to the configuration directory for the second Oracle HTTP Server instance (OHS_2):

    cd OHS_ADMIN_CONF_DIR/moduleconf

  5. Edit the admin_vh.conf and soainternal_vh.conf files and change any references to WEBHOST1 to WEBHOST2 in the <VirtualHost> directives.

  6. Restart the Administration Server.

  7. After the Administration Server is running, review the files in the following directories on both WEBHOST1 and WEBHOST2 to be sure they contain the modifications made in the Administration Server domain directory:

    MSERVER_HOME/config/fmwconfig/components/OHS/instances/OHS_1/

    MSERVER_HOME/config/fmwconfig/components/OHS/instances/OHS_2/

  8. Restart both Oracle HTTP servers.

11.7.4 Validating the Virtual Server Configuration on the Load Balancer

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://soainternal.example.com/index.html

11.7.5 Configuring Routing to the Administration Server and Oracle Web Services Manager

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 WebLogicCluster parameter:

  1. Log in to SOAHOST1, and change directory to the following location:

    OHS_ADMIN_CONF_DIR/moduleconf

  2. Add the following directives to the admin_vh.conf file within the <VirtualHost> tags:

    # Admin Server and EM
<Location /console>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>

<Location /consolehelp>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>

<Location /em>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>

    The admin_vh.conf file will appear as it does in Example 1.

  3. Add the following directives to the soainternal_vh.conf file within the <VirtualHost> tag:

    # WSM-PM
<Location /wsm-pm>
    SetHandler weblogic-handler
    WebLogicCluster SOAHOST1:7010,SOAHOST2:7010
    WLProxySSL ON
    WLProxySSLPassThrough ON
</Location>

    The soainternal_vh.conf file will appear as it does in Example 2.

    For more information about the WebLogicCluster parameter in this example, see Section 11.7.1.3.

  4. Restart the Administration Server.

  5. Restart both Oracle HTTP Server instances.

Example 1   admin_vh.conf file
<VirtualHost WEBHOST1:7777>
    ServerName admin.example.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit

# Admin Server and EM
<Location /console>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>

<Location /consolehelp>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>

<Location /em>
    SetHandler weblogic-handler
    WebLogicHost ADMINVHN
    WeblogicPort 7001
</Location>
</VirtualHost>
Example 2   soainternal_vh.conf file

Contents of this file:

<VirtualHost WEBHOST1:7777>
    ServerName soainternal.example.com:80
    ServerAdmin you@your.address
    RewriteEngine On
    RewriteOptions inherit

# WSM-PM
<Location /wsm-pm>
    SetHandler weblogic-handler
    WebLogicCluster SOAHOST1:7010,SOAHOST2:7010
</Location>
</VirtualHost>

11.7.6 Validating the Virtual Server Routing Through the Load Balancer, Web Tier, and Application Tier

To verify the changes you have made in this chapter:

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

    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.

  2. Similarly, you should be able to access the Fusion Middleware Control using a similar URL:

    http://admin.example.com/em

  3. After you log in to Fusion Middleware Control, verify the successful configuration of the Oracle HTTP Server instances, by viewing the Oracle HTTP Server instances in the Target Navigation pane:

    1. In the Target Navigation pane, expand the HTTP Server folder.

    2. Click one of the Oracle HTTP Server instances to display the HTTP Server home page.

    3. Verify that the instance is up and available.

  4. Validate the Oracle Web Services Manager URL, using the following URL:

    http://soainternal.example.com/wsm-pm