Installation Prerequisites

This page covers the minimum hardware and software requirements to install and run Digital.ai Release. Also, you will get information about the supported operating systems, databases, web browsers, kubernetes platforms, JDKs, message brokers, upgrade versions, and so on. Ensure that your setup is better than the stated minimum requirements, depending on your site’s size and usage pattern. For more assistance, contact Digital.ai support.

Supported Operating Systems

The following operating systems are supported:

Operating Systems Versions Supported
Windows Server 2022, 2019, and 2016
Ubuntu 20.04 LTS and 18.04 LTS
CentOS 7.x
RHEL 8.X

Supported Databases

The following databases are supported:

Database Versions Supported
PostgreSQL 14.3 and 13.7
MySQL 8.0 and 5.7
Oracle 19c and 12c
Microsoft SQL Server 2019 and 2017
IBM DB2 11.5 and 11.1

Important: DB2 is no longer supported as the database of choice for new sites. However, existing DB2 sites are supported by Digital.ai until IBM stops support for DB2.

Release is installed with an embedded database, by default for easy setup in evaluation and test environments. For production use, we recommend using an industrial-grade external database server such as PostgreSQL, MySQL, Oracle, or Microsoft SQL Server. For more information, see Configure the SQL repository.

Note: You may use the older versions of Release and Databases. However, we have performed limited validations to ensure that Release works in database cluster environment. For example, we validated Release 10.2.x with PostgreSQL 12.4 cluster using Patroni.

Supported Web Browsers

The following web browsers are supported:

Web Browsers Versions Supported
Chrome 109 and 108
Edge chromium 108
Firefox 109.0 and 108.0

Note: Minimum screen resolution of 1280 x 1024 is recommended to work with the Release UI.

Supported Kubernetes Platforms

The following Kubernetes platforms are supported:

  • AWS EKS
  • Azure AKS
  • GCP GKE
  • Kubernetes on-premise
  • OpenShift on VMWare vSphere
  • OpenShift on AWS

Note: This is only for operator-based installation, and not for JVM based installation.

Supported Java Development Kit

The following Java Development Kits (JDK) is supported:

JDKs Versions Supported
IBM JDK 11
Oracle JDK 11
Open JDK 11

Important: Release is not supported on non-LTS Java Development Kits (JDKs). For more information on LTS and non-LTS Java versions, see Java SE support roadmap.

Supported Message Brokers

The following message brokers are supported:

  • ActiveMQ
  • RabbitMQ

Release Server Hardware Requirements

The following are the hardware requirements to install the Release server:

CPU

Modern multi-core CPU with x64 architecture.

RAM

  • At least 4GB - 6GB of RAM available for the Release process.

Note: Allocating more than 6 GB to the Release process does not show significant performance improvements.

Hard Disk

  • Install Digital.ai Release on a hard drive that is persistent, and not a Network File System (NFS).
  • Hard disk usage depends on configuration of the product.
  • At least 100GB of storage for the default installation that runs an embedded database.
  • Use a faster hard drive. For example, use SSDs in RAID 4 environment.

Release Server Software Requirements

The following are the software requirements to install the Release server:

Network Time Protocol (NTP) synchronization

There must be a NTP synchronization between Release server and Database server(s).

From https://github.com/brettwooldridge/HikariCP#configuration-knobs-baby:

HikariCP relies on accurate timers for both performance and reliability. It is important that your server is synchronized with a time-source such as an NTP server. This is required if your server is running within a virtual machine. For more information, see HickariCP documentation.

Important: Do not rely on the hypervisor settings to synchronize the clock of the virtual machine. Configure time-source synchronization inside the virtual machine.

Reference Setup

The following sections cover the hardware and configuration details of Release:

Release Application Server

  • Two Quad Intel(R) Xeon(R) CPU E5450 3.00GHz
  • 16GB RAM
  • Two 300GB 10K SAS 2.5” disks
Specification Details
Operating system CentOS Linux 7.x
Installed software A single Release instance running as a service and a monitoring system
Release version 22.3
Release setup Standalone, non-clustered
Java version IBM JDK 11

Release configurations

Parameter Value Location Description
wrapper.java.additional.1 -Xms2048m XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-linux.conf Sets the heap size to minimum 2GB. The default minimum value is 1GB.
wrapper.java.additional.2 -Xmx6144m XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-linux.conf Sets the heap size to maximum 6GB. The default maximum value is 4GB.
threads.min 64 XL_RELEASE_SERVER_HOME/conf/xl-release-server.conf Sets the minimum number of HTTP threads to 64.
threads.max 256 XL_RELEASE_SERVER_HOME/conf/xl-release-server.conf Sets the maximum number of HTTP threads to 256.
xl.executors.scheduler.maxThreadsCount 128 XL_RELEASE_SERVER_HOME/conf/xl-release.conf Sets the maximum number of threads for asynchronous operations to 128.
xl.database.max_pool_size 64 XL_RELEASE_SERVER_HOME/conf/xl-release.conf Sets the maximum number of threads for database pool to 64.

SQL Database Server

  • Two Quad Intel(R) Xeon(R) CPU E5450 3.00GHz
  • 16GB RAM
  • Two 300GB 10K SAS 2.5” disks
Specification Details
Operating system CentOS Linux 7.x
Release persistence PostgreSQL 15.0 or 14.4

PostgreSQL configurations

Parameter Value
max_connections 512
shared_buffers 4GB
effective_cache_size 12GB
synchronous_commit off
max_wal_size 1GB

For more information about the configuration, see tuning your PostgreSQL server.

This configuration supports up to 2000 concurrent users running a test set of 200 active releases, 200 templates, 200 completed releases, and 200 folders. All of these, with a mean response time of less than 100 milliseconds.

Note: Other configuration settings may be optimal for your environment (active-active) and load profile (number of concurrent users and release structure).

LDAP

To connect Release to your corporate Active Directory or LDAP server, see Configure LDAP security for Release.

Upgrade Release version

You can perform an one-hop upgrade from the following versions to Release 22.3 version:

  • Release 10.2.x
  • Release 10.3.x
  • Release 22.0.x
  • Release 22.1.x
  • Release 22.2.x