Edit

Hardware and OS

Hardware and OS

IA Cloud Enterprise requires a minimum of five servers to be prepared in the production environment. You can scale the environment to any extent by adding extra Agent and RPA servers, if needed.

The product can be installed in two modes:

• Basic. This mode requires fewer servers but doesn't provide high availability. See the Basic environment tab.

• High-availability.

  High availability (HA) is the ability of a system to be continuously operational for a long period. Its aim is zero data loss and a maximum of 10 minutes of service downtime, after which it must be fully restored. For that, you need 2-3 instances of each server that you want to be highly available. See the High-availability environment tab

Basic environment

High-availability environment

Server	OS (Recommended in bold)	CPU (cores)	RAM (GB)	Disk (GB)
Master1	RHEL/CentOS 8.5, 8.4, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3	8	32	750
Agent (1-3 servers)4	RHEL/CentOS 8.5, 8.4, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3	8	32	150
Analytics (BI)2	Microsoft Windows Server 2019, 2016, 2012 R2	4	16	150
MS SQL	Microsoft Windows Server 2019, 2016, 2012 R2	4	16	500
RPA (5 bots)2	Enterprise Server: Microsoft Windows Server 2019, 2016, 2012 R2 VDI Server: Microsoft Windows Server 2019, 2016, 2012 R2 Microsoft Windows 10	8	16	150

Note that MS SQL Server is not provided by WorkFusion and must be prepared and licensed on your own.

Also, in previous releases, the OCR server was a separate instance. In 10.2, it is implemented as a service running on Agent servers. This needs to be taken into account when making decision about scaling the amount of Agent servers.

Server	Number of servers for HA mode	OS (Recommended in bold)	CPU (cores)	RAM (GB)	Disk (GB)
Master	3	RHEL/CentOS 8.5, 8.4, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3	8	32	750
Agent4	3	RHEL/CentOS 8.5, 8.4, 7.9, 7.8, 7.7, 7.6, 7.5, 7.4, 7.3	8	32	150
Analytics (BI)2	2	Microsoft Windows Server 2019, 2016, 2012 R2	43	16	150
MS SQL Server	2	MS Windows Server 2019, 2016, 2012 R2	4	16	500
RPA (5 bots)2	2	Enterprise Server: Microsoft Windows Server 2019, 2016, 2012 R2 VDI Server: Microsoft Windows Server 2019, 2016, 2012 R2 Microsoft Windows 10	8	16	150

¹—Make sure that at least 15% of disk space on the server is always available.

²—The server is required only if you are planning to use the functionality.

³—If you deploy the Analytics server on a cloud platform (AWS, Azure), note that the number of virtual CPUs (vCPU) does not always directly correspond to the number of cores that Tableau Server detects for licensing purposes. For more information, see Additional information.

⁴—Using burstable instances is not recommended in case of the AWS deployment.

Disk space and file system

• It is strongly recommended to install and run IA Cloud on a separate non-root partition. It can be a separate disk mounted to the server or a partition on the same disk.

  The installation is performed via Ansible, which requires at least 8GB of free space for temporary files in the /tmp directory on Linux servers.

  After the installation or update, the components are allocated on the file system only within the installation directory (hereinafter, INSTALL_DIR) and do not use the space allocated for the operating system. The default installation directory is /opt/workfusion/.

• The root disk with the Operating system must have reasonably enough space to keep Red Hat family 7.x OS functioning. For example, 20 GB is enough.

• For RHEL/CentOS servers, the XFS or EXT4 filesystems are required.

• It is highly recommended to dedicate a separate SSD disks for ZooKeeper datalog (at least 10 GB of free space) and Elasticsearch data directories (at least 100 GB of free space). For more information, see the instruction.

• It is recommended to dedicate separate SSD disks for aggregated logs from Logstash (at least 70 GB of free space). For more information, see the Shared file system section below and the instruction.

Shared file system

The disk on a shared file system must be mounted to the Master server before the installation.

Supported types of the file system on shared disks:

• NFS
• GFS2
• GPFS
• AWS EFS

warning

Windows Server based storage solutions (DFS, NFS, CIFS/SMB) are not supported.

When mounting a shared file system, you have the following options depending on your installation mode:

Basic mode

High availability mode

The Master server is the storage host and shares its INSTALL_DIR/vds-data directory among the Agents. Create the INSTALL_DIR/vds-data directory on the Master server and install it to Agent servers.

You can optionally install external shared disk for aggregated logs to INSTALL_DIR/logs_aggregated on the Master server.

Server	Directory on the server	Shared disk size
Master server	INSTALL_DIR/vds-data	250 GB
Agent servers	INSTALL_DIR/vds-data	-
(optionally) Master server	INSTALL_DIR/logs_aggregated	70 GB

Note that, on the Master server, the vds-data directory must be separate from the main disk space. Thus, the total disk space on the Master server must be at least 1 TB (750 GB + vds-data 250 GB).

Before the installation, the single directory must be installed from the external shared disk to the directories on the Master and Agent servers.

You can optionally install an external shared disk for aggregated logs to INSTALL_DIR/logs_aggregated on Master servers.

Server	Directory on the server	Shared disk size Development or Pilot	Shared disk size Production
Master Agent 1-3	INSTALL_DIR/vds-data	500 GB	250 GB
Master	INSTALL_DIR/shared	250 GB	500 GB
(optionally) Master server	INSTALL_DIR/logs_aggregated	70 GB	35 GB

On the Master server, the vds-data and shared (and optional logs_aggregated) directories must be separate from the main disk space. Thus, the total disk space on the Master server must be at least 1.5 TB (750 GB + vds-data 250 GB + shared 500 GB + optional logs_aggregated 70 GB).

System updates

After you deploy required Linux servers, act as follows:

1. Find out the exact version of the operating system by running the command on each Linux server:

   uname -a
   

   Specify this version in the checklist.

2. Make sure that you have the latest OS updates installed. For that, on all Linux servers run the following command to see all package updates (if any):

   yum check-update
   

   If there are no available packages of newer versions, your system is up-to-date.

3. If the command displays any available OS updates, install them to the system:

   yum update -y
   

If the RHEL repository is not available, for example, because the server is not connected to the Internet, see the troubleshooting guide.

Other requirements

• For optimal work of the IA Cloud Enterprise components, use the latest Chrome version.

• Make sure that the TLS 1.2 support is enabled in the browser.

• JavaScript must be allowed on the Analytics servers.

• It is highly recommended to dedicate a separate SSD disks for Zookeeper datalog (at least 10 GB of free space) and Elasticsearch data directories (at least 100 GB of free space). For more information, see the instruction.

• The timezone on the Master and Agent servers must be set to UTC. To verify or change your current timezone, on the server, use the following commands:

  timedatectl status
  timedatectl set-timezone UTC
  

  Note that changing system's timezone requires root user or sudo priveleges.

Checklist

To facilitate preparation for the IA Cloud installation, after you deploy the necessary servers or prepare Virtual Machines, in the checklist for the high-availability or basic setup, complete the Hardware section, depending on the planned mode, save, and provide it to the WorkFusion deployment engineers.