Architecture
ZebraTester contains four built-in server components which are started on your local computer
Local Architecture
- Proxy Sniffer: A special proxy server used to record Web surfing sessions.
- Web Admin: An embedded, local Web server for the GUI.
- Exec Agent: A server which supports the execution of load test jobs.
- Job Controller: A server which allows to combine several load-releasing machines into a cluster.
The following TCP/IP server ports have been set up on your local system:
Port Number |
Port Description |
|---|---|
7990 |
Embedded Web Server, GUI (web admin) |
7993 |
Load Test Execution Server (exec agent) |
7995 |
Load Test Cluster Controller (job controller) |
7996 (optional) |
REST API Server (proxy sniffer) |
7998 |
Internal communication port (proxy sniffer) |
7997 |
HTTP/S Proxy Port (proxy sniffer) |
7999 (deprecated) |
HTTP Proxy Port, HTTP only (proxy sniffer) |
Note: The ZebraTester Console application execute all of these four server components as integrated threads.
Distributed Architecture
Remote execution of load tests, as well as combining several Exec Agents (load generators) to a load generating cluster, is supported in an easy and transparent way.
On remote systems normally only Exec Agent are installed and started. They are normally running on port 7993 when plain TCP/IP connections are used or on Port 80 or 443 when HTTP/S connections are used for the internal ZebraTester communication between your local system and the remote Exec Agents – but any other TCP/IP port can also be configured. Please note that you have to enable the corresponding inbound firewall rule on the remote systems.