1935421.1 914 E1 WebLogic12c Clustering-BSSV Fixed

JD Edwards EnterpriseOne 9.1.
4 Clustering
Best Practices with Oracle WebLogic Server
12.1.2 for the Business Services Server
O R A C L E W H IT E P A P E R | D EC E MB E R 2 0 1 4
Disclaimer
The following is intended to outline our general product direction. It 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 Oracle’s products remains at the sole
discretion of Oracle.
JD Edwards EnterpriseOne 9.1.4 Clustering Best Practices With Oracle WebLogic Server 12.1.2 for the Business Services Server
Table of Contents
Overview 1
WebLogic Definitions 2
About Clusters 2
Cluster and Domain Differences 2
Benefits of Clustering 3
Vertical and Horizontal WebLogic Clusters 3
WebLogic Administration Server and WebLogic Administration Console 3
Machines and Node Manager 3
Overview of the Install 4 vmserver44 4 vmserver4444 4
JD Edwards Instance details 4
Overview of a Vertical Cluster Setup 4
Setting Up a Vertical Cluster 5 Create the E1_914 WebLogic Domain 5 Start the
Administration Server 15
Create the Cluster 16
Overview of a Horizontal Cluster Setup 22
Setting Up a Horizontal Cluster 23
Load Balancing the Clustered Server 28
Installing Oracle HTTP Server 28
Configuring SSL 45
I |
Configuring SSL for WebLogic Managed Server 46
Configuring Oracle HTTP Server as a Client that Trusts the WebLogic Server 49
Setting Up HTTPS Proxy for Load Balancing 49
Setting Up OHS as Trusted Party for Business Services Servers 50
Test Business Services 51
II |
Overview
The purpose of this document is to provide all the necessary steps for JD Edwards EnterpriseOne
customers to setup Oracle WebLogic Server clusters. The clusters can then be used for deployment of
the JD Edwards EnterpriseOne business services application.
1 | JD Edwards EnterpriseOne 9.1.4 Clustering Best Practices With Oracle WebLogic Server 12.1.2 for the Business Services Server
WebLogic Definitions
The beginning of this paper discusses each part of a WebLogic Server used in the setup of the JD Edwards
EnterpriseOne clusters. For the complete WebLogic documentation, see:
http://docs.oracle.com/middleware/1212/wls/index.html.
About Clusters
A WebLogic Server cluster consists of multiple WebLogic Server instances running simultaneously and working
together to provide increased scalability and reliability. To clients, the cluster shows as a single WebLogic Server
instance. The server instances that constitute a cluster can run on the same machine or be located on different
machines. You can increase a cluster’s capacity by adding additional server instances to the cluster on an
existing machine, or you can add machines to the cluster to host the incremental server instances. Each server
instance in a cluster must run the same version of WebLogic Server.
Cluster and Domain Differences

A cluster is part of a particular WebLogic Server domain.
A domain is an interrelated set of WebLogic Server resources that are managed as a unit. A domain includes one
or more WebLogic Server instances, which can be clustered, non-clustered, or a combination of clustered and
non-clustered instances. A domain can include multiple clusters. A domain also contains the application
components deployed in the domain, and the resources and services required by those application components,
and the server instances in the domain.
In each domain, one WebLogic Server instance acts as the Administration Server—the server instance which
configures, manages, and monitors all other server instances and resources in the domain. Each Administration
Server manages one domain only. If a domain contains multiple clusters, each cluster in the domain has the same
Administration Server.
All server instances in a cluster must reside in the same domain; you cannot “split” a cluster over multiple
domains. Similarly, you cannot share a configured resource or subsystem between domains.
Clustered WebLogic Server instances behave similar to non-clustered instances, except that they provide failover
and load balancing. The process and tools used to configure clustered WebLogic Server instances are the same
as those used to configure non-clustered instances. However, to achieve the load balancing and failover benefits
that clustering enables, you must follow guidelines for cluster configuration.
You can follow the cluster configuration guidelines by two methods. One method is to use a hardware load
balancer to achieve load balancing and failover. The second method is to use the WebLogic Server functionality.
This paper discusses the steps required to:
» Achieve load balancing using only WebLogic tools, and not the load-balancing hardware.
» Install and configure Oracle HTTP Server.
For load balancing, you can use Oracle HTTP Server as a proxy server in front of WebLogic Clusters.
For details about WebLogic Server clustering, including the steps to implement clustering with load balancing
hardware, see the Oracle WebLogic Clustering Guide:
http://docs.oracle.com/middleware/1212/wls/INTRO/clustering.htm
Benefits of Clustering
A WebLogic Server cluster provides these benefits:
» Scalability: The capacity of an application deployed on a WebLogic Server cluster can be increased
dynamically. You can add server instances to a cluster without interruption of service—the application
continues to run without impacting clients and end users.
» High-Availability: In a WebLogic Server cluster, application processing can continue when a server instance
fails. You cluster application components by deploying them on multiple server instances in the cluster—so,
if a server instance on which a component is running fails, another server instance on which that
component is deployed can continue application processing.
Vertical and Horizontal WebLogic Clusters

A vertical cluster exists when two or more WebLogic Managed Servers on the same physical machine are
grouped together. Vertical clusters can help optimize machine resources as well as provide protection if another
Managed Server on the same machine is unavailable.
A horizontal cluster exists when two or more WebLogic Managed Servers on different physical machines are
grouped together. Horizontal clusters can help optimize machine and network resources, and also provide
failover protection if other cluster members are unavailable.
WebLogic Administration Server and WebLogic Administration Console

Administration Server is a special instance of WebLogic Server in each domain. Administration Server provides
a central point for managing a WebLogic Server domain.
Administration Console is a Web application hosted by Administration Server. You can use Administration
Console to manage and monitor an active domain, including:
» Configuring active domains
» Stopping and starting servers
» Monitoring server health and performance
» Monitoring application performance
» Viewing server logs
Machines and Node Manager

A machine in WebLogic is a logical representation of the physical machine that hosts a WebLogic Server
instance. To set up a vertical cluster, the Managed Servers in the cluster must be assigned to run on the same
machine as the Manager Server.
You use WebLogic Node Manager when you set up Managed Servers in a horizontal cluster configuration. Node
Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and
Managed Server instances from a remote location. A Node Manager process is not associated with a specific
WebLogic domain but with a machine. You can use the same Node Manager process to control server
instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the
Node Manager process. Node Manager must run on each computer that hosts WebLogic Server instances
(Administration Server or Managed Server) that you want to control with Node Manager.
Overview of the Install

For this paper, clustering the JD Edwards EnterpriseOne business services application with WebLogic Server
was accomplished using the following machines.
vmserver44
» Windows Server 2008 R2 64bit
» Server Manager Agent 9.1.4
» Oracle WebLogic Server 12.1.2
» Domain E1_914
» Administration Server
» Cluster C1
» Managed Server C1_VC1
» Managed Server C1_VC2
» Node Manager for machine vmserver44
» Oracle HTTP Server 12.1.2 (Used for proxy server in front of WebLogic Cluster. Installation and
configuration steps are listed below.)
» Server Manager Console 9.1.4
» Managed Instance for Oracle WebLogic
» Managed Instance for E1_C1_BSSV (Business Services Server deployment)
vmserver4444
» Windows Server 2008 R2 64bit

» Oracle WebLogic Server 12.1.2
» Domain E1_914
» Cluster C1
» Managed Server C1_HC1
» Node Manager for machine vmserver4444
JD Edwards Instance details

» JD Edwards Application Release 9.1 with Tools Release 9.1.4
Overview of a Vertical Cluster Setup

Assumptions
» Oracle WebLogic 12.1.2 64bit is installed on vmserver44.

Note: Oracle WebLogic Server is offered in several editions, each of which grants license to different
levels of functionality. For details about the different editions of Oracle WebLogic Server, see the Oracle
Fusion Middleware 12c Licensing Information Guide.
Note: The systems described in this document were configured using Oracle WebLogic Server Enterprise
Edition.
» Oracle JD Edwards Server Manager Console 9.1.4 is installed and running on vmserver44.
» Oracle JD Edwards Server Manager Agent 9.1.4 is installed and running on vmserver44.
» WebLogic Node Manager on vmserver44 is up and running.
» JD Edwards EnterpriseOne services are up and running to validate the business services server sign-on
with JD Edwards Security Server.
» The person implementing these steps has a thorough understanding of JD Edwards installation, including
Server Manager, and Oracle WebLogic Server 12c.
The vertical cluster setup consists of two Managed Servers running on the same machine. The following is an
overview of setting up a vertical cluster:
» Install Oracle WebLogic 12.1.2 64bit on machine vmserver44.
» Create domain E1_914 in WebLogic.
» Create machine vmserver44 in E191 domain.
» Create the cluster C1 with the Managed Servers C1_VC1.
» Deploy EnterpriseOne Business Services Server to the cluster using the package deploy application.
» Create Managed Server C1_VC2 and add to cluster C1.
» Edit Startup values for the Managed Servers.
» Configure all the business services settings for EnterpriseOne Business Services Server.
» Start the EnterpriseOne Business Services Server Instance.
» Set up HTTP Proxy for load balancing by performing either of the following actions:
» Create Managed Server using WebLogic HTTPClusterServlet.
» Install Oracle HTTP Server and configure proxy.
For this paper, WebLogic was installed on a Windows platform; therefore, all commands and screenshots shown
in this paper are from Windows.
Setting Up a Vertical Cluster

Create the E1_914 WebLogic Domain
1. Run the Configuration Wizard provided with the WebLogic Server (WLS) Tools to create a new
domain. This wizard can also be launched by running the command config.cmd available at
<WLS_HOME>\oracle_common\common\bin
2. Select the Create a new domain option, enter the domain name E1_914 in the Domain Location
field, and then click Next.
3. Select the first option Basic WebLogic Server Domain in Available Templates, and then click
Next.
4. Enter the name and password for the domain, and then click Next.
5. Select Production for Domain Mode, enter the Java Development Kit (JDK) path, and then click
Next. Note that only JDK 1.7 Update 25+ is supported.
6. Select Administration Server and Node Manager, and then click Next.
Note that you create the cluster, Managed Servers, and machine by using the Administration
Console. You can create the cluster by using the config.cmd program.
7. Change the listen port to an open port, and then click Next. In this example, the port is 7501.
8. Select Per Domain as the Node Manager Type, enter the Node Manager user name and
password, and then click Next.
9. Verify the configuration summary, and then click Create to create the domain.
10. When the configuration progress shows as 100%, click Next.
11. On the confirmation screen, note the URL for the Administration Console, (in this example, it is
http://vmserver44.us.oracle.com:7501/console), and then, click Finish.
WMSERVER44:
Start the Administration Server

1. Change directories to the domain location: cd
<WLS_HOME>/user_projects/domains/E1_914
2. Start the server:
startWebLogic.cmd
3. Enter the user name and password when required.
Create the Cluster

1. Use log-in credentials to log in to the Administration Console URL:
http://vmserver44.us.oracle.com:7501/console/login/LoginForm.jsp
The system displays the Administration Console home page
vmserver44
2. Click Environment, Clusters, Lock & Edit, and then click New.
Change the name to C1. Retain Messaging Mode as Unicast.
Note: Clusters use messaging for sharing sessions, load balancing and failover, Java Message
Service (JMS), and for other information shared between cluster members. Clusters can use
either Unicast or Multicast messaging. Multicast is a simple broadcast technology that enables
multiple applications to subscribe to a given IP address and port number and listen for messages,
but requires hardware configuration and support. Unicast does not have these requirements and
is recommended for new clusters.
a. Keep all other options as the default and click OK. Then, click Activate Changes. The
system displays a summary of clusters.
b. After a cluster is created, edit the cluster and enter the cluster address. The cluster
address should be the IP address of the machine that the cluster is created on.
10.139.111.11
3. Create the machine.

a. Click Environment, Machines, Lock & Edit, and then click New.
b. Change the machine name to vmserver44 and OS to Other, and then click Next.
c. Change the Listen Address to vmserver44.
Note: This step is important for remotely managing Managed Servers existing in
WebLogic domains that span multiple machines.
vmserver44
d. Click Next.
vmserver44
e. Select the type as SSL. For the node manager machine name, enter Listen Address.
For the Node Manager Port, enter Listen Port. Check to ensure that Node Manager is
reachable.
f. Click Finish, and on the next screen, click Activate Changes. The system displays the
Summary of Machines page.
4. Create the Vertical Cluster Managed Server.

a. Click Environment, Clusters, Lock & Edit, and then click New.
b. Change the name to C1_VC1, change the Server listen port to 7503, select Yes,
make this server a member of an existing cluster, select C1, and then click Finish.
c. Click C1_VC1 and change the machine to vmserver44.
d. Select SSL Listen Port Enabled. Enter the value for a unique port (7504 in this
example).
e. Click Save, and then Activate Changes.
Note: You can access this screen by using different methods in the Administration
Console.
One method is:
Click Environment, C1, the Servers tab, and then click the server name.
Another method is:
Click Environment, Servers, and then click the server name.
5. Deploy EnterpriseOne Business Services Server application.
a. Ensure that the Server Manager agent is started on vmserver44.
b. In Server Manager Console on machine vmserver44, register Oracle WebLogic Server
12c as a managed instance. The screen below shows the instance name as
WLS_1212, the install location as C:\oracle\Middleware\Oracle_Home, and uses the
same user name and password as when the domain E1_914 was created.
c. When you click the new managed instance, the system displays the WebLogic domain
details. Note the E1_91 domain with the one Managed Server C1_VC1 in the cluster
C1. The Administration Server is also in the E1_91 domain and it is shown as running
because the startWebLogic.cmd command was issued after the domain was created.
d. In Server Manager Console, create a new managed instance on the managed home
for vmserver44, for the EnterpriseOne business services application.
i. Create a new managed instance called E1_BSSV_C1 under the managed home
for vmserver44 by using the j2ee server for C1_VC1, port 7503, and the software
component loaded in the previous step. Click Continue.
ii. Enter the required information for the JD Edwards instance and click Continue
then confirm the action by clicking Create Instance.
iii. Deploy the EnterpriseOne Business Services Server application to this instance
using the package deploy application.
6. Create Managed Server C1_VC2 and add to cluster C1.
a. In the WebLogic Administration Console, click Environment, Servers, Lock & Edit,
and then click New.
b. Change the name to C1_VC2, change the Server listen port to 7505, select Yes,
make this server a member of an existing cluster, select C1, and then click Finish.
c. Click the server C1_VC2 and change the machine to vmserver44.
d. Select SSL Listen Port Enabled. Provide a unique port (7506 in this example).
e. Click Save, and then click Activate Changes.
The system displays details about the C1_VC2 settings:
7. Edit startup values for the Managed Servers.

The startup values for the servers need to be changed to uniquely identify each cluster member
for Server Manager. The unique identification is used to separate the cluster members for both log
separation and runtime metrics displayed within the Server Manager Console.
a. In WebLogic Administration Console, click Environment, Servers, C1_VC1, and then
click Lock & Edit.
b. Click the Server Start tab, and add the following in the Arguments box:
-Xms768m –Xmx1280m -DcloneId=C1_VC1
Note: The –DcloneId is case-sensitive. If there are any errors or special characters in the
arguments, the server will not start. If the server does not start, it is recommended that
you delete the values for startup and retype them in the Arguments box. The argument
already consists of the value:
Ddefault_path=C:/jde_agent/targets/E1_BSSV_C1/config
where C:/jde_agent is the agent install location.
c. Click Save, and then click Activate Changes.
d. Repeat the same steps for C1_VC2, using:
–Ddefault_path=C:/jde_agent/targets/E1_BSSV_C1/config -Xms768m –Xmx1280m
DcloneId=C1_VC2
8. Configure the Business Services Server.
a. Using the Server Manager console, edit your configuration items for the EnterpriseOne
Business Services Server E1_BSSV_C1 managed instance. Ensure that all of the
correct information is entered for Network Settings, JDBJ Database Configuration, and
so on, and save the changes.
The current configuration is connecting to an Oracle Database; therefore, you must
enter the correct database connect strings in the tnsnames.ora section of the JDBJ
Database Configuration. Also, the fully qualified path to the tnsnames.ora file must be
removed. This step is necessary for the jdbj.ini file to find the proper location to the
tnsnames.ora file after the synchronization of the configuration files.
When the configurations are saved within Server Manager, the files are stored in:
C:/jde_agent/targets/E1_BSSV_C1/config
b. Click the Managed Instance Name E1_BSSV_C1 in Server Manager, and then click the
Synchronize Configuration button. The synchronization process takes a few minutes to
complete. The configuration files are copied to a location within the Server Manager
Agent folders, as well as a location within the WebLogic folders.
9. Start the EnterpriseOne Business Services Server Instance.
Overview of a Horizontal Cluster Setup

The vertical cluster is now set up with two Managed Servers running on the same physical machine. The Setting
Up a Horizontal Cluster section discusses the steps required to add another Managed Server to the same
cluster, with the new Managed Server running on a separate physical machine. When this process is complete,
a horizontal cluster is set up.
Assumptions
» Oracle WebLogic 12.1.2 64bit is installed on vmserverd4444. WebLogic must be installed in the same
directory structure on each machine. This is mandatory, and if there is any deviation in the install location
between the two machines then the clustered Managed Server will not work on vmserverd4444.
Note: Oracle WebLogic Server is offered in several editions, each of which grants license to different levels
of functionality. For details about various editions, see the Oracle Fusion Middleware 11g Licensing
Information Guide. The systems described in this document were configured using Oracle WebLogic Server
Enterprise Edition.
» Oracle WebLogic 12.1.2 is installed and running on vmserver44. The Administration Console is running on
port 7501. The two vertical Managed Servers discussed in the previous section are installed.
» Oracle JD Edwards Server Manager Console 9.1.4 is installed on vmserver44
» Oracle JD Edwards Server Manager Agent 9.1.4 is installed on vmserver44
» WebLogic Node Manager on vmserver44 is up and running
» WebLogic Node Manager on vmserverd4444 is up and running
» JD Edwards EnterpriseOne services are up and running in order to validate the Business Services Server
sign-on with JD Edwards Security Server
» E1_BSSV_C1 managed instance is stopped in Server Manager
» The user implementing these steps has a thorough understanding of JD Edwards installation, including
Server Manager, and WebLogic 12c.
Here is an overview of setting up a horizontal cluster:
» Install Oracle WebLogic 12.1.2 64bit on machine vmserverd4444. WebLogic must be installed in the same
directory structure as installed on vmserver44. This is mandatory, and if there is any deviation in the install
location between the two machines then the clustered Managed Server will not work on vmserverd4444.
Note: The Node Manager must be started on the horizontal cluster machine.
» Create machine vmserverd4444 in E1_914 domain using Administration Console.
» Create Managed Server C1_HC1 and add to the cluster C1.
» Edit Startup values for the Managed Server C1_HC1.
» Create the domain E1_914 on vmserverd4444.
» Start the EnterpriseOne Business Services Server Instance.
» Setup HTTP Proxy for load balancing.
Setting Up a Horizontal Cluster
When setting up a horizontal cluster, it is mandatory that the same release of Oracle WebLogic is installed on
both physical machines involved in the cluster. Also, the machines where WebLogic is installed should share the
same hardware and operating system characteristics. You can spread the cluster across heterogeneous
machines; however, it is recommended that all machines be similar.
1. Create a machine vmserverd4444 in the E1_914 domain using Administration Console.
The following step is important because the machines in WebLogic are used to direct the
Administration Console to the Node Manager process on the appropriate machine, so that the cluster
and cluster members are appropriately administered.
a. Log in to WebLogic Administration Console running on vmserver44.
b. Click Environment, Machines, Lock & Edit, and then click New.
c. Change the machine name to vmserverd4444 and the OS to Other, and then click OK.
d. Click vmserverd4444, click the Node Manager tab, change the value in the Listen Address
field to vmserverd4444, and provide the Node Manager port on vmserverd4444. This step is
important for remotely managing Managed Servers existing in WebLogic domains that span
multiple machines.
Ensure that the type is SSL in this configuration.
vmserverd4444
2. Create Managed Server C1_HC1, and add to the cluster C1.

a. In WebLogic Administration Console, click Environment, Servers, Lock & Edit, and then
click New.
b. Change the name to C1_HC1, change the Server listen port to 7507, select Yes, and make
this server a member of an existing cluster, select C1, and then click Finish.
c. Click the server C1_HC1 and select the machine vmserverd4444.
d. Select SSL Listen Port Enabled. Provide a unique port (7507 in this example).
3. Edit Startup values for the Managed Server C1_HC1.

a. In WebLogic Administration Console, click Environment, Servers, C1_HC1, and then
click Lock & Edit.
b. Click the Server Start tab, and enter the following in the Arguments box:
–Ddefault_path=C:/jde_agent/targets/E1_BSSV_C1/config -Xms768m –Xmx1280m -
DcloneId=C1_HC1
The –DcloneId is case-sensitive. If there are any errors or special characters in the
Arguments, the server will not start. If the server does not start, it is recommended that
you delete the values for the startup and retype them in the Arguments box.
C:/jde_agent is the SM Agent install location.
4. Create the domain E1_914 on vmserverd4444.
After the steps to create the cluster are complete on vmserver44, the domain has to be distributed to
vmserverd4444. Use the pack and unpack commands to accomplish the distribution.
a. On vmserver44, change directories to: <WLS_HOME>\wlserver\common\bin folder cd
C:\oracle\Middleware\Oracle_Home\wlserver\common\bin
b. Pack the domain into a jar file. There are no line breaks in the following command.
Create the user_templates folder if it does not exist on vmserver44.
pack.cmd -managed=true -
domain=C:\oracle\Middleware\Oracle_Home\user_projects\domains\E1_914
template=C:\oracle\Middleware\Oracle_Home\user_templates\E1_914.jar
template_name="E1_914"
c. Copy the C:\oracle\Middleware\Oracle_Home\user_templates\E1_914.jar file to

vmserverd4444 machine to the same location:
C:\oracle\Middleware\Oracle_Home\user_templates.
Create the user_templates folder if it does not exist on vmserverd4444.
d. Unpack the jar file on dnshravindvm.
Change the directory to common/bin in <WLS_HOME>\wlserver\common\bin.
Unpack the E1_914.jar file. There are no line breaks in the following command:
unpack.cmd -domain=
C:\oracle\Middleware\Oracle_Home\user_projects\domains\E1_914 -template=
C:\oracle\Middleware\Oracle_Home\user_templates\E1_914.jar file
e. After unpacking, ensure that SBFLoginModule_JAR.jar is available at:

C:\oracle\Middleware\Oracle_Home\user_projects\domains\E1_914\lib
Also ensure that an E1BSSVAuthenicatorV2.jar is available at:
C:\oracle\Middleware\Oracle_Home\wlserver\lib\mbeantypes folder of the horizontal
machine.
If they are not available at these locations, please copy them from the primary server
machine.
5. Copy the agent install folder from the primary machine to the horizontal machine. Ensure that the
agent in both of the machines resides in the same folder location. If you are unable to copy the entire
agent install folder, at least copy the business services instance target folder. In the horizontal
machine, verify the INI files for the Business Services Server instance has the correct file path
reference for a UNIX install.
6. Start the EnterpriseOne Business Services Server managed Instance using the Server Manager
Console.
7. Notes about Server Manager and Horizontal Cluster Members.
Runtime Metrics
Server Manager Console receives instance information and runtime metrics from the Server Manager
Agents running on each of the managed home machines. For the vertical cluster members, all metrics
are transferred successfully because of an agent running on vmserver44.
However, no Server Manager agent is installed on vmserverd4444 (the machine containing the
horizontal cluster member), which means that no data is reported to the Server Manager Console.
To correct this, copy the agent.properties file from vmserver44 to vmserverd4444. The
agent.properties file is located in <Server Manager Home>/config on vmserver44. The file contains the
name of the Server Manager Console machine, and Management Server JMX port, which is the port
that the Manager Server listens to for incoming connections.
By copying this file to the machine hosting the horizontal cluster member, we send data to the server
manager on the port listed; therefore, the information is displayed in the Server Manager console.
The file must be in the same physical location on each of the two machines, and it must be owned by
the same user account that runs WebLogic.
Action
» Create the file structure on your horizontal machine and copy the properties file to that location.
After the horizontal server is installed, Server Manager displays this:
server102
Logs
The logs from Managed Server running on the horizontal cluster machines are not brought into the
Server Manager console for viewing. The functionality of displaying logs is performed by the Server
Manager Agent, and because no additional agent is installed on the horizontal cluster machine, no
logs will be available in the Server Manager Console. To view these logs, log in to the machine as the
user running WebLogic, change directories to the log location (as specified by jdelog.properties file),
and open in an editor. The functionality to view horizontal cluster member logs will be included in a
future release of Server Manager.
The screen below shows that only the Vertical Member logs are displayed.
server102
JDBC Drivers
Proper Java Database Connectivity (JDBC) drivers must be installed on all physical machines that host
Managed Servers in the cluster. The recommended method of installing JDBC drivers is using the
Server Manager Console. Currently, this method requires a Server Manager Agent running on the
target machine for successful JDBC file copy.
Similar to logs, the JDBC drivers will not be copied to machines that host horizontal cluster members
because there is no Server Manager Agent running on that machine.
The workaround is to manually copy the required JDBC file to the horizontal cluster machine. The file
must be identical to the file on the vertical cluster machine, owned by the user running WebLogic, and
placed in the same folder structure as exists on the vertical cluster machine.
The proper folder to install the JDBC file is:
<Server Manager Home>/targets/<WebLogic Managed Instance>/config/jdbc/<WLS Domain

Name>/<WLS Managed Server Name>/
Action
» Create the above folder on the horizontal cluster machine, then copy the JDBC file to that folder.
Load Balancing the Clustered Server

You can load-balance the connections to the WebLogic clustered servers by various methods.
One method involves using the WebLogic-supplied proxy plug-in HTTPClusterServlet and creating an additional
WebLogic Managed Server to proxy the connections. For the details about this method, see the: WebLogic
Cluster Guide:
http://docs.oracle.com/middleware/1212/wls/CLUST/setup.htm#i685302
You can load-balance the connections by using Oracle HTTP Server in front of the WebLogic Server. A specific
module in Oracle HTTP Server called mod_wl_ohs allows requests to be proxied from Oracle HTTP Server to
Oracle WebLogic Server. For details, see:
http://docs.oracle.com/middleware/1212/core/EMPRC/ohs_mod_weblogic_proc.htm
The Oracle HTTP Server can be installed on the same server as WebLogic or a separate server altogether,
allowing more flexibility in your overall architecture.
Installing Oracle HTTP Server

The examples in this document assume that you are using a Windows based platform. If you are installing the
Oracle HTTP Server on a Unix machine, some of the file names and directories might be slightly different. When
installing on Unix, the Oracle web tier components should be installed using a non-root user.
For details, see http://docs.oracle.com/middleware/1212/webtier/WTINS/index.html.

1. Download the “Oracle Fusion Middleware 12c Oracle HTTP Server (12.1.2.0)” package that is
appropriate for your platform from the edelivery web site (https://edelivery.oracle.com). For more
information, see the JD Edwards EnterpriseOne Certifications.
2. Extract the downloaded file to a temporary directory on the machine that you are targeting for
installation.
3. Run the .exe program to start the installation. The first screen you see is the welcome screen. Click
Next to begin the installation.
4. On this screen, perform the following actions:
a. Click View to view an existing directory into which one or more
Oracle products have already been installed.
To install the product in a new directory, type the full path of your new directory in the Oracle
Home field. The installer will create the specified directory for you.
Note: Provide the Oracle Home folder based on availability. Oracle_Home used here is a
default folder.
b. Click Next.
5. Determine the type of installation you want to perform and which products and features you want to
install.
The options you see on this screen will differ depending on the product you are installing. For specific
details, see your product installation guide.
Click Next.
6. Ensure that specific operating system prerequisites have been completed. Click Next.
7. If you want to register your installation, enter your e-mail address and your My Oracle Support
password. If you want to decline registration, clear the I wish to receive security updates via My
Oracle Support check box.
Click Next.
username
8. The Installation Summary screen contains a list of the feature sets you selected for installation. Click
Install.
9. This screen shows the progress of the installation. When the progress bar reaches 100%, the
installation is complete.
Click Next.
10. The system then displays the Installation Complete screen and provides a summary of the products
and features that are now installed.
Click Finish.
11. Create a domain using the Configuration Wizard:

If you had selected Installation Type as Standalone HTTP Server Install during installation, then you
need to run the Configuration Wizard to create a domain. Configuration Wizard can also be invoked
by running the command < ORACLE_ HOME>\oracle_common\common\bin\config.cmd. Otherwise,
if you had selected Installation Type as Collocated HTTP Server, the HTTP Server is installed and
managed through the WLS Console.
Enter the domain location, and then click Next.
12. Select the template Oracle HTTP Server (Standalone), and then click Next.
13. A JDK location is selected by default. You can provide an external JDK location. Click Next.
14. Enter the system component name, select OHS as the component type, and then click Next.
15. If required, change the Admin Port, Listen Port, and Secure Socket Layer (SSL) Listen Port values on
this screen.
Enter the system component name, select OHS as the Component Type, and then click Next.
16. Select Per Domain as the Node Manager Type, enter the node manager user name and password,
and then click Next.
17. The system displays the Configuration Summary page.
Click Create.
18. This screen shows the progress of the installation.
When the progress bar reaches 100%, click Next.
19. The Success page indicates that the domain creation is successful. Click Finish.
Configuring SSL
SSL secures communication by providing message encryption, integrity, and authentication. The SSL standard
allows the involved components (such as browsers and HTTP servers) to negotiate encryption, authentication,
and integrity.
» Encryption provides confidentiality by allowing only the intended recipient to read the message.
» Integrity ensures that a message sent by a client is received intact by the server, unaltered.
» Authentication enables the server and client to check that the other party is who it claims to be.
Oracle WebLogic Server supports two types of keystores for keys and certificates:
» Java Keystore format (JKS): JKS-based keystore and truststore Oracle wallet
» Oracle wallet
Java components and applications use the JKS keystore to store keys and certificates. Configuring SSL for
these components requires setting up and using JKS keystores.
Other components use the Oracle wallet as their storage mechanism. An Oracle wallet is a container that stores
your credentials, such as certificates, trusted certificates, certificate requests, and private keys. You can store
Oracle wallets on the file system or in LDAP directories, such as Oracle Internet Directory. Oracle wallets can be
auto-login or password-protected wallets.
Oracle HTTP Server uses Oracle wallet.
Configuring SSL for these components requires setting up and using Oracle wallets.
There are various lines of communication that you can secure with SSL. One consideration is that the
computation required to encrypt and decrypt HTML pages will affect performance. The examples below walk
through configuring SSL for two different communication lines by building on the basic configuration discussed
above, and also demonstrate the use of both a JKS keystore and an Oracle wallet.
If you elect to secure the communication channel from the browser to the Oracle HTTP Server, you must also
secure the communications between the Oracle HTTP Server and the Oracle WebLogic Server applications.
This consists of two steps: Configuring SSL for your WebLogic Managed Server, and then configuring Oracle
HTTP Server as a client that trusts the WebLogic Server.
Configuring SSL for WebLogic Managed Server

1. For this example, the java “keytool” utility is used to create a custom keystore that will contain the
server identity. These commands assume the Java 1.7 version of “keytool” is in your PATH. An
example command to generate a custom key pair is below (the values in blue will change based on
your site):
keytool -genkeypair -v -keyalg RSA -dname "cn=vmserver44,dc=us,dc=oracle,dc=com" -alias

enterpriseone -keypass admin123 -keystore enterpriseone.jks -storepass admin123 -validity 365
Note: This certification expires after one year, and you will need to regenerate the certificate for the
server to start.
2. Export the certificate containing the public key that will be imported into the client’s trust store. In this
case, the client is the Oracle HTTP Server, with the server being the Oracle WebLogic Managed
Server:
keytool -exportcert -v -alias enterpriseone -keystore enterpriseone.jks -storepass admin123 -rfc -file
enterpriseone.cer
3. Enable SSL Listen Port.
a. In the WebLogic Administration Console, click Environment, Servers, C1_VC1, and then
click Lock & Edit.
b. Select SSL Listen Port Enabled. Provide a unique port (7504 in this example).
The system displays the page to configure general features of the server:
vmserver44
Repeat this step (assigning SSL port) for all of the servers in the cluster. Port 7506 and 7508 are
assigned to C1_VC1 and C1_HC1 respectively.
4. Enable WebLogic Plug-In.
WebLogic plug-in needs to be enabled to receive requests from a proxy plug-in.
a. In the WebLogic Administration Console, click Environment, Clusters, C1, and then click
Lock & Edit.
b. Go to the Advanced section.
c. Set WebLogic Plug-In Enabled to yes.
d. Click Save, and then click Activate Changes.
The system displays the page to define the general settings for the cluster:
5. Select the Keystores sub-tab.
a. From the Keystores drop-down list, select Custom Identity and Java Standard Trust
b. In the Identity section, in the Custom Identity Keystore field, enter the path and the file name
of the identity keystore that was created in Step 1. Enter JKS for the Custom Identity
Keystore Type.
c. Fill in the keystore passphrase with the password that was used in Step 1.
d. Click Save at the bottom of the screen to apply your changes.
On this screen, notice the path and file name of Java Standard Trust Keystore at the top of
the Trust section. This is the file containing the recognized Certificate Authorities that
WebLogic will recognize. Use this file in the next step.
e. From the command line, run the keytool command to import the self-signed certificate that
was created in Step 2 above into the Java trust keystore (changeit is the default password for
the Java trust keystore):
keytool -importcert -trustcacerts -alias enterpriseone -file C:\enterpriseone.cer –keystore
C:\Oracle\Middleware\Oracle_Home\oracle_common\jdk\jre\security\cacerts
-storepass changeit
f. In the WebLogic console, select the SSL sub-tab.
Fill in the Private Key Alias and Private Key Passphrase for the certificate that was created in Step 2
above. Click Save to apply your changes.
Configuring Oracle HTTP Server as a Client that Trusts the WebLogic Server
After setting up the WebLogic Server to use SSL, configure the Oracle HTTP Server to recognize the WebLogic
Server as a valid Certificate Authority.
Following are the steps to complete the SSL communication loop:

1. Copy the file containing the public key certificate to the machine that is running your Oracle HTTP
Server. In this example, this is the enterpriseone.cer file that was created in Step 2 of the previous
section. This certificate must be imported into the Oracle wallet that the Oracle HTTP Server is using.
2. Import this certificate into the Oracle HTTP Server wallet. Use the orapki utility, located in the bin
directory under your oracle_common directory. The example below assumes that the orapki utility is
already in your PATH, and you have changed the local directory to be the default wallet directory:
(<ORACLE_HOME>\user_projects\domains\<DOMAIN_NAME>\config\fmwconfig\components\OHS\in
s tances\<OHS_INSTANCE_NAME\keystores)
orapki wallet add -wallet . -trusted_cert -cert C:\enterpriseone.cer –auto_login_only
Setting Up HTTPS Proxy for Load Balancing

Next configure the Oracle HTTP Server installation to communicate with an existing EnterpriseOne Business
Services Server installed on a WebLogic cluster. The following example shows how to configure the default
HTTPS port (7778) in OHS and dispatch a request to the EnterpriseOne Business Services client HTTPS port
running on WebLogic cluster.
For Vertical Cluster Install (Assume that Business Services Server instance is created on a cluster with two
servers on a vertical node running on https port 7504 and 7506):
Listen 7778
<VirtualHost *:7778>
<Location /jde>
SetHandler weblogic-handler
WebLogicCluster vmserver44:7503,vmserver44:7505
</Location>
<IfModule ossl_module>
SSLEngine on
SSLVerifyClient None
SSLProtocol nzos_Version_1_0 nzos_Version_3_0
SSLCipherSuite
SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_RSA_WITH_DES_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_
S
HA
SSLCRLCheck Off
SSLWallet
"${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_N
A
ME}/keystores/default"
</IfModule>
</VirtualHost>
For Horizontal Cluster Install (Assume that the Business Services Server instance is created on a cluster with
three servers on a horizontal node running on https port 7504, 7506 and 7508):
Listen 7778
<VirtualHost *:7778>
<Location /jde>
SetHandler weblogic-handler
WebLogicCluster vmserver44:7503,vmserver44:7505,vmserverd4444:7507
</Location>
<IfModule ossl_module>
SSLEngine on
SSLVerifyClient None
SSLProtocol nzos_Version_1_0 nzos_Version_3_0
SSLCipherSuite
SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,
SSL_RSA_WITH_DES_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_
S
HA
SSLCRLCheck Off
SSLWallet
"${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_N
A
ME}/keystores/default"
</IfModule>
</VirtualHost>
NOTE: The ports used (7503, 7505 and 7507) in this configuration are the HTTP ports of the respective WLS
Managed Servers and not the HTTPS port on which the Business Services Server is installed.
Setting Up OHS as Trusted Party for Business Services Servers

To make OHS a trusted party for the Business Services Server, follow these steps:
1. To install and export the certificate:
(Access a WSDL URL with OHS port from Firefox, and export the certificate)
a. Open Internet Explorer and enter this URL:
https://HTTP_SERVER:PORT/DV910/RI_AddressBookManager
b. Click the Continue to this website (not recommended) link.
The system displays the following message:
Welcome to the {tap://oracle.e1.bssv.JPR01000/}RI_AddressBookManager home page
Test page
WSDL page
In the address bar, the Certificate Error button is displayed next to the Refresh button.
c. Click the Certificate Error button and select View Certificate.
d. Click the Install Certificate button.
e. Continue through the wizard until you receive the “Import was successful” message, and
then click Ok.
f. In Internet Explorer, select the Tools menu, Internet Options, Content tab, and then the
Certificates button.
g. Click the Intermediate Certification Authorities or Other People tab, and look for the
Business Services Server machine name in the Issue To column.
h. Click the Export button.
i. Select the DER encoded binary X.509 (.CER) option.
j. Browse to the location you want to export this file and enter this name for the file:
myCertificate.cer
2. Import the above exported certificate into the cacerts file of the JDK used by the Business Services
Servers.
JDK_HOME>/keytool -importcert -trustcacerts -alias <HOST_MACHINE_NAME> -file myCertificate.cer
keystore cacerts -storepass changeit
Note: Replace <JDK_HOME> and <HOST_MACHINE_NAME> with appropriate values.
a. Restart OHS and the Business Services Server Instance.
3. Start the Business Services Server.
a. Start Node Manager by running the command startNodeManager.bat available at
<ORACLE_ HOME>\user_projects\domains\<DOMAIN_NAME>\bin.
b. Start HTTP Server by running the command startComponent.bat available at < ORACLE_
HOME>\user_projects\domains\<DOMAIN_NAME>\bin.
Pass the http server component name to the command:
startComponent ohs1
c. Start the Business Services Server.
You should now be able to connect to the EnterpriseOne application through Oracle HTTP Server
using SSL.
Test Business Services

Testing of the OHS server is similar to testing the individual Managed Server instances. Testing and validation
can be done using the SoapUI tool with the exception that a new URL is used to test the OHS server.
https://vmserver44:7778/DV910/AddressBookManager?WSDL
Successfully testing Address Book will validate the OHS server configuration with the WebLogic Server Cluster.
C O N N EC T W I T H U S
blogs.oracle.com/oracle
facebook.com/oracle
twitter.com/oracle
oracle.com
Oracle Corporation, World Headquarters Worldwide Inquiries

500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
Copyright © 2014, Oracle and/or its affiliates. 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 and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron
logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
1214
JD Edwards EnterpriseOne 9.1.4 Clustering Best Practices with Oracle WebLogic Server 12.1.2
December 2014

1935421.1 914 E1 WebLogic12c Clustering-BSSV Fixed

Uploaded by

Copyright:

Available Formats

1935421.1 914 E1 WebLogic12c Clustering-BSSV Fixed

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1935421.1 914 E1 WebLogic12c Clustering-BSSV Fixed

Uploaded by

Copyright:

Available Formats

JD Edwards EnterpriseOne 9.1.

Cluster and Domain Differences 2

Vertical and Horizontal WebLogic Clusters 3

WebLogic Administration Server and WebLogic Administration Console 3

Machines and Node Manager 3

Overview of the Install 4 vmserver44 4 vmserver4444 4

JD Edwards Instance details 4

Overview of a Vertical Cluster Setup 4

Create the Cluster 16

Overview of a Horizontal Cluster Setup 22

Setting Up a Horizontal Cluster 23

Load Balancing the Clustered Server 28

Installing Oracle HTTP Server 28

Setting Up HTTPS Proxy for Load Balancing 49

Setting Up OHS as Trusted Party for Business Services Servers 50

Test Business Services 51

Cluster and Domain Differences

Vertical and Horizontal WebLogic Clusters

WebLogic Administration Server and WebLogic Administration Console

Machines and Node Manager

Overview of the Install

» Windows Server 2008 R2 64bit

JD Edwards Instance details

Overview of a Vertical Cluster Setup

» Oracle WebLogic 12.1.2 64bit is installed on vmserver44.

Setting Up a Vertical Cluster

Start the Administration Server

Create the Cluster

3. Create the machine.

4. Create the Vertical Cluster Managed Server.

7. Edit startup values for the Managed Servers.

Overview of a Horizontal Cluster Setup

2. Create Managed Server C1_HC1, and add to the cluster C1.

3. Edit Startup values for the Managed Server C1_HC1.

c. Copy the C:\oracle\Middleware\Oracle_Home\user_templates\E1_914.jar file to

e. After unpacking, ensure that SBFLoginModule_JAR.jar is available at:

The proper folder to install the JDBC file is:

<Server Manager Home>/targets/<WebLogic Managed Instance>/config/jdbc/<WLS Domain

Load Balancing the Clustered Server

Installing Oracle HTTP Server

For details, see http://docs.oracle.com/middleware/1212/webtier/WTINS/index.html.

11. Create a domain using the Configuration Wizard:

18. This screen shows the progress of the installation.

Configuring SSL for WebLogic Managed Server

keytool -genkeypair -v -keyalg RSA -dname "cn=vmserver44,dc=us,dc=oracle,dc=com" -alias

5. Select the Keystores sub-tab.

f. In the WebLogic console, select the SSL sub-tab.

Following are the steps to complete the SSL communication loop:

Setting Up HTTPS Proxy for Load Balancing

Setting Up OHS as Trusted Party for Business Services Servers

Test Business Services

Oracle Corporation, World Headquarters Worldwide Inquiries

You might also like