1. Administering Oracle SOA Cloud Service
  2. Administer Oracle SOA Cloud Service
  3. Perform Lifecycle Operations on an Oracle SOA Cloud Service Instance
  4. Stop or Start an Oracle SOA Cloud Service Instance and Individual VMs
  5. About Stopping or Starting an Oracle SOA Cloud Service Instance and Individual VMs

About Stopping or Starting an Oracle SOA Cloud Service Instance and Individual VMs

You can stop or start an Oracle SOA Cloud Service instance. When the service instance is running, you can stop, start, and restart individual Managed Server or load balancer VMs.

Note:

The stop and restart procedures stop VMs. If you want to shut down the WebLogic Administration Server or Managed Server processes running on the VMs, without stopping the VMs, see Shutting Down and Starting the WebLogic Server Managed Servers and Administration Server Processes on VMs in Using Oracle Java Cloud Service. You might want to do this if you have other processes besides the servers running on the VMs and you do not want to shut down these other processes.

Why Stop an Oracle SOA Cloud Service Instance?

Stopping an Oracle SOA Cloud Service instance frees up compute resources used by the service instance’s VMs.

What Happens When an Oracle SOA Cloud Service Instance is Stopped or Started?

Stopping and starting an Oracle SOA Cloud Service instance has the following results:

  • Stopping the service instance: The VMs on which the Administration Server, Managed Servers, and load balancer, are running are stopped. You cannot start, stop, or restart the Administration Server, Managed Server, or load balancer VMs individually while the service instance is stopped.

    When an Oracle Cloud Infrastructure instance is stopped, billing depends on the compute shape used to create the instance. Oracle SOA Cloud Service supports only standard shapes, which means that stopping an Oracle SOA Cloud Service instance always pauses billing. See Resource Billing for Stopped Instances in the Oracle Cloud Infrastructure documentation.

  • Starting the service instance: All VMs on which the Administration Server, Managed Server, and load balancer are running are started. You can restart the Administration Server, and stop, start, or restart the Managed Servers and load balancer VMs individually.

Note:

Block storage should not be added manually by using the Oracle Compute Cloud Service because VM restart detaches that block storage. To reattach the block storage, you must use the Oracle Compute Cloud Service. However, block storage added manually is not deleted when an Oracle SOA Cloud Service instance is restarted. You must delete it manually. Instead of attaching block storage manually, add storage by scaling a node. For more information, see Scale an Oracle SOA Cloud Service Node Up or Down .

Why Stop, Start, or Restart an Administration Server, Managed Server, or Load Balancer VM?

If an Oracle SOA Cloud Service instance is running:

  • You can restart the VMs on which the Administration Server, Managed Server, or load balancer are running if you are experiencing problems with the server that would warrant a reboot. The restart operation is the same as stopping the server or load balancer VM, then starting it immediately.

  • You can stop the VMs on which the Managed Server or the load balancer are running to free up resources and stop metering those resources. You might also want to stop the service instance instead of scaling, keeping the server or load balancer ready for a later time. If you stop all but one Managed Server VM, you might want to stop the load balancer VM because it is not needed.

  • You can start a Managed Server or load balancer VM if it is stopped and you want to use it again. Metering begins again.

How Do I Monitor the Stop, Start, or Restart Operation?

You can monitor progress of a stop, start, or restart operation on the Activity section of the Oracle SOA Cloud Service Instance Overview page. The Oracle SOA Cloud Service Instance Overview page is described in Explore the Oracle SOA Cloud Service Activity Page.

The Activity section indicates what kind of operation is in progress, and whether it is in progress or complete. When the operation ends, the start and end time of the operation is displayed.