Typically, LoadComplete can start recording without any additional configuration. However, in certain cases, you may need to change some settings. This topic describes these changes. You can also use this information as a checklist if you experience issues.
Specifying a Port for Recording
During recording, LoadComplete acts as a proxy between your system and the network.
By default, the LoadComplete proxy port, through which your system communicates with the network, is 8889. If this port is used by some application on your computer, configure LoadComplete to use another port to record traffic:
Select Tools > Options from the main menu.
In the resulting dialog, choose the Recording > General category.
Specify the needed port number in the Proxy port setting.
Specifying Proxy Settings
Your computer may connect to the Internet via proxy. If this is your case, you need to specify the proxy address and port in LoadComplete settings. If you are not sure whether you connect through a proxy server or not, ask your system administrator.
You need to configure the proxy settings only once:
Select Tools > Options from LoadComplete’s main menu. This will invoke the Options dialog.
In the dialog, select the Network > Proxy category on the left.
Select Manual Proxy Configuration from the Mode drop-down list.
If your proxy server requires authentication, specify your user name and password that will identify you on your proxy server.
If your tests simulate virtual users on remote computers or on Amazon cloud computers, and you want them to use the same proxy, enable the Use proxy settings for remote agents option in the Simulating > General category.
Filtering Domains and Applications
By default, LoadComplete records all the requests sent from your computer to the Web. To avoid having unwanted traffic in recorded scenarios, you can specify the domains and applications the traffic to which you want to record, or, alternatively, you can specify the domains and applications to ignore. You can do this using the Filter settings (Tools > Options > Recording > Filters). After you define the filters, LoadComplete will record traffic only from the domains and applications that match these filters.
Defining Data Correlation Rules
If your web application uses dynamic parameters to pass data, you may want to create correlation rules for these parameters before you start recording. You can also skip this step and correlate dynamic parameters after you record the scenario. If you are not sure whether your web application uses dynamic parameters or what these parameters are, you can ask the application developers.
LoadComplete includes a number of data correlation rules for dynamic parameters used by various frameworks and applications. To view or change them:
Select Tools > Options from LoadComplete’s main menu. This will open the Options dialog. In the dialog, go to the Recording > Data Correlation category.
Find the rule that controls the correlation of dynamic parameters in your web application and make sure the rule is enabled and works as expected. Modify the rule if needed.
To correlate cookies, enable the Common/Cookie rule.
If LoadComplete does not have a predefined rule for dynamic parameters in your application, create the needed rule. See Creating Custom Data Correlation Rules Manually.
Checking If the LoadComplete Service Is Running
To record traffic, LoadComplete uses the LoadComplete Remote Agent (LCRAS4 in Task Manager) service running on your computer. The service starts automatically. If you experience issues with starting recording, check if the service is running. You can do this in the Windows Control Panel.