If your application is small or has a simple service architecture, such as an application with a single instance, you can deploy a new version directly after development and testing. This topic describes how to deploy an application in a single batch in the SAE console.
Prerequisites
The application is running.
Procedure
After you redeploy an application, the application is restarted. To prevent unpredictable errors such as business interruptions, we recommend that you deploy applications during off-peak hours.
On the SAE Application List page, select a region and namespace at the top, and click the ID of the target application to open the application details page.
On the Basic Information page, click Deploy Application.
Configure deployment parameters.
NoteThe deployment method of an application is based on the deployment method that you selected for the application for the first time. Configure the parameters based on the selected method.
Deployment with WAR Packages: Upload another WAR package or enter the path of a newly deployed WAR package, and configure the runtime environment and other settings.
Deployment with JAR Packages: Upload another JAR package or enter the path of a newly deployed JAR package, and configure the runtime environment and other settings.
Deployment with ZIP Packages: Upload another ZIP package or enter the path of a newly deployed ZIP package, and configure the runtime environment and other settings.
Image: In the Configure Image section, click Modify Image. In the Modify Image panel, select another image repository or image version.
In the Release Policy Settings section, set Minimum Available Instances.

By Number: Enter the minimum number of available instances.
By Ratio: Enter a percentage. You can also select Use System Recommended Value.
NoteMake sure that at least one instance is available during application deployment and rollback. This ensures business continuity. If you set the value to 0, business interruptions occur when the application is upgraded.
If you specify a percentage, the minimum number of available instances is rounded up to the nearest integer. For example, five instances are available and you specify 25%. In this case, the minimum number of available instances is 2.
Optional:Configure the following advanced settings as needed.
After you configure the settings, click Confirm.
You can verify that the configuration is effective as follows.
Method 1:
In the navigation pane on the left of the Basic Information page, click Change History. On the Change History page, view the application change details. If the status is Execution Successful, the application is successfully deployed.
Method 2:
On the Basic Information page, click the Instance Information tab to view the Running Status of the instances. If the Running Status is Running, the application is successfully deployed.
Stop a change
To stop a change that is in progress, click Stop Change on the Change Details page.
Stopping a change may cause multiple versions of the application to run at the same time:
Deployed instances: remain in their current state and continue to run. No rollback is triggered.
Instances being deployed: continue the deployment process and then run the new version from this release.
Undeployed instances: remain in their current state and continue to run. The release process is stopped for these instances.
New instances created by auto scaling: use the new version from this release when scaling out.
After you stop the change, redeploy the application or roll back to a previous version as soon as possible. This ensures that all application instances run the same version.
More information
After you deploy an application in SAE, you can perform the following operations on the application.
Operation | References |
Lifecycle management operations, such as updating, scaling, starting, stopping, and deleting an application | |
Operations to improve application performance, such as auto scaling, CLB instance binding, and batch start and stop | |
Operations related to the application running status, such as log management, monitoring management, viewing application events, and viewing change records |