Administration basics
Use Administration to perform all site, project, and lab administration tasks.
Key tasks
After the OpenText Enterprise Performance Engineering administrator has configured the site, created projects and users, and set up test resources and assets, users can use OpenText Enterprise Performance Engineering to schedule and run tests on remote hosts without requiring further administrator intervention.
This section lists the key administration tasks that can be performed in Administration.
Note: For administration tasks related to OpenText Enterprise Performance Engineering communication security and the OpenText Enterprise Performance Engineering system user, see Secure communication and the system user in the OpenText Enterprise Performance Engineering Installation Guide.
Project and user management | |
![]() |
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. |
![]() |
Add new users and define user properties, including changing passwords. For details, see Project and user management. |
![]() |
Manage your OpenText Enterprise Performance Engineering 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 OpenText Enterprise Performance Engineering version. For details, see Manage projects. |
![]() |
View a list of changes made to the 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 | |
![]() |
|
![]() |
Manage test runs and view result information for OpenText Enterprise Performance Engineering tests run across all projects. For details, see Manage test runs. |
![]() |
Schedule and reserve hosts for manual maintenance work. For details, see Manage timeslots. |
![]() |
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. |
Configuration | |
![]() |
Manage the following integrations:
|
![]() |
Configure the orchestrators and load generator images which are used for dynamic provisioning of Dockerized load generators. For details, see Provision Docker hosts automatically. |
![]() |
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 OpenText Enterprise Performance Engineering and host licenses. For details, see Manage licenses. |
![]() |
Create and manage the servers in your performance testing environment. For details, see Manage 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 users and define the project file repository. For details, see Site configuration. |
Dashboard and reports | |
![]() |
Get a top level summary view of OpenText Enterprise Performance Engineering. For details, see Administration dashboard. |
![]() |
Analyze OpenText Enterprise Performance Engineering site users and system resource usage. For details, see Reports. |
Initial configuration
Immediately after installing the OpenText Enterprise Performance Engineering 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 OpenText Enterprise Performance Engineering.
You can perform the configuration by running the configuration tool on the relevant machine, or alternatively by defining the settings manually in Administration.
-
Prerequisites
The Database server, OpenText Enterprise Performance Engineering server, and OpenText Enterprise Performance Engineering hosts must be installed according to instructions provided in the OpenText Enterprise Performance Engineering Installation Guide (available from Install).
-
Create a OpenText Enterprise Performance Engineering project
-
Log onto Administration as described in Log on to Admin area.
-
On the OpenText Enterprise Performance Engineering sidebar, select Management > Projects.
-
Create your project and configure the limits and other settings for the project. For details, see Create domains and projects and Manage projects.
-
-
Add the OpenText Enterprise Performance Engineering license and the host license
-
On the Administration sidebar, select Configuration > Licenses.
-
Click the Add License button
and add the OpenText Enterprise Performance Engineering license, and then the host license. For interface details, see View the Licenses page.
-
-
Add OpenText Enterprise Performance Engineering hosts to the system
On the Administration sidebar, select Maintenance > Hosts, and click the Add Host button
. For details, see Add a host.
Configure session timeouts and concurrent logins
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.json configuration file.
Configure session timeouts and concurrent login limits
-
Go to <Server_installdir>\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 OpenText Enterprise Performance Engineering, that an idle session can remain active before the session expires, or the session is prolonged.
Default value: 7200 seconds (2 hours)
SessionTimeoutSec 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)
MaxSessionTimeoutSec 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)
KeepSessionInCache 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)
ConcurrencyOptions 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.
Type Configuration that is assigned to indicate the session type. Possible values:
-
Admin
-
User
-
AdminAccessKey
-
UserAccessKey
Example:
Copy code"SessionConfiguration": {
"SessionInitialDurationSec": 7200,
"SessionTimeoutSec": 300,
"MaxSessionTimeoutSec": 172800,
"KeepSessionInCacheSec": 300,
"ConcurrencyOptions": [
{
"MaxConcurrentSessions": 20,
"OnLimitHit": "ThrowConcurrencyLimitError",
"Type": "Admin"
},
{
"MaxConcurrentSessions": 20,
"OnLimitHit": "ThrowConcurrencyLimitError",
"Type": "User"
},
{
"MaxConcurrentSessions": 100,
"OnLimitHit": "ThrowConcurrencyLimitError",
"Type": "AdminAccessKey"
},
{
"MaxConcurrentSessions": 100,
"OnLimitHit": "ThrowConcurrencyLimitError",
"Type": "UserAccessKey"
}
]
} -
Session expiration mechanism
This section provides definitions of the session expiration values and how the mechanism works.
SessionExpiration |
Amount of time, in seconds, before the session expires.
The API call checks if
If Otherwise the expiration = |
creationTime | The time that the session was created. |
currTime | The current time. |
Download Help Center
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
See also: