LoadView On-Prem Load Injector Installation & Configuration

The following requirements are fundamental and essential for the proper functioning of On-Prem Load Injectors. While these cover the basics, it’s important to note that certain aspects may be intricately tied to specific security policies on the client’s side. These individual nuances will be addressed on a case-by-case basis through technical support requests, as they pertain to client-specific security considerations.

System Requirements

Hardware requirements:

• 2-core CPU or higher
• 16 GB RAM
• 2 GB Hard Drive space

Software prerequisites:

• On-Prem Add-on enabled in your LoadView account
• Administrative Access for installation and execution
• OS Windows Server 2016 or higher x 64bit
• Chrome (latest release) or Edge (latest release) for On-Prem Agent registration only
• Windows Media Player (for Streaming Media tasks only)
• The Remote Desktop service is enabled on the machine (for browser-based tests only)
• The Always Prompt for Password group policy is set to Not Configured or Is Disabled

Outbound traffic requirements for ASP.NET Core 7.0 Runtime (v7.0.11) – Windows x64

Access to the following resource from the server with the installed On-Prem Agent app:

https://lvbridge.dotcom-monitor.com/privateagentapi/ping/auth/1

Outbound traffic requirements for .NET 7.0 Desktop Runtime (v7.0.11) – Windows x64

Access to the following resources from the server with installed On-Prem Agent app:

The addresses should return a web service page:
https://privateagentcontroller.dotcom-monitor.com/PrivateAgentController/RemoteConfigurationService.svc
https://privateagentcontroller2.dotcom-monitor.com/PrivateAgentController/RemoteConfigurationService.svc
The addresses should return a blank page:
https://privateagentcontroller.dotcom-monitor.com/PrivateAgentWebProxy/entrypoint.wproxy
https://privateagentcontroller2.dotcom-monitor.com/PrivateAgentWebProxy/entrypoint.wproxy

Installation Using The Setup Wizard

Configuring On-Prem Load Injector in LoadView

To connect an On-Prem Load Injector installed on your server to LoadView, first you need to create and configure an injector instance in your LoadView account:

1. Login into your LoadView account and go to Manage > On-Prem Load Injectors
2. Click New Injector on the On-Prem Load Injectors screen.
3. Give a unique name to the injector, provide a region and a description.
4. If you want to limit payload for load testing in real browsers (Web app/ Web page load test), set the Maximum Load Injector Payload for Real Browser Testing parameter.
5. Save changes. The injector name will appear in the list of On-Prem Load Injectors.

Installing On-Prem Load Injector 

To install On-Prem Load Injectors on your server, follow the steps provided below:

1. From Manage > On-Prem Load Injectors, click Download Installer.

3. Run the installer and follow the steps of the On-Prem setup wizard.

4. Finish On-Prem Load Injector setup and register the injector by logging in into your Dotcom-Monitor account. Registrator runs several prerequisite checks before registering the OnPrem Agent service with LoadView. If any prerequisite checks failed, please consult the On-Prem Agent Troubleshooting article for troubleshooting.

5. To connect the injector to your account, once logged in successfully, select an injector name from the list of the On-Prem Injectors created in your LoadView account.

Silent Install

The On-Prem Load Injector supports command-line installation, allowing for a seamless setup process. During the installation, a new On-Prem Load Injector instance is automatically created, configured in your LoadView account, and connected to the injector on your server. By following the instructions in this section, you can efficiently deploy the On-Prem Load Injector in enterprise environments without manual intervention.

Copy the Installation Command

1. On your server, run Command Prompt (cmd) as Administrator.
2. Copy and past the following command in your command line:

OnPremAgentSetup.msi REGISTRATORCMD="-autoinstall -authtoken=<UID>" /qb

Create Your Auth Token

To proceed with the installation, you need to replace ‘<UID>‘ in the -authtoken parameter with your actual authentication token. To do this:

1. Log in to the LoadView account.
2. In LoadView, create an integration UID, which will be used as your auth token, under Manage> Integrations > Add Integration > Load Testing Web API.
3. Click Create Integration and copy the Load Testing Web API Unique Identifier from the Integration UIDs list.
4. Replace ‘<UID>‘ in the command with the Unique Identifier you just copied. Your command should look like on the example below.

Run the Command

Press Enter to run the command. The installation process will begin and the agent will be automatically registered in LoadView.

Custom On-Prem Load Injector Configuration & Proxy Settings

If you want to use proxy in load testing and specify custom On-Prem Load Injector settings upon registration in LoadView, to the command line, add the – configfile parameter followed by a config file path :

OnPremAgentSetup.msi REGISTRATORCMD="-autoinstall -authtoken=8E0999933D6474EBC91BC596B92B2EE -configfile=<ConfigFilePath>.config" /qb

Replace ‘<ConfigFilePath>‘ in the -configfile parameter with a full path to the config file. Use the template below to create your On-Prem Load Injector configuration file.

{
  "ClientData": {
    "BrowserInjectorsCount": N,
    "Region": "RegionName"
  },
    "ProxySettings": {
    "DetectAutomatically": false,
    "UseConfigurationScript": false,
    "AddressConfigurationScript": "",
    "UseProxyServer": false,
    "ProxyServerAddress": "x.x.x.x",
    "ProxyServerPort": "xxxx",
    "NoProxyFor": "",
    "BypassProxyForLocalAddress": false
  },
  "AgentSettings": {
    "Name": "AgentName",
    "Description": "AgentDescription",
     }
}

Centralized Installation

Centralized installation of On-Prem Agent across multiple servers can be implemented with various group deployment tools. As an example, you can use our lightweight PowerShell script for installing the agent on specific servers within the Active Directory domain.

Note that the script must be run with an account that has administrator rights on the servers on which you want to install the agent.

param ([Parameter(ValueFromRemainingArguments=$true)][String[]]$servers)

$script = 
    {
    $fullPathToInstaller = $env:TEMP + "\OnPremAgentSetup.msi"
    start-process $fullPathToInstaller -ArgumentList 'REGISTRATORCMD=" -autoinstall -authtoken=8E049B6B64D6474EBC91BC596B92B2EE" /log OnPremLog.txt /qn' -Wait
    }

$installerFileName = "OnPremAgentSetup.msi"
$fullPathToInstaller = $PSScriptRoot + "\" + "$installerFileName"

foreach ($s in $servers)
{
$s
$tempFolder = Invoke-Command -ComputerName $s -ScriptBlock {$env:TEMP}
$DestComputerSession = New-PSSession -ComputerName $s
Copy-Item $fullPathToInstaller -Destination $tempFolder -ToSession $DestComputerSession -Force
Invoke-Command -ScriptBlock $script -Session $DestComputerSession
Remove-PSSession -Session $DestComputerSession
}

Enabling On-Prem Regions For Departments

If you have Departments under your LoadView parent account, you can allow departments to run load tests using On-Prem regions.

To enable access to specific On-Prem regions and set a limit on the number of on-premises load tests for a department, go to your Account settings > Departments and configure the corresponding settings in the Load Testing Limits section.