Use LoadRunner Enterprise Administration to perform all site, project, and lab administration tasks.
After the LoadRunner Enterprise administrator has configured the site, created projects and users, and set up test resources and assets, users can use LoadRunner Enterprise to schedule and execute tests on remote hosts without requiring further administrator intervention.
This section lists the key administration tasks that can be performed in LoadRunner Enterprise Administration.
Update the Communication Security passphrase on the LoadRunner Enterprise server and hosts. For details, see Update the Communication Security passphrase.
Change the system user on the LoadRunner Enterprise server and hosts. For details, see Change the details of the LoadRunner Enterprise user.
|Project and user management|
|Roles and Permissions||
Protect a project from unauthorized access by assigning each user to one or more roles made up of permissions. For details, see Assign project roles and permissions to users.
|Users||Add new users and define user properties, including changing passwords. For details, see Project and user management.|
Manage your LoadRunner Enterprise projects. This includes adding new domains and projects, modifying project settings, restoring projects, and activating or deactivating projects.
You can also upgrade projects from a previous version to the current LoadRunner Enterprise version. For details, see Manage projects.
|Audit||View a list of changes made to the various test entities and track user login and logout times on the site. For details, see Audit entities and user connections.|
|Host resources and lab management|
|Runs||Manage test runs and view result information for LoadRunner Enterprise tests run across all projects. For details, see Manage test runs.|
Schedule and reserve hosts for manual maintenance work. For details, see Manage timeslots.
|Application Under Test||
Create and modify the pools and machines which host the Application Under Test (AUT) components. For details, see Manage Application Under Test hosts.
|System Health||Track and maintain the health of the system, and schedule automated maintenance tasks to provide constant monitoring of the system's key components. For details, see Maintain system health and Schedule automated maintenance tasks.|
Manage analysis database servers which enhance online graph views and capabilities, and provide data for offline graphs. For details, see Manage analysis servers.
|Orchestration||Configure the orchestrators and load generator images which are used for dynamic provisioning of Dockerized load generators. For details, see Automatic provisioning of Docker hosts.|
Add your external cloud accounts and create and modify the templates used to provision dynamic cloud hosts. For details, see Manage elastic cloud hosts.
Maintain the LoadRunner Enterprise and host licenses. For details, see Manage licenses.
|Servers||Create and manage the various servers in your performance testing environment. For details, see LoadRunner Enterprise servers, and Database server, SMTP server.|
Create alerts to notify users of test start and end times, and when timeslots are idle. For details, see Activate alerts.
Configure the authentication method for LoadRunner Enterprise users and define the project file repository. For details, see Site configuration.
|Dashboard and reports|
Get a top level summary view of LoadRunner Enterprise. For details, see Administration dashboard.
|Usage Reports||Analyze LoadRunner Enterprise site users and resource usage. For details, see Reports.|
Immediately after installing the LoadRunner Enterprise server and hosts, the relevant component's configuration tool opens, prompting you for initial configuration settings. If any parts of the configuration were skipped, you must configure the settings manually before you can start working with LoadRunner Enterprise.
You can perform the configuration by running the configuration tool on the relevant machine, or alternatively by defining the settings manually in LoadRunner Enterprise Administration.
The Database server, LoadRunner Enterprise server, and LoadRunner Enterprise hosts must be installed according to instructions provided in the LoadRunner Enterprise Installation Guide (available from Installation).
Create a LoadRunner Enterprise project
Log onto LoadRunner Enterprise Administration as described in Log on to LoadRunner Enterprise Administration.
On the LoadRunner Enterprise sidebar, select Management > Projects.
On the LoadRunner Enterprise Administration sidebar, select Configuration > Licenses.
Click Add License and add the LoadRunner Enterprise license, and then the host license. For interface details, see View the Licenses page.
On the LoadRunner Enterprise Administration sidebar, select Maintenance > Hosts, and click Create New Host . For details, see Add a host.
After a user session starts, it remains active until the client application specifically issues a disconnect instruction to the server. This instruction forces an immediate termination, or the session "times out" due to inactivity, whichever comes first. You can also customize the number of concurrent logins per user per application.
You configure session timeouts and concurrent login limits in the appsettings.defaults.json configuration file.
Configure session timeouts and concurrent login limits
Navigate to <LoadRunner Enterprise server installation>\LRE_BACKEND\ and open the appsettings.defaults.json file.
In the SessionConfiguration section, modify the timeout values as required:
Setting Description SessionInitialDurationSec
Amount of time, in seconds, after a user logs on to LoadRunner Enterprise, that an idle session can remain active before the session expires, or the session is prolonged.
Default value: 7200 seconds (2 hours)
Amount of time, in seconds, that a session can be prolonged, before the server terminates the session. A session is prolonged when the server detects activity in the browser close to the expiration time.
Default value: 1200 seconds (20 minutes)
Maximum amount of time, in seconds, that a session can continue to be prolonged, before the session is terminated.
Default value: 172800 seconds (2 days)
Amount of time, in seconds, that session data is stored in the cache before it is refreshed from the database.
Default value: 300 seconds (5 minutes)
The concurrent login enforcement rules. Set the maximum number of sessions per user per session type, and define the behavior when this limit is reached.
MaxConcurrentSessions Maximum number of sessions for a specific type. OnLimitHit
Behavior of the concurrency when the concurrent sessions limit is reached. Possible values:
ThrowConcurrencyLimitError: Displays an error in the login screen that the concurrent session limit was reached.
DisconnectOldest: Disconnects the oldest active session that is available for that user.
Configuration that should be assigned to indicate the session type. Possible values:
Session expiration mechanism
This section provides definitions of the session expiration values and how the mechanism works.
Amount of time, in seconds, before the session expires.
The API call checks if
Otherwise the expiration =
|creationTime||The time that the session was created.|
|currTime||The current time.|
You can access the Help Center on the Web, or use a locally installed version of the Help Center (we recommend you use the online help for the most up-to-date content).
For details on how to download and install the local version of the help, see