Starting, Stopping, and Restarting Oracle API Platform Cloud Service

About Starting, Stopping, and Restarting Oracle API Platform Cloud Service - Classic Instances

You can stop and start an Oracle API Platform Cloud Service - Classic instance and, when the service instance is running, stop, start, and restart individual 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.

This topic describes why you would want to stop or start a service instance, or stop, start, or restart individual server or load balancer VMs. This topic also describes what happens when service instances are stopped and started, and how to monitor these operations.

Note:

You can’t start or stop Administration Server VMs; you can restart them instead while the service instance is running. See Restarting the Administration Server VM.

Why Stop an Oracle API Platform Cloud Service - Classic Instance

Stopping an Oracle API Platform Cloud Service - Classic instance frees up compute resources used by the service instance’s VMs. Metering for those resources stops.

What Happens When an Oracle API Platform Cloud Service - Classic Instance is Stopped or Started

Stopping and starting an Oracle API Platform Cloud Service - Classic 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.
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 API Platform Cloud Service - Classic instance is restarted. You must delete it manually.

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

If an Oracle API Platform Cloud Service - Classic 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 Services 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.

Starting and Stopping an Oracle API Platform Cloud Service - Classic Instance

You can stop and start an Oracle API Platform Cloud Service - Classic instance through the Oracle API Platform Cloud Service - Classic Services page or the Overview page.

To stop or start an Oracle API Platform Cloud Service - Classic instance:

Navigate to the Oracle API Platform Cloud Service - Classic Overview page:
1. From the Services page, click the name of the Oracle API Platform Cloud Service - Classic instance you want to stop or start.
  The Oracle API Platform Cloud Service - Classic Overview page is displayed with the Overview tile in focus, displaying detailed information about the service instance.
Click the Menu icon in the right corner of the page and select Start or Stop.
A confirmation dialog is displayed.
Click OK in the confirmation dialog.

When the operation completes, the Oracle API Platform Cloud Service - Classic instance is stopped or started. The entry for the service shows that the stop or start operation has ended.

Restarting the Administration Server VM

You can restart the VM on which the Administration Server is running in an Oracle API Platform Cloud Service - Classic instance that is in a running state.

To restart the Administration Server:

Navigate to the Services page, and then click the name of the service instance in which you want to restart the Administration Server.
The Oracle API Platform Cloud Service - Classic Overview page is displayed with the Overview tile in focus, displaying detailed information about the service instance.
Click the Menu icon adjacent to the Administration Server row and select Restart.
A confirmation dialog is displayed.
Click OK in the confirmation dialog.

The Administration Server VM restarts.

Stoppping, Starting, and Restarting Managed Server and Load Balancer VMs

You can stop, start, and restart the VMs on which the Managed Servers or the load balancer are running in an Oracle API Platform Cloud Service - Classic instance if the service instance is in a running state. Restarting a Managed Server or load balancer VM is the same as stopping it, then starting it.

Navigate to the Services page, and then click the name of the service instance in which you want to start, stop, or restart a Managed Server or load balancer VM.
The Oracle API Platform Cloud Service - Classic Overview page is displayed with the Overview tile in focus, displaying detailed information about the service instance.
Click the Menu icon to the right of the Managed Server or load balancer row and select Stop, Start, or Restart.
A confirmation dialog is displayed.
Click OK in the confirmation dialog.
The Managed Server or load balancer VM is stopped, started, or restarted.

Restarting WebLogic Servers

You can start and stop servers in an Oracle API Platform Cloud Service - Classic instance by using the WebLogic Server Administration Console and via WebLogic Scripting Tool (WLST) commands.

Oracle API Platform Cloud Service - Classic is built on top of Oracle Java Cloud Service, which in turn is built on top of Oracle WebLogic Server. When you create an API Platform instance, an Oracle WebLogic domain is provisioned across all machines that are part of that instance.

An Oracle WebLogic Domain is made up of a set of WebLogic server instances that work together to host and operate your Java EE applications. Within the domain only one WebLogic server instance is responsible for administrative operations, such as creating new server instances or deploying applications. That privileged server is referred to as the administration server, whereas all the rest are managed servers.

The administration server also hosts the WebLogic Server Administration Console.

The tutorial Restarting WebLogic Servers in an Oracle Java Cloud Service Instance describes how start and stop both the administration and the managed servers in two ways:

Using the WebLogic Server Administration Console
Using WLST Commands