Installation Prerequisites
Here’s the software and hardware requirements to install and run Digital.ai Release. You can also find information about the supported OS platforms, databases, and browsers to run Digital.ai Release. These are the minimum requirements to install and run Digital.ai Release. Your setup might have to be better than the stated minimum requirements depending on your site’s size and usage pattern. Contact Digital.ai support for assistance.
Supported Operating Systems
Digital.ai Release supports any of the following commercially supported 64-bit operating systems:
- Microsoft Windows 2012, 2016, and 2019 (under Mainstream Support)
-
Linux/Unix-based operating systems
- Ubuntu 18.04 and 20.04
- CentOS 7.x and 8.x
- RedHat Enterprise Linux 8.x
Supported Databases
The following databases are supported.
| Database | Versions Supported |
|---|---|
| PostgreSQL | 12.9, 13.5, and 14.2 |
| MySQL | 5.7 and 8.0 |
| Oracle | 12c and 19c |
| Microsoft SQL Server | 2017 and 2019 |
| DB2 | 11.1 and 11.5 |
Important: Note that DB2 is no longer supported as the database of choice for new sites. However, existing DB2 sites are supported until further notice about dropping support for DB2.
By default, Release is installed with an embedded database. The embedded database is meant for easy setup in evaluation and test environments. For production use, it is strongly recommended to use an industrial-grade external database server such as PostgreSQL, MySQL, Oracle, or Microsoft SQL Server.
For more information, see Configure the SQL repository
Supported Java Development Kit
Digital.ai Release supports OpenJDK 11. You must install OpenJDK 11 to install and run Digital.ai Release.
Important: Release is not supported on non-LTS Java Development Kits (JDKs). See the Java SE support roadmap for details on which Java versions are LTS and non-LTS.
Release Server Hardware Requirements
To install the Release server, your server must meet the following requirements:
CPU
Modern multi-core CPU with x64 architecture
RAM
- At least 4GB-6GB of RAM available for the Release process.
Note: Allocating more than 6GB to the Release process does not show significant performance improvements.
Hard Disk
- Install Digital.ai Release on a hard drive that is persistent, but not NFS.
- Hard disk usage depends on configuration of the product.
- At least 100GB of storage is recommended for the default installation that runs an embedded database.
- Use a fast hard drive. SSDs in a RAID 4 environment, for example.
Release Server Software Requirements
- Network Time Protocol (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 hypervisor settings to synchronize the clock of the virtual machine. Configure time-source synchronization inside the virtual machine.
Reference Setup
Release Application Server
- Two Quad Intel(R) Xeon(R) CPU E5450 3.00GHz
- 16GB of RAM
- Two 300GB 10K SAS 2.5” disks
| Spec | Detail |
|---|---|
| Operating system | CentOS Linux 7.x or 8.x |
| Installed software | A single Release instance running as a service, and monitoring systems |
| Release version | 22.0 |
| Release setup | Standalone, non-clustered |
| Java version | Oracle JDK 11 |
Release configuration:
| Parameter | Value | Location | Description |
|---|---|---|---|
wrapper.java.additional.1 |
-Xms2048m |
XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-linux.conf |
Sets the heap size to minimum 2 GB. The default minimum value is 1 GB |
wrapper.java.additional.2 |
-Xmx6144m |
XL_RELEASE_SERVER_HOME/conf/xlr-wrapper-linux.conf |
Sets the heap size to maximum 6 GB. The default maximum value is 4 GB |
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 50 |
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
- 16 GB of RAM
- Two 300 GB 10K SAS 2.5” disks
| Spec | Detail |
|---|---|
| Operating system | CentOS Linux 7.x or 8.x |
| Release persistence | PostgreSQL 12.9, 13.5, or 14.2 |
PostgreSQL configuration:
| Parameter | Value |
|---|---|
| max_connections | 512 |
| shared_buffers | 4GB |
| effectivecachesize | 12GB |
| synchronous_commit | off |
| maxwalsize | 1GB |
for more information about the configuration, see tuning your PostgreSQL server.
This configuration supports up to 2000 concurrent users running a test set with 200 active releases, 200 templates and 200 completed releases and 200 folders, with a mean response time less then 100 milliseconds.
Note: Other configuration settings may be optimal for your environment (active-active) and load profile (number of concurrent users, release structure).
Supported Web Browsers
- Firefox: the latest 2 versions
- Chrome: the latest 2 versions
- Microsoft Edge Chromium: the latest 2 versions
Note: A minimum screen resolution of 1280 x 1024 is recommended for working with the Release UI.
LDAP
To connect Release to your corporate Active Directory or LDAP server, see Configure LDAP security for Release