Oracle WebLogic Server 12c: Installing and Configuring a Cluster Proxy

If the administration server of the domain is not already running, it must be started. To start it, in a Terminal window, navigate to the domain directory, and enter the command:

./startWebLogic.sh

When prompted for a username and password, enter the credentials of the domain administrator.

After the administration server is up and running, determine whether or not your domain is running the Enterprise Manager Fusion Middleware Control application.

Open a web browser and enter the URL:

http://hostname:port/em

In this tutorial, that is: http://host01.example.com:8001/em

Note: Use the host name of your host. Also, if you used a different port number for the administration server, use that port instead.

If you receive a 404 or Not Found message, then Enterprise Manager is not running on your domain. You will use this information when installing Web Tier.

If any of the servers in your WebLogic cluster (dizzy1, dizzy2, dizzy3) are not yet running, start them.

If you have previously configured and started the Node Manager, as described in the Oracle WebLogic Server 12c: Configuring and Using Node Manager tutorial, you can start these managed servers by using the administration console. Otherwise, start each server from within a Terminal window with the start script. For example:

./startManagedWebLogic.sh dizzy1 host01.example.com:8001

Download the browsestore.war web application. Place it in a location that is accessible to your WebLogic domain.

In this tutorial, the directory /u01/app/oracle/Middleware/user_projects/applications was created and the file was placed there.

Open a web browser and enter the URL of the domain's administration console. In this tutorial, that is: http://host01.example.com:8001/console

Note: Use the host name and port of the administration server of your domain.

On the Welcome screen, log in using the username and password entered to start the servers.

In the Change Center, click the Lock & Edit button.

Under Domain Structure, click Deployments.

On the right, under Deployments, click the Install button.

Find the Current Location field. Use the links to browse to the location in which you placed the downloaded browsestore.war file. There you will see browsestore.war with a radio button next to it. Select that radio button. The console then fills in the Path field for you.

Alternatively, you can type in the path and file name in the Path field yourself.

Then click Next.

On the next screen, ensure that the option Install this deployment as an application is selected. Then click Next.

On the next screen, select the cluster dizzycluster. Then click Next.

On the next screen, keep all the default values and click Finish.

In the Change Center, click the Activate Changes button.

In the Deployments table, select the check box to the left of the browsestore application. Then use the Start drop-down list to select the option Servicing all requests.

When prompted, click Yes to continue.

Download and extract the Oracle WebTier Utilities 11g installer zip file.

The WebLogic plug-in supports Oracle HTTP Server 11.1.1.1 or later, but using the latest (11.1.1.6+) is recommended.

You can install Oracle Web Tier either on the same machine that is running WebLogic Server or on a different machine.

Open a Terminal window and navigate to the location where you extracted the installer. Launch the installer:

cd Disk1

./runInstaller

If no Oracle installation inventory already exists on this machine for the current user, the Specify Inventory Directory screen appears. Accept the defaults and click OK.

You are also prompted to run a script createCentralInventory.sh as the root user. Follow these instructions and then click OK.

When the Welcome screen appears, click Next.

In the Install Software Updates screen, select the option Skip Software Updates and click Next.

In the Select Installation Type screen, select the option Install and Configure and click Next.

In the Prerequisite Checks screen, verify that all checks succeeded and then click Next.

If one or more tests fail, a full description of the issue can be found in the bottom panel, along with possible workarounds or corrections. You may need to exit the installer to correct a problem before proceeding.

In the Specify Installation Location screen, enter an appropriate install location. This can either be an existing Middleware Home or a new one. This tutorial will use the following values:

Oracle Middleware Home: /u01/app/oracle/Middleware

Oracle Home Directory: Oracle_WT1

Click Next.

In the Specify Security Updates screen, if you have an Oracle Support account you can enter your Email address. For this tutorial, the option I wish to receive security updates via My Oracle Support is cleared.

Click Next. If prompted for confirmation, click Yes.

In the Configure Components screen, verify that both Oracle HTTP Server and Oracle Web Cache are selected.

If you determined earlier that Enterprise Manager Fusion Middleware Control is running in your domain, then select the option Associate Selected Components with WebLogic Domain. Otherwise, do not select this option.

Click Next.

If you selected this option, the Specify WebLogic Domain screen appears. Enter the Host Name, Port Number, User Name, and Password for your WebLogic administration server. For this tutorial those values would be:

Host Name: host01.example.com

Port Number: 8001

User Name: weblogic

Password: Welcome1

In the Specify Component Details screen, leave the default values for all fields. Then click Next.

In the Web Cache Administrator Password screen, enter the password Welcome1. Then click Next.

In the Configure Ports screen, select the option Auto Port Configuration and click Next.

In the Installation Summary screen, click Install. Complete the installation and configuration.

You are also prompted to run a script oracleRoot.sh as the root user. Follow these instructions and then click OK.

When finished, click Finish to exit the installer.

Locate and edit the file <WEBTIER_HOME>/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf.

In this tutorial, <WEBTIER_HOME> is /u01/app/oracle/Middleware/Oracle_WT1.

Directly below the line <IfModule weblogic_module>, add a new line to link this HTTP Server to your WebLogic cluster. Provide the host and port for at least one server in the cluster. If you enter multiple host / port combinations, separate them with commas:

<IfModule weblogic_module>
WebLogicCluster host01.example.com:8003,host02.example.com:8005

Note: You are not required to specify the location of every WebLogic Server in your cluster. After one successful connection, the server will provide the plug-in with the locations of all servers that are currently running in the cluster. This server list is then updated with each request.

Add the following new lines to the end of the file:

<Location />
SetHandler weblogic-handler
</Location>

Save your changes.

Open a Terminal window and change directories to <WEBTIER_HOME>/instances/instance1/bin.

Execute the following command:

./opmnctl status

From the output of the command, verify that the HTTP Server process ohs1 is running ("Alive").

Execute the following command to restart the HTTP Server with the latest configuration changes:

./opmnctl restartproc ias-component=ohs1

Direct a browser to the browsestore application, but via the HTTP Server proxy. The default port is 7777:

http://<host>:7777/browsestore

For example:

http://host01.example.com:7777/browsestore

Locate the Terminal windows from which you started the servers in your WebLogic cluster. Use the output messages to confirm which server the request was directed to:

serviced request for the welcome page

If you started these servers with Node Manager instead of from a Terminal window, you will need to view the output log files (<server_name>.out in the server's logs directory).

Click the Browse Store link in the application. Then select a category check box and click the Retrieve Items button.

Once again, check which server each of the two prior requests was routed to:

serviced the request to browse the store

serviced request to print items

Kill the server that processed the most recent request ("serviced request to print items"). Use either Ctrl + C or the Linux kill command.

Return to your Web browser, and use the browsestore application to continue shopping. Select a different category.

Oracle HTTP Server should avoid the failed server with no interruption to the client.