1. Home
  2. Knowledge Base
  3. Howto's
  4. How to load balance Oracle JD Edwards for high availability

How to load balance Oracle JD Edwards for high availability

How to load balance Oracle JD Edwards


The goal of this article is to explain how to configure the SKUDONET Load Balancer for offering High availability and load balance service to JD Edwards, this configuration will allow the continuity of the service behind any failure.

Load Balancing is a technique used by the application delivery controller software that offers the IT system the capacity to scale easily, create total availability, and not lose the service in case some part of the IT architecture fails. SKUDONET offers the possibility of load balance JD Edwards adding the following features:

  • The user sessions are saved and persistent in case a failure is detected in one of the JD Edward servers that built the IT architecture.
  • Increase of concurrency, as the load balancer offers the capability of configuring more than one JD Edward server in case one of them fails, the other can continue with the service.
  • The sysadmin team can update part of the JD Edwards’ servers without losing the service, and the other servers can continue working and managing users without concern.

Oracle JD Edwards EnterpriseOne

Oracle JD Edwards EnterpriseOne is a suite of Oracle Applications that are built to offer ERP services (Enterprise resource planning), in the list of services offered by an ERP includes, voice calls, planning, invoices, purchases, financial activities, sales and marketing, inventory, delivery, shipping among others.

To continue with the configuration of JD Edwards in high availability for high performance and scalability it is required to deploy a SKUDONET Application Delivery Controller appliance on-premise or on cloud.

Please refer to our load balancing solutions in case you have not deployed a SKUDONET appliance yet.

The information you will find in this article works for SKUDONET Enterprise 6.3 and later versions and for SKUDONET Community 7.0 and later versions.

The environment we are going to describe is the following:

Load balance Oracle JD Edwards environment high availability

SKUDONET Application delivery controller can configure the Weblogic applications service (JD Edward frontends) in high availability in two different ways, please use one of them based on which one fits better your needs.

  • SKUDONET ADC will be configured with an L4XNAT profile (mode 1), the TCP traffic will pass through the load balancer.
  • SKUDONET ADC will be configured with an HTTP(S) profile, the application data is forwarded and decisions can be taken based on the HTTP Headers.

Follow the indications that better fit your needs.

Before starting to configure the Weblogic replication data service

JD Edwards server offers mechanisms to avoid any session data loss, Weblogic offers the cluster service, and this cluster replicates information related to the sessions, in case one of the Weblogic instances fails, the session related to the client created in this instance will be available in the other available servers. This capability ensures that the information related to the session isn’t lost but this service doesn’t offer load balancing, scalability, and high availability completely, for that we will use the SKUDONET Application Delivery controller.

The configuration of the WebLogic cluster is out of this scope, please refer to the official documentation.

Configure the farm in HTTPS, mode 2

Step 1: Create an HTTP(S) farm

In this section, we present a different configuration method, the load balancer will work now like a reverse proxy in user space analyzing the HTTP headers and moving traffic not at the TCP level but at the Application level (HTTP protocol)

Go to the Lateral menu of the web GUI, LSLB >> Farms

Create a new farm in the LSLB  section, now, select HTTP as profile, and port 443, configure the descriptive name of JDEdwardsHTTP, and select the Virtual IP (configured as Virtual Interface previously)

Create an HTTP(S) farm

Once the farm is created edit it and click on the Global Tab, please change the Listener to HTTPS mode, this change will show new parameters related to the HTTPS protocol configuration, please configure them  as shown below:

How to change the Listener to HTTPS mode

Taking into consideration HTTPS parameters, Only TLSv1.1 and TLSv1.2 should be enabled. TLSv1.3 is enabled by default.

Ciphers are configured in All mode but if you want to not allow different Ciphers please apply the configuration here.

The Certificates section shows the available certificates in the system, for testing purpose the present certificate by default is good enough but once you move to production we recommend configuring a new certificate, you can deploy a certificate for a CN from 3rd party certifiers or use our Let’s Encrypt connector in lateral menu LSLB > Let’s Encrypt

The other parameters in this Global Tab are configured by default, no further changes are required.


Step 2: Create a service and the backends

In this section, we will configure a new Service as we have done in the L4XNAT section, go to tab “Services” in the HTTPS farm we are configuring, and add a new service with the name Find the JDService

Create a service and the backends

Step 3: Advanced checking

We will proceed here exactly the same way as for the L4xNAT farm, the already created Health check for the L4XNAT farm can be used here. In difference to the L4XNAT profile, the usage of farmguardian in HTTP(S) farms is not mandatory as this profile runs inherent TCP checks in each HTTP backend connection. The L4XNAT profile doesn’t run any checks so if we want to detect a failure in the backends configured in this profile a farmguardian health check is required.

Now the system is ready to load balance JD Edward EnterpriseOne with a SKUDONET HTTPS profile in the LSLB module using the same Virtual IP in TCP port 443 listening in SSL mode, the request is sent to the JD Edwards backends in the WebLogic servers IPs and with Port 8080 in HTTP mode. This configuration is known as SSL Offloading, the communication between clients and the Load Balancer is done in HTTPS Secure Mode but the communication between the Load Balancer and Backends is done in HTTP mode (no SSL).

Final considerations

SKUDONET fully supports JD Edwards load balanced in High availability, so we hope you find this how-to for Load Balance JD Edwards useful; in case you have further doubts and want to discuss any topic related to this implementation please contact us and we will be glad to solve any doubt.

Was this article helpful?

Related Articles

Download Skudonet ADC Load Balancer
Community Edition

Source Code

A versatile and installable ADC system designed for diverse vendor hardware.


Installable ISO 

Load Balancing as a Service alongside an ADC orchestration toolkit.

Download Community Edition

Download Community Edition

“We manage the information you provide with the sole aim of assisting with your requests or queries in regards to our products or services; applying the computer and security procedures to ensure its protection. Your data can be rectified or removed upon request but won’t be offered to any third parties, unless we are legally required to do so.” Responsible: SKUDONET SL - info@skudonet.com