Adding Recording Profiles

In the Silk Performer menu, click Settings > System .

Click the Recorder icon. The Recording Profiles page opens.

Click Add to add a new recording profile to the list. The Recording Profile dialog opens.

In the Profile name field, type a unique name for the recording profile. The profile name is required to identify the application in the Silk Performer Recorder window.

In the Application path field, type the name of the application's executable and the directory in which it resides. To locate the executable, click the browse icon.

In the Working directory field, type the working directory of the application. The working directory is the folder that contains the application or related files. Some applications need files located in other directories, so you might have to specify the folder in which these files reside.

In the Application arguments field, type any number of application parameters. Passing parameters to an application is useful, for example, when recording the function calls performed by a command-line tool without a graphical UI.

In the Executables to be recorded field, specify the executables that are to be recorded. This allows you to record processes that are different from the specified application's executable, which might be required if the application is hosted by another process that powers the communication process.

Enable Record new and running instances (Secure Boot mode) to record all instances of an application that are already running at the time the Recorder is launched, as well as all instances that are started with the Recorder or later on. You can enable this option in case the conventional recording mechanism does not work as expected for your application. This option is automatically enabled on machines that have the UEFI feature secure boot enabled.

In the Protocol selection area, check the check box that identifies the function library into which you want the Silk Performer Recorder to hook. Available options vary according to the selected application type, as follows:

Web – The Silk Performer Recorder hooks into a Web application, intercepts all function calls, and displays the results.

When the Web option is selected, you can click Web Settings to open the Web Settings dialog box, which enables you to select the method that the Recorder uses to capture Web- and TCP/IP-based traffic.
TCP/IP – The Silk Performer Recorder hooks into a TCP/IP application, intercepts all function calls, and displays the results.
IIOP – The Silk Performer Recorder hooks into the IIOP function library of the client application, intercepts all the function calls, and displays the results.
Citrix XenApp – The Silk Performer Recorder hooks into a Citrix XenApp application, intercepts all function calls, and displays the results.
ODBC – The Silk Performer Recorder hooks into the ODBC function library of the client application, intercepts all function calls, and displays the results.
DB2 CLI – The Silk Performer Recorder hooks into the DB2 CLI function library of the client application, intercepts all function calls, and displays the results.
Oracle OCI – The Silk Performer Recorder hooks into the Oracle function library of the client application, intercept all functions calls, and displays the results.

Click OCI Settings to open a dialog box that allows you to select the OCI client library to use for intercepting function calls. Select the appropriate library from the list box and click OK.
Tuxedo – The Silk Performer Recorder hooks into the TUXEDO function library of the client application, intercepts all function calls, and displays the results.
SAPGUI – The Silk Performer Recorder hooks into functions of SAP GUI interfaces, intercepts all the function calls, and displays the results.

Click OK to add the new profile to the list.