Installation Prerequisites

This topic describes server and client requirements for Release.

Server requirements

To install the Release server, your system must meet the following requirements:

  • Release license: See Release licensing.
  • Operating system: Any commercially supported version of 32-bit or 64-bit Microsoft Windows (under Mainstream Support), or a commercially supported Linux/Unix-based operating system.
  • OpenJDK:

    • OpenJDK 11
    • We recommend using the latest stable build for your Java installation and applying updates over time

For more information on installing Release, see the appropriate installation topic:

Server hardware requirements

  • Multicore CPU
  • RAM: 4-6 GB 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: Release must be installed on a hard drive that is persistent, but not NFS. Hard disk usage depends on configuration of the product. At least 100 GB 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.

Server software requirements

  • Network Time Protocol (NTP) synchronization between Release server and database server(s)


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.

External systems

  • Database: 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, Microsoft SQL Server or DB2. See Configure the Release SQL repository in a database for details. Click here to know the list of supported databases for Release.
  • LDAP: To connect Release to your corporate Active Directory or LDAP server, see Configure LDAP security for Release.

Reference setup

Release 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.2
Installed software A single Release instance running as a service, and monitoring systems
Release version 9.0
Release mode Standalone, non-clustered
Java version Oracle JRE 1.8.0_74

Release configuration:

Parameter Value Location Description -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 -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

  • 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.2
Release persistence PostgreSQL 9.6 and 10.1

PostgreSQL configuration:

Parameter Value
max_connections 512
shared_buffers 4GB
effectivecachesize 12GB
synchronous_commit off
maxwalsize 1GB

For more details 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).

Client requirements

The following web browsers are supported for the Release user interface:

  • Chrome
  • Firefox

Note: A minimum screen resolution of 1280 x 1024 is recommended for working with the Release UI.