Database server

This topic describes the database server and how to view the properties of the database server that was defined during the installation process.

About the database server

The database server is defined during the LoadRunner Enterprise installation process. For installation details, see the LoadRunner Enterprise Installation Guide (available from Installation).

The database server stores three types of schemas:

  • Site Administration schema. Stores information related to the LoadRunner Enterprise system, such as domains, users, and site parameters. A row exists in this schema for each project you create. Irrespective of how you configure your system, there is always only one Site Administration schema.

  • Lab Management. Stores lab information related to managing performance testing on remote hosts, LoadRunner Enterprise server data, and licenses. There is only one Lab Management schema.

  • Project schemas. Stores project information, such as entity data and user data. A separate schema exists for every project you create.

The schemas can reside on an Oracle, Microsoft SQL, or PostgreSQL database server.

Back to top

View database server properties

This section explains the database server properties that are displayed in LoadRunner Enterprise Administration.

Note: You can modify the database server properties from the LoadRunner Enterprise Configuration wizard. For details, see the LoadRunner Enterprise Installation Guide (available from Installation).

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

  2. The database server details are displayed (read only):

    UI Element Description
    Server Name Name of the database server.

    The type of database server being used: Oracle, Microsoft SQL (using SQL or Windows authentication), or PostgreSQL.

    Oracle Service Name

    (Oracle only)

    The net service name for an Oracle database server found in the local tnsnames.ora file.

    Note: The Oracle Net service name must be in the case as it appears in the tnsnames.ora file.

    Site Admin Schema Name The name of the source Site Admin schema (read only).
    Lab Project Admin Schema Name The name of the source LAB database schema (read only).
    Description Description of the database.
  3. The Database Administration Credentials section displays the name of the administrator user account that is used for creating LoadRunner Enterprise projects on the database server.

    Note: The User name box is unavailable for MS-SQL (Win Auth.) because the login name of the database administrator is the Windows user that is set to run as a service.

  4. The Connection Details section displays the connection option that is being used.

    • Connection string parameters. If selected, the database server name and port number are displayed.

    • Connection String. If selected, the connection string is displayed.

    Note: For an Oracle database, the connection string parameters are grayed out.

Back to top

Change the database administrator and user passwords

You can change the database administrator and user passwords that you configured for the LoadRunner Enterprise server from the Database Passwords Changer utility in the Start menu.

Note: You can use a REST command to change the database user password in the Database Password Changer utility without having to use the user interface. For details, see Update database passwords.

  1. Stop the LoadRunner Backend Service.

  2. Change the database administrator and/or user passwords (according to the required change) on the database server.

  3. Run the Database Passwords Changer utility from the Start menu, and enter the new password for the LoadRunner Enterprise database administrator and/or user.

    Note for Oracle databases only: Changing the username password affects only the LRE_SITE_MANAGEMENT_DB and LRE_SITE_ADMIN_DB user's password.

    For more details on DB Administrator and User credentials, see Configure the connection to the LoadRunner Enterprise database server in the LoadRunner Enterprise Installation Guide (available from Installation).

  4. Upon successful completion of the utility, restart the LoadRunner Backend Service.

Back to top

See also: