The major components of a Service Plan can be managed on the Cloud Portal’s Details page.
![](https://downloads.verj.io/verjio/resourceHub/media/images/tutorials/cloud_tour/details/servicePlanDetails.png)
Service Plan Overview
Service Plan details such as its name and current configuration can be seen here.
![](https://downloads.verj.io/verjio/resourceHub/media/images/tutorials/cloud_tour/details/overview.png)
Clicking on the Service Plan’s URL will take you to its landing page. The URL will use the IP address of the Service Plan until it has detected that its configured domain is active. This usually takes a few minutes after the creation of the Service Plan or a change in the domain’s configuration.
The entire Service Plan can be restarted from here. This completely removes the Service Plan from the Verj.io Cloud and rebuilds it. No data is lost during this process, but your application will be unavailable until it has been rebuilt.
Container Details
Provides an overview of the Service Plan’s Workflow Engine and all Application Containers.
Settings allows common configuration options to be set, for example the time zone and domain, and provides a link to the Service Plan’s Admin Application. These settings apply to the Workflow Engine and all the Application Containers.
View Logs opens a page containing the combined logs for the Workflow Engine and all the Application Containers. This includes logs from your application as well as access logs.
Stop and Restart All affect the Workflow Engine and all Application Containers. Stop turns off all the containers until you start them again and Restart All stops and then automatically starts them all. Your application will be unavailable unless one Application Container is running. No data is lost during this process.
The Workflow Engine and all Application Containers have their own section providing information and management options for each individual container.
![](https://downloads.verj.io/verjio/resourceHub/media/images/tutorials/cloud_tour/details/containerDetails.png)
An Application Container has a name starting with webapp followed by a number, for example webapp_1. A Service Plan’s Workflow Engine is named workflow. These names are used in the logs to help distinguish entries from a particular Application Container or Workflow Engine.
The number of end users currently served by the container is displayed, along with the amount of memory the container is using. A container’s maximum memory is dependent on the Service Plan’s configuration and is shown in the Service Plan Overview.
If an Application Container is using a high percentage of its available memory, it may be appropriate to move to a Service Plan configuration that allows a container to use more memory or to scale the Service Plan by adding another Application Container. Note that changing the configuration of your Service Plan may affect the cost of your subscription.
The logs of a container can be opened, and each container can be individually restarted. Note that restarting your only active Application Container or the Workflow engine may make your application unavailable until it has finished starting up.
Finally, the current configured state of the container is shown.
Application Database Details
Each Application Database entry displays its configured state and allows you to stop or restart it. Note that while a database is stopped your application will not be able to contact it and may not function as expected.
![](https://downloads.verj.io/verjio/resourceHub/media/images/tutorials/cloud_tour/details/applicationDatabaseDetails.png)
Clicking more provides information about how to connect a compatible database client to that database. Before a client can connect to the database, external access must be granted by clicking on Access disabled to change its state to Access enabled. It is recommended that access is only granted for as long as it is needed and then disabled.
A live backup of the database can be triggered from here, which is added to the backups directory of the Application Filesystem.
FTP Details
A Service Plan allows SFTP access to your application's filesystem.
![](https://downloads.verj.io/verjio/resourceHub/media/images/tutorials/cloud_tour/details/ftpDetails.png)
Clicking more expands to provide connection details for your SFTP client. Before a client can connect to the application’s filesystem external access must be granted by clicking Enable Access. It is recommended that access is only granted for as long as it is needed and then disabled.
Statistics
The number of end users across all Application Containers is displayed in this section combined with the average response time for the Service Plan. More statistics can be seen by clicking on the View More button.