📄️ 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.
📄️ Trial Install
This topic describes how to install a trial version of Release.
📄️ Basic Install
This topic describes how to install Release in a standard installation - either a simple setup with the default configuration, or a manual setup in which you can choose specific options. If you are installing Release in a production-ready environment that includes options like a separate database server, load balancing for your Release servers, an active/active cluster configuration for your Release servers, and other security, monitoring, and performance considerations, see Production environment install.
📄️ Production Environment Installation
This topic describes how to set up Release in a production environment. It describes how to configure the product, environment, and server resources to get the most out of the product. This document is structured in three sections:
📄️ Cluster Mode
This topic describes how to install and upgrade Release as a cluster. Running Release in a cluster mode lets you have a Highly Available (HA) Release setup. Release supports the following HA mode.
📄️ Upgrade Release - JVM
This topic describes the prerequisites, process and considerations for upgrading to the latest version of Release.
📄️ Configure the SQL Repository
Digital.ai Release stores its data in a repository. By default, this repository is an embedded database stored in XLRELEASESERVERHOME/repository. Completed releases and reporting information are stored in another database called archive. By default, this is also an embedded database stored in XLRELEASESERVERHOME/archive. Embedded databases are automatically created when Release is started for the first time. They are used to simplify the setup for evaluation and test environments. For production use, you must use an industrial-grade external database server.
📄️ Back up Release—JVM
It is a best practice to create regular backups of your Release server. This topic describes how to create a backup and how to restore from that backup.