Modify project settings

This topic describes how to modify LoadRunner Enterprise project settings in LoadRunner Enterprise Administration.

View or edit project settings

To view project settings in LoadRunner Enterprise Administration, select Management > Projects. The Projects page is displayed.

To edit project settings, select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.

Projects Page/Project details (Main Details view)

Use these pages to view all your projects and to manage their settings.

Field (A-Z)	Description
Projects page
	Filter. Enables you to filter projects to display only those projects that meet the criteria that you define. For details, see Filter. Alternatively, click the filter box under the column you want to filter, and select a filter (or enter text to filter).
Group by	Enables you to group projects by Tenant, Domain, or Tenant and Domain.
	Export to XLS. Enables exporting information from the projects grid to an Excel file. Data from the grid is saved to an Excel file and downloaded to the Downloads folder of the client user.
	Select Columns. Enables you to determine which fields to display in the grid.
	Refresh. Refreshes the grid so that it displays the most up-to-date information.
Project Details page
<Project details migration status>	The migration status, or a progress bar, is displayed in the top panel of the project details for projects created in LoadRunner Enterprise that have not completed the migration process.
	Migrate Project. Displayed in the right side of the top panel if the project has not been migrated to LoadRunner Enterprise. Click to start the migration process. For details, see Migrate projects to LoadRunner Enterprise.
AUT Pool	The AUT host pool of the project.
Concurrent Run Limit	The maximum number of concurrent test runs allowed within a project.
Deactivation Date	The date on which the project was deactivated.
Description	Displays a description of the project (if added during project creation).
Diagnostics Server	The Diagnostics Server defined for the project.
Domain / Domain Name	The domain in which the project was created.
Host Limit	The total number of hosts (Controller + load generators) reserved for a timeslot may not exceed this limit.
ID / Project ID	The project's ID.
Last Run	The time and date of the last test run in the project.
LRC Project Name	The name of the LoadRunner Cloud project. For details, see Integrate with LoadRunner Cloud.
Migration State	Displays the selected project's migration or upgrade state. It can be one of the following: Not Migrated/Upgraded. The project has not been migrated to LoadRunner Enterprise, or has not been upgraded to the latest LoadRunner Enterprise version. Pending Migration/Upgrade. The project is queued for migration or upgrade. Migrating/Upgrading. Project migration or upgrade is in progress. Completed. The project was successfully created, migrated, or upgraded. Failed. An error occurred during file migration or upgrade, and could not be completed. Check the cause of the error in the project log (see View migration issues). Fix the error, and run the migration process again. For details on migrating projects, see Migrate projects to LoadRunner Enterprise. For details on upgrading projects, see Upgrade projects to the latest LoadRunner Enterprise version.
Mode	Indicates whether the project is versioned or non-versioned.
Pool / Pool Name	The project's host pool.
Post-Run Action	Select the action that is triggered automatically when the test run ends. This does not replace the user privileges, and is not enforced on collate or analyze actions that can be performed by the user from the Test Runs page at a later time. Unrestricted (user-defined). Enables the user to select the post-run action when they start or stop a test, or when they select a timeslot. Do not collate results. Frees the machines immediately after the performance test ends. When the run has finished, the run results are left on the load generators. Collate results. When the run has finished, the run results are collected from all the load generators. This is recommended because collation of results takes only a few minutes, and can prevent loss of or inaccessibility to results in case any of your load generators becomes unavailable. Collate and analyze results. When the run has finished, the run results are collected and analyzed. Data analysis requires some time, depending on the size of the results file. Note: If you set the post-run action to Unrestricted (user-defined) and subsequently change the setting after a user has reserved a timeslot, LoadRunner Enterprise will not enforce or modify the settings in reserved timeslots where it conflicts with the user's post-run action setting. When you set a post-run action other than Unrestricted (user-defined), the selected action will be set as the only option for tests across the project, and users will not be able to change this setting. If you set a post-run action for which a user lacks permissions in LoadRunner Enterprise Administration (for example, you set the post-run action to Collate and analyze results, and the user does not have Analyze permissions), the user is unable to run or reserve a timeslot for the test. In such circumstances, update the user’s permissions in LoadRunner Enterprise Administration, or contact the site administrator. For details on permissions, see the Permission categories. Post-run actions are not applicable for test runs driven by the REST API or Jenkins plugin. They are enforced for tests driven from the user interface only.
Project Name	The name of the project. Click the project name link to display the project's details in the Main Details view.
Project State	Displays the selected project's state. It can be one of the following: Active. The project is currently in the Active state, and users can connect to the project. Inactive. The project is currently in an inactive (unavailable) state, and users cannot connect to the project. For details, see Deactivate and activate a project
Project Unique ID	The project's Unique ID number.
Recurrent Timeslot	Indicates whether the recurrent timeslot reservations are enabled or disabled (default) for the project. For details, see Enable recurring timeslots.
Tenant	Name of the tenant. Note: This field is empty in LoadRunner Enterprise 2020.
VUDs Consumed	The number of VUDs consumed by the project.
VUDs Limit	The maximum number of Virtual User Days (VUDs) a project can run at once. The total number used by all of the project's concurrent performance tests must not exceed this limit.
Vuser Limit	The maximum number of Vusers available to the project.
VuGen Working Mode	The mode to use to upload scripts from VuGen: Runtime Files. Uploads only the necessary files to replay the script correctly. User Defined. Enables users to choose whether to upload runtime setting files only or all files. If you select Runtime Mode, only the .usz file is uploaded to LoadRunner Enterprise. If you select All Files Mode, all available files including thumbnail images are uploaded (the script size is much larger).

View project database settings

The Project Database view enables you to view database settings for your projects.

On the LoadRunner Enterprise Administration sidebar, select Management > Projects.
Select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.

Select the Project Database view to display the following project database settings:

Field	Description
Database Name	The project name, as defined in the database.
Maintenance State	Indicates whether a maintenance task, such as migrating a project, is being performed on this project. Possible values are: Idle. No maintenance is being performed on this project. Corrupted. Maintenance cannot be completed because the project is corrupted. To resume, a backup copy of this project must be restored. Under maintenance task. Maintenance is being performed on this project. For details on maintaining projects, see Migrate projects to LoadRunner Enterprise.
Connection String	String to connect to the project database.
Project Directory	The GUID of the project relative to the project repository root directory. For details on the repository, see View or modify the project repository root path. Note: For a non-migrated project, this field displays the location of the project repository in the ALM file system.

Manage users assigned to a project

You can manage the users assigned to the project from the project user settings.

On the LoadRunner Enterprise Administration sidebar, select Management > Projects.
Select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.
Select the Users view.

Edit the project user settings as required.

Field	Description
Assign Users	Opens the Assign Users dialog box, enabling you to assign users to the project. The users list displays only the users not already assigned to the project. Select the users you want to assign, and click Assign.
Unassign	Enables you to unassign users from the project. For details, see Remove users from a project.
Assign to Role	Opens the Assign Users to Role dialog box, enabling you to assign a role to the selected users. For details, see Assign projects and roles to a user.
User Name	Name of the user assigned to the project (the LoadRunner Enterprise login name).
Full Name	Full name of the user (optional).
Role	Role of the user assigned to the project. You can change the user role by clicking the Role dropdown and selecting a different role.

Note: Before project migration, all users are automatically set with Viewer role. After migration, any TDAdmin users from the ALM project are set with Performance Tester permissions in LoadRunner Enterprise, and the rest are set with Viewer permissions.

Follow VUDs transactions in your projects

You can follow the VUDs transactions in your projects from the VUDs Transactions view.

On the LoadRunner Enterprise Administration sidebar, select Management > Projects.
Select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.

Select the VUDs Transactions view.

The view displays the following VUDs information:

Field	Description
VUDs Transaction ID	The action ID.
Post Date	The date that the transaction occurred.
Action	The VUDs action performed. For details about the possible actions, see VUDs actions.
VUDs Number	The project's VUDs limit.
In use by Run ID	The ID of the test run that is currently running the VUDs.
Updated Pending VUDs	The current number of VUDs that are in the Pending state as a result of the transaction.
Updated in use VUDs	The current number of VUDs that are running as a result of the transaction.
Updated Project Limit	The project's VUDs limit as a result of the transaction.
Responsible	The user, or automated system process responsible for the transaction.

VUDs actions

The following table lists the possible VUDs (Virtual User Day) actions. For details of VUDs, see LoadRunner Enterprise licenses overview.

UI Elements (A - Z)	Description
Allocated	VUDs added to the project's VUDs limit by the administrator.
Deallocated	VUDs removed from the project's VUDs limit by the administrator.
Expired	VUDs removed from the license after their 24 hour active period has ended. Note: VUDs that are involved in a performance test that exceeds 24 hours continue to run until completion before expiring.
Issued	VUDs added to a performance test. Note: All VUDs involved in a performance test are considered to be issued from the start of the test, irrespective of whether they have started running or not. The amount of issued VUDs decreases the project's VUDs limit accordingly. All unused VUDs are returned to the project's VUDs limit at the conclusion of the test.
Pending	VUDs which have completed a test run but are still available for further use as their 24 hour active period has not yet ended.
Refunded	VUDs which were issued but not used in the test. These VUDs are returned to the project's VUDs limit and may be reissued at a later date.
Reused	Running VUDs that are taken from VUDs in the Pending state. Note:LoadRunner Enterprise first reuses VUDs in the Pending state before issuing new VUDs. For example, assume you define a performance test that includes 100 VUDs, where the current project limit is 200, and where 25 VUDs are currently in the Pending state. LoadRunner Enterprise first reuses the 25 Pending VUDs and only issues 75 from the license. The new limit will be 125.

View the project log

You can view details about the project, including creation, migration, and upgrade steps, in the Logs grid.

On the LoadRunner Enterprise Administration sidebar, select Management > Projects.
Select a project from the Projects list (click the link in the Project Name column). The project details page opens in the Main Details view.
Select the Logs view.

The Logs grid displays detailed information about the project, including step name, start and end time, status, and messages.
Click Export to Excel File to export the log data to an Excel file.

For details on troubleshooting project issues, see View migration issues and View upgrade issues.