Oracle JD Edwards

1 Introduction

Oracle’s JD Edwards EnterpriseOne is an integrated applications suite of comprehensive enterprise resource planning software that combines business value, standards-based technology and deep industry experience into a business solution with a low total cost of ownership.

JD Edwards EnterpriseOne offers a choice of databases, operating systems and hardware to build and expand an IT solution to meet business requirements. JD Edwards delivers over 80 application modules to support a diverse set of business processes and key industry solutions such as Consumer Package Goods, Manufacturing, Asset Intensive and Projects and Services.

Introduction.png

The KEMP LoadMaster can be used to enable scalability, load balancing and High Availability (HA) for JD Edwards environments. The diagram above shows an example network architecture where the LoadMaster is balancing traffic between two application servers.

1.1 Document Purpose

The purpose of this document is to explain how to add and configure a Virtual Service in the LoadMaster to load balance JD Edwards traffic. For further information and step-by-step instructions on LoadMaster functionality in general, such as HA, please refer to the KEMP documentation web page: http://kemptechnologies.com/documentation/.

1.2 Intended Audience

This document is intended to be used by anyone who is interested in finding out how to use a KEMP LoadMaster to load balance the Oracle JD Edwards EnterpriseOne workload.

1.3 Prerequisites

LoadMaster firmware version 7.16 or above should be installed.

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 Configure the LoadMaster

3.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.

3.2 Create a Content Rule (Header Modification)

The KEMP LoadMaster supports content switching, sometimes referred to as URL switching. This allows the LoadMaster to direct specific requests to specific Real Servers based on the contents of the requested URL.

Content switching can be very useful if there are dedicated server types that perform different functions such as image servers, static content servers, mapping servers, specialized content servers, application servers and media servers, that all need to be served from the same general hostname, for example www.mysite.com. Content switching also allows for hostname-specific servers and source IP-specific servers.

Content rules give the ability to:

  • Strip out server information
  • Redirect requests for the root of a server
  • Rewrite redirections from HTTP to HTTPS
  • Force connections to close
  • Secure cookies

The following content rule, which can be used when configuring a Virtual Service with or without SSL offloading, writes the URL so that users are sent to the domain.com/JDE_Hompage rather than the default homepage of the server:

Create a Content Rule Header.png

1. In the main menu, select Content Rules > Create New.

2. Enter a recognisable Rule Name in the text box.

3. Select Modify URL from the Rule Type drop-down list.

4. Enter /^\/$/ in the Match String text box.

5. Enter /jde/E1menu.maf in the Modified URL text box.

6. Select [Unset] from the Perform If Flag Set drop-down list.

7. Click the Create Rule button.

3.3 Configure the Virtual Service

3.3.1 Configure the Virtual Service without SSL Offloading for Oracle JD Edwards

This example configuration assumes that one Virtual Service and one Real Server are being set up. In a real situation, users may need to configure more.

To add and configure the Oracle JD Edwards without SSL Offloading Virtual Service, follow the steps below in the LoadMaster Web User Interface (WUI):

1. Add a Virtual Service:

Configure the Virtual Service_1.png

2. In the main menu, go to Virtual Services > Add New.

3. Enter a valid IP address in the Virtual Address text box.

4. Enter 80 as the Port.

5. Enter a recognizable Service Name, such as Oracle JD Edwards EnterpriseOne HTTP.

6. Ensure tcp is selected as the Protocol.

7. Click Add this Virtual Service.

8. Add the Content Rule to the Virtual Service.

9. Expand the Advanced Properties section.

VSVSAP024.png

10. Click the Show Header Rules button.

Configure the Virtual Service_1_2.png

11. From drop-down list in the Request Rules section of the HTTP header modification Rule Management screen, select the rule you created and click the Add button.

12. Click the Back button.

13. Configure the Standard Options section.

Configure the Virtual Service_1_3.png

14. Expand the Standard Options section.

15. Deselect the Transparency check box.

16. Select Active Cookie as the Persistence Mode.

17. Select 1 Hour as the Timeout value.

18. Enter EnterpriseOne-Cookie as the Cookie name and then click Set Cookie.

19. Select least connection as the Scheduling Method from the drop-down list.

20. Enter 1800 in the Idle Connection Timeout text box and click Set Idle Timeout.

21. Ensure Normal-Service is selected as the Quality of Service.

22. Expand the Real Servers section.

Configure the Virtual Service_1_4.png

23. Select HTTP Protocol in the Real Server Check Parameters drop-down list.

24. Enter /jde/index.jsp in the URL text box and then click the Set URL button.

25. Select GET from the HTTP Method drop-down list.

26. Enter <html> as the Reply 200 Pattern and click Set Pattern.

27. Add a Real Server.

Configure the Virtual Service_1_5.png

a) Click the Add New button.

b) Enter the Real Server Address.

c) Enter the correct Port.

d) Click the Add This Real Server button.

Steps b) and c) use the IP Address and Port of the backend server.

The Forwarding method and the Weight values are set, by default. If required these settings may be altered.

3.3.2 Configure the Virtual Service with SSL Offloading for Oracle JD Edwards

This example configuration assumes that one Virtual Service and one Real Server are being set up. In a real situation, users may need to configure more.

To add and configure the Oracle JD Edwards with SSL Offloading Virtual Service, follow the steps below in the LoadMaster Web User Interface (WUI):

1. Add a Virtual Service.

Configure the Virtual Service_2.png

2. In the main menu, go to Virtual Services > Add New.

3. Enter a valid IP address in the Virtual Address text box.

4. Enter 443 as the Port.

5. Enter a recognizable Service Name, such as Oracle JD Edwards EnterpriseOne HTTPS.

6. Ensure tcp is selected as the Protocol.

7. Click Add this Virtual Service.

8. Add the Content Rule to the Virtual Service.

9. Expand the Advanced Properties section.

Configure the Virtual Service_2_1.png

10. Click the Show Header Rules button.

Configure the Virtual Service_2_2.png

11. From drop-down list in the Request Rules section of the HTTP header modification Rule Management screen, select the rule you created and click the Add button.

12. Click the Back button.

13. Configure the Standard Options section.

Configure the Virtual Service_2_3.png

14. Expand the Standard Options section.

15. Deselect the Transparency check box.

16. Select Active Cookie as the Persistence Mode.

17. Select 1 Hour as the Timeout value.

18. Enter EnterpriseOne-Cookie as the Cookie name and then click Set Cookie.

19. Select least connection as the Scheduling Method from the drop-down list.

20. Enter 1800 in the Idle Connection Timeout text box and click Set Idle Timeout.

21. Ensure Normal-Service is selected as the Quality of Service.

22. Configure the SSL Properties section.

Configure the Virtual Service_2_4.png

23. Expand the SSL Properties section.

24. Select the SSL Acceleration Enabled check box.

25. Select Support TLS Only check box.

26. Select No Client Certificates required from the Client Certificates drop-down list.

27. Expand the Real Servers section.

Configure the Virtual Service_1_4.png

28. Select HTTP Protocol Real Server Check Parameters drop-down list.

29. Enter /jde/index.jsp in the URL text box and then click the Set URL button.

30. Select GET from the HTTP Method drop-down list.

31. Enter <html> as the Reply 200 Pattern and click Set Pattern.

32. Add a Real Server.

Configure the Virtual Service_2_5.png

a) Click the Add New button.

b) Enter the Real Server Address.

c) Enter the correct Port.

d) Click the Add This Real Server button.

Steps b) and c) use the IP Address and Port of the backend server.

The Forwarding method and the Weight values are set, by default. If required these settings may be altered.

References

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

Virtual Services and Templates, Feature Description

Document History

 

Date

Change

Reason for Change

Version

Resp.

Sep 2015

Initial draft

First draft of document

1.0

LB

Oct 2015

Release updates

Updates for 7.1-30 release

2.0

LB

Dec 2015

Release updates

Updates for 7.1-32 release

3.0

LB

Jan 2016

Minor updates

Updated Copyright Notices

4.0

LB

Mar 2016

Release updates

Updates for 7.1-34 release

5.0

LB

Jan 2017

Minor updates

Enhancements made

6.0

LB

July 2017 Minor updates Enhancements made 7.0 CMC

 

 

Was this article helpful?

0 out of 0 found this helpful

Comments