script. The proxy control directory is required.
Usage: runProxy options -- proxyCommunicationDir logDirectory [jvmOption=jvmOptionValue [ jvmOption=jvmOptionValue [...] ]
Options:
-r <dir>, --proxy-runtime-dir=<dir> #Specifies proxy runtime directory
-d <dir>, --proxy-dir=<dir> #Specifies root proxy directory
-j <dir>, --jre-dir=<dir> #Specifies root JRE directory
-v, --verbose #Enable verbose output
-h,--help #Show this
jvmOption
-Dappdynamics.controller.hostName=<hostName> #Set the host name or IP address of the Splunk AppDynamics Controller
-Dappdynamics.controller.port=<port> #Set the HTTP(S) port of the Splunk AppDynamics Controller
-Dappdynamics.agent.applicationName=<applicationName> #Set the name of the logical business application
-Dappdynamics.agent.tierName=<tierName> #Set the name of the logical tier
-Dappdynamics.agent.nodeName=<nodeName> #Set the name of the instrumented node
-Dappdynamics.agent.accountName=<accountName> #Set the account name used to authenticate with the Controller
-Dappdynamics.agent.accountAccessKey=<accessKey> #Set the account access key used to authenticate with the Controller
-Dappdynamics.controller.ssl.enabled=<true> #Set if the agent should use SSL (HTTPS) to connect to the Controller
-Dappdynamics.agent.uniqueHostId=<uniqueHostId> #Set a unique host ID for the App agents