1. Administering Oracle Java Cloud Service
  2. Administer the Load Balancer for an Oracle Java Cloud Service Instance
  3. Add a Second Load Balancer Node to a Service Instance

Add a Second Load Balancer Node to a Service Instance

If your Oracle Java Cloud Service instance has a load balancer node, you can add a second active load balancer node to the same instance.

Note:

This procedure applies only to service instances that include a user-managed load balancer (Oracle Traffic Director). 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.

A service instance can include zero, one, or two Oracle Traffic Director (OTD) nodes. Each node is assigned a separate public IP address. A configuration with two active load balancer nodes can be used to provide high availability and higher load-balancing capacity.

Note:

Oracle Java Cloud Service does not fail-over application requests between load-balancer nodes. If one of the load-balancer nodes is unavailable, you are responsible for ensuring that requests fail over to another node. The failover-group feature of Oracle Traffic Director is not supported.

To add a second Oracle Traffic Director node to a service instance, complete the following steps:

  1. Navigate to the Overview page for the instance to which you want to add a node.
  2. Click Manage this instance Menu icon next to the instance name and select Scale Out.
  3. In the Scale Out dialog box, select OTD.
  4. If the first load balancer node uses a reserved IP address, you must select an IP reservation for the second node in the Reserved IPs field.

    To reserve an IP address for use by the second load balancer node, click the gear icon next to this field. See Creating an IP Reservation.

  5. Click Scale Out.

The Overview page is updated to show that 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. Click the Refresh icon(Refresh) icon to check the latest status.

Both the load balancer nodes are active and can distribute requests to the Managed Servers in your service instance. Each load balancer node has a unique public IP address.

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. For details, see Understanding the use of “WebLogic Plugin Enabled”.