Deployment Guide Version 1.0

Deploying the BIG-IP LTM with Oracle JD Edwards EnterpriseOne

What’s inside: 2 Prerequisites and configuration notes 2 Configuration example 3 Preparation Worksheet 4 Configuring the BIG-IP for HTTP traffic (no SSL offload) 5 Configuring the BIG-IP for HTTPS traffic (SSL offload) 6 Configuring optional iRules 7 Document Revision History

Welcome to the F5 deployment guide for Oracle JD Edwards EnterpriseOne and BIG-IP 10.2.1. This guide shows administrators how to configure the BIG-IP Local Traffic Manager (LTM) for directing traffic, ensuring application availability, improving performance and providing a flexible layer of security for JD Edwards EnterpriseOne deployments.

Why F5 The BIG-IP LTM provides high availability, load balancing, enhanced performance, simple scalability and high operational resiliency for Oracle JD Edwards EnterpriseOne Application deployments. In a JD Edwards One environment, the BIG-IP LTM provides intelligent traffic management and high availability by monitoring and managing connections to the WebLogic services. In addition, the built-in performance optimization capabilities of the LTM provide faster operations to facilitate a better end-user experience. The LTM also keeps persistence records for connections to always be directed to the same server for a specified period of time, to ensure that the workflow in the JD Edwards environment is fully preserved. For more information on Oracle JD Edwards EnterpriseOne, see http://www.oracle.com/us/products/applications/jd-edwards-enterpriseone/index.html For more information on the F5 BIG-IP LTM, see http://www.f5.com/products/big-ip/product-modules/local-traffic-manager.html To provide feedback on this deployment guide or other F5 solution documents, contact us at [email protected] Products and versions tested

Document Version 1.0

Product

Version

BIG-IP LTM

10.2.1

JD Edwards EnterpriseOne

9.0/8.98.4

Oracle WebLogic Server

10.3.2

Important: M  ake sure you are using the most recent version of this deployment guide, available at http://www.f5.com/pdf/deployment-guides/oracle-jd-edwards-dg.pdf.

DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Prerequisites and configuration notes The following are general prerequisites and configuration notes for this guide: hh You must have administrative access to the BIG-IP web-based Configuration utility. hh Y  ou must have administrative level privileges to the JD Edwards EnterpriseOne servers, for editing configurations and stopping/starting services. hh O  ptional: You must have a valid SSL certificate and key if you going to offload SSL to the BIG-IP LTM.

Configuration example In this deployment guide, we provide guidance on configuring the BIG-IP LTM for intelligent traffic management and high availability for JD Edwards EnterpriseOne environments. The following is a simple, logical diagram of our configuration. Clients

BIG-IP LTM

JD Edwards EnterpriseOne

Figure 1: Logical configuration example

2

DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Preparation Worksheet Before beginning the configuration, it is helpful to gather some information, such as IP addresses and certificate/key information. This worksheets contains the information that is helpful to have in advance. You might find it useful to print the table and then enter the information. We provide a blank worksheet, and then one completed with our examples. ÂÂ Note: A  lthough we show space for nine pool members, you may have more or fewer members in your pool

IP Addresses Virtual server IP address:

Service Port:

1 2

Pool Members WebLogic Server IPs:Port 1: 2: 3: 4: 5: 6: 7: 8: 9:

Health monitor URI required for accessing the JD Edwards deployment (/jde/index.jsp by default):

Certificate and Key? Only required if offloading SSL onto the BIG-IP 2. Certificate:

User name for a JD Edwards account 1: Key: Associated password:

We strongly recommend creating a user account specifically for this monitor If offloading SSL, you must have imported a valid certificate and key on to the BIG-IP system before beginning the configuration. See the Online help or product documentation for more information

IP Addresses Virtual server IP address: 192.0.2.101 Service Port: 443

Pool Members WebLogic Server IPs:Port 1: 10.10.10.101:7003 2: 10.10.10.102:7003 3: 10.10.10.103:7003 4: 10.10.10.104:7003 5: 10.10.10.105:7003 6: 10.10.10.106:7003 7: 8: 9:

3

Health monitor URI required for accessing the JD Edwards deployment (/jde/index.jsp by default): /jde/index.jsp User name for a JD Edwards account: JDE Associated password: password

Certificate and Key? Only required if offloading SSL onto the BIG-IP. Certificate: JDE-SSL Key: JDE-SSL

DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Configuring the BIG-IP LTM for HTTP traffic (no SSL offload) Use the following table for guidance on configuring the BIG-IP LTM for JD Edwards EnterpriseOne using HTTP with no SSL offload. This table contains any non-default setting you should configure as a part of this deployment. Unless otherwise specified, settings not mentioned in the table can be configured as applicable for your configuration. Give each object a unique name. We recommend using names that are prefaced by “JDE-” such as JDE-monitor. LL Tip

For specific instructions on configuring individual objects, see the online help or product documentation. Also see Configuring optional iRules on page 6. BIG-IP object

Health Monitor

Pool

Non-default settings/Notes Type

HTTP

Interval

60

Timeout

180

Send String

GET /jde/index.jsp \r\n 1

Receive String



User Name

Type the user name, if appropriate. We use JDE

Password

Associated password, if appropriate. We use password

Health monitor

Add health monitor above

Slow Ramp Time

120 (must select Advanced for this option to appear)

Load Balancing Method

Least Connections (node) recommended

Address

WebLogic server IP address

Service Port

7003 (default) Repeat Address and Port for all members)

HTTP

Parent Profile

http

Parent Profile

tcp-wan-optimized

Idle Timeout

1800

Parent Profile

tcp-lan-optimized

Idle Timeout

1800

Persistence (Cookie)2

Persistence Type

Cookie

Persistence (Source Address)

Persistence Type

Source Address Affinity

OneConnect

Parent Profile

oneconnect

Destination Address

IP address (clients use to access JD Edwards via BIG-IP)

Service Port

80

Profiles

Add select each profile you created above from the appropriate list. Source Address Affinity is the Fallback Persistence method.

SNAT Pool

Automap (recommended; with more than 65,000 users, use SNAT Pool)

iRules

Optional. See Configuring optional iRules on page 6

Default Pool

Select the pool you created above

TCP WAN

Profiles

TCP LAN

Virtual Server

1

If you changed from the default JD Edwards URI, replace /jde/index.jsp with that URI. See Using an iRule to persist WebLogic connections on JSessionID on page 6. If using this iRule, the Persistence Type is Universal, you must enable Match Across Services, and then select the iRule.

2 

4

DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Configuring the BIG-IP LTM for HTTPS traffic (SSL offload) ÂÂ Important: For SSL offload, we

Use the following table for guidance on configuring the BIG-IP LTM to offload SSL for JD Edwards EnterpriseOne. This table contains any non-default setting you should configure as a part of this deployment. Unless otherwise specified, settings not mentioned in the table can be configured as applicable for your configuration.

assume you have already obtained a valid SSL certificate/key pair and imported it onto the BIG-IP system. For more information on certificates and keys, see the BIG-IP documentation.

Give each object a unique name. We recommend using names prefaced by “JDE-”. For specific instructions on configuring individual objects, see the online help or product documentation. Also see Configuring optional iRules on page 6.

BIG-IP object

Health Monitor

Pool

Non-default settings/Notes Type

HTTP

Interval

60

Timeout

180

Send String

GET /jde/index.jsp \r\n 1

Receive String



User Name

Appropriate user name. We use JDE

Password

Associated password. We use password

Health monitor

Add health monitor above

Slow Ramp Time

120 (must select Advanced for this option to appear)

Load Balancing Method

Least Connections (node) recommended

Address

WebLogic server IP address

Service Port

7003 (default) Repeat Address and Port for all members)

HTTP

TCP WAN

TCP LAN

Profiles

Client SSL Persistence (Cookie)

2

Persistence (Source Address)

Virtual Server

1

2

Parent Profile

http

Request Header Insert

WL-Proxy-SSL:true

Parent Profile

tcp-wan-optimized

Idle Timeout

1800

Parent Profile

tcp-lan-optimized

Idle Timeout

1800

Parent Profile

clientssl

Certificate/Key

Select the Certificate and Key you imported

Persistence Type

Cookie

Persistence Type

Source Address Affinity oneconnect

OneConnect

Parent Profile

Destination Address

IP address (clients use to access JD Edwards via BIG-IP)

Service Port

443

Profiles

Add select each profile you created above from the appropriate list. Source Address Affinity is the Fallback Persistence method.

SNAT Pool

Automap (recommended; with more than 65,000 users, use SNAT Pool)

iRules

Optional. See Configuring optional iRules on page 6

Default Pool

Select the pool you created above

If you changed from the default JD Edwards URI, replace /jde/index.jsp with that URI. See Using an iRule to persist WebLogic connections on JSessionID on page 6. If using this iRule, the Persistence Type is Universal, you must enable Match Across Services, and then select the iRule.

2 

5

DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Configuring optional iRules The following two iRules are optional, but can be helpful in certain scenarios.

Using an iRule to mask the root context When accessing the EnterpriseOne application, you may want to mask the root context, and provide a simpler way for users to access the application. When the user types the URI to access the EnterpriseOne application, the following BIG-IP iRule automatically appends the context root to the base URI. For example, if you type http://jdedwards.example.com, the iRule would send http://jdewards.example.com/jde/EiMenu.maf to the server. Create an iRule on the BIG-IP LTM using the following code (omitting the line numbers). 1 2 3 4 5

when HTTP_REQUEST { if {([HTTP::uri] == "/") } { HTTP::uri "/jde/E1Menu.maf" } }

Use the following procedure to add the iRule to the virtual server. To add the iRule to the virtual server 1.

On the Main tab, expand Local Traffic and then click Virtual servers.

2.

From the Virtual Server list, select the name of the virtual server you created for JD Edwards earlier in this guide.

3.

On the Menu bar, click Resources.

4.

In the iRules section, click Manage.

5.

From the Available list, select the iRule you just created and then click the Add (<<) button.

6.

Click the Finished button.

Using an iRule to persist WebLogic connections on JSessionID Most WebLogic servers keep track of a particular user session using a JSessionID as either a cookie or as a parameter appended to a URI. In some cases, you may want to persist these connections through the BIG-IP using the WebLogic JSessionID instead of the recommended Cookie persistence profile. The iRule is available on DevCentral: http://devcentral.f5.com/wiki/default.aspx/iRules/Weblogic_JSessionID_Persistence.html As mentioned in the article, you must use a Universal persistence method, enable Match Across Services, and then add the iRule to the persistence profile (and not the virtual server).

6

7 DEPLOYMENT GUIDE JD Edwards EnterpriseOne

Document Revision History Version 1.0

F5 Networks, Inc. 401 Elliott Avenue West, Seattle, WA 98119

Description New deployment guide

888-882-4447

www.f5.com

F5 Networks, Inc. Corporate Headquarters

F5 Networks Asia-Pacific

F5 Networks Ltd. Europe/Middle-East/Africa

F5 Networks Japan K.K.

[email protected]

[email protected]

[email protected]

[email protected]

© 2011 F5 Networks, Inc. All rights reserved. F5, F5 Networks, the F5 logo, BIG-IP, FirePass, and iControl are trademarks or registered trademarks of F5 Networks, Inc. in the U.S. and in certain other countries.

Deploying the BIG-IP LTM with JD Edwards ... - F5 Networks

In a JD Edwards One environment, the BIG-IP LTM provides intelligent traffic ... Virtual server IP address: Service Port: WebLogic Server IPs:Port. 1: 2: 3: 4: 5: 6:.

946KB Sizes 49 Downloads 416 Views

Recommend Documents

Deploying the BIG-IP LTM with Microsoft Remote ... - F5 Networks
Aug 16, 2013 - Configuring the DNS settings. 28 ..... Name must correspond to the fully-qualified DNS name that is associated with the Client SSL profile that you create on the BIG- ...... This monitor checks the CPU, memory, and disk usage of the no

Deploying the BIG-IP LTM with Citrix XenDesktop - F5 Networks
To import the script using Linux/Unix/MacOS systems. 1. Download the script: http://devcentral.f5.com/wiki/default.aspx/tmsh/CitrixXenDesktopMonitor.html. 2.

Deploying the BIG-IP LTM with Microsoft Remote ... - F5 Networks
Aug 16, 2013 - Remote Desktop Services, one for the Remote Desktop Gateway Servers, .... and precludes exposing required services in the DMZ network.

Deploying the BIG-IP LTM with multiple BIG-IP ... - F5 Networks
h You must be running BIG-IP version 10.x. ... The LTM then intelligently directs the request to the best available web application server. You can host both the internal and external virtual servers on the same BIG-IP LTM, or you may.

Deploying the BIG-IP LTM with the VMware Zimbra ... - F5 Networks
find the table does not contain enough information for you to configure an individual .... In the Domain box, type the domain name you want the monitor to check.

Deploying the BIG-IP LTM with IBM InfoSphere Guardium - F5 Networks
Oct 22, 2012 - To achieve the levels of uptime demanded by advanced solutions, F5 ... h Reduced total cost of ownership through easier configuration and management, ... IBM Guardium see: http://www-01.ibm.com/software/data/guardium/.

Deploying the BIG-IP LTM and APM v11 with Citrix ... - F5 Networks
Jul 24, 2012 - h You can optionally configure the BIG-IP APM for two factor .... ://support.f5.com/kb/en-us/solutions/public/10000/200/sol10240.html for more.

Deploying F5 with SAP ERP Central Component - F5 Networks
Jun 11, 2013 - F5 Analytics (also known as Application Visibility and Reporting or AVR) is ...... first install and configure the necessary server software for these.

Deploying the BIG-IP LTM with Oracle Database Firewall - F5 Networks
Sep 19, 2012 - managing connections to the Database Firewall Proxy services running in .... 1. On the Main tab, expand Network, and then click Interfaces. 2.