1. Administering Oracle SOA Cloud Service in a Customer-Managed Environment
  2. Administer Oracle SOA Cloud Service
  3. Scale An Oracle SOA Cloud Service Instance
  4. About Scaling an Oracle SOA Cloud Service Node

About Scaling an Oracle SOA Cloud Service Node

You can scale an Oracle SOA Cloud Service node to change its compute shape in response to changes in workload or to add block storage to a node that is running out of storage. However, you cannot remove block storage from a node.

You can scale only the Administration Server node and Managed Server nodes in a WebLogic Server cluster. Oracle SOA Cloud Service does not support scaling for other nodes in a service instance, such as the load balancer node.

You must scale each node in a cluster individually. You cannot scale all nodes in a cluster in a single operation.

About Changing the Compute Shape of a Node

Not Oracle Cloud Infrastructure This topic does not apply to Oracle Cloud Infrastructure.

You can change the compute shape of a node to adjust capacity in response to changes in workload. The compute shape specifies the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to the node.

Oracle SOA Cloud Service provides a set of compute shapes that are optimized for different use cases. Choose from a set of all-purpose and memory-intensive shapes. The larger the compute shape, the greater the processing power.

  • To meet the demands of heavier workloads, scale up the compute shape of a node by choosing a larger compute shape.

    For example, changing the compute shape from OC1M to OC2M doubles the capacity of the node from one OCPU to two OCPUs and doubles the amount of RAM allocated to the node.

  • To save costs if the workload is lightened, scale down the compute shape of a node by choosing a smaller compute shape.

    For example, changing the compute shape from OC2M to OC1M reduces the capacity of the node by half from two OCPUs to one OCPU and reduces the amount of RAM allocated to the node by half.

Note:

To optimize performance and balance the load on Managed Sever instances correctly, ensure that the compute shapes of all nodes in a cluster are the same. When routing requests to Managed Server instances, the load balancer treats all Managed Sever instances as being equivalent.

About Adding Block Storage to a Node

You can add block storage to a node that is running out of storage. When you add storage to a node, an Oracle Compute Cloud Service storage volume is created and attached to the node’s VM.

Note:

You cannot remove block storage from a node.

The new storage volume created by scaling remains attached and available to the node’s VM even when the service instance is restarted or is stopped and then started. Also, this storage volume exists until you delete the service instance, at which time the storage volume is also deleted.

You can add the storage to a new volume or one of the following existing volumes:

  • Backup storage volume (Administration Server node only)

  • Domain home storage volume

  • Middleware home storage volume

For details of these volumes, see About the Disk Volumes.

You can add storage a maximum of five times to a storage volume.

Caution:

Before adding storage to the domain home or middleware home storage volume, back up the service instance to avoid the risk of data loss. For instructions, see Initiate an On-Demand Backup of an Oracle SOA Cloud Service Instance.