After you develop an application, you can deploy the application in the application hosting platform SAE. This topic describes how to deploy a Java web application by using a WAR package in the SAE console.

Prerequisites

  • A namespace is created. For more information, see Create a namespace.
  • A virtual private cloud (VPC) is created. For more information, see Create a VPC.

Procedure

  1. Log on to the SAE console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region and click Create Application.
  3. In the Basic Information step, configure the parameters and click Next: Application Deployment Configurations.
    ParameterDescription
    Application Name

    Enter a custom application name.

    VPC

    Select a configuration method for the VPC. Valid values:

    • Custom Configuration: If you select this option, you must manually specify the namespace, VPC, vSwitch, and security group for the application that you want to create.
    • Automatic Configuration: If you select this option, SAE automatically specifies the namespace, VPC, vSwitch, and security group for the application.
    Namespace

    This parameter is required only if the VPC parameter is set to Custom Configuration. Select an existing namespace from the drop-down list.

    Note Namespaces and VPCs are in one-to-one mapping relationships. For information about how to modify a VPC, see Create and manage a VPC.
    vSwitch

    This parameter is required only if the VPC parameter is set to Custom Configuration. Click Select vSwitch. In the Select vSwitch dialog box, configure the parameters.

    You must specify at least one vSwitch. We recommend that you specify no more than three vSwitches. Each vSwitch must match at least one application instance.

    Security Group

    This parameter is required only if the VPC parameter is set to Custom Configuration. Select a security group from the drop-down list.

    Note If you have not created a security group in your VPC, click Create Security Group to create a security group as prompted. For more information, see Create a security group.
    Application InstancesSelect the number of instances that you want to create.
    VCPUSelect the CPU specification for the instances that you want to create.
    MemorySelect the memory specification for the instances that you want to create.
    Application DescriptionEnter the basic information about the application.
  4. In the Deployment Configurations step, configure the parameters.
    1. Configure the parameters that are used to deploy an application.
      ParameterDescription
      Technology Stack Programming LanguageSelect Java.
      Application Deployment MethodSelect Deployment with WAR Packages.
      Application Runtime Environment
      • apache-tomcat-XXX: This option is suitable for Spring Boot applications or Dubbo applications.
      • EDAS-Container-XXX: This option is suitable for high-speed service framework (HSF) applications.
      Java Environment
      • Dragonwell X (recommended): supports OpenJDK. If you select this option, the startup and runtime of the application are accelerated and garbage collection (GC) efficiency is improved. For more information, see Configure startup commands.
      • Open JDK X: This environment is based on the CentOS operating system and the size of the base image is large.
      • openjdk-XXXXX-jdk-alpine3.9: This environment is based on the Alphine operating system and the size of the base image is small.
      Note Compared with the CentOS operating system, the Java environment that is based on the Alphine operating system supports fewer tools or commands. If you select openjdk-XXXXX-jdk-alpine3.9, some commands in the webshell may fail to be run. Select an environment based on your business scenario.
      File Upload MethodSelect Upload WAR Package or WAR Package Address.
      • Upload WAR Package: Click Select File and select the WAR package that you want to use to deploy the application.
      • WAR Package Address: Enter the directory in which the WAR package is stored.
      Note The name of the package that you want to use to deploy an application can contain only letters, digits, hyphens (-), and underscores (_).
      VersionThe version number of the application. Enter a version number or click Use Timestamp as Version Number.
      Time Zone SettingsSelect the time zone of the application. Example: UTC+8.
    2. Optional:Configure the advanced settings based on your business requirements.
      Advanced settingDocumentation
      Service Registration and DiscoveryN/A
      Startup Command SettingsConfigure startup commands
      Java Tomcat SettingsConfigure Java Tomcat parameters
      Note You can configure Tomcat settings only if the Application Deployment Method parameter is set to Deployment with JAR Packages.
      Environment Variable SettingsConfigure environment variables
      Hosts Binding SettingsConfigure host bindings
      Application Health CheckConfigure application health checks
      Application Outbound/Inbound Internet AccessConfigure EIPs
      Application Lifecycle ManagementConfigure application lifecycle management
      Log Collection Service
      Persistent StorageConfigure NAS storage
      Configuration ManagementInject configurations
      Graceful Release and Shutdown of MicroservicesN/A
  5. Click Next: Confirm Specifications.
  6. In the Specification Confirmation step, view the details of the application and the fee for the selected specifications. Then, click Confirm.
    The Creation Completed step appears. You can click Application Details to go to the Basic Information page of the application.

Verify the deployment result

After an application is deployed, you can use one of the following methods to verify the deployment result for the application.

  • View the running status of application instances.
    1. Log on to the SAE console.
    2. In the left-side navigation pane, click Applications. On the Applications page, click the name of the application that you want to manage.
    3. On the Basic Information page, click the Instance Deployment Information tab to view the running status of the instances.

      If Running or Completed is displayed in the Status column, the application is deployed.

  • Add an Internet-facing Server Load Balancer instance to the application.

    After an application is deployed, you can configure an SLB instance to allow access to the application within a specified period of time for other applications.

    SLB instances are classified into the following types:

    • Internal-facing SLB instance: provides an access portal in the VPC where the application resides to ensure that the application can be accessed by other applications in the same VPC.
    • Internet-facing SLB instance: SAE can automatically purchase an Internet-facing SLB instance for an application, or you can use an Internet-facing SLB instance that you purchased in the SLB console. This helps ensure that the application can be accessed by other applications over the Internet.
    Note You can allow access to an application by using an Internet-facing SLB instance the same way you allow access to an application by using an internal-facing SLB instance. For more information, see Bind an SLB instance to an application. After an SLB instance is bound to an application, you can enter a URL that consists of the IP address, port, and access path of the SLB instance in the address bar of your browser to access the application. Example: 192.168.XX.XX:80/image.

View application metrics

After an application is deployed, you can view the key performance metrics of the application in the Application Monitoring module.

  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 the application that you want to manage.
  3. In the left-side navigation pane, view application monitoring data as needed.
    • Application Overview: Choose Application Monitoring > Application Overview. The Application Overview page displays the key performance metrics of the application, such as the total number of requests and the average response time.
    • Application Details: Choose Application Monitoring > Application Details. The Application Details page displays more comprehensive application monitoring data, such as the data for JVM monitoring and exception analysis.
    • API Operation Calls: Choose Application Monitoring > API Operation Calls. The API Operation Calls page displays the monitoring data by API operation, such as the call topology, upstream and downstream links.
    • Advanced Monitoring: Choose Application Monitoring > Advanced Monitoring. The Advanced Monitoring page displays higher-performance monitoring and management data, such as global application topology, data of SQL exception analysis, and local call stack.

References