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.
Prerequisites
- Make sure that the security group of your ECS instance has opened the TCP outbound
permission of ports 8442, 8443, and 8883. For more information about how to open outbound
permissions for ECS, see Add a security group rule.
Note ARMS can be connected to not only applications on ECS, but also applications on other servers that can access the Internet.
- Make sure that the third-party components or frameworks you use are within the scope of application monitoring compatibility lists. See ARMS-compatible components and frameworks .
-
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 version to the latest version, which is 1.8.X.
Procedure
- In the Backend applications section of the Access Center panel, click Java.
- Install the Security Center agent.
- Add the AppName and LicenseKey parameters. Note In the STEP2 section, replace
{LicenseKey}and{AppName}in the sample code with your actual license key and application name. The application name cannot contain Chinese characters. Replace{user.workspace}with the actual directory to which the installation package of Agent is decompressed. Replace demoApp.jar with the actual JAR package address.
- 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/setenv.sh 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 setenv.sh configuration file, open the {TOMCAT_HOME}/bin/catalina.sh file and append the preceding configurations to the JAVA_OPTS parameter. For more information, see Row 256 in the catalina.sh 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}"Jetty Append the following configurations to the {JETTY_HOME}/start.ini configuration file:
--exec -javaagent:/{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar -Darms.licenseKey={LicenseKey} -Darms.appName={AppName}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.jarResin When you start the Resin process, append the following tag to the conf/resion.xml configuration file:
<server-default> <jvm-arg>-javaagent:{user.workspace}/ArmsAgent/arms-bootstrap-1.7.0-SNAPSHOT.jar</jvm-arg> <jvm-arg>-Darms.licenseKey={LicenseKey}</jvm-arg> <jvm-arg>-Darms.appName={AppName}</jvm-arg> </server-default>Append the following tag to the conf/app-default.xml file:
<library-loader path="{user.workspace}/ArmsAgent/plugin"/>Windows 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.jarTo 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: Append the following configurations to the arms-agent.config file:
arms.licenseKey={LicenseKey} arms.appName={AppName}
- Method 1: Edit the JVM parameters based on the runtime environment of your application.
- Add the AppName and LicenseKey parameters.
Verify the result
After about one 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.
- Delete all parameters that you added in Step 7, such as {AppName} and {LicenseKey}.
- 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 was manually installed?.