This topic describes the hardware, software, and user requirements for installing Tamr Core, and lists supported browser versions.

Hardware Requirements

For hardware requirements, see Single-Node Deployments.

Important: Do not run other software on a server where you intend to install and deploy Tamr Core.

Operating System Requirements

Tamr Core can be deployed on the following operating systems:

• Red Hat Enterprise Linux (RHEL) 9, 8.6, or 7.8
• Ubuntu Server 18.04 supported only when upgrading existing deployments.
  Important: Ubuntu 18.04 reached End of Standard Support in June 2023. See Notice for Ubuntu for recommended steps.
• Ubuntu Server 22.04 for new deployments.

Tamr Functional User Requirements and Creation

Operating system users are identified by either standard user accounts, tied to individual people at your organization, or functional system accounts, which are privileged differently and are used to manage specific applications.

Tamr recommends that you create a local functional system account, such as tamr, to use for all Tamr Core deployment and administration tasks, as described below. Tamr recommends against using an externally-managed standard user account.

This documentation refers to the functional system account for the administration of Tamr Core and its dependencies as the “functional user”.

Important: The username for the functional account must not contain the backslash (\) character. If the account you use to manage Tamr includes this character, Spark jobs fail to run.

To create an operating system functional user, such as tamr, see the following resources:

• RHEL: Managing Users and Groups
• Ubuntu Server: User Management

Required Privileges for Installation Steps

PostgreSQL install or upgrade must be performed by a user with sudo privileges.

All other install or upgrade steps must be performed as the functional user (for example, tamr). The user performing these steps does not require sudo access.

Important: Never use the root user to install or upgrade Tamr Core, or to start or stop Tamr Core services or dependencies.

Setting ulimit Limits

Configure the following ulimit resource limits for the tamr functional user.

To set ulimit resource limits:

1. Create a new 99-tamr.conf file in the /etc/security/limits.ddirectory. Do not edit the file /etc/security/limits.conf directly.
2. Add configuration to this file as shown in the following example.

# /etc/security/limits.d/99-tamr.conf 
*               soft    nofile       1000000
*               hard    nofile       1000000
*               soft    nproc        104381
*               hard    nproc        104381

3. Sign out and then sign in again as the tamr functional user to set the new values.
4. Verify the current values:
   • Maximum number of open files (nofile) is 1000000. To confirm the current value, run ulimit -n.
   • Maximum number of user processes (nproc) is 104381. To confirm the current value, run ulimit -u.

For more information about ulimit resource limits, see the following:

• RHEL: How to set ulimit values
• Ubuntu: Configuration file for ulimit limits

Setting vm.max_map_count

You can change the maximum number of memory map areas a process may have, specified with vm.max_map_count. The minimum number of memory map areas is 262144.

To set vm.max_map_count:

1. Edit the /etc/sysctl.conf file; add a line at the end containing: vm.max_map_count=<value>, where <value> is the maximum number of memory map areas for a process.
2. Run sudo sysctl -p to use the newly set value.
   If you receive a "Could not parse vm.max_map_count value" error message, follow the instructions below to add permissions to the tamr functional user.
3. Run sysctl vm.max_map_count to confirm the current value.

To add permissions to the tamr functional user:

1. Add the following line to the tamr functional user’s .bash_profile or .bashrc:
   export PATH="/sbin/:$PATH"
2. Log in again as the tamr functional user to put the change into effect.

Port Requirements

You can access the Tamr Core user interface and APIs over a single port for inbound web access. The default HTTP port Tamr Core uses is 9100.

Tamr Core and its dependent services use other ports, but typically these ports do not need to be exposed for inbound access.

Optionally, Tamr recommends that you expose the monitoring port for inbound web traffic. The default port number is 31101. For more information, see Monitoring.

NGINX Version Requirements

Tamr Core requires NGINX version 1.11 at a minimum, and recommends installing the latest version of NGINX supported by the OS. See Installing NGINX and Configuring HTTPS.

Postgres Version Requirements

Tamr Core requires PostgreSQL v12. To ensure your installation has the latest bug and security fixes, install or upgrade to the latest minor version of PostgreSQL v12 . See Installing Postgres and Upgrading Postgres.

Browser Support for the Web Application