To install the LoadRunner provider, create a YAML file (called provider.yml in this example) with the definition of the provider:

Then you can install the provider using the Akamas CLI:

The installed provider is shared with all users of your Akamas installation and can monitor many different systems, by configuring appropriate telemetry provider instances.

To create an instance of the LoadRunner provider, build a YAML file (instance.yml in this example) with the definition of the instance:

# LoadRunner Telemetry Provider Instance
provider: LoadRunner
config:
 hostname: cifsserver.mycompany.com
 username: akamas
 password: mypassword
 shareName: akamas_lr_results

Then you can create the instance for the system using the Akamas CLI:

akamas create telemetry-instance instance.yml system

Configuration options

When you create an instance of the LoadRunner provider, you should specify some configuration information to allow the provider to correctly extract and process metrics from LoadRunner.

You can specify configuration information within the config part of the YAML of the instance definition.

Required properties

• hostname: The hostname or IP of the server that hosts the CIFS share where the LoadRunner results have been exported. See LoadRunner operator.

• username: The username and the domain required to access the network share. Supported formats are:

  • username

  • domain\username

  • username@domain

• password: The password required to access the network share

• shareName: The name of the network share as it is exposed by the server

Telemetry instance reference

The following YAML file provides the reference for the definition of a telemetry instance.

provider: LoadRunner # this is an instance of the LoadRunner provider
config:
 hostname: cifsserver.mycompany.com # Share server
 username: user@mycompany
 password: mypassword
 shareName: akamas_lr_results
 pathPrefix:YAML

The following table describes the reference for the config section within the definition of the LoadRunner provider instance:

The LoadRunner provider collects metrics generated by a LoadRunner instance (converted to their JSON format and placed in CIFS network share) and makes them available to Akamas.

Prerequisites

This section provides the minimum requirements that you should match before using the LoadRunner telemetry provider.

Supported versions

• Micro Focus LoadRunner 12.60 or 2020

Network requirements

• The network share is reachable at port 445/TCP

• The network share is reachable at port 139/UDP

Permissions (optional)

• Username, domain (if required), and password of the network share.

• Read permission on the network share.

Supported component types

• Web Application

You can check to see how component-types metrics are extracted by this provider.

Setup the data source

Share a Controller folder

To share a folder on Windows, please follow these steps:

1. Right-click on the folder, then select Properties

2. Go to Sharing tab, then select Advanced Sharing

3. In the opened window, enable Share this folder

4. In the "Share name" textbox type the name of the share. This is the name of the share over the network\
5. Then click on Permissions, then Add

6. In the textbox type the name of the user or the group (with the domain if required) that you want to grant access to the share, then click "OK"\
7. Select the added user (or group) and grant the required permissions\
8. Click OK, OK, and then Close

Mount network share on the controller

1. Open "This PC" from the Start menu, then click on "Map network drive"\
2. In the "Map Network Drive" window, select a suitable drive letter name and enter the remote folder path of the network share that has been given to you by your storage admin (it should be something with the format \\mycompanyshareserver.mycompany\foldername)\
3. Make sure to check "Reconnect at sign-in" and "Connect using different credentials".

4. Click Finish

5. In the "Windows Security" window enter the username (with the domain, if required) and the password for the network share and check "Remember my credentials".

6. Click "OK"

Components configuration

Akamas reasons in terms of a system to be optimized and in terms of parameters and metrics of components of that system. To understand the link between metrics collected from LoadRunner and a specific component, the LoadRunner provider looks up the property loadrunner in the components of a system: