a Windows-based machine
Performing Path Translation
LoadRunner Controller User's Guide (Windows)
337
The Script window contains a list of all the Vuser scripts associated with a
scenario--and their locations. A script's location (path) is always based on the
Controller host's mapping of that location. If a Vuser host maps to the script's path
using a different name--path translation is required.
For example, assume that the Controller is running on a Windows-based machine
named
pc2
, and that a Vuser script is located on a network drive.
The Controller
machine maps the network drive as
m
:\lr_tests. If the remote machine hosting the
Vusers also maps the path as
m
:\lr_tests, no translation is necessary
.
However, if
the remote machine maps the path as another drive or path, for example
r
:\lr_tests,
you must translate the path to enable the Vuser host to recognize the script
location.
Similarly, when saving run-time result files to a shared drive that is mapped
differently by the Controller and remote host, you must perform path translation.
Path translation is also effective across platforms--between Windows and UNIX.
You use path translation to translate Windows-based paths (as seen by the
Controller) into paths recognized by the UNIX Vuser host.
