TCP Proxy Recorder

An alternative solution involves using a TCP/IP proxy recorder. As a prerequisite, you must be able to control the server name and TCP port number the client application connects to. Typically, these settings can be found in the registry or in a configuration file. Then, you can configure Silk Performer and the client application so that traffic is explicitly routed over the Silk Performer recorder.

Assuming that the client connects to MYSERVER on port 5012, you would change these settings to LOCALHOST and port 49152 (or any other unused TCP port) in the registry or appropriate configuration file. In Silk Performer, choose Settings > System > Recorder > Proxies > Add. Add a new proxy, and configure it as a TCP proxy listening on port 49152, connecting to the remote host MYSERVER on port 5012.

In this way, the following scenario is configured:

The client application doesn't notice a difference in performance when the recorder is running. This is in contrast to the scenario in which the client is connected directly to the server.