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 Traffic (Recommended)
The proxy often resides in the DMZ for the network and presents a virtual IP address to forward requests from the on-prem Synthetic Server to SaaS Synthetic Server through the SaaS EUM Server as shown below.
Connection | Source | Destination | Protocol | Default Port(s) |
---|---|---|---|---|
|
The |
| HTTP(S) | 7001/7002 |
|
The |
| HTTP(S) | N/A |
The on-prem Synthetic Server Client Feeder communicates with the SaaS Synthetic Server Feeder through a bi-directional WebSocket connection that is not made through the proxy server.
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.
Connection | Source | Destination | Protocol | Default Port(s) |
---|---|---|---|---|
|
The |
| HTTP(S) | 7001/7002 |
|
The |
| HTTP(S) | N/A |
|
The |
| HTTP(S) | 80/443 |
| HTTP(S) | 80/443 | ||
|
The
|
| WebSocket |
16101 |
| WebSocket | 16001 |