Configuring Silk Performer

The Silk Performer configuration options provide the opportunity to set global Silk Performer settings that are not associated with a particular project.

Silk Performer Workbench: The basic characteristics of a Silk Performer load testing configuration are set here—those related to the agent computers used in tests, the directories where files used in and generated by tests are located, the layout of the text of test scripts, and how results information is generated.

Silk Performer Recorder: The basic settings used by Silk Performer's recording and script generating program, the Silk Performer Recorder, are defined here. These include the settings for capturing and recording the network traffic that will be modeled in your test scripts. Here, profiles are set up and managed for the client applications that are to be used during data capture and recording. Proxies can be added or removed, and their settings edited. Here you can set the port for the integrated Web server that is used by the Silk Performer Recorder, and enable recording to begin as soon as the client application starts.

Remote Agents: Silk Performer allows for remote agent computers to be located both in the LAN, out on the Internet, and even behind firewalls— connected through HTTP and SOCKS proxies. The communication between the remote agents and the controller can be configured to include secure, encrypted connections in a distributed secure environment.

Java Configuration: Java Framework projects and Java based APIs require a Java SDK Environment. The Java SDK version, its location, and parameters such as class path and optional Java Virtual Machine settings can be configured here.