All Products
Search
Document Center

Serverless App Engine:Perform a single-batch release for an application

Last Updated:Sep 03, 2024

If your application is a small-scale application or uses a simple service architecture, you can develop and test a new version, and then deploy the new version to upgrade the application. For example, if your application contains only one instance, you can perform a single-batch release. This topic describes how to perform a single-batch release for an application in the SAE console.

Procedure

Warning

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.

  1. Log on to the SAE console.

  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. Then, click the name of an application.

  3. In the upper-right corner of the Basic Information page, click Deploy Application.

  4. Configure deployment parameters.

    Note

    The 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.

  5. 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.

    Note
    • Make 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.

  6. Optional:Configure the advanced settings based on your business requirements.

    Java

    Advanced setting

    References

    Startup Command Settings

    Configure a startup command

    Java Tomcat Settings

    Configure Java Tomcat parameters

    Note

    You can configure Tomcat settings only if the Application Deployment Method parameter is set to Deployment with WAR Packages.

    Environment Variable Settings

    Configure environment variables

    Service Registration and Discovery

    Hosts Binding Settings

    Configure hosts binding

    Application Health Check

    Configure application health checks

    Application Outbound/Inbound Internet Access

    Application Lifecycle Management

    Configure application lifecycle management

    Log Collection Service

    Persistent Storage

    Configure NAS storage

    Configuration Management

    Inject configurations

    Graceful Start and Shutdown of Microservices

    Note

    If you set the Application Deployment Method parameter to Deployment with WAR Packages or Deployment with JAR Packages, and set the Application Runtime Environment to EDAS-Container-XXX, this section is not displayed.

  7. After you configure the settings, click Confirm.

  8. Check whether the configurations have taken effect.

    • Method 1:

      In the left-side navigation pane of the Basic Information page, click Change Records. On the Change Records page, view the change details. If Executed is displayed in the Change Status column, the application is deployed and the configurations have taken effect.

    • Method 2:

      On the Basic Information page, click the Instance Deployment Information tab to view the Status of the instances. If Running is displayed in the Status column, the application is deployed and the configurations have taken effect.

References

The following table describes the operations that you can perform on an application after you deploy the application on SAE.

Operation

References

Lifecycle management operations, such as updating, starting, stopping, and deleting an application, and scaling in or scaling out the instances for an application

Manage the lifecycle of an application

Performance optimization operations, such as configuring auto scaling policies for an application, binding Server Load Balancer (SLB) instances to an application, and starting or stopping applications in batches

Application status-based operations, such as managing logs, configuring monitoring settings, viewing application events, and viewing change records