Project repository

This section describes the project repository and how to view the repository root path.

Note: The File Repository tab is not available to Tenant Admin users. For details, see Predefined admin roles.

Project repository overview

The project repository stores all files to be used by all the projects in the system. For example, scripts, run results, .xml files, templates, and attachments.

When you install LoadRunner Enterprise, the installation program creates an empty project repository on the LoadRunner Enterprise server file system, according to the repository root path you entered in the Configuration wizard.

By default, the project repository is located under the root directory. The folder is named by the project's unique ID (GUID), and supports only local path drives (C:\) and UNC paths (such as \\system\Remote Repo). The repository is supported with Azure Files Share via a UNC path. For details, see Understanding the project structure.

Migrating the repository

After installing LoadRunner Enterprise, you can migrate the repository from existing projects to LoadRunner Enterprise.

The repository files are gradually migrated to the new system. In this stage, the files are moved from their old location to their new location. Depending on various factors, such as the size of the repository and the network speed, the file migration may take considerable time.

You can track the file migration status for each project, and troubleshoot any problems that may occur. For details, see View migration issues.

Deleting entities from a project

When you delete an entity that has related folders or files within the project's repository, these related folders and files are deleted from the repository after 7 days as part of the cleanup job.

Back to top

Understanding the project structure

The root folder contains a sub-folder for each project; the name of the folder is the unique ID of the project (GUID).

When a new project is created or migrated, each of the following sub-folders and files is created in the project folder:

  • resources. Contains the analysis template files.

  • results. Contains results for each performance test run.

  • tests. Contains a folder denoted by the test ID, and a sub-folder with attachments (if any) for the test.

  • scripts. Contains a folder for each script, and a sub-folder with attachments (if any) for the script.

  • dbid.json. An initialization file that stores project information required for restoring a connection to a project. This file is only generated after you remove the project; it is not part of the project structure. For details, see Restore access to a project.

Back to top

View the project repository root path

To view the repository root path, in LoadRunner Enterprise Administration, select Configuration > Site Configuration, and click File Repository. The repository root path and description (if any) are displayed.

Back to top

View repository usage for all projects in the system

The file repository usage reports enable you to keep track of file usage and see how much storage space is used for each project in the system.

Tip: To view details of file storage usage at the project level, see View project repository usage.

  1. In LoadRunner Enterprise Administration, select Configuration > Site Configuration, and click File Repository.

  2. The file repository usage reports are displayed:

    File Storage Usage. The pie chart shows the percentage of the total file repository that each project uses.

    File Repository Usage Over Time. The graph shows the file repository usage (scripts, attachments, results, and resources) over time for all projects in the system. You can filter the graph by selecting a start and end date.

Back to top

Notes and limitations

  • We do not recommend that you modify the project file system as this could adversely affect the functioning of your projects.

  • Windows password protected sharing settings might influence the usage of the repository. When password protected sharing is turned on for the repository machine, there is no log record of failure to access the repository.

Back to top

See also: