After you install the Application Real-Time Monitoring Service (ARMS) agent for a Java application, ARMS starts to monitor the Java application. Then, you can view the monitoring data of the Java application, such as the application topology, traces, abnormal transactions, slow transactions, and SQL analysis. You can install the ARMS agent manually or by using scripts. This topic shows you how to manually install the ARMS agent for a Java application.


  • Ports 8442, 8443, and 8883 in the security group have been opened for TCP outbound access. For more information about how to grant outbound permissions to ECS, see Add security group rules.
    Note In addition to applications on Alibaba Cloud ECS instances, applications on public network servers can also access ARMS.
  • Make sure your third-party components or frameworks are within the application monitoring compatibility list. For more information about the compatibility list, see application monitoring compatibility list.
  • If the JDK Version is 1.8.0_25 or 1.8.0_31, you may fail to install the arms Agent. In this case, upgrade the JDK to the latest version in 1.8.X.


  1. Log on to the ARMS console.
  2. In the left-side navigation pane, choose Application Monitoring > Applications. In the top navigation bar, select a region.
  3. On the Applications page, click Add Application in the upper-right corner.
  4. On the Add Application page, perform the following operations:
    1. Select Java as the programming language of your application.
    2. Select Default as the environment where your application is deployed.
    3. Select Install Manually as the method to install the ARMS agent.
  5. Download the ARMS agent and click Next in the Download Agent step on the Add Application page. You can use one of the following methods to download the ARMS agent:
    • Method 1: Manually download the ARMS agent. In the Download Agent step, click Download Agent.
    • Method 2: Run the wget command. Download the installation package based on your region.
      Note Use the public endpoint. If the download fails, use the VPC endpoint.
      Region list Public endpoint VPC endpoint
      China (Hangzhou)
                wget "" -O 
                wget "" -O 
      China (Shanghai)
                wget "" -O 
                wget "" -O 
      China (Qingdao)
                wget "" -O 
                wget "" -O 
      China (Beijing)
                wget "" -O 
                wget "" -O 
      China (Zhangjiakou)
                wget "" -O 
                wget "" -O 
      China (Shenzhen)
                wget "" -O 
                wget "" -O 
      China (Hong Kong)
                wget "" -O 
                wget "" -O 
                wget "" -O 
                wget "" -O 
      Japan (Tokyo)
                wget "" -O 
                wget "" -O 
      US (Silicon Valley)
                wget "" -O 
                wget "" -O 
      China East 1 Finance
                wget "" -O 
                wget "" -O 
      China East 2 Finance
                wget "" -O 
                wget "" -O 
      China South 1 Finance
                wget "" -O 
                wget "" -O 
  6. Go to the directory of the installation package. Run the following command to decompress the installation package to a working directory:
    unzip -d /{user.workspace}/ 
    Note {user.workspace} is a sample directory. Replace it with an actual directory.
  7. Copy the license key in the upper part of the Add Application page.
    Obtain the license key
  8. Use one of the following methods to add the AppName and LicenseKey parameters:
    Note Replace {LicenseKey} in the sample code with your license key. Replace {AppName} with your application name. The application name cannot contain Chinese characters. Replace {user.workspace} with the directory where the ARMS agent is decompressed. Replace demoApp.jar with the path to the actual JAR package.
    • Method 1: Edit the JVM parameters based on the runtime environment of your application.
      Runtime environment Procedure
      Tomcat on Linux or macOS

      Append the following configurations to the {TOMCAT_HOME}/bin/ file:

      JAVA_OPTS="$JAVA_OPTS -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName}" 

      If your Tomcat does not contain the configuration file, open the {TOMCAT_HOME}/bin/ file and append the preceding configurations to the JAVA_OPTS parameter. For more information, see Row 256 in the file.

      Tomcat on Windows Append the following configurations to the {TOMCAT_HOME}/bin/catalina.bat file:
      set "JAVA_OPTS=%JAVA_OPTS% -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName}" 

      If the preceding setting does not take effect, append the following configurations to the {TOMCAT_HOME}/bin/catalina.bat file:

      set "CATALINA_OPTS=-javaagent:/{user.workspace}/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName}"

      Append the following configurations to the {JETTY_HOME}/start.ini configuration file:

      Spring Boot

      When you start the Spring Boot process, append the -javaagent parameter to the startup command:

      java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName} -jar demoApp.jar 

      When you start the Resin process, append the following tag to the conf/resion.xml configuration file:


      Append the following tag to the conf/app-default.xml file:

      <library-loader path="{user.workspace}/ArmsAgent/plugin"/> 

      When you run a CMD command to start the Java process, use a backslash (\) as the delimiter in the mount path of the ARMS agent.

      java -javaagent:\{user.workspace}\ArmsAgent\arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName} -jar {user.workspace}\demoApp.jar 

      To deploy multiple instances of the same application on a server, you can differentiate the JVM processes by setting the -Darms.agentId parameter to a logical number. Example:

      java -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName} -Darms.agentId=001 -jar demoApp.jar
    • Method 2:
      1. Append the following configurations to the arms-agent.config file:

        arms.licenseKey={LicenseKey} arms.appName={AppName}
      2. Append the following parameter to the startup script of the Java application:

  9. Restart the Java application.


After about 1 minute, if your application is displayed in the application list and some data records are sent, your application is monitored by ARMS.

Uninstall the ARMS agent

If you no longer need ARMS to monitor your Java application, perform the following steps to uninstall the ARMS agent.

  1. Delete all parameters that you added in Step 8, such as {AppName} and {LicenseKey}.
  2. Restart the Java application.

Change the application name

If you forget to change the sample name Java-Demo to a custom name, you can change the application name by performing a few operations. You do not need to restart the application or reinstall the ARMS agent. For more information, see How do I modify the name of a common Java application on which the ARMS agent is manually installed?.