Configure the Synthetic Server to Use Proxy

You need to configure the Synthetic Server to use the proxy to forward traffic to the SaaS EUM Server. In the examples configurations below, the proxy URL is 127.0.0.1 and the proxy port is 3128. You will need to replace those values with the URL and port of your proxy server.

Synthetic Shepherd

From the host machine of the Synthetic Server, set the proxyUrl and proxyPort properties in the <synthetic-server_installation_dir>/synthetic-processor/conf/synthetic-shepherd.yml file to point to the URL and port of the proxy server, which the Synthetic Shepherd will send requests.

saasLink:
proxyUrl: "127.0.0.1"
proxyPort: 3128

Synthetic Scheduler

Set the proxyUrl and proxyPort properties in the <synthetic-server_installation_dir>/synthetic-processor/conf/synthetic-scheduler.yml file to point to the URL and port of the proxy server so that Synthetic Shepherd also sends requests to the proxy.

saasLink:
proxyUrl: "127.0.0.1"
proxyPort: 3128

Synthetic Feeder Client

Finally, set the proxyUrl and proxyPort properties in the <synthetic-server_installation_dir>/synthetic-processor/conf/synthetic-feeder.yml file to point to the URL and port of the proxy server so that Synthetic Server Client Feeder also sends requests to the proxy.

websocketConfiguration:
proxyUrl: "127.0.0.1"
proxyPort: 3128
Note: NoteFeeder Client for Synthetic services does not support Proxy authentication.