AppDynamics Synthetic Agent Install

synthetic-agent-install-2016.md

Requirements

• A license for Synthetic Private Agents ( not included in Synthetic Server Monitoring )
• Processor: 2 GHz
• Memory: 4 GB RAM
• Disk Space: 40 GB
• Dedicated host
• Windows Server 2012 64-Bit or Windows Server 2012 R2 64-Bit (Only English version)
• Microsoft .NET Framework 4.7 or greater
• SaaS: https://synthetic.api.appdynamics.com:443;
• OR On-Premises: http://:10101 ( http recommended )

Prerequisites

• Recommended Settings for the Host Machine
• Steps for Preparing the Host Machine
• Windows Domains Versus Workgroups
• Configure Local Policies for Workgroups
• Configure Group Policies for Windows Domains
• Remove Internet Browsers from Dedicated Machine
• Prevent Anti-Virus Software from Affecting the Private Synthetic Agent

Set up group as Powershell ( Administrator )

secpol.msc

Check Results of Group Settings

gpresult /H output.html

Update install.ps1 for Windows greater than 2012

function isPlatformSupported

# last line of function isPlatformSupported
Return $true

Update cookbook file

cookbooks\synthagent\attributes\default.rb

Before if windows_version.windows_server_2012?

default['synthagent']['browsers'] = ["IE11", "Firefox", "Chrome", "Chrome.DeviceEmulation"]

Configure Proxy

Does not support credentials

Run Install

Set-ExecutionPolicy Unrestricted
.\install.ps1

Check config

C:\appdynamics\synthetic-agent\synthetic-driver\conf

## Use the URL to your Synthetic Server and the port to the Synthetic Shepherd (10101)
shepherdUrl: http://<on-prem-synthetic-server-host>:10101
## You can get the values for this from the Controller Admin Console > Controller Settings
## or the properties 'property_eum-account-name' and 'property_eum-license-key' from your license file.
privateClient:
    # from the license area in the controller
    eumAccount: "<eum_account>"
    licenseKey: "<license_key>"

Configure browser proxy settings

At a clients you will probably need to login as the user which runs the agent and configure the proxy settings in each browser. In the advanced proxy settings you will also need to add exceptions so that the proxy ignores localhost and 127.0.0.1. If you don't do this jobs will fail.

In synthetic.yml you can remove the sudo line at the start of the file and run the selenium server as the logged in user.

Run Agent

• Double click stop icon
• Double click start icon
  • Output: Waiting for incoming task...

Create a job to confirm working

Configure Autologin

Schedule Agent to Start on Login