Integrating LoadRunner Enterprise
Last updated
Last updated
The integration relies on InfluxDB acting as an external analysis server for LoadRunner Enterprise (LRE).
The following schema illustrates the components and networking connections you need to configure to setup the environment:
connection granted between the Akamas server and the LRE server (the one exposing LRE APIs) on port 443 - this connection is used by Akamas to invoke LRE APIs over HTTPs;
bi-directional connection granted between the LRE server (the one exposing LRE APIs) and InfluxDB on port 8086.: this connection is used by LRE to store analysis data into InfluxDB;
connection granted between Akamas server and InfluxDB on port 8086 - this connection is used by Akamas to collect LRE analysis data from InfluxDB.
The following assumes that you have already deployed your InfluxDB instance. For more information on how to deploy an InfluxDB instance. As a reference, please see here for a native deployment or here for a containerized deployment.
Once you have an InfluxDB deployment, you can configure it by running the following commands:
Since Akamas starts importing 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 (akamasinfluxadmin | 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 the following:
or, in a multitenancy-enabled environment, like:
First, navigate to the Projects menu:
then click on the Manage domains button, add a domain and then 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), then click on the Manage domains button, add a domain and then fill in the required information:
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.
Notice: you may want to test that the connection to InfluxDB is working correctly by clicking on the Test connection button.
It is 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:
this user must be associated with the project created before and it must have the Performance tester role
this user does not need to have any special admin privilege
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.
aside positive In the following it is assumed that you already have a test scenario defined in your LRE environment that Akamas will execute as part of an optimization study.
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 by 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 be integrated with Akamas.
To leverage the integration with LoadRunner Enterprise via InfluxDB, a telemetry instance needs to be created on the Akamas side.
First of all, check whether the telemetry provider for LoadRunnerEnterprise is installed:
Then, create a telemetry instance as follows:
where:
address: it is the FQDN of the server hosting your InfluxDB instance
port: the port where InfluxDB is running
username and password: credentials of the InfluxDB schema created in the previous steps
database: the name of the InfluxDB database schema created in the previous steps.
A workflow needs to be created for your specific offline optimization study by leveraging the LoadRunnerEnterprise operator to trigger the execution of a performance test.
The following only represents 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:
where:
address: it is the basic address of your LRE farm, where the tenant and any other URL or path parameter have been removed
username and password: the credentials that you have previously created in the LRE admin panel
domain and 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 fa128c06-5436-413d-9cfa-9f04bb738df3
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.
