Related pages:

Watch the video:

Getting Started with the Standalone Machine Agent

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
10 rates
  1. Ensure you have Java 1.5 or later installed on the machine. Java 1.7 is required if you want to use AppDynamics Analytics.
  2. Shut down the Standalone Machine Agent process before you install. A machine can have only one active Standalone Machine Agent installation at a time. 
  3. Download the Standalone Machine Agent installation zip file.
  4. Extract the zip file to the destination directory.

    (warning) Do not use spaces in the destination directory path.

    For Windows environments, unblock the zip file before you extract it as follows: right-click on the zip file, select Properties, and choose unblock.

  5. Configure how the agent connects to the Controller. 

    Configure properties for the Controller host name and port number using either the <agent home>/conf/controller-info.xml file or by adding system properties to the JVM startup script file.

    Configure using controller-info.xml: <controller-host>
    Configure using System Properties-Dappdynamics.controller.hostName
    Required: Yes
    Default: None

    Configure using controller-info.xml: <controller-port>
    Configure using System Properties-Dappdynamics.controller.port
    Required: Yes
    Default:  For On-premise Controller installations: Port 8090 for HTTP and 8181 for HTTPS communication.
                   For SaaS Controller service: Port 80 for HTTP and port 443 for HTTPS communication.

     If you start a Standalone Machine Agent on a machine that already has a Java Agent or the PHP Agent installed, the Standalone Machine Agent will automatically associate itself with the app agent's application, tier, and node settings. If you install an App Agent for PHP on the same machine as the Standalone Machine Agent, install the App Agent before the Standalone Machine Agent, and do not specify the tier and node in the machine agent configuration.

    To configure agent to use SSL see Enable SSL for Communicating with the Controller.

    To configure the agent to use proxy settings see Proxy Settings for the Controller.

  6. (For Multi-tenant mode or SaaS installations only.) Configure the agent account information.

    Specify the properties for Account Name and Account Key as provided in the welcome email sent by AppDynamics Support Team.

    Configure using controller-info.xml: <account-name>
    Configure using System Properties: -Dappdynamics.agent.accountName

    Configure using controller-info.xml: <account-access-key>
    Configure using System Properties: -Dappdynamics.controller.hostName  
     

  7.  Configure the business application, tier, and node.

    If an App Agent is installed on the same machine, AppDynamics automatically makes the association.

    If no App Agent is installed on the same machine, specify the application, tier, and node name where you want the metrics to appear.

    Edit the agent <agent home>/conf/controller-info.xml file and specify the following elements:

    Configure using controller-info.xml: <application-name>
    Configure using System Properties: -Dappdynamics.agent.applicationName

    Configure using controller-info.xml: <tier-name>
    Configure using System Properties: -Dappdynamics.agent.tierName

    Configure using controller-info.xml: <node-name>
    Configure using System Properties: -Dappdynamics.agent.nodeName

    If you do not provide configuration details the Standalone Machine Agent will not be associated with a business application. You can manually associate the agent in the UI at a later time. See Associate Standalone Machine Agents with Applications.

  8. (Optional) Configure the agent to run automatically when the machine starts on Linux or Windows.
  9. Start the agent.

    In a command line console, execute the following command to start the Standalone Machine Agent:

    java -Xmx32m -jar machineagent.jar
    

    Alternatively, in a Linux environment, you can execute the following command in the background:

    nohup java -Xmx32m -jar machineagent.jar &
    

    Note: The agent requires read, write, and delete permission to the <agent home>\conf and <agent home>\logs directories. Depending on the version of unix and whether you're using the Sigar or shell script version of the OS monitor, the agent may require elevated privileges in order to make some system calls to collect metrics.
    If your application uses a large number of AppDynamics extensions with the Standalone Machine Agent, you may need to increase the size of the memory allocation as follows:

    java -Xms64m -Xmx64m -jar machineagent.jar &
  10. Verify the agent installation.

    Open the <agent home>/logs/machine-agent.log file. If successful, this file should contain the following message:

    Started AppDynamics Machine Agent Successfully
    

    This message is also printed on the STDOUT of the process.

     
  11. Verify that the agent is reporting to the Controller on the Tier Dashboard.

    You should see an "up" arrow symbol for the agent in the Machine Agent Status column.

     

 

 

  • No labels