Serverless App Engine:Use the Alibaba Cloud Toolkit for IntelliJ IDEA plug-in to deploy an application

Deploy an application in SAE

Alibaba Cloud Toolkit allows you to deploy applications in SAE only by using WAR packages, JAR packages, or images.

1. In the Project section on the left side of IntelliJ IDEA, right-click the name of the project that you want to deploy and choose Alibaba Cloud > Deploy to SAE... from the shortcut menu.
2. In the Deploy to SAE dialog box, configure the application deployment parameters and click Apply to save the settings.
   The following table describes the parameters.

   Parameter	Description
   Region	The region where the application resides.
   Namespace	The namespace of the application
   Application	The application name.
   Build	Maven Build: If you select this option to build the application, the system adds a Maven job to build the deployment package. Upload File: If you select this option to build the application, you must upload a WAR or JAR package. Image: If you select this option to build the application, you must configure an image address. Gradle Build: Not supported.

3. Optional:In the Deploy to SAE dialog box, click Advanced. In the Advanced section, configure advanced application parameters.
   Note If you do not configure advanced application parameters, the settings in the SAE console are used by default.

   The following table describes the parameters.

   Type	Parameter	Example	Description
   Deployment with JAR Packages	Package Version	1.0.1	The version number of the application.
   	JDK	Open JDK 8	The version of the JDK on which the deployment package of the application depends.
   	Web Container	apache-tomcat-7.0.91	The version of the Tomcat container on which the deployment package depends.
   Startup Command Settings	Jar Start Options	custom-option	The option settings that are used to deploy the JAR package. The following default startup command is used: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs
   	Jar Start Args	custom-args	The parameters that are used to deploy the JAR package. The following default startup command is used: $JAVA_HOME/bin/java $JarStartOptions -jar $CATALINA_OPTS "$package_path" $JarStartArgs
   Release Policy Settings	Update Strategy	{"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}}	The deployment policy. Examples: Example 1: Perform canary release for one instance and automatically release the remaining instances in two batches with a one-minute interval between the deployment of each instance. {"type":"GrayBatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":1},"grayUpdate":{"gray":1}} Example 2: Automatically release the instances in two batches with no interval between the deployment of each instance. {"type":"BatchUpdate","batchUpdate":{"batch":2,"releaseType":"auto","batchWaitTime":0}}
   Hosts Binding Settings	Custom Host Alias	[{"hostName":"samplehost","ip":"127.0.0.1"}]	The custom mappings between hostnames and IP addresses.
   Application Health Check	Liveness	{"exec":{"command":["sleep","5s"]},"initialDelaySeconds":10,"timeoutSeconds":11}	The details of the availability check that was performed on the container. If the container fails this health check multiple times, the system disables and restarts the container. The health check can be performed only by sending commands in a container. {"exec":{"command":["sleep","5s"]},"initialDelaySeconds":10,"timeoutSeconds":11}
   	Readiness	{"exec":{"command":["sleep","6s"]},"initialDelaySeconds":15,"timeoutSeconds":12}	The readiness check of the container. If a container fails this health check multiple times, the system disables and restarts the container. Containers that fail this health check cannot receive traffic from Server Load Balancer (SLB) instances.
   Deployment Settings	Min Ready Instances	1	The minimum number of available instances of the application.
   	Batch Wait Time	10	The wait time between batches. Unit: seconds.
   Environment Variable Settings	Envs	[{"name":"envtmp","value":"0"}]	The environment variables.

4. Click Run.
   You can use one of the following methods to verify that the application has been deployed:

   • BUILD SUCCESS is displayed in the logs printed in the Console section of IntelliJ IDEA.
   • The application change record in the SAE console displays Success.

Manage Maven jobs

In the Before launch section of the Deploy to SAE page, you can add, delete, modify, or move Maven jobs.

1. In the Project section on the left side of IntelliJ IDEA, right-click the name of the project that you want to deploy and choose Alibaba Cloud > Deploy to SAE... from the shortcut menu.
2. In the Before launch section of the Deploy to SAE page, manage Maven jobs.
   • Add a job
     1. Click the icon on the right side of the Before launch section and select Run Maven Goal from the drop-down list.
     2. In the Select Maven Goal dialog box, select the modules available for the current project and enter the build command in the Command line field.
     3. Click OK.
   • Delete a job: Select the job that you want to delete and click the icon on the right side of the Before launch section.
   • Modify a job: Select the job that you want to modify and click the icon on the right side of the Before launch section. In the Select Maven Goal dialog box, modify the job information and click OK.
   • Move a job: Select the job that you want to move and click the or icon on the right side of the Before launch section.

Deploy a multi-module project

A multi-module project is a project in which each module is independently developed and with call relationships among the modules. Alibaba Cloud Toolkit can be used to deploy a submodule in a multi-module project.

To deploy a submodule for a multi-module Maven project, you must execute the job of the submodule in the end in the Before launch section of the Deploy to SAE page.

References