Cybersecurity
DevOps Cloud
IT Operations Cloud
Introduction:
In LoadRunner Enterprise 2020 SP2 release, we added support for a fully containerized environment deployment.
The environment contains four elements: Database server, LoadRunner Enterprise server, LoadRunner Enterprise host, and a Load Generator.
This article will guide you through the requirements, deployment process, how to access the user interface, and some basic troubleshooting methods.
Requirements:
Before you begin:
The LRE_Docker_SP2.zip consists of three files:
Perform the following:
Setting up the environment:
Digest: sha256:302b44eac54c9bccecb935f0c8ca995406e4b8804a9567be10ce315910d0b172
Status:
Downloaded newer image for performancetesting/custom_mssql:2019
docker.io/performancetesting/custom_mssql:2019
Creating mssql ... done
Creating lgsa ... done
Creating lrhost ... done
Creating lre ... done
Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted
Running Configuration Wizard, wait another five minutes before connecting to LRE !!!
Access the LoadRunner Enterprise Administration site:
Wait about five minutes after setting up the environment before logging onto LoadRunner Enterprise Administration.
1. Open a web browser and type: http://<localhost or hostname or IP>/admin
User name: "sa"
Password: "saqa"
2. Add a Host and LG SA from LoadRunner Enterprise as defined in the Docker compose file.
In the attached docker-compose.yml file we use Host as "lrhost" and LG as "lgsa":
3. Create a project. For details, see: https://admhelp.microfocus.com/pc/en/2020.2.0/online_help/Content/PC/Manage-Projects.htm
4. (Optional) Install licenses, For details, see : https://admhelp.microfocus.com/pc/en/2020.2.0/online_help/Content/PC/Manage-Licensing.htm
Access the LoadRunner Enterprise application site (formerly MyPC):
Basic troubleshooting within containers:
For troubleshooting container issues access them by running the following from an elevated PowerShell:
docker exec -it <container name or id> powershell
Status Name DisplayName
------ ---- -----------
Running LoadRunner Aler... LoadRunner Alerts Service
Running LoadRunner Back... LoadRunner Backend Service
Running LoadRunner Data... LoadRunner Data Collection Agent
Running LoadRunner Remo... LoadRunner Remote Management Agent ...
2. In the LRE container verify that IIS has started.
From PowerShell run:
Get-IISSite "Default Web Site"
Name ID State Physical Path Bindings
---- -- ----- ------------- --------
Default Web Site 1 Started %SystemDrive%\inetpub\wwwroot http *:80:
3. In the LRE container, verify in the Configuration Wizard log that schemas were created and
services were installed.
Open an interactive session to the LRE container and run:
type C:\PC_Server\orchidtmp\Configuration\configurationWizardLog_pcs.txt
4. Check the LREcore log from the LRE container.
From PowerShell run:
more C:\PC_Server\orchidtmp\LTLogger\LRECore.API\log.txt
5. Check w3wp log from the LRE container.
From PowerShell run:
more C:\PC_Server\orchidtmp\LTLogger\w3wp\log.txt
6. Check the services are running on the host container:
Get-Service -Name "LoadRunner*"
Status Name DisplayName
------ ---- -----------
Running LoadRunner **bleep**... LoadRunner Analytics Service
Running LoadRunner Data... LoadRunner Data Collection Agent
Running LoadRunner Data... LoadRunner Data Service
Running LoadRunner Load... LoadRunner Load Testing Service
Running LoadRunner Remo... LoadRunner Remote Management Agent ...
Running LoadRunnerAgent LoadRunner Agent Service
7. If you have issues to add a host, check the logs on the host.
From PowerShell run:
more C:\PC_Host\orchidtmp\LTLogger\LTOPSvc\log.txt
8. Verify that the Load Generator services are running.
Run from PowerShell :
Get-Service -Name "LoadRunner*"
Status Name DisplayName
------ ---- -----------
Running LoadRunner Remo... LoadRunner Remote Management Agent ...
Running LoadRunnerAgent LoadRunner Agent Service