Skip Headers
Oracle® Fusion Middleware Using Clusters for Oracle WebLogic Server
12c Release 1 (12.1.1)

Part Number E24425-05
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

D Configuring Radware Load Balancers for MAN/WAN Failover

WebLogic Server provides failover within MAN and WAN networks. This feature provides more reliability by allowing failover to occur across a larger geographic area. It also provides failover across multiple WebLogic Server domains.

To provide failover within a MAN/WAN environment, you must use hardware load balancers. This document outlines the procedures for configuring Radware hardware load balancers to work with WebLogic Server.

For information on configuring WebLogic Server to use MAN/WAN, see Session State Replication Across Clusters in a MAN/WAN. For information on configuring Radware hardware load balancers, see http://www.radware.com.

The following sections describe how to configure Radware hardware load balancers:

Requirements

Before performing the procedures described in this appendix, ensure that you have performed the following:

Once these requirements are met, use the following procedures to configure your load balancers to work within a MAN/WAN environment.

Step 1: Configure an Authoritative Delegation Zone

The first step in configuring Web Server Director is to create an Authoritative Delegation Zone within the local DNS. To do this, perform the following using the Radware administration utility:

  1. Click on the name of your local DNS.

  2. Click New Delegation.

  3. Enter a name for the new delegation zone

  4. Add the IP address for each Radware device

Step 2: Configure Farm Virtual IPs and Servers

Web Server Director balances load among servers within a server farm. Clients access a server using a virtual IP address. Web Server Director directs traffic from this virtual IP address to the appropriate server. The following sections describe how to create and configure server farm virtual IPs.

Create a Farm IP

To create a farm IP, perform the following using the Radware administration utility:

  1. Select WSD.

  2. Select Farms.

  3. Select Farm Table.

  4. Click Create a Farm.

  5. Enter an IP address and DNS alias for the farm.

  6. Ensure that Admin Status is enabled.

  7. Click Set.

Configure the Dispatch Method for the Server Farm

To configure the dispatch method for the server farm, perform the following procedures using the Radware configuration utility:

  1. Select WSD.

  2. Select Farms.

  3. Select Farm Table.

  4. Select the farm you want to configure

  5. In the Farm Properties window, select the menu next to Dispatch Method.

  6. Select the desired algorithm

  7. Click Set.

Creating Farm Servers

To configure a farm server, perform the following procedures using the Radware administration utility:

  1. Select WSD.

  2. Select Servers.

  3. Select Application Servers.

  4. Select the Farm IP created above.

  5. Add the server IP address.

  6. Add the server name.

  7. Ensure that Admin Status is enabled.

Step 3: Configure Port Multiplexing

Use the following procedures to configure port multiplexing:

  1. Select WSD.

  2. Select Farms.

  3. Select Farm Table.

  4. Select the farm you want to configure.

  5. In the Properties window, enter a value in the Multiplexed Port field.

  6. Select WSD.

  7. Select Servers.

  8. Select Application Servers.

  9. For each local server, select the server from the table and enter the application port in the Multiplexed Server Port field.

  10. Click Set.

Step 4: Configure HTTP Redirects

You must configure HTTP redirects in order to configure global load balancers to work within a MAN/WAN environment. HTTP redirects ensure proper distribution of traffic across Web Server Director devices.

To configure HTTP redirect, perform the following procedures using the Radware administration utility:

  1. Select WSD.

  2. Select Farms.

  3. Select Farm Table.

  4. Select the farm that you want to configure.

  5. Select HTTP Redirection in the Redirection Mode section.

  6. Select HTTP Redirection in the DNS Redirection Fallback section.

  7. Click Set.

  8. Select WSD.

  9. Select Servers.

  10. Select Application Servers.

  11. Select the server in the farm that represents the distributed farm on the remote WSD

Step 5: Configure Session ID Persistency

Server persistence is based on HTTP session IDs. Web Server Director inspects incoming traffic to a farm, then selects the appropriate server based on session information in the HTTP header. To configure session ID persistency, perform the following procedures using the Radware administration utility:

  1. Select WSD.

  2. Select L7 Load Balancing.

  3. Select Session Persistency.

  4. Click Create.

  5. Select the farm you want to configure.

  6. Set the application port of your farm.

  7. Set Persistency Identification to JESESSIONID.

  8. Set Value Offset to 53.

  9. Set Stop Chars to :!.

  10. Set Inactivity Timeout to the value of your session time-out.

Step 6: Configure LRP

Configuring the LRP component ensures that traffic is correctly distributed to remote locations. To configure LRP, perform the following:

  1. Select WSD.

  2. Select Distributed Systems.

  3. Select Report Configuration.

  4. Click Create Distributed Farm Address.

  5. Set Distributed Farm Address to the remote farm IP address.

  6. Set Remote WSD Address to the IP address of the second Radware device.

  7. Click Set.

Step 7: Configure WebLogic Server Components

After you have configured your Radware devices, you must configure WebLogic Server to use MAN/WAN failover. For information on configuring WebLogic Server to use MAN/WAN, see Session State Replication Across Clusters in a MAN/WAN.