Embed Size (px)
Citation preview
Configuring JD Edwards EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
An Oracle JD Edwards EnterpriseOne White Paper
February 2011
EnterpriseOne Servers and F5 BIG-IP Page i
PURPOSE STATEMENT
This document provides considerations when reviewing system performance relative to
your JD Edwards EnterpriseOne system Many factors can influence performance and your results may differ depending on many different variables
This document is intended for information purposes only and may not be incorporated into any contract It is not a commitment to deliver any material code or functionality and should not be relied upon in making purchasing decisions The development release and timing of any features or functionality described for Oraclersquos products remains at the sole discretion of Oracle Updates and enhancements are provided in accordance with Oraclersquos Technical Support Policies at
wwworaclecomsupportcollateraloracle-technical-support-policiespdf
EnterpriseOne Servers and F5 BIG-IP Page ii
Configuring JD Edwards EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview 1 Creating the Health Monitor 2 Creating the Pool 4 Creating the Profiles 7
Creating an HTTP Profile 7 Creating the TCP profiles 8 Creating the LAN optimized TCP profile 8 Creating the WAN optimized TCP profile 9 Creating persistence profile 10 Creating a OneConnect profile 10
Creating the Virtual Servers 11 EnterpriseOne HTML server with Oracle WebLogic Server 15 EnterpriseOne WSRP Solution with F5 BIG-IP 17 Appendix A iRules 20 Appendix B Additional Resources 22
1
Configuring EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview This document contains step-by-step procedures on how to configure the BIG-IP Local Traffic Manager (LTM) for directing traffic to the Oracle WebLogic Server with Oracle JD Edwards EnterpriseOne Products There are two sections to this document The first section is for BIG-IP LTM with EnterpriseOne HTML servers and the other section is for BIG-IP LTM with Oracle WebCenter running with EnterpriseOne Portlets
Before you Begin
EnterpriseOne HTML server is installed and configured on Oracle WebLogic Server
Oracle WebCenter is installed and WebCenter Spaces is started
You must have your F5 BIG-IP Server installed and configured This document covers only the configuration between the F5 BIG-IP and EnterpriseOne products
Configuration Example
PTOVMENT2
E1 Logic Server
8984
PTOVMDB2
E1 Database 11gR2
8984
dnhpbl21
WebLogic Server
103x
dnhpbl33
WebLogic Server
103x
dnhpbl29
WebCenter
1111x
dendell16
WebCenter
1111x
Users F5 BIG-IP
denverf5a
F5 BIG-IP
denverf5b
2
For this example we are using two F5 BIG-IP LTMs One F5 BIG-IP (denverf5a) is configured in front of two EnterpriseOne HTML servers and the other (denverf5b) is in front of two WebCenter servers Users will access EnterpriseOne Portlets thru the F5 BIG-IP URL It will load balance between the Oracle WebCenter and EnterpriseOne HTML servers
Note Depends on the load configuration the second F5 BIG-IP is optional You can configure all requests using only one F5 BIG-IP server
Product Versions Product and versions tested for this deployment guide
Products Tested Version Tested
F5 BIG-IP LTM BIG-IP 930 Build 1785
EnterpriseOne 90 8984
Oracle WebLogic Server 1032
Oracle WebCenter 11112
To configure the BIG-IP LTM system for WebLogic Server you need to complete the following tasks
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
Creating the Health Monitor
The first step is to set up a health monitor for the EnterpriseOne HTML Servers This monitor is used for health checking the application server F5 BIG-IP will check the health of all servers if one of the application servers is off-line it will route requests to other servers until that server is back up again You also can manually disable one of the servers from the BIG-IP This allows system administrator to perform maintenance to the server
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
EnterpriseOne Servers and F5 BIG-IP Page i
PURPOSE STATEMENT
This document provides considerations when reviewing system performance relative to
your JD Edwards EnterpriseOne system Many factors can influence performance and your results may differ depending on many different variables
This document is intended for information purposes only and may not be incorporated into any contract It is not a commitment to deliver any material code or functionality and should not be relied upon in making purchasing decisions The development release and timing of any features or functionality described for Oraclersquos products remains at the sole discretion of Oracle Updates and enhancements are provided in accordance with Oraclersquos Technical Support Policies at
wwworaclecomsupportcollateraloracle-technical-support-policiespdf
EnterpriseOne Servers and F5 BIG-IP Page ii
Configuring JD Edwards EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview 1 Creating the Health Monitor 2 Creating the Pool 4 Creating the Profiles 7
Creating an HTTP Profile 7 Creating the TCP profiles 8 Creating the LAN optimized TCP profile 8 Creating the WAN optimized TCP profile 9 Creating persistence profile 10 Creating a OneConnect profile 10
Creating the Virtual Servers 11 EnterpriseOne HTML server with Oracle WebLogic Server 15 EnterpriseOne WSRP Solution with F5 BIG-IP 17 Appendix A iRules 20 Appendix B Additional Resources 22
1
Configuring EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview This document contains step-by-step procedures on how to configure the BIG-IP Local Traffic Manager (LTM) for directing traffic to the Oracle WebLogic Server with Oracle JD Edwards EnterpriseOne Products There are two sections to this document The first section is for BIG-IP LTM with EnterpriseOne HTML servers and the other section is for BIG-IP LTM with Oracle WebCenter running with EnterpriseOne Portlets
Before you Begin
EnterpriseOne HTML server is installed and configured on Oracle WebLogic Server
Oracle WebCenter is installed and WebCenter Spaces is started
You must have your F5 BIG-IP Server installed and configured This document covers only the configuration between the F5 BIG-IP and EnterpriseOne products
Configuration Example
PTOVMENT2
E1 Logic Server
8984
PTOVMDB2
E1 Database 11gR2
8984
dnhpbl21
WebLogic Server
103x
dnhpbl33
WebLogic Server
103x
dnhpbl29
WebCenter
1111x
dendell16
WebCenter
1111x
Users F5 BIG-IP
denverf5a
F5 BIG-IP
denverf5b
2
For this example we are using two F5 BIG-IP LTMs One F5 BIG-IP (denverf5a) is configured in front of two EnterpriseOne HTML servers and the other (denverf5b) is in front of two WebCenter servers Users will access EnterpriseOne Portlets thru the F5 BIG-IP URL It will load balance between the Oracle WebCenter and EnterpriseOne HTML servers
Note Depends on the load configuration the second F5 BIG-IP is optional You can configure all requests using only one F5 BIG-IP server
Product Versions Product and versions tested for this deployment guide
Products Tested Version Tested
F5 BIG-IP LTM BIG-IP 930 Build 1785
EnterpriseOne 90 8984
Oracle WebLogic Server 1032
Oracle WebCenter 11112
To configure the BIG-IP LTM system for WebLogic Server you need to complete the following tasks
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
Creating the Health Monitor
The first step is to set up a health monitor for the EnterpriseOne HTML Servers This monitor is used for health checking the application server F5 BIG-IP will check the health of all servers if one of the application servers is off-line it will route requests to other servers until that server is back up again You also can manually disable one of the servers from the BIG-IP This allows system administrator to perform maintenance to the server
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
EnterpriseOne Servers and F5 BIG-IP Page ii
Configuring JD Edwards EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview 1 Creating the Health Monitor 2 Creating the Pool 4 Creating the Profiles 7
Creating an HTTP Profile 7 Creating the TCP profiles 8 Creating the LAN optimized TCP profile 8 Creating the WAN optimized TCP profile 9 Creating persistence profile 10 Creating a OneConnect profile 10
Creating the Virtual Servers 11 EnterpriseOne HTML server with Oracle WebLogic Server 15 EnterpriseOne WSRP Solution with F5 BIG-IP 17 Appendix A iRules 20 Appendix B Additional Resources 22
1
Configuring EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview This document contains step-by-step procedures on how to configure the BIG-IP Local Traffic Manager (LTM) for directing traffic to the Oracle WebLogic Server with Oracle JD Edwards EnterpriseOne Products There are two sections to this document The first section is for BIG-IP LTM with EnterpriseOne HTML servers and the other section is for BIG-IP LTM with Oracle WebCenter running with EnterpriseOne Portlets
Before you Begin
EnterpriseOne HTML server is installed and configured on Oracle WebLogic Server
Oracle WebCenter is installed and WebCenter Spaces is started
You must have your F5 BIG-IP Server installed and configured This document covers only the configuration between the F5 BIG-IP and EnterpriseOne products
Configuration Example
PTOVMENT2
E1 Logic Server
8984
PTOVMDB2
E1 Database 11gR2
8984
dnhpbl21
WebLogic Server
103x
dnhpbl33
WebLogic Server
103x
dnhpbl29
WebCenter
1111x
dendell16
WebCenter
1111x
Users F5 BIG-IP
denverf5a
F5 BIG-IP
denverf5b
2
For this example we are using two F5 BIG-IP LTMs One F5 BIG-IP (denverf5a) is configured in front of two EnterpriseOne HTML servers and the other (denverf5b) is in front of two WebCenter servers Users will access EnterpriseOne Portlets thru the F5 BIG-IP URL It will load balance between the Oracle WebCenter and EnterpriseOne HTML servers
Note Depends on the load configuration the second F5 BIG-IP is optional You can configure all requests using only one F5 BIG-IP server
Product Versions Product and versions tested for this deployment guide
Products Tested Version Tested
F5 BIG-IP LTM BIG-IP 930 Build 1785
EnterpriseOne 90 8984
Oracle WebLogic Server 1032
Oracle WebCenter 11112
To configure the BIG-IP LTM system for WebLogic Server you need to complete the following tasks
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
Creating the Health Monitor
The first step is to set up a health monitor for the EnterpriseOne HTML Servers This monitor is used for health checking the application server F5 BIG-IP will check the health of all servers if one of the application servers is off-line it will route requests to other servers until that server is back up again You also can manually disable one of the servers from the BIG-IP This allows system administrator to perform maintenance to the server
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
1
Configuring EnterpriseOne Servers on Oracle Fusion Middleware with F5 BIG-IP
Overview This document contains step-by-step procedures on how to configure the BIG-IP Local Traffic Manager (LTM) for directing traffic to the Oracle WebLogic Server with Oracle JD Edwards EnterpriseOne Products There are two sections to this document The first section is for BIG-IP LTM with EnterpriseOne HTML servers and the other section is for BIG-IP LTM with Oracle WebCenter running with EnterpriseOne Portlets
Before you Begin
EnterpriseOne HTML server is installed and configured on Oracle WebLogic Server
Oracle WebCenter is installed and WebCenter Spaces is started
You must have your F5 BIG-IP Server installed and configured This document covers only the configuration between the F5 BIG-IP and EnterpriseOne products
Configuration Example
PTOVMENT2
E1 Logic Server
8984
PTOVMDB2
E1 Database 11gR2
8984
dnhpbl21
WebLogic Server
103x
dnhpbl33
WebLogic Server
103x
dnhpbl29
WebCenter
1111x
dendell16
WebCenter
1111x
Users F5 BIG-IP
denverf5a
F5 BIG-IP
denverf5b
2
For this example we are using two F5 BIG-IP LTMs One F5 BIG-IP (denverf5a) is configured in front of two EnterpriseOne HTML servers and the other (denverf5b) is in front of two WebCenter servers Users will access EnterpriseOne Portlets thru the F5 BIG-IP URL It will load balance between the Oracle WebCenter and EnterpriseOne HTML servers
Note Depends on the load configuration the second F5 BIG-IP is optional You can configure all requests using only one F5 BIG-IP server
Product Versions Product and versions tested for this deployment guide
Products Tested Version Tested
F5 BIG-IP LTM BIG-IP 930 Build 1785
EnterpriseOne 90 8984
Oracle WebLogic Server 1032
Oracle WebCenter 11112
To configure the BIG-IP LTM system for WebLogic Server you need to complete the following tasks
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
Creating the Health Monitor
The first step is to set up a health monitor for the EnterpriseOne HTML Servers This monitor is used for health checking the application server F5 BIG-IP will check the health of all servers if one of the application servers is off-line it will route requests to other servers until that server is back up again You also can manually disable one of the servers from the BIG-IP This allows system administrator to perform maintenance to the server
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
2
For this example we are using two F5 BIG-IP LTMs One F5 BIG-IP (denverf5a) is configured in front of two EnterpriseOne HTML servers and the other (denverf5b) is in front of two WebCenter servers Users will access EnterpriseOne Portlets thru the F5 BIG-IP URL It will load balance between the Oracle WebCenter and EnterpriseOne HTML servers
Note Depends on the load configuration the second F5 BIG-IP is optional You can configure all requests using only one F5 BIG-IP server
Product Versions Product and versions tested for this deployment guide
Products Tested Version Tested
F5 BIG-IP LTM BIG-IP 930 Build 1785
EnterpriseOne 90 8984
Oracle WebLogic Server 1032
Oracle WebCenter 11112
To configure the BIG-IP LTM system for WebLogic Server you need to complete the following tasks
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
Creating the Health Monitor
The first step is to set up a health monitor for the EnterpriseOne HTML Servers This monitor is used for health checking the application server F5 BIG-IP will check the health of all servers if one of the application servers is off-line it will route requests to other servers until that server is back up again You also can manually disable one of the servers from the BIG-IP This allows system administrator to perform maintenance to the server
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
3
To configure a health monitor
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Monitors
3 Click the Create button The New Monitor screen opens
4 In the Name box type a name for the Monitor
In our example we type JDEMonitor
5 From the Type list select HTTP 6 Enter the Alias Port number this is the port number that you want to monitor
This normally is the EnterpriseOne HTML port
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
4
7 In the Configuration section in the Interval and Timeout boxes type an Interval and Timeout We recommend at least a 13 +1 ratio between the
interval and the timeout In our example we use an Interval of 30 and a
Timeout of 91
8 In the Send String and Receive String sections you can add a Send String and Receive Rule specific to the device being checked In our example we used the EnterpriseOne index page to monitor the
heartbeats of the EnterpriseOne HTML server or you can create your own
page
9 Click the Finished button
Creating the Pool
The next step is to define a load balancing pool for the EnterpriseOne HTML Servers A BIG-IP pool is a set of devices grouped together to receive traffic according to a load balancing method This pool uses the monitor you just created
To create a pool
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
5
1 Log into the F5 BIG-IP console
2 On the Main tab expand Local Traffic and then click Pools
3 In the upper right portion of the screen click the Create button
4 From the Configuration list select Advanced
5 In the Name box type a name for your pool
In our example we use JDE-WLS-Pool
6 In the Health Monitors section select the name of the monitor you created in the
Creating the health monitor section and click the Add (ltlt) button In our example
we select JDEMonitor
7 Leave the Slow Ramp Time to the default value
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
6
8 From the Load Balancing Method list choose your preferred load balancing method (different load balancing methods may yield optimal results for a particular network)
In our example we select Round Robin method
Note It depends on your server configuration the ldquoLeast Connections (member)rdquo method will work well if the servers are in different CPU power or performance Also
change the Slow Ramp Time from the previous step to 120 seconds if this method is used
9 For this pool we leave the Priority Group Activation Disabled
10 In the New Members section make sure the New Address option button is selected
11 In the Address box add the IP address of first WebLogic server to the pool
In our example we type 10139190108
12 In the Service Port box type7003
13 Click the Add button to add the member to the list 14 Repeat steps 10-12 for each server you want to add to the pool
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
7
In our example we repeat these steps once for the remaining server
1013919078
15 Click the Finished button
Creating the Profiles
A profile is an object that contains user-configurable settings for controlling the behavior of a particular type of network traffic such as HTTP connections Using profiles enhances your control over managing network traffic and makes traffic-management tasks easier and more efficient Although it is possible to use the default profiles we strongly recommend you create new profiles based on the default parent profiles even if you do not change any of the settings initially Creating new profiles allows you to easily modify the profile settings specific to this deployment and ensures you do not accidentally overwrite the default profile
Creating an HTTP Profile
The first new profile we create is an HTTP profile The HTTP profile contains numerous configuration options for how the BIG-IP LTM system handles HTTP traffic
To create a new HTTP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this profile In our example we type JDE-HTTP
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
8
4 From the Parent Profile list select http
5 You may leave the default values for other parameters
6 Click the Finished button
Creating the TCP profiles
The next profiles we create are the TCP profiles If most of the EnterpriseOne HTML users are accessing the devices via a Local Area Network we recommend using the
tcp-lan-optimized (for server-side TCP connections) parent profile If the majority of the users are accessing the system from remote or home offices we recommend using
an additional TCP profile called tcp-wan-optimized (for client side TCP connections)
Creating the LAN optimized TCP profile
Next we configure the LAN optimized profile Remember if you are not using version 94 or do not want to use this optimized profile you can choose the default TCP parent profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-LAN
5 From the Parent Profile list select tcp-lan-optimized
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
9
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the WAN optimized TCP profile
Now we configure a WAN optimized profile
To create a new TCP profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Protocol menu click tcp
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-WAN
5 From the Parent Profile list select tcp-wan-optimized
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
10
Creating persistence profile
The next profile we create is a Persistence profile We recommend using persistence for Oracle WebLogic Servers although the type of persistence depends on your configuration In our example use cookie persistence (HTTP cookie insert)
To create a new cookie persistence profile based on the default profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar click Persistence
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-Cookie
5 From the Persistence Type list select Cookie 6 Modify any of the settings as applicable for your network In our example we leave
the settings at their default levels
7 Click the Finished button
Creating a OneConnect profile
The next profile we create is a OneConnect profile With OneConnect enabled client requests can utilize existing server-side connections thus reducing the number of server-side connections that a server must open to service those requests This can
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
11
provide significant performance improvements for WebLogic implementations For more information on OneConnect see the BIG-IP LTM documentation In our example we leave all the options at their default settings You can configure these options as appropriate for your network
To create a new OneConnect profile
1 On the Main tab expand Local Traffic and then click Profiles
2 On the Menu bar from the Other menu click OneConnect
3 In the upper right portion of the screen click the Create button
4 In the Name box type a name for this profile In our example we type JDE-
oneconnect
5 From the Parent Profile list ensure that oneconnect is selected
6 Modify any of the other settings as applicable for your network In our example we leave the settings at their default levels
7 Click the Finished button
Creating the Virtual Servers
Next we configure a virtual server that references the profiles and pool you created in the preceding procedures
To create the virtual server
1 On the Main tab expand Local Traffic and then click VirtualServers
2 In the upper right portion of the screen click the Create button
3 In the Name box type a name for this virtual server In our example we type JDE-
Server
4 In the Destination section select the Host option button
5 In the Address box type the IP address of this virtual server (the IP address on the
F5 BIG-IP) In our example we use 10139190161
6 In the Service Port box type 80
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
12
7 From the Configuration list select Advanced
8 Leave the Type list at the default setting Standard
9 From the Protocol Profile (Client) list select the profile you created in ldquoCreating the
LAN optimized TCP profile sectionrdquo In our example we select JDE-WAN
10 From the Protocol Profile (Server) list select the profile you created in Creating
the LAN optimized TCP profile In our example we select JDE-LAN
11 From the OneConnect Profile list select the profile you created in ldquoCreating an
OneConnect profilerdquo Section In our example we select JDE-oneconnect
12 From the HTTP Profile list select the profile you created in ldquoCreating an HTTP
profilerdquo In our example we select JDE-HTTP
13 In the Resources section from the Default Pool list select the pool you created in
the Creating the pool section In our example we select JDE-WLS-Pool
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
13
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
14
14 From the Default Persistence Profile list select the persistence profile you created
in the Creating persistence profile section In our example we select JDE-Cookie
15 Click the Finished button
16 Verify the Load Balancing parameters are correctly set Select Edit from the Virtual Host page
17 Ensure the Fallback Persistence Profile is set to ldquononerdquo otherwise the load balancing might not work correctly
18 Click the Update button if yoursquove made any changes
19 Reset the membersrsquo statistics before starting a test
20 Select all the members and click Reset
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
15
EnterpriseOne HTML server with Oracle WebLogic Server 1 Since you are running EnterpriseOne HTML server on Oracle WebLogic Server
there are no additional configurations needed
2 Launch a browser and test your F5 configuration
httpdenverf5amlabjdedwardscom80jdeE1Menumaf
Ensure the server name remains using your F5 BIG-IP
3 Review the statistics from the F5 BIG-IP
4 Also you can verify the user count from Server Manager
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
16
5 Open a new browser and launch the EnterpriseOne HTML server using the F5 URL
6 Review the statistics again now the requests went to the other server
7 Review the user count from Server Manager again
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
17
EnterpriseOne WSRP Solution with F5 BIG-IP Once you have EnterpriseOne HTML server running with the F5 BIG-IP then the next step is to configure EnterpriseOne Portlets on Oracle WebCenter Spaces In order to have the F5 BIG-IP to route the WSRP requests successfully you need to modify the EnterpriseOne wsdl file prior to register the WSRP producer
Changing the endpoint address in EnterpriseOne wsdl file 1 Change directory to mw_homeuser_projectsdomainsltyour
domaingtserversltyour servergtstageltyour instancegtappwebclientwarwsdl
2 Open the WSRP_v1_Servicewsdl file for edit
3 Replace the original server and port with your F5 BIG-IP name (Fully Qualified Domain Name) and port
4 Save the file
Register the EnterpriseOne WSRP Producer 1 Open the WebCenter Enterprise Manager Console
2 Navigate to Service Configuration
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
18
3 Select ldquoPortlet Producersrdquo to view or add producer
4 Select ldquoAddrdquo
5 Enter a Connection Name and select WSRP Producer type
6 Enter the WSDL URL httpf5serverFQDNportjdewsdlWSRP_v1_Servicewsdl
Note Ensure to use a Fully Qualified Domain Name with your server
7 Increase the default timeout from 30 to 300 seconds (To prevent network timeout)
8 Click OK to register the producer
9 The next step is to create a page and add portlet to WebCenter Follow the ldquo898 E1Tools Portal Guide for Oracle WebCenter- Doc ID 12709191rdquo to complete this task You may want to create a ldquoGroup Spacerdquo in WebCenter prior to creating a portal page
10 After your portal page has been created connect to Oracle WebCenter Spaces httphost8888webcenter (This is the actual WebCenter host name)
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
19
11 Repeat the above steps for your second Oracle WebCenter Server
12 Once you have verified that all WebCenter Spaces are functioning correctly and then the final step is to create the second F5 BIG-IP for these WebCenter Servers
13 You can follow the similar steps of creating the first BIG-IP in this document to configure the second F5 BIG-IP
bull Creating the health monitor bull Creating the pool bull Creating profiles bull Creating the virtual server
14 Access EnterpriseOne Portlets thru the second F5 BIG-IP (httpdenverf5bwebcenter or use this link to directly access the EnterpriseOne Group page httpdenverf5bwebcenterspacesEnterpriseOne)
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
20
Appendix A iRules
An iRule is a powerful and flexible feature of BIG-IP devices based on F5rsquos exclusive TMOS architecture iRules provide you with unprecedented control to directly manipulate and manage any IP application traffic iRules utilizes an easy to learn scripting syntax and enables you to customize how you intercept inspect transform and direct inbound or outbound application traffic
Creating an URL masking
You can create an iRules within F5 BIG-IP to mask the context root of the EnterpriseOne URL
1 Select ldquoCreaterdquo from the iRules
2 Enter the Definition
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
21
when HTTP_REQUEST if [HTTPuri] == HTTPuri jdeE1Menumaf
3 Add your iRule to your Virtual Server
4 Select your iRule and move it the Enabled column
5 Click Finished 6 Now Access EnterpriseOne URL without the context root (jdeE1Menumaf)
httpdenverf5amlabjdedwardscom
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
22
Appendix B Additional Resources
Additional documentation for JD Edwards EnterpriseOne products
JD Edwards EnterpriseOne 8983 Configuration with Oracle HTTP Server (Doc
ID 11803931)
WebLogic 1032 AppServer Clustering (Doc ID 11000201)
Installing Oracle Fusion Middleware WebCenter 11g with JD Edwards
EnterpriseOne (Doc ID 11000761)
JD Edwards EnterpriseOne Tools 898 Update 3 Oracle WebLogic Server 11g
(Doc ID 10865771)
JD Edwards EnterpriseOne Tools 898 Update 4 WSRP Portlet Producer
Running on Oracle WebLogic Server (Doc ID 12703521)
Additional Resources from F5 BIG-IP
F5 BIG-IP Product Page httpwwwf5comproductsbig-ip
Web-Based Training for F5 BIG-IP httpwwwf5comservicesglobal-trainingweb-based-training
F5 BIG-IP and Oracle Fusion Middleware httpwwwf5comsolutionsapplicationsoraclemiddleware
F5 BIG-IP and Oracle Applications httpwwwf5comsolutionsapplicationsoracle
F5 BIG-IP and Oracle Fusion Middleware Identity Management 11gR1 httpwwwf5compdfdeployment-guidesoracle-identity-management-big-ip-dgpdf
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
23
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores CA 94065
USA
Worldwide Inquiries
Phone +16505067000
Fax +16505067200
oraclecom
Copyright copy 2006 Oracle All rights reserved
This document is provided for information purposes only and the
contents hereof are subject to change without notice
This document is not warranted to be error-free nor subject to any
other warranties or conditions whether expressed orally or implied
in law including implied warranties and conditions of merchantability
or fitness for a particular purpose We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document This document
may not be reproduced or transmitted in any form or by any means
electronic or mechanical for any purpose without our prior written permission
Oracle JD Edwards PeopleSoft and Retek are registered trademarks of
Oracle Corporation andor its affiliates Other names may be trademarks
of their respective owners
This document is for informational purposes only and may not be incorporated
into a contract or agreement
