TruWeb installation and configuration

This topic describes TruWeb installation, and how to customize the default configurations.

For instructions on installing the Proxy Recorder (for TruWeb Standalone), see TruWeb Proxy Recorder.



To install the standalone version of TruWeb:

  1. Prerequisite for Windows: Visual Studio 2015 redistributable package (
  2. Download the appropriate TruWeb .zip file for your environment from the AppDelivery Marketplace.
  3. Unpackage the file to a local folder on the machine where you will be creating and running TruWeb scripts.
  4. Define an environment variable called TRUWEB_PATH, whose value is the location of the TruWeb installation (for example, for Windows: C:\TruWeb). This allows integration of the standalone version of TruWeb into other tools (for example,

    For Linux, define this environment variable in the relevant .rc file in your home directory.

    For MacOS, define this environment variable in the relevant .bash_profile file in your home directory. If this file does not exist, create it.


When you install your Micro Focus testing tool (LoadRunner/Performance Center version 12.60 and later), TruWeb is installed and the required TRUWEB_PATH environment variable is automatically created.

Note: Only one instance of TruWeb can run at any time.

Back to top

TruWeb configuration

TruWeb is installed with a configuration file, config.yml (located in the TruWeb installation folder) that contains the default configurations for running the TruWeb application. Information about the configuration settings is included alongside each setting in the file.

Note: This file must not be modified.

If you want customize the configuration, you can create a local configuration file whose customized settings will take precedence over the default configuration settings when running TruWeb.

To customize the TruWeb configuration:

  1. Create a new file, called local.config.yml, in the TruWeb installation folder.
  2. Populate local.config.yml only with the configuration settings that you want to customize, using config.yml as a reference.

Back to top

See also: