|
|
This document provides information on minimum requirements,
recommended environments, and supported environments for running ALM 24.1.x.
In this topic:
· Server-side system requirements
· Quality Insight requirements
· Install and run ALM in cloud environments
Server-side system requirements
The following are the server-side system requirements and configurations for installing ALM 24.1.x on Windows and Linux.
Hardware
ALM has the
following hardware requirements:
|
Component |
Requirement |
|
CPU |
Quad
Core AMD64 processor or equivalent x86-compatible processor |
|
Memory (RAM) |
8 GB minimum |
|
Free disk space |
8 GB minimum |
Software
ALM has the
following software requirements:
|
Component |
Requirement |
Notes |
|
· Amazon Linux 2023 · Microsoft Windows Server 2022 · Microsoft Windows Server 2019 · Microsoft Windows Server 2016 · Red Hat Enterprise Linux 9.x 64-bit · Red Hat Enterprise Linux 8.x 64-bit · Red Hat Enterprise Linux 7.x 64-bit · Oracle Linux 9.x 64-bit · Oracle Linux 8.x 64-bit · SUSE Linux Enterprise Server 15 64-bit · SUSE Linux Enterprise Server 12.0 64-bit |
· Operating systems’ service packs and
updates are supported, provided they are compatible with the vendor’s general
availability release. · Oracle Linux versions are supported,
provided they are compatible with the supported versions of Red Hat Linux. |
|
|
Application Server |
· Apache 2.4x · Microsoft IIS 10 |
· The application server functionality is
now built into the ALM/QC platform and there is no need to install a
third-party application server (WebLogic, WebSphere, and JBoss) from version
11.50 and later. The ALM application server supports 64-bit JVM. · By default, application servers include
HTTP servers. If you need additional functionality, a web server can be
added. · OpenText will certify major and minor releases of Apache (e.g. Apache 2.4), while all minor-minor releases of Apache (e.g. version 2.4.x) will not undergo specific certifications, as it is expected that minor-minor software releases from Apache will maintain full compatibility. |
|
Database Server |
· Oracle 21c · Oracle 19c · Microsoft SQL Server 2022 · Microsoft SQL Server 2019 · Microsoft SQL Server 2017 · Microsoft SQL Server 2016 · Microsoft SQL Server 2014 |
· For Oracle databases: To store
non-English or multiple language
groups.OpenText recommends you set Database Character Set to Unicode
Character Set. · Otherwise, some non-English characters
may be corrupted after upgrading to Oracle 12.2.0.1. This issue has been
identified as an Oracle defect. The fix is included in Oracle patch 26380097.
For additional help, contact Oracle Support. · SQL Server Standard and Enterprise
editions are supported. For the edition differences, check the Microsoft
official documents. |
|
JDK/JRE |
· Oracle Java 17 · Oracle Java 11 · Oracle Java 8 · OpenJDK 17 · OpenJDK 11 · OpenJDK 8 |
· We will remove support for Oracle Java 8,
OpenJDK 8, OpenJDK 11, Oracle Java 11
anytime in the future. · Limitation for Oracle Java 11 GA: Fail to deploy ALM when Oracle Java 11 GA is installed. Use versions later than GA. |
|
Virtual environments |
VMWare ESX/ESXi Server 5.0 and higher |
ALM is certified to work with VMWare ESX/ESXi. Due to the rapidly evolving architectures provided by
virtualization vendors (e.g. Hyper V or Citrix), as long as the above-stated
vendor guarantees full compatibility of the virtualized environment to the
ALM approved system requirements for physical hardware, ALM supports the
virtualized environments and function as designed. |
Supported languages
ALM 24.1 supports 7 languages: English, French, German, Simplified Chinese, Japanese, Korean, and Brazilian Portuguese.
· English, Simplified Chinese, French, and German have both Linux and Windows installations.
· Japanese, Korean, and Brazilian Portuguese have Windows installation only.
Server-side recommended environments
The following table lists the server-side recommended environments:
|
Operating System |
Database |
Application Server |
JDK/JRE |
|
Microsoft Windows
Server 2019 |
Microsoft SQL Server 2019 |
Microsoft IIS 10.0 |
Oracle Java 17 |
|
Red Hat Enterprise
Linux 9.x 64-bit |
Oracle 19c |
Apache 2.4 |
Oracle
Java 17 |
Desktop Client requirements
The following are the system requirements and configurations for running ALM Desktop Client.
Hardware
ALM Desktop Client
has the following hardware requirements:
|
Component |
Requirement |
|
CPU |
Core duo 1.6 Ghz (or
higher) or equivalent compatible processor |
|
Memory (RAM) |
2 GB reserved |
|
Free disk space |
4 GB reserved |
Software
ALM Desktop Client
has the following software requirements:
|
Component |
Requirement |
Notes |
|
Operating System |
· Microsoft Windows 11 · Microsoft Windows 10 · Microsoft Windows Server 2022 · Microsoft Windows Server 2019 · Microsoft Windows Server 2016 |
All Windows 10 builds distributed and approved by Microsoft are supported, provided they are compatible with the Windows 10 general availability release. Due to the "blue screen" error in some builds of Microsoft Windows 10, you may need to apply a required fix: · For Windows 10 Build 1507 (32-bit), see http://support.microsoft.com/kb/KB4048956. · For Windows 10 Build 1703 (32-bit or 64-bit), see http://support.microsoft.com/kb/KB4022716. · For Windows 10 Build 1903 and later (32-bit or 64-bit), see http://support.microsoft.com/kb/KB5010415. |
|
ALM Client Launcher |
Download it from the marketplace: https://www.microfocus.com/marketplace/appdelivery/content/alm-client-launcher |
Prepare the following before installing and using ALM Client Launcher: · Install .NET Framework 4.7 or later. · Install Microsoft Visual C++ 2015 Redistributable (x86) or later. · If you install ALM Client Launcher in Windows Server, to have better download experience, OpenText recommends that you disable the IE Enhanced Security Configuration option in Windows Server. |
|
Browser |
Microsoft Edge with IE mode enabled See the online help for how to enable IE mode. |
You can run the same ALM Desktop Client using either ALM Client Launcher or the Microsoft Edge browser with IE mode enabled. OpenText recommends you use ALM Client Launcher. |
|
Screen
resolution |
Minimum
requirement: 1024*768 Recommended: 1600*900 or higher |
Using a lower resolution may lead to unnecessary
scrollbars. |
|
DPI settings |
100% |
Using manufacturer-recommended screen resolution, the recommended DPI setting is 125% and the maximum DPI setting is 150%. If you use higher DPI settings, the ALM Desktop Client menu items and columns may not be fully displayed. |
|
Virtual environments |
· Citrix XenApp 6.0 or higher · Microsoft Terminal Services · Remote Desktop Services |
ALM is certified to work with Citrix XenApp, Microsoft Terminal Services, and Remote Desktop Services. Due to the rapidly evolving architectures provided by Virtualization vendors, as long as the above-stated vendors guarantee full compatibility of the virtualized environment to the ALM approved system requirements for physical hardware, ALM functions as designed. |
Desktop Client recommended environments
The following table lists the recommended environments for ALM Desktop Client:
|
Component |
Requirement |
|
Operating System |
Microsoft
Windows 10 64-bit |
|
ALM Client Launcher |
The latest version |
|
Office Suites |
Microsoft 365 desktop apps |
Web Client requirements
ALM Web Client has
the following requirements:
|
Component |
Requirement |
|
Browser |
· Google Chrome (Recommended) · Microsoft Edge · Firefox · Safari |
|
Screen resolution |
Recommended: 1440*900 or higher Using a lower resolution may lead to unnecessary
scrollbars. |
|
ALM |
15.0.x or later |
Quality Insight requirements
The following table lists the system
requirements for installing Quality Insight.
|
Component |
Requirement |
|
Operating System |
For Windows: ·
Microsoft Windows Server 2022 ·
Microsoft Windows Server 2016 ·
Microsoft Windows Server 2012 R2 For Linux: Red Hat Enterprise Linux 6.5 (64-bit) or higher |
|
CPU |
Quad Core AMD64 processor or equivalent x86-compatible processor |
|
Memory |
·
Recommended:
32 GB ·
Supported:
16 GB |
|
Free Disk Space |
Ratio of 1:5 between the size of the ALM database and Quality Insight. For example, if your ALM database is 20 GB, then you need at least 100 GB of free disk space for Quality Insight. There
is an option to change the location where Quality Insight data is stored,
such as to a shared location. In this case, the above requirements would
apply for the specified location where the data is saved. |
|
JDK |
JDK 8 |
|
Network |
To prevent network access to Quality Insight data, make
sure that the Quality Insight machine is protected behind a firewall,
and that only the ALM server and other trusted machines can access it. |
Install and run ALM in cloud environments
The following table lists the cloud platforms that are tested and verified to install and run ALM. Any other cloud platforms are also supported if all components of the cloud computing environment follow the system requirements specified above.
|
Cloud Platform |
Requirement |
Notes |
|
Amazon AWS |
· Computing: Amazon EC2 running supported
operating systems. · File system: Amazon Elastic File System (EFS) · Database: Amazon RDS for Oracle 19c · Email service: Amazon Simple Email Service (SES) · Networking: Amazon Application Load Balancer |
· Amazon RDS for Microsoft SQL Server
database instances: You can create up to 30 databases on each database
instance. The Microsoft system databases, such as master and model, are not
counted toward this limit. · In AWS GovCloud (US) Regions, ALM is
certified to work with Amazon EC2 running Microsoft Windows Server 2016. For
details, consult AWS. |
|
Microsoft Azure |
· Computing: Azure Virtual Machines running supported
operating systems. · File system: Azure Files · Database: Azure SQL Database - Deployment Model:
Managed Instance · Email service: SendGrid Email Delivery for Microsoft
Azure · Networking: Azure Load Balancer |
· There are several deployment models
available for Azure SQL Database. ALM supports Managed Instance deployment
model. For details, see the Microsoft
Azure documentation. · For a sample that shows how to install
ALM on Microsoft Azure, see KM03280653. · For a sample that shows how to
migrate OnPrem ALM databases to Azure SQL Database Managed Instance,
see KM03276819. · In Azure Government, ALM is certified to
work with Azure Virtual Machines running Microsoft Windows Server 2016. For
details, consult Azure. |
|
Google Cloud Platform |
· Computing: Google Cloud Compute Engine Virtual
machine instances (Redhat 9) · File system: Google Cloud Filestore · Database: Google Cloud SQL (SQL Server 2019
Standard) · Networking: Google Cloud Load Balancing |
|
Full Disk Encryption
Full disk encryption (FDE) is supported for all system components, including database, server, repository server, and client machines. Implementation of FDE does have an impact on system performance. For details, contact the vendor that provides the encryption.
Add-in requirements
The following table lists the requirements for ALM add-ins.
|
ALM Add-in |
Microsoft 365 desktop apps |
Microsoft Office 2021 |
Microsoft Office 2019 |
Microsoft Office 2016 |
|
Microsoft Excel add-in |
√ |
√ |
√ |
√ |
|
Microsoft Word add-in |
√ |
√* |
√* |
√* |
|
Note: √* indicates 64-bit of the application is
not verified but may also work. |
||||
Plugin requirements
The following table lists the requirements for ALM plugins.
|
ALM plugin |
Jira Requirement |
ALM Requirement |
|
ALM – Test Management for Jira
on-premises plugin |
· Jira Data Center: 8.0.0 - 9.12.x · Jira Server: 7.0.0 - 9.12.x |
15.0.1 and later versions Note: If a secure protocol is used
to access the ALM server, make sure the relevant certificate is trusted by
the Jira server. |
|
ALM – Test Management for Jira
Cloud plugin |
N/A |
15.0.1 and later versions, both on-premises and
SaaS. Note: · If a secure protocol is used to access
the ALM server, make sure the relevant certificate is trusted by the Jira
server. · If you use this plugin on an ALM
on-premises server, make sure the server is accessible by Jira Cloud and the
server uses a secure protocol. |
Product support lifecycle
Visit the Product Support
Lifecycle table for release details and dates.
The Product Support Lifecycle policy defines the level of support OpenText provides for each product version.