Oracle WebLogic Server Deployment Guide
Oracle WebLogic Server Deployment Guide
WebLogic Server
Version 1.1.0
Table of Contents
1. About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Loadbalancer.org Appliances Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Software Versions Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Loadbalancer.org Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Oracle WebLogic Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Oracle WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Load Balancing Oracle WebLogic Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Persistence (aka Server Affinity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.2. Virtual Service (VIP) Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.3. Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.4. TLS/SSL Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Deployment Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
7. Configuring Oracle WebLogic Server for Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Loadbalancer.org Appliance – the Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Virtual Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.2. Initial Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.3. Accessing the WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Main Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.4. Appliance Software Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Determining the Current Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Checking for Updates using Online Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Using Offline Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.5. Ports Used by the Appliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.6. HA Clustered Pair Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Appliance Configuration for Oracle WebLogic Server – Using Layer 7 SNAT Mode. . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Configuring the Virtual Service (VIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.2. Defining the Real Servers (RIPs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.3. Setting Up the TLS/SSL Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Uploading the Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Creating the TLS/SSL Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.4. Finalizing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10. Testing & Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Using the Load Balanced Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.2. Using System Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
11. Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
12. Further Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
13. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
13.1. Configuring HA - Adding a Secondary Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Non-Replicated Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Adding a Secondary Appliance - Create an HA Clustered Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
14. Document Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1. About this Guide
This guide details the steps required to configure a load balanced Oracle WebLogic Server environment utilizing
Loadbalancer.org appliances. It covers the configuration of the load balancers and also any Oracle WebLogic
Server configuration changes that are required to enable load balancing.
For more information about initial appliance deployment, network configuration and using the Web User Interface
(WebUI), please also refer to the Administration Manual.
Some features may not be supported in all cloud platforms due to platform specific limitations, please check with
Loadbalancer.org support for further details.
The screenshots used throughout this document aim to track the latest Loadbalancer.org
software version. If using an older software version, note that the screenshots presented here
may not match the WebUI exactly.
HTTP
In addition, a TLS/SSL termination service is required to allow clients to connect using HTTPS.
Instructions on how to configure a TLS/SSL termination service are given in the 'Appliance Configuration' section.
6. Deployment Concept
The load balancer can be deployed as a single unit, although Loadbalancer.org recommends a
clustered pair for resilience & high availability. Please refer to the section Configuring HA -
Adding a Secondary Appliance in the appendix for more details on configuring a clustered pair.
The solution to this issue is to inform the WebLogic server that it is running behind a proxy server. This is done by
enabling the WebLogic Plugin. This will, among other things, prompt WebLogic to look for certain HTTP request
headers: in particular, a header field named WL-Proxy-SSL. The load balancer needs to add this header to client
HTTP requests, ensuring that the header is present on connections that are sent to the backend servers.
2. On the left hand side of the admin console, select your base domain.
5. Scroll down to the very bottom of the console window and click Save. This will apply the setting server-wide
and will not require a restart of WebLogic server.
The same download is used for the licensed product, the only difference is that a license key file
(supplied by our sales team when the product is purchased) must be applied using the
appliance’s WebUI.
Please refer to Virtual Appliance Installation and the ReadMe.txt text file included in the VA
download for additional information on deploying the VA using the various Hypervisors.
The VA has 4 network adapters. For VMware only the first adapter (eth0) is connected by
default. For HyperV, KVM, XEN and Nutanix AHV all adapters are disconnected by default. Use
Be sure to set a secure password for the load balancer, when prompted during the setup routine.
There are certain differences when accessing the WebUI for the cloud appliances. For details,
please refer to the relevant Quick Start / Configuration Guide.
A number of compatibility issues have been found with various versions of Microsoft Internet
Explorer and Edge. The WebUI has been tested and verified using both Chrome & Firefox.
https://<IP-address-configured-during-the-network-setup-wizard>:9443/lbadmin/
You’ll receive a warning about the WebUI’s certificate. This is due to the default self signed
certificate that is used. If preferred, you can upload your own certificate - for more
information, please refer to Appliance Security Features.
Username: loadbalancer
Password: <configured-during-network-setup-wizard>
To change the password, use the WebUI menu option: Maintenance > Passwords.
3. If the latest version is already installed, a message similar to the following will be displayed:
4. If an update is available, you’ll be presented with a list of new features, improvements, bug fixes and security
related updates.
Do not navigate away whilst the update is ongoing, this may cause the update to fail.
6. Once complete (the update can take several minutes depending on download speed and upgrade version)
the following message will be displayed:
7. If services need to be reloaded/restarted or the appliance needs a full restart, you’ll be prompted accordingly.
Please contact [email protected] to check if an update is available and obtain the latest
offline update files.
6. If services need to be reloaded/restarted or the appliance needs a full restart, you’ll be prompted accordingly.
TCP 22 SSH
2. Define the Label for the virtual service as required, e.g. WL_VIP.
3. Set the Virtual Service IP Address field to the required IP address, e.g. 192.168.98.102.
2. Define the Label for the real server as required, e.g. examplesvr01.
3. Set the Real Server IP Address field to the required IP address, e.g. 192.168.98.10.
4. Click Update.
1. Using the web user interface, navigate to Cluster Configuration > SSL Certificate and click on Add a new SSL
Certificate.
3. Define the Label for the certificate as required. It may make sense to use the domain that the certificate is
associated to, e.g. 4.example.com.
5. If uploading a PFX certificate, enter the certificate’s password in the PFX File Password field.
For more information on creating PEM certificate files and converting between certificate formats please refer to
Creating a PEM File.
2. Using the Associated Virtual Service drop-down, select the Virtual Service created above, e.g. WL_VIP.
Once the VIP is selected, the Label field will be auto-populated with SSL-WL_VIP. This can
be changed if preferred.
6. Click Update.
It may be necessary to create a host entry for this test to work, if host name resolution using
DNS is not possible.
We recommend that the Primary appliance is configured first and then the Secondary should be added. Once the
Primary and Secondary are paired, all load balanced services configured on the Primary are automatically
replicated to the Secondary over the network using SSH/SCP.
For Enterprise Azure, the HA pair should be configured first. In Azure, when creating a VIP using
an HA pair, 2 private IPs must be specified – one for the VIP when it’s active on the Primary and
one for the VIP when it’s active on the Secondary. Configuring the HA pair first, enables both IPs
to be specified when the VIP is created.
The clustered HA pair uses Heartbeat to determine the state of the other appliance. Should the active device
(normally the Primary) suffer a failure, the passive device (normally the Secondary) will take over.
Non-Replicated Settings
A number of settings are not replicated as part of the Primary/Secondary pairing process and therefore must be
manually configured on the Secondary appliance. These are listed by WebUI menu option in the table below:
Local Configuration Network Interface All network settings including IP address(es), bonding
Configuration configuration and VLANs
Local Configuration Routing Routing configuration including default gateways and static routes
Local Configuration System Date & time All time and date related settings
Local Configuration Physical – Advanced Various settings including Internet Proxy, Management Gateway,
Configuration Firewall connection tracking table size, NIC offloading, SMTP relay,
logging and Syslog Server
1. Deploy a second appliance that will be the Secondary and configure initial network settings.
2. Using the WebUI on the Primary appliance, navigate to: Cluster Configuration > High-Availability
Configuration.
3. Specify the IP address and the loadbalancer user’s password for the Secondary (peer) appliance as shown in
the example above.
Clicking the Restart Heartbeat button on the Primary appliance will also automatically restart
heartbeat on the Secondary appliance.
For more details on configuring HA with 2 appliances, please refer to Appliance Clustering for
HA.
For details on testing and verifying HA, please refer to Clustered Pair Diagnostics.
1.0.2 26 April 2022 Updated SSL related content to reflect New software RJC
latest software version release
1.0.3 28 September 2022 Updated layer 7 VIP and RIP creation Reflect changes in AH
screenshots the web user
interface
About Loadbalancer.org