Attach the Java Agent to the Synthetic Server

To attach the Java Agent to the Synthetic Server, set Java options through the variables SCHEDULER_OPTS and SYNTHETIC_SHEPHERD_OPTS. The node names and tier names given in the examples below can be modified for your use case. One JVM process requires one Java Agent to be attached.

  1. Set the options for the Synthetic Scheduler so that the Java Agent is attached to the JVM process:
    CODE 
    SCHEDULER_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-scheduler -Dappdynamics.agent.tierName=scheduler-tier"
  2. Set the options for the Synthetic Shepherd so that the Java Agent is attached to the JVM process:
    CODE 
    SYNTHETIC_SHEPHERD_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-shepherd -Dappdynamics.agent.tierName=shepherd-tier"
  3. Set the options for the Synthetic Feeder Client so that the Java Agent is attached to the JVM process:
    CODE 
    FEEDER_CLIENT_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-feeder-client -Dappdynamics.agent.tierName=feeder-client-tier"
  4. Export the variables for the Synthetic Server options:
    CODE 
    export SYNTHETIC_SHEPHERD_OPTS
export SCHEDULER_OPTS
export FEEDER_CLIENT_OPTS
  5. From the Synthetic Server installer directory, run the following to stop and start the Synthetic Server:
    CODE 
    unix/deploy.sh stop
unix/deploy.sh start