LoadRunner

Enterprise
Software version: 2023-2023 R1

Installation Guide
Go to Help Center online
https://admhelp.microfocus.com/lre/
Installation Guide

Document release date: October 2023

Send Us Feedback
Let us know how we can improve your experience with the
Installation Guide.
Send your email to: docteam@microfocus.com

Legal Notices
© Copyright 2023 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors
(“Open Text”) are as may be set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional
warranty. Open Text shall not be liable for technical or editorial errors or omissions contained
herein. The information contained herein is subject to change without notice.
Disclaimer
Certain versions of software accessible here may contain branding from Hewlett-Packard
Company (now HP Inc.) and Hewlett Packard Enterprise Company. This software was
acquired on September 1, 2017 by Micro Focus and is now offered by Open Text, a separately
owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE
marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the
property of their respective owners.

LoadRunner Enterprise (2023-2023 R1) Page 2 of 194

Installation Guide

Contents
Welcome to this guide 7

Installation overview 8
Before you install 9
LoadRunner Enterprise components and data flow 10
Architecture and components 11
Applications 13
Communication paths 14
Load considerations 18
Distributed Denial of Service attack protection 20
Clustered configuration 20
System component considerations 22
Windows system locale considerations 26
Required services 27
Pre-installation prerequisites and considerations 28
Database prerequisites 29
Oracle Database servers 30
Microsoft SQL Database servers 35
PostgreSQL Database servers 36
Installation package details 39

Pre-installation project migration steps 40

Project migration pre-installation activities 41
Pre-installation project migration considerations 41
Upgrade existing Performance Center/ALM projects to LoadRunner Enterprise 42
Back up projects in existing ALM installation 43
Overview of migration process 44

Installation and configuration 46

Install LoadRunner Enterprise 47
Installation flow 48
Upgrade LoadRunner Enterprise 50
Install and configure LoadRunner Enterprise servers and hosts 50
Install a LoadRunner Enterprise server or host 51
Configure a LoadRunner Enterprise server or host 55
Secure communication and the system user 70
Overview 70
Update the Communication Security passphrase 71
Change the system user 71

LoadRunner Enterprise (2023-2023 R1) Page 3 of 194

Installation Guide

System Identity Changer Utility 74

Configure a non-administrator system user 78
Required policies for the system user 79
Troubleshoot System Identity Changer and system user issues 80
Error running the System Identity Changer utility 80
Unable to connect to the LoadRunner Enterprise Server 80
Error changing the system user 81
Unable to reconfigure LoadRunner Enterprise hosts or servers 83
Denied access to the internal Influx database server 84
Post-installation configuration steps 84
Configure LoadRunner Enterprise servers and hosts post-installation 84
Log on to LoadRunner Enterprise Administration 85
Perform site and lab administration tasks 86
Change the database administrator and user passwords 88
Install LoadRunner Enterprise silently 89
Prerequisite software for silent installation 89
Customize silent installation 91
Silently install LoadRunner Enterprise server and hosts 93
Notes and limitations 97
Deploy LoadRunner Enterprise on AWS 98
Install standalone components (Windows) 99
Available standalone components for Windows 99
Install standalone components 100
Silently install standalone applications 101
Install Load Generator on Linux 103
Deploy Dockerized load generators on Linux 104
Prerequisites 104
Run a Dockerized load generator using the predefined image 105
Run a Dockerized load generator using a custom image 107
After running the load generator containers 108
Tips and guidelines 108
Deploy Dockerized load generators on Windows 109
Prerequisites 110
Run a Dockerized load generator using the predefined image 110
Run a Dockerized load generator using a custom image 111
Examples of customized content for Dockerfiles 113
After running the load generator containers 114
Tips and guidelines 114
Install additional components 114
Uninstall LoadRunner Enterprise server and hosts 116
Uninstall Load Generator from Linux 117
Post installation verification 118
LoadRunner Enterprise configuration options 121

LoadRunner Enterprise (2023-2023 R1) Page 4 of 194

Installation Guide

Configuring LoadRunner Enterprise to work with TLS/SSL 122

TLS/SSL configuration workflow 122
Configure IIS to work with TLS/SSL 124
Distribute certificates 127
Configure the LoadRunner Enterprise server to work with TLS/SSL 128
Configure LoadRunner Enterprise hosts to work with TLS/SSL 131
Configure LoadRunner components to work with TLS/SSL 136
Configure TLS/SSL for load generators 137
Create and copy digital certificates 137
Enable TLS communication for load generators in LoadRunner Enterprise
Administration 140
Working with the LoadRunner Enterprise agent 140
Run the LoadRunner Enterprise agent as a process 141
Run the LoadRunner Enterprise agent as a service 141
Configure the agent on load generator machines 141
Map network drives when running the agent as service 142
LoadRunner Remote Management Agent 142
Recommended configuration for Linux load generators 143
Recommended change to the TEMP folder used by the load generator 143
Enable downloading standalone applications 144
Customize the Download Applications window 145
Enable MS-SQL Windows authentication 146

Working with firewalls 147

Using firewalls 148
About using firewalls in LoadRunner Enterprise 149
Example of over firewall deployment 151
Set up the system to use firewalls: basic steps 152
Install over firewall components 154
Initial configuration of the over firewall system 154
Set up your deployment (TCP or TCP over proxy) 155
Configure the firewall to allow agent access 156
TCP configuration 156
TCP over proxy configuration 156
Local System account configuration 157
Configure the MI Listener 157
Specify MI Listeners 159
Run Vusers over a firewall 161
Run Vusers over a firewall: basic steps 162
Configure hosts to run Vusers over a firewall 163
Monitor over a firewall 166
Monitor over a firewall: basic steps 167
Configure monitor settings 168

LoadRunner Enterprise (2023-2023 R1) Page 5 of 194

Installation Guide

Clone a monitored server's properties 171

Add and remove measurements 172
Configure measurement frequency 172
Configure the project to receive monitor over firewall information 173
Edit monitor over firewall machines during a test run 174
Configure the LoadRunner Enterprise agent 175
Configure LoadRunner Enterprise agents over the firewall: basic steps 176
Configure the Windows LoadRunner Enterprise agent 176
Configure and run the Linux LoadRunner Enterprise agent 178
Agent configuration settings 179
Check connectivity 181

Troubleshooting 184
Troubleshooting installation issues 185

LoadRunner Enterprise (2023-2023 R1) Page 6 of 194

Welcome to this guide
This OpenText™ guide describes how to install and set up LoadRunner
Enterprise 2023 or any later minor release (they are all full installations).

LoadRunner Enterprise is a cross-enterprise tool for planning and running multiple

performance test projects across different geographic locations. Using
LoadRunner Enterprise, you can stress your applications to isolate and identify
potential client, network, and server bottlenecks.

Note: If your organization has firewall restrictions that prevent you from
using the online Help Center, you can download and deploy the Help Center
on your local server. For details, see the Download Help Center instructions
in the LoadRunner Enterprise Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 7 of 194

Installation overview

LoadRunner Enterprise (2023-2023 R1) Page 8 of 194

Before you install
This chapter provides information to prepare you for the LoadRunner Enterprise
component installations.

This chapter includes:

• LoadRunner Enterprise components and data flow 10

• System component considerations 22
• Windows system locale considerations 26
• Required services 27
• Pre-installation prerequisites and considerations 28
• Database prerequisites 29
• Installation package details 39

LoadRunner Enterprise (2023-2023 R1) Page 9 of 194

Installation Guide
Installation overview

LoadRunner Enterprise components and data

flow
This section describes the LoadRunner Enterprise system.

This section includes:

l "Architecture and components" on the next page

l "Applications " on page 13
l "Communication paths" on page 14
l "Load considerations" on page 18
l "Distributed Denial of Service attack protection" on page 20
l "Clustered configuration" on page 20

LoadRunner Enterprise (2023-2023 R1) Page 10 of 194

Installation Guide
Installation overview

Architecture and components

This section describes the architecture and components of LoadRunner
Enterprise.

Architecture/Component Description

Database server The database server stores four types of

schemas:
l Site Management schema. Stores information
related to each tenant in the system, including
users and site management tasks. A row exists
in this schema for each tenant you create.
l Site Administration schema. Stores

information related to the LoadRunner

Enterprise system, such as domains, users, and
site parameters. A row exists in this schema for
each project you create. Irrespective of how you
configure your system, there is always only one
Site Administration schema.
l Lab Management. Stores lab information
related to managing lab resources (such as
hosts and host pools), and for managing
LoadRunner Enterprise assets (such as
LoadRunner Enterprise server, licenses, and
usage reports). There is always only one Lab
Management schema.
l Project schemas. Stores project information,

such as entity data and user data. A separate

schema exists for every project you create.
The schemas can reside on an Oracle, Microsoft
SQL, or PostgreSQL server.
Note: To improve system performance, it is
advisable that the LoadRunner Enterprise server
and the Database server be installed on separate
machines and be connected over LAN.

LoadRunner Enterprise (2023-2023 R1) Page 11 of 194

Installation Guide
Installation overview

Architecture/Component Description

Project repository Stores all files to be used by all the projects in the
system. For example, scripts, run results, .xml
files, templates, and attachments. By default the
repository is located on the same machine as the
application server, which is useful for smaller
setups. For larger organizations however, or when
working in a clustered environment, it is advisable
to install the repository on a dedicated machine.
When working in a clustered environment, the
repository must be accessible by all nodes.

LoadRunner Enterprise Hosts the LoadRunner Enterprise Web pages that

Server enable you to design performance tests, configure
monitors, reserve testing resources, run and
monitor test runs, and analyze test results.

LoadRunner Enterprise The center for managing lab resources (such as

Administration hosts and host pools), and for managing
LoadRunner Enterprise assets (such as
LoadRunner Enterprise servers, licenses, projects,
runs, timeslots, and usage reports).
Also used for managing cloud settings when using
cloud hosts in LoadRunner Enterprise, and
automated maintenance of the system's key
components to detect system failures.

LoadRunner Enterprise (2023-2023 R1) Page 12 of 194

Installation Guide
Installation overview

Architecture/Component Description

LoadRunner Enterprise Used to control performance tests, generate load,

Hosts and analyze data. LoadRunner Enterprise hosts
can be configured as Controllers, load generators,
or data processors:
l Controller. The manager of a performance test.
The Controller receives scripts, runtime
settings, and a list of load generators to use. The
Controller issues instructions to the load
generators including which scripts to run, how
many Vusers to run per script, and scheduler
settings. At the conclusion of the test run, the
Controller collates the data. There is only one
Controller per performance test.
l Load Generator. Generates load by running
virtual users (Vusers). The Controller dictates
the manner in which they start and stop running.
There can be any number of load generators for
a given test.
l Data Processor. Used for analyzing and
publishing performance test results.

Applications
The following standalone applications integrate with your LoadRunner Enterprise
system:
Application Description

Analysis Provides graphs and reports with in-depth performance analysis

information. Using these graphs and reports, you can pinpoint
and identify the bottlenecks in your application and determine
what changes need to be made to your system to improve its
performance.

MI Listener Needed when running Vusers and monitoring applications over a

firewall.

Monitors Used to monitor servers that are located over a firewall.

Over Firewall
Agent

LoadRunner Enterprise (2023-2023 R1) Page 13 of 194

Installation Guide
Installation overview

Application Description

OneLG A combined (standalone) load generator installer for all of the

LoadRunner family products.
Virtual User Generates Vusers by recording actions that typical end-users
Generator would perform on your application. VuGen records your actions
(VuGen) into automated Vuser scripts which form the foundation of your
performance tests.

Use the diagram and table in the "Communication paths" below and "Load
considerations" on page 18 sections to determine which machines to allocate for
which performance testing tasks.

For example, you can combine a number of applications that have a light load on a
single machine. For details on which standalone applications can be installed
together, see the Support Matrix (System Requirements) in the LoadRunner
Enterprise Help Center.

For information on installing the standalone applications, see "Install standalone

components" on page 100.

Communication paths
When installing LoadRunner Enterprise, it is important to consider the
communication paths between the various components, and their resource
demands.

When running a performance test, components share information with LoadRunner

Enterprise via a distinct system of communication. Understanding which
components communicate with one another and the method of communication is
essential for configuring your system.

LoadRunner Enterprise (2023-2023 R1) Page 14 of 194

Installation Guide
Installation overview

The following diagram illustrates the LoadRunner Enterprise communication paths

in an advanced deployment:

Note:
l To view other deployment options that can be used for configuring
LoadRunner Enterprise on-premises or on the cloud, see LoadRunner
Enterprise Deployments in the LoadRunner Enterprise Help Center.
l If the installation cannot use a default port because it is already in use, you
can change the port. For details, see Installing One of the Components
Cannot Use Default Port: Port Already in Use.
l You cannot have a firewall between the LoadRunner Enterprise server,
LoadRunner Enterprise hosts (used as Controllers), and MI Listener.
l Port 8182 from LoadRunner Enterprise host to load generators is relevant
when running NV emulation for viewing NV related graphs during online. If

LoadRunner Enterprise (2023-2023 R1) Page 15 of 194

Installation Guide
Installation overview

the port is closed, graphs are still available in the offline results and
Analysis report.
l Connections from APM tools to the AUT are not displayed in the diagram.
Each AUT tool uses its own ports, which can be found in the corresponding
product’s documentation.
l When using a load balancer for LoadRunner Enterprise servers:
l The load balancer needs to be configured for sticky sessions based on
the HTTP cookie ASP.Net_SessionId.
l You need to configure WebSocket on the load balancer. However, if you
have SSL configured on the load balancer only (and not on LoadRunner
Enterprise servers), you need to terminate SSL for WebSocket on the
load balancer.

The following table displays the connection ports that must be opened for the
incoming traffic on the various LoadRunner Enterprise components:

Component Ports

LoadRunner HTTP (80) * **

Enterprise
Server

LoadRunner Enterprise (2023-2023 R1) Page 16 of 194

Installation Guide
Installation overview

Component Ports

LoadRunner HTTP (8731)

Enterprise
TCP (3333, 54245, 54345)
Host
8182 for LoadRunner Enterprise hosts used as Load Generators
to see online graphs for NV emulation information. If the port is
closed, you can still see NV information in the offline results.
8731 for LoadRunner Enterprise server to communicate with the
Load Testing Operator service that orchestrates the test.
8086 for LoadRunner Enterprise server/host to get online/offline
analysis data. The port should be open for outgoing
communication from the LoadRunner Enterprise server, and for
incoming communication for the LoadRunner Enterprise host
(for an internal database). For an external database, the port
should be open for both incoming and outgoing communication
from the LoadRunner Enterprise server and LoadRunner
Enterprise host.
54345 for LoadRunner Agent Service. Enables the Controller to
connect to this host when it acts as a Load Generator.
54245 for LoadRunner Remote Management Agent Service.
Enables LoadRunner Enterprise server to perform lab
maintenance operations on this host.
3333 for LoadRunner Data Collection Agent. Enables
LoadRunner Enterprise to control the machine routing table
during test execution, based on the definitions set in Target IPs
in the project settings. It also enables getting resource utilization
metrics while a test is running.

Database TCP 1433 (SQL), 1521 (Oracle) **, 5432 (PostgreSQL) **

Repository NetBIOS

Standalone TCP (54245, 54345)

Load
8182 to see online graphs for NV emulation information. If the
Generator
port is closed, you can still see NV information in the offline
results.

Cloud-based As defined in the Cloud Network Settings dialog box. For details,
Load see Initial cloud settings in the LoadRunner Enterprise Help
Generator Center.

LoadRunner Enterprise (2023-2023 R1) Page 17 of 194

Installation Guide
Installation overview

Component Ports

MI Listener HTTP/TCP for load generator only: 443 **

TCP for LoadRunner Enterprise server and host (used as a
Controller) only: 50500

Application Any; HTTP (Random)

under test

SiteScope - HTTP (8080) *

Topology

SiteScope - HTTP (8888) *

Monitor
Profiles

* HTTPS is also supported on this component.

** Default values that can be changed during configuration.

Load considerations
The following table provides some basic installation considerations for each
LoadRunner Enterprise component:

Quantity in the
Machine system Load Considerations

LoadRunner At least one. Heavy load.

Enterprise
Also supports To balance the load, you can install and
Server
cluster configure external load balancers to work with
configuration. LoadRunner Enterprise.
For details, see
For additional load balancing support, you can
"Clustered
install multiple LoadRunner Enterprise
configuration"
Servers.
on page 20.

LoadRunner Enterprise (2023-2023 R1) Page 18 of 194

Installation Guide
Installation overview

Quantity in the
Machine system Load Considerations

LoadRunner At least one of Controller has heavy load.

Enterprise each.
Load generator has medium load.
Hosts:
Controller, Data processor has medium to high load.
Load
Generator, It is recommended to designate spare
and Data Controllers and load generators for fault-
Processor tolerance and high availability purposes.
Note:
l You can configure a host as a Controller +
Load Generator, but this is not
recommended because running Vusers
consumes a lot of resources. Running
Vusers on the Controller host is only
appropriate for performance tests that have
a very small number of Vusers.
l You can configure a host as a Controller +
Data Processor, but this is not
recommended because data processing
might consume high amounts of CPU and
resources.

MI Listener At least one, if Medium load.

you are l Standalone installation is required.
monitoring over
a firewall. l Cannot exist on a machine running IIS.

Monitor Over At least one, if Light load.

Firewall you are
Standalone installation is required.
machine monitoring over
a firewall.

SiteScope One Light load.

(optional)

Tip: You should also consider the communication paths between the various
components when installing LoadRunner Enterprise, and their resource
demands. This information helps you configure your system to evenly
distribute the load, and prevent overloading any particular resource. For
details, see "Communication paths" on page 14.

LoadRunner Enterprise (2023-2023 R1) Page 19 of 194

Installation Guide
Installation overview

Distributed Denial of Service attack protection

Consider implementing DDoS attack protection on servers hosting LoadRunner
Enterprise Web client only in cases where your LoadRunner Enterprise Web client
is exposed to the public Internet. In most production environments, deploying
LoadRunner Enterprise Web client on the public Internet are rare so carefully
consider if this best practice applies to your specific deployment.

A few DDoS attacks such as Slowloris may be mitigated by implementing third

party protections such as the following:

l Setting request limits.

l Setting header limits.
l Restricting IP addresses.
For details, see the Microsoft documentation.

In addition, you can also apply restrictions, such as setting timeouts and header
limits, in the PCWEB\Web.config and PCWEB\PCX\Web.config files.

Note: Due to the nature of these attacks, it is not possible to implement

application-specific fixes or enhancements to prevent these types of
attacks.

Clustered configuration
LoadRunner Enterprise can be run on a single node cluster. A cluster is a group of
application servers that run as if they were a single system. Each application server
in a cluster is referred to as a node.

Clusters provide mission-critical services to ensure maximum scalability. The load

balancing technique within the cluster is used to distribute client requests across
multiple application servers, making it easy to scale to an infinite number of users.

Take the following into consideration when setting up a clustered environment:

l All nodes must have access to the database server on which you configure the
system.

LoadRunner Enterprise (2023-2023 R1) Page 20 of 194

Installation Guide
Installation overview

l All nodes must have access to the repository. For example, if the repository is
located on the first node in the cluster, all other nodes must have access to the
first node. If you install the repository on a dedicated machine, each node must
have access to that machine.
l The load balancer must be configured with session persistency. Set the
persistency to sticky session enabled or destination address affinity,
depending on the load balancer.
The following diagram illustrates a clustered LoadRunner Enterprise system
configuration:

Prerequisites for clustering

You can install LoadRunner Enterprise on a single node or as a cluster. This section
describes the prerequisites for installing LoadRunner Enterprise as a cluster on a
Windows environment.

LoadRunner Enterprise (2023-2023 R1) Page 21 of 194

Installation Guide
Installation overview

l Check with your system administrator whether you are installing LoadRunner
Enterprise on a single node or as a cluster.
l If you are installing LoadRunner Enterprise on cluster nodes, verify which
machine to use as the first node to start the installation and the number of
machines you should use. This depends on the number of users and availability
considerations.
l When creating a common repository for the cluster nodes, the folder must be
shared with the domain user used for configuring the cluster nodes.
l The LoadRunner Enterprise account should be set with a domain user that has
the correct permissions for setting a cluster environment; the IUSR_METRO user
does not have permissions on a remote repository or on the IIS web server of the
first node and on hosts.
l Configure each cluster node with the same domain/user as provided in the first
node. The name is case sensitive.
l Configure each node with the same Site Administration and Lab database
schema names (not just the same database server).
This is important because when a node is installed in cluster mode, the Lab
schema name is not read from the common repository. For example, if node A is
installed with schema names LRE_ADMIN_MYSCHEMA and LRE_LAB_
MYSCHEMA, when node B is installed, the schema names is automatically
populated in the Configuration wizard with LRE_ADMIN_MYSCHEMA and LRE_
DEFAULT_LAB_DB.
Therefore, you need to manually change the Lab database schema name from
LRE_DEFAULT_LAB_DB to LRE_LAB_MYSCHEMA.
l You must use the same communication passphrase on all nodes.
For details on installing LoadRunner Enterprise as a cluster, contact OpenText
support.

System component considerations

The LoadRunner Enterprise system includes several components. This section
provides pre-installation considerations for each of the components.

LoadRunner Enterprise (2023-2023 R1) Page 22 of 194

Installation Guide
Installation overview

For system requirement details for each component, see the Support Matrix
(System Requirements).

LoadRunner Enterprise (2023-2023 R1) Page 23 of 194

Installation Guide
Installation overview

LoadRunner l Uninstall any 12.6x or earlier installations of the LoadRunner

Enterprise Enterprise Server (formerly Performance Center Server) from
Server your machine. Also make sure that Network Virtualization was
uninstalled, or uninstall it manually.
l You can install LoadRunner Enterprise 2023.x as a full

installation, or over an existing LoadRunner Enterprise 2020.x

installation. If installing as a full installation, we recommend
installing the LoadRunner Enterprise Server on a clean
machine with a new image.
l To install a LoadRunner Enterprise Server, you must have full

local administrative rights on the designated machine.

l The LoadRunner Enterprise Server requires a specific

Windows user to be defined on the machine. When using the

default user or a custom local user, the user is created on the
machine and is added to the Administrator group. Ensure that
there is no security system in place that prevents creating the
user or that removes the user from the Administrators group.
For details on how to create this user, see "Install and
configure LoadRunner Enterprise servers and hosts" on
page 50.
l Microsoft Windows Script Host should be version 5.6 or later.

To verify the version number, navigate to the <Windows

installation directory>\Windows\system32 directory. Right-
click wscript.exe and select Properties. In the Version tab,
verify the file version number.
IIS:
l Before you install the LoadRunner Enterprise Server, you must
install Microsoft Internet Information Services (IIS 8.0/8.5/10).
Note: For better security, we recommend you follow the
Microsoft IIS security best practices to harden your IIS web
server.
l You must allow LoadRunner Enterprise file extensions in IIS.
To do so, open IIS Manager. Under the IIS section for the
LoadRunner Enterprise Server application, open Request
Filtering. Click Edit Feature Settings and clear the Allow
unlisted file name extensions option so only file extensions
that are explicitly defined are used. Add the following to the
list of allowed file extensions: : .html, .js, .css, .map, .aspx,
.ascx, .ash, .asmx, .eot, .otf, .ttf, .woff, .woff2, .json, .svg, .svc,
.xml, .png, .jpg, .jpeg, .gif, .axd, .ico, and . (to include paths
with no extension).
l During installation, some IIS features are updated on all

LoadRunner Enterprise (2023-2023 R1) Page 24 of 194

Installation Guide
Installation overview

LoadRunner Enterprise Servers using IIS.

l The following features are enabled: Active Server Pages,

ASP.NET 4.5 (IIS 8.0/8.5), ASP.NET 4.6 (IIS 10), Metabase,

Static content, IIS 6.0 Management Compatibility, and
Dynamic Compression.
l The following feature is disabled: URL Authorization

Oracle:
l Ensure that the Oracle client installed on the LoadRunner
Enterprise server is at least the same version as on the Oracle
server, and that connectivity is established with the Oracle
server.
l Only a 64-bit Oracle client installation is required.
l If you install the Oracle client after installing the LoadRunner
Enterprise Server, you must restart the machine after
installing the Oracle client.
l Oracle Monitoring: When defining Oracle monitors, install the
LoadRunner Enterprise Server in a directory whose path does
not include any of the following characters: ( ) : ; * \ / " ~ & ? { }
$ % | < > + = ^ [ ]. For example, on a 64-bit machine, do not
install the LoadRunner Enterprise Server in the default
installation directory (C:\Program Files (x86)\....), as this path
includes illegal characters.

LoadRunner l To install a LoadRunner Enterprise Host, you must have full

Enterprise local administrative rights on the designated machine.
Host l The LoadRunner Enterprise Host requires a specific Windows
user to be defined on the machine. This user is configured
when adding the Host to LoadRunner Enterprise
Administration. When using a default user or a custom local
user, the user is created on the machine and added to the
Administrator group. Ensure that there is no security system in
place that prevents creating the user or removes the user
from the Administrators group. For details on how to create
this user, see "Install and configure LoadRunner Enterprise
servers and hosts" on page 50.
l LoadRunner Enterprise supports the InfluxDB time series
database for storing data externally. The InfluxDB time series
database is installed as part of the LoadRunner Enterprise
Host installation.

LoadRunner Enterprise (2023-2023 R1) Page 25 of 194

Installation Guide
Installation overview

Standalone You cannot install the Standalone Load Generator on the same
Load machine as the LoadRunner Enterprise Server or LoadRunner
Generator Enterprise host.
(Windows)

Standalone You can install the Standalone Load Generator on Linux to run
Load Vusers. The Linux Vusers interact with the Controller that is
Generator installed on a Windows machine. For details, see "Install
(Linux) Load Generator on Linux" on page 103.

MI Listener l The MI Listener must be installed on a standalone machine.

l The MI Listener cannot be installed on a machine running IIS.

Monitor Over The Monitor Over Firewall agent must be installed on a

Firewall standalone machine.
Machine

SiteScope l SiteScope is used for monitoring applications.

Server l Refer to the SiteScope Deployment Guide for minimum
requirements.

Windows system locale considerations

The Windows system locale (Culture and UI Culture) of the user running the
LoadRunner Enterprise environment (IUSR_METRO unless changed) must match
the localized version of your LoadRunner Enterprise software.

When working with a non-localized version of LoadRunner Enterprise, the locale

must be set to English (EN-xx). Since the LoadRunner Enterprise user is created
and configured when the machine is added to the LAB project, the system locale
needs to be verified after completing all of the configuration steps.

To set the system locale for the LoadRunner Enterprise server:

1. Open Control Pane > Clock and Region, and in the Formats tab set the
format to the desired language.
2. In the Administrative tab, click the Change system locale button, set Current
system locale to the desired language, and then restart the machine.
3. After the machine restarts, in Language settings, set the selected language as
the default language, and then restart the machine.
To set the system locale for the LoadRunner Enterprise host:

LoadRunner Enterprise (2023-2023 R1) Page 26 of 194

Installation Guide
Installation overview

1. Open Control Pane > Clock and Region, and in the Administrative tab click
the Copy settings button.
2. Select the check box for Welcome screen and system accounts, and then
click OK.
3. Restart the machine.

Required services
Before you install LoadRunner Enterprise components, check that the services
defined in the table below are running on each component machine and that the
startup type for each service is defined as Automatic.

Note: The default settings for running the services on the operating system
may differ from one version to another. You should go through all of the
services on each machine to ensure that the required services are running.

Machine Services

All LoadRunner Enterprise l IPsec Policy Agent (for TCP/IP security)

servers and hosts l Remote Procedure Call (RPC)
l Windows Management Instrumentation (for
LoadRunner Enterprise health check)
l Windows Event Log (optional— used for
debugging)
l COM+ services (Event System and System
application)
l System Event Notification (for COM+)

LoadRunner Enterprise l IIS Admin Service (Microsoft Service)

servers l Workstation
l TCP/IP NetBIOS Helper
l World Wide Web Publishing Service (Microsoft
Service)
l Distributed Transaction Coordinator (MSDTC)

LoadRunner Enterprise l Remote Registry Service (requires for host

hosts monitor)

LoadRunner Enterprise (2023-2023 R1) Page 27 of 194

Installation Guide
Installation overview

Pre-installation prerequisites and considerations

This section includes pre-installation prerequisites and considerations for all
LoadRunner Enterprise components.

Prerequisite For the list of prerequisites software that must be installed on

software your machine before you can install LoadRunner Enterprise,
see the Support Matrix (System Requirements) in the
LoadRunner Enterprise Help Center.

Permission To install and configure a LoadRunner Enterprise server or

requirements LoadRunner Enterprise host, you must have full local
administrative rights on the designated machine.
UAC and DEP do not need to be disabled to install or run
LoadRunner Enterprise components.

Planning the l Separate machines. The LoadRunner Enterprise server

environment and the LoadRunner Enterprise host cannot be installed on
the same machine.
l LoadRunner installations. You cannot install LoadRunner
Enterprise components on machines with existing
LoadRunner Professional installations. Before installing
LoadRunner Enterprise, ensure that you have removed all
versions of LoadRunner Professional from the machine.
l Load considerations. Before you begin installing, you
should decide which machine is to be used for what
purpose. Consider the expected load on each machine
when determining which components to install on which
machines. For details, see "Load considerations" on
page 18.
l Dedicated host machines. We recommend that you install
LoadRunner Enterprise hosts on dedicated machines that
do not contain, or provide access to sensitive information;
and that you do a thorough security review of the network
topology and access levels in your testing environment.

Not FIPS LoadRunner Enterprise server and host components are not
compliant FIPS complaint and cannot operate on a FIPS enabled
Windows machine without additional configuration. For
details on how to work with LoadRunner Enterprise on a FIPS
enabled Windows machine, see Software Self-solve
knowledge base article KM01420828.

LoadRunner Enterprise (2023-2023 R1) Page 28 of 194

Installation Guide
Installation overview

Network l Map network drive. If the LoadRunner Enterprise

considerations installation directory is located on a network drive, it is
recommended to map the network drive before you run the
installation. For details, see Unable to run the LoadRunner
Enterprise component installation from a network drive.
l Add to Trusted Sites. To enable running the installation
from a network location, make sure that the network
location path is added to the Trusted Sites of the machine
on which you are running the installation.

Remote Desktop If you are installing a LoadRunner Enterprise server or

connection LoadRunner Enterprise host using a Remote Desktop
connection (RDP), you must connect using the Console
session.

VMWare LoadRunner Enterprise is certified to work with VMWare

ESX/ESXi 5.0 and higher. Due to the rapidly evolving
architectures provided by Virtualization vendors, as long as
the third party vendor guarantees full compatibility of the
virtualized environment with the LoadRunner Enterprise
approved system requirements for physical hardware, then
LoadRunner Enterprise functions designed.

Standalone For installation of standalone applications, you must manually

applications install the prerequisite software. For the list of required
prerequisites, see the Support Matrix (System Requirements)
in the LoadRunner Enterprise Help Center. For details on
installing the prerequisites in silent mode, see "Install
LoadRunner Enterprise silently" on page 89.

Language Ensure that the operating system and the database are both
settings configured for the same language. If not, some texts
displayed in LoadRunner Enterprise might be corrupted. For
example, if you are working with German, ensure that you are
working on a German operating system, and that the
database is configured for German.

Database prerequisites
This section provides an overview of the prerequisites for connecting LoadRunner
Enterprise to an Oracle, Microsoft SQL, and PostgreSQL database server.

Note:

LoadRunner Enterprise (2023-2023 R1) Page 29 of 194

Installation Guide
Installation overview

l Make sure you create the LoadRunner Enterprise database user before
you start the LoadRunner Enterprise installation process.
l LoadRunner Enterprise is not supported with cloud managed databases
(RDS).

Oracle Database servers

This section includes:

l "Oracle Database Admin user requirements" below

l "Oracle client requirements" on the next page
l "Oracle Database considerations: Specify an Oracle user profile" on page 32
l "Oracle Database considerations: Add additional Oracle grants" on page 33

Oracle Database Admin user requirements

l To connect LoadRunner Enterprise to an Oracle database server, the installing
database user must have sufficient permissions to perform certain
administrative tasks in Oracle. These tasks include creating the project user
schema and copying data between projects.
l If you are unable to use the Oracle system user due to security reasons, we
recommend that your database administrator create a LoadRunner Enterprise
database administrative user, for example lre_admin_db, with the specific
privileges required to install LoadRunner Enterprise.
Your database administrator can create a LoadRunner Enterprise database
administrative user using a script, see this KB article. This script creates the
LoadRunner Enterprise database administrative user with the recommended
grants required on the database.
If you are using a container database (CDB), all scripts for creating the
LoadRunner Enterprise database user must be run while directly connected to
the CDB. Those scripts should be run by a user with SYSDBA system privileges.

Note: When using CDB, the script invokes the "CONTAINER=Current"

parameter.

LoadRunner Enterprise (2023-2023 R1) Page 30 of 194

Installation Guide
Installation overview

Oracle client requirements

l The Oracle clients should be installed on the LoadRunner Enterprise server with
Administrator installation type, and connectivity must be successfully
established with the Oracle server.
l The tnsnames.ora file should contain the net service configuration that has the
information to access the Oracle database server.
l Only a 64-bit Oracle client installation is required.

To install the Oracle clients:

a. Create a root folder for the Oracle clients (c:\oracle in the example).
b. Install the Oracle client 64-bit version within a new dedicated folder (client_
64 in the example) under the root folder.
c. Copy the relevant tnsnames.ora and sqlnet.ora files into the Oracle clients
root folder.
d. Set the TNS_ADMIN environment variable for the Oracle clients root folder
(see the example above).
e. Restart the machine.

LoadRunner Enterprise (2023-2023 R1) Page 31 of 194

Installation Guide
Installation overview

f. Install LoadRunner Enterprise. See "Install and configure LoadRunner

Enterprise servers and hosts" on page 50.

Oracle Database considerations: Specify an Oracle user profile

Since every project created in LoadRunner Enterprise is a user in Oracle, and each
user created needs to be connected to a profile, you can specify a profile for your
project to use in the configuration. This profile is added to the user when the
Oracle user is created.

1. On the LoadRunner Enterprise server, stop the LoadRunner Backend Service.

2. Copy the following:

"SiteParameters": {

"OracleDbUserProfileForNewProject": {

"Value": "",

"Description": "Add the db profile that will be used when creating a new oracle
user, value is a string",

"IsSystem": true,

"IsVisible": false

3. Depending on the type of environment you are using:

l For a clustered environment: To affect all cluster nodes, paste the copied
section to the remote appsettings.json file under the repository (for
example, pc-repo\SqlEnvironment\system_config\).
l For a single node: To affect this node only, paste the copied section to
appsettings.json in the <LoadRunner Enterprise server installation>\LRE_
BACKEND\ folder.

Note: Do not make any changes to the default configuration file,

appsettings.defaults.json.

LoadRunner Enterprise (2023-2023 R1) Page 32 of 194

Installation Guide
Installation overview

4. Add the user profile you want to use to the

OracleDBUserProfileForNewProject value.
Make sure you define the user profile in the same way that it is defined in the
database—with or without quotes. When defined with quotes in the database,
you must use the escape character ( \ ) in the configuration file.

Example: Profile created without quotes

"SiteParameters": {

"OracleDbUserProfileForNewProject": {

"Value": "myprofile",

"Description": "",

"IsSystem": true,

"IsVisible": false

Example: Profile created with quotes (use escape character)

"SiteParameters": {

"OracleDbUserProfileForNewProject": {

"Value": "\"myprofile\"",

"Description": "",

"IsSystem": true,

"IsVisible": false

5. Make sure the JSON file is valid and save your changes.

Oracle Database considerations: Add additional Oracle grants

You can customize the LoadRunner Enterprise configuration file by adding
additional Oracle grants to a user if the default grants are not sufficient.

LoadRunner Enterprise (2023-2023 R1) Page 33 of 194

Installation Guide
Installation overview

1. On the LoadRunner Enterprise server, stop the LoadRunner Backend Service.

2. Copy the following:

"SiteParameters": {

"OracleDbUserExtraGrants": {

"Value": "",

"Description": "Add extra grants to each user created by the app, separate each
grant with ';' omit the word 'GRANT' and 'to', will added by the app.",

"IsSystem": true,

"IsVisible": false

3. Depending on the type of environment you are using:

l For a clustered environment: To affect all cluster nodes, paste the copied
section to the remote appsettings.json file under the repository (for
example, pc-repo\SqlEnvironment\system_config\).
l For a single node: To affect this node only, paste the copied section to
appsettings.json in the <LoadRunner Enterprise server installation>\LRE_
BACKEND\ folder.

Note: Do not make any changes to the default configuration file,

appsettings.defaults.json.

4. Add any specific grants that you want to give to a user to the
OracleDBUserExtraGrants value.
Separate each grant with a semi-colon (;) and omit the words "GRANT" and "to"
since they are added automatically.

Example:

"SiteParameters": {

"OracleDbUserExtraGrants": {

LoadRunner Enterprise (2023-2023 R1) Page 34 of 194

Installation Guide
Installation overview

"Value": "EXECUTE ON SYS.DBMS.LOB",

"Description": "",

"IsSystem": true,

"IsVisible": false

5. Make sure the JSON file is valid and save your changes.

Microsoft SQL Database servers

Below is a list of prerequisites that are required when using a Microsoft SQL
Database server:

DB To connect LoadRunner Enterprise to a Microsoft SQL database

connection server, the installing database user must have sufficient
permissions permissions to perform certain administrative tasks in SQL.
l For SQL Authentication: An admin database user with
"dbcreator" level permissions and a user with "public"
permissions.
l For Windows Authentication: A domain user with "dbcreator"
permissions. LoadRunner Enterprise must be configured with
this service user.

Collation Collation for the SQL server should be set to SQL_Latin1_

General_CP1_CI_AS.

LoadRunner Enterprise (2023-2023 R1) Page 35 of 194

Installation Guide
Installation overview

Connection To add additional connection string parameters to a SQL server:

parameters
1. Navigate to <LRE server installation>\LRE_BACKEND and
open the appsettings.defaults.json file.
2. Modify the connection string in the
"SiteParameters:MssqlExtraGlobalConnectionStringParam
s" section as required.
3. Save the changes.
4. Restart the LoadRunner Backend Service, and try the
database connection again from the Configuration wizard.
Note: If the certificate installed on the SQL Server is self-signed
(which is generally not recommended provided a proper
certificate is installed), you need to add
"TrustServerCertificate=true" to "Value". After the change,
this section should look like:

PostgreSQL Database servers

To connect LoadRunner Enterprise to a PostgreSQL database server, the installing
database user must either be:

l A PostgreSQL superuser with "CreateDatabase" and "CreateRole" permissions,

or
l A PostgreSQL non-superuser with the following permissions: Rolcanlogin =
true, Rolcreatedb = true, Rolcreaterole = true, and Rolconnlimit = -1.

Notes and limitations

l Migrating projects from 12.6x versions of LoadRunner Enterprise on Oracle or
Microsoft SQL to LoadRunner Enterprise 202x on PostgreSQL is not supported.
l If you try to install two environments (such as staging and production or a multi-
tenant environment) on the same PostgreSQL database server, they overrun
each other.

LoadRunner Enterprise (2023-2023 R1) Page 36 of 194

Installation Guide
Installation overview

Resolution: Set up a separate PostgreSQL database server for each

environment.
a. The first environment can be configured by running the LoadRunner
Enterprise Configuration wizard. For details, see "Configure a LoadRunner
Enterprise server or host" on page 55.
b. For the second environment, you must change the LRE tenant name.
i. Open the appsettings.defaults.json file located in the <LR Enterprise
server installation>\LRE_BACKEND folder.
ii. In the ‘Site’ section, change the “LRETenantName” value to one that is to
different to the values on all the other environments.

l The first time you install LoadRunner Enterprise, and for every time zone change
you make on the LoadRunner Enterprise server or database, make sure that you
align the time zone from the operating system with the time zone in
postgresql.conf on the database server machine. Failure to do so results in the
Active Reservation/Timeslot ID column being empty in the Hosts grid when you
run a test.

To align the time zone:

a. On the database server machine, open pgAdmin. Open lre_<tenant-name>_
tenant_db or any LoadRunner Enterprise related DB file.
Open a new script and run:

SELECT now()

Check if there are any differences between the time displayed in the query
result and the time of the operating system.
b. Check the time zone set in PostgreSQL by running:

LoadRunner Enterprise (2023-2023 R1) Page 37 of 194

Installation Guide
Installation overview

SHOW timezone

Check the time zone on the operating system to verify that a different time
zone is set. If the time zones are the same then you have a different issue and
there is no need to continue with these steps.
c. Navigate to <postgresql-install-dir>/<version-of-pg>/data and open the
postgresql.conf file. Search for the "timezone" section. You should find the
following line:

timezone = '<Continent>/<City>'

d. Go back to pgAdmin and run the following:

SELECT name, abbrev, utc_offset, is_dst FROM pg_timezone_names ORDER BY utc_

offset;

This should give you a table of all available values that you could put in the
postgresql.conf file. Select the name that matches the operating system
time zone. Replace the value in postgresql.conf with the chosen value, and
save the file.
e. In pgAdmin run:

SELECT pg_reload_conf();

Followed by:

SHOW timezone

Followed by:

SELECT now()

It should now display the correct (OS) time zone and time.

LoadRunner Enterprise (2023-2023 R1) Page 38 of 194

Installation Guide
Installation overview

f. Run a test and check for Active Reservation/Timeslot ID in the Hosts grid.
The problem should be resolved.

Installation package details

You can find information and components for the installation as follows:

Support Matrix Provides information on supported operating systems,

technologies, and integrations. For details, see Support
Matrix (System Requirements).

Standalone Found in the installation package's Standalone

installations (for Applications folder. For details, see "Install standalone
example, for the load components" on page 100.
generator)
Additional Found in the installation package's Additional
components (such as Components folder. For details, see "Install additional
the Citrix Agent) components" on page 114.

LoadRunner Enterprise (2023-2023 R1) Page 39 of 194

Pre-installation project migration steps

LoadRunner Enterprise (2023-2023 R1) Page 40 of 194

Project migration pre-installation activities
If you are migrating performance tests from Performance Center, this chapter
presents migration considerations to be taken into account before installing
LoadRunner Enterprise.

This chapter includes:

l "Pre-installation project migration considerations" below

l "Upgrade existing Performance Center/ALM projects to LoadRunner Enterprise"
on the next page
l "Back up projects in existing ALM installation" on page 43
l "Overview of migration process" on page 44

Pre-installation project migration considerations

Review and perform the following before migrating existing projects to LoadRunner
Enterprise.

l To work with Performance Center/ALM projects in LoadRunner Enterprise, you

first need to upgrade your projects to Performance Center 12.6x (ALM 12.60)
before you can migrate them to LoadRunner Enterprise 2023. For details, see
"Upgrade existing Performance Center/ALM projects to LoadRunner Enterprise"
on the next page.

Note: Starting from LoadRunner Enterprise 2023 R1, direct ALM migration
is no longer supported. Instead, you must first migrate ALM projects to
LoadRunner Enterprise 2023, and then upgrade to the latest LoadRunner
Enterprise version.

l In addition, review the Support Matrix (System Requirements) in the LoadRunner

Enterprise Help Center to make sure you meet the requirements for working with
the LoadRunner Enterprise version being used.
l Review the list of features that are not available or fully implemented in this
release. For details, see Unsupported features in the LoadRunner Enterprise Help

LoadRunner Enterprise (2023-2023 R1) Page 41 of 194

Installation Guide
Pre-installation project migration steps

Center.
l Before beginning the installation, back up the projects, the database, and the
repository. For details, see "Back up projects in existing ALM installation" on the
next page.

Note: During the migration process, data is taken from ALM in read-only
mode so no changes should occur on the database level.

l Migrating projects from one database type in ALM 12.60 to another database
type in LoadRunner Enterprise is not supported.

Upgrade existing Performance

Center/ALM projects to LoadRunner Enterprise
The following table describes how to upgrade and migrate projects from
Performance Center/ALM to LoadRunner Enterprise. Note that not all projects can
be migrated directly to LoadRunner Enterprise.

Performance
Center To LoadRunner Enterprise

Performance Projects in ALM 12.60 can be migrated directly to LoadRunner

Center 12.6x Enterprise 2020-2023, provided the LoadRunner Enterprise
system user has access to the location where the Performance
Center/ALM 12.6x repository (source for migration) is stored.
Starting from LoadRunner Enterprise 2023 R1, direct
ALM migration is no longer supported. Instead, you must first
migrate to LoadRunner Enterprise 2023, and then upgrade to
the latest LoadRunner Enterprise version.
For migration details, see Migrate projects to LoadRunner
Enterprise in the LoadRunner Enterprise Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 42 of 194

Installation Guide
Pre-installation project migration steps

Performance
Center To LoadRunner Enterprise

Performance The Performance Center/ALM repository must be moved to the

Center 11.52 - location of the ALM 12.6x repository.
12.5x
Projects must first be upgraded to ALM 12.60. For details, see
the ALM 12.60 Installation and Upgrade Guide.
Note: You must first upgrade LAB_PROJECT, and then any
Performance Center template projects, before migrating
Performance Center projects.

Performance Projects must first be upgraded to ALM 11.52, and then to ALM
Center 11.00 12.60. For details, see the ALM 11.52 Installation and Upgrade
Guide.
Note: You must first upgrade LAB_PROJECT, and then any
Performance Center template projects, before upgrading
Performance Center projects.

Back up projects in existing ALM installation

Back up all your projects in the existing ALM installation that you plan to migrate.
We recommend that you deactivate projects before backing them up.

If you must back up while your project is still active, you must back up the
database before the file system. We also recommend backing up the file system as
soon as possible after backing up the database.

Note:
l Before you run the migration process, perform a full backup of your
projects that includes the project database schema and the project
repository.
l Version Control: Version control enabled projects cannot be backed up
while there are checked out entities. All entities must be checked in to the
corresponding version of Quality Center or ALM. To determine if there are
checked out entities, see this KB article.

LoadRunner Enterprise (2023-2023 R1) Page 43 of 194

Installation Guide
Pre-installation project migration steps

To back up the project database schema on the database server:

l Microsoft SQL database. To back up the project database schema on the
database server, see this KB article.
l Oracle database. To back up the project database schema on the database
server, see this KB article.

Overview of migration process

Migrating projects from Performance Center to LoadRunner Enterprise requires the
following steps:

1. Upgrading Performance Center projects to ALM 12.60 (pre-installation)

For details on upgrading Performance Center projects to ALM 12.60, see
Upgrading Projects to a New Version in the ALM Help Center.
2. Migrating the Site Admin and LAB schemas from ALM (during installation)
During the installation process, you need to migrate the configuration data that
was stored in ALM Site Admin and LAB to LoadRunner Enterprise.
For details, see "Configure Site Admin and LAB schema migration (LoadRunner
Enterprise 2023 only)." on page 63

Note: You can also perform this step post-installation from the
Configuration wizard, provided you specify a new Site Admin and LAB
schema for LoadRunner Enterprise (if you use the existing schemas
nothing happens). For details, see "Post-installation configuration steps"
on page 84.

3. Migrating the project data (post-installation)

After installing LoadRunner Enterprise, you need to migrate project data and
the file repository from existing projects to LoadRunner Enterprise using the
migration tool in LoadRunner Enterprise Administration.
Project data which includes scripts, attachments, run results, .xml files, and
templates is migrated from ALM Site Admin and LAB to the LoadRunner
Enterprise server.

LoadRunner Enterprise (2023-2023 R1) Page 44 of 194

Installation Guide
Pre-installation project migration steps

For details, see Migrate projects to LoadRunner Enterprise in the LoadRunner

Enterprise Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 45 of 194

Installation and configuration

LoadRunner Enterprise (2023-2023 R1) Page 46 of 194

 Install LoadRunner Enterprise
This chapter describes how to install LoadRunner Enterprise 2023 or any later
minor release (they are all full installations).

Note:
l You can install LoadRunner Enterprise 2023.x as a clean installation, or
over an existing LoadRunner Enterprise 2020 or later installation. The
installation process, which is the same for both, is described below. You
can also migrate projects in ALM 12.60 directly to LoadRunner
Enterprise 2023. To migrate ALM to later LoadRunner Enterprise versions,
you must first migrate ALM projects to LoadRunner Enterprise 2023, and
then upgrade to the latest LoadRunner Enterprise version. For details, see
"Project migration pre-installation activities" on page 41.
l When upgrading from Performance Center 12.6x or LoadRunner Enterprise
2020 or later, you need to request and upload new licenses to work with
the upgraded LoadRunner Enterprise version. For details, see Set
LoadRunner Enterprise license keys in the LoadRunner Enterprise Help
Center.

This chapter includes:

• Installation flow 48
• Upgrade LoadRunner Enterprise 50
• Install and configure LoadRunner Enterprise servers and hosts 50
• Secure communication and the system user 70
• Post-installation configuration steps 84
• Install LoadRunner Enterprise silently 89
• Deploy LoadRunner Enterprise on AWS 98
• Install standalone components (Windows) 99
• Install Load Generator on Linux 103
• Deploy Dockerized load generators on Linux 104
• Deploy Dockerized load generators on Windows 109
• Install additional components 114
• Uninstall LoadRunner Enterprise server and hosts 116
• Uninstall Load Generator from Linux 117

LoadRunner Enterprise (2023-2023 R1) Page 47 of 194

Installation Guide
Installation and configuration

Installation flow
This section describes the steps required to install LoadRunner Enterprise.

Before beginning the actual installation

procedure, check that you meet the
prerequisite criteria for working with
LoadRunner Enterprise. For details, see
"Before you install" on page 9.

If you plan to work with projects from an

earlier version of LoadRunner Enterprise
(formerly Performance Center), follow the
"Project migration pre-installation activities"
on page 41.

Install the Database server. For details, see

"Database prerequisites" on page 29 and
"LoadRunner Enterprise configuration
options" on page 121.

1. Install and configure LoadRunner

Enterprise servers and hosts. For details,
see "Install and configure LoadRunner
Enterprise servers and hosts" on page 50.
2. Configure LoadRunner Enterprise in
LoadRunner Enterprise Administration. For
details, see "Post-installation
configuration steps" on page 84.

LoadRunner Enterprise (2023-2023 R1) Page 48 of 194

Installation Guide
Installation and configuration

Install standalone applications that provide

advanced features for working with
LoadRunner Enterprise. For details, see
"Install standalone components (Windows)"
on page 99.
To install a load generator on Linux, see
"Install Load Generator on Linux" on page 103.
To install the load generator through a Docker
container, see "Deploy Dockerized load
generators on Linux" on page 104 / "Deploy
Dockerized load generators on Windows" on
page 109.

Perform additional tuning and configuration

settings to get the most out of LoadRunner
Enterprise. For details, see "LoadRunner
Enterprise configuration options" on page 121.
You can set LoadRunner Enterprise to run
Vusers and monitor servers over a firewall.
For details, see "Working with firewalls" on
page 147.
Perform a post-installation verification. For
details, see "Post installation verification" on
page 118.
For installation troubleshooting details, see
"Troubleshooting installation issues" on
page 185.

After the installation is successful, you can

migrate existing projects from Performance
Center 12.6x (ALM 12.60) to the latest
LoadRunner Enterprise version. For details,
see Migrating the project data in "Overview of
migration process" on page 44.

LoadRunner Enterprise (2023-2023 R1) Page 49 of 194

Installation Guide
Installation and configuration

Upgrade LoadRunner Enterprise

LoadRunner Enterprise versions 2023 and later are full installations that can be
installed over any LoadRunner Enterprise 2020 or later installation.

To upgrade all components in your installation, follow the installation process as

described in "Install and configure LoadRunner Enterprise servers and hosts"
below. The installation process detects the older version, and gives you the option
to upgrade.

Note: For silent upgrade, see "Installing an upgrade in silent mode" on

page 97.

Before upgrading to a later version

l We recommend creating a back up of your Site Admin and Lab DB schemas
before you start to safeguard against any unexpected changes during the
upgrade process. For details, see Back up projects in the LoadRunner Enterprise
Help Center.
l If you are upgrading to a new version of LoadRunner Enterprise and you have
more than one LoadRunner Enterprise server installed, you must perform the
following on all LoadRunner Enterprise servers:
a. Stop IIS and the LoadRunner Backend Service and the LoadRunner Alerts
Service.
b. Install the latest version of LoadRunner Enterprise. For details, see "Install
and configure LoadRunner Enterprise servers and hosts" below.

Install and configure LoadRunner Enterprise

servers and hosts
This section describes how to install and configure LoadRunner Enterprise servers
and hosts.

l "Install a LoadRunner Enterprise server or host" on the next page

l "Configure a LoadRunner Enterprise server or host" on page 55

LoadRunner Enterprise (2023-2023 R1) Page 50 of 194

Installation Guide
Installation and configuration

Note:
l Review the LoadRunner Enterprise installation flow before you begin the
installation. For details, see "Installation flow" on page 48.
l If you are upgrading from an earlier version of LoadRunner Enterprise,
review the upgrade instructions in "Upgrade LoadRunner Enterprise" on
the previous page.
l If you are migrating 12.6x or earlier projects from Performance Center,
follow the instructions in "Project migration pre-installation activities" on
page 41.

Install a LoadRunner Enterprise server or host

1. Launch the LoadRunner Enterprise installer.
Download the installer package, and run setup.exe.
2. Select an installation option.
The setup program starts and displays the installation menu page.
Select LoadRunner Enterprise or LoadRunner Enterprise Host.

Note: If a particular host machine is to be used as a load generator only,

we recommend that you install the Standalone Load Generator because
the installation requires less disk space, and it is less time-consuming to
move the load generator's setup files (compared to the LoadRunner
Enterprise Host). For details on installing the Standalone Load Generator,
see "Install standalone components (Windows)" on page 99. To install a
load generator on Linux, see "Install Load Generator on Linux" on
page 103.

3. If necessary, install prerequisite software.

Specific software needs to be installed on the machine before you can install
the LoadRunner Enterprise component (see the Support Matrix (System
Requirements) in the LoadRunner Enterprise Help Center). If the prerequisite
software is not already installed on your computer, a dialog box opens
displaying the list of prerequisite programs that are required.

LoadRunner Enterprise (2023-2023 R1) Page 51 of 194

Installation Guide
Installation and configuration

Click OK and follow the on-screen instructions to install the prerequisite

software before continuing with the LoadRunner Enterprise component
installation. You cannot continue with the LoadRunner Enterprise component
installation unless all the prerequisite software is installed.

Note:
l If you are prompted to restart the machine after installing the
prerequisite software, you must do so before continuing with the
installation. After rebooting the machine, run setup.exe again to
continue with the installation. If the installation continues from where it
left off before rebooting, we recommend starting the setup again—the
installer detects the installed prerequisites and continues with the
installation.
l When installing a LoadRunner Enterprise server, if Microsoft Internet
Information Services (IIS) 8.0/8.5/10 is listed on this page, it is required
that you close the installation, install IIS, and restart the installation.

4. If an earlier version is installed on your machine.

The installation process detects the older version, and gives you the option to
upgrade or exit the installation.
5. Start the installation.
l For LoadRunner Enterprise Server: The LoadRunner Enterprise Setup Wizard
opens, displaying the Welcome page. Click Next.
l For LoadRunner Enterprise Host: The LoadRunner Setup Wizard opens,
displaying the Welcome page. Select LoadRunner Enterprise Host, and
click Next.
6. Review the License agreement.
To accept the terms of the license agreement, select I accept the terms in the
License Agreement.
For LoadRunner Enterprise Host only:
l If you plan to run JMeter, Gatling, or Silk Performer scripts in LoadRunner
Enterprise, make sure to select the Install JMeter after installation, Install
Gatling after installation, or Install Silk Performer Agent after installation

LoadRunner Enterprise (2023-2023 R1) Page 52 of 194

Installation Guide
Installation and configuration

options during setup as required.

l To help us improve the quality, reliability, and performance of LoadRunner
Enterprise, select Participate in LoadRunner improvement program. This
enables us to collect anonymous information about your software and
hardware configuration, and about how you use LoadRunner Enterprise.
Click More Details in the user interface for more information.

Caution: Participating in the improvement program creates

unnecessary overhead on the host machine and is not recommended.

Click Next.
7. Select a destination folder.
Specify the location in which to install the LoadRunner Enterprise component.
By default, LoadRunner Enterprise is installed to C:\Program Files
(x86)\Micro Focus\LoadRunner Enterprise\.
To choose a different location, enter the location or click the Change button,
select a location, and click OK.

Note:
l When upgrading from LoadRunner Enterprise 2020 SP2 or SP3, the
location field is read-only.
l (LoadRunner Enterprise Host only). To reduce problems due to the
Microsoft Windows API path limitation, choose a short name for your
installation directory path. For example: “C:\LREHost”.

Click Next.
8. Start the installation process.
The wizard prompts you to confirm the details and start the installation. To
review or change any settings, click Back.
Click Install to start the installation. The wizard displays the installation
progress.
Upon completion of the LoadRunner Enterprise installation, click Next, and
continue with the steps in the Configuration wizard as described below.

LoadRunner Enterprise (2023-2023 R1) Page 53 of 194

Installation Guide
Installation and configuration

9. Upon completion of the installation, determine whether to install Network

Virtualization (NV).
Upon completion of the installation, the Finish page opens.
To view the installation log files, click the Open Installation Log link. The files
are also available on the LoadRunner Enterprise server or host from
<installation folder>\orchidtmp\Configuration\configurationWizardLog_
pcs.txt.
To install NV, choose one of the below options, or click Do not install to skip
NV installation (you can install NV manually at a later time).
l Typical. Automatically launches a non-interactive NV installation, using the
default NV settings.
l Custom. Automatically launches an interactive NV installation, enabling you
to set the installation folder, data folder, and port to be used, and select
which NV components to install.

Note:
l The LoadRunner Enterprise installation is complete, regardless of the
selected NV installation option.
l If you install NV on a LoadRunner Enterprise server, the NV for
LoadRunner Enterprise installation is launched.
l If you install NV on a LoadRunner Enterprise host, both the NV for
Controller and the NV for Load Generator installations are launched
(one after the other).
l If you install NV automatically, disable Windows SmartScreen before
proceeding with the installation. To do so, open HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer in
the Registry Editor, and change the Value data for
"SmartScreenEnabled" to "Off". You do not need to disable
SmartScreen when installing NV manually.
l If you upgrade host machines from Performance Center 12.6x to
LoadRunner Enterprise 2023.x, and NV for Controller and NV for Load
Generator co-exist on the same machine, you cannot modify setup
configuration settings for a Custom mode installation.
Resolution: Exit the wizard and uninstall the NV components. Then

LoadRunner Enterprise (2023-2023 R1) Page 54 of 194

Installation Guide
Installation and configuration

reinstall them by manually running the NV installation. See the

installation section in the Network Virtualization for LoadRunner Help.
l NV installation log files are available from C:\Temp\NV_Logs.

Upon completion of the LoadRunner Enterprise installation (and NV installation

if selected), click Next, and continue with the steps in the Configuration wizard
as described below.

Configure a LoadRunner Enterprise server or host

1. Prerequisites.
If you plan configuring the LoadRunner Enterprise server and IIS to work with a
secure (SSL) connection, we recommend making sure that a server certificate
has been imported and a corresponding HTTPS binding is created for the site
before running the Configuration Wizard.

Note: For increased security, we recommend changing the default

IIS landing page so that it redirect users to a different realm, such as the
secure portal.
a. Navigate to the IIS root folder (usually C:\inetpub\wwwroot), and make
a copy of the iisstart.htm file.
b. Open iisstart.htm, running notepad as administrator, and locate the
following section:
<meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1" />
c. Change it to the following:
<meta http-equiv="refresh" content="0; url=THE REALM YOU
WANT TO REDIRECT TO" />
Example: <meta http-equiv="refresh" content="0; url=https://
[your site url]/LRE/" />

Refer to the product documentation for more details.

2. Start the LoadRunner Enterprise configuration.

LoadRunner Enterprise (2023-2023 R1) Page 55 of 194

Installation Guide
Installation and configuration

After completing the LoadRunner Enterprise installation, click Next. The

Welcome page of the Configuration wizard opens.
Click Next to start the configuration process.
3. Create the LoadRunner Enterprise service user (LoadRunner Enterprise server
only).
LoadRunner Enterprise requires that a system user is created for use by the
LoadRunner Enterprise server, hosts and the Load Generator standalone
machines.
a. In the LRE Service User page, specify a user to run the service.
o If you select Use Default Credentials, LoadRunner Enterprise is
configured with the LoadRunner Enterprise system user, IUSR_METRO,
and adds it to the machine's Administrators group.
o To define your own system user for the LoadRunner Enterprise
environment, clear the Use Default Credentials checkbox, and enter the
domain, user, and password. Enter credentials using one of the following
formats: domain\username or username@domain.

Note:
o You can use a local or a domain user. When using a local user, if the
user does not exist on the LoadRunner Enterprise server machine,
the installer creates it.
o When using a local user, if the user name does not exist or is not in
the Administrators group, it is added to the Administrators group.
o When using a domain user, make sure that the domain user is a
member of the Administrators group.
o You must have a domain user set in the Configuration wizard when
setting the repository path to a network location.
o The LRE Service user you set here must have permissions for the
file repository (see Configure the repository).
o After adding the LoadRunner Enterprise server to the project, the
LoadRunner Enterprise user is saved to that database. Each
subsequent LoadRunner Enterprise server or host added, is
configured with that user.

LoadRunner Enterprise (2023-2023 R1) Page 56 of 194

Installation Guide
Installation and configuration

o After a LoadRunner Enterprise server is added, you can use the

System Identity utility (<LRE server installation
directory>/bin/IdentityChangerUtil.exe) to change the user. For
details, see the System Identity Utility Window in the LoadRunner
Enterprise Help Center.
o Once you succeed in creating the user and configuring the server,
the next time you launch the Configuration wizard, this page is not
displayed.

b. Click Next.
4. Configure the repository.
a. In the Repository page, click the Browse button to navigate to, or enter the
path of the new LoadRunner Enterprise repository.

Note:
o Make sure you select a path where you have full read and write
permissions.
o The user account that was set in the LRE Service User page must
have permissions for the file repository (see Create the LRE Service
User).
o The file repository is supported with Azure Files Share via a
UNC path (not a mapped drive).
o To work with cluster nodes, make sure that all nodes have access
to the file repository path and that the path is UNC. All nodes in the
cluster must have the same string for the repository path.
o The length of the file repository path cannot exceed 200
characters.
o The file repository path cannot reside on the root folder.
o Due to a Windows limitation, the file repository path cannot be on a
mapped drive.

b. Click Test Connection to check whether you can connect to the repository
using the user credentials you provided.
c. Click Next.
5. Configure the connection to the LoadRunner Enterprise database server.

LoadRunner Enterprise (2023-2023 R1) Page 57 of 194

Installation Guide
Installation and configuration

a. In the DB Connection page, select the database type to be used in your

LoadRunner Enterprise system: Oracle, Microsoft SQL, or PostgreSQL
(supported for on-premises versions only).
b. If you select a Microsoft SQL Server, choose the authentication type: SQL
Authentication or Windows Authentication.

MS-SQL (SQL Authenticates the user to the database using a

Auth) database user name and password.

MS-SQL Windows authentication relies on the user being

(Windows authenticated by the operating system.
Auth)

c. Configure the database administrator and user credentials:

Database MS-SQL:
Administrator o SQL Authentication: Enter the name and password of
Credentials an admin database user with "dbcreator" level
permissions required to install LoadRunner
Enterprise on the database server.
o Windows Authentication: Read-only field which

displays the name and password of the domain user

used for the LoadRunner Enterprise installation.
Note: Windows Authentication mode is only
supported if LoadRunner Enterprise is configured
with a domain user. If it is configured with a local
user, such as IUSR_METRO, only SQL Authentication
is available.
Oracle:
o Enter the name and password of the user with the

administrative permissions required to install

LoadRunner Enterprise on the database server.
PostgreSQL:
o Enter the name and password of a PostgreSQL

superuser with "Create Database" and "CreateRole"

permissions, or a PostgreSQL non-superuser with
the following permissions: Rolcanlogin = true,
Rolcreatedb = true, Rolcreaterole = true, and
Rolconnlimit = -1 on the database server.

LoadRunner Enterprise (2023-2023 R1) Page 58 of 194

Installation Guide
Installation and configuration

Database User SQL Authentication:

Credentials o Enter the name and password of a user with "public"

level privileges to be used by LoadRunner Enterprise

to connect to the database after the installation is
complete.
Oracle:
o Set the default password for the new database

users.

Note: You can change the database administrator and user

credentials at any time from the Database Password Changer utility.
For details, see "Change the database administrator and user
passwords" on page 88.

d. In the Connection Details section, select one of the following options:

o Connection string parameters. Select this option to enter database
server information using the following fields:

Server MS-SQL: Enter the database server name. For example,

Host dbsrv01.
Oracle: This field is read-only.
PostgreSQL: The PostgreSQL server address.

Port MS-SQL: Enter the database server port number, or accept

the default port number.
Oracle: This field is read-only.
PostgreSQL: Enter the port on which the PostgreSQL server
is listening, or leave empty to use the default port (5432).

Net Enter the net service name found in the local tnsnames.ora
Service file.
Name Note: The Oracle net service name must be in the same
(Oracle case as it appears in the tnsnames.ora file.
only)
o Connection string. Select this option to manually edit the database
server connection string, and provide the net service name from the local
tnsnames.ora file.

LoadRunner Enterprise (2023-2023 R1) Page 59 of 194

Installation Guide
Installation and configuration

Note: The database name cannot be longer than 128 characters for
a Microsoft SQL database, or 253 characters for an Oracle or
PostgreSQL database.

e. Click Test Connection to check whether you can connect to the database
server using the user credentials you provided.
f. Click Next.
6. Configure the database schema.
a. In the DB Schema Configuration page, enter a schema name for the Site
Management database, the Site Admin database, and the LAB database.

Note: The Site Management schema is created regardless of whether

you are using a single or multi-tenant system.

b. If you are creating a PostgreSQL project, enter the password to be used

when creating the new logins which are part of the database creation
process.
c. If you are creating an Oracle project, enter the following:

Tablespace Select or enter the path to a storage location that has

sufficient space to store the new project.
You should not use UNDO as the storage location.

Temporary Select or enter the path to a temporary storage location

Tablespace that has sufficient space to store the new project.

d. Click Next.
7. Configure security settings.
a. In the Security Settings page, enter a confidential data passphrase that
LoadRunner Enterprise uses to encrypt the information. The passphrase is
case-sensitive, and must contain at least 12 alphanumeric characters.
Ensure there are no empty spaces before or after the passphrase.
We recommend making a note of the passphrase for future usage.

Note:

LoadRunner Enterprise (2023-2023 R1) Page 60 of 194

Installation Guide
Installation and configuration

o After completing the server configuration wizard, you cannot

change the confidential data encryption passphrase.
o If you are installing LoadRunner Enterprise on a cluster, you must
use the same passphrase for all nodes.
o Passwords for accessing external systems (databases and LDAP)
are stored by LoadRunner Enterprise after encryption.

b. Enter a secure communication passphrase that LoadRunner Enterprise uses

to encrypt the SSO token. Communication between LoadRunner Enterprise
and other OpenText applications is enabled after authentication by a Single
Sign-On (SSO) token.
The passphrase must contain at least 12 alphanumeric characters only.
c. Click Next.
8. Configure the LoadRunner Enterprise server and IIS for SSL.
When you configure a LoadRunner Enterprise server, you can choose whether
to work with a non-secure (HTTP) or a secure (SSL) connection. When you use
the SSL option during server installation, a self-signed SSL certificate is
automatically generated on the local LoadRunner Enterprise machine and the
IIS server. Alternatively, you can import a certificate from a certified authority
(CA).

Note: If you intend to use the LoadRunner Enterprise server with a

secure connection, make sure you have configured IIS to use SSL on the
LoadRunner Enterprise server machine (you can also configure
LoadRunner Enterprise to work with SSL post-installation). For details,
see "Configuring LoadRunner Enterprise to work with TLS/SSL" on
page 122.

a. In the SSL Configuration page, select Configure SSL for LoadRunner

Enterprise to use a secure connection.
If you are using a non-secure (HTTP) connection, clear this option and click
Next to proceed to the next step.
b. From the Certificate store list, select the name of the provider that stores
the certificate.

LoadRunner Enterprise (2023-2023 R1) Page 61 of 194

Installation Guide
Installation and configuration

c. Select the server-side certificate file that is to be used on the listening port
during an SSL handshake. You can import a certificate, or use an existing
certificate.

Import a i. To import a certificate from a certified authority, select

certificate the Import certificate checkbox, and choose a
certificate file (it must be in .pfx format).
ii. Enter the password used to access the certificate file.
iii. Enter the host name and port of the LoadRunner
Enterprise server used by the agent.

Use i. To use an existing certificate, clear the Import

existing certificate checkbox, and select a certificate from the
certificate Existing certificates list.
ii. Enter the host name and port of the LoadRunner
Enterprise server used by the agent.

d. Click Next.
9. Define the site administrator.
Enter a user name and password for a site administrator. These credentials are
used to create a user to log in to both LoadRunner Enterprise Administration
and the Site Management console for the first time (these are two separate
users, and updating one does not have any effect on the other).
After installation, you can change the site administrator or add other site
administrators.
a. In the LRE Administration User page, enter a site administrator user name
and password, and retype the password to confirm.

Note:
o The user name cannot include the following characters: \ / : * ? " <
>|
o The password cannot be longer than 20 characters.
o Keep a record of these credentials because you need them to
initially access LoadRunner Enterprise Administration, the Site
Management console, and the System Identity Changer utility.

LoadRunner Enterprise (2023-2023 R1) Page 62 of 194

Installation Guide
Installation and configuration

b. Select a secret question for resetting the password and enter an answer.
c. Click Next.
10. Configure the mail server.
A mail server enables LoadRunner Enterprise users to send emails to other
users in a project.
a. In the Mail Server Configuration page, select Configure Mail Server if you
plan to use a mail server. Otherwise, click Next and proceed to the next
step.
b. Select which server to use and complete the SMTP account settings:

Address The user's email address.

Outgoing mail The SMTP server available on your local area
server (SMTP) network.
Port The port number used by the outgoing mail server.
By default, port 25.
Use the following Choose whether to make your connection more
type of secure. The following options are available: SSL and
encrypted Start TLS.
connection Note: SSL/TLS is currently not supported.

Outgoing server If your SMTP server requires authentication, select

(SMTP) requires this option to provide credentials for authentication.
authentication Enter the user name and password.
Send Test Email Opens the Test Mail dialog box. Enter an email
address and click Send. A message box confirms
whether the mail was sent successfully.

c. Click Next.
11. Configure Site Admin and LAB schema migration (LoadRunner Enterprise 2023
only).

Note: Direct ALM migration is not supported in LoadRunner Enterprise

2023 R1 and later versions.

LoadRunner Enterprise (2023-2023 R1) Page 63 of 194

Installation Guide
Installation and configuration

If you are creating a PostgreSQL project, proceed to the Summary step (the
Migration Configuration step is not displayed).
To work with projects from a previous version of LoadRunner Enterprise (in
which the projects were stored in ALM), you need to migrate data from the Site
Admin and LAB schemas to LoadRunner Enterprise.
a. In the Migration Configuration page, select Migrate Site Admin and LAB
data and configuration to perform the migration during the installation
process.
Otherwise, click Next and proceed to the next step.

Note:
o This option is disabled if the Site Admin or LAB schemas already
exist in LoadRunner Enterprise.
o You can also migrate Site Admin and LAB configuration data post-
installation from the Configuration wizard, provided you specify a
new Site Admin and LAB schema for LoadRunner Enterprise (if you
use the existing schemas nothing happens).

b. In the Migration Configuration (Step) section, enter the names of the

source Site Admin and LAB database schemas.
c. Select the source database type: MS-SQL (SQL Authentication), MS-SQL
(Windows Authentication), or Oracle.
d. Configure the source database schema credentials:

LoadRunner Enterprise (2023-2023 R1) Page 64 of 194

Installation Guide
Installation and configuration

User Name The name of the user with the permissions required to
(Oracle and access LoadRunner Enterprise on the database server.
MS-SQL Note that this is not the database admin user.
(SQL Auth) Note:
only) o For MS-SQL (Win Auth), the Windows user running the

LoadRunner Enterprise Backend Service is used to

access the SQL server.
o For MS-SQL (SQL Auth):

l The login supplied to authenticate to the SQL server

should be mapped to the ‘td’ user of the database. If

you are using the same SQL server used by ALM, the
‘td’ user that is present in each database is by default
mapped to the ‘td’ login, and this ‘td’ login can be
supplied to perform the migration.
l If you backed up and restored the database of the

project in another SQL server, make sure you map the

login supplied to perform the migration to the ‘td’ user
of the database. For example, run the following SQL
command:
--Map database user td to login John for
database DEFAULT_PCPROJECT_DB USE DEFAULT_
PCPROJECT_DB;
GO
EXEC sp_change_users_login 'Update_One', 'td',
'John';
GO

Password The password of a user with the permissions required to

(Oracle and access LoadRunner Enterprise on the database server; this
MS-SQL is not retrieved from ALM.
(SQL Auth) For Oracle: Enter the source ALM/PC12.6x Site Admin or
only) LAB_PROJECT schema's (Oracle user) password.
For MS-SQL (SQL Auth): Password for the ‘td’ user with at
least read permissions, or the login mapped to the ‘td’ user
of the database.

Note: For the database migration, if the ALM Site Admin and LAB
databases were created using SQL Authentication, you should also
use SQL Authentication in the migration configuration; if ALM used
Windows Authentication then you should use Windows Authentication
for migration configuration.

LoadRunner Enterprise (2023-2023 R1) Page 65 of 194

Installation Guide
Installation and configuration

e. In the Connection Details section, select one of the following options:

o Connection String Parameters. Select this option to enter database
server information using the following fields:

Server (MS-SQL only) Type the database server name. For

Host example, dbsrv01.

Port (MS-SQL only) Type the database server port number, or

accept the default port number.
Net (Oracle only) Enter the net service name found in the local
Service tnsnames.ora file.
Name
o Connection string. Select this option to manually edit the database
server connection string, and provide the net service name from the local
tnsnames.ora file.
f. Click Test Connection to check whether you can connect to the database
server using the user credentials you provided.
g. Click Next.
12. Check the configuration summary.
The Summary page opens, and displays the configuration settings you
selected. Review and confirm the details.
To change any settings, click Edit in the relevant section to open the
corresponding page in the wizard, and make the necessary changes.
Click Start Configuration to start the configuration.

Note: Make sure the Windows Services Manager is closed when running
the configuration.

13. Database schema creation or upgrade.

Note: Database schema creation is not supported in LoadRunner

Enterprise 2023 R1 and later versions.

LoadRunner Enterprise (2023-2023 R1) Page 66 of 194

Installation Guide
Installation and configuration

After the configuration process is completed successfully, the DB Schema

Creation page opens, and displays the progress of the database schema
creation.

Note: The DB Schema Creation or DB Schema Upgrade page opens,

displaying the progress of the database schema creation or upgrade
(depending on whether you are creating the DB schema when migrating
projects from ALM, or upgrading the DB schema for existing LoadRunner
Enterprise projects).

14. The background configuration starts.

After the DB schema has been created or upgraded, the Configuration
Process page opens, and displays the progress bar as it performs the
configurations on the relevant component.
The wizard performs the following configurations on the relevant component:
LoadRunner LoadRunner
Configuration Enterprise Server Enterprise Host

Copies and updates configuration files. Yes Yes

Creates the LoadRunner Enterprise system user. Yes No (The user is

For details on changing the system user, see created when
Change the LoadRunner Enterprise system user in adding a host to
the LoadRunner Enterprise Help Center. LoadRunner
Enterprise
Administration)

Configures DCOM objects. No (the DCOM No (the DCOM

objects are objects are
configured when configured when
adding a server to adding a host to
LoadRunner LoadRunner
Enterprise Enterprise
Administration) Administration)

LoadRunner Enterprise (2023-2023 R1) Page 67 of 194

Installation Guide
Installation and configuration

LoadRunner LoadRunner
Configuration Enterprise Server Enterprise Host

Installs LoadRunner Enterprise services: Yes (*except for Yes (**except for
l LoadRunner Data Collection Agent* LoadRunner Data LoadRunner Alerts
Collection Agent) Service and
l LoadRunner Remote Management Agent Service
LoadRunner
l LoadRunner Alerts Service (available in Backend Service)
LoadRunner Enterprise**
l LoadRunner Backend Service**
For details on how to reconfigure the port used by
the LoadRunner Data Collection Agent service, see
Software Self-solve knowledge base article
KM01526547.

Installs LoadRunner Enterprise services: -- Yes

l LoadRunner Agent Service
l LoadRunner Data Service
l LoadRunner Load Testing Service

LoadRunner Enterprise (2023-2023 R1) Page 68 of 194

Installation Guide
Installation and configuration

LoadRunner LoadRunner
Configuration Enterprise Server Enterprise Host

Configures IIS: Yes --

l Creates virtual directories and application pools.
l Configures IIS application pools to work as 32-
bit application pools.
l Sets the .NET version for the application pools to
.NET 4 (v4.0.30319).
l Sets Integrated mode for the application pools.
l Sets read and write permissions for the Modules
feature.
l Updates Mime type list.
l Updates IIS Feature Delegation.
For IIS 8.0/8.5/10:
l Adds rules: IIS-ASP, IIS-ASPNET, IIS-ASPNET45,
IIS-ManagementConsole, IIS-Metabase,
IIS-IIS6ManagementCompatibility, IIS-
StaticConten,
IIS-HttpCompressionDynamic.
l Disables rules: IIS-URLAuthorization
If the configuration is stuck in the "Updating IIS
installation" stage (at about 40% progress) for more
than 15 minutes, there might be a lock conflict if
Windows Update is running in parallel. We
recommend canceling and restarting the
configuration.

15. Complete the configuration.

Upon completion of schema creation, the Finish page opens.
To view the configuration log files click the Open Configuration Log link. The
files are also available on the LoadRunner Enterprise server or host from
<installation folder>\orchidtmp\Configuration\configurationWizardLog_
pcs.txt.

Note:
l To prevent Denial-of-Service (DoS) attacks on LoadRunner Enterprise
servers, we recommend configuring Dynamic IP Restrictions for IIS.

LoadRunner Enterprise (2023-2023 R1) Page 69 of 194

Installation Guide
Installation and configuration

For details, see Using Dynamic IP Restrictions in the Microsoft

IIS documentation.
l After completing the configuration process, if the site is accessed from
a public network, we recommend configuring IIS for accessing HTTPS
protocols only. For details, see "Configure IIS to work with TLS/SSL" on
page 124.
l If you are using the TLS 1.2 protocol, we recommend disabling the
3DES and RC4 ciphers on Windows servers by removing them from
the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
Cryptography\Configuration\Local\SSL\00010002 registry. You can
check the list of the ciphers on a machine by running the Get-
TlsCipherSuite command in PowerShell.

Click Finish to exit the Configuration wizard.

16. Perform additional required LoadRunner Enterprise configuration steps.
For details, see "Post-installation configuration steps" on page 84.

Note: After installing and configuring LoadRunner Enterprise, you need to

restart the virtual machine on which the LoadRunner Enterprise server is
installed.

Secure communication and the system user

This topic provides information on LoadRunner Enterprise communication security
and the LoadRunner Enterprise system user.

Overview
During installation of the LoadRunner Enterprise servers and hosts, a
Communication Security passphrase is defined which enables secure
communication between the LoadRunner Enterprise components. You can update
the Communication Security passphrase on the LoadRunner Enterprise system
components. For details, see "Update the Communication Security passphrase" on
the next page.

LoadRunner Enterprise also creates a default system user for use by the
LoadRunner Enterprise server and hosts, the Site Management console, and the

LoadRunner Enterprise (2023-2023 R1) Page 70 of 194

Installation Guide
Installation and configuration

Load Generator standalone machines. You can change the system user using the
System Identity Changer Utility. For details, see "Change the system user" below.

Update the Communication Security passphrase

This task describes how to update the Communication Security passphrase on the
LoadRunner Enterprise system components. The Communication Security
passphrase must be identical on all of the components of the system.

1. From the LoadRunner Enterprise server installation's bin directory, open the
System Identity Changer Utility (<LRE server installation
directory>\bin\IdentityChangerUtil.exe).

Note: You can run this utility from any one of the LoadRunner Enterprise
servers in the system.

2. The System Identity Changer Utility opens. For user interface details, see
"System Identity Changer Utility" on page 74.
In the Communication Security Passphrase section, select Change, and enter
the new Communication Security passphrase.

3. Click Apply.
After the Communication Security passphrase has been successfully updated
on the LoadRunner Enterprise components, you must reset IIS and restart the
LoadRunner Backend Service and the LoadRunner Alerts Service on the
LoadRunner Enterprise servers.

Change the system user

During installation of the server and hosts, a default LoadRunner Enterprise system
user, IUSR_METRO (default password P3rfoRm@1nceCen1er), is created in the
Administrators user group of the server/host machines.

The LoadRunner Enterprise server is installed with the System Identity Changer
Utility that enables you to manage the LoadRunner Enterprise system user on the
LoadRunner Enterprise server and hosts from one centralized location. Use this
utility to update the LoadRunner Enterprise system user name and password.

LoadRunner Enterprise (2023-2023 R1) Page 71 of 194

Installation Guide
Installation and configuration

Note: To prevent security breaches, you can replace LoadRunner

Enterprise's default system user by creating a different local system user, or
by using a domain user.

When you change the system user, or a user's password, the System Identity
Changer Utility updates the LoadRunner Enterprise components.

To change the system user:

1. Prerequisites
l When changing the system user, LoadRunner Enterprise must be down. That
is, all users must be logged off the system and no tests may be running.
l When changing the user password:
o Ensure that each host is listed in the Machines table under one alias only.
o In the case of a domain user, when the domain IT team notifies you that the
password is to be changed, you need to temporarily change the
LoadRunner Enterprise system user on the LoadRunner Enterprise server
and hosts to a different user. After the domain IT team has changed the
password of the domain user and has notified you of this change, you need
to change the LoadRunner Enterprise system user back to the domain user
on the LoadRunner Enterprise server and hosts.

Note: This utility does not apply changes to UNIX machines, Standalone
load generators, or machines that are located over the firewall.

2. Launch the System Identity Changer Utility on the LoadRunner Enterprise

server
In the LoadRunner Enterprise server installation's bin directory, open the
System Identity Changer Utility (<LRE server installation
directory>\bin\IdentityChangerUtil.exe).
The System Identity Changer Utility opens. For user interface details, see
"System Identity Changer Utility" on page 74.
3. Change the details of the LoadRunner Enterprise user

LoadRunner Enterprise (2023-2023 R1) Page 72 of 194

Installation Guide
Installation and configuration

a. Enter the relevant details to update and click Apply.

b. In the lower part of the utility window, the Machines table displays the
status of each machine during the configuration process.
c. The utility performs steps in the following order:
i. LoadRunner Enterprise hosts are reconfigured first. Any failures at this
phase won't stop the process from continuing.
ii. If you are using a cluster environment with multiple LoadRunner
Enterprise servers, all LoadRunner Enterprise servers except for the
one from which the utility is running are reconfigured. Any failures at
this phase won't stop the process from continuing.
iii. The LoadRunner Enterprise server from which the utility is running is
reconfigured. Failure at this level is critical, and prevents the process
from continuing.
iv. The configuration shared by all LoadRunner Enterprise environments is
updated. This step is dependent on the previous step succeeding.
d. The utility attempts to configure all the hosts, even if the configuration on
one or more hosts is unsuccessful. In this case, after the utility has
attempted to configure all the hosts, correct the errors on the failed hosts
and click Reconfigure. The utility runs again on the whole system.
For details on troubleshooting System Identity Changer Utility issues, see
"Troubleshoot System Identity Changer and system user issues" on
page 80.
4. Verify that the system user was changed on the LoadRunner Enterprise server
a. Open IIS Manager. Under Sites > Default Web Site, choose a virtual
directory.
b. Under Authentication select Anonymous Authentication. Verify that the
anonymous user defined was changed for the following virtual directories:
PCS, LoadTest and Files (a virtual directory in LoadTest).
c. Check in the PCQCWSAppPool and LoadTestAppPool application pools
that the identity is the LoadRunner Enterprise user.

LoadRunner Enterprise (2023-2023 R1) Page 73 of 194

Installation Guide
Installation and configuration

System Identity Changer Utility

This utility enables you to update the LoadRunner Enterprise Communication
Security passphrase, as well as the LoadRunner Enterprise system user and/or
password on the LoadRunner Enterprise server, hosts, and Site Management
console from one centralized location.

You can open the System Identity Changer Utility from <LRE server installation
directory>\bin\IdentityChangerUtil.exe.

Note:
l When using the System Identity Changer Utility, you should always
authenticate with internal authentication using the initial admin user and
password provided during LoadRunner Enterprise configuration, no matter
which authentication type is in use.
l For a single tenant environment: Only a Site Admin user can log into the
System Identity Changer Utility.
l For a multi-tenant environment: Only a Site Management user can log into
the System Identity Changer Utility. For details, see Multi-tenancy in the
LoadRunner Enterprise Help Center.

UI Elements Description

Applies the selected changes on the LoadRunner Enterprise

Apply server and hosts, starting with the LoadRunner Enterprise
server.

If, when applying a change, there are errors on any of the

Reconfigure LoadRunner Enterprise hosts, troubleshoot the problematic
host machines, then click Reconfigure. The utility runs again
on the LoadRunner Enterprise server and hosts.

LoadRunner Enterprise (2023-2023 R1) Page 74 of 194

Installation Guide
Installation and configuration

UI Elements Description

LoadRunner The LoadRunner Enterprise system user details.

Enterprise User l Change. Enables you to select which detail to change.
l None. Do not change the user's name or password.

l Password Only. Enables you to change only the

LoadRunner Enterprise system user's password.

Note: See "Prerequisites" on page 72.
l User. Enables you to change the LoadRunner Enterprise

system user name and password.

l Domain\Username. The domain and user name of the
LoadRunner Enterprise system user.
l Password/Confirm Password. The password of the
LoadRunner Enterprise system user.
l Delete Old User. If you are changing the user, this option
enables you to delete the previous user from the machine.
Note: You cannot delete a domain user.

LoadRunner Enterprise (2023-2023 R1) Page 75 of 194

Installation Guide
Installation and configuration

UI Elements Description

User Group The details of the user group to which the LoadRunner
Enterprise system user belongs.
Group type. The type of user group.
l Administrator Group. Creates a user in the
Administrators group with full administrator policies and
permissions.
l Other. Creates a local group under the Users group,

granting policies and permissions as well as other

LoadRunner Enterprise permissions.
Note: To configure LoadRunner Enterprise with a
configuration user and a restricted user, you must specify a
Group type. If the group type is not the Administrator
Group, you must set the group with full permission over the
LoadRunner Enterprise repository prior to applying the
change from the System Identity Changer Utility. To do so:
1. On the LoadRunner Enterprise server(s), navigate to the
LoadRunner Enterprise repository.
2. Right-click the folder, and select Properties.
3. Select the Security tab.
4. Edit the "Group or user names" section.
5. Add the group you intend to use in the System Identity
Change Utility.
6. Allow this group to have Full control and apply the
change.

LoadRunner Enterprise (2023-2023 R1) Page 76 of 194

Installation Guide
Installation and configuration

UI Elements Description

Configuration If you are creating a non-administrative LoadRunner

User Enterprise system user, that is, if you selected Other under
User Group, you need to configure a configuration user (a
system user with administrative privileges) that the non-
administrative LoadRunner Enterprise system user can
impersonate when it needs to perform administrative tasks.
For details, refer to "Change the system user" on page 71.
If you selected Delete Old User in the LoadRunner
Enterprise User area, ensure that the configuration user you
are configuring is not the same as the system user you are
deleting. Alternatively, do not delete the old user.
l Domain\Username. The domain and user name of a
system user that has administrator privileges on the
LoadRunner Enterprise server and hosts.
l Password/Confirm Password. The password of a system
user that has administrator privileges on the LoadRunner
Enterprise server and hosts.

Communication The Communication Security passphrase that enables the

Security LoadRunner Enterprise servers and hosts to communicate
Passphrase securely.
l Change. Enables you to change the passphrase.
l New passphrase. The new Communication Security
passphrase.
Note: This passphrase must be identical on all
LoadRunner Enterprise components. For details, refer to
the "Update the Communication Security passphrase" on
page 71.

LoadRunner Enterprise (2023-2023 R1) Page 77 of 194

Installation Guide
Installation and configuration

UI Elements Description

Machines grid The machine configuration settings:

l Type. Indicates whether the machine type is a
LoadRunner Enterprise server or a host.
l Name. The machine name.
l Configuration Status. Displays the configuration status
on each of the LoadRunner Enterprise components.
l Configuration complete. The system user

configuration was completed.

l Needs to be configured. The LoadRunner Enterprise

server/host is pending configuration. Displayed only

after the LoadRunner Enterprise server configuration is
complete.
l Configuring..... The LoadRunner Enterprise server/host

is being configured.
l Configuration failed. The LoadRunner Enterprise

server/host configuration failed. The utility displays the

reason for failure together with this status.
Note: See "Change the details of the LoadRunner
Enterprise user" on page 72.

Configure a non-administrator system user

For stronger security, you can configure the LoadRunner Enterprise system to use
a non-administrator user and a custom group (lockdown mode).

This system user has the same permissions granted to any user in the built-in
‘Users’ group with additional extended rights to Web services and the file system
and registry as described below:

l Granted all the privileges described in "Required policies for the system user" on
the next page.
l Added to the built-in system groups Performance Log Users and IIS_IUSRS (on
LoadRunner Enterprise server only).
l The custom group is added to the built-in system groups Distributed COM
Users and Users.

LoadRunner Enterprise (2023-2023 R1) Page 78 of 194

Installation Guide
Installation and configuration

With the above-mentioned permissions, a system user cannot perform all of the
administrative system tasks. Therefore, when configuring the system to use non-
administrator user, you need to specify a configuration user (a user with
administrative privileges that is defined on the LoadRunner Enterprise server and
hosts).

This configuration user is used by LoadRunner Enterprise when administrative

tasks are required by system. For example, tasks for changing a system user,
resetting IIS, restarting services, accessing IIS metadata, configuring DCOM.

After completing such tasks, the system user reverts back to the previous user
with the limited LoadRunner Enterprise user permissions.

Note: The configuration user is saved in the database, so that whenever an

administrative-level system user is required to perform a task, the system
automatically uses the configuration user, without prompting for the user's
credentials.

Required policies for the system user

This section describes the required policies LoadRunner Enterprise grants
automatically to a system user.

Note: This section applies to:

l An administrative or non-administrative LoadRunner Enterprise user.
l All LoadRunner Enterprise servers and hosts.

The LoadRunner Enterprise user must be granted all of the following policies:

Policy Name Reason

Create global object For Autolab running Vusers on the Controller.

(SeCreateGlobalPrivilege)

Batch logon rights The minimum policies required to run Web

(SeBatchLogonRight) applications.

Service logon rights The minimum policies required to run Web

(SeServiceLogonRight) applications.

LoadRunner Enterprise (2023-2023 R1) Page 79 of 194

Installation Guide
Installation and configuration

Policy Name Reason

Access this computer from The minimum policies required to run Web
the network applications.
(SeNetworkLogonRight)

Log on locally Required by infra services. For example, after

(SeInteractiveLogonRight) reboot, the system logs in with the LoadRunner
Enterprise system user.

Impersonate a client after Required for running LoadRunner Enterprise

authentication processes under the LoadRunner Enterprise
(SeImpersonatePrivilege) system user.

Troubleshoot System Identity Changer and system user

issues
This section provides information for troubleshooting issues related to the System
Identity Changer utility and the LoadRunner Enterprise system user.

Error running the System Identity Changer utility

Problem Description

When running IdentityChangerUtil.exe, you receive the following error: “Another

instance is already running. Please switch to it.”

This is because there is another instance of the System Identity Changer utility
already running.

Troubleshooting

l If you can see the other instance, you should use that one, or close it and then
restart the utility.
l If you cannot see the other instance of the utility, it means that another user is
running it on the same machine. Switch to the other user and close the utility
before attempting to run it with a different username.

Unable to connect to the LoadRunner Enterprise Server

Problem Description

LoadRunner Enterprise (2023-2023 R1) Page 80 of 194

Installation Guide
Installation and configuration

When entering the LoadRunner Enterprise site administrator credentials on the

LoadRunner Enterprise server, the “Unable to connect to the LoadRunner
Enterprise Server” error occurs.

This error can be caused by a number of issues, including connectivity problems,

security settings, or because the LoadRunner Enterprise server services are not up
and running.

Troubleshooting

Verify that the LoadRunner Enterprise Backend Service is up and running.

Error changing the system user

The following are possible error messages you could encounter when trying to
change the system user.

Error Message Description Troubleshooting

Can’t apply changes. You receive this error 1. Log in to LoadRunner

Not all hosts are in idle because one or more of Enterprise Administration
state. the hosts is currently and go to the Hosts
busy with another module. Verify that all
operation. hosts are in the Idle
state.
2. If all of the hosts are in
the Idle state, make sure
that any other hosts that
belong to the host pool
are not idle.
3. Open the System Identity
Changer utility again. For
details, see "System
Identity Changer Utility"
on page 74.

Make sure you have You receive this error Choose a different
entered a different because you are trying to username.
username. change the user to the
current username.

LoadRunner Enterprise (2023-2023 R1) Page 81 of 194

Installation Guide
Installation and configuration

Error Message Description Troubleshooting

Configuration failed: This error might appear l Select Start > Run and
Failed to find the Load because the LoadRunner enter services.msc. In the
Testing Service on Load Testing Service Services window, verify
<machine name>. isn’t running, or because that the LoadRunner Load
Please verify that the the SSO key is defined Testing Service is running.
service exists and that on the host. l Check that the SSO key
it is running. which is defined on the
host matches the SSO key
defined on the
LoadRunner Enterprise
Server. You can check the
SSO key in the following
locations:
l On the LoadRunner

Enterprise Server:
<LoadRunner
Enterprise Server
installation
dir>\dat\PCS.config
l On the host:

<LoadRunner
Enterprise host
installation
dir>\dat\LTS.config
If the keys do not match,
change the key in
LTS.config file on the
host. Then open the
Services window and
restart the LoadRunner
Load Testing Service.

LoadRunner Enterprise (2023-2023 R1) Page 82 of 194

Installation Guide
Installation and configuration

Error Message Description Troubleshooting

One of the following You probably receive Supply a configuration user

error messages this error because the which has administrator
appears: configuration user you privileges on all the
provided does not have machines on which you are
l Problem adding
the required permissions trying to change the user.
required policies
to perform the requested
l Problem adding operation.
user to group
l Problem changing
application pool
identity
l Problem changing
COM settings
l Problem changing
IIS
l Problem changing
password
l Problem changing
PC Group
l Problem creating
group
l Problem creating
user
l Problem deleting
old identity
l Problem removing
user from Admin

Unable to reconfigure LoadRunner Enterprise hosts or servers

Problem Description

Unable to reconfigure hosts or the LoadRunner Enterprise Server from LoadRunner

Enterprise Administration.

This occurs when the System Identity Changer utility failed to configure the
LoadRunner Enterprise Server or hosts, and you have since closed the utility.

Troubleshooting

LoadRunner Enterprise (2023-2023 R1) Page 83 of 194

Installation Guide
Installation and configuration

Perform the change System User task again from the beginning. For details, see
"Change the system user" on page 71.

Denied access to the internal Influx database server

Problem Description

If you uninstall a host and reinstall it again, and during this time the LoadRunner
Enterprise system user name or password is changed, access to the internal Influx
database on the host is denied.

This is because InfluxDB stores its data in a folder that also includes the data of the
previous authentication user. By default, the folder is under <host installation
drive>\orchidtmp\influxdb.

Troubleshooting

You need to delete this folder in order for LoadRunner Enterprise to reconfigure
the database with the new user.

Post-installation configuration steps

After running the LoadRunner Enterprise installation and Configuration wizard, you
must perform additional configuration steps in LoadRunner Enterprise
Administration before you can use the product.

This section includes:

l "Configure LoadRunner Enterprise servers and hosts post-installation" below

l "Log on to LoadRunner Enterprise Administration" on the next page
l "Perform site and lab administration tasks" on page 86
l "Change the database administrator and user passwords" on page 88

Configure LoadRunner Enterprise servers and hosts post-

installation

Note: You can skip these steps if you configured LoadRunner Enterprise
servers and hosts during the installation process.

LoadRunner Enterprise (2023-2023 R1) Page 84 of 194

Installation Guide
Installation and configuration

While you can configure LoadRunner Enterprise servers and hosts during the
installation process, you can also configure them post-installation from the
Configuration wizard in the Start menu. To do so, you must run the wizard as an
administrator.

1. Prerequisites
Install LoadRunner Enterprise. For details, see "Install and configure
LoadRunner Enterprise servers and hosts" on page 50.
2. Launch the Server Configuration Wizard or Host Configuration Wizard from
the Start menu using the Run as administrator option.
For details, see "Configure a LoadRunner Enterprise server or host" on
page 55.

Log on to LoadRunner Enterprise Administration

LoadRunner Enterprise administration tasks are performed in LoadRunner
Enterprise Administration.

To log in to LoadRunner Enterprise Administration:

1. Open your Web browser (Chrome, Edge, Firefox and Safari are supported) and
type the LoadRunner Enterprise Administration URL in the following format:

http://<LoadRunner_Enterprise_Server_name>/admin

The LoadRunner Enterprise Administration Login window opens.

2. In the User Name box, type your user name. Only a Site or Tenant Admin user
can log on to LoadRunner Enterprise Administration. For details, see
Administrator user types in the LoadRunner Enterprise Help Center.

Note: The first time you log in to LoadRunner Enterprise Administration,

you must use the site administrator name that you specified during the
installation of LoadRunner Enterprise (see page 62). After you log in to
LoadRunner Enterprise Administration, you can define additional site
administrators. For details, see Define a LoadRunner Enterprise site
administrator in the LoadRunner Enterprise Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 85 of 194

Installation Guide
Installation and configuration

3. In the Password box, type the site administrator password.

If you are logging in using your internal LoadRunner Enterprise password, you
can reset the password by clicking Forgot or want to change your password
(not available when using LDAP or SSO authentication).
4. Select the language for displaying the LoadRunner Enterprise user interface.
The multilingual user interface, or MLU, provides support for multiple
languages on a single instance of LoadRunner Enterprise without having to
install language packs. Supported languages are English, French, Italian,
Korean, German, Japanese, Simplified Chinese, and Spanish.
5. Click the Login button. LoadRunner Enterprise Administration opens.

Perform site and lab administration tasks

After installing LoadRunner Enterprise servers and hosts, you perform the site and
lab administration tasks from LoadRunner Enterprise Administration.

1. Log on to LoadRunner Enterprise Administration.

For details, see "Log on to LoadRunner Enterprise Administration" on the
previous page.
2. Perform site configuration tasks.
Configure the authentication method which allows users to log in to
LoadRunner Enterprise, and define the project file repository.
For details, see Select authentication type and Project repository in the
LoadRunner Enterprise Help Center.
3. Create and maintain projects.
You can create and maintain projects, and define the limits and other settings
for the project from Management > Projects.
For details, see Manage projects in the LoadRunner Enterprise Help Center.
4. Create and manage users and user roles.
You can create users and control access to a project by defining the users who
can log in to the project, and by specifying the types of tasks (roles) each user
may perform from Management > Users.

LoadRunner Enterprise (2023-2023 R1) Page 86 of 194

Installation Guide
Installation and configuration

For details, see Manage users in a project and Assign roles and permissions in
the LoadRunner Enterprise Help Center.
5. Add or reconfigure LoadRunner Enterprise hosts.
To work with hosts, you must first add them to LoadRunner Enterprise
Administration and define the host's location. If the host is a load generator
over a firewall, you must define the MI Listener through which the load
generator communicates with the LoadRunner Enterprise server.
When adding hosts, the system configures the LoadRunner Enterprise user on
that machine. For details, see Add a host in the LoadRunner Enterprise Help
Center.

Note:
l If you upgrade LoadRunner Enterprise from an earlier version, or
migrate an existing LAB_PROJECT from ALM (direct migration is
supported up to LoadRunner Enterprise 2023), and the hosts become
unavailable, you need to reconfigure them as follows:
i. Install the latest LoadRunner Enterprise version (see "Upgrade
LoadRunner Enterprise" on page 50).
ii. In LoadRunner Enterprise Administration, select Management >
Hosts.
iii. Select the hosts you want to reconfigure in the Hosts grid, and
click Reconfigure Host.
l If you upgrade from LoadRunner Enterprise 2023 or earlier and the
hosts are available, we still recommend reconfiguring them after
installing or upgrading to the current version.

6. Run a system health check.

After adding a LoadRunner Enterprise server to the system, and adding or
reconfiguring LoadRunner Enterprise hosts, you should perform a system
health check to make sure all components are running as expected.
For details, see Perform a system health check in the LoadRunner Enterprise
Help Center.
7. Set the license keys.

LoadRunner Enterprise (2023-2023 R1) Page 87 of 194

Installation Guide
Installation and configuration

To run tests from LoadRunner Enterprise, you must install the appropriate
LoadRunner Enterprise server and host licenses.
For details, see Manage licenses in the LoadRunner Enterprise Help Center.

Change the database administrator and user passwords

You can change the DB Administrator and User passwords that you configured for
the LoadRunner Enterprise server from the Database Passwords Changer utility in
the Start menu.

1. Stop the LoadRunner Backend Service.

2. Change the DB Administrator and/or User passwords (according to the
required change) on the database server.
3. Run the Database Passwords Changer utility from the Start menu, and enter
the new password for the LoadRunner Enterprise DB Administrator and/or
User.

Note for Oracle databases only: Changing the username password

affects only the LRE_SITE_MANAGEMENT_DB and LRE_SITE_ADMIN_DB
user's password.

For more details on DB Administrator and User credentials, see the "Configure
the connection to the LoadRunner Enterprise database server." on page 57
4. Upon successful completion of the utility, restart the LoadRunner Backend
Service.

LoadRunner Enterprise (2023-2023 R1) Page 88 of 194

Installation Guide
Installation and configuration

Install LoadRunner Enterprise silently

A silent installation is an installation that is performed automatically, without the
need for user interaction. This section describes how to perform a silent
installation of LoadRunner Enterprise components.

Before you perform the installation, review the pre-installation information,

including the system requirements, described in "Before you install" on page 9.

This section includes:

l "Prerequisite software for silent installation" below

l "Customize silent installation" on page 91
l "Silently install LoadRunner Enterprise server and hosts" on page 93

Prerequisite software for silent installation

Install the prerequisite software silently by running the relevant commands as
follows:

Prerequisite
Software Command

.NET Framework <Installation_Disk_Root_

4.8 Directory>\Setup\Common\dotnet48\ndp48-x86-x64-
allos-enu.exe /LCID /q /norestart /c:"install /q"
Note: .NET Framework 4.8 replaces the .NET Framework
4.6.2 and earlier files. If there are any applications that are
using the .NET Framework 4.6.2 or earlier files and are
running during the installation of .NET Framework 4.8, you
may need to restart your machine. If you are prompted to
restart the machine, restart it before continuing the
installation. For details, see the .NET documentation.

.Net core <Installation_Disk_Root_

hosting Directory\Setup\Common\dotnet_hosting\dotnet-
hosting-<version_number>-win.exe /quiet OPT_NO_
l 3.1.3 in LRE
RUNTIME=1 OPT_NO_SHAREDFX=1 OPT_NO_X86=1
2023
l 6.0.15 in LRE
2023 R1 or later

LoadRunner Enterprise (2023-2023 R1) Page 89 of 194

Installation Guide
Installation and configuration

Prerequisite
Software Command

Microsoft <Installation_Disk_Root_
Access Directory\Setup\Common\AccessDatabaseEngine_
Database Engine x64\accessdatabaseengine_X64.exe /quiet /norestart
2016

Microsoft Visual For 2015-2019 (LRE 2022 R1 or earlier):

C++
<Installation_Disk_Root_
Redistributable
Directory>\Setup\Common\vc2015_redist_x86\vc_
for Visual Studio
redist.x86.exe /quiet /norestart
2015-2019 /
2015-2022 For 2015-2022 (LRE 2022 R2 or later on LRE hosts only):
<Installation_Disk_Root_
Directory>\Setup\Common\vc2022_redist_x86\vc_
redist.x86.exe /quiet /norestart

Microsoft Visual For 2015-2019 (LRE 2022 R1 or earlier):

C++
<Installation_Disk_Root_
Redistributable
Directory>\Setup\Common\vc2015_redist_x64\vc_
for Visual Studio
redist.x64.exe /quiet /norestart
2015-2019 /
2015-2022 For 2015-2022 (LRE 2022 R2 or later on LRE hosts only):
(x64)
<Installation_Disk_Root_
Directory>\Setup\Common\vc2022_redist_x64\vc_
redist.x64.exe /quiet /norestart

Internet See the Microsoft documentation for the PowerShell

Information command required for your IIS version.
Services (IIS)
Note: LoadRunner Enterprise Server only.

LoadRunner Enterprise (2023-2023 R1) Page 90 of 194

Installation Guide
Installation and configuration

Customize silent installation

This section describes how to customize the file used for silent configuration of the
LoadRunner Enterprise. The UserInput.xml file—installed with LoadRunner
Enterprise—contains parameters for the LoadRunner Enterprise server and
LoadRunner Enterprise host configurations.

You can customize the parameters in the UserInput.xml file. You then instruct the
Installer to use the customized file for the silent configuration input.

To configure the properties in the UserInput.xml file:

1. Copy the UserInput.xml file from the LoadRunner Enterprise installation
directory (...\Setup\Install\[Host][Server]\) to another location.
2. Open the copy of the file and enter a user-defined value for the LW_CRYPTO_
INIT_STRING property.

Note: This passphrase must be identical to the passphrase defined

during the installation.

LoadRunner Enterprise (2023-2023 R1) Page 91 of 194

Installation Guide
Installation and configuration

3. Configure the following properties on the LoadRunner Enterprise Server:

Property Description

IIS_WEB_SITE_ Choose the IIS web site used to host the LoadRunner
NAME Enterprise server services.
Note:
l The web site must exists prior to running the

configuration.
l The value is optional. If no web site is specified and

there is more than one defined on your machine, the

configuration uses the first one (the one with the
smallest ID value).

SystemUserName Choose the name of the user configured as the

LoadRunner Enterprise Windows system user.
Note: You can use a local or a domain user:
l If you are using a local user, the user is added to the

Administrator group.
l If you are using a domain user, the value for this

property should be in the form of <domain\user>.

Make sure the machine and the user are part of the
same domain and that the user exists on the
machine.
l If you do not provide a user name, the system uses

the default user name ('IUSR_METRO').

l A user name cannot include the following

characters [ ] : | < + > = ; , ? * @

l If the supplied user's details are invalid (for

example, the user name contains invalid characters,

or the domain user does not exist), the system uses
the default user name ('IUSR_METRO') instead.
For details on defining a user, see "Install and
configure LoadRunner Enterprise servers and hosts"
on page 50.

LoadRunner Enterprise (2023-2023 R1) Page 92 of 194

Installation Guide
Installation and configuration

Property Description

SystemUserPwd Choose the password for the LoadRunner Enterprise

Windows system user.
Note:
l If the installer uses the default user (for example,

when the value for property 'SystemUserName' is

empty), the password property is ignored and the
installer uses the default password
(‘P3rfoRm@1nceCen1er’).
l A password cannot include the following characters

< > | & " ^ or space.

l A password cannot be empty. If this field is left

empty, the system uses the default password

(‘P3rfoRm@1nceCen1er’).
l If using an existing user for the ‘SystemUserName’

property, the password must match the password

used by the existing user.

4. Configure the following properties on the LoadRunner Enterprise host:

Property Description

LRASPCHOST=1 Add this property to install LoadRunner as

a LoadRunner Enterprise Host.

IMPROVEMENTPROGRAM=0 The option to participate in the VuGen

improvement program is enabled by
default. Add this property if you want to
disable it. For details, see VuGen
improvement program.

5. Save the UserInput.xml file.

6. Specify the location of the saved file when running the silent installation
command.

Silently install LoadRunner Enterprise server and hosts

This section describes how to run the silent installation of the LoadRunner
Enterprise server and LoadRunner Enterprise hosts on a Windows platform.

The silent installation is followed by the silent configuration which calls the
UserInput.xml file for configuration parameters. You can customize the

LoadRunner Enterprise (2023-2023 R1) Page 93 of 194

Installation Guide
Installation and configuration

parameters in this file for the LoadRunner Enterprise server configuration. For
details, see "Customize silent installation" on page 91.

You can perform a silent installation of LoadRunner Enterprise using one of the
following options:

l "Option 1: Install the prerequisite software and the LoadRunner Enterprise

component" below
l "Option 2: Install the prerequisite software together with the LoadRunner
Enterprise components" on page 96

Note: If you are installing Network Virtualization (NV), you must disable
Windows SmartScreen before proceeding with the silent installation. To do
so, open HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer in the
Registry Editor, and change the Value data for "SmartScreenEnabled" to
"Off".

Option 1: Install the prerequisite software and the LoadRunner

Enterprise component
1. Install the prerequisite software. For details, see "Prerequisite software for
silent installation" on page 89.

Note: If you are prompted to restart the computer after installing the
prerequisite software, you must do so before continuing with the
installation.

2. After you have installed all the prerequisite software, install the LoadRunner
Enterprise component by running the appropriate command from the
command line.

Server installation with default properties

msiexec /i <Installation_Disk_Root_Directory>\Setup\Install\Server\LRE_Server.msi

INSTALLDIR="<Target Installation Directory>" NVINSTALL=Y /qnb /l*vx "<Path to log

file>"

LoadRunner Enterprise (2023-2023 R1) Page 94 of 194

Installation Guide
Installation and configuration

Server installation with customized UserInput.xml

msiexec /i <Installation_Disk_Root_Directory>\Setup\Install\Server\LRE_Server.msi

USER_CONFIG_FILE_PATH="<Full path to UserInput file>" INSTALLDIR="<Target

Installation Directory>" NVINSTALL=Y /qnb /l*vx "<Path to log file>"

Host installation:

msiexec /i <Installation_Disk_Root_Directory>\Setup\Install\Host\LoadRunner_x64.msi

USER_CONFIG_FILE_PATH="<Full path to UserInput file>" [optional installer properties

- see list below] /qn /l*vx "<Path to log file>"

In the above examples:

<Full path to Is the path to your customized UserInput.xml file.

UserInput
file>

<Target Is the directory in which to install the LoadRunner Enterprise

Installation server or host.
Directory>

<Path to log Is the full path to installation log file.

file>

NVINSTALL Indicates whether to launch the NV installation in silent

mode, once the LoadRunner Enterprise installation is done.
By default, NV is not installed in silent mode.

Note: Restarting the machine is required in order for NV to function properly.

LoadRunner Enterprise (2023-2023 R1) Page 95 of 194

Installation Guide
Installation and configuration

Option 2: Install the prerequisite software together with the

LoadRunner Enterprise components
You can also install in silent mode using the setup.exe file from the LoadRunner
Enterprise installation directory. This enables you to install the prerequisites in
silent mode automatically before running the MSI installation in silent mode. Using
this option also invokes the correct MSI file depending on the operating system
platform.

Server installation:

<Installation_Disk_Root_Directory>\Setup\En\setup_server.exe /s

USER_CONFIG_FILE_PATH="<Full path to UserInput file>"

INSTALLDIR="<Target Installation Directory>" NVINSTALL=Y

Host installation:

<Installation_Disk_Root_Directory>\Setup\En\setup_host.exe /s

INSTALLDIR="<Target Installation Directory>"

USER_CONFIG_FILE_PATH="<Full path to UserInput file>" NVINSTALL=Y INSTALL_GATLING=1

INSTALL_JMETER=1

In the above examples:

<Full path to Is the path to your customized UserInput.xml file.

UserInput
file>

<Target Is the directory in which to install the LoadRunner Enterprise

Installation server or host.
Directory>

setup.exe When using the setup.exe file, the installation log is created
under the user's temp directory.
l Host installation: %temp%\LREHost.log
l Server installation: %temp%\LREServer.log

LoadRunner Enterprise (2023-2023 R1) Page 96 of 194

Installation Guide
Installation and configuration

NVINSTALL Indicates whether to launch the NV installation in silent mode,

once the LoadRunner Enterprise installation is done (by default,
NV is not installed in silent mode).

INSTALL_ Supported from version: 2023 R1. In version 2023, Gatling is

GATLING installed automatically.
To install Gatling as part of the OneLG installation, add the
following to the installation command: INSTALL_GATLING=1
By default, Gatling is not installed in silent mode.

INSTALL_ Supported from version: 2023 R1. In version 2023, JMeter is

JMETER installed automatically.
To install JMeter as part of the OneLG installation, add the
following to the installation command: INSTALL_JMETER=1
By default, JMeter is not installed in silent mode.

Note: Restarting the machine is required in order for NV to function properly.

Installing an upgrade in silent mode

If you are installing an upgrade, run the following command:

msiexec.exe /update <full path to msp file> [/qn] [/l*vx <full path to log file>]

The msp files are located in the installation package.

The /qn option sets the silent mode and /l*vx enables logging in verbosity mode.

Notes and limitations

If you attempt to download Network Virtualization installation files from the
Internet or an FTP site, the files are blocked to protect the computer from
untrusted files and you get the following message:

LoadRunner Enterprise (2023-2023 R1) Page 97 of 194

Installation Guide
Installation and configuration

Resolution: Before installing NV, unblock the files as follows:

1. Right-click one of the NV installation executable files located in <NV

installation path>\Additional Components\Network Virtualization, and
select Properties.
2. If there is an Unblock checkbox in the General tab, select it and click OK.
3. Verify that the Unblock checkbox is gone.
4. Repeat for each executable file in the Network Virtualization folder.

Deploy LoadRunner Enterprise on AWS

LoadRunner Enterprise is certified to be installed and run under Amazon Web
Services (AWS), using a BYOL (Bring Your Own License) model.

Requirements for deploying LoadRunner Enterprise on the cloud:

l All components of the cloud computing environment follow the system

requirements specified in this document.
l The required ports are open for communication. For the required posts, see
"Communication paths" on page 14.

Note:
l Cloud load generators can be provisioned using the built-in functionality of
LoadRunner Enterprise. For details, see Manage Load Generators on the
Cloud in the LoadRunner Professional Help Center and Provision cloud
load generators in the LoadRunner Enterprise Help Center. All other
components must be manually installed and configured by the user.

LoadRunner Enterprise (2023-2023 R1) Page 98 of 194

Installation Guide
Installation and configuration

l To improve performance, it is preferable to deploy the LoadRunner

Enterprise server and hosts, and the database in the same region. Consult
AWS for best practices about network performance.
l Cloud load generator ports are configurable. When all the components are
in the cloud, the ports to use are defined by the cloud provider (they are
not based on internal IT policies).

Install standalone components (Windows)

You can install standalone components that provide advanced features for
working with LoadRunner Enterprise.

To install a load generator on Linux, see "Install Load Generator on Linux" on

page 103.

Note: For all standalone applications, you must first manually install the
prerequisite applications. For details, see "Prerequisite software for silent
installation" on page 89

This section includes:

l "Available standalone components for Windows" below

l "Install standalone components" on the next page
l "Silently install standalone applications" on page 101

Available standalone components for Windows

The following standalone components are available. To install these components,
see "Install standalone components" on the next page.

LoadRunner Enterprise (2023-2023 R1) Page 99 of 194

Installation Guide
Installation and configuration

Component Description

OneLG Instead of installing a LoadRunner Enterprise Host and then

configuring it as a load generator, you can install a standalone
version of the load generator (OneLG). This host can behave
only as a load generator, unlike the LoadRunner Enterprise host,
which can also be configured as a Controller or data processor.
You can use a local or a cloud-based machine to host your load
generator.
Note: If you know in advance that a particular host machine is to
be used as a load generator only, we recommend that you install
OneLG for the following reasons:
l The installation requires less disk space
l Moving the load generator's setup files is less time consuming
than moving the setup files of the LoadRunner Enterprise
Host.

Virtual User Virtual User Generator (VuGen) generates virtual users, or

Generator Vusers, by recording actions that typical end-users would
perform on your application. VuGen records your actions into
automated Vuser scripts which form the foundation of your
performance tests.

LoadRunner Analysis provides graphs and reports with in-depth performance

Analysis analysis information. Using these graphs and reports, you can
pinpoint and identify the bottlenecks in your application and
determine what changes need to be made to your system in
order to improve its performance.

MI Listener The MI Listener is one of the components needed to run Vusers

and monitor applications over a firewall. To install, run
SetupMIListener.exe. For details about firewalls in LoadRunner
Enterprise, see "Working with firewalls" on page 147.

Monitor Over Used to monitor servers that are located over a firewall. For
Firewall details about firewalls in LoadRunner Enterprise, see "Working
Agent with firewalls" on page 147.

Install standalone components

This section describes the installation process for standalone components.

1. From the LoadRunner Enterprise installation directory, run setup.exe. The

setup program displays the installation menu page.

LoadRunner Enterprise (2023-2023 R1) Page 100 of 194

Installation Guide
Installation and configuration

2. Select one of the following options: OneLG, VuGen, Analysis, MI Listener, or

Monitors Over Firewall. For details, see the LoadRunner Installation Guide
available from the LoadRunner Professional Help Center.

Note:
l During the installation of Load Generator Standalone, MI Listener, or
Monitors over Firewall components, the setup wizard prompts you to
select the mode for running the installed agent. Select LoadRunner
Enterprise mode.
The agent runs as a service under a special account named IUSR_
METRO. This is a local Windows account, created during the
installation process (some additional LoadRunner Enterprise
configuration is also added on the load generator).
You can delete the IUSR_METRO account only if the LoadRunner
Enterprise system user was configured to a different Windows
account; otherwise the host does not function correctly.
l If you attempt to install standalone components on a system drive
other than the default C drive, you get a warning that you are out of
disk space on your system drive even though you are not installing
there. This is because the installer, while installing the components to
the drive as specified by the user, still needs to use the Windows
temporary file locations during installation.
Workaround: Free up space on your C system drive.

3. (MI Listener/Monitors Over Firewall installations only) Follow the instructions in

the installation wizard. After installation, the configuration wizard opens,
requesting the name of the product you are working with. Select LoadRunner
Enterprise.

Silently install standalone applications

This section describes how to perform a silent installation of the standalone
applications.

Note: For instructions on installing the Load Generator silently on Linux, see
the LoadRunner Installation Guide available from the LoadRunner
Professional Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 101 of 194

Installation Guide
Installation and configuration

Choose one of the following options:

l "Option 1: Install the prerequisite software and the application separately" below
l "Option 2: Install the prerequisite software and the application together" on the
next page

Option 1: Install the prerequisite software and the application

separately
1. Install required prerequisite software. For details, see "Prerequisite software
for silent installation" on page 89.
2. Extract the Load Generator installation files to a local directory:
a. Select an application from the <Installation_Disk_Root_
Directory>\Standalone Applications folder.
b. Extract the .msi file from the .exe application to the installation folder.
3. Run one of the following commands from the command line:

Load Generator:

msiexec /i "<Installation_Folder>\OneLG_x64.msi" /qb /l*vx "<Path to log file>" IS_

RUNAS_SERVICE=1 START_LGA="1"

VuGen Standalone:

msiexec /i "<Installation_Folder>\VuGen_x64.msi" /qb /l*vx "<Path to log file>"

Analysis Standalone:

msiexec /i "<Installation_Folder>\Analysis_x64.msi" /qb /l*vx "<Path to log file>"

where <Installation_Folder> is the local directory where you saved the

installation files, and <Path to log file> is the full path to the installation log file.

Note: You can install the Load Generator component on a Linux platform
to run virtual users. The Linux virtual users interact with the Controller,
installed on a Windows machine. For details on installing the Load

LoadRunner Enterprise (2023-2023 R1) Page 102 of 194

Installation Guide
Installation and configuration

Generator on Linux, see the LoadRunner Installation Guide available from

the LoadRunner Professional Help Center.

Option 2: Install the prerequisite software and the application

together
1. Select an application from the <LRE installation directory>\Additional
Component\Applications folder.
2. Run one of the following commands from the command line:

Load Generator:

SetupOneLG.exe /s /a /s IS_RUNAS_SERVICE=1 START_LGA=1 INSTALLDIR="C:\OneLG"

VuGen Standalone:

SetupVuGen.exe /s /a /s INSTALLDIR="c:\Micro Focus\VuGen_SA"

Analysis Standalone:

SetupAnalysis.exe /s /a /s

Install Load Generator on Linux

You can install the Load Generator component on a Linux platform to run virtual
users. The Linux virtual users interact with the Controller, installed on a Windows
machine. For details on installing the Load Generator on Linux, see the LoadRunner
Installation Guide available from the LoadRunner Professional Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 103 of 194

Installation Guide
Installation and configuration

Deploy Dockerized load generators on Linux

This section describes how to run a Dockerized load generator on a Linux
distribution.

Docker is a platform that allows you to develop, ship, and run applications via a
container. Refer to the product documentation for more details.

Note: For supported protocols on Dockerized load generators, see the

Supported Protocols guide.

Prerequisites
Below is a list of prerequisites that are required to run a Dockerized load generator
on a Linux distribution:

Install Install Docker on the target machine, along with its dependencies,
Docker and set up the target machine environment as required. Currently,
only the 64-bit version is supported.

Obtain Obtain the predefined load generator Docker image. Two images are
Docker available, Linux-Ubuntu and RHEL.
image
Pull the image from the from the relevant page, accessible from the
performance testing page
(https://hub.docker.com/u/performancetesting) in the Docker hub.
Use the following commands and appropriate <tag version number>,
for example, 23.01:
Linux-Ubuntu:
docker pull performancetesting/microfocus_onelg_linux_
ubuntu:<tag version number>
RHEL:
docker pull performancetesting/microfocus_onelg_linux_
rhel:<tag version number>
Note: The Ubuntu image for the OneLG load generator replaces the
previous Ubuntu load generator docker image.

LoadRunner Enterprise (2023-2023 R1) Page 104 of 194

Installation Guide
Installation and configuration

Run a Dockerized load generator using the predefined

image
Use the ready-to-use image to run a load generator on Docker for Linux. If you
need customization for your container, for example, for proxy servers, see "Run a
Dockerized load generator using a custom image" on page 107.

From version 2023 R1:

l The following environment variables are available to enable JMeter and
Gatling on the load generator if required:
l ENABLE_JMETER
l ENABLE_GATLING
In version 2023, JMeter and Gatling are enabled on the load generator by
default.
l If one Docker load generator is configured with either JMeter or Gatling
scripts or both, then all Dockers load generators get these flags as well,
even if they are configured with other scripts types.

To run a Dockerized load generator:

Run the load generator container using the following command for Linux-Ubuntu or
RHEL:

Linux-Ubuntu

Version 2023:

docker run -id -p <host_port>:54345 -e "ONELG_FLAVOR=1" --net=host

performancetesting/microfocus_onelg_linux_ubuntu:<tag version number>

From version 2023 R1:

docker run -id -p <host_port>:54345 -e "ONELG_FLAVOR=1" -e "ENABLE_GATLING=1" -e

"ENABLE_JMETER=1" --net=host performancetesting/microfocus_onelg_linux_ubuntu:<tag
version number>

RHEL

LoadRunner Enterprise (2023-2023 R1) Page 105 of 194

Installation Guide
Installation and configuration

Version 2023:

docker run -id -p <host_port>:54345 performancetesting/microfocus_onelg_linux_rhel:<tag

version number>

From version 2023 R1:

docker run -id -p <host_port>:54345 -e "ENABLE_GATLING=1" -e "ENABLE_JMETER=1"

performancetesting/microfocus_onelg_linux_rhel:<tag version number>

Note: Check that the <host_port> on the Linux machine is available and
allows incoming requests. Specify this port on the Controller side when
connecting to this load generator.

Example using SSH

The following gives a simple C# code example for running multiple load generator
containers using SSH. There are container orchestrator tools which do the same,
for example, Kubernetes, OpenShift, and Docker Swarm.

using (var client = new SshClient(dockerHost, dockerHostUserName, dockerHostPasswd))

client.Connect();

for (int i =0; i > numOfContainers; i++)

string command = "docker run -id -p " + lgInitialPort + i) + ":54345

performancetesting/microfocus_onelg_linux_ubuntu:<tag version number>";

var terminal = client.RunCommand(command);

if (terminal.ExistStatus != 0)

throw new Exception("Failed to create new Docker container");

Console.WriteLine("Docker LG with external port" + lgInitialPort + i + "created.");

client.Disconnect();

LoadRunner Enterprise (2023-2023 R1) Page 106 of 194

Installation Guide
Installation and configuration

Run a Dockerized load generator using a custom image

If your environment requires customized settings for running the container, for
example for proxy servers, you can create a Dockerfile to build a custom image.

Note: Another alternative for customized settings: Start the container; once
it is running, set up the load generator environment variables, then start the
load generator manually inside the container.

To run a custom Dockerized load generator:

1. Create a new folder, and within it create a file named dockerfile. Paste the
FROM line, plus the required customization lines, into the file, using the
appropriate LoadRunner Enterprise version for the <tag version number>:

FROM performancetesting/microfocus_onelg_linux_ubuntu:<tag version number>ENV http_

proxy http://my_proxy_name:port

Note: The above customization example is for a proxy. It defines an

environment variable for the proxy server host and port in the target
image.

2. Save the Dockerfile.

3. Open a command line at the dockerfile folder path and run the following
command, using the name you want for your custom image:

Linux-Ubuntu:

docker build -t <custom dockerfile name> .

RHEL:

docker build -t <custom dockerfile name> .

4. Create a container for each load generator you want to use, by running the
following command:

LoadRunner Enterprise (2023-2023 R1) Page 107 of 194

Installation Guide
Installation and configuration

Linux-Ubuntu:

docker run -id -p <host_port>:54345 <custom image name>

RHEL:

docker run -id -p <host_port>:54345 <custom image name>

If the custom image in step 3 was built with a tag then include it in the
command:

docker run -id -p <host_port>:54345 <custom image name>:<tag version number>

Note: Check that the <host_port> on the Linux machine is available and
allows incoming requests. Specify this port on the Controller side when
connecting to this load generator.

After running the load generator containers

Add the load generators containers to your tests.

l For elastic hosts, see Set up elastic hosts on Windows or Linux containers in the
LoadRunner Enterprise Help Center.
l For manually configure Dockerized load generators, see Add Dockerized hosts
to your tests in the LoadRunner Enterprise Help Center.

Tips and guidelines

l Dockerized load generators, run from the predefined image, are not supported
when running over a firewall. (Workaround for advanced users: You can develop
your own Docker image with MI Listener support.)
l Use docker ps to list the containers that are running.
l To stop the load generator service:
l Use docker stop <load generator container name or ID> if you want to
reuse the same load generator.

LoadRunner Enterprise (2023-2023 R1) Page 108 of 194

Installation Guide
Installation and configuration

l Use docker rm -f <load generator container name or ID> in order to

remove the load generator container.
l The Dockerfile container has an ENTRYPOINT section. The container first runs
the commands in ENTRYPOINT. It sets up the environment and then starts the
load generator. The command uses a While loop to wait for input, in order to
keep the container from exiting. This behavior prevents you from accessing the
container while it is running. Add -i when starting the container to prevent the
While loop from consuming an excessive amount of CPU.
l If you need entry into the container, add an argument such as --
entrypoint=/bin/bash when starting the container. After entering the
container, set the load generator environments and start the load generator. You
can then switch to the host using CTRL+p and CTRL+q while keeping the
container running in the background. To access the container again, use the
docker attach container_id command.
l To access the host network directly, use --net=host in place of -p <host_
port>:54345. We recommend you use this flag if the AUT generates a lot of
network activity.

Deploy Dockerized load generators on Windows

This section describes how to run a Dockerized load generator on a Windows
platform.

Docker is a platform that allows you to develop, ship, and run applications via a
container. Refer to the product documentation for more details.

Note: For supported protocols on Dockerized load generators, see the

Supported Protocols guide.

LoadRunner Enterprise (2023-2023 R1) Page 109 of 194

Installation Guide
Installation and configuration

Prerequisites
Below is a list of prerequisites that are required to run a Dockerized load generator
on a Windows platform:

Install Install Docker on the target machine, along with its dependencies,
Docker and set up the target machine environment as required. Currently,
only the 64-bit version is supported.

Obtain Pull the Windows load generator Docker image accessible from the
Docker performance testing page
image (https://hub.docker.com/u/performancetesting) in the Docker hub.
Use the following command and appropriate <tag version number>,
for example, 23.01:
docker pull performancetesting/microfocus_onelg_
windows:<tag version number>
Note: The Docker image for the OneLG load generator replaces the
previous Windows standalone load generator docker image.

Run a Dockerized load generator using the predefined

image
Use the ready-to-use image to run a load generator (OneLG) on Docker for
Windows. If you need customization for your container, for example, for Java or to
run under a specific user, see "Run a Dockerized load generator using a custom
image" on the next page.

From version 2023 R1:

l The following environment variables are available to enable JMeter and
Gatling on the load generator if required:
l ENABLE_JMETER
l ENABLE_GATLING
In version 2023, JMeter and Gatling are enabled on the load generator by
default.
l Since Java is not installed in the Windows OneLG load generator image,
you need to build a customized image with Java to run JMeter or Gatling
scripts.

LoadRunner Enterprise (2023-2023 R1) Page 110 of 194

Installation Guide
Installation and configuration

l If one Docker load generator is configured with either JMeter or Gatling

scripts or both, then all Dockers load generators get these flags as well,
even if they are configured with other scripts types.

To run a Dockerized load generator:

Run the load generator container using the following command:

Version 2023:

docker run -id -p <host_port>:54345 performancetesting/microfocus_onelg_windows:<tag

version number>

From version 2023 R1:

docker run -id -p <host_port>:54345 -e "ENABLE_GATLING=1" -e "ENABLE_JMETER=1"

performancetesting/load_generator_redhat:<tag version number>

Note: Check that the <host_port> on the machine is available and allows
incoming requests. You specify this port on the Controller side when
connecting to this load generator.

Run a Dockerized load generator using a custom image

If your environment requires customized settings for running the container, you
can create a Dockerfile to build a custom image for Docker on Windows.

Examples for custom images:

l To use a specific user account for the processes under which the Vusers are
running, to provide support for accessing network resources like script
parameter files. After running, the container should be able to verify the user.
l To run Java, Gatling, or JMeter protocols on Windows load generator containers.
l To define environment variables for proxy server host and port.

LoadRunner Enterprise (2023-2023 R1) Page 111 of 194

Installation Guide
Installation and configuration

To run a custom Dockerized load generator:

1. Create a new folder, and within it create a file named dockerfile. Paste the
following FROM line into the file, using the appropriate LoadRunner Enterprise
version for the <tag version number>, and add the relevant customization
lines:

FROM performancetesting/microfocus_onelg_windows:<tag version number><Customization

lines>

For customization examples, see "Examples of customized content for

Dockerfiles " on the next page

Tip: Refer to the Docker documentation for commands that can be used
in Docker files.

2. Save the Dockerfile.

3. Open a command line at the dockerfile folder path and run the following
command, using the name you want for your custom image:

docker build -t <custom dockerfile name> .

4. Create a container for each load generator you want to use, by running the
following command (or use any Docker orchestrator tool for running
containers):

docker run -id -p <host_port>:54345 <custom image name>

If the custom image in step 3 was built with a tag then include it in the
command:

docker run -id -p <host_port>:54345 <custom image name>:<tag version number>

Note:

LoadRunner Enterprise (2023-2023 R1) Page 112 of 194

Installation Guide
Installation and configuration

l Check that the <host_port> on the machine is available and allows

incoming requests. You specify this port on the Controller side when
connecting to this load generator. This is not relevant when using
elastic load generators, since this is managed by the orchestrator.
l To deploy elastic load generators, you must provide the custom image
name in the Swarm orchestrator.

Examples of customized content for Dockerfiles

The following gives an example of dockerfile content for running the Vusers under
a specified user account with network access to shared locations. Replace the
values between <> with credentials for a valid user account in your environment,
with network access to the shared resources.

Example for Vusers under a specified user account:

#escape=`

FROM performancetesting/microfocus_onelg_windows:22.02

RUN c:\LG\launch_service\bin\magentservice.exe -remove

RUN c:\LG\launch_service\bin\magentservice -install <domain>\<user name> <password>

Example of dockerfile content for running Java protocols:

#escape=`

FROM performancetesting/microfocus_onelg_windows:22.02

COPY .\<folder contains JDK> <target path in the container>

The path to the target JDK directory defined in the COPY line for the <target path
in the container> must also be added to the Java VM runtime settings page:

Note: For Java 64-bit protocol testing, include the following command line in
the dockerfile, in order to add the path to the bin folder for the JDK 64-bit to
the machine PATH environment variable:

RUN powershell [Environment]::SetEnvironmentVariable(\"Path\",

$env:Path + \";<target JDK path in the container>\bin\",
[EnvironmentVariableTarget]::Machine)

LoadRunner Enterprise (2023-2023 R1) Page 113 of 194

Installation Guide
Installation and configuration

After running the load generator containers

Add the load generators containers to your tests.

l For elastic hosts, see Set up elastic hosts on Windows or Linux containers in the
LoadRunner Enterprise Help Center.
l For manually configure Dockerized load generators, see Add Dockerized hosts
to your tests in the LoadRunner Enterprise Help Center.

Note: This is not relevant when using orchestrators.

Tips and guidelines

l Dockerized load generators, run from the predefined image, are not supported
when running over a firewall.
l Use docker ps to list the containers that are running.
l To stop the load generator service:
l Use docker stop <load generator container name or ID> if you want to
reuse the same load generator.
l Use docker rm -f <load generator container name or ID> in order to
remove the load generator container.
l To access the host network directly, use --net=host in place of -p <host_
port>:54345. We recommend you use this flag if the AUT generates a lot of
network activity.

Install additional components

You can install additional components that provide advanced features for working
with LoadRunner Enterprise. You install these components from the Additional
Components directory, located in the root directory of the installation directory.
The following components are available:

LoadRunner Enterprise (2023-2023 R1) Page 114 of 194

Installation Guide
Installation and configuration

Component Description

Agent for Installs an optional component on the server machine that

Citrix Server enhances VuGen's capabilities in identifying Citrix client
objects.

Agent for Used for extended RDP protocol record-replay. This

Microsoft component runs on the server side, and is used to create and
Terminal run enhanced RDP scripts.
Server.

Assembly Installs a command-line utility to build a .NET configuration file

Crawler for for a LoadRunner Analysis API application. For details, refer to
Analysis API the Analysis API Reference.

Azure Installs the Azure API Service on Windows machines, which

API Service enables you to run Vuser scripts that include Azure API
functions. For details, see the LoadRunner Professional
Help Center.

Entity Installs a utility that enables users to unlock tests, scripts,

Unlocker monitor profiles, and analysis templates for editing when
locked by that user in another session. It also enables
administrators to unlock entities that have been locked by
other users. For details, see Unlock entities and manage
unlocking jobs in the LoadRunner Enterprise Help Center.
IDE Add-ins Installs add-ins for Visual Studio or Eclipse, enabling you to
create NUnit or JUnit tests in your standard development
environment using the LoadRunner API.

Network Network Virtualization (NV) integrates with LoadRunner

Virtualization Enterprise to help you test point-to-point performance of
network-deployed products under real-world conditions. For
details, see the Network Virtualization for LoadRunner Help.
SAP Tools The following SAP tools are available:
l SAPGUI Spy. Examines the hierarchy of GUI Scripting
objects, on open windows of SAPGUI Client for Windows.
l SAPGUI Verify Scripting. Verifies that the SAPGUI Scripting
API is enabled.

Third Parties Includes the source code for open-source packages that are
incorporated into LoadRunner Enterprise, and which have
licenses with source distribution clauses.

LoadRunner Enterprise (2023-2023 R1) Page 115 of 194

Installation Guide
Installation and configuration

Component Description

Virtual Table Virtual Table Server (VTS) is a web-based application that

Server works with Vuser scripts. VTS offers an alternative to standard
parameterization.
Two versions of VTS are available: 32-bit and 64-bit. You can
install 32-bit VTS on both 32-bit and 64-bit operating systems;
64-bit VTS can be installed only on 64-bit operating systems.

VuGen Script Installs the VuGen Script Converter that enables converting
Converter NUnit/JUnit tests to VuGen scripts in order to run them in
LoadRunner Enterprise.

Uninstall LoadRunner Enterprise server and

hosts
You can uninstall LoadRunner Enterprise servers and hosts using the LoadRunner
Enterprise Setup Wizard or using the silent commands.

Note:
l When uninstalling earlier versions of LoadRunner Enterprise, the Network
Virtualization components installed during the installation are
automatically uninstalled.
l For cluster environments: Uninstall LoadRunner Enterprise from all nodes.

To uninstall LoadRunner Enterprise components using the setup

wizard:
1. From the Windows Control Panel, open the Add/Remove Programs dialog box.
2. From the list of currently installed programs, select the program you want to
uninstall, and click Remove.
l Micro Focus LoadRunner Enterprise <product version> for LoadRunner
Enterprise server
l Micro Focus LoadRunner <product version> for LoadRunner Enterprise
hosts
3. Follow the instructions in the wizard to complete the uninstall process.

LoadRunner Enterprise (2023-2023 R1) Page 116 of 194

Installation Guide
Installation and configuration

To uninstall LoadRunner Enterprise components silently:

Run the applicable command from the command line:

LoadRunner Enterprise Server:

msiexec.exe/uninstall "<Installation_Disk_Root_Directory>\Setup\Install\Server\LRE_
Server.msi" /qnb

LoadRunner Enterprise Host:

msiexec.exe/uninstall "<Installation_Disk_Root_Directory>\Setup\Install\Host\LoadRunner_
x64.msi" /qnb

Uninstall Load Generator from Linux

You can use the Load Generator Setup Wizard to uninstall the load generator. For
details, see the LoadRunner Professional Installation Guide available from the
LoadRunner Professional Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 117 of 194

Post installation verification
This section describes how to verify that the installation of the LoadRunner
Enterprise server and hosts was successful. The environment for this process
should be a staging environment, including a LoadRunner Enterprise server and
two to three LoadRunner Enterprise hosts.

Note: You can run a full validation on your LoadRunner Enterprise system
from LoadRunner Enterprise Administration, in the System Health page's
Check System tab. For details, see Maintain system health in the LoadRunner
Enterprise Help Center.

Administrator workflow
This section describes the workflow for the LoadRunner Enterprise administrator.

1. Log onto LoadRunner Enterprise Administration.

For details, see Log onto LoadRunner Enterprise Administration in the
LoadRunner Enterprise Help Center.
2. Create a project administrator user.
For details, see Create a new user in the LoadRunner Enterprise Help Center.
3. Create a domain.
For details, see Create a domain in the LoadRunner Enterprise Help Center.
4. Create a new project.
Follow the steps to create the project in Create a project in the LoadRunner
Enterprise Help Center, and:
a. In the Domain Name list, select the domain you just created.
b. Skip the Main Details for now (you define them after adding a host and host
pool in step 9).
c. Assign the project administrator user you created above to the Users list.
5. Assign more project administrators to the project - optional.

LoadRunner Enterprise (2023-2023 R1) Page 118 of 194

Installation Guide
Installation and configuration

a. Select Management > Projects, and in the projects list, click the name of
project you created to display the project details.
b. In the right lower pane, click the Users tab, and assign another project
administrator user.
6. Verify the LoadRunner Enterprise configuration.
On the LoadRunner Enterprise Administration sidebar,
l Under Configuration, select Servers and verify that the LoadRunner
Enterprise Server is listed.
l Under Configuration, select Licenses and verify the license details.
7. Define additional hosts for the staging environment.
For the staging environment, you should have two to three LoadRunner
Enterprise hosts, where at least one host purpose is configured as Controller,
and at least one host purpose is configured as Load Generator.

Note: When adding hosts, fields in red marked with an asterisk (*) are
mandatory. Make sure to include the operating system type, and the
purpose of the host. For details, see Manage hosts in the LoadRunner
Enterprise Help Center.

a. On the LoadRunner Enterprise Administration sidebar, under Maintenance,

select Hosts.

b. Click the Create New Host button, and define the host details.

8. Create host pools.

a. On the LoadRunner Enterprise Administration sidebar, select Maintenance
> Hosts, and click the Pools tab.

b. Click the Add New Pool button. The New Pool page opens, enabling you
to define a new host pool.
c. Add a name and description (optional) for the host pool.
d. In the Linked Hosts grid, select the hosts to add to the pool, and click
Assign. The selected hosts are added to the pool.
9. Define project settings.

LoadRunner Enterprise (2023-2023 R1) Page 119 of 194

Installation Guide
Installation and configuration

a. On the LoadRunner Enterprise Administration sidebar, select Management >

Projects.
b. Under the Project Name column, click the project to display the project
details.
c. In the Main Details tab, finish defining the project's settings. In particular, set
the Vuser limit, Host limit, and Concurrent run limit. Also, select the host pool
you created above for the project.

LoadRunner Enterprise (2023-2023 R1) Page 120 of 194

LoadRunner Enterprise configuration
options
The LoadRunner Enterprise system comes with default configuration settings that
enable you to use LoadRunner Enterprise for its intended purpose. This chapter
describes additional tuning and configuration to help you get the most out of your
system.

Note: Not all procedures in this chapter are suitable for all usage scenarios.
You should assess which procedures are suitable to your system's needs.

This chapter includes:

• Configuring LoadRunner Enterprise to work with TLS/SSL 122

• Configure LoadRunner components to work with TLS/SSL 136
• Configure TLS/SSL for load generators 137
• Working with the LoadRunner Enterprise agent 140
• LoadRunner Remote Management Agent 142
• Recommended configuration for Linux load generators 143
• Recommended change to the TEMP folder used by the load generator 143
• Enable downloading standalone applications 144
• Enable MS-SQL Windows authentication 146

LoadRunner Enterprise (2023-2023 R1) Page 121 of 194

Installation Guide
Installation and configuration

Configuring LoadRunner Enterprise to work with

TLS/SSL
The following section describes how to enable TLS to ensure secure
communication on LoadRunner Enterprise. It includes:

l "TLS/SSL configuration workflow" below

l "Configure IIS to work with TLS/SSL" on page 124
l "Distribute certificates" on page 127
l "Configure the LoadRunner Enterprise server to work with TLS/SSL" on page 128
l "Configure LoadRunner Enterprise hosts to work with TLS/SSL" on page 131

Tip: For additional information (and examples) on how to configure secure

communication on the various LoadRunner Enterprise components, see our
blog series:
l Configure LoadRunner Enterprise Server to support SSL
l Configure LoadRunner Enterprise Host to support SSL

TLS/SSL configuration workflow

This section describes the workflow for configuring the LoadRunner Enterprise
server and hosts to work over TLS. You can configure both the LoadRunner
Enterprise server and hosts, or the LoadRunner Enterprise server only.

LoadRunner Enterprise (2023-2023 R1) Page 122 of 194

Installation Guide
Installation and configuration

For the 1. Configure IIS

LoadRunner For details, see "Configure IIS to work with TLS/SSL" on the
Enterprise next page.
Server
2. Add the root certificate to the machine truststore
For details, see "Distribute certificates" on page 127.
3. Configure the LoadRunner Enterprise server to work with
TLS/SSL
a. Replace the certificates* on the LoadRunner Enterprise
server. For details, see "Configure LoadRunner
components to work with TLS/SSL" on page 136.
b. Update and replace the relevant configuration files
(update pcs.config internalUrl with https URL and
replace web.config). For details, see "Configure the
LoadRunner Enterprise server to work with TLS/SSL" on
page 128.
c. Restart the LoadRunner Backend Service and IIS.
d. Update the internal and external URLs with the "https"
URL.

For 1. Add certificates to the machine truststore

LoadRunner For details, see "Distribute certificates" on page 127.
Enterprise
2. Configure LoadRunner Enterprise hosts and load
Hosts
generators to work with TLS/SSL
a. Replace the certificates* on LoadRunner Enterprise hosts
and load generators. For details, see "Configure TLS/SSL
for load generators" on page 137.
b. Configure secure communication on a LoadRunner
Enterprise host. For details, see "Configure LoadRunner
Enterprise hosts to work with TLS/SSL" on page 131.

*The certificate files within the <installation root>\dat\cert folder should have the
exact names of cert.cer and verify\cacert.cer, no matter if they are the default
ones provided as part of the installation, or if they are your company certificates,
and should be the same for all LoadRunner Enterprise components—LoadRunner
Enterprise servers, hosts, and load generators.

LoadRunner Enterprise (2023-2023 R1) Page 123 of 194

Installation Guide
Installation and configuration

Configure IIS to work with TLS/SSL

This section describes the basic steps involved in setting up IIS (Microsoft Internet
Information Server) on the LoadRunner Enterprise server machine to use TLS/SSL.

IIS is a prerequisite software for the LoadRunner Enterprise servers. You can
configure the IIS LoadRunner Enterprise virtual directories (LoadRunner Enterprise
server and host) to use TLS/SSL.

For LoadRunner Enterprise host, the root certificate of the CA should appear in the
Microsoft Management Console under Certificates (Local Computer) > Trusted
Root Certification Authorities. For details, see "Distribute certificates" on
page 127.

LoadRunner Enterprise (2023-2023 R1) Page 124 of 194

Installation Guide
Installation and configuration

To configure IIS to use TLS/SSL on the LoadRunner Enterprise server machine:

LoadRunner Enterprise (2023-2023 R1) Page 125 of 194

Installation Guide
Installation and configuration

1. Perform the following before you configure IIS:

Support latest TLS Configure your servers to support the latest

versions TLS versions to ensure you are using only the
strongest cryptographic protocols.
Make sure you disable old SSL and TLS versions
(SSLv2, SSLv3, TLS 1.0, and TLS 1.1) on IIS and on your
operating system. Refer to the product Microsoft
documentation for more details.

Disable ciphers on If you are using TLS 1.2, we recommend disabling the
TLS 1.2 3DES and RC4 ciphers on Windows servers by
removing them from the HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Control\
Cryptography\Configuration\Local\SSL\00010002
registry. You can check the list of the ciphers on a
machine by running the Get-TlsCipherSuite
command in PowerShell.

Make port 443 Make sure port 443 on the LoadRunner Enterprise
available for IIS server is available for use by IIS.
IIS uses port 443 to work with TLS/SSL. Since certain
LoadRunner Enterprise components might also be
configured to use this port, configure the LoadRunner
Enterprise components to use a different port.
Note: As of LoadRunner Enterprise 2022 R1, the
Remote Management agent was moved to port 3333
for the LoadRunner Enterprise server. However, the
agent still uses port 443 for LoadRunner Enterprise
hosts and OneLGs. Use the Network and Security
Manager tool to change the port being used by the
agent to a new port. For details, see the LoadRunner
Professional Help Center.

Prevent host Prevent host header injection in a Server-Side Request

header injection Forgery (SSRF) attack.
We recommend configuring the HTTPS communication
and IIS host binding for all relevant protocols (these
configurations are not provided by OpenText by
default).
Note: By not implementing the secure configuration
and proper hardening of the IIS you may exposing the
system to increased security risks.

LoadRunner Enterprise (2023-2023 R1) Page 126 of 194

Installation Guide
Installation and configuration

2. Obtain a server certificate issued to the fully qualified domain name of your
LoadRunner Enterprise server.
3. Configure IIS to work with TLS/SSL.
Update IIS with the https binding (the same port as you used in step 1 above)
and remove the http binding.
a. Open IIS Manager, and select Server Home > Server Certificates >
Import.
b. Import the server certificate (in pfx format) that you obtained above.
c. In the Actions pane, click Bindings. and then click Add in the Site Bindings
window.
d. In the Edit Site Binding dialog box, configure the following:
o Type: https
o IP address: All Unassigned
o Port: 444
o SSL Certificate: *.<your domain name>
Refer to the product documentation for more details.

Distribute certificates
Add the root certificate to the machine truststore on the LoadRunner Enterprise
server, LoadRunner Enterprise hosts, and OneLG standalone load generators.

1. Extract the contents from the domain certificate in .pfx format to the personal
truststore of the host.
2. Add the CA certificate to the machine's truststore.
If your are using a secure connection for the internal URL of the LoadRunner
Enterprise server, you need to establish trust to the Certificate Authority (CA)
that issued your LoadRunner Enterprise server certificate.
a. Run the following command to update the certificates using MMC
(Microsoft Management Console):

LoadRunner Enterprise (2023-2023 R1) Page 127 of 194

Installation Guide
Installation and configuration

run mmc.exe

b. In the console, select Run > Add/Remove Snap-in.

c. From the list of available snap-ins, select Certificates and click Add.
d. In the Certificates snap-in dialog box, select Computer account, and then
click Next.
e. In the Console Root tree, expand Trusted Root Certification Authorities.
Right-click Certificates and select All Tasks > Import.
f. In the Certificate Import Wizard, click Next.
g. Click Browse, and navigate to the unzipped certs folder. Select
PCSecureEnvTestingCA certificate, and click Open.
h. Click Next in the certificate stores page of the wizard, and then click Finish.
Wait for the import success message.
3. Repeat on all LoadRunner Enterprise machines.
4. (For LoadRunner Enterprise hosts used as Controllers only) Import the domain
certificate in .pfx format to the personal truststore of the host.

Configure the LoadRunner Enterprise server to work with

TLS/SSL
This section explains how to configure secure communication on a LoadRunner
Enterprise server for incoming requests from the LoadRunner Enterprise server
and hosts.

To configure the LoadRunner Enterprise server to use TLS/SSL, you need to

perform the following:

1. Update the web.config file located in the <LRE server installation

folder>\PCS directory.
a. Create a backup copy of the web.config file and save it in a different folder.
b. To update the web.config file, you can replace it with the predefined
web.config-for_ssl file. See step 1d below.

LoadRunner Enterprise (2023-2023 R1) Page 128 of 194

Installation Guide
Installation and configuration

If you have manual changes you want to preserve in the web.config file,
you can manually modify the file. See step 1c below.
c. Edit the web.config file. Under the <system.servicemodel><services>
tag, there are eight areas where the following comment appears:
Uncomment to enable SSL. Uncomment the XML lines which appear
thereafter, and comment the non-TLS/SSL settings as shown in the
example below.

Example before:

<endpoint binding="basicHttpBinding" contract="HP.PC.PCS.ILabService"><identity>

<dns value="localhost"/></identity></endpoint>

<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>

<!- Uncomment to enable TLS/SSL ->

<!-- endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_

TransportSecurity" contract="HP.PC.PCS.ILabService"><identity>

<dns value="localhost"/></identity></endpoint -->

Example after:

<!--<endpoint binding="basicHttpBinding"
contract="HP.PC.PCS.ILabService"><identity>

<dns value="localhost"/></identity></endpoint>

<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/> -

->

<!-- Uncomment to enable TLS/SSL -->

<endpoint binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_

TransportSecurity" contract="HP.PC.PCS.ILabService"><identity>

<dns value="localhost"/></identity></endpoint>

Under the <system.servicemodel><behaviors> tag, there are seven areas

where you need to change the httpGetEnabled parameter to false, and the
httpsGetEnabled parameter to true.

LoadRunner Enterprise (2023-2023 R1) Page 129 of 194

Installation Guide
Installation and configuration

Example before:

<serviceMetadata httpGetEnabled="true" httpsGetEnabled="false" />

Example after:

<serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" />

d. To replace web.config with the predefined web.config-for_ssl file, copy

web.config-for_ssl from the <LRE server installation
folder>\conf\httpsConfigFiles directory and place it under the <LRE
server installation folder>\PCS directory.
Rename web.config-for_ssl to web.config.
2. Open the PCS.config file, located in the <LRE server installation folder>\dat
path, and update the Internal URL attribute with https to connect to
LoadRunner Backend Service through a secure port:

internalUrl="https://<lre-dns-name>:444"

3. Update the LoadRunner Enterprise server to ensure that communication with

the host is secure (only required when you plan to configure hosts to work with
TLS/SSL)
If the LoadRunner Enterprise host is secured, edit the PCS.config file located in
the <LoadRunner Enterprise server install path>\dat path, by changing the
value of the ItopIsSecured parameter to true.

Example before:

<PCSSettings ltopPortNumber="8731" ltopIsSecured="false" StartRunMaxRetry="3"

DataProcessorPendingTimeoutMinutes="2880"/>

Example after:

<PCSSettings ltopPortNumber="8731" ltopIsSecured="true" StartRunMaxRetry="3"

DataProcessorPendingTimeoutMinutes="2880"/>

LoadRunner Enterprise (2023-2023 R1) Page 130 of 194

Installation Guide
Installation and configuration

4. Restart the LoadRunner Backend Service.

5. Restart IIS.
6. In LoadRunner Enterprise Administration, update the LoadRunner Enterprise
server internal and external URLs with the https URL.

Configure LoadRunner Enterprise hosts to work with

TLS/SSL
This section explains how to configure secure communication on a LoadRunner
Enterprise host for incoming requests from LoadRunner Enterprise servers.

Configure the LoadRunner Enterprise hosts

1. The default port used by a LoadRunner Enterprise host service is 8731. Refer to
the Microsoft documentation for details on configuring a port with an SSL
certificate.

Note: Server certificates for all LoadRunner Enterprise host machines

must be installed and trusted on all servers that are part of the
environment. This requires:
l Binding port 8731 on each host to its respective certificate.
l Ensuring the LoadRunner Enterprise server certificate within the <LRE
server installation folder >\dat\cert folder contains the private key
and the intermediate CA certificates (in the order that they appear in
the chain) on all systems.

Below are examples of the steps described in the above link.

a. Check that the port is not configured:

Example:

C:\Users\Demo>netsh http show sslcert ipport=0.0.0.0:8731

SSL Certificate bindings:

-------------------------

The system cannot find the file specified.

b. Run the netsh command:

LoadRunner Enterprise (2023-2023 R1) Page 131 of 194

Installation Guide
Installation and configuration

You can use the command below (where certhash is the certificate
thumbprint and the appid parameter is a GUID that can be used to identify
the owning application. You can use any valid GUID. There are many tools
that can generate a GUID).

Example:

C:\Users\Demo>netsh http add sslcert ipport=0.0.0.0:8731

certhash=1b337c1f17e0f96b09f803fs0c2c7b3621baf2bb appid={114F6E0C-EB01-4EE9-9CEF-
3D1A500FD63F}

SSL Certificate successfully added

c. Check that the port is now configured:

Example:

C:\Users\Demo>netsh http show sslcert ipport=0.0.0.0:8731

SSL Certificate bindings:

-------------------------

IP:port : 0.0.0.0:8731

Certificate Hash : 1b337c1f17e0f94b09f803ff0c2c7b7621baf2bb

Application ID : {114f6e0c-eb01-4ee9-9cef-3d1a500fd63f}

Certificate Store Name : (null)

Verify Client Certificate Revocation : Enabled

Verify Revocation Using Cached Client Certificate Only : Disabled

Usage Check : Enabled

Revocation Freshness Time : 0

URL Retrieval Timeout : 0

Ctl Identifier : (null)

Ctl Store Name : (null)

DS Mapper Usage : Disabled

Negotiate Client Certificate : Disabled

2. Perform the following steps to update the LTOPSvc.exe.config file:

a. Create a backup copy of the LTOPSvc.exe.config file, and save it in a
different folder. The file is located under the <install path>\bin\LTOPbin

LoadRunner Enterprise (2023-2023 R1) Page 132 of 194

Installation Guide
Installation and configuration

directory.
b. To update the LtopSvc.exe.config file, you can replace it with the
predefined LTOPSvc.exe.config-for_ssl file. See step 2d on page 136.
If you have manual changes you want to preserve in the
LTOPSvc.exe.config file, you can manually modify the file. See step 2c
below.
c. Under the <system.servicemodel><bindings><basicHttpBinding> tag,
there are two areas where the following comment appears: Uncomment to
enable SSL. Uncomment the XML lines which appear thereafter.

Example before:

<binding name="BasicHttpBinding_ILoadTestingService" closeTimeout="00:10:00"

openTimeout="00:01:00" receiveTimeout="00:20:00"
sendTimeout="00:10:00"

allowCookies="false" bypassProxyOnLocal="false"
hostNameComparisonMode="StrongWildcard"

maxBufferSize="2147483647" maxBufferPoolSize="2147483647"
maxReceivedMessageSize="2147483647"

messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"

useDefaultWebProxy="true">

<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"

maxArrayLength="2147483647"

maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />

<!-- Uncomment to enable TLS/SSL -->

<!--<security mode="Transport">

<transport clientCredentialType="None"/>

</security>-->

</binding>

Example after:

<binding name="BasicHttpBinding_ILoadTestingService" closeTimeout="00:10:00"

LoadRunner Enterprise (2023-2023 R1) Page 133 of 194

Installation Guide
Installation and configuration

openTimeout="00:01:00" receiveTimeout="00:20:00"
sendTimeout="00:10:00"

allowCookies="false" bypassProxyOnLocal="false"
hostNameComparisonMode="StrongWildcard"

maxBufferSize="2147483647" maxBufferPoolSize="2147483647"
maxReceivedMessageSize="2147483647"

messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"

useDefaultWebProxy="true">

<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"

maxArrayLength="2147483647"

maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />

<!-- Uncomment to enable TLS/SSL -->

<security mode="Transport">

<transport clientCredentialType="None"/>

</security>

</binding>

Under the <system.servicemodel><services> tag, switch between the

non-secured and secured endpoints and base addresses.

Example before:

<endpoint contract="HP.PC.LTOP.Services.ILoadTestingService"
address="LoadTestingService" name="basicHttp" binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_ILoadTestingService"/>

<!-- Use the first endpoint for regular communication and the second
endpoint for TLS/SSL -->

<endpoint contract="IMetadataExchange" binding="mexHttpBinding"

name="mex" />

<!--<endpoint contract="IMetadataExchange" binding="mexHttpsBinding"

name="mex" />-->

<host>

<baseAddresses>

<!-- Use the first address for regular communication and the second
address for TLS/SSL -->

<add baseAddress="http://localhost:8731/LTOP/LoadTestingService"/>

LoadRunner Enterprise (2023-2023 R1) Page 134 of 194

Installation Guide
Installation and configuration

<!--<add
baseAddress="https://localhost:8731/LTOP/LoadTestingService"/>-->

</baseAddresses>

</host>

</service>

Example after:

<service name="HP.PC.LTOP.Services.LoadTestingService"
behaviorConfiguration="CommonBasicHTTPBehavior">

<endpoint contract="HP.PC.LTOP.Services.ILoadTestingService"
address="LoadTestingService" name="basicHttp" binding="basicHttpBinding"
bindingConfiguration="BasicHttpBinding_ILoadTestingService"/>

<!-- Use the first endpoint for regular communication and the second
endpoint for TLS/SSL -->

<!-- <endpoint contract="IMetadataExchange" binding="mexHttpBinding"

name="mex" />-->

<endpoint contract="IMetadataExchange" binding="mexHttpsBinding"

name="mex" />

<host>

<baseAddresses>

<!-- Use the first address for regular communication and the second
address for TLS/SSL -->

<!--<add
baseAddress="http://localhost:8731/LTOP/LoadTestingService"/>-->

<add baseAddress="https://localhost:8731/LTOP/LoadTestingService"/>

</baseAddresses>

</host>

</service>

Under the
<system.servicemodel><behaviors><serviceBehaviors><behaviornam
e="CommonBasicHTTPBehavior"> tag, change the httpGetEnabled
parameter to false, and the httpsGetEnabled parameter to true.

LoadRunner Enterprise (2023-2023 R1) Page 135 of 194

Installation Guide
Installation and configuration

Example before:

<serviceMetadata httpGetEnabled="true" httpsGetEnabled="false" />

Example after:

<serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" />

d. To replace LTOPSvc.exe.config with the predefined LTOPSvc.exe.config-

for_ssl file, copy LTOPSvc.exe.config-for_ssl from the <install
path>\conf\httpsconfigfiles directory and place it under the <install
path>\bin\LTOPbin directory.
Rename LTOPSvc.exe.config-for_ssl to LTOPSvc.exe.config.
3. Restart the Windows service "LoadRunner Load Testing Service".

Note: If the "LoadRunner Load Testing Service" does not start after
configuring the LoadRunner Enterprise host to listen on HTTPS, see
Software Self-solve knowledge base article KM03101264.

4. Run the following command:

<install path>\bin\lr_agent_settings.exe -check_client_cert 1 -restart_agent

5. After you finish configuring the LoadRunner Enterprise host to support

TLS/SSL, reconfigure any hosts that are part of the environment.

Configure LoadRunner components to work with

TLS/SSL
You must update CA and TLS certificates if they were created with LoadRunner
tools (Controller, MI Listener, Load Generators, Monitors Over Firewall) or they do
not contain the required extension information for the CA certificate being used.

You also need to update CA and TLS certificates for the LoadRunner Enterprise
server which communicates with load generators for LAB-related operations.

LoadRunner Enterprise (2023-2023 R1) Page 136 of 194

Installation Guide
Installation and configuration

Make sure the certificate files within the <LRE server installation folder
>\dat\cert folder have the exact names of cert.cer and verify\cacert.cer, no
matter if they are the default ones provided as part of the installation, or if they are
your company certificates.

For details on how to obtain the required certificates, see Secure Communication
with TLS (SSL) in the LoadRunner Professional Help Center.

Note: After configuring secure communication with TLS, you need to restart
the services. To do so, you can either:
l Run LoadRunner Agent Service and LoadRunner Remote Management
Agent Service.
l Alternatively, run the following command:
lr_agent_settings.exe -restart_agent

Configure TLS/SSL for load generators

This section describes how to configure TLS (SSL) communication to the load
generators. It describes how to create and install a Certification Authority and a
Client Certificate for working with TLS to secure communication to your load
generators. It also describes how to enable TLS from LoadRunner Enterprise
Administration.

Create and copy digital certificates

1. Create a Certification Authority (CA)

Note: This step describes how to create a CA using the gen_ca_cert.exe

utility. If you are working on a Linux platform, use the gen_ca_cert utility
instead.

On one of your LoadRunner Enterprise hosts, run the gen_ca_cert command

from the <LRE host installation folder>\bin with at least one of the following
options:

LoadRunner Enterprise (2023-2023 R1) Page 137 of 194

Installation Guide
Installation and configuration

l -country_name
l -organization name
l -common_name
This process creates two files in the folder from which the utility was run: the
CA Certificate (cacert.cer), and the CA Private Key (capvk.cer).

Note: By default, the CA is valid for three years from when it is

generated. To change the validation dates, use the -nb_time
(beginning of validity) and/or -na_time (end of validity) options.

The following example creates two files: ca_igloo_cert.cer and ca_igloo_

pk.cer in the current folder:

gen_ca_cert - country_name "North Pole" -organization_name "Igloo Makers" -common_

name "ICL" -CA_cert_file_name "ca_igloo_cert.cer" - CA_pk_file_name "ca_igloo_
pk.cer" -nb_time 10/10/2013 -na_time 11/11/2013

2. Install Certification Authority (CA)

You need to install the CA on the hosts that you want to enable TLS
communication including Controllers, LoadRunner Enterprise servers, Load
Generators, and MI Listeners.
Run the gen_ca_cert utility from the <Installation root folder>\bin
folder with one of the following parameters:
l -install <name/path of the CA certificate file>. Replaces any previous CA
list and creates a new one that includes this CA only.
l -install_add <name/path of the CA certificate file>. Adds the new CA to
the existing CA list.

Note:
l The -install and -install_add options install the certificate file only.
Keep the private key file in a safe place and use it only for issuing
certificates.

LoadRunner Enterprise (2023-2023 R1) Page 138 of 194

Installation Guide
Installation and configuration

l If your load generator is over firewall, install the CA on the MI Listener

machine.

3. Create a Client Certificate

Note: This step describes how to create a client certificate using the
gen_cert.exe utility. If you are working on a Linux platform, use the gen_
cert utility instead.

On one of your LoadRunner Enterprise hosts, run the gen_cert command from
the <LoadRunner Enterprise host root folder>\bin folder with at least one of
the following options:
o -country_name
o -organization_name
o -organization_unit_name
o -eMail
o -common_name
It is important to note the following:
l The CA Certificate and the CA Private Key files are necessary for the
creation of the certificate. By default, it is assumed that they are in the
current folder, and are named cacert.cer and capvk.cer respectively. In any
other case, use the -CA_cert_file_name and -CA_pk_file_name options to
give the correct locations.
l The certificate file is created in the folder from which the utility was run. By
default, the file name is cert.cer.
4. Install a Client Certificate
You need to install the client certificate on the hosts that you want to enable
TLS including LoadRunner Enterprise hosts (used as Controllers), LoadRunner
Enterprise servers, Load Generators, and MI Listeners.
Run the gen_cert utility from the <LoadRunner Enterprise host root
folder>\bin folder with the following parameter:

LoadRunner Enterprise (2023-2023 R1) Page 139 of 194

Installation Guide
Installation and configuration

-install <name/path of the client certificate file>

Note:
l Steps 3 and 4 describe how to install the same client certificate.
Alternatively, you can create a new client certificate on each machine.
l Make sure the certificate files within the <installation root>\dat\cert
folder have the exact names of cert.cer and verify\cacert.cer, no
matter if they are the default ones provided as part of the installation,
or if they are your company certificates.

5. Restart the agent configuration

On the load generator machines, open LoadRunner Enterprise Agent
Configuration and click OK to restart the agent configuration. On the MI
Listener machines, open Agent Configuration and click OK to restart the agent
configuration.

Enable TLS communication for load generators in

LoadRunner Enterprise Administration
1. Log onto LoadRunner Enterprise Administration. For details, see "Log on to
LoadRunner Enterprise Administration" on page 85.
2. On the LoadRunner Enterprise Administration sidebar, under Maintenance
select Hosts.
3. Under the Host Name column, click the name of an existing host or load
generator over a firewall host.
Alternatively, click New Testing Host to create a new host.

4. In the Host Details or New Host page, select Enable SSL.

Working with the LoadRunner Enterprise agent

The LoadRunner Enterprise agent runs on the load generators and enables
communication between the Controller, Load Generators, and MI Listeners (in over
firewall configurations). The agent receives instructions from the Controller to

LoadRunner Enterprise (2023-2023 R1) Page 140 of 194

Installation Guide
Installation and configuration

initialize, run, pause, and stop Vusers. At the same time, the agent also relays data
on the status of the Vusers back to the Controller.

Run the LoadRunner Enterprise agent as a process

In some cases, running GUI Vusers on remote machines, or terminal sessions, the
LoadRunner Enterprise Agent must run as a process.

To change the LoadRunner Enterprise Agent from a service to a

process:
On the host machine, select LoadRunner > Tools > Agent Runtime Settings
Configuration from the Start menu, and select Manual log in to this machine.

Run the LoadRunner Enterprise agent as a service

In most cases, the LoadRunner Enterprise Agent runs as a service.

To change the LoadRunner Enterprise Agent from a process to a

service:
1. On the host machine, select LoadRunner > Tools > Agent Runtime Settings
Configuration from the Start menu.
2. Select Allow virtual users to run on this machine without user login, and
enter a valid user name and password.

Configure the agent on load generator machines

When working with protocols that use network files or Web protocol Vusers that
access the Internet through a proxy server, the Load Generator agent must have
network privileges. Note that the default user created by LoadRunner Enterprise,
System, does not have network privileges.

By default, the agent runs as a service on the Load Generator machines. You can
either run the agent as a process or you can continue running the agent as a
service. To continue running it as a service, configure it to run the session using the
local system account or another user account with network access privileges.

LoadRunner Enterprise (2023-2023 R1) Page 141 of 194

Installation Guide
Installation and configuration

Map network drives when running the agent as service

For all Windows platforms, when the user is logged off, the service cannot resolve
the mapping of network drives. In cases when the service cannot work with
mapped network drives, use the full path to the directory, for example,
<\\<machine-name>\<directory>\>.

LoadRunner Remote Management Agent

The LoadRunner Remote Management Agent Service enables you to manage
remote machines from LoadRunner Enterprise Administration.

The agent is hosted on a Windows-based operating system, and is run as a service

under a Local System account which has extensive privileges.

Note: We recommend changing the Local System account to run the service with
the minimal permissions required for its operation (see below for details).

Change user under which the services are running

To run the agent service with a less-privileged user, change the user under which
the service is running. To do so, configure a limited user account with restricted
privileges (such as a Windows service account), that allows the user to perform
only the necessary actions required by the system.

When creating a limited user account for running the agent service, we
recommend using a Standalone Load Generator. Otherwise you have to
reconfigure the service to run under this user account each time the LoadRunner
Enterprise server or host are reconfigured (since the process recreates the
LoadRunner Remote Management Agent Service with the default Local System
account privileges).

Note: Remote rebooting of hosts and running remote installations is not

supported when the Remote Management Agent service is running under a
non-admin user account.

LoadRunner Enterprise (2023-2023 R1) Page 142 of 194

Installation Guide
Installation and configuration

Recommended configuration for Linux

load generators
You can increase the number of file descriptors, process entries, and amount of
swap space by configuring the kernel.

For details and recommendations on improving Linux Load Generator

performance, see the LoadRunner Professional Installation Guide available from
the LoadRunner Professional Help Center.

Recommended change to the TEMP folder used

by the load generator
This section describes how to manually change the default TEMP folder used by
the load generator to store data during a test run. The TEMP folder is predefined,
and is based on the load generator installation folder.

Why change the location of the folder?

l The TEMP folder also contains the script. Depending on the machine and the
script, this path can get very long, and exceed the character limitation set by
Windows.
l You want to use a different folder or drive instead of the default one.

Note: You cannot change the TEMP folder location if your load generator is
configured over a firewall (whether the firewall is enabled or disabled).

Before changing the TEMP folder

Note the following before changing the TEMP folder used by the load generator:

l The change is made on the LoadRunner Enterprise Host that is serving as a

Controller. Therefore, such change applies only to the load generators using this
Controller.
l If you are using the same load generators with a new Controller, you need to
reapply this change on the new Controller.

LoadRunner Enterprise (2023-2023 R1) Page 143 of 194

Installation Guide
Installation and configuration

To change the TEMP folder:

1. Log onto the LoadRunner Enterprise Host machine.
2. Verify that the Wlrun.exe process is down.
3. Open <LG installation folder>\config\Wlrun7.ini in a text editor.
4. Add the line "UserRemoteTmpDir=<Custom temp location>" under the '[Host]'
section
5. Save the change.

Enable downloading standalone applications

This section explains the steps necessary to enable you to download standalone
applications from the Download Applications window.

To enable downloading standalone applications:

1. Navigate to the <LRE server installation directory>\Additional Components
folder. This directory contains the applications' execution (.exe) files.

Note: The necessary .exe files for downloading VuGen, Analysis,

Standalone Load Generator, Monitor over Firewall, and MI Listener, are
located in the Applications directory, which is contained within the
Additional Components directory.

2. On the LoadRunner Enterprise server, navigate to the Downloads directory,

which is located in <LRE server installation directory>\PCWEB\Downloads.
3. To enable downloading an application, copy the relevant execution file (.exe)
from the <LRE server installation directory>\Additional Components folder
to the Downloads directory on the LoadRunner Enterprise server.

Note: You may need to refresh the Download Applications window for
the changes to take effect.

LoadRunner Enterprise (2023-2023 R1) Page 144 of 194

Installation Guide
Installation and configuration

Customize the Download Applications window

You can edit and customize the appearance of the Download Applications window.
To customize the window, edit the downloads.xml file located in the Downloads
directory on the LoadRunner Enterprise server.

The following tags in the downloads file control the following features on the
window. Edit the tags as desired to change the appearance of the window.

l App Name. The name of the application.

l Image. Whether the application's icon appears to the left or to the right of the
name.
l File Name. If you changed the name of the application's execution file, you must
update this section so that it matches the new name of the execution file.
l Description. The application's description.

To customize the Download Applications window:

1. (Recommended) Make a backup copy of the downloads.xml file before
customizing the appearance of the Download Applications window.
2. Open the downloads.xml file, and update the tags as required.
For example:

<app name="MyNewApp" image="assets/images/download-

applications/my_Icon.svg">
<file name="my_file_name.exe">
<description>My file description...</description>
</file>
</app>

Note: The Download Applications window supports a multilingual user

interface for the default applications only. Any changes to the default
application tags, and new applications that are added to the downloads.xml
file, are not supported by MLU.

LoadRunner Enterprise (2023-2023 R1) Page 145 of 194

Installation Guide
Installation and configuration

Enable MS-SQL Windows authentication

This section describes how to configure an MS-SQL database with Windows
authentication.

Note: The procedure below requires you to make changes to the MS-SQL
database. We recommend that you make these changes using the SQL
Server Management Studio tool.

To enable Windows authentication:

1. Verify that the LoadRunner Enterprise server and database server all belong to
the same domain, and that there is a domain user with administrator privileges
common to all the machines.
2. Change users to domain users using the System Identity Utility. For details, see
Change the LoadRunner Enterprise system user in the LoadRunner Enterprise
Help Center.
3. Download the SQL Server Management Studio tool from the Microsoft
Download Center.
4. In SQL Server Management Studio, perform the following actions:
a. In the Object Explorer pane, expand the Security folder.
b. Right-click Logins and select New Login.
c. Enter the domain user in the Login name box, and make sure that Windows
Authentication is selected.

Note: Verify that the domain user is assigned the same Server Roles
as the database administrative user (td_db_admin).

5. Make sure that the relevant project is created in LoadRunner Enterprise

Administration with the MS-SQL (Win Auth) database type. For details, see
the LoadRunner Enterprise Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 146 of 194

Working with firewalls

LoadRunner Enterprise (2023-2023 R1) Page 147 of 194

Using firewalls
You can set up your LoadRunner Enterprise system to run Vusers and monitor
servers over a firewall.

This chapter includes:

• About using firewalls in LoadRunner Enterprise 149

• Example of over firewall deployment 151
• Set up the system to use firewalls: basic steps 152
• Install over firewall components 154
• Initial configuration of the over firewall system 154
• Specify MI Listeners 159

LoadRunner Enterprise (2023-2023 R1) Page 148 of 194

Installation Guide
Working with firewalls

About using firewalls in LoadRunner Enterprise

Working with a firewall means that you can prevent unauthorized access to or from
a private network, on specific port numbers.

For example, you can specify that no access is allowed to any port from the
outside world, with the exception of the mail port (25), or you can specify that no
outside connection is allowed from any ports to the outside except from the mail
port and WEB port (80). The port settings are configured by the system
administrator.

In a regular performance test (not over a firewall), the Controller has direct access
to the LoadRunner Enterprise agents running on remote machines. This enables
the Controller to connect directly to those machines.

When running Vusers or monitoring applications over a firewall, this direct

connection is blocked by the firewall. The connection cannot be established by the
Controller, because it does not have permissions to open the firewall.

LoadRunner Enterprise solves this problem by using secure TCP over proxy. This
communication is secure by using TLS (formerly SSL). For details on

LoadRunner Enterprise (2023-2023 R1) Page 149 of 194

Installation Guide
Working with firewalls

communication over proxy, see "Set up your deployment (TCP or TCP over proxy)"
on page 155.

LoadRunner Enterprise agent is already installed on load generators (running

Vusers over a firewall), and on Monitor Over Firewall machines (that monitor the
servers that are located over a firewall). The agent communicates with the
MI Listener machine on port 443.

The MI Listener is a component that serves as router between the Controller and
the LoadRunner Enterprise agent.

When the LoadRunner Enterprise agent connects to the MI Listener, the

MI Listener keeps a listing of the connection to the agent using a symbolic name
that the agent passed to it.

When the Controller connects to the MI Listener, it communicates to the MI

Listener on port 50500.

The Controller uses a symbolic name for the agent, and provides the MI Listener
machine's name. If there has been a connection from the agent with the same
symbolic name to this MI Listener, the connection is made between the Controller
and the agent. After you have a connection with the agent, you can run Vusers

LoadRunner Enterprise (2023-2023 R1) Page 150 of 194

Installation Guide
Working with firewalls

over firewall or monitor AUT machines behind the firewall.

Example of over firewall deployment

The following diagram is a basic example of a LoadRunner Enterprise deployment
over a firewall.

As explained in the previous section, the LoadRunner Enterprise agent is installed

on both the load generator machine and the Monitor Over Firewall machine. During
installation, the LoadRunner Enterprise agent is added as a Windows service.

The MI Listener serves as a router between:

l The agent on the load generator machine and the Controller, enabling the
Controller to run Vusers over a firewall.

LoadRunner Enterprise (2023-2023 R1) Page 151 of 194

Installation Guide
Working with firewalls

l The agent on the Monitor Over Firewall machine and the Controller, enabling the
Controller to monitor the servers that are located over a firewall.

Set up the system to use firewalls: basic steps

Setting up the system to use firewalls involves the following stages of
configuration:
Stage Description

Installation Install the necessary components and perform initial

and initial configuration settings. For details, see "Install over firewall
configuration components" on page 154, and "Initial configuration of the over
firewall system" on page 154.

Enabling When there is a firewall between the Controller and load

running generator host machines, set up the system to run Vusers over
Vusers over a the firewall. For details, see "Run Vusers over a firewall" on
firewall page 161.

Enabling Set up your system to monitor the application under test (AUT)
monitoring when there is a firewall between the Controller and the AUT.
over a firewall For details, see "Monitor over a firewall" on page 166.

Checking After installing and configuring all the necessary components,

Connectivity check that you are able to establish a connection between the
LoadRunner Enterprise agent, the MI Listener, and the
Controller machine. For details, see "Check connectivity" on
page 181.

The following flow chart provides a general outline of the steps that you need to
perform to set up your system to work with firewalls.

LoadRunner Enterprise (2023-2023 R1) Page 152 of 194

Installation Guide
Working with firewalls

LoadRunner Enterprise (2023-2023 R1) Page 153 of 194

Installation Guide
Working with firewalls

Install over firewall components

To enable over firewall communication, ensure that you have installed the
following LoadRunner Enterprise components:

Component Description

MI Listener Serves as a router between the Controller and the LoadRunner

Enterprise agent. You install the MI Listener component on a
dedicated machine. For installation instructions, see "Install
standalone components (Windows)" on page 99.
For instructions on configuring the MI Listener machine, see
"Configure the MI Listener" on page 157.

Monitor Over Used to monitor the servers that are located over a firewall. You
Firewall install the Monitors over Firewall component on a dedicated
component machine. For installation instructions, see "Install standalone
components (Windows)" on page 99.
For information about configuring the Monitor Over Firewall
machine, see "Monitor over a firewall" on page 166.

Initial configuration of the over firewall system

After you have installed the necessary components, you are ready to configure
your over firewall system.

To perform initial configuration of your over firewall system:

1. Configure the system according to TCP or TCP over proxy.
See "Set up your deployment (TCP or TCP over proxy)" on the next page.
2. Modify the firewall settings to enable communication between the machines on
either side of the firewall.
See "Configure the firewall to allow agent access" on page 156.
3. Configure the MI Listener.
See "Configure the MI Listener" on page 157.

LoadRunner Enterprise (2023-2023 R1) Page 154 of 194

Installation Guide
Working with firewalls

Set up your deployment (TCP or TCP over proxy)

To run Vusers or monitor servers over the firewall, configure your system
according to one of the following configurations. Note that these configurations
contain a firewall on each LAN. There may also be configurations where there is a
firewall for the Over Firewall LAN only.

l TCP configuration
The TCP configuration requires every LoadRunner Enterprise agent machine
behind the customer's firewall to be allowed to open a port in the firewall for
outgoing communication.

LoadRunner Enterprise (2023-2023 R1) Page 155 of 194

Installation Guide
Working with firewalls

l TCP over proxy configuration

In the TCP over proxy configuration, only one machine (the proxy server) is
allowed to open a port in the firewall. Therefore it is necessary to tunnel all
outgoing communications through the proxy server. The proxy server must
support HTTP tunneling using the CONNECT method.

Configure the firewall to allow agent access

You modify your firewall settings to enable communication between the machines
inside the firewall and machines outside the firewall.

TCP configuration
The LoadRunner Enterprise agent attempts to establish a connection with the MI
Listener using port 443, at intervals specified in the Connection Timeout field in
the Agent Configuration dialog box. To enable this connection, allow an outgoing
connection on the firewall for port 443. The agent initiate the connection and the
MI Listener communicates with the Load Generator through the connection.

TCP over proxy configuration

The LoadRunner Enterprise agent attempts to establish a connection with the MI
Listener, using the proxy port specified in the Proxy Port field, and at intervals
specified in the Connection Timeout field in the Agent Configuration dialog box.

LoadRunner Enterprise (2023-2023 R1) Page 156 of 194

Installation Guide
Working with firewalls

When the connection to the proxy server is established, the proxy server connects
to the MI Listener. To enable this connection, allow an outgoing connection on the
firewall for port 443. The proxy server can then connect to the MI Listener, and the
MI Listener can connect back to the agent through the proxy server. From this
point on, the agent listens to commands from the MI Listener.

Local System account configuration

If you intend to start the LoadRunner Agent Service from the Local System
account, you need to grant it permissions. If you do not provide permissions, the
monitor graph does not display any data.

To grant it permissions, add a local user on the AUT machine with the same name
and password as the local user on Agent machine. Add the AUT local user to the
Performance Monitor Users group and restart the Agent process.

Configure the MI Listener

To enable running Vusers or monitoring over a firewall, you need to install the MI
Listener on one or more machines in the same LAN as the Controller outside the
firewall. For installation instructions, see, "Install standalone components
(Windows)" on page 99.

To configure the MI Listener:

1. Prerequisites and security recommendations.
l You must configure the MI Listener to work with TLS/SSL. For details, see
"Configure LoadRunner components to work with TLS/SSL" on page 136.
l We recommend replacing the LoadRunner Agent Service local system user
with a different user account that has lower access levels. For example, you
can use the built-in LRE_SERVICE user or create a new LoadRunner user in
the Administrators group.
l Since the PEM file stored on the MI Listener is not encrypted, we recommend
limiting the file permissions of the folder in which the file is located to the
same user running the LoadRunner Agent Service from above. To do so:

LoadRunner Enterprise (2023-2023 R1) Page 157 of 194

Installation Guide
Working with firewalls

i. Navigate to the <LoadRunner installation directory>\dat directory.

ii. Right-click the cert folder and select Properties. In the Security tab,
add a LoadRunner user with full control permissions.
iii. Remove any other users including SYSTEM, Administrator, and all
groups such as Authenticate Users, Administrators, and Users so only
the LoadRunner user is displayed.

2. On the MI Listener server, open port 443 for the incoming traffic.
3. Select Start > Administrative Tools > Services, and stop LoadRunner Agent
Service.
4. Select Start > All Programs > Micro Focus > LoadRunner > Advanced
Settings > MI Listener Configuration, or run

<LoadRunner root folder>\launch_service\bin\MILsnConfig.exe

5. Set each option as described in the following table:

LoadRunner Enterprise (2023-2023 R1) Page 158 of 194

Installation Guide
Working with firewalls

Option Description

Check Client Select True to request that the client send a TLS/SSL
Certificates certificate when connecting, and to authenticate the
certificate.
Default value: False

Private Key The password that may be required during the TLS/SSL
Password certificate authentication process.
Default value: none

Click OK to save your changes or Use Defaults to use the default values.
6. Select Start > Administrative Tools > Services. To restart the LoadRunner
Agent Service, select Start > All Programs > Micro Focus > LoadRunner >
Advanced Settings > Agent Service.
7. Make sure that no Web Servers are running on the MI Listener or Monitor over
Firewall machine. These servers use port 443 and do not allow the access
required by the listening and monitoring processes.

Specify MI Listeners
In LoadRunner Enterprise Administration, you specify one or more MI Listeners to
enable running Vusers or monitoring data over a firewall.

To add an MI Listener:
1. On the LoadRunner Enterprise Administration sidebar, under Maintenance >
Hosts, select MI Listeners.
2. In the MI Listeners tab, click the Add New MI Listener button. The New
MI Listener page opens.

LoadRunner Enterprise (2023-2023 R1) Page 159 of 194

Installation Guide
Working with firewalls

3. Enter the following details:

Field Description

MI Listener The host name of the MI Listener.

Name Note: If you have two different IP addresses for the same
MI Listener—one for internal communication with the
Controller and a second for public communication with a
Load Generator located over a firewall—enter the internal IP
address here. Enter the public IP address in the Public IP
field (see below).

Description A description of the MI Listener.

Public IP The public IP address of the MI Listener.

Note:
If you have two different IP addresses for the same MI
Listener, one for public communication with a Load
Generator located over a firewall and a second for internal
communication with the Controller, enter the public IP
address here. Enter the internalIP address in the MI Listener
Name field (see above).

Purpose The role designated to the MI Listener:

l Monitoring over a firewall

l Running Vusers over a firewall

4. Click Save. The MI Listener is added to the grid.

LoadRunner Enterprise (2023-2023 R1) Page 160 of 194

Run Vusers over a firewall
You can set up LoadRunner Enterprise to run Vusers over a firewall.

This chapter includes:

• Run Vusers over a firewall: basic steps 162

• Configure hosts to run Vusers over a firewall 163

LoadRunner Enterprise (2023-2023 R1) Page 161 of 194

Installation Guide
Working with firewalls

Run Vusers over a firewall: basic steps

Note: Before you configure your system to run Vusers over the firewall,
ensure that you have completed the configuration steps described in "Initial
configuration of the over firewall system" on page 154.

To run Vusers over a firewall:

1. In LoadRunner Enterprise Administration, specify the details of the MI Listener
used to run Vusers over the firewall. For details, see "Specify MI Listeners" on
page 159.
2. Configure the LoadRunner Enterprise agent on each Load Generator machine
that runs over a firewall to communicate with the MI Listener.
For information on how to configure the LoadRunner Enterprise agent, see
"Configure the LoadRunner Enterprise agent" on page 175.

LoadRunner Enterprise (2023-2023 R1) Page 162 of 194

Installation Guide
Working with firewalls

Note: After you configure the LoadRunner Enterprise agent on the Load
Generator machine, you can edit the configuration settings from
LoadRunner Enterprise Administration. For details, see Manage hosts in
the LoadRunner Enterprise Help Center.

3. In LoadRunner Enterprise Administration, configure the relevant Load

Generator hosts to run over a firewall. For details, see "Configure hosts to run
Vusers over a firewall" below.

Configure hosts to run Vusers over a firewall

To use a LoadRunner Enterprise host to run Vusers over a firewall, you need to
configure the relevant hosts as Load Generators in LoadRunner Enterprise
Administration.

Part of the process of configuring a LoadRunner Enterprise host involves selecting

a location for your host. For example, locations can be defined according to
physical areas. The location also determines whether the host is located over a
firewall.

Before you configure the host, you need to ensure that you have added a location
over a firewall. When you are configuring a host to operate over a firewall, you
select a location that is located over a firewall.

This section describes the basic steps of how to add a host as a Load Generator
for running Vusers over a firewall. For detailed information about adding hosts in
LoadRunner Enterprise, refer to the LoadRunner Enterprise Administration Guide.

To configure a host to run Vusers over a firewall:

1. Add the location that is over a firewall.
a. In LoadRunner Enterprise Administration, select Maintenance > Hosts and
click the Locations tab.

b. Click Add New Location . The New Location dialog box opens.

c. Enter the following details:

LoadRunner Enterprise (2023-2023 R1) Page 163 of 194

Installation Guide
Working with firewalls

Location The name of the host location. The name should have a
Name logical connection to the host location.

Description A description of the host location.

Over Firewall Indicates whether the host location is over a firewall.

2. Add the over firewall host.

a. On the LoadRunner Enterprise Administration sidebar, select Maintenance >
Hosts.

b. Select the Hosts tab, and then click Create New Host .

c. In the New Host dialog box, enter the following details:

Host Name The fully qualified domain name or IP address of the host
that is assigned when creating the host.

Description A description of the host.

Purpose Select a purpose for the host. Note that a host over a
firewall can only have a Load Generator purpose.

Source Select the host's source: Local if the host exists in your
testing lab, or Cloud if the host was provisioned from a
cloud provider.
Priority A rank assigned to the host. Assigning a higher priority to a
host increases the likelihood of the host being allocated to
a test. There are a number of criteria to consider when
assigning priority. The main considerations are whether
the host is a dedicated machine or a shared resource, and
the type of hardware installed on the machine.

Status Indicate the current status of the host.

Location The location of the host that is over the firewall.

Installation Select the installation type of the host.

For a standalone installation of the Load Generator, select
OneLG.

MI Listener Enter the IP address or host name of the MI Listener that

enables data collection.

LoadRunner Enterprise (2023-2023 R1) Page 164 of 194

Installation Guide
Working with firewalls

Enable SSL Indicates whether the Load Generator is to communicate

with the Controller via TLS (formerly SSL) or not. This
option is available when the load generator is located over
a firewall.

Note: The load generator uses TLS to communicate

with the Controller during runtime only. For non
runtime functionality (including collating results), the
Load Generator does not use Tas the
communication protocol.

Belongs to The host pools to which the host is assigned.

Pools Host pools enable you to control which hosts are allocated
to which projects.

Host Attributes of the host.

Attributes Example: Memory, strength, installed components

LoadRunner Enterprise (2023-2023 R1) Page 165 of 194

Monitor over a firewall
You can set up LoadRunner Enterprise to monitor servers over a firewall.

This chapter includes:

• Monitor over a firewall: basic steps 167

• Configure monitor settings 168
• Configure the project to receive monitor over firewall information 173
• Edit monitor over firewall machines during a test run 174

LoadRunner Enterprise (2023-2023 R1) Page 166 of 194

Installation Guide
Working with firewalls

Monitor over a firewall: basic steps

Note: Before you configure your system to monitor servers over a firewall,
ensure that you have completed the configuration steps described in "Initial
configuration of the over firewall system" on page 154.

To set up your system to monitor servers over a firewall:

1. In LoadRunner Enterprise Administration, specify the details of the MI Listener
used to monitor servers over the firewall. For details, see "Specify MI Listeners"
on page 159.
2. Configure the LoadRunner Enterprise agent on each Monitor Over Firewall
machine to communicate with the MI Listener.
For details, see "Configure the LoadRunner Enterprise agent" on page 175.

LoadRunner Enterprise (2023-2023 R1) Page 167 of 194

Installation Guide
Working with firewalls

3. Use the Monitor Configuration tool to configure the servers to monitor and
define specific measurements that LoadRunner Enterprise collects for each
monitored server.
For details, see "Configure monitor settings" below.

4. In the relevant project, establish a connection between the tests you are
running and the Monitor Over Firewall machines.
For details, see "Configure the project to receive monitor over firewall
information" on page 173.

Configure monitor settings

You configure the monitor settings from the Monitor Over Firewall machine, using
the Monitor Configuration tool. You select the type of monitors to run and the
server whose resources you want to monitor, add the measurements to monitor for
each server, and specify the frequency at which the monitored measurements are
to be reported.

To configure monitor settings:

1. On the Monitor Over Firewall machine, select LoadRunner > Advanced
Settings > Monitor Configuration from the Start menu. For machines without
the complete LoadRunner Enterprise installation, select Server Monitor >
Monitor Configuration from the Start menu. The Monitor Configuration dialog
box opens.

LoadRunner Enterprise (2023-2023 R1) Page 168 of 194

Installation Guide
Working with firewalls

2. Click the Add Server button . The New Monitored Server Properties dialog
box opens.

LoadRunner Enterprise (2023-2023 R1) Page 169 of 194

Installation Guide
Working with firewalls

3. In the Monitored Server box, enter the name or IP address of the server whose
resources you want to monitor.

Note: To add several servers simultaneously, you can specify IP ranges,

or separate the server names or IP ranges with commas. For example,
255.255.255.0-255.255.255.5, or server1, server2.

4. From the Available Monitors list, select the monitors suitable for the server
being monitored.
5. Click OK to close the New Monitored Server Properties dialog box. The
Monitored Servers list is displayed in the Monitor Configuration dialog box.

Default measurements are displayed for some of the monitors in the

Measurements to be Monitored section. You can specify the frequency at which
to report the measurements in the Measurement Properties section.

LoadRunner Enterprise (2023-2023 R1) Page 170 of 194

Installation Guide
Working with firewalls

6. To add additional monitored servers to the list, repeat the steps above.
7. To edit the monitor configuration properties for a server, click the Edit button
. The Monitored Server Properties dialog box opens enabling you to edit
the monitors for the server whose resources you are monitoring.
8. Click Apply to save your settings.

Clone a monitored server's properties

To monitor the same properties on different server machines, you can clone a
selected server's properties using the Clone Monitored Server Properties dialog
box.

To clone a monitored server's properties:

1. Open the Monitor Configuration dialog box.
2. Right-click the server you want to clone, and select Clone. The Clone
Monitored Server Properties dialog box opens.

3. In the Monitored Server box, enter the name or IP address of the cloned server
you want to create.

LoadRunner Enterprise (2023-2023 R1) Page 171 of 194

Installation Guide
Working with firewalls

Tip: To create several cloned servers simultaneously, you can specify IP

ranges, or separate the server names or IP ranges with commas. For
example, 255.255.255.0-255.255.255.5, or server1, server2.

4. The Available Monitors list displays the monitors that were selected for the
server being cloned. Select additional suitable monitors for the cloned server.
5. Click OK to close the Clone Monitored Server Properties dialog box. The cloned
server is displayed in the Monitored Servers list.
6. Click Apply to save your settings.

Add and remove measurements

After you configure one or more server machines to monitor, you add
measurements to monitor for each server. If LoadRunner Enterprise added default
measurements, you can edit them as required.

To add a measurement to monitor:

1. Open the Monitor Configuration dialog box.
2. Select a server from the Monitored Servers list.

3. Click the Add Measurement button . Select the appropriate monitor. A

dialog box opens, enabling you to choose measurements for the monitor you
selected.
4. Select the measurements that you want to monitor, and click OK.
5. Click Apply to save your settings.

To remove a measurement from the measurements list:

1. Select the measurement, and click the Delete button .

2. Click Apply to save your settings.

Configure measurement frequency

After you have configured monitor measurements, you set a schedule for reporting
each measurement.

LoadRunner Enterprise (2023-2023 R1) Page 172 of 194

Installation Guide
Working with firewalls

To configure measurement frequency:

1. In the Monitor Configuration dialog box, under the Measurement Properties
section, select the configured server measurement you want to schedule.
2. Specify the frequency at which you want LoadRunner Enterprise to report the
measurement.
3. Click Apply to save your settings.

Configure the project to receive monitor over

firewall information
After you configure the monitors, you configure the project to receive Monitor Over
Firewall information during performance test runs.

Note: The steps in the section are described in more detail in the section
about monitor profiles in the LoadRunner Enterprise User Guide.

To configure the project to receive Monitor Over Firewall

information:
1. Add a monitor over firewall which can be accessed by performance tests in this
project.

a. In LoadRunner Enterprise, click Open the navigation toolbar and select

Monitors (under Assets).

b. Click New Monitor Over Firewall.

c. Enter a name, the machine key, and select the MI Listener with which the
monitor is to connect.
2. Select the Monitor Over Firewall agent to use in a specific performance test.
a. In the Test Plan module, select a performance test, and click Edit Test to
open the test in the Performance Test Designer window.
b. In the Monitors tab, select the Monitor Over Firewall agent.

LoadRunner Enterprise (2023-2023 R1) Page 173 of 194

Installation Guide
Working with firewalls

Edit monitor over firewall machines during a test

run
While a performance test is running, you can change the status of a Monitor Over
Firewall agent or add another monitor to the test.

To modify the Monitor Over Firewall machines:

1. On the Test Run page, click the Monitors button and select Monitors
Over Firewall. The Monitors Over Firewall dialog box opens.
2. You can view the Monitor Over Firewall agents that are monitoring the test, as
well as their connection status.
l To connect or disconnect a Monitor Over Firewall agent, click the
Connect/Disconnect button.
l To add a Monitor Over Firewall agent to the test, select it from the Add
Monitor Over Firewall list.

LoadRunner Enterprise (2023-2023 R1) Page 174 of 194

Configure the LoadRunner Enterprise agent
You can set up your LoadRunner Enterprise system to run Vusers and monitor
servers over a firewall. As part of the process of setting up your LoadRunner
Enterprise system to work over firewalls, you configure the LoadRunner Enterprise
agent.

This chapter includes:

• Configure LoadRunner Enterprise agents over the firewall: basic steps 176
• Configure the Windows LoadRunner Enterprise agent 176
• Configure and run the Linux LoadRunner Enterprise agent 178
• Agent configuration settings 179
• Check connectivity 181

LoadRunner Enterprise (2023-2023 R1) Page 175 of 194

Installation Guide
Working with firewalls

Configure LoadRunner Enterprise agents over

the firewall: basic steps
For LoadRunner Enterprise to work over firewalls, you need to configure the
LoadRunner Enterprise agent on each Load Generator machine running over a
firewall, and on each Monitor Over Firewall machine.

You configure the LoadRunner Enterprise agent to communicate with the

MI Listener. The MI Listener serves as a router between the LoadRunner Enterprise
agent and the Controller.

Configure the Windows LoadRunner Enterprise

agent
This section describes how to configure the LoadRunner Enterprise Agent on
Windows machines to communicate with the MI Listener.

LoadRunner Enterprise (2023-2023 R1) Page 176 of 194

Installation Guide
Working with firewalls

To configure the LoadRunner Enterprise agent on Windows

machines:
1. From the Start menu, select LoadRunner > Advanced Settings > LoadRunner
Enterprise Agent Configuration or run <LoadRunner Enterprise
root>\launch_service\bin\AgentConfig.exe.
2. In the Agent Configuration dialog box, select Enable Firewall Agent.
3. Click Settings. The Agent Configuration dialog box displays a list of settings.
4. Set each option as described in "Agent configuration settings " on page 179.
Pay careful attention to the first three settings.
5. Click OK to save your changes.
6. When prompted, click OK to restart the LoadRunner Enterprise agent.
7. Check the connection status between the LoadRunner Enterprise agent and
the MI Listener.
a. Change the Agent Runtime settings to run as a process and check the
status. For details, see "Run the LoadRunner Enterprise agent as a process"
on page 141.
b. If the status is OK, revert back to running it as a service. For details, see "Run
the LoadRunner Enterprise agent as a service" on page 141.

Notes:
o When you configure the LoadRunner Enterprise agent on Windows
machines, the Remote Management agent is automatically
configured with the same settings. The Remote Management agent
enables you to manage remote machines from LoadRunner
Enterprise Administration.
o After you have configured the LoadRunner Enterprise agent on the
Load Generator machine, you can edit the configuration settings
from LoadRunner Enterprise Administration. For details, see the
Help Center.

LoadRunner Enterprise (2023-2023 R1) Page 177 of 194

Installation Guide
Working with firewalls

Configure and run the Linux LoadRunner

Enterprise agent
Load Generator hosts can be installed on Linux machines. This section describes
how to configure and run LoadRunner Enterprise agents on Linux machines.

Note: As part of the process of configuring the LoadRunner Enterprise Agent

on Linux machines, you also need to configure the Remote Management
agent. The Remote Management agent enables you to manage remote
machines from LoadRunner Enterprise Administration.

To configure the LoadRunner Enterprise Agent on Linux machines:

1. Activate the firewall service for the LoadRunner Enterprise agent:
a. Open <LoadRunner Enterprise root folder>/dat/br_lnch_server.cfg in a
text editor.
b. In the Firewall section, set FireWallServiceActive to 1 and save your
changes.
2. Activate the firewall service for the Remote Management agent:
a. Open <LoadRunner Enterprise root folder>/al_agent/dat/
br_lnch_server.cfg in a text editor.
b. In the Firewall section, set FireWallServiceActive to 1 and save your
changes.
3. Run agent_config from the <LoadRunner Enterprise root folder>/bin
directory and enter the agent configuration settings (see "Agent configuration
settings " on the next page).

Note: When you set the agent configuration settings, they are applied to
both the LoadRunner Enterprise and Remote Management agents.

4. Restart the LoadRunner Enterprise agent for the configuration changes to take
effect.

LoadRunner Enterprise (2023-2023 R1) Page 178 of 194

Installation Guide
Working with firewalls

5. Restart the Remote Management agent for the configuration changes to take
effect.
a. To stop the Remote Management agent, run the following command from
the <LoadRunner Enterprise root folder>/al_agent/bin directory:

al_daemon_setup -remove

b. To start the Remote Management agent, run the following command from
the <LoadRunner Enterprise root folder>/al_agent/bin directory:

al_daemon_setup -install

Agent configuration settings

The following table provides an explanation of the agent configuration settings:
Default
Setting Value Description

MI Listener none The host name, fully qualified domain name, or IP

name address of the MI Listener.

Local none A symbolic string identifier used to establish a

Machine Key unique connection between the Controller host and
the agent machine, via the MI Listener machine.
When configuring a Monitor Over Firewall agent, you
can enter any logical name, using lowercase letters
only.
When configuring the agent on a load generator to
run Vusers over a firewall, you must use the format
hostname_locationname where:
l hostname is the name of the host as found in
LoadRunner Enterprise Administration's Hosts
page.
l locationname is the name of the host location as
found in LoadRunner Enterprise Administration's
Host Locations page.

LoadRunner Enterprise (2023-2023 R1) Page 179 of 194

Installation Guide
Working with firewalls

Default
Setting Value Description

Connection 20 The length of time you want the agent to wait before
Timeout seconds retrying to connect to the MI Listener machine. If
(seconds) zero, the connection is kept open from the time the
agent is run.

MI Listener none The user name needed to connect to the MI Listener

User Name machine.

MI Listener none The password needed to connect to the MI Listener

Password machine.

Server none The domain name needed to connect to the MI

Domain Listener machine. This field is required only if NTLM
is used.

Connection TCP Select either TCP or HTTP, depending on the

Type - configuration you are using.
TCP/HTTP

Connection none If you select HTTP, configure the following:

Type - l Proxy Name. The name of the proxy server. The
HTTP
proxy server must support HTTP tunneling using
the CONNECT method. This field is mandatory if
the Connection Type setting is HTTP.
l Proxy Port. The proxy server connection port.
This field is mandatory if the Connection Type
setting is HTTP.
l Proxy User Name/Password. The credentials of a
user with connection rights to the proxy server.
l Proxy Domain. The user's domain if defined in the
proxy server configuration. This option is required
only if NTLM is used.

LoadRunner Enterprise (2023-2023 R1) Page 180 of 194

Installation Guide
Working with firewalls

Default
Setting Value Description

Use Secure disabled Enable to connect using the TLS (formally SSL)
Connection protocol.
(SSL)
When a proxy server is used, TLS is enabled by
default and cannot be disabled.
If you enable this option, enter the following
information:
l Check Server Certificates. Authenticates the
TLS certificates that are sent by the server.
l Select Medium to verify that the server

certificate is signed by a trusted Certification

Authority.
l Select High to verify that the sender IP matches

the certificate information. This setting is

available only if Use Secure Connection is set
to True.
l Private Key Password. The password that might
be required during the TLS certificate
authentication process. This option is relevant
only if the Client Certificate Owner option is
enabled.

Check connectivity
To run Vusers or monitor servers over a firewall, you must be able to establish a
connection between the LoadRunner Enterprise agent, MI Listener, and the
Controller machine.

If you encounter connectivity problems after installing and configuring all the
necessary components, check the table below for troubleshooting tips.

LoadRunner Enterprise (2023-2023 R1) Page 181 of 194

Installation Guide
Working with firewalls

Check Solution

To check that l Windows Installation:

the Firewall a. Change the Agent Runtime settings to run as a process
service was and check the status. For details, see "Run the
activated on the LoadRunner Enterprise agent as a process" on page 141.
agent machine:
b. If the status is OK, revert back to running it as a service.
For details, see "Run the LoadRunner Enterprise agent as
a service" on page 141.
Otherwise, you need to reconfigure the LoadRunner
Enterprise Agent on your Windows machine. For details,
see "Configure the Windows LoadRunner Enterprise
agent" on page 176.
l Linux Installation:
In the temporary directory of the LoadRunner Enterprise
Agent machine, locate the <local_machine_key>_
connected_to_MI_Listener file. If the file is missing, this
indicates that the FirewallServiceActive=1 is not set in the
[FireWall] section of the Agent Settings. For details, see
"Configure and run the Linux LoadRunner Enterprise agent"
on page 178.

To check that On the agent machine, open a command prompt window, and
port 443 is type the following:
open: telnet <MI_Listener_IP> 443.
Example: telnet 111.111.111.1111 443
If port 443 is open, a new Telnet window opens. If port 443 is
not open, contact your network administrator.

To check that If a web server is running on the MI Listener or Monitor Over

port 443 is Firewall machine, port 443 does not allow the access required
available: by the listening and monitoring processes. Contact your
network administrator to change the web server port.

LoadRunner Enterprise (2023-2023 R1) Page 182 of 194

Installation Guide
Working with firewalls

Check Solution

To check When running the LoadRunner Enterprise Agent as a service,

connectivity do the following:
between the l Check that port 443 is open. See "To check that port 443 is
agent and the
open: " on the previous page.
MI Listener,
when running l Check that the Agent Settings and Agent Configuration are
the LoadRunner correctly set. For details, see "Configure LoadRunner
Enterprise Enterprise agents over the firewall: basic steps" on
Agent as a page 176.
service: l Run the agent as a process by launching
<Installation>\Launch_service\bin\magentproc.exe. If
you are successful, this indicates an authentication issue
with the LoadRunner Agent Service. Browse to the
Administrative Tools > Services > LoadRunner Agent
Service and change the properties of this service to System
User Account, or provide the username and password of a
user who has administrative privileges on this machine.

LoadRunner Enterprise (2023-2023 R1) Page 183 of 194

Troubleshooting

LoadRunner Enterprise (2023-2023 R1) Page 184 of 194

Troubleshooting installation issues
This chapter provides troubleshooting for issues that arise when installing
LoadRunner Enterprise components and during initial configuration.

Problem Troubleshooting

Default monitor This occurs when LRE is configured with a local user.
measurements
Create a user account on OneLG hosts with the same credentials and
aren't displayed in
permissions as the LRE account.
online graphs when
using OneLG hosts For example, if you used the default local user (IUSR_METRO) on LRE servers
and hosts, create the IUSR_METRO user and add it to the Administrators
group on the OneLG machine.

Host silent .NET Framework 4.8 replaces the .NET Framework 4.6.2 and earlier files. If
installation stops there are any applications that are using the .NET Framework 4.6.2 or earlier
after installing .NET files and are running during the installation of .NET Framework 4.8, you may
Framework 4.8 need to restart your machine.

If you are prompted to restart the machine, restart it before continuing the
installation. Refer to the product documentation for more details.

LRE uninstall fails or This error can occur if LRE uninstall does not complete successfully, takes a
freezes long time and seems to have frozen, or if LoadRunner Enterprise is not found
in Add/Remove Programs.
l Reboot the machine and uninstall again (unless LRE no longer appears in
Add/Remove Programs).
l Alternatively, you can:
a. Open a command prompt and run:
<Host installation path>\bin\HP.PC.PCS.Configurator.exe
/CFG:..\dat\setup\lts\xml\Configurator.xml /G:Uninstall

b. Delete LoadRunner Enterprise Host from the Start menu.

c. Open the Windows Installer CleanUp Utility and delete the product
from the MSI manager. Refer to the product documentation for more
details.

LoadRunner Enterprise (2023-2023 R1) Page 185 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

Unable to log on to If you encounter "JavaScript is not installed or is disabled in your browser"
LRE via the client error, this problem is related to running JavaScript in your browser.
machine
To resolve this issue:

1. In the Control Panel, select Internet options > Security.

2. Select Internet zone and click Custom Level.
3. Make sure that Active Scripting is enabled.
4. Enable the following items under ActiveX controls and Plug-ins:
l Automatic prompting for ActiveX controls
l Binary and script behaviors
l Run ActiveX controls and plugins
l Script ActiveX controls marked safe for scripting

Initializing Run page The client machine needs to have access to the machine. For example, if the
does not load when Administrator inserted the machine name without the domain, you might need
starting a test run to add the IP address and machine name to the host file
(C:\WINDOWS\system32\drivers\etc\hosts) on the client machine.

Unable to run the To run setup.exe from a network location, you need to add the network
setup LRE server or server location to your Trusted Sites, and then run setup.exe again.
host installation
To add the network server to your Trusted Sites:
from a network
drive 1. In the Control Panel, select Internet Options > Security.
2. Click Trusted Sites and then click the Sites button.
3. In the Trusted Sites dialog box, add the location of the network server
where the LRE component setup file is located, to the list of trusted sites.

Unable to install 1. Make sure the user running the installation has sufficient permissions to
LRE components launch executable files.
from the installation 2. Restart the machine and try again.
directory

LoadRunner Enterprise (2023-2023 R1) Page 186 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

LRE information is To prevent LRE information being disclosed in the IIS and ASP.NET response
displayed in IIS and headers, we recommend removing the server- and version-specific headers
ASP.NET response from the default Web site, or any other site that was used for the LRE
headers installation.

If using IIS 10.0 or later:

1. Open IIS Manager.

2. Select the server in Connection tree view.
3. Expand Sites, and select Default Web Site.
4. Open the Configuration Editor User Interface module, and in the Section
combo box, select system.webServer/security/requestFiltering.
5. Change the value of the removeServerHeader property to True.

If using an earlier version of IIS:

In IIS Manager, use the URL Rewrite extension for removing these HTTP
headers.

LoadRunner Enterprise (2023-2023 R1) Page 187 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

LRE does not work The Microsoft SQL instance must use a static port. The correct port must be
on non-default defined in the connection string.
ports in Microsoft
SQL

No error message This problem is possibly caused by the configuration process. Validate the
when a following:
performance test l The LoadRunner Load Testing Service in running on the host machine
fails to start
under the system account.
l The LRE user (IUSR_METRO) exists.
l On LRE host machines designated as Controllers, open the folder
<LRE root folder>\config. Open wlrun7.ini in a text editor, and make sure
that IsOrchid and IsOrchid10 are both set to 1.

Online topology When running a performance test that contains topology, the topology
monitors are not monitors data is not shown. You may get the following error when clicking the
displayed topology tab view: This node does not have a monitor.

1. On the Host machine, validate that EnableInUi is set to 1 in <install

folder> dat\online_graphs\online_resource_graphs.rmd
2. In Sitescope, set the monitor frequency value (by default it is set to 10
minutes). Make sure it is set for less than 10 seconds.

Unable to configure After running the LRE Server Configuration wizard, the following error is
LRE server or host displayed in the log file: "The process cannot access the file
when the process is 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\config\machine.config'
used by another because it is being used by another process."
process
This problem occurs when the configuration updates the .NET machine.config
file while it is in use by another process (for example, IIS). When the file is in
use, the update fails.

Restart the machine and start the LRE Server Configuration wizard.

LRE configuration This problem occurs if the influxdb.exe process and the LRE Host
host fails to start Configuration wizard are running at the same time.
the LoadRunner
Make sure the influxdb.exe process is not running before you run the LRE
Center Data Service
Host Configuration wizard.

LoadRunner Enterprise (2023-2023 R1) Page 188 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

LRE service fails to Increase the global timeout for the service startup in the Windows registry. By
start after default, the timeout is 30000 milliseconds and the registry value does not
successfully exist.
configuring the LRE
1. Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control in
server
the Registry Editor.
2. Add a new DWORD value (name it ServicesPipeTimeout), set Base to
Decimal, and enter a value of 60000 (equivalent to 60 seconds).

LoadRunner Enterprise (2023-2023 R1) Page 189 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

Configure LRE to For requests over HTTPS only, you need to configure LRE to work with secure
work with secure cookies over a secure connection.
cookies over a
Set secure cookies on LRE web pages:
secure connection
1. Log onto the LRE server machine.
2. Open the <LRE server installation folder>\PCWEB\web.config file for
editing.
3. Search for ‘requireSSL’ in the file (there should be two occurrences), and
set the requireSSL attribute to true.
4. Save the file.
5. Open the <LRE server installation
folder>\PCWEB\bin\HP.PC.Web.UI.UserSite.dll.config file for editing
and repeat steps 3 and 4.
6. Repeat steps 1-5 for each LRE in the same environment.
Set secure cookies on LRE Administration web pages

1. Log onto the LRE server machine.

2. Open the <LRE server installation folder>\PCWEB_ADMIN\web.config
file for editing.
3. Search for the section 'httpCookies'.
l If it exists, set the value of the requireSSL attribute to true.
l If the section does not exist, add the following element under the
<system.web> XML element:
<httpCookies httpOnlyCookies="true" requireSSL="true" />
4. Save the file.
5. Repeat steps 1-4 for each LRE server in the same environment.
Note: You may be exposing the system to increased security risks if you do
not set the requireSSL cookie configuration.

Unable to log on to If you receive the following error message "Problem encountered when
the database server application tried to connect to database.", verify that the database server
host name, type, username, and password are correct. Consult your database
administrator if you are unsure.

Incorrect time Changing the time zone on the LRE Server or any external analysis database,
range displayed in results in the incorrect time range being displayed when running a
online graph performance test in the online graph.

To ensure the correct time range for running the performance test is
displayed in the online graph, verify the time zone is synchronized on the LRE
Server and any external analysis database servers.

LoadRunner Enterprise (2023-2023 R1) Page 190 of 194

Installation Guide
Troubleshooting

Problem Troubleshooting

Unable to install Windows SmartScreen prevents NVinstaller.exe from running and installing
Network NV Components.
Virtualization (NV)
1. Before proceeding with the NV installation, open HKEY_LOCAL_
components
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
in the Registry Editor.
2. Change the Value data for SmartScreenEnabled to "Off" to disable
Windows SmartScreen.

Working with LRE When working with LRE, we recommend disabling the Windows Firewall on all
when Windows LRE server and host machines in the system, except for SiteScope.
Firewall is enabled
If you are using LRE with Windows Firewall enabled, the Windows Firewall
must be reconfigured to allow inbound and outbound communication on
specific ports used by LRE. For details, "Configure LRE to work with Windows
Firewall" below.

Unable to install a If the installation cannot use a default port because it is already in use,
LRE component if change the port as per the instructions described in "Change LRE component
the default port is in port when default port in use" on the next page.
use

Configure LRE to work with Windows Firewall

LoadRunner Enterprise server:

Local
Process / Service Direction Protocol Port Remote Port Path

World Wide Web Inbound TCP 80 Any Service

Service
(HTTP Traffic-In)

LoadRunner Remote Inbound TCP 3333 Any <LRE Server install

Management Agent dir>\al_agent\bin
Service \alagentservice.exe

ALWrapperServer.exe Outbound TCP Any 54245 <LRE Server install

dir>\bin
\ALWrapperServer.exe

LRECoreAPI.exe Outbound TCP Any Default ports: 1433

(MS SQL), 1521
(Oracle), 5432
(PostgreSQL)

w3wp.exe Outbound TCP Any 8080, 8731, 3333

HTTP Any 8086

LoadRunner Enterprise (2023-2023 R1) Page 191 of 194

Installation Guide
Troubleshooting

LoadRunner Enterprise host:

Local Remote
Process / Service Direction Protocol Port Port Path

Datacollectionagent.exe Inbound TCP 3333 Any <Host install dir>\bin

\datacollectionagent.exe

LoadRunner Remote Inbound TCP 54245 Any <Host install dir> \al_agent\bin
Management Agent \alagentservice.exe
Service

LoadRunner Agent Inbound TCP 54345, Any <Host install dir>\ launch_
Service 50500 service \bin\magentservice.exe

System Inbound TCP 8731 Any

Influxdb.exe Inbound HTTP 8086 Any <Host install

dir>\bin\influxdb\Influxdb.exe

LTOPSvc.exe Outbound TCP Any 80, 8080 <Host install

dir>\LTOPbin\LTOPSvc.exe

Change LRE component port when default port in use

Component How to change the port

LRE Server IIS To change this port, refer to the product documentation.

LRE host To change port 8731 to a different port:

1. On each LoadRunner Enterprise host, open

LTOPSvc.exe.config located in <LRE host Installation
directory>\bin\LTOPbin\ and change all four occurrences of
8731 to a new port number. Restart the LoadRunner Load
Testing Service.
2. On the LoadRunner Enterprise server, open pcs.config
(located in <LRE server installation directory>\dat\). Under
PCSSettings, change ltopPortNumber to the new port
number.

LoadRunner Enterprise (2023-2023 R1) Page 192 of 194

Installation Guide
Troubleshooting

Component How to change the port

MI Listener To change port 443 to a different port, perform the following steps
on the following machines:

MI Listener or Controller machine if used as MI Listener:

1. Open <Component installation directory>\launch_

service\dat\mdrv.dat, and locate the [launcher] section.
2. Add OFWPort=<port>, where <port> is the new port number.
3. Go to <Component installation directory>\launch_
service\dat\channel_configure.dat and locate the [General]
section.
4. Add OFWPort=<port>, where <port> is the new port number.
5. Restart the agent.
Windows OneLG machine:

1. Open C:\Program Files (x86)\Micro Focus\LoadRunner

OneLG\config\m_agent_attribs.cfg, and add
ServerPort=<port> to the Agent section.
2. Restart the LoadRunner Agent service.
Linux OneLG machine:

1. Open the $M_LROOT/config/.mercury/m_agent_attribs_

<hostname>.cfg file, and add ServerPort=<port> to the
Agent section.
2. Restart the daemon:
./m_daemon_setup -remove
/m_daemon_setup -install
MOFW machine:

1. Open C:\Program Files (x86)\Micro Focus\Monitors Over

Firewall\config\m_agent_attribs.cfg, and add
ServerPort=<port> to the Agent section.
2. Restart the LoadRunner Agent service.
Note: There is no support for changing port 50500.

LoadRunner Enterprise (2023-2023 R1) Page 193 of 194

Installation Guide
Troubleshooting

Component How to change the port

LoadRunner Agent Changing the port for a Controller machine:

1. Stop 'LoadRunner Agent Service'.

2. Open for edit the file: <Install folder\dat\merc_agent.cfg
3. Under the [Attributes] section, add the line: "AgentPort=<New
Port Value>"
4. Restart the service.
Changing the port for a Load Generator machine:

1. Stop 'LoadRunner Agent Service'.

2. Open for edit the file: <Install folder\launch_service\dat\merc_
agent.cfg
3. Under the [Attributes] section, add the line: "AgentPort=<New
Port Value>"
4. Restart the service.

Autolab Agent This service is used to perform administration tasks on all

(RemoteManagementAgent) LoadRunner Enterprise machines. By default, Autolab Agent is
using port 54245. The port number can be changed. However, the
new value must be configured on each machine (server, host, Load
Generator).

To change the port:

1. Stop 'RemoteManagementAgent'.
2. Open <Install folder>\launch_service\al_agent\dat\merc_
agent.cfg
3. Under the [Attributes] section, add the line: "AgentPort=<New
Port Value>“
4. Restart the service.

SiteScope (Topology) In LoadRunner Enterprise, change the port of the Topology entity
to the same port as that defined during the SiteScope
configuration.

SiteScope (Topology) - SSL In LoadRunner Enterprise, change the port of the Topology entity
to the same port as that defined during the SiteScope
configuration.

SiteScope (Monitor Profiles) In LoadRunner Enterprise, change the port of the Monitor Profile
entity to the same port as that defined during the SiteScope
configuration.

LoadRunner Enterprise (2023-2023 R1) Page 194 of 194