Synthetic Server Proxy Architecture

You can also, optionally, set up a proxy to forward traffic from the SaaS Synthetic Server Feeder to the on-prem Synthetic Server Client Feeder, but your proxy server must support WebSockets.

Proxy for Downstream and Upstream (Optional)

When setting a proxy for downstream and upstream traffic, the proxy must support WebSocket. The on-prem Synthetic Server Client Feeder initializes the WebSocket connection with the SaaS Synthetic Server Feeder through the proxy server. Once the WebSocket connection is established, the on-prem Synthetic Server Client Feeder and the SaaS Synthetic Server Feeder can use the persistent connect to make bi-directional requests.

Proxy for downstream and upstream architecture

Connection Source Destination Protocol Default Port(s)

The on-prem Synthetic Server (Scheduler) sends the job requests to the proxy server, when then forwards the requests to the SaaS EUM Server.

SaaS EUM Server
HTTP(S)7001/7002

The SaaS EUM Server forwards the requests to the SaaS Synthetic Server.

SaaS Synthetic Server
HTTP(S)N/A

The on-prem Synthetic Server (Client Feeder) establishes a WebSocket connection with the SaaS Synthetic Server (Synthetic Server Feeder) through the proxy server.

SaaS Synthetic Server

HTTP(S)80/443

on-prem Synthetic Server

HTTP(S)80/443
The SaaS Synthetic Server (Synthetic Server Feeder) and on-prem Synthetic Server (Client Feeder) communicate bi-directionally through the proxy server. Most of the traffic is from the SaaS Synthetic Server Feeder to the on-prem Synthetic Client Feeder.
on-prem Synthetic Server
WebSocket

16101

SaaS Synthetic Server
WebSocket16001