Adding a Load Balancer to an Oracle Java Cloud Service Instance on OPCM

You can add a load balancer to an Oracle Java Cloud Service instance after its creation.

For any Oracle Java Cloud Service instance that contains more than one Managed Server node, a load balancer provides these benefits:

  • Manages the routing of requests across all Managed Servers.

  • Enables you to configure the routing policy.

  • Enables you to suspend a service instance temporarily to perform routine maintenance, as described in Suspending an Oracle Java Cloud Service Instance.

A service instance can include zero, one or two load balancer nodes (VMs). Each node is assigned a separate public IP address. A configuration with two active load balancer nodes provides these advantages:

  • High availability if a load balancer becomes unavailable.

  • Multiple load balancers for greater application throughput.

Note:

Oracle Java Cloud Service does not automatically fail over application requests to the other load balancer node if one becomes unavailable.

Oracle Traffic Director (OTD) is used as the load balancer for a service instance.

To add a load balancer to a service instance:

  1. From the Services page of the Oracle Java Cloud Service Console, click an existing service instance.
    The Overview page is displayed.
  2. Click menu icon and select Add Load Balancer.
    The Add Load Balancer dialog box opens.
  3. 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 is useful for smoothing distribution when Managed Servers get bogged down. 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 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.

    For more information about the defined compute shapes, contact your Oracle Cloud Administrator.

    Valid compute shapes include:

    • OC3: 1 OCPU and 7.5 GB memory

    • OC4: 2 OCPUs and 15 GB memory

    • OC5: 4 OCPUs and 30 GB memory

    • OC6: 8 OCPUs and 60 GB memory

    • OC7: 16 OCPUs and 120 GB memory

    Additional shapes are available for more memory-intensive applications:

    • OC1M: 1 OCPU and 15 GB memory

    • OC2M: 2 OCPUs and 30 GB memory

    • OC3M: 4 OCPUs and 60 GB memory

    • OC4M: 8 OCPUs and 120 GB memory

    • OC5M: 16 OCPUs and 240 GB memory

    You can also change the compute shape after creating the Oracle Java Cloud Service instance. See Scaling an Oracle Java Cloud Service Node on OPCM

    Add Another Active OTD Node

    Choose whether or not to add a second load balancer node to this service instance.

    User Name

    Enter your choice of user name for the Oracle Traffic Director administrator.

    The name must be between 8 and 128 characters long and cannot contain any of the following characters:

    • Tab

    • Brackets

    • Parentheses

    • These special characters:

      • Left angle bracket (<)

      • Right angle bracket (>)

      • Ampersand (&)

      • Pound sign (#)

      • Pipe symbol (|)

      • Question mark (?)

    Note:

    You can change the user name and password through the Load Balancer Console after you have added the load balancer.

    Password

    Define the password for the Oracle Traffic Director administrator.

    The password must meet these requirements:

    • Starts with a letter

    • Is between 8 and 30 characters long

    • Contains letters, at least one number, and, optionally, any number of these special characters:

      • Dollar sign ($)

      • Pound sign (#)

      • Underscore (_)

        No other special characters are allowed.

    Confirm Password

    Re-enter the password for the Oracle Traffic Director administrator.

  4. Click Add Load Balancer.
The Overview page is updated to show that the load balancer is being added.

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.

After the load balancer is added, information about the load balancer is also available on the Load Balancer tab on the Administration page.

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”.