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>]

where:

  • controller_host is the name or type of the machine that is running the Controller.

  • The value of controller_host can be:

    • <hostname>. The name of the machine running the Controller, for example, LOADPC1

    • win. The Controller is running on a Windows-based computer

  • controller_path is the path of a specific folder—as recognized by the Controller. For example, if the folder scripts is located on the network drive r—as mapped by the Controller—type the path r:\scripts in the controller_path field.

  • remote_path is the 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 n:\scripts in the remote_path field.

    If a Vuser on the remote Linux load generator recognizes the above path as /m/tests, you would type this path in the remote_path field.

  • remote_host is the name or type of the remote load generator. For example, if all the remote machines are Linux workstations, you could type Linux in the remote_host field. The options for the remote_host field are the same as the options for the controller_host field, listed above. The remote_host parameter is optional.

Examples

The examples below show the use of the Path Translation table for a Windows-based Controller called Merlin.

  • Example 1: Vusers are running on a Windows 2003 machine, Oasis. Merlin maps the network drive as f:, while Oasis maps it as g:\loadtest.

    merlin f:\ g:\loadtest\ Oasis

  • Example 2: Vusers are running on a Linux machine, Ultra. Ultra maps the networks drive as /u/tests/load.

    merlin f:\ /u/tests/load/ Ultra

  • Example 3: The mapping of the network drive by the remote load generator Jaguar, is identical to the 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 m:\loadtest.

    merlin l:\mnt\ m:\loadtest\ win

Back to top