About Life Cycle Management of Oracle SOA Cloud Service Instances

With a few clicks of the mouse, you can create an Oracle WebLogic Server production environment in the cloud that is based on best practices, optimized for high performance and reliability, and is integrated with your Oracle SOA Cloud Service instances.

When you create an Oracle SOA Cloud Service instance, you create and configure an Oracle Fusion Middleware Infrastructure domain with the resources defined in the following table.

Resources Description

Administration Server

Operates as the central control entity for the configuration of the entire domain. It maintains the domain's configuration documents and distributes changes in the configuration documents to managed servers.

Each Oracle SOA Cloud Service instance has one server instance that hosts the Administration Server.

Managed Servers

Host business applications, application components, Web services, and their associated resources.

When creating an Oracle SOA Cloud Service instance, you can configure up to four Managed Servers, then scale out, as needed.

By default, the Managed Servers are named as follows: first8charsOfDomainName_server_n (where n starts with 1 and is incremented by 1 for each additional Managed Server to guarantee unique names).

Cluster

Consists of multiple Oracle WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. In a cluster, most resources and services are deployed identically to each Managed Server (as opposed to a single Managed Server), enabling failover and load balancing.

A cluster is configured automatically for a production-level Oracle SOA Cloud Service instance.

By default, the cluster name is generated from the first eight characters of the Oracle SOA Cloud Service instance name using the following format: first8charsOfInstanceName_cluster.

Load Balancer

Employs Oracle Traffic Director for load balancing to manage routing requests across all Managed Servers and provide failover and replication.

It is recommended that you enable the load balancer when you configure more than one Oracle SOA Cloud Service in your environment. Enabling the load balancer is optional.

If you want more information about Oracle WebLogic Server domains, see "WebLogic Server Domains" in Understanding Oracle WebLogic Server (12.2.1.4 | 12.2.1.3).

After the Oracle SOA Cloud Service instance is created, the Administration Server in the domain is started automatically. You can deploy applications and manage the domain resources using the standard administration tools, including Enterprise Manager Fusion Middleware Control, Oracle WebLogic Server Administration Console, Oracle WebLogic Scripting Tool (WLST), Node Manager, and Oracle Traffic Director Console.

Note:

If you extend your domain using the administration tools (for example, to add an additional cluster), you are responsible for maintaining those additional resources.

Typical Workflow for Managing the Life Cycle of Oracle SOA Cloud Service Instances

To manage the life cycle of Oracle SOA Cloud Service instances, follow the typical workflow shown in the following table.

Note:

The table provides links to information about how to perform each task using the web browser-based Oracle SOA Cloud Service Console. For information about using the REST API to manage the life cycle of Oracle SOA Cloud Service instances, see REST API for Oracle SOA Cloud Service.

Task More Information
Access the Oracle SOA Cloud Service Console after you have signed in.

See Access the Oracle SOA Cloud Service Console

Create a new Oracle SOA Cloud Service instance by stepping through the Oracle SOA Cloud Service provisioning wizard.

For Oracle Cloud Infrastructure, see Provision a Custom Oracle SOA Cloud Service Instance on Oracle Cloud Infrastructure

For Oracle Cloud Infrastructure Classic, see Provision a Custom Oracle SOA Cloud Service Instance on Oracle Cloud Infrastructure Classic

View status, resource allocation, and other details for all Oracle SOA Cloud Service instances.

Explore the Oracle SOA Cloud Service Console

View status, resource allocation, and other details for an individual Oracle SOA Cloud Service instance.

Explore the Oracle SOA Cloud Service Instance Overview Page

Deploy and undeploy applications to an Oracle SOA Cloud Service instance using JDeveloper, Fusion Middleware Control, the WebLogic Server Administration Console, and WLST commands. You cannot deploy and undeploy applications directly through the Oracle SOA Cloud Service Console.

Deploy and Undeploy Applications to an Oracle SOA Cloud Service Instance

Stop Oracle SOA Cloud Service instances or individual Managed Servers. Restart the Administration Server or individual Managed Servers if reboot is needed.

Stop or Start an Oracle SOA Cloud Service Instance and Individual VMs

Disable the load balancer to block any new traffic to an Oracle SOA Cloud Service instance temporarily while maintenance is performed.

Disable Load Balancer Traffic to Suspend an Oracle SOA Cloud Service Instance

Scale an Oracle SOA Cloud Service instance by scaling a cluster or a node. Scale an Oracle SOA Cloud Service Instance
Add storage to a node that is running out of space. An Oracle Compute Cloud Service storage volume is created and attached to the node’s VM. Add Storage to a Node

Change the license type of an Oracle SOA Cloud Service instance from BYOL to Cloud License or vice versa after the instance is created.

Change the License Type for an Oracle SOA Cloud Service Instance

Back up your Oracle SOA Cloud Service instances to preserve them in a particular state. If necessary, undo changes by restoring the instance’s configuration data from a backup. You can also restore the software to its current official patch set update (PSU) level. Back Up and Restore an Oracle SOA Cloud Service Instance

Manage access to an Oracle SOA Cloud Service instance by deleting the instance.

Delete an Oracle SOA Cloud Service Instance

Use tags to organize and categorize your Oracle SOA Cloud Service instances, and to search for them.

unresolvable-reference.html