NICE DCV Session Manager requirements - NICE DCV Session Manager

NICE DCV Session Manager requirements

The NICE DCV Session Manager Agent and Broker have the following requirements.

Broker Agent

Operating system

  • Amazon Linux 2

  • CentOS 7.6 or later

  • CentOS Stream 8

  • RHEL 7.6 or later

  • RHEL 8.x

  • Rocky Linux 8.5 or later

  • Ubuntu 18.04

  • Ubuntu 20.04

  • Ubuntu 22.04

  • Windows

    • Windows Server 2019

    • Windows Server 2016

    • Windows Server 2012 R2

  • Linux server

    • Amazon Linux 2

    • CentOS 7.6 or later

    • CentOS Stream 8

    • RHEL 7.6 or later

    • RHEL 8.x

    • Rocky Linux 8.5 or later

    • Ubuntu 18.04

    • Ubuntu 20.04

    • Ubuntu 22.04

    • SUSE Linux Enterprise 12 with SP4 or later

    • SUSE Linux Enterprise 15

Architecture

  • 64-bit x86

  • 64-bit ARM

  • 64-bit x86

  • 64-bit ARM (Amazon Linux 2, CentOS 7.x/8.x, RHEL 7.x/8.x, and Ubuntu 18.04 only)

  • 64-bit ARM (Ubuntu 22.04)

Memory

8 GB

4 GB

NICE DCV version

NICE DCV 2020.2 and later

NICE DCV 2020.2 and later

Additional requirements

Java 11

-

Networking and connectivity requirements

The following diagram provides a high-level overview of the Session Manager networking and connectivity requirements.


					NICE DCV Session Manager network architecture

The Broker must be installed on a separate host, but it must have network connectivity with the Agents on the NICE DCV servers. If you choose to have multiple Brokers to improve availability, then you must install and configure each broker on a separate host, and use one or more load balancers to manage the traffic between the client and the Brokers, and the Brokers and the Agents. The Brokers should also be able to communicate with each other in order to exchange information about the NICE DCV servers and sessions. The Brokers can store their keys and status data on an external database and have this information available after reboot or termination. This helps mitigate the risk of losing important Broker information by persisting it on the external database. You can retrieve it later. If you choose to have it, then you must set up the external database and configure the brokers. DynamoDB, MariaDB, and MySQL are supported. You can find configuration parameters are listed on the Broker Configuration File.

The Agents must be able to initiate secure, persistent, bi-directional HTTPs connections with the Broker.

Your client, or frontend application, must be able to access the Broker in order to call the APIs. The client should also be able to access your authentication server.