You can add a load balancer to an Oracle SOA Cloud Service instance after its creation.
For any Oracle SOA 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 SOA Cloud Service Instance.
A service instance can include zero or one load balancer nodes (VMs). Each node is assigned a separate public IP address.
Oracle Traffic Director (OTD) is used as the load balancer for a service instance.
To add a load balancer to a service instance:
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 SOA Cloud Service instance after the service instance was created, Oracle SOA 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”.