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.

Set the options for the Synthetic Scheduler so that the Java Agent is attached to the JVM process:

SCHEDULER_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-scheduler -Dappdynamics.agent.tierName=scheduler-tier"

Set the options for the Synthetic Shepherd so that the Java Agent is attached to the JVM process:

SYNTHETIC_SHEPHERD_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-shepherd -Dappdynamics.agent.tierName=shepherd-tier"

Set the options for the Synthetic Feeder Client so that the Java Agent is attached to the JVM process:

FEEDER_CLIENT_OPTS="-javaagent:./java_agent/javaagent.jar -Dappdynamics.agent.applicationName=synthonprem -Dappdynamics.agent.nodeName=synthetic-feeder-client -Dappdynamics.agent.tierName=feeder-client-tier"

Export the variables for the Synthetic Server options:

export SYNTHETIC_SHEPHERD_OPTS
export SCHEDULER_OPTS
export FEEDER_CLIENT_OPTS

From the Synthetic Server installer directory, run the following to stop and start the Synthetic Server:
```
unix/deploy.sh stop
unix/deploy.sh start
```