Scale a Domain

Resize your Oracle WebLogic Server for Oracle Cloud Infrastructure domain to meet changing workload requirements.

Add or Remove WebLogic Server Nodes

You can change the number of nodes (compute instances) in your Oracle WebLogic Server for Oracle Cloud Infrastructure stack to increase performance or to reduce costs. Add nodes to scale out, or remove nodes to scale in.

Note:

You cannot use this procedure to scale a domain that was created before June 29, 2020.

To scale the domain, edit the node count variable for the stack and then run an Apply job.

Oracle WebLogic Server for Oracle Cloud Infrastructure performs these tasks for a scaling operation:

  • Add or remove compute instances
  • Add or remove managed servers in the domain configuration (optional)
  • Scale up or scale down the new compute instances (optional)
  • Add managed servers to the existing cluster in the domain configuration, if the domain is not running Oracle WebLogic Server Standard Edition (optional)
  • Update the backend set of the load balancer, if your stack includes a load balancer (optional)

If you customized your domain configuration after creating it (changing port numbers, changing server names, and so on), there is no guarantee that the domain modification part of the scaling job will succeed. You can disable this feature and perform these tasks manually after the scaling job completes.

  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Select the Compartment that contains your stack.
  3. Click the name of your stack.
  4. Click Variables.
  5. Click Edit Variables.
  6. Edit WebLogic Server Node Count, and then change the shape of the new compute instances or use the default shape.
    For the compute instance shape:
    • If you select VM.Standard.E3.Flex, you can specify the OCPU count for the instance.

    • If the default shape is VM.Standard.E3.Flex, and you choose to use this default shape, you can edit the OCPU count for the additional instances.

    • If you select the standard shape for the new compute instance, you cannot specify the OCPU count for the instance.

      Note:

      If you do not increase the node count and edit the OCPU count for the VM.Standard.E3.Flex shape, the OCPU count remains unchanged.

    If you increase the node count and modify the SSH Public Key, the key will be used for new compute instances only. The keys for existing compute instances remain unchanged.

  7. Optional: If you want Oracle WebLogic Server for Oracle Cloud Infrastructure to create compute instances but not update your domain configuration, select Do Not Update Domain Configuration For Scale Out.
  8. Click Next.
  9. Click Save Changes.
  10. Click Terraform Actions, and then click Apply.
  11. Enter a name for the job, and then click Apply.
  12. Periodically monitor the progress of the Apply job until it is finished.
  13. Click Outputs.
  14. Locate WebLogic_Instances, and verify the number of compute instances in the updated stack.

If you selected Do Not Update Domain Configuration For Scale Out, then you must manually update your domain configuration and add the managed servers. Use the WebLogic Server Administration Console or the WebLogic Server Scripting Tool (WLST).

If your domain is in a private subnet, the bastion compute instance is deleted and recreated. As a result, the bastion might have a different IP address. See Access the WebLogic Console in a Private Subnet.

Change the Shape of the Existing Compute Instances

You can scale up the existing compute resources for your Oracle WebLogic Server for Oracle Cloud Infrastructure domain to increase performance, or you can scale down the existing compute resources to reduce costs.

Note:

Do not use Resource Manager to change the shape of the compute instances in your domain. You must use the Compute service.

When you change the shape of an existing compute instance, you select a different processor, number of cores, amount of memory, network bandwidth, and maximum number of VNICs for the instance. The instance's public and private IP addresses, volume attachments, and VNIC attachments remain the same. For example, changing the shape of an instance from VM-Standard2.2 to VM-Standard2.4 doubles the capacity of the node from two OCPUs to four OCPUs, and also doubles the amount of memory allocated to the node.

The original shape of the compute instance determines which shapes you can select as a target for the new shape. You cannot modify the shape of an instance that uses a bare metal shape or certain virtual machine (VM) shapes. See Changing the Shape of an Instance.

Oracle recommends that you use the same shape for all compute instances that comprise a single WebLogic Server cluster. This allows traffic to be distributed uniformly across the cluster.

When you change a shape, the compute instance must be restarted. To avoid downtime and ensure your applications remain available to users, Oracle recommends that you create a cluster with multiple compute instances, and that you change the shape for one compute instance at a time.

When you change the shape of the first compute instance, the domain's administration server will be temporarily unavailable. However, your applications do not depend on the administration server and will not be affected.

  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Select the Compartment in which your domain was created.
  3. Click the name of the first compute instance for your domain.
    The instance has wls-0 appended to the name. For example: mydomain-wls-0
  4. Click Edit, and then select Edit Shape.
  5. Select a new shape, and then click Save Changes > Reboot Instance.
  6. Repeat from step 2 for the remaining compute instances in your domain.

Add a Load Balancer

You can add a load balancer to an existing Oracle WebLogic Server for Oracle Cloud Infrastructure domain that was originally created without a load balancer.

Note:

You cannot use this procedure on a domain that was created before June 29, 2020.

Oracle WebLogic Server for Oracle Cloud Infrastructure configures the new load balancer to distribute application traffic to the managed servers in your domain.

Edit the load balancer variables for the stack and then run an Apply job.

  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Select the Compartment that contains your stack.
  3. Click the name of your stack.
  4. Click Variables.
  5. Click Edit Variables.
  6. Select Provision Load Balancer.
  7. Configure the load balancer network.
    • If you chose to use an existing regional subnet for WebLogic Server, then select an existing regional subnet from the list of regional and availability domain-specific subnets. A load balancer can have only one regional subnet, which is shared between both nodes.
    • If you chose to create a regional subnet for WebLogic Server, then specify a CIDR for the new load balancer subnet.
  8. Select a minimum and maximum flexible load balancer shape.
    By default, the minimum bandwidth size is set to 10Mbps and maximum to 400Mbps.

    Note:

    You can update the shape to a maximum of 8000Mbps. Before you select the maximum bandwidth, ensure to check the available service limit for the flexible load balancer bandwidth.
  9. Select Private Load Balancer if you do not want to assign a public IP address to the load balancer.
    If you change the load balancer for an existing domain from public to private, or change the load balancer from private to public, then you must also change the load balancer subnet CIDR.
  10. Click Next.
  11. Click Save Changes.
  12. Click Terraform Actions, and then click Apply.
  13. Enter a name for the job, and then click Apply.
  14. Periodically monitor the progress of the Apply job until it is finished.
  15. Click Outputs.
  16. Identify the IP address of the load balancer in the updated stack.

If your domain includes the sample application, you can access it using the load balancer. See Access the Sample Application.

Remove the Load Balancer

If you created an Oracle WebLogic Server for Oracle Cloud Infrastructure domain with a load balancer, and no longer require the load balancer, you can remove it.

Note:

You cannot use this procedure on a domain that was created before June 29, 2020.

Edit the load balancer variables for the stack and then run an Apply job.

  1. Sign in to the Oracle Cloud Infrastructure Console.
  2. Select the Compartment that contains your stack.
  3. Click the name of your stack.
  4. Click Variables.
  5. Click Edit Variables.
  6. Clear Provision Load Balancer.
  7. Click Next.
  8. Click Save Changes.
  9. Click Terraform Actions, and then click Apply.
  10. Enter a name for the job, and then click Apply.
  11. Periodically monitor the progress of the Apply job until it is finished.