Software requirements

Olga Semme

Operating system

IMPORTANT

  • The life cycle of Centos 7 ended on June 30, 2024.

  • Ubuntu 22.04 is being replaced by Ubuntu 24.04 in releases after April 1, 2026.

  • Alt Linux 8.4 SP is being replaced by Alt Linux 10 SP in releases after January 1, 2026.

  1. ADS supports only x86_64 architecture and the following operating systems:

    • Centos 7.9;

    • RHEL 7.9;

    • Ubuntu 22.04;

    • AltLinux sp 8.4 — available only for the Enterprise version;

    • Astra Linux 1.7 "Orel" SE with Axiom JDK — available only for the Enterprise version;

    • Astra Linux 1.7 "Voronezh" SE with Axiom JDK — available only for the Enterprise version;

    • RED OS 7.3 Certified edition — available only for the Enterprise version.

  2. You need to prepare all dependent repositories together with the chosen operating system.

  3. All machines in the cluster must have access to the official repositories (or create a local mirror):

  4. In the case of online installation, you must provide access to the repositories listed on the Configuration tab in the ADS cluster menu in the ADCM UI. The Configuration tab is described in Configure a cluster.

  5. In the case of offline installation, you must provide access to the host where the Enterprise Tools cluster is deployed. Installing an Enterprise Tools cluster is described in the section Install Enterprise Tools cluster.

  6. To support kTLS (supported since ADS 3.9.0.1.b1), you need an operating system kernel version 5.9 or higher. kTLS mode is enabled by default. However, if your kernel version is lower than required, you will be rolled back to the default mode.

  7. To use Astra Linux "Voronezh", the ADCM service user must have the integrity label 63: sudo pdpl-user -i 63 adcm.

Preinstalled software

  1. NTP must be preconfigured on servers.

  2. Access must be given to the root user or another user with sudo rights.

  3. The hosts must have Java 17 pre-installed.

NOTE

Centos, RedHat, and AstraLinux operating systems do not have Java 17 in the system packages.

For hosts with one of these operating systems, use one of the following methods to install Java 17 before upgrading/installing the cluster:

  • Manually install Java 17 on hosts and configure the JAVA_HOME variable.

  • Install Java 17 from the Arenadata repository using the method described below.
Install Java from the Arenadata repository

 

Starting with ADS 3.7.2.1.b1, on the cluster configuration page, there is an option to install Java 17 from the Arenadata repository.

If you enable the option before running the Install, Add/Remove components, or Update action for a cluster or service, the latest version of Java 17 will be installed on cluster hosts during the action.

To enable the option to install Java 17 from the Arenadata repository, expand the group with the repositories of the selected OS (for example, Centos 7 repositories), select the arenadata_java repository, and expand its parameters. Set the enabled parameter to true.

Configuring Java 17 installation from Arenadata repository for Centos 7
Configuring Java 17 installation from Arenadata repository for Centos 7

Once this option is enabled, Java 17 will be installed from the Arenadata repository regardless of what is specified in the JAVA_HOME variable (Custom JDK settings group).

CAUTION
Arenadata is not an official JDK provider, and this feature is provided to ensure a fully automatic installation on systems that do not have the necessary dependencies. In production environments, we recommend using a JDK from official providers.

Installation features

  1. The installation process modifies files that should not be controlled by the configuration management system (if available):

    • system file /etc/hosts;

    • system file /etc/selinux/config;

    • system file /etc/sysctl.conf.

  2. The installation process creates files in /usr/lib/systemd/system/ that should not be controlled by the configuration management system (if available).

  3. Services installed on a cluster should not be controlled by the configuration management system (if available).

  4. It is recommended to switch off any antivirus software before ADS installation and during the ADS operation process. In case of using antivirus, please contact your antivirus software vendor to find out the settings necessary to allow ADS.

SELinux

SELinux must be turned off. The full guide about this operation you can find in Install ADCM.

Firewall

Firewall must be stopped. The full guide about this operation you can find in Install ADCM.

Supported browsers for NiFi

  1. The work of the NiFi service is supported by browsers:

    • Chrome

    • FireFox

    • Edge

    • Safari

  2. UI is supported in the current stable release of that browser and the preceding one. For instance, if the current stable release is 45.X then the officially supported versions will be 45.X and 44.X.

  3. For Safari, which releases major versions much less frequently, supported versions will be the two latest releases.

  4. The supported browser versions are driven by the capabilities the UI employs and the dependencies it uses. UI features are developed and tested against the supported browsers.

Found a mistake? Seleсt text and press Ctrl+Enter to report it