Share this page

# Upgrades

This section describes the upgrade process.

In this topic:

## About upgrades

Version 26.1 is a full installation that can be installed over a 2020 or later installation.

To upgrade all components in your installation, follow the installation process as described in Install and configure servers and hosts. The installation process detects the older version, and gives you the option to upgrade.

For silent upgrade, see Installing an upgrade in silent mode.

Before upgrading to a later version

- We recommend creating a backup of your Site Admin and Lab DB schemas before you start to safeguard against any unexpected changes during the upgrade process. For details, see Back up projects.

- If you are upgrading and you have more than one OpenText Enterprise Performance Engineering server installed, you must perform the following on all servers:

  1. Stop IIS, the OpenText Performance Engineering Backend Service, and the OpenText Performance Engineering Alerts Service.

  2. Install the latest version. For details, see Install and configure servers and hosts.

Back to top

## Upgrading to 26.x

This section describes how to upgrade and migrate project data when upgrading from versions 24.1 or later to 26.x, when using an Oracle database for a repository.

To upgrade to version 26.x:

1. Install version 24.3 and run the Configuration wizard.

2. Upgrade any required projects from the Admin Site’s Projects tab.

3. Install version 26.x and perform a standard upgrade via the Configuration wizard.

Note: To upgrade old projects that were not upgraded during the 24.3 stage, install a clean 24.3 environment, import the project, upgrade it to 24.3, and then upgrade it in 26.x using the Configuration wizard.

Upgrading old projects that were not upgraded earlier

This section describes how to upgrade old projects that were not upgraded during the environment upgrade process. These instructions are primarily relevant to customers with a large number of projects that cannot all be upgraded during the environment upgrade step.

Note:

- The following instructions assume that different database servers are used. If you are using the same database server for the intermediate 24.3 environment, you can skip the steps of exporting and importing the project DB schema.

- Database related operations, such as exporting, importing, and manipulating schemas, should be performed by the DBA.

1. Install a separate 24.3 environment. It will be used to upgrade projects that were not upgraded in the Environment Upgrade stage.

2. Remove the project to be upgraded from the up-to-date environment, and save its json file.

3. Export the project's DB schema.

4. Import the DB schema into the DB server of the 24.3 intermediate environment.

5. Restore the project into the 24.3 environment.

6. Upgrade the project in the 24.3 environment. Wait for the operation to complete successfully.

7. Remove the project from the 24.3 environment and save its json file.

8. Export the project's DB schema from the database server of the 24.3 intermediate environment.

9. Import the DB schema into the database server of the up-to-date environment. The original, non-upgraded schema may need to be renamed or dropped prior to importing the upgraded one.

10. Restore the project in the up-to-date environment.

11. Upgrade the project normally.

12. Perform steps 2-11 from the above procedure for every project that you upgraded.

Back to top

## Upgrade tips

Follow these guidelines when performing an upgrade:

- For silent installations and configurations, make sure that the - userinput.xml for all nodes have the same domain and user. The values are case sensitive.

- After an upgrade or after running the server configuration wizard, make sure that the OpenText Enterprise Performance Engineering service user is the same for all nodes on dat\pcs.config and on all hosts dat\LTS.config. The user name is case sensitive.

- After an upgrade, make sure that the OpenText Enterprise Performance Engineering service user is the same user and that case sensitivity is maintained within the <repository>\system_config\appsettings.json file.

- After running the Identity Changer utility, make sure that the OpenText Enterprise Performance Engineering service user is the same, maintaining case sensitivity, in the following files.

  Area | path | file
  --- | --- | ---
  Servers | dat | pcs.config
  Hosts | dat | lts.config
  Repository | system_config | appsettings.json

Back to top

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: