Installation command line options
You can use the Windows command line to install the products. The CLI uses
- The full installation can be launched using the setup.exe file. For details, see Installing the full package from the wrapper file.
- The installations of standalone applications and additional components can be launched using PFTW files. For details, see Installing from a PFTW file.
Installing the full package from the wrapper file
You can do a full install from the installation wrapper file, setup.exe, located in \lrunner\<your_language> folder of your installation package. The following command line options are available:
Option | Description |
---|---|
/s | Runs the installation in the background (silently), with no user interaction. |
/qb | Runs the installation in unattended mode, with limited user interaction. |
/InstallOnlyPrerequisite |
Installs only the prerequisites – does not install any OpenText Professional Performance Engineering components. By default, the setup program checks that your machine has the required prerequisites, and installs them if necessary, before installing the components. |
You can set public properties for the command line installation, using the following syntax:
setup.exe PROPERTY_NAME="value"
The following properties are available:
Property name | Description |
---|---|
INSTALLDIR="your_path" | Specifies the location where the application will be installed. |
REBOOT_IF_NEED |
1: Reboots the machine after installation, if required. This is recommended if you include the NV installation. 0: Does not reboot the machine after installation. Default: 0 |
NVINSTALL |
Empty string: Excludes the installation of the NV component. Y: Includes the installation of the NV component. Default: Y |
INSTALL_NV_MODE |
1: Sets the NV installation mode to Typical. 2: Sets the NV installation mode to Custom. Default: Typical |
INSTALL_DIR="your_path" | Specifies a path for the installation. |
START_LGA |
Empty string: Instructs the machine not to start the load generator after installation. 1: Instructs the machine to start the load generator after installation. Default: 1 |
IS_RUNAS_SERVICE |
0: OpenText Professional Performance Engineering mode, runs the load generator's agent as a process. 1: OpenText Enterprise Performance Engineering mode, runs the load generator's agent as a service. 2: (Relevant for OneLG only) OpenText Core Performance Engineering mode, runs the load generator's agent as a service, and triggers launch of agent configuration at the end of the installation. Default: 1 |
INSTALL_GATLING |
0: Does not install Gatling on the load generator. 1: Installs Gatling on the load generator. Default: 0 |
INSTALL_JMETER |
0: Does not install JMeter on the load generator. 1: Installs JMeter on the load generator. Default: 0 |
SECURE_CONNECTION |
0: Configures the agent to run in non-SSL mode. 1: Configures the agent to run in SSL mode. Default: 1 |
SKIP_CHECK_PRIVILEGE |
0: The installation process checks the install path for access privileges. 1: The installation process skips the access check for the install path. Default: 0 |
Example:
The following command performs the installation silently and then reboots the machine if necessary:
DVD\lrunner\en\setup.exe /s REBOOT_IF_NEED="1"
Installing from a PFTW file
You can install
Double-click on the packaged file, or run it from the command line using the following options:
Option | Description |
---|---|
/s | Runs the installation in the background (silently), with no user interaction. |
/e | Only extracts the installation files; does not run them. |
/f |
Specifies the path of a temporary folder for file extraction. For example: If you leave out this option, the default temporary folder is used. |
/a |
Allows you to pass parameters or properties to the autorun file, such as Use the properties defined above (in the wrapper file section) for the setup.exe file. |
Note: Silent installation for VuGen and OneLG: If you need to insert a quotation mark character into the command line parameter, use two consecutive quotation marks.
The following commands silently run setup, and install the application in the specified folder. Where relevant, they also start the agent after installation:
-
Examples for SetupVuGen.exe and SetupOneLG.exe:
SetupOneLG.exe -s -sp"/s" INSTALLDIR=""C:\Program Files (x86)\OpenText\LoadRunner OneLG"" IS_RUNAS_SERVICE=0 START_LGA=1 NVINSTALL=N"
SetupVuGen.exe -s -sp"/s" INSTALLDIR=C:\VuGen"
-
Examples for other standalone applications:
SetupAnalysis.exe /s /a /s INSTALLDIR="C:\Analysis"
SetupMIListener.exe /s /a /s INSTALLDIR="C:\MiListener"
SetupMoFW.exe /s /a /s INSTALLDIR="C:\MoFW"
See also: