Start Recording dialog box

This dialog box enables you to record your business process.

To access

  • Record > Record

  • [VuGen] Start Recording button
Important information
This dialog box is dynamic and changes according to the options you select and the protocol you are using.
  • To see all the options, click the More Options button in the top right of the dialog box.
  • To see only the basic options, click Fewer Options.
Relevant tasks

User interface elements are described below:

UI Element Description
Record into action
The section of the script into which you want to record. You can choose one of the built-in action sections: vuser_init (for initialization steps), Action (for repeatable steps), or vuser_end (for sign off steps).
 
You can also add your own action. Type the action name in the Record into action field and click the Add button . The new action is added to the script.
Record
The mode used to record your business process.

  • Web Browser. For example, Web and Oracle NCA protocols record web applications.

    Note: Recording intranet sites may not work with Microsoft Edge. For information on the workaround for this, see the troubleshooting entry for Recording on Microsoft Edge.

  • Windows Application. For example, the Windows Socket protocol records Windows applications.
  • Remote Application via LoadRunner Proxy. (For Internet protocols only) This option allows you to record traffic when VuGen cannot run on the client machine, such as Linux machines, Mac OS machines, and mobile devices. If you choose this mode, you can specify the following options:
    • LoadRunner proxy listens on port: The port on which the proxy will listen.
    • LoadRunner Professional uses network interface. For Network Virtualization, enables you to select a network interface if there is more than one interface defined on the VuGen machine.
    • Display recording toolbar on client machine: Enables you to interact with the recording toolbar on the client machine.
  • Captured Traffic File Analysis. For details about creating a script using a captured traffic file, see Captured Traffic File Analysis below.
Application

  • For Web Browser recording: Select one of the browsers detected on the machine.

  • For Windows Application recording: Specify the path of an executable file.

    Note: To run a batch file (a file with a .bat extension), specify cmd.exe with its path as the Application, and the batch file as the Program arguments.
URL address
The starting URL address.
This option is displayed only when you select the Web Browser recording mode.
Program arguments
(Windows Application recording mode only) The command line arguments for the executable file specified in Recorded application. For example, if you specify plus32.exe (recorded application) with the command line options peter@neptune, it connects the user Peter to the server Neptune when starting plus32.exe.
Start Recording
 (For Internet protocols only)
You can record your business process either:

  • Immediately - Recording starts as soon as you click the Start Recording button.

  • In delayed mode - In the following instances, you may not want to record immediately:

    • You are recording multiple actions, in which case you only need to perform the startup in one action.

    • You want to navigate to a specific point in the application before starting to record.

    • You are recording into an existing script.
Working directory
For applications that require you to specify a working directory.

Recording Options

Opens the Recording Options dialog box. For user interface details, see Recording options.
Start Recording button
Begins to record your business processes based on the option selected above: Immediately or In delayed mode.
UI Element Description
Record into action
Record
Select Captured Traffic File Analysis. See All Protocols - recording above for details about the other options.
Captured file

Locate your pcap, saz (Fiddler), or har capture file.

For details about creating a capture file in a Windows, Linux, or mobile environment, using an external tool such as Wireshark, see Create a PCAP file.
Client side filter

The IP address of the client whose traffic you want to examine. VuGen typically detects the client side filter by analyzing the capture file.

Tip: Use the recording options to set a server side filter (Recording > Recording Options > Network > Mapping and Filtering).
SSL Attributes

A list of the SSL attributes for the servers being analyzed.

Use the Add, Edit, and Remove buttons to manage the entries.

The Add button opens the Add SSL Attribute dialog box, allowing you to add a server and specify its IP address, port, certificate file, and password if required.

This list is visible only after you select a pcap or saz capture file that contains SSL data and requires a certificate. This list is not available for har files—instead, configure the SSL through Fiddler.
Start Recording button
Begins to analyze your captured file.
UI Element Description
Record into action
The section into which you want to record.
Record:

  • Java applet to record a Java applet through Sun's applet viewer.

  • Java application to record a Java application.

  • Internet Explorer to record an applet within a browser.

  • Executable/Batch to record an applet or application that is launched from within a batch file or the name of an executable file.

  • Listener to instruct VuGen to wait for the batch file that initializes the configuration and runs an application before recording. This mode requires you to define the system variable _JAVA_OPTIONS as -agentlib:jdhook.
URL address
The URL to start recording (for Internet Explorer recordings)
Parameters
Any additional parameters that your application requires.
Main Class
The complete path of the Java class with the main method.

Note: This option is only present for Java Application type applications.

Applet path
This option is only present for Java applets.
Internet Explorer path
This option is only present for Internet Explorer type applications.
Executable\Batch
This option is only present for Executable\Batch type applications.
Working directory
A working directory is necessary only if your application must know the location of the working directory (for example, reading property files or writing log files). The default is the local LoadRunner Professional/VuGen bin directory.
Recording Options Opens the Recording Options dialog box. For user interface details, see Recording options.