Why do I need to use the LoadView On-site Agent?
Sometimes, it’s necessary to test a website that is not accessible from the public Internet. Dotcom-Monitor provides two options to do this.
First, you can whitelist LoadView Static Proxy IPs to allow traffic from LoadView in a company network. Although it is a simple way to implement load testing behind a firewall, it may be inappropriate to open the company’s firewall due to security reasons.
If whitelisting of the Static Proxy IP range is not allowed by your security policies, we provide another secure option: load testing from within your local network with LoadView On-site Agent. The LoadView On-site Agent can be installed on a dedicated Windows Server inside the same network as the target website.
Using the On-site Agent shouldn’t require you to open your firewall for incoming traffic.
How it works
Once the On-site Agent has been configured, it sends outgoing requests to Dotcom-Monitor Service to check if any load tests were started for the corresponding target website and the load test configuration. Once the test configuration has been received by the On-site Agent, it initiates multiple connections to Load Injector Servers (LIs) from within the local network using port 443. LIs use the same connections to send load testing data to On-site Agent. Thus, all load testing traffic to the target will be sent via the On-site Agent from the company network.
The On-site Agents can be installed and used to execute HTTP, web application, and web page tests.
On-site Agent capacity is limited by two factors: the number of virtual users and the number of load tests per On-site Agent.
The On-site Agent can run a maximum of 3 load tests at a time regardless of the type of the load tests.
Generally, the On-site Agent limitations for an average website are:
- Browser-based test: 50 virtual users per agent
- HTTP-based test: 1000 virtual users per agent
Let’s say you need to simulate 100 virtual users on the target website, then you need to leverage at least two On-site Agents for the test.
This guideline walks you through all steps required to prepare the installation, execute the setup, and configure your test scenario to use the LoadView On-site Agent.
- 2-core CPU or higher
- 8 GB RAM
- 1 GB Hard Drive space
- OS Windows 10, Windows Server 2012 or higher x 64bit
- .NET Framework 4.7
- Administrative Access for installation and execution
Outgoing traffic requirements:
Due to the dynamic nature of the IP addresses of our Load Injector Servers, LoadView On-site Agent must have an outgoing connection to all URLs. If it is not an option, you can open an outgoing connection to the specific cloud region that will be used in load testing. Please check the AWS and Azure online resources for an IP range of the required cloud region.
In addition, make sure that your LoadView On-site Agent has access to:
- https://userauth.dotcom-monitor.com/ – for SSO login if required
To make sure that access to https://privateagentcontroller.dotcom-monitor.com is allowed check the following URLs:
- https://privateagentcontroller.dotcom-monitor.com/PrivateAgentWebProxy/entrypoint.wproxy – must return a blank page
- https://privateagentcontroller.dotcom-monitor.com/PrivateAgentController/RemoteConfigurationService.svc – must return a web service page
Preparation of your LoadView On-site Agent Installation
We highly recommend using a dedicated Windows Server for the agent installation. Depending on the test scenario, the load can be high and can have an impact on the CPU or memory utilization of this server.
Follow all preparation steps below once you’ve selected your LoadView On-site Agent server:
Step Details 1 Open Server Manager Click the Server Manager icon on the desktop. 2 Click Add roles and features on the Server Manager Dashboard. 3 In the Add Roles and Features Wizard, navigate through tabs to the Features tab. 4 Select .Net Framework 4.7 Features Installed and all enclosed items. 5 Click Install. 6 Restart your Windows Server.
Install LoadView On-site Agent on your Server
Once all preparation steps are done, you can install the LoadView On-site Agent software on your server. This section covers all installation steps. Follow those instructions step by step.
Step Details 1 Use an account with Admin Permission You need an account with Admin permission for this LoadView On-site Agent installation. Ask your domain admin to get administrative rights on your Windows Server. 2 Configure LoadView On-site Agent 2.1 Login to your LoadView Account.
2.2 Go to Manage > On-site Agent.
2.3 Click Add Agent.
2.4 Specify a descriptive name that is recognizable in a list of other LoadView On-site Agents. Optionally, fill in the Description field.
2.5 Adjust LoadView On-site Agent options, if necessary, and click the Add button.
A new LoadView On-site Agent item will be displayed in the list of LoadView On-site Agents.
3 Setup LoadView On-site Agent 3.1 Login to your Windows Server (with Admin Account).
3.2 Start a browser on your Windows Server.
3.3 Login to your LoadView Account.
3.4 Go to Manage > On-site Agent.
3.5 Click Download Agent. It will bring you to the Tools page.
If the Download LoadView On-site Agent button is disabled, please contact the Dotcom-Monitor support team.
3.6 On the Tools page, click Download on the LoadView On-site Agent Installer panel.
3.7 Run the installer after it has been downloaded.
3.8 Follow the steps of the Setup Wizard by clicking Next.
Accept the terms in the license agreement and confirm or change the destination folder.
3.10 To finish the installation process, click Install and Finish.
3.14 In the LoadView On-site Agent Registrator dialog, provide your Dotcom-Monitor account name and password and click Continue.
3.15 Choose the existed LoadView On-site Agent item in the list to associate the installed agent with and click Continue.
3.16 Review details of the LoadView On-site Agent Configuration, and then click Continue.
Registration of LoadView On-site Agent will take a few minutes.
3.17 If successful, click Close in the corresponding dialog.
4 Restart your Windows Server In some cases, the LoadView On-site Agent can’t be used without a restart, so it’s recommended to restart your Windows Server.
If the machine that the On-site Agent is installed on requires a proxy to connect to the internet, you can set it up during the agent registration.
You can update the proxy settings of the On-site Agent by launching the On-site Agent Version Manager from your start menu under the Dotcom-Monitor folder.
If you do not know your proxy settings, you can find the info by opening up internet explorer or chrome and selecting internet options. Select the Connections tab and go to LAN Settings. From here you can enter a Proxy IP address and Port.