Configure Load Balancer

Only Oracle Cloud Infrastructure This topic applies only to Oracle Cloud Infrastructure.

Specify whether or not you want to use the load balancer.

Note:

  • If you do not select a load balancer, then the managed server URLs (b2bconsole, worklistapp) are not accessible using the load balancer IP address. You will have to create SSH tunnels to access these URLs.
  • You cannot add a load balancer or a load balancer shape as a post-provisioning task. You must select these details as part of this provisioning wizard session.
Item Description
Load Balancer
  • None: Select if you do not need a load balancer.
  • Oracle-Managed Load Balancer: Select if you want Oracle to manage your load balancer.
  • Oracle Traffic Director: Select if you want to manage the load balancer.

Load Balancer Policy (if Oracle Traffic Director is selected)

Load Balancing Policy (if Oracle-Managed Load Balancer is selected)

Select the load balancer mechanism for routing traffic to servers.

If you selected Oracle Traffic Director:
  • Least Connection Count. Passes each new request to the managed server with the least number of connections. This policy is useful for smoothing distribution when managed servers slow down. managed servers with greater processing power receive more connections over time.

  • Least Response Time. Passes each new request to the managed server with the fastest response time. This policy is useful when managed servers are distributed across networks.

  • Round Robin. Passes each new request to the next managed server in line, evenly distributing requests across all managed servers regardless of the number of connections or response time.

If you selected Oracle-Managed Load Balancer:
  • IP Hash. Uses an incoming request's source IP address as a hashing key to route traffic to the same backend server. The load balancer routes requests from the same client to the same backend server as long as that server is available.
  • Least Connections. Passes each new request to the managed server with the least number of connections. This policy is useful for smoothing distribution when managed servers slow down. managed servers with greater processing power receive more connections over time.

  • Round Robin. Passes each new request to the next managed server in line, evenly distributing requests across all managed servers regardless of the number of connections or response time.

Subnet for Load Balancer Node 1 Select the subnet on which to create the first load balancer. This field is displayed if you selected Oracle-Managed Load Balancer as your load balancer type.
Subnet for Load Balancer Node 2 Select the subnet on which to create the second load balancer. This field is displayed if you selected Oracle-Managed Load Balancer as your load balancer type.

For each load balancer node, select a subnet from a different availability domain. If the selected region has only one availability domain, Subnet for Load Balance Node 2 is not shown. You can only select one subnet, which is assigned to both nodes. For at least one of the nodes, Oracle recommends selecting a subnet from the same availability domain as that of the service instance. This ensures that as long as the service instance is running, the applications deployed on it remain accessible through the load balancer.

Load Balancer Shape

Select the shape to use. Each shape represents a template that is used to determine the load balancer's total preprovisioned maximum capacity (bandwidth) for ingress and engress traffic. This field is displayed if you selected Oracle-Managed Load Balancer as your load balancer type.

  • 100 Mbps:
  • 400 Mbps:
  • 8000 Mbps:

Compute Shape

Select the number of Oracle Compute Units (OCPUs) and amount of RAM memory that you want to allocate to the VM for the load balancer. The larger the compute shape, the greater the processing power. This field is displayed if you selected Oracle Traffic Director as your load balancer type.

The valid compute shapes for Oracle Cloud Infrastructure are:

  • VM.Standard1.1 – 1.0 OCPU, 7.0GB RAM

  • VM.Standard2.1 – 1.0 OCPU, 15.0GB RAM

  • VM.Standard1.2 – 2.0 OCPU, 14.0GB RAM

  • VM.Standard2.2 – 2.0 OCPU, 30.0GB RAM

  • VM.Standard1.4 – 4.0 OCPU, 28.0GB RAM

  • VM.Standard2.4 – 4.0 OCPU, 60.0GB RAM

  • VM.Standard1.8 – 8.0 OCPU, 56.0GB RAM

  • VM.Standard2.8 – 8.0 OCPU, 120.0GB RAM

  • VM.Standard1.16 – 16.0 OCPU, 112.0GB RAM

  • VM.Standard2.16 – 16.0 OCPU, 240.0GB RAM

  • VM.Standard2.24 – 24.0 OCPU, 320.0GB RAM

  • BM.Standard1.36 – 36.0 OCPU, 256.0GB RAM

  • BM.Standard2.52 – 52.0 OCPU, 768.0GB RAM

Note:

If you select a VM. Standard1.X shape, verify that your account has entitlement for it before proceeding with the provisioning.

Note that you cannot change the compute shape after you have created the Oracle SOA Cloud Service instance.