Share this page

# Create domains and projects

You can create domains and projects in Administration.

In this topic:

## About creating domains and projects

As a project administrator, you control access to a project by defining the users who can access the project, and by determining the types of tasks each user can perform by assigning roles.

To start working, you need to create a domain and a project. A domain contains a group of related projects and assists you in organizing and managing a large number of projects. A project collects and stores data relevant to the application management process. For details, see Create a domain and Create a project.

You can also create a project by copying the contents of an existing project. During the process, you can choose which attributes (resources and configurations) you want to copy from the project. For details, Create a project from an existing project.

If your deployment uses an Oracle database server, you can create a project with a custom Oracle user. For details, Create a project with a custom Oracle user.

After creating a project, you can add and remove users from the project.

Back to top

## Create a domain

This section describes how to create a new domain.

To create a new domain:

1. In Administration, select Management > Projects.

2. Click the Manage Domains button . The Manage Domains dialog box opens.

3. Click the Add Domain button , enter a Domain Name, and then click Save. The new domain is added to the Projects list in alphabetical order.

Back to top

## Create a project

This section describes how to create a new project.

To create a new project:

1. In Administration, select Management > Projects.

2. Click the Add Project button . The Create Project page opens.

3. Type a name for your project in the Project Name box.

   Note: The project name cannot be longer than 30 characters and can only include letters, digits, and underscores. It cannot include special characters, non-English characters, or empty spaces. Avoid using a string that could be interpreted as a date format, for example: NOV22 or NOV-22-2023.

4. Select the domain in which you want to create the project from the Domain Name list, or click the Manage Domains button , and create a new domain to which to add the project. For details, see Create a domain.

5. The Mode field indicates whether version control is enabled for the project: Versioned or Non Versioned.

   Note: This field is inactive because Version control is not available in this release of OpenText Enterprise Performance Engineering.

6. (Optional) Enter a description of the project.

7. In the Main details tab, select the host pool to use for the project in the Pool field. For details, see Manage host pools.

8. Set the project limits.

   Project Limits | Description
   --- | ---
   Vuser Limit | Specify the maximum number of Vusers available to the project.
   Concurrent Run Limit | The maximum number of concurrent test runs allowed within a project.
   Host Limit | The total number of hosts (Controller + load generators) reserved for a timeslot may not exceed this limit.
   VUFDs Limit | The maximum number of Virtual User Flex Days (VUFDs) a project can run at once. The total number used by all of the project's concurrent performance tests must not exceed this limit.

9. Select the mode to use to upload VuGen scripts.

   VuGen Working Mode | Description
   --- | ---
   User Defined | Enables users to choose whether to upload all files or runtime setting files only. If you select Runtime Mode, only the .usz file is uploaded. If you select All Files Mode, all available files including thumbnail images are uploaded (the script size is much larger).
   Runtime Files | Uploads only the necessary files to replay the script correctly.

10. Select the action that is triggered automatically when the test run ends. This does not replace the user permissions, 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.

    Post-Run Action | Description
    --- | ---
    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. Note: If you set the post-run action to Unrestricted (user-defined) and subsequently change the setting after a user has reserved a timeslot, the settings in reserved timeslots where it conflicts with the user's post-run action setting are not enforced or modified.
    Do not collate | Frees the machines immediately after the performance test ends. When the run has finished, the run results remain on the load generators.
    Collate results (Recommended because result collation only takes a few minutes, but can prevent loss of or inaccessibility to results in case any of your load generators becomes unavailable.) | When the run has finished, the run results are collected from all the load generators. Select an option for collating the run results: At end of test. This prompts automatic collation on completion of the run (default setting). During test run. The raw data is collated during the course of the test run. This reduces the time required to collate all data at the end of the run. The log and NV data is always collated at the end of the test, not during runtime.
    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. Select an option for collating the run results: At end of test. This prompts automatic collation on completion of the run (default setting). During test run. The raw data is collated during the course of the test run. This reduces the time required to collate all data at the end of the run. The log and NV data is always collated at the end of the test, not during runtime.

    Note:

    - When you set a post-run action other than Unrestricted (user-defined), the selected action is set as the only option for tests across the project, and users cannot change this setting.

    - If you set a post-run action for which a user lacks permissions in 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 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 plug-in. They are enforced for tests driven from the UI only.

11. In the Recurrent Timeslot field, set the recurrent timeslot reservations option for the project: Enabled or Disabled (default). For details, see Enable recurring timeslots.

12. If your deployment uses an Oracle database server, the Database Creation Mode field is displayed, enabling you to create a project with a custom Oracle user. For details, see Create a project with a custom Oracle user.

    If you prefer to use the default user instead of a custom Oracle user, change the Database setting to Default, and click Save.

13. Select the Users tab and click the Assign Users button . The Assign Users dialog box opens and displays the users not already assigned to the project. Select the users you want to assign, and click Assign.

    You can also assign roles to users, and remove users from projects using this tab. For details, see Manage users assigned to a project.

14. Click Save to create the new project. After the project is generated it is added to the Projects list in the `Active` state.

Back to top

## Create a project from an existing project

You can create a new project by copying the contents of an existing project.

1. In Administration, select Management > Projects.

2. In the Add Project list, select Create project from another project.

3. Enter a name for your new project in the New Project Name box.

   Note: The project name cannot be longer than 30 characters and can include only letters, digits, and underscores (it cannot include special characters, non-English characters, or empty spaces).

4. Select the domain in which you want to create the project from the Domain Name list, or click the Manage Domains button , and create a new domain to which to add the project. For details, see Create a domain.

5. In the Based on Project section, select the domain and project you want to copy.

6. In the Copy Available Assets section, select the test assets you want to copy.

   - Resources: Enables you to include test and scripts, test runs, trend reports, monitors (including monitors over a firewall) and analysis templates.

   - Configuration: Enables you to include users and user roles.

   Note:

   - Due to hidden dependencies, you cannot select Runs without selecting Test and Scripts, and you cannot select Trend Reports without selecting Test and Scripts and Runs.

   - User credentials are also copied when copying monitors to a new project.

7. Click Continue. Details of the project are displayed in the Main Details tab. You can modify the project settings and assign users as required. For details, see View or edit project settings and Manage users assigned to a project.

8. Click Save to create the new project. After the project has been copied it is added to the Projects list in the `Active` state.

Notes and limitations

- Timeslot information is not copied from the original project.

- Since not all result data associated with the original project is copied, you might encounter the following message in the Test Runs module: "Run data could not be found. It might have been purged. Please contact your administrator to increase the disk quota on the Controller machine.” You can ignore this message.

  As a consequence, Collate and analyze results might not work on specific runs.

Back to top

## Create a project with a custom Oracle user

If your deployment uses an Oracle database, you can create a project with a custom Oracle user.

There are two ways to create a project with a custom Oracle user.

Option | Description
--- | ---
Automatic | A new Oracle user is automatically created to hold the project schema if it has an administrative Oracle user with the permissions to do so. The Oracle user requires either a DBA role or permissions allowing it to create users and allocate permissions to them. Note: Since most organizations control or restrict the level of access to the database (and don't want applications to be able to create users in their database servers), these organizations are unlikely to provide an administrative user with this level of permissions.
Created by DBA | Your DBA can create a new custom Oracle user for each project that you want to add (with the permissions mentioned above). You must then provide this user when creating the project, either in Administration or using the REST API.

Step 1: Create a custom Oracle user on the Oracle server

Note: Skip to step 2 if you are creating a project using the default user.

Ask your DBA to create a new custom Oracle user on the Oracle database server.

The new Oracle user, which must have either a DBA role or permissions allowing it to create users and allocate permissions to them, should be based on the following commands:

Copy code

    CREATE USER "<CUSTOM_ORACLE_USER>" IDENTIFIED BY "<CUSTOM_PASSWORD>" DEFAULT TABLESPACE "<TABLESPACE_NAME>" QUOTA UNLIMITED ON "<TABLESPACE_NAME>" TEMPORARY TABLESPACE "<TEMP_TABLESPACE_NAME>";
    GRANT CREATE TRIGGER TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE TRIGGER TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE VIEW TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE SESSION TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE TABLE TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE SEQUENCE TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE PROCEDURE TO "<CUSTOM_ORACLE_USER>";
    GRANT CREATE TYPE TO "<CUSTOM_ORACLE_USER>";

Note: On the Oracle database server, your DBA must replace `<CUSTOM_ORACLE_USER>` with the user you want to create in Oracle, `<TABLESPACE_NAME>` with the tablespace name in use on the Oracle server, and `<TEMP_TABLESPACE_NAME>` with the temporary tablespace in use on the Oracle server.

Guidelines for creating the `<CUSTOM_ORACLE_USER>`:

- The name must be in upper case only.

- It can contain underscores, provided they are not used at the beginning or end of the name.

- It can contain numbers, provided they are not used at the beginning of the name.

Any references to the Oracle user when creating the project in the user interface or in the REST API commands must also comply with these requirements.

Step 2: Provide the custom Oracle user when creating a new project

This step explains how to create a new project and provide the custom Oracle user from the user interface. You can also provide the Oracle user using the REST API. For details, see Create a project in the Administration REST API Guide.

1. In Administration, select Management > Projects, and click the Add Project button .

2. The Create Project page opens and displays the additional database fields listed below. Configure the main details as described in Create a project, and enter the following details for the database server:

   UI Elements | Description
   --- | ---
   Database Creation Mode | Choose an option for creating the Oracle user on your database server: Automatic. Select to create the Oracle user automatically. This is the default setting when the ability to create Oracle users is detected (if the Database Name and Password fields are hidden). Created by DBA. Select to use a custom Oracle user that has been predefined by your DBA. This is the only option available when OpenText Enterprise Performance Engineering detects that it does not have permissions to create an Oracle user.
   Database Name | Enter the name of the custom Oracle user that is used to hold the schema of the project (created by your DBA in the previous step).
   Password | Enter the password of the custom Oracle user that is used to hold the schema of the project (created by your DBA in the previous step).

3. Click Test Connection to check the connection to the database server using the credentials provided.

   Note: If the Oracle user provided was not yet created by the DBA, or is already in use by another project, you cannot create a new project and the Test Connection fails.

4. Click Save to create the new project. An additional validation is performed on the schema of the provided Oracle user (the schema must not contain any tables), and if successful, the project is generated and added to the Projects list.

Update an Oracle user password

To maintain a high level of security and to minimize risk, organizations typically require periodic password changes. When the password of the user that holds the OpenText Enterprise Performance Engineering project schema is modified on the Oracle server, you must update the password of the corresponding Oracle user in Administration.

Tip:

- We recommend changing the user password on the Oracle server shortly before changing it in Administration. If necessary, you can use the REST API command to create a procedure that updates the connection to the database for a specific project almost simultaneously. For details, see Update database connection to a project in the Administration REST API Guide.

- If you update the Oracle user password in Administration before it is changed on the Oracle server, OpenText Enterprise Performance Engineering is unable to connect to the Oracle user that holds the schema. As a result, users cannot sign in to this project. OpenText Enterprise Performance Engineering also tries repeatedly to connect to the Oracle user which might result in the user account being locked. The same occurs if you change the user password on the Oracle server without updating it in Administration.

1. In Administration, select Management > Projects.

2. Select a project on the Oracle database server from the Projects list (click the link in the Project Name column), and then click the Project Database tab.

3. Click Change and enter a new password (the characters are hidden and replaced by asterisks). Re-enter the password.

4. (Optional) Click Test Connection to check the connection to the database server.

   Note: The test connection fails if you use the same Oracle user that has been used by another project.

5. Click Save to save your changes. You can save the updated password even if the test connection fails. However, you cannot sign in to the project until the password has also been updated on the Oracle server.

Remove and restore a project with a custom Oracle user

You can remove and restore a project with a custom Oracle user. To do this, you need to add the password of the Oracle user to the dbid.json file when restoring the file.

1. Prerequisite: When removing a project, make sure that you keep a record of the Oracle user password because it is not stored in the dbid.json file. For details, see Remove a project.

2. Restore access to a project as described in Restore access to a project.

   In step 5 (open the dbid.json file), find the `"DatabasePassword": null,` line, and replace `null` with the password of the Oracle user (in double quotes). If you leave the value as `null`, the default OpenText Enterprise Performance Engineering password is used to restore the project, and the connection to the Oracle server fails.

   Example: `"DatabasePassword": "MyOraclePW",`.

Back to top

See also:

- Manage projects
- Migrate projects
- Understanding the project structure

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: