Add a Load Balancer to a Service Instance

You can add a load balancer to an existing Oracle Java Cloud Service instance.

Note:

This procedure applies only to adding a user-managed load balancer (Oracle Traffic Director) that’s hosted on nodes within your service instance. You can’t use Oracle Java Cloud Service to add an Oracle-managed load balancer to an existing service instance that was provisioned without any load balancer. Instead you must manually provision and configure the load balancer by using either Oracle Cloud Infrastructure Load Balancing or Oracle Cloud Infrastructure Load Balancing Classic, depending on the region where the service instance was created. Refer to these topics:

• Getting Started with Load Balancing in the Oracle Cloud Infrastructure documentation

• Use an Oracle Cloud Infrastructure Load Balancer (with Oracle Identity Cloud Service)
• Create and Configure an Instance of Oracle Cloud Infrastructure Load Balancing (without Oracle Identity Cloud Service)

• Typical Workflow for Creating a Load Balancer in Using Oracle Cloud Infrastructure Load Balancing Classic

To add a user-managed load balancer (Oracle Traffic Director) to a service instance:

1. Navigate to the Overview page for the instance to which you want to add the load balancer.
2. Click Manage this instance in the instance name bar at the top.
3. Select Add Load Balancer.
4. In the Add Load Balancer dialog box, define the routing policy and compute shape for the load balancer, and the user name and password for the Oracle Traffic Director administrator.

   The user name and password are used to access the Load Balancer Console as described in Accessing the Administrative Consoles Used by Oracle Java Cloud Service.

   Note:

   If you add a load balancer to an Oracle Java Cloud Service instance after the service instance was created, you must define the user name and password for the Oracle Traffic Director administrator explicitly. The user name and password are not set by default to the user name of the WebLogic Server administrator. This behavior differs from the behavior when a load balancer is added to a service instance while the service instance is being created.

   Option	Description
   Load Balancer Policy	Select the policy to use for routing requests to the load balancer. Valid policies include: Least Connection Count—Passes each new request to the Managed Server with the least number of connections. This policy helps prevent a Managed Server from getting overloaded. Managed Servers with greater processing power to handle requests will 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.
   Compute Shape	Select the compute shape to use for all the load balancer nodes in the service instance. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes. The list of available shapes varies depending on whether you selected an Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure region. You are billed for Oracle Traffic Director nodes at the same price that you are billed for Oracle WebLogic Server nodes in your Oracle Java Cloud Service subscription.
   Reserved IPs	If this service instance is in a region, you can assign each load balancer node a public IP address that you had previously reserved. See Creating an IP Reservation.
   Add Another Active OTD Node	Choose whether to add a second Oracle Traffic Director (OTD) node to this service instance. Note: A configuration with two active load balancer nodes can be used to provide high availability and higher load-balancing capacity. But Oracle Java Cloud Service does not fail-over application requests between load-balancer nodes. The failover-group feature of Oracle Traffic Director is not supported. If one of the load-balancer nodes is unavailable, you are responsible for ensuring that requests fail over to another node.
   User Name	Enter a user name for the Oracle Traffic Director administrator.
   Admin Password	Define the password for the Oracle Traffic Director administrator.
   Confirm Admin Password	Re-enter the password for the Oracle Traffic Director administrator.

5. Click Add.

The Overview page is updated to show that the load balancer is being added. Click the (Refresh) icon to check the latest status.

While the load balancer is being added, the service instance is in maintenance status and you cannot start any other management operation on the service instance.

If you require the WebLogic Plug-in Enabled control to be set in Oracle WebLogic Server, you must set this control manually. If you add a load balancer to an Oracle Java Cloud Service instance after the service instance was created, Oracle Java Cloud Service does not set the WebLogic Plug-in Enabled control in Oracle WebLogic Server for you. This behavior differs from the behavior when a load balancer is added to a service instance while the service instance is being created. See Understanding the use of “WebLogic Plugin Enabled”.