On this page:

Related pages:

This topic describes how to install the Standalone Machine Agent using the Linux ZIP archive that includes JRE 1.8.

If your Linux distribution supports the RPM Package Manager, it is easier to download and use the RPM package.

Install the Agent

  1. Before installing, review the installation notes at Install the Standalone Machine Agent.

    You need read/write privileges to the <machine-agent-home> installation directory.

  2. Download and unzip the Agent zip bundle. On the command line, use the following command, where <zip-bundle.zip> is the name of the zip archive for your environment and
               <machine-agent-home> is the name of the directory where you want to install the agent. 

       unzip <zip-bundle.zip> -d <machine-agent_home>

    This package includes a supported version of JRE in the following folder: 
    If the Machine Agent host already has a supported JRE (version 1.7 or higher) that you want to use, delete this folder. 

  3. Gather your configuration details and configure the agent by editing<machine_agent_home>/conf/controller-info.xml file or by adding system properties to the JVM startup script file.
    See Plan the Standalone Machine Agent Configuration.

    1. (Required) Configure the Controller host name and port number, and account access key 
    2. (Optional) Review memory requirements. See Standalone Machine Agent Requirements and Supported Environments.
    3. (Optional) To configure agent to use SSL see Enable SSL for Standalone Machine Agent.
    4. (Optional) To configure the agent to use proxy settings see the proxy settings in Standalone Machine Agent Configuration Property Reference.
    5. (Required for multi-tenant mode or SaaS installations) Configure the Agent Account Information.
    6. (Optional) Application and tier name. Usually, if you are installing the Standalone Machine Agent on the same server with any APM app agent, you should not specify application name and tier name. See Standalone Machine Agents and Applicationsto determine if you need to specify and application name and tier name. 
  4. If you prefer to add the machine agent as a service, see the section Add the Agent as a Service below and start it accordingly.
  5. Start the machine agent: <machine_agent_home>/bin/machine-agent. For example, from the <machine_agent_home> directory:


    To see usage, enter machine-agent -h.

    Usage: machine-agent [-dh] [-j JAVA_HOME] [-p pidfile] [-D prop] [-X prop]
    Start the machine agent.
        -d            daemonize (run in background)
        -p pidfile    write PID to <pidfile>
        --help        print command line options
        -D prop       set JAVA system property
        -X prop       set non-standard JAVA system property
  6. (Optional) Verify the installation. See Verify the Standalone Machine Agent Installation.

Add the Agent as a Service Using SysV

  1. Install the Standalone Machine Agent as described above.
  2. Create a link to /etc/sysconfig

    ln -s <machine-agent-home>/etc/sysconfig/appdynamics-machine-agent /etc/sysconfig/appdynamics-machine-agent
  3. Add the machine agent to /etc/init.d, for example:

    ln -s <machine-agent-home>/etc/init.d/appdynamics-machine-agent /etc/init.d/appdynamics-machine-agent
  4. Edit the environment variables in /etc/sysconfig/appdynamics-machine-agent configuration file:

  5. Add the agent as a service. For example, on the command line enter:

    chkconfig --add appdynamics-machine-agent
  6. Start the agent service: service appdynamics-machine-agent start. 

  7. Verify that the Agent is reporting to the Controller. See Verify the Standalone Machine Agent Installation.

Add the Agent as a Service Using systemd

  1. Install the Standalone Machine Agent as described above.
  2. Edit the environment variables and options in the following service file as needed: <machine-agent-home>/etc/systemd/system/appdynamics-machine-agent.service 

    1. MACHINE_AGENT_HOME – Specifies where the Machine Agent files are located.
    2. JAVA_HOME – Specifies the JRE the agent uses. The Machine Agent  bundles the JRE that we recommend you use, but you can use an existing JRE. (1.7 or higher for versions up to 4.3, 1.8 or higher for version 4.4 and higher)
    3. User – This option in the service file specifies the system user to be used to start the Standalone Machine Agent. By default this is root.  AppDynamics recommends that you create a non-root user to run the machine agent. The new user needs to have read access to controller-info.xml and write access to the log files. See Permissions for Non-Root User to Run the Machine Agent for more details. The systemd service file does not include the "MACHINE_AGENT_USER" variable.
  3. Copy the  file as follows:
    cp <machine-agent-home>/etc/systemd/system/appdynamics-machine-agent.service \
  4. Enable the Machine Agent to start at system startup:
    systemctl enable appdynamics-machine-agent
  5. Start the agent service:
    systemctl start appdynamics-machine-agent 
  6. Check the service status:
     systemctl status appdynamics-machine-agent

  7. Verify that the Agent is reporting to the Controller. See Verify the Standalone Machine Agent Installation.