Share this page

# Install

This section details the system prerequisites and installation process on both Windows and Linux, as well as the project upgrade process.

In this topic:

## Installation and upgrade

This section provides the following:

- Step-by-step instructions for installation and configuration.

- Step-by-step instructions for upgrading projects from earlier versions.

- Generic installation instructions.

There are many scenarios in which you may need to install OpenText Application Quality Management. The most common installation and upgrade scenarios are covered.

Back to top

## Download

You can download the installation packages from the Software Licenses and Downloads page. It requires a customer service ID, order number, or software serial number for software activations and downloads.

Back to top

## Upgrade versions

The following table describes the latest versions to which you can directly upgrade projects from previous versions.

From versions | Latest version to support direct upgrade
--- | ---
11.0 | 12.2
11.5x | 12.5
12.0 | 15.0
12.2 | 15.5
12.5x | 16.0.x
12.6x | 17.0.x
15.0.x | 24.1
15.5.x | 25.1.x
16.x.x | 26.1
17.x.x | 26.1
24.1.x | 26.1
25.1.x | 26.1

Back to top

## Breaking changes

This section lists the changes you must know before you install or upgrade to the target version.

Version | Changes
--- | ---
16.00 | Send X-XSRF-TOKEN header with all requests Starting from 16.00, after getting authenticated, you should send the X-XSRF-TOKEN header in all your subsequent REST API calls, except for the ones that use the GET HTTP method. Otherwise, you cannot access ALM resources using ALM REST APIs. For details, see "REST API Reference (Core)" on page 1 and "Site Administration REST API Reference" on page 1.

Back to top

## Explore options

You've got plenty of options to plan your ALM future. Upgrade to the latest ALM version, move your ALM environment to SaaS, or switch to the ALM Client Launcher to remove the IE dependency and greatly reduce administration overhead.

For details, see Explore your ALM options.

Back to top

## Printer-friendly guide

The installation guide is also available in PDF: Installation Guide

## Install and upgrade FAQ

Here are some frequently asked questions regarding the installation and upgrade process:

Q: I want to upgrade the Java build or replace Oracle JDK. What should I do to change the Java path on the installed server without reinstalling?

A: Java has been decoupled from the installation starting from 12.6. You should handle the Java installation and upgrade by yourself. After you upgrade Java or replace Oracle JDK with OpenJDK, you should update the MICRO_FOCUS_JAVA_PATH environment variable with the new Java path.

To update the MICRO_FOCUS_JAVA_PATH environment variable:

1. Stop the ALM service.

2. Install the new Java build.

3. If you are using Windows:

1. Open System > Advanced System Settings > Environment Variables > System Variables.

2. Update the MICRO_FOCUS_JAVA_PATH variable with the new Java directory. For example, C:\Program Files\Java\jdk-17.

4. If you are using Linux:

   1. Open the /etc/profile file.

   2. Locate export MICRO_FOCUS_JAVA_PATH, and update the value with the new Java path.

   3. Save the /etc/profile file, and in the current directory, run the source .profile command.

5. Restart the ALM server to apply the changes and clean the server cache.

6. Start the ALM service and validate if the service is running by monitoring the wrapper.log file, which is located in <ALM deployment directory>\log.

Q: Do you have information on how to upgrade to the existing SA schema?

A: Yes, please refer to the MySupport page by clicking on this link How to Upgrade Existing SA Schema.

Q: What are the latest system requirements when upgrading?

A: For a comprehensive list of version system requirements, see Support Matrix.

Q: How long does it take to complete the upgrade?

A: The time it takes to upgrade to ALM depends on many parameters. Examples include number of projects, amount of users, size of each project, amount and size of attachments, hardware resources, network settings, and DB configuration. Therefore, we cannot predict in advance how long it will take to complete the ALM upgrade. To help with your upgrade, we recommend you first perform the ALM upgrade using a staging (testing) environment. This will provide you with a good estimation for the time it may take to perform the upgrade. It will also ensure there won't be blockers when you perform the upgrade on your production environment.

Q: We have a lot of projects planned for the upgrade, and we are planning to use ALM Robot to facilitate this process. Where can I get more information about this tool?

A: See ALM Robot to find all relevant information about ALM Robot.

Q: We have noticed that our current product version contains many Site Parameters set from previous installations. Is there a way we can get their descriptions and applications updated before upgrading to the next version?

A: See Site Parameters.

Q: We have some integrations with other OpenText products. Where we can find the integration supportability documentation?

A: See ALM integrations with other products.

Q: What add-ins or extensions do we have?

A: For the full list of add-ins and extensions, see Tools.

Q: What new functionalities were added to the latest version?

A: See What's new.

Back to top

https://admhelp.microfocus.com Application Quality Management 8942
Tips to improve your search results... OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help Center OpenText™ Application Quality Management Help 26.1 All View Local Help Center View Online Help Center Version: