This topic describes how to set parameters for common applications.including JVM parameters, Tomcat, Server Load Balancer (SLB), health check, and basic information.
- Log on to the EDAS console.
Click Applications in the left-side navigation pane, and click an application on the Applications page to go to the Basic Information page.
Click Settings in the Application Settings area.
JVM parameters are the container parameters that must be configured when an application is started.Correct setting of JVM parameters helps reduce the overhead of garbage collection and thus shorten the server response time and improve throughput.If container parameters are not set, JVM parameters are allocated by default.
In the Application Settings dialog box, click the JVM tab.
Click Memory, Application, GC, Tools, and Custom to set parameters.Click Save to save the settings.
Note: After you set JVM parameters, restart the application manually through EDAS for the settings to take effect.
You can configure the following parameters for the Tomcat container in the EDAS console: port number, application access path, and maximum number of threads in the connection pool.
In the Application Settings dialog box, click the Tomcat tab.
Set Tomcat parameters, and click Configure Tomcat.
Description of Tomcat parameters:
Configuration NOTE Application Port The port number range is (1024, 65535).The admin authority is needed for container configuration and the root authority is required to operate ports with numbers less than 1024. Therefore, enter a port number greater than 1024. The default value is 8080.Therefore, enter a port number greater than 1024.If this parameter is not set, the default value is 8080. Tomcat Context Select an application access path.
- If you select Package Name, you do not need to set the Custom Path parameter. The application access path is the name of the WAR package.
- If you select Root, you do not need to set the Custom Path parameter. The application access path is /.
- If you select Custom, set the Custom Path parameter.If the “Custom Path” parameter is not set, the default application access path is the same as the name of the WAR package.
Maximum Threads Set the number of connections in the connection pool. It corresponds to the maxThreads parameter. The default value is 400.We recommend that this parameter be set under professional guidance. Tomcat Encoding Select an encoding format of Tomcat. The options include UTF-8, ISO-8859-1, GBK, and GB2312.Default format is ISO-8859-1.
If you have bought Alibaba Cloud Server Load Balancer, EDAS synchronizes your Server Load Balancer instance to the EDAS console and provides the relevant configuration function.For more SLB information, see What is Server Load Balancer.
Server Load Balancer instances are classified into Internet- and intranet-based instances by IP address, which share the same configuration method.
The following describes how to configure an Internet-based Server Load Balancer instance.
In the Application Settings dialog box, click the SLB tab.
Set SLB instance parameters, and click Configure SLB.
Description of SLB parameters:
SLB (intranet): intranet SLB instance.After you select Use the virtual server group, click New virtual server group, and set Virtual Server group name.
Listener (intranet): Set the port, or click Create new listener and set SLB frontend port number.
SLB (Internet): Internet SLB instance.After you select Use the virtual server group, click New virtual server group, and set Virtual Server group name.
Listener (Internet): Set the port, or click Create new listener and set SLB frontend port number.
EDAS provides the health check function used to check whether deployed applications run properly.To use this function, configure a health check URL.
Health check is the process where EDAS Agent periodically checks and reports the status of containers and applications and then sends the check results to the console.Health check helps you understand the overall service running status in a cluster environment and facilitates auditing and troubleshooting.You can configure a health check URL in the EDAS console to check whether deployed applications run properly.
The following figure shows how EDAS Agent performs health check for applications.
Health check is triggered every 10 seconds.The steps marked by 1 and 2 are described as follows.
EDAS Agent checks whether the Ali-Tomcat process for running your application is alive.
If the process is alive, the agent proceeds to Step 2.
If the process is not alive, health check ends and the check result is “Fail”.
EDAS Agent checks whether Code 200 is returned by the configured URL.
If no URL is configured, health check does not start; if a URL is configured, EDAS Agent checks whether HTTP 200 is returned by the configured URL.
For description of status in Steps 1 and 2, see the following section.
go to the Application Details page .
View the Running Status field of the Instance Information list in the lower part of the page.
Description of real-time status:
Container Exits: Displayed when the agent detects that the Ali-Tomcat process is not alive in Step 1.
Application Exception: displayed when any other code than 200 is returned by the configured URL in Step 2.
Normal: displayed if no exception occurs in Step 1 and Step 2.
If EDAS Agent detects no configured URL in Step 2, the Normal state is still displayed, followed by an exclamation mark. When you place the pointer over it, the “Configure a health check URL to check the application status accurately” message appears.”
Agent Abnormal: Displayed if the agent does not report status information to the EDAS server in 30 seconds.
If health check is not configured, containers with agent versions later than EDAS Agent 2.8.0 automatically allocate the health check path http://127.0.0.1:8080/healthCheck.html. Click Modify next to the health check URL in the Basic Information tab of the Application Details page.
Click the Health Check tab in the Application Settings dialog box, set the health check URL, and click Save.
If you have set related container parameters, configure a health check URL in the format of http://127.0.0.1:[custom port number/[configured path]/healthCheck.html based on the container configuration.“healthCheck.html” is the default path. Replace it with a custom path as needed.Ensure that the health check URL is accessible by applications and can return HTTP Code 200 to Code 500.
[Example] Assume that the WAR package name is “order.war”. You can configure such a health check URL http://127.0.0.1:8080/order/healthCheck.html if no other container parameters are configured; or you can configure the health check URL as http://127.0.0.1:8081/healthcheck.html if the container path is configured as the root path, the port number is set to “8081”, and the WAR package contains the “healthcheck.html” file for the purpose of health status marking.
In the Application Settings dialog box, click the Basic Information tab, set Application Name and Application Description, and click Modify.