JBoss Application Server

1 Introduction

JBoss is an application server authored by JBoss, which is now developed by Red Hat. It was renamed WildFly in November 2014. It is written in Java and implements the Java Platform, Enterprise Edition (Java EE) specification. It runs on multiple platforms and is open source.

The KEMP LoadMaster is used to load balance the JBoss workload. The LoadMaster offers advanced Layer 4 and Layer 7 server load balancing, SSL Acceleration and a multitude of other advanced Application Delivery Controller (ADC) features. The LoadMaster intelligently and efficiently distributes user traffic among the application servers so that users get the best experience possible.

1.1 Document Purpose

This document provides the recommended LoadMaster settings used when load balancing the JBoss workload. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined. The KEMP support site can be found at: https://support.kemptechnologies.com

1.2 Intended Audience

This document is intended to be read by anyone who is interested in configuring the LoadMaster to optimize JBoss Application Server.

2 Template

KEMP has developed a template containing our recommended settings for this workload. You can install this template to help when creating Virtual Services, as it automatically populates the settings. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation.

For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description on the KEMP Documentation Page.

For steps on how to manually add and configure each of the Virtual Services using the recommended settings, refer to the steps in this document.

3 Architecture

Architecture.png

4 Configure the LoadMaster

The deployed JBoss environment determines which of the following setups is used.

4.1 Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet not the Virtual Service address.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration > Miscellaneous Options > Network Options.

SCMONO002.png

2. Tick the Subnet Originating Requests check box.

4.2 Enable Check Persist Globally

It is recommended that you change the Always Check Persist option to Yes – Accept Changes. Use the following steps:

1. Go to System Configuration > Miscellaneous Options > L7 Configuration.

SCMOLC001.png

2. Click the Always Check Persist dropdown arrow and select Yes – Accept Changes.

4.3 Create the JBoss Virtual Services

The following sections describe the recommended settings for the JBoss Virtual Services.

4.3.1 Create a JBoss Web App HTTP Virtual Service

The following are the steps involved and the recommended settings to configure the JBoss Web App HTTP Virtual Service:

1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services > Add New.

Create a JBoss Web App HTTP.png

2. Enter a valid Virtual Address.

3. Enter 80 as the Port.

4. Enter a recognizable Service Name, such as JBoss Web App HTTP.

5. Click Add this Virtual Service.

6. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 

 

Timeout

1 Hour

 

 

Scheduling Method

least connection

 

 

Idle Connection Timeout

660 (seconds)

Click Set Idle Timeout.

Real Servers

Checked Port

8080

 

7. Add the Real Servers:

a) Expand the Real Servers section.

b) Click Add New.

c) Enter the address of the relevant real server.

d) Complete the other fields as required.

e) Click Add this Real Server then click OK to the pop-up message.

f) Repeat the steps above to add more Real Servers as needed, based on your environment.

4.3.2 Create a JBoss Web App HTTPS Offloaded Virtual Service

The following are the steps involved and the recommended settings to configure the JBoss Web App HTTPS Offloaded Virtual Service:

1. In the main menu of the LoadMaster WUI, go to Virtual Services > Add New.

Create a JBoss Web App HTTPS.png

2. Enter a valid Virtual Address.

3. Enter 443 as the Port.

4. Enter a recognizable Service Name, such as JBoss Web App HTTPS Offloaded.

5. Click Add this Virtual Service.

6. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 

 

Timeout

1 Hour

 

 

Scheduling Method

least connection

 

 

Idle Connection Timeout

660 (seconds)

Click Set Idle Timeout.

SSL Properties

SSL Acceleration

Enabled

 

 

Cipher Set

BestPractices

 

Advanced Properties

Add a Port 80 Redirector VS

https://%h%s

Click the Add HTTP Redirector button. This automatically creates a redirect on port 80.

Real Servers

Checked Port

8080

 

7. Add the Real Servers:

a) Expand the Real Servers section.

b) Click Add New.

c) Enter the address of the relevant Real Server.

d) Complete the other fields as required.

e) Click Add this Real Server then click OK to the pop-up message.

f) Repeat the steps above to add more Real Servers as needed, based on your environment.

4.3.2.1 Create a JBoss Web App HTTPS Offloaded HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected using HTTP to the HTTPS Virtual Service. KEMP also recommends changing the Persistence Mode to None.

4.3.3 Create a JBoss Web App HTTPS Reencrypted Virtual Service

The following are the steps involved and the recommended settings to configure the JBoss Web App HTTPS Reencrypted Virtual Service:

1. In the main menu of the LoadMaster WUI, go to Virtual Services > Add New.

Create a JBoss Web App HTTPS_1.png

2. Enter a valid Virtual Address.

3. Enter 443 as the Port.

4. Enter a recognizable Service Name, such as JBoss Web App HTTPS Reencrypted.

5. Click Add this Virtual Service.

6. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 

 

Timeout

1 Hour

 

 

Scheduling Method

least connection

 

 

Idle Connection Timeout

660 (seconds)

Click Set Idle Timeout.

SSL Properties

SSL Acceleration

Enabled

 

 

Reencrypt

Enabled

 

 

Cipher Set

Best Practices

 

Advanced Properties

Add a Port 80 redirector VS

https://%h%s

Click the Add HTTP Redirector button. This automatically creates a redirect on port 80.

Real Servers

Checked Port

8443

 

7. Add the Real Servers:

a) Expand the Real Servers section.

b) Click Add New.

c) Enter the address of the relevant Real Server.

d) Complete the other fields as required.

e) Click Add this Real Server then click OK to the pop-up message.

f) Repeat the steps above to add more Real Servers as needed, based on your environment.

4.3.3.1 Create a JBoss Web App HTTPS Reencrypted Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected using HTTP to the HTTPS Virtual Service. KEMP also recommends changing the Persistence Mode to None.

4.3.4 Create a JBoss Web App HTTPS Straight Through Virtual Service

The following are the steps involved and the recommended settings to configure the JBoss Web App HTTPS straight through Virtual Service:

1. In the main menu of the LoadMaster WUI, go to Virtual Services > Add New.

Create a JBoss Web App HTTPS_2.png

2. Enter a valid Virtual Address.

3. Enter 443 as the Port.

4. Enter a recognizable Service Name, such as JBoss Web App HTTPS straight through.

5. Click Add this Virtual Service.

6. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 

 

Timeout

1 Hour

 

 

Scheduling Method

least connection

 

 

Idle Connection Timeout

660

Click Set Idle Timeout.

Advanced Properties

Add a Port 80 Redirector VS

 

Click the Add HTTP Redirector button. This automatically creates a redirect on port 80.

Real Servers

Checked Port

8443

 

7. Add the Real Servers:

a) Expand the Real Servers section.

b) Click Add New.

c) Enter the address of the relevant Real Server.

d) Complete the other fields as required.

e) Click Add this Real Server then click OK to the pop-up message.

f) Repeat the steps above to add more Real Servers as needed, based on your environment.

4.3.4.1 Create a JBoss Web App HTTPS Straight Through HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected using HTTP to the HTTPS Virtual Service. KEMP also recommends changing the Persistence Mode to None.

References

Unless otherwise specified, the following documents can be found at http://kemptechnologies.com/documentation.

Virtual Services and Templates, Feature Description

Document History

 

Date

Change

Reason for Change

Version

Resp.

Aug 2016

Initial draft

First draft

1.0

POC

May 2017

Minor updates

Minor enhancements

2.0

CMC

July 2017 Minor updates Updates made 3.0 CMC

 

 

Was this article helpful?

0 out of 0 found this helpful

Comments