
You can start and stop the agent service using the relevant systemctl commands. If you did not edit the path, then it points to the correct place by default. If you did not install the Machine Agent in /opt/appdynamics/machine-agent, then change the path to /scripts/machine-agent-daemon. If systemcd is detected on the system when you install the RPM package or run the postinstall.sh script, the systemd unit file for the agent service is copied to the following location: /etc/systemd/system/rviceĮxecStart: This option in the systemd service file points to a script that starts the agent as a daemon. Installs a systemd Unit File for the Agent Service The installer either copies the SysV script to add the service or, if systemd is detected, the installer copies the agent unit file /etc/systemd/system/rvice and adds the agent to the services using this unit file. From the Launcher – /etc/init.d/appdynamics-machine-agent startĪfter the package is installed, the appdynamics-machine-agent runs opt/appdynamics/machine-agent/bin/postInstall.sh to add the agent to the services.From the Command Line – /bin/machine-agent.Using systemd – systemctl start appdynamics-machine-agent.Using SysV – service appdynamics-machine-agent start.If systemd was detected during installation, you can use the systemctl command to start the agent service. Start the Agent. You can start the agent as a service (requires sudo or root user) or from the command line.If you are installing the Machine Agent on the same server with any APM app agent, do not specify application name and tier name.

See Machine Agent Installation Scenarios.

( Optional) Determine if you need to specify an application name and tier name.( Required for Multi-Tenant Mode or SaaS installations) Configure the Agent Account Information. See Machine Agent Configuration Properties. ( Optional) Configure the agent to use proxy settings.( Optional) Configure the agent to use SSL.See Machine Agent Requirements and Supported Environments.

( Optional) Review memory requirements.( Required) Configure the Controller host name, port number, and account access key.Linux Install Using the RPM Package v23.1. Gather your configuration details and configure the agent by editing/conf/controller-info.xml file or by adding system properties to the JVM startup script file. The agent files are installed in opt/appdynamics/machine-agent and the agent is added as a service.
