Support Matrix

LoadRunner Professional and LoadRunner Enterprise

Software version 24.3

The Support Matrix provides up-to-date system requirements and supported environments for installing and running LoadRunner Professional (LRP) and LoadRunner Enterprise (LRE).

The Support Matrix is also known as a Product Availability Matrix (PAM).

In this topic:

·    LRP and LRE host requirements  1

·    LRE server requirements  4

·    LRE web client requirements  5

·    Prerequisite software  6

·    Load generator requirements on Linux  9

·    LRE server monitors – IPv6 support 12

·    Virtual Table Server requirements  13

·    Cloud computing  13

·    Integrations  13

·    Supported GUI languages  16

·    Product Support Lifecycle  17

LRP and LRE host requirements

This section provides system requirement information for installing the following products on a Windows machine: LoadRunner Professional Full, LoadRunner Enterprise Host, VuGen Standalone, Analysis Standalone, OneLG (standalone load generator), Monitor over Firewall, and MI Listener.

Hardware requirements

This table provides hardware requirements for the products listed above. Memory and CPU requirements vary per protocol and system under test.

Hardware component

Supported / Recommended

Processor

·        4 core CPU

·        8 core CPU (Recommended)

Processor for UI-level protocols*

·        8 core CPU

·        16 core CPU (Recommended)

Memory (RAM)

·        8 GB

·        16 GB (Recommended)

Memory (RAM) for UI-level protocols*

·        16 GB

·        32 GB (Recommended)

Available hard disk space**

·        50 GB

·        100 GB; SSD drive (Recommended)

Network card

1 Gbit/s

* For example, Citrix, SAP GUI.

** All drives must have the minimum disk size required: at least 2 GB on the host system drive, and the amount specified in the product installation guide for any other drive.

Software requirements

This table provides software requirements for the products listed above. For some Vuser protocols, one or more of the below OS may not be supported. For Vuser protocol details, see Supported Protocols.

Software component

Supported / Recommended

Operating system
(see Windows Updates below)

·        Microsoft Windows 10 64-bit versions Enterprise LTSC 2019, 22H2 - (Recommended)

·        Microsoft Windows 11 64-bit 21H2, 22H2, 23H2

·        Microsoft Windows Server 2016 64-bit*

·        Microsoft Windows Server 2019 64-bit* (Recommended)

·        Microsoft Windows Server 2022 64-bit*

Browser
(used for recording and replaying protocols only)

·        Google Chrome (Recommended)

·        Microsoft Edge

·        Mozilla Firefox

Screen resolution**

·        1366x768 or higher

·        1600x900 or higher (Recommended)

* We recommend enabling Desktop Experience when using this operating system.

** Controller is not supported on display monitors with a 4K or higher resolution.

Windows updates

Before you install any components on a Windows machine, make sure that the full set of Windows updates has been installed, or install the Windows updates listed in the table below.

Windows version

Required updates

Windows 2016 64-bit*

Install the following pack of updates:

1.      KB4494440 x64

2.     KB5031362 x64

Windows 2019 64-bit*

KB5031361 x64

Windows 2022 64-bit*

KB5031364 x64

     Windows 10 64-bit*

1.      KB5031356 x64

2.     KB4495610 x64

3.     KB4487026 x64

4.     KB4480961 x64

* The list of required updates might change due to Microsoft’s update delivery policy or new Windows update releases. If you experience any issues, please contact Software Support.

Component coexistence

The LoadRunner Professional Full installation is installed on a single machine.

All the other LoadRunner components listed in LRP and LRE host requirements must be installed on a separate machine, except for the following:

·        Analysis Standalone which can coexist on the same machine with VuGen Standalone

·        OneLG which can coexist on the same machine with VuGen Standalone

Analysis database types

The following table lists the database types and versions that are supported by LoadRunner Analysis:

Supported database type

Versions

Microsoft Access

2016, 2021

Microsoft SQL Server

2019

SQLite

V3

 Back to top

LRE server requirements

The LRE server has the following system requirements:

Component

Supported / Recommended

Processor

·        8 core CPU

·        16 core CPU (Recommended)

Memory (RAM)

·        16 GB

·        32 GB or higher (Recommended)

Available hard disk space*

·        150 GB

·        200 GB; SSD drive (Recommended)

Operating system

·        Microsoft Windows Server 2016 64-bit**

·        Microsoft Windows Server 2019 64-bit** (Recommended)

·        Microsoft Windows Server 2022 64-bit**

Database***

·        Microsoft SQL Server 2014 (SP3 and above)

·        Microsoft SQL Server 2016

·        Microsoft SQL Server 2017

·        Microsoft SQL Server 2019

·        Microsoft SQL Server 2022

·        Oracle 18c

·        Oracle 19c

·        PostgreSQL 11.x, 12.x, 13.x, 14.x

Web server

IIS 8.0, 8.5, 10.0

* All drives must have the minimum disk size required: at least 2 GB on the host system drive, and the amount specified in the product installation guide for any other drive.

** We recommend enabling Desktop Experience when using this operating system.

*** LRE is not supported with cloud managed databases (RDS).

 Back to top

LRE web client requirements

The following table displays the system requirements for LRE web client:

Component

Supported / Recommended

Screen resolution

·        Microsoft Windows: 1366x768 or higher

·        Microsoft Windows: 1600x900 or higher (Recommended)

·        Mac OS: 1280x800 or higher

For best results, set the display scaling to 100%.

Browser

Windows*:

·        Google Chrome (Recommended):

·        The two latest versions

·        Chrome for Business

·        Microsoft Edge 79 or later

·        Mozilla Firefox:

·        The two latest versions

·        ESR 52

macOS:

·        Apple Safari 13, 14

* For optimal performance on Windows, we recommend using Google Chrome.

 Back to top

Prerequisite software

Before installing LRP or LRE, make sure the prerequisite software is installed on the LoadRunner machine running on Windows environment. Some of the prerequisite software is automatically detected and installed by the installer; other prerequisite software must be installed manually.

When you run the installation wizard, the wizard detects which prerequisite software is already installed on the machine and which software is missing. When you continue with the installation, all missing prerequisite software is installed.

LRP

The following prerequisite software must be installed:

Prerequisite software

   Means of detection

.NET Framework 4.8

Searches the registry key for the Release value. Its expected value should be greater than 528040:

HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

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.

Microsoft Visual C++ Redistributable for Visual Studio 2015-2022 (x86 and x64)

 

Queries the MSI manager for the GUID:

·        x86: {65E5BD06-6392-3027-8C26-853107D3CF1A}

·        x64: {36F68A90-239C-34DF-B58C-64B30153CE35}

In addition, the following Windows updates need to be manually installed:

·        Windows 10: KB5031356

 

LRE

The following table provides a list of the prerequisite software, the machines on which it should be installed, and how LRE detects whether the software is installed:

Prerequisite software

Machines

   Means of detection

.NET Framework 4.8

·        All LRE server and host machines

·        Standalone VuGen

·        OneLG (load generator)

·        Standalone Analysis

Searches the registry key for the Release value. Its expected value should be greater than 528040:

HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

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.

.NET Core hosting 8.0.10

LRE server

Check for the registry key:

\HKEY_LOCAL_ MACHINE\SOFTWARE\WOW6432Node\Microsoft\Updates\.NET Core\Microsoft .NET Core - Windows Server Hosting (x86)

Microsoft Access Database Engine 2016

LRE server

Queries the MSI manager for the GUID:

{90160000-00D1-0409-0000-0000000FF1CE}

Note: Uninstall any previous version of Microsoft Access Database Engine before installing Microsoft Access Database Engine 2016.

Microsoft Visual C++ Redistributable for Visual Studio 2015–2022 (x86 and x64)

·        All LRE server and host machines

·        Standalone VuGen

·        OneLG (load generator)

·        Standalone Analysis

Queries the MSI manager for the GUID:

·        {65E5BD06-6392-3027-8C26-853107D3CF1A}

·        {36F68A90-239C-34DF-B58C-64B30153CE35}

In addition, the following Windows updates need to be manually installed:

·        Windows 10: KB5031356

Internet Information Services (IIS)

LRE server

HKLM\SOFTWARE\Microsoft\InetStp

Looks for both Major and Minor numbers.

Supports IIS version 10.0 (Windows Server 2016 with Desktop Experience)

Strawberry Perl 5.10.1

Standalone VuGen

Queries the MSI manager for the GUID:

{C977182F-221A-337A-B681-963808E0023A}

 Back to top

Load generator requirements on Linux

The following table lists the system requirements and distributions for installing the load generator component on a Linux machine. Only the load generator component is supported for installation on Linux. For some Vuser protocols, one or more of the below distributions may not be supported. For Vuser protocol details, see the Supported Protocols guide available from Support Matrix.

Note:

·        Load generators support all X Servers.

·        Network Virtualization is no longer supported on Linux load generators.

Component

Supported / Recommended

Processor

·        4 core CPU

·        8 core CPU (Recommended)

Distribution

·        Oracle Enterprise Linux 8 64-bit

·        Red Hat Enterprise Linux 8.x 64-bit*

·        Red Hat Enterprise Linux 9.x 64-bit (Recommended)

·        SUSE Linux Enterprise Server (SLES) version 15 64-bit

·        Ubuntu Server Linux 20.04 LTS 64-bit*

·        Ubuntu Server Linux 22.04 LTS 64-bit* (Recommended)

Memory (RAM)

·        8 GB

·        16 GB (Recommended)

Available hard disk space

·        20 GB

·        40 GB (Recommended)

* Supports Dockerized load generators.

Prerequisite packages for 64-bit installations

The following table lists the packages that must be installed on Linux machines before installing the 64-bit version of a load generator:

Prior to installing i386 packages, run the command sudo dpkg --add-architecture i386

Distribution

Prerequisites

How to check if it is installed

   How to install

Red Hat family including Oracle Linux

·        glibc.i686

·        glib2.i686

·        keyutils-libs.i686

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'glibc\.(i686|i386)'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'glib2\.(i686|i386)'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'keyutils-libs\.(i686|i386)'

·        yum install <package_name>

·        yum install keyutils-libs.i686

·        yum install libidn.i686

·        yum install libidn2.i686

Note: If your machine already has GLib 64-bit (such as OL7), make sure to update it to the latest version to avoid conflicts before installing GLib2 32-bit.

 

·        libstdc++.i686

·        libstdc++47.i686 (Amazon Linux)

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'libstdc\+\+[0-9]*\.(i686|i386)'

·        libidn.i686

·        libidn2.i686

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'libidn\.(i686|i386)'

·        ncurses-libs.i686 (required by Security Console)

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'ncurses(-libs)?\.(i686|i386)'

Ubuntu Server

·        libc6-i386

·        libglib2.0-0:i386

·        lib32stdc++6

·        libkeyutils1:i386

·        lib32ncurses6 (required by Security Console)*

·        libidn11:i386**

·        libidn12:i386***

·        libnss3-tools

·        dpkg -l libc6-i386 | grep 'ii'

·        dpkg -l libglib2.0-0:i386 | grep 'ii'

·        dpkg -l lib32stdc++6 | grep 'ii'

·        dpkg -l libkeyutils1:i386 | grep 'ii'

·        dpkg -l lib32ncurses5 | grep 'ii'

·        dpkg -l libidn11:i386 | grep 'ii'

·        dpkg -l libidnss3-tools | grep 'ii'

·         

·        apt-get install <package_name>

·        apt-get install libkeyutils1:i386

·        apt-get install libidn11:i386

·        apt-get install libidn12:i386

·        • apt-get install libnss3-tools

 

 

* for Ubuntu Server Linux 20.04 LTS 64-bit and 22.04 LTS 64-bit

** for Ubuntu Server Linux 20.04 LTS 64-bit

*** for Ubuntu Server Linux 22.04 LTS 64-bit

 

SUSE Linux Enterprise Server (SLES) 64-bit

·        lincurses5 32-bit

·        glibc 32-bit

·        libglib-2_0-0-32bit

·        libstdc++6 32-bit

·        keyutils-libs-32bit

·        libidn11-32bit

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'ncurses[0-9]*-32bit'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'glibc-32bit'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'libglib-2_0-0-32bit'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'libstdc\+\+6-32bit'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'keyutils-libs-32bit'

·        rpm -qa --qf '%{NAME}.%{ARCH}\n' | grep -E 'libidn11-32bit'

·        zypper install libncurses5-32-bit

·        zypper install glibc-32-bit

·        zypper install libglib-2_0-0-32bit

·        zypper install libstdc++6-32-bit

·        zypper install libkeyutils1-32bit

·        zypper install libidn11-32bit

 Back to top

LRE server monitors – IPv6 support

When configuring monitors in LRE, you can specify the server’s name as an IP address in IPv4 format or as an FQDN.  The following table lists the monitors that also support the IPv6 format.

Support status

Monitor name

Full support for IPv6 format

Prometheus, Network Delay Time, SiteScope

Uncertified support for IPv6 format

Apache Web Server, AppDynamics, Azure Insights, CA APM, Dynatrace SaaS, New Relic, Service Virtualization, UNIX Resources

 

No support for IPv6 format

Citrix Server, Microsoft Active Server Pages, Microsoft IIS, Windows Resources

For a list of the relevant monitors, see Monitors requiring configuration.

 Back to top

Virtual Table Server requirements

The system requirements for installing the Virtual Table Server on a Linux machine are the same as for installing a load generator on Linux. For details, see Load generator requirements on Linux.

 Back to top

Cloud computing

LRP and LRE are certified to be installed and run under Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform instances or virtual machines, using a BYOL (Bring Your Own License) model.

Requirements for deploying LRP and LRE on cloud platforms:

·        All components of the cloud computing environment follow the system requirements specified in this document.

·        The required ports are open for communication. For the required ports, see Load Generators on the Cloud in the LRP help, and Communications Paths in the LRE Installation Guide.

Note:

·        Cloud load generators can be provisioned using the built-in functionality of LRP and LRE. For details, see Manage Load Generators on the Cloud in the LRP help and Provision elastic cloud load generators in the LRE help. All other components must be manually installed and configured by the user.

·        To improve performance, it is preferable to deploy the LRE server and hosts, and the database in the same region. Consult the cloud provider help for best practices about network performance.

·        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).

 Back to top

Integrations               

The following integrations are supported with this version of LRP and LRE.

Integrations with other OpenText products

Note: IPv6 support is provided for Application Lifecycle Management and SiteScope.

Product

LoadRunner Professional

LoadRunner Enterprise

Application Lifecycle Management (ALM) 12.60, 12.60 P1, 12.60 P2, 12.60 P3, 15.0, 15.5*, 16.0.x*, 17.0.x*, 24.1*

ü

ü**

ALM Octane 12.55.4 or later (using Jenkins plugin 5.4 or later)

x

ü

Network Virtualization 24.3.0.85

ü

ü

VuGen 2020 SP1, 2020 SP2, 2020 SP3, 2021, 2021 R1, 2021 R2, 2022, 2022 R1, 2022 R2, 2023, 2023 R1, 24.1, 24.3

x

ü

Analysis 2021, 2021 R1, 2021 R2, 2022, 2022 R1, 2022 R2, 2023, 2023 R1, 24.1, 24.3

x

ü

Service Virtualization 5.4.1, 2022, 2022 R1, 2022 R2, 2023 R1

ü

ü

SiteScope 2020.10, 2021.05, 2021.11, 2022.05, 2022.11, 2023.05, 23.4, 24.2

ü

ü

UFT Digital Lab 24.2 (supported in TruClient – Native Mobile protocol only)

ü

ü

UFT One 24.2

ü

ü

* ALM Lab Extension for functional and performance testing should not be enabled on the project.

** LRE integrates with Application Lifecycle Management (ALM) 15.0, 15.5, 16.0.x, 17.0.x and 24.1 only.

Integration with non-OpenText products

The following integrations with non-OpenText products are compatible with this version of LRP and LRE:

Supported products

Supported versions

Comments

Bamboo

Bamboo 5.10.3 – 9.2.3

Uses App Delivery Management Bamboo CI Plugin CE 23.4, available from Atlassian Marketplace.

See the Bamboo plug-in documentation in the LRE help.

Jenkins

Jenkins server 2.461

Uses OpenText Application Automation Tools plugin 24.2.

See the Jenkins documentation in the LRP or LRE help.

TeamCity

TeamCity 2024.03.2

Uses LRE CI plugin 1.0.4, available from JetBrains.

See TeamCity plug-in in the LRE help.

Azure DevOps/TFS

Tested with Team Foundation Server 2018 and Azure DevOps Server 2020

Uses LRE CI plugin 1.1.2, available from Visual Studio Marketplace.

See Azure DevOps plug-in in the LRE help.

New Relic*

Tested with New Relic REST API (v2)

See New Relic Monitor in the LRE help.

Dynatrace SaaS and Managed

 

See Dynatrace SaaS and Managed monitors in the LRP or LRE help.

AppDynamics*

SaaS Controller 23.4.2

See the AppDynamics Monitor documentation in the LRE help.

CA Application Performance Management (CA APM)

10.7

See the CA APM documentation in the LRP or LRE help.

InfluxDB (on-premises)*

2.7.5

See Manage analysis servers in the LRE help. 

Kubernetes (on-premises)*

1.29.4

See Provision Docker hosts automatically in the LRE help.

EKS*

1.29

See Kubernetes configuration settings in the LRE help.

AKS*

1.29.4

See Kubernetes configuration settings in the LRE help.

* Supported in LRE only.

 Back to top

Supported GUI languages

Language Packs enable you to view the LoadRunner user interfaces in your local language.

LRP and LRE support the following languages:

Language

LoadRunner Professional

LoadRunner Enterprise

Chinese – Simplified

ü

ü

French

ü

ü

German

ü

ü

Italian

ü

ü

Japanese

ü

ü

Korean

ü

ü

Spanish

ü

ü

 Back to top

Product Support Lifecycle

Visit the Product Support Lifecycle table for release details and dates. The Product Support Lifecycle policy defines the level of support OpenText provides for each product version.

 Back to top

 

© 2024 Open Text