This guide walks you through the steps to set up the integration between Akamas and Micro Focus LoadRunner Enterprise (LRE).
The following schema illustrates the components and networking connections you need to configure to setup the environment:
The integration relies on InfluxDB acting as external analysis server for LRE.
Once you have an InfluxDB deployment, you can configure it by running the following commands:
#create the admin of your influxdb instance (only for a brand new installation) curl -i -XPOST -G http://localhost:8086/query -data-urlencode "q=CREATE USER admin WITH PASSWORD admin WITH ALL PRIVILEGES" #create a specific admin user for the analysis database, it will be used by Akamas to retrieve the data curl -i -XPOST -G http://localhost:8086/query -u admin:admin -data-urlencode "q=CREATE USER akamasinfluxadmin WITH PASSWORD password" #create the database hosting the analysis data curl -i -XPOST -G http://localhost:8086/query -u akamasinfluxadmin:password -data-urlencode "q=CREATE DATABASE LR2020SP3" #grant on the created database curl -i -XPOST -G http://localhost:8086/query -u akamasinfluxadmin:password -data-urlencode "q=GRANT ALL ON lr2020sp3 TO LR2020SP3" #retention policy settings curl -i -XPOST -G http://localhost:8086/query -u admin:admin -data-urlencode "q=CREATE RETENTION POLICY lr_default_rp ON LR2020SP3 DURATION 1d REPLICATION 1"
Since Akamas will import the LRE analysis data immediately once the execution is ended, there is no need to store data for a longer period of time than 1 day, which is the value set in the last command.
Please take note of the admin user credentials (
password in the example above) as you will need them later in order to configure the external analysis server on LRE.
It is recommended to create a dedicated LRE project to store the scripts and tests that you want to run using Akamas. It is also a good practice to also create a dedicated domain.
This can be done by accessing the administration panel on your LRE installation, whose URL should either look like:
or, in a multitenancy-enabled environment, like:
First, navigate to the
then click on the
Manage domains button, add a domain and fill in the required information:
Second, click on the
Add project button and add a project:
and fill in the required information (make sure to select the correct domain):
Access the administration panel of your LRE installation and navigate to the
Analysis Servers menu:
and then click on the plus button to create a new Analysis Server by filling in the required information:
Make sure that the linked projects section lists the dedicated project you have created in the previous step. This step is required to let LoadRunner publish the performance test metrics to InfluxDB for the selected projects.
It is also recommended to reserve a dedicated user for executing performance tests that you want to run using Akamas.
To create this user please access the administration panel of your LRE installation, then navigate to the Users menu:
then click on the plus button to add a user by filling in the required information:
Please notice that:
As a final step on the LRE environment, you need to retrieve the Test Identifier (ID) and the Test Set associated to the performance tests what will be executed by Akamas.
These test ID and test set can be retrieved from LRE Loadtest panel, which you can access it through a link which looks similar to:
or, for a multitenancy-enabled environment:
You can retrieve the ID by selecting the Test Management menu:
and then clicking on the test that you want to execute: the ID is displayed next to the test name:
You can also retrieve the test set from the test details page: the test set is displayed in the upper right corner of the screen:
At this point your LoadRunner Enterprise is ready to work jointly with Akamas! The next sections will guide you through the steps you need to do on the Akamas side.
The Akamas integration with LRE has been designed so that the most important metrics collected by LRE during a performance test (such as transaction throughput, response time and virtual users) will be imported by Akamas.
Those are typical metrics related to web applications. Akamas comes with a
Web Application optimization pack available OOTB that you can use to create a component in your system. To tell Akamas that you want LoadRunner Enterprise as a source for these metrics, you need to specify the property
loadrunnerenterprise in the component manifest.
Here's an example:
name: webApplication description: web application component componentType: Web Application properties: loadrunnerenterprise: ""
As part of the integration, Akamas can natively gather metrics from LoadRunner Enterprise by collecting the time series from the InfluxDB server you have configured in the previous sections.
To do so, you need to create a telemetry instance. First of all, check whether the telemetry provider for LoadRunnerEnterprise is installed:
Then, create a telemetry instance as follows:
provider: LoadRunnerEnterprise config: address: http://influx.dev.akamas.io port: 8086 username: lr2020sp3 password: password database: LR2020SP3
address: it is the FQDN of the server hosting your InfluxDB instance
port: the port where InfluxDB is running
password: credentials of the InfluxDB schema created in the previous steps
database: the name of the InfluxDB database schema created in the previous steps.
Now it is time for you to define a workflow that leverages the
LoadRunnerEnterprise operator to trigger the execution of a performance test.
Here is an example of a simple workflow that you can use to test your LRE integration. It contains just one task that triggers the execution of the specified performance test on LoadRunner Enterprise:
name: LRE simplest workflow tasks: - name: "LRE test" operator: "LoadRunnerEnterprise" arguments: retries: 0 address: http://lre2020.akamas.io/ username: johndoe password: password domain: akamasdomain project: akamas tenantID: "cf59c1a8-ad3d-4c9a-9222-edadaae7b8b9" testId: 183 testSet: demotestset timeSlot: "30m" verifySSL: false
address: it is the basic address of your LRE farm, where the tenant and any other URL or path parameter has been removed
password: the credentials that you have previously created in the LRE admin panel
project: the domain and the project you have previously created in the LRE admin panel
tenantID: the ID of the tenant your project and user belong to - in case multitenancy is not enabled on your LRE environment, you can skip this parameter or set to the default value, thus
testId: the test ID of the test that will be executed by Akamas (you should have already identified it in the previous steps)
testSet: the test set related to the test specified by testId (you should have already identified it in the previous steps)
timeSlot: it specifies the amount of time that LRE will reserve for running your test, therefore it must be greater or equal of the test duration
verifySSL: a flag to enable or ignore the SSL validation when connecting to LRE APIs - this flag is especially useful if your LRE environment exposes APIs over HTTPs with a self signed certificate.
Congratulations! You have configured all the artifacts required by the Akamas LoadRunner Enterprise integration.
Here are a couple of next steps for you:
© Akamas Spa 2018-present. Akamas and the Akamas logo are registered trademarks of Akamas Spa.