Wilson Mar bio photo

Wilson Mar


Email me Calendar Skype call

LinkedIn Twitter Gitter Instagram Youtube

Github Stackoverflow Pinterest

From the new Micro Focus in AWS cloud and locally

US (English)   Norsk (Norwegian)   Español (Spanish)   Français (French)   Deutsch (German)   Italiano   Português   Estonian   اَلْعَرَبِيَّةُ (Egypt Arabic)   中文 (简体) Chinese (Simplified)   日本語 Japanese   한국어 Korean


This is a hands-on tutorial on the different ways to get your hands on LoadRunner 12.55.

There are different scopes of what is installed on a machine:

  • LoadRunner VuGen” client only for use with Performance Center central web server, which presents collects and displays run results on a web page rather than via Controller and local Analysis.

  • LoadRunner Load Generator” only for call by a separate Controller or Performance Center. This is decribed at https://www.guru99.com/creating-amazon-ec2-instance.html and https://community.saas.hpe.com/t5/LoadRunner-and-Performance/Step-by-step-instructions-to-Provision-Load-Generators-in-the/ba-p/245072#.WaW1-pOGNZo

  • LoadRunner UI” after full install of VuGen, Controller, and Analysis plus VTS and Load Generator on same machine for learning. This is the scope of this document.

Gaspare Marino, HPE Marketing, on August 30, 2017 points to version features in LoadRunner and Performance Center 12.55 to dispel competing vendors painting LoadRunner as a “dinosaur”.

Amazon EC2 LoadRunner UI

  1. Get an Amazon account.
  2. In IAM, setup a different account than your master account used for billing.

  3. Get to EC2 from the AWS Management Console.
  4. Click “Launch Instance”.
  5. Click Community AMIs and type LoadRunner.


  6. Click the 4 results for “loadrunner” on AWS Marketplace.

    LR12.55 CE on Windows 2016

    I have enlisted the help of a company which specialises in the creation of secure/hardened images in AWS EC2. As of September 5, they are creating image:
    “LoadRunner_12-55_CE_Windows-2016x64_50_Users” to contain all components of LoadRunner 12.55 CE (a 50 user license) on a base of Windows 2016 x64.

    This AMI use does not involve additional fees like HPE charges, only Amazon hourly fees. But I gladly take donations to my charity for the many hours of work figuring this out and documenting the steps here.

    I am creating a PowerShell script to load what HPE’s images do not provide:

    • Git for Windows
    • Firefox browser to emulate
    • Community Edition (CE) of Microsoft’s IDE Visual Studio 2017 CE
    • Additional Components for VTS and Visual Studio
    • Server management utilities

    The remainder of this document describes creation and use of this image.

    Let’s begin with use of the image. Futher down this document is a description of steps to use a base image, install, and “rebundle” for your use.

    Skip to ConfigureInstance

    Images from HPE/MicroFocus

    “HPE_LoadRunner_12-53P4_Windows-2012R2x64150_Users…” and
    contains (the older) LoadRunner 12.53 Patch 4 on Windows Server 2012 R2 2012R2 x64.

    PROTIP: Notes from HPE developers is here as part of the Jan 4, 2017 release. This link should really be among AWS EC2 documentation.

    MicroFocus has not gotten around yet to updating this for LoadRunner 12.55 under its name.

    A HP/MicroFocus Performance Center AMI is not offered.

  7. Click Select on the “Free Trial”.

    CAUTION: “Free Trial refers to the 14-day grace period on what Amazon pays HPE/MicroFocus $25 per hour, which means $600 per day or $1,800 per month.

    The expiration date is displayed here.

    CAUTION: The extent it has been “hardened” for security I have not seen documented.

  8. Click Continue.

    Configure Instance

  9. Get to EC2 from the AWS Management Console: https://console.aws.amazon.com/console/home
  10. Login with your credentials.
  11. Select the Region at the upper right. For example, the N. Virginia:


    PROTIP: If you are building a source AMI for AWS Marketplace, the region MUST be in us-east-1 region. AWS Marketplace will take the source AMI and clone for other regions.

  12. Click the blue “Launch Instance” button.
  13. Select a base image: “Microsoft Windows Server 2016 Base” (Data Center Edition). It has a “Microsoft Windows 10” look and feel.

    NOTE: If you were to construct a Load Generator instead, you would instead select “Amazon Linux AMI…”.

  14. If you’re just working on installation, select “t2.micro” because it’s Free tier eligible.

    PROTIP: Select “t2.medium” with 4 GB memory if you’re going to use it to do anything real.

  15. Click Next: Configure Instance Details.
  16. Select a VPC you’ve defined previously. If you haven’t, open another window and do that first.
  17. You don’t need to with this instance. But other instances (such as for IIS servers), scroll down to expand Advanced Details to specify server start-up commands.

  18. Click “Next: Add Storage”. Defaults are for the machine chosen earlier (for t2.micro, 30 GiB, General Purpose SSD, not encrypted).

    PROTIP: Amazon’s current maximum volume size that can be given to a General Purpose volume is 16GB.

  19. Click “Next: Add Tags”.
  20. Click “Add Tag”. In Key, type Name. In Value, type LR1255.01 (or whatever to differentiate rather than “Web Server”).

    PROTIP: This is the name that appears in the EC2 Console, which doesn’t provide much room. So keep it short.

  21. Click “Next: Configure Security Group”.
  22. Use default “Create a new security group” and the random name created.
  23. For Security Group Name, specify RDP port 3389 for use by “Windows Remote Desktop clients”.

    NOTE: Since this is a Windows machine, SSH (via port 22) is not needed.

  24. For its Source, select Anywhere because this is used during training by anyone.

    CAUTION: This setup is not safe to handle corporate or HSI data.

  25. Click Add Rule. For its Type, select HTTP. Leave Port as 80. For its Source, select Anywhere.
  26. Click Add Rule. For its Type, select HTTPS. Leave Port as 443. For its Source, select Anywhere.

    NOTE: The LoadRunner port 54345 does not need to be specified for instances containing both Controller and Load Generator in the same server.

  27. Click “Review and Launch”.
  28. Click “Launch”.
  29. Click OK to the security warning if it appears.

  30. Create a new key pair. (But in Quiklab, Choose an existing one.)
  31. Type a Key Pair Name with a date and your initials, such as

    “HPE_LoadRunner_12-53_P4_Windows-2012x64_50_Users-20171001-wm” for HP


  32. Click Download Key Pair. .pem file. The default is your Downloads folder.
  33. Click OK to the download dialog.
  34. Click Lauch Instances. CAUTION: Charges now begin accumulating..

    NOTE: A “Thank you for subscribing…” email is sent to you from AWS Marketplace <no-reply-aws@amazon.com>.

    PROTIP: Immediately set an hourly alarm 50 minutes from the time stamp on the email. Amazon charges by the hour. So if you stop before the hour is up, you’ll still be charged for the whole hour.

    Other images


    Access server via RDP Windows

    This applies to Windows servers everywhere, not just in the AWS EC2 cloud.

  35. See “Use RDP (Remote Desktop Protocol) clients to access Windows Servers”

    Configure the Windows Instance

  36. Refer to my “Windows 10 client configuration page”.

  37. Click the Windows icon and type enough of server manager for it to appear in the list. Click on it in the list.

  38. Click the File Explorer icon on the Task Bar. Click This PC. Notice the space remaining free:


Stop or Terminate instance

PROTIP: Stopping an instance enables you to change the RAM, and even the instance type to a bigger or smaller machine.

CAUTION: Stopping, then starting an instance re-starts the billing clock such that if you stop and start an instance within the same hour, you will be billed for two hours.

  1. To stop an instance in the EC2 Console, right-click on your instance name:


    If you select Stop of the instance, usage fees will stop. However, the root volume of the instance (EBS volume, also called “Provisioned storage”) is preserved and storage charges will continue to accure. Other devices that are attached to the instance keep on running, accumulating charges.

    You can now make an AMI of the instance just created.

  2. If you select Terminate, you will need to go through the steps to create a new instance.

    Since the .rdp file for the instance downloaded are no longer valid:

  3. Delete the .rdp file from your local machine.
  4. Remove the instance from your RDP client.

Get Sample Scripts

Download Git repository containing bootstrap script:

  1. Open a Git Bash window.
  2. cd to where you add Git repositories:

    cd gits;
    git clone https://github.com/wilsonmar/loadrunner.git --depth=1
    git clone https://github.com/wilsonmar/git-utilities.git --depth=1

Install yourself manually

There are several steps to this:

Download Installers

  1. Invoke the Internet Explorer browser. (Firefox browsers don’t recognize the website’s Download button)
  2. https://software.microfocus.com/en-us/download/loadrunner


    Download CE core installer

  3. Right-Click to Download “Community Edition”.
  4. Click the green Download button for: HPELR_1255_Community_Edition.zip (919 MB)

  5. In general, if you see a pop-up to save your password, just say NO, NEVER.
  6. WARNING: If you press Alt+left for the previous browser page, another download will start.

  7. PROTIP: Click the previous browser tab containing the list of downloads.

    Download Additional Components

  8. Click to Download “Additional Components” (for VSTS). HPELR_1255_Community_Edition_Additional_Components.zip ( MB)

  9. Other links:

    “Useful resources”

    “Tech talks” is still https://community.saas.hpe.com/t5/LoadRunner-Performance-Center/ct-p/sws-LoadRunner

    “HP LoadRunner Help” is https://lrhelp.saas.hpe.com/en/12.55/help/WebHelp/Content/Resources/_TopNav/_TopNav_Home.htm

    Extract Installer Zip files

  10. Double-click to Extract file HPELR_1255_Community_Edition.zip.
  11. Click “Extract” on the menu line. Click “Extract All”. Click “Extract”.
  12. On the Windows Explorer left pane, click “Downloads”.
  13. Right-click on the zip file to Delete it (to recover disk space).

  14. Double-click to Extract file HPELR_1255_Community_Edition_Additional_Components.zip.
  15. Click “Extract” on the menu line. Click “Extract All”. Click “Extract”.
  16. On the Windows Explorer left pane, click “Downloads”.
  17. Right-click on the zip file to Delete it (to recover disk space).

    Invoke Base Installer

  18. On the Windows Explorer left pane, click “Downloads”.
  19. Double-click to open the HPELR_1255_Community_Edition folder.
  20. Right-click on the HPELR_1255_Community_Edition.exe Application to select “Run as Administrator”.
  21. If the UAC appears, click Yes.


  22. If you’re installing into a WorkSpace, change the path from C:\Temp\… to D:\Temp.

  23. In the Installer, click Install.
  24. Click OK to install the Redistributables.


    Installed include C++ 2013.

  25. When the “Welcome to the HPE LoadRunner Setup Wizard” appears, click Next.


  26. When the “End-User License Agreement” dialog appears, check “I accept”.
  27. Uncheck “Participate in VuGen Improvement Program”.


  28. Click Next.
  29. When the “Change destination folder” dialog appears for C:\Program Files (x86)\HPE\LoadRunner\


    PROTIP: The “Program Files (x86)” location means LoadRunner is a 32-bit program.

  30. Click OK.

  31. When the “Ready to Install” dialog appears, click “Install”.

    It will take a while for the Setup Wizard to install LoadRunner.

  32. When the “HPE Authentication Settings” dialog appears, uncheck “Specify a certificate that will be used…”.


  33. Click Next.
  34. When the “Completed the HPE LoadRunner Setup” dialog appears, uncheck “Install HPE Network Virtualization”.


  35. Uncheck “Launch License Utility Tool on Exit”.
  36. Click Finish.

    PROTIP: Do not delete the installer .exe files because they may be needed in the future.

    Manage LoadRunner Icons

  37. Right-click on the Windows “start” icon to select Desktop.

    Notice LoadRunner’s application icons.

    Install VTS Additional

VTS (Virtual Table Server) is a node.js application that runs outside of LoadRunner. Thus, VTS is placed under the HP folder because it can be used by other systems, not just by LoadRunner. VTS enables data to be manipulated outside of LoadRunner scripts running on load generators.


Data can be imported into VTS several ways. CSV (Comma Separated Values) can be imported, perhaps after editing using Excel or other spreadsheet program. External systems can dynamically (during runs) make web services requests to change data in VTS. There is a web page for manual.

#### A) Download from HP Marketplace


#### B) Additional Components

  1. In Windows Explorer, be at your account’s Downloads folder.
  2. Right-click on the HPELR_1255_Community_Edition_Additional_Components.exe Application to select “Run as Administrator”.
  3. If the UAC appears, click Yes.

    Install VTS

  4. Click “Install”. If you are installing in WorSpaces, changd from C:\Temp\\... to <strong>D:</strong>\Temp
  5. Navigate into folder Temp\HPE LoadRunner 12.55 Community Edition\DVD\Additional Components\Virtual Table Service
  6. Right-click on SetupVTS Application and select “Run as Administrator”.
  7. Click Yes to UAC.

  8. Change C:\TempHPE LoadRunner VTS 12.55 to D:\Temp\HPE LoadRunner VTS 12.55 Click Next, then Next.
  9. Check “I accept the terms…”. Click Next. Click Install to C:\ProgramData\HP\VTS\db\data.
  10. Click Install.
  11. Click Finish for a pop-up browser containing a link to http://localhost:4000/
  12. Click Enable.
  13. Enable Access from Script.

  14. Open Windows Explorer to see how much disk space remains.

    Populate VTS with Data

    TODO: Move steps from LoadRunner Tutorial to here:


    Install WebTours

    Since version 12.55, the WebTours sample application has been moved.

  15. Download it from: https://marketplace.microfocus.com/appdelivery/content/web-tours-sample-application
  16. Unzip the WebTours.zip.
  17. Double-click to run “strawberry-perl-
  18. Click the “I accept…”, then Install. Click Yes to UAC. Click Finish.

  19. Extract all files in WebTours.zip.
  20. Open a Run cmd windows. Navigate to the folder.
  21. Type StartServer.bat to invoke the server. Leave it running.
  22. Open a web browser to:


  23. In the browser, bookmark the site.

    Populate VTS



  24. Copy this and paste it in a cmd window:

    echo D:\Users\%USERNAME%\gits\loadrunner\gapi-lr-starter\gapi-lr-starter.usr

    Copy the response to your Clipboard to paste into VuGen

    Alternately, double-click on the file within Windows Explorer.

    PROTIP: The install process enables double-clicking on a .usr file extension to invoke VuGen.

  25. Click the Windows logo at the lower-left corner of the screen.
  26. Click Virtual User Generator.
  27. Maximize the screen by clicking on the button at the upper-left corner.
  28. Click File, Open. Paste the path from above or navigate to open the .usr file.

Get Sample Scripts

  1. In VuGen, click “Version Control”, “Git Options”, “Import from Remote Repository”.


  2. In the “Remote Repository URL”, type the URL to a GitHub repository:



    The dialog automatically obtains the repository name from the URL.

    PROTIP: The default folder for VuGen scripts is:

  3. Click VuGen File, Open, Solution. Select the path above.
  4. Click to open “gapi-lr-starter.usr” in VuGen.

Run sample script

  1. Click Run. Let it finish running.
  2. View the Output pane.

    PROTIP: Get your own Google API Key.

Create a Vuser script in Visual Studio


WARNING: LoadRunner is typically several months behind each Visual Studio release in order to come up with integrations.

  1. Use Windows Explorer to view folder C:\Temp\HPE LoadRunner 12.55 Community Edition\DVD\Additional Components\IDE Add-Ins Dev

    Specific versions of Visual Studio is supported:

    • LRVS2013IDEAddInSetup.exe supports Visual Studio 2013.
    • LRVS2015IDEAddInSetup.exe supports Visual Studio 2015.

    PROTIP: Even if the latest version is not supported, you can still use Visual Studio and LoadRunenr separately.

  2. Install the Visual Studio IDE add-in the version of Microsoft Visual Studio.

In Visual Studio, select the appropriate template from the Installed Templates LoadRunner VB C++ C# .NET Vuser. Visual Studio creates a new project with one class and a template for a Vuser, and the script file, .usr. The template contains three sections, Initialize, Actions, and Terminate.

The following example shows a Visual C# template:

public int Initialize() { // TO DO: Add virtual user’s initialization routines return lr.PASS; }
public int Actions() { // TO DO: Add virtual user’s business process actions return lr.PASS; } public int Terminate() { // TO DO: Add virtual user’s termination routines return lr.PASS; } Add code to the template, in the TODO sections.

Open the Object Browser (View menu). Expand the LoadRunner node (for example Interop.LoadRunner) to see the LoadRunner elements. Add the desired elements to your script, such as transactions, rendezvous points, and messages.

Expand the Toolbar menu, Vuser, and enhance your script with runtime settings and parameters. For more information, see the runtime settings General > Run Logic or the Parameter List Dialog Box.

Use the Vuser menu to replay the script and test its functionality.

Select Vuser > Create Load Scenario, to create a LoadRunner scenario using this .usr file.

You can also build the LoadRunner project as a DLL file, which will be saved in the same folder as the project. You can reference this DLL directly from a LoadRunner scenario.

Wait, there’s more. Click one of these …

This article is one of a series about tuning and performance: