If your application has a small scale or a relatively simple service architecture, such as having only a single application instance, you can directly upgrade and release after development and testing are completed. This article introduces how to publish an application in a single batch in the SAE console.
Prerequisites
The application is started.
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.
Log on to the SAE console. In the left-side navigation pane, choose . On the page that appears, select a region in the top navigation bar and a namespace from the Namespace drop-down list, and then click the desired application name.
On the Basic Information page of the target application, 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, configure the Minimum Available Instances parameter.
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.
Use one of the following methods to check whether the configurations have taken effect.
Method 1:
In the navigation pane on the left of the Basic Information page, click Change History, and view the application change details. If Execution Successful is displayed, the application is deployed and the configurations have taken effect.
Method 2:
On the Basic Information page of the application, click the Instance tab to view the Status of the instances. If the Status is Running, the application is deployed and the configurations have taken effect.
More information
After you deploy an application in SAE, you can perform the following operations on the application.
Operation | References |
Application lifecycle management operations such as updating, scaling, starting, stopping, and deleting applications | |
Operations to improve application performance, such as automatic scaling, CLB binding, and batch start and stop | |
Application status-based operations, such as managing logs, configuring monitoring settings, viewing application events, and viewing change records |