Configure an HWLB to accept client requests in HTTP mode

Note This topic applies to Windows clients and to Service Manager web tier clients.

Prerequisites

Before you begin this process, verify that the following conditions are true:

  • The F5 management URL can be accessed through the management IP.
  • A VLAN is created on the interfaces.
  • Static IPs are available for the interfaces.

Step 1: Configure Secure Network Address Translation (SNAT)

If the server and client are located in the same local network, SNAT is required. To determine whether you must configure SNAT, please consult your Network Engineering team.

To configure SNAT, follow these steps:

  1. Click Local Traffic > SNATs > SNAT Pool List.
  2. Type TEST_SNAT in the Name field, type the IP address of the Virtual Server IP in the IP Address field, and then click Add.
  3. Click Finished.

Step 2: Configure an iRule to enable session persistence

Configure an iRule to enable session persistence for HTTP requests, based on the JSESSIONID cookie that the Service Manager server provides. To do this, follow these steps:

  1. Click Local Traffic > Virtual Servers > iRules > iRule List.
  2. Click Create, and then type TEST_JSESSION_IRULE in the Name field.
  3. If OneConnect transformations are enabled in the default HTTP profile, create an HTTP profile to disable the OneConnect transformations. To do this, Click Local Traffic > Profiles > Services > HTTP.

  4.  Copy the following text into the Definition area:
    when HTTP_REQUEST {
    if {[HTTP::cookie "JSESSIONID"] ne ""}{
    persist uie [string tolower [HTTP::cookie "JSESSIONID"]] 300
    } else {
    set jsess [findstr [string tolower [HTTP::path]] "jsessionid=" 11 ";"]
    if { $jsess != "" } {
    persist uie $jsess 300
    }
    }
    }when HTTP_RESPONSE {
    if {[HTTP::cookie "JSESSIONID"] ne ""} {
    persist add uie [string tolower [HTTP::cookie "JSESSIONID"]] 300
    }
    }
  5. Click Finished.

Step 3: Disable OneConnect transformations

If OneConnect transformations are enabled in the default HTTP profile, you must create a new HTTP profile. To do this, follow these steps:

  1. Click Local Traffic > Virtual Servers > Profiles > Services > HTTP.

  2. Click Create, and then type the TEST_HTTP in the Name field.

  3. Click the Custom check box.

  4. Disable the OneConnect Transformations, and then click Finish.

    Note Only complete step 4 (above) on HWLB configurations that use HTTP mode to connect to a web service (such as SRC).

Step 4: Create a new TCP-based health monitor

A TCP-based health monitor detects whether the Service Manager process is already listening to the port. You can also use the interface provided by Service Manager to check the RTE servlet status. For more information, see Configure an HWLB Health Monitor for the Service Manager server.

To create a new TCP-based health monitor, follow these steps:

  1. Click Local Traffic > Monitors.
  2. Click Create, and then type TEST_TCP in the Name field.
  3. Select tcp in the Type field, and then click Finished.

Step 5: Create a node

To create a node, follow these steps:

  1. Click Local Traffic > Nodes > Node List.
  2. Click Create, and then type the SM server host IP address.

Note  

  • There may be many Service Manager nodes (for example, in a horizontally-scaled Service Manager system).
  • You may add as many nodes as are required by your deployment.

Step 6: Configure a pool member

To configure a pool member, follow these steps:

  1. Click Local Traffic > Nodes > Pool List.
  2. Click Create, and then type TEST_POOL in the Name field.
  3. Select TEST_TCP as the health monitor.
  4. Type your server node and port, click Add, and then click Finished.
  5. On the Members tab, select TEST_POOL in the Pool list. Verify the members, and then click Enable.

Step 7: Create a new virtual server

To create a new virtual server, follow these steps:

  1. Click Local Traffic > Virtual Servers > Virtual Server List.
  2. Click Create, and then type TEST_VS in the Name field.
  3. Specify a virtual server IP address and port number.
  4. Select oneconnect as the OneConnect profile.

  5. Select TEST_HTTP as the HTTP Profile option.
  6. Select TEST_SNAT as the SNAT Pools option.
  7. Enable the TEST_JSESSION_IRULE iRule that you created previously.
  8. Select TEST_POOL as the Default Pool option.
  9. Click Finished.