LoadRunner Enterprise servers

This topic describes how to manage the LoadRunner Enterprise server and to check its status.

Note: You currently cannot manage more than one LoadRunner Enterprise server in LoadRunner Enterprise Administration.

Change server settings

A site administrator can change the status of the LoadRunner Enterprise server, and update the internal and external server URL.

To change LoadRunner Enterprise server settings:

  1. In LoadRunner Enterprise Administration, select Configuration > Servers and click the LoadRunner Enterprise tab.

  2. Click the LoadRunner Enterprise server name link in the grid to open the server details page.

  3. In the Main details tab, perform the following:

    1. Select the LoadRunner Enterprise server status:

      • Non-Operational. Select when performing a maintenance task to prevent users accessing the system.

      • Operational. Select after maintenance is complete, so that LoadRunner Enterprise and other LoadRunner Enterprise components can access the LoadRunner Enterprise server.

    2. Change the internal and external URL as required:

      • Internal URL. The URL is used for all internal communication between the LoadRunner Enterprise server and hosts, such as performing system health checks.

      • External URL. The URL is used to connect to the LoadRunner Enterprise server from an external source. This is used, for example, if the environment is configured with a load balancer, or if the internal URL is not directly accessible.

        Note: For SSL connectivity, add a LoadRunner Enterprise server using the following format for the external URL:

        https://<LRE_server>

  4. Click Save to save your changes.

Back to top

Check server

This task explains how to monitor LoadRunner Enterprise server status.

  1. In LoadRunner Enterprise Administration, select Configuration > Servers and click the LoadRunner Enterprise tab.

  2. Select the LoadRunner Enterprise server in the grid, and click the Check Server button .

    The Check Server dialog box opens, and displays whether the last configuration, connectivity, performance, and installation check passed or failed.

Back to top

Export server details to Excel

This task describes how to export information displayed in the LoadRunner Enterprise Servers grid to an Excel file.

  1. In LoadRunner Enterprise Administration, select Configuration > Servers and click the LoadRunner Enterprise tab.

  2. Click the Export to XLS button Export to Excel button. Data from the grid is saved to an Excel file and downloaded to the Downloads folder of the client user.

Back to top

Kill a server process

This task explains how to kill a LoadRunner Enterprise server process.

  1. In LoadRunner Enterprise Administration, select Configuration > Servers and click the LoadRunner Enterprise tab.

  2. Under the Name column, click a server name, and then click the Processes tab.

  3. Select the process you want to end in the grid, and click the Kill Process button .

    Click the Refresh button Refresh button to refresh the grid so that it displays the most up-to-date list of processes.

    Note:  

    • To perform a Get Processes or Kill Processes action, the server requires a public key. For details, see Installation.

    • A user with Viewer permissions can end the selected process.

Back to top

View server details, events, processes, and status

This task explains how to view or edit LoadRunner Enterprise server details, including events, processes and server status.

  1. In LoadRunner Enterprise Administration, select Configuration > Servers and click the LoadRunner Enterprise tab.

  2. In the Name column, click the server name.

    Use the following tabs to view or edit server details:

    UI Elements

    Description

    Main Details

    By default, the Main Details view is displayed, which provides a description of the LoadRunner Enterprise server, external and internal URL, and whether the last configuration, connectivity, performance, and installation check passed or failed.

    Note: The LoadRunner Enterprise node that performs the server check must resolved the Internal and External URLs of the selected server.

    Processes

    Displays the following detailed information about the processes and resource usage of the selected server:

    • Name. The name of the process.

    • PID. The process ID.

    • Processor Time (%). The percentage of processor time used by the process.

    • Memory Usage (KBytes). The amount of memory (in kilobytes) used by the process.

    • Elapsed Time (d.hh:mm:ss). The amount of elapsed time since the start of the process, where d is the number of days and hh:mm:ss is the number of hours, minutes, and seconds that have elapsed.

    • Kill Process. For details on killing a process, see Kill a server process.

    Note: This tab is unavailable if the connection to the server fails.

    Check Server Status

    Displays the status of each step of the server checks.

    • Name. The name of each step of the server check.

    • Category. The areas in which the Check Server feature checks the server: Configuration, Connectivity, Installation, and Performance.

    • Check. The sub-areas in which the Check Server feature checks the servers.

    • Expected Result. Result expected to result from the server check.

    • Actual Result. Actual value resulting from the server connectivity check.

    • Status. Indicates whether the server check passed or failed.

    • Error. If an error occurred during the check, displays the error.

    • Date. The date the server was checked.

    Note: This tab is unavailable if the connection to the server fails.

    Event Logs

    Displays detailed information about the tasks performed on the selected LoadRunner Enterprise server, the action status, and a description of any errors.

    • ID. The event ID.

    • Type. The event type (Info, Warning, Error).

    • Project. The project in which the event occurred.

    • Time. The date and time the event was logged.

    • Description. A description of the event.

    • Responsible. The user, or automated system process responsible for the event.

    • Action. The category of action where the event occurred. For example, Create Server.

Back to top