Path translation might be required when storing scripts and runtime data results from a scenario on a shared network drive (Tools > Options > Runtime File Storage tab).
What is path translation?
Path translation is a mechanism used by LoadRunner Professional to convert a remote path name for Controller so that all participating machines recognize the same network drive.
Example 1. The scenario runs on a Windows-based machine and includes multiple Vusers running on both Windows-based and Linux load generators. One remote load generator may map the network drive as F, while another load generator maps the same drive as H. In a complex situation such as this, you need to ensure that all participating load generators recognize the same network drive.
Example 2. The Scenario Groups/Scripts pane in the Design view 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 machine's mapping of that location. If a load generator maps to the script's path using a different name, path translation is required.
For example, assume that the scenario 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 load generator 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 load generator to recognize the script location.
Note: If the Controller and load generator machines are all Windows machines, consider using the Universal Naming Convention method instead of manually adding path translation information. On Windows machines, you can tell Controller to convert all paths to UNC, in which case all the machines are able to recognize the path without requiring path translation. An example of UNC format is
You add path translation entries in the Path translation table.
To translate a path from one Windows-based computer to another, or between Windows-based and Linux machines, you create an entry in the Path Translation table. This table contains a list of paths translated into formats that can be recognized by different machines.
Each line of the Path Translation table has the following format:
<controller_host> <controller_path> <remote_path> [<remote_host>]
Name or type of the machine that is running Controller.
The value of controller_host can be:
Path of a specific folder—as recognized by Controller.
For example, if the folder scripts is located on the network drive r—as mapped by Controller—type the path
Path of a specific folder—as recognized by the remote machine.
For example, if the folder scripts is located on the network drive n—as mapped by the remote load generator—type the path
If a Vuser on the remote Linux load generator recognizes the above path as
Name or type of the remote load generator.
For example, if all the remote machines are Linux workstations, you could type
The examples below show the use of the Path Translation table for a Windows-based Controller called
Example 1: Vusers are running on a Windows 2003 machine,
Oasis. Merlin maps the network drive as
Oasismaps it as
merlin f:\ g:\loadtest\ Oasis
Example 2: Vusers are running on a Linux machine,
Ultramaps the networks drive as
merlin f:\ /u/tests/load/ Ultra
Example 3: The mapping of the network drive by the remote load generator
Jaguar, is identical to Controller's mapping, so no translation is required. This line can be excluded from the Path Translation table.
merlin n:\ n:\ Jaguar
Example 4: All Windows-based Vuser load generators map the network drive as
merlin l:\mnt\ m:\loadtest\ win