Administration basics

Use Administration to perform all site, project, and lab administration tasks.

Key tasks

After the administrator has configured the site, created projects and users, and set up test resources and assets, users can schedule and run tests on remote hosts without requiring further administrator intervention.

This section lists the key administration tasks that can be performed.

Note: For administration tasks related to communication security and the system user, see Secure communication and the system user in the Installation guide (available from Install).

Project and user management

Menu item Description
Roles and permissions 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.
Projects Projects

Manage your 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 version. For details, see Manage projects.
Audits Audit 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

Menu item Description
Hosts

  • Host. Create and modify the testing hosts that are used to run server-side tests. For details, see Manage hosts.

  • Pools. Create and modify pools of testing hosts. Host pools are assigned to projects. For details, see Manage host pools.

  • Locations. Define the locations which can be assigned to testing hosts. For details, see Manage host locations.

  • MI Listeners. Create and modify MI Listeners, which enable you to run performance tests across a firewall. For details, see Specify MI Listeners.
Runs Manage test runs and view result information for performance tests run across all projects. For details, see Manage test runs.
Timeslots

Schedule and reserve hosts for manual maintenance work. For details, see Manage timeslots.
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.

Configuration

Menu item Description
Integrations Integrations

Manage the following integrations:

  • Analysis servers to enhance online graph views and capabilities, and provide data for offline graphs. For details, see Manage analysis servers.

  • Disruption providers which provide simulated attacks on your services and environments. For details, see Chaos testing.
Orchestration Orchestration Configure the orchestrators and load generator images which are used for dynamic provisioning of Dockerized load generators. For details, see Provision Docker hosts automatically.
Cloud button Cloud

Add your external cloud accounts and create and modify the templates used to provision dynamic cloud hosts. For details, see Manage elastic cloud hosts.
Licenses Licenses

Maintain the server and host licenses. For details, see Manage licenses.
Servers Servers Create and manage the servers in your performance testing environment. For details, see Manage servers, and Database server, SMTP server.
Alerts Alerts

Create alerts to notify users of test start and end times, and when timeslots are idle. For details, see Activate alerts.
Site configuration Site Configuration

Configure the authentication method for users and define the project file repository. For details, see Site configuration.

Dashboard and reports

Menu item Description
Dashboard

Provides a top level summary view. For details, see Administration dashboard.
Reports Analyze site users and system resource usage. For details, see Reports.

Back to top

Initial configuration

Immediately after installing the 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.

You can perform the configuration by running the configuration tool on the relevant machine, or alternatively by defining the settings manually.

  1. Prerequisites

    The Database server and the OpenText Enterprise Performance Engineering server and hosts must be installed according to instructions in the Installation Guide (available from Install).

  1. Create a project

    1. Sign in to Administration as described in Sign in to Admin area.

    2. Select Management > Projects.

    3. Create your project and configure the limits and other settings for the project. For details, see Create domains and projects and Manage projects.

  1. Add the server and host licenses

    1. Select Configuration > Licenses.

    2. Click the Add License button Add button and add the server and host licenses. For interface details, see View the Licenses page.

  1. Add hosts to the system

    Select Maintenance > Hosts, and click the Add Host button Add button. For details, see Add a host.

Back to top

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

  1. Go to <Server_installdir>\LRE_BACKEND\ and open the appsettings.defaults.json file.

  2. In the SessionConfiguration section, modify the timeout values as required.

    Setting Description
    SessionInitialDurationSec

    Amount of time, in seconds, after a user logs on, 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.

SessionExpiration = creationTime + SessionInitialDurationSec.

The API call checks if currTime + SessionTimeoutSec (prolongBy) is greater than SessionExpiration. If it is, the session is prolonged as follows:

newExpiration = SessionExpiration + SessionTimeoutSec (prolongBy)

If newExpiration > maxTimeout then the expiration is maxTimeout.

Otherwise the expiration = newExpiration.
creationTime The time that the session was created.
currTime The current time.

Back to top

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 Download Help Center.

Back to top

See also: