Upgrading Vuser Scripts for VTS
Significant changes were made to VTS in LoadRunner version 11.52. When upgrading to VTS 11.52 or later, these changes may create various compatibility issues. In order to describe the VTS upgrade options, the following terms will be used to refer to the versions of VTS:
|VTS-New||Versions of VTS that were released with LoadRunner 11.52 or later. VTS-New connects to the new VTS Server that has a web interface. With VTS-New, it is not necessary to reference any additional files from the Vuser script.|
Versions of VTS that were released prior to the release of LoadRunner 11.52. VTS-Old connects to a Windows application, vtconsole.exe, which is the VTS Server. With VTS-Old, the Vuser script must include the vtc2.h header file and load the vtclient.dll library.
Depending on the version of VTS with which a Vuser script originally worked, and the version of VTS with which you now want to use the Vuser script, you may be required to perform certain modifications to the Vuser script to resolve the compatibility issues. The various upgrade scenarios are described below.
Note: If you have a Vuser script that originally worked with VTS-Old, it is necessary to modify the Vuser script to enable the script to work with VTS-New. For details, see below.
|Version of VTS with which the Vusers script originally worked||Version of VTS that you now want to use with the Vuser script||
Action Required to Upgrade
No changes to the Vuser script are required. The script includes the vts2.h header, and dynamically loads the vtclient.dll file.
|VTS-New||VTS-Old||No changes to the Vuser script are required. The script includes the vts2.h header, and dynamically loads the vtclient.dll file.|
|VTS-New||VTS-New||No changes to the Vuser script are required. The script calls the VTS API's directly from the Vuser script, without including the vts2.h header file, and without loading the vtclient.dll file explicitly. Unlike with previous versions of VTS, with the current version, it is not necessary to reference any additional files from the Vuser script.|
Note: If the script includes an lrvtc_connect function, the function now returns the error code instead of the PVCI handle. Therefore, check the return code instead of using vtc_get_last_error to check the error.
After you make changes to the script, the script should point to the new VTS server. If the new VTS server is located on different server, update the VTS server name and port number in all vtc_connect and lrvtc_connect functions in the Vuser script.