1. Home
  2. Previous Releases
  3. Latest Release
  4. Guides
    1. Start
    2. Administer
    3. Analyze
    4. Configure
    5. Deploy
    6. Install
      1. Installation Requirements
        1. Install Java
      2. Install on a Single Node
      3. Finish Installing Incorta with the CMC
      4. Installation Troubleshooting
      5. Install in the Cloud
    7. Migrate
    8. Organize
    9. Secure
    10. Upgrade
    11. Visualize
  5. Concepts
  6. Tools
  7. References
  8. Integrations
  9. Data applications
  10. Releases
  11. Incorta Premium

Installation Requirements

Context

This content applies to On-Premises installations only.

Before you install Incorta, ensure your system meets the following requirements.

Operating System

The following Operating Systems (OS) support the Incorta platform :

  • CentOS 7 and up (7.5 and up recommended)
  • Ubuntu
  • Redhat 8
  • Oracle Linux 8.0

Requirements

Installation of the Incorta platform requires the following:

  • A valid license key if you are installing Incorta. To obtain your license key, please contact Incorta Support.
  • At least 16 GB of RAM. This number could increase depending on the amount of data
  • A temporary directory (/tmp folder) with at least 4 GB of available space
  • Fast storage disk (e.g. SSD)
  • NFS v4 shared storage disk, accessible by all the services within the same cluster (i.e. loader and analytic services). The shared disk will be used to store data files (if applicable), parquet files, and snapshot files used by the system. This is not required if you are installing Incorta on a single server (for example, on your laptop)
  • Java Development Kit (JDK) 8u144, JDK 8u171 and up, Open JDK 11, or Oracle JDK 8. Incorta does not support Java SDK 1.8.0.151 (8u151) through 1.8.0.171 (8u171). Starting 2024.7.x, JDK 8u144 will not be supported either. Install Java and set the Java home path. For more on how to install Java, see Install Java
  • A database to connect to Incorta. See Database Requirements
  • Zookeeper 3.6.1, bundled with Incorta, but you can install it separately. For more information, see Set up a Zookeeper Cluster
  • Spark 3.3 and Hadoop 3.2.0, bundled with Incorta, but you can install them separately. For more information, see About Spark and Spark official documentation. Starting 2024.7.x, Incorta uses Spark 3.4.1, and all Incorta applications, including the Advanced SQL Interface, will use one unified Spark instance.
  • Python 3.8 or 3.9
  • Font families installed on each server where Incorta will be installed: Lucida Grande, Lucida Sans Unicode, Verdana, Arial, Helvetica, Sans-serif
    Note

    Install any other font you may need in your business.

  • (Incorta Excel Add-in only) Microsoft Excel 2013
  • (Incorta Excel Add-in only) Microsoft Excel Plugin, Version 16.8.1
Spark 3.x

Spark 3.x requires a tmp directory with read, write, and execute permissions. You need also to specify this directory in the CMC and the spark-env.sh file.

  1. Create a new tmp directory with the required permissions or use the <InstallationPath>/IncortaNode/spark/tmp directory.
  2. Add the following configurations to this file <InstallationPath>/IncortaNode/spark/conf/spark-env.sh:
    SPARK_WORKER_OPTS="-Djava.io.tmpdir=<DirWithPremissions>"
    SPARK_LOCAL_DIRS=<DirWithPremissions>
  3. In the CMC > Server Configurations > Spark Integration > Extra options for Materialized views and notebooks, add the following options:
    spark.driver.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions>;spark.executor.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions>
  4. In the CMC > Server Configurations > Spark Integration > SQL App extra options, add the following options:
    spark.driver.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions> -Dorg.xerial.snappy.tempdir=<DirWithPremissions>;spark.executor.extraJavaOptions=-Djava.io.tmpdir=<DirWithPremissions> -Dorg.xerial.snappy.tempdir=<DirWithPremissions>

Make sure to replace <DirWithPremissions> with the tmp folder that Spark uses, whether a directory you create with the required permissions or <InstallationPath>/IncortaNode/spark/tmp.

Database Requirements

The Incorta Direct Data Platform requires one of the following RDBMS for the Incorta metadata database:

  • MySQL (8)
  • Oracle 12c and 19c
New customers and new installation considerations

New installations will not come with the MySQL driver as part of the installation package. You will need to provide your own MySQL driver. Existing customers, when upgrading existing instances to 2024.1.3 or later on-Premises releases, will not experience any change of behavior .

For details about how to install your MySQL driver, refer to Guides → Install MySQL Driver.

When you install the Incorta Direct Data Platform on an Oracle or MySQL database, the user needs to be granted certain privileges in order to complete the installation successfully. If these privileges are not granted, users can experience database authorization issues during the installation process. Refer to the following table for the minimum required privileges.

OracleMySQL
CONNECTCONNECT
ALTER TABLEALTER TABLE
CREATE TABLECREATE TABLE
INSERTINSERT
CREATE INDEXCREATE INDEX
CREATE OR REPLACE SYNONYMDROP TABLE
CREATE OR REPLACE TRIGGER

Incorta currently uses 0000-00-00 00:00:00 as default creation date. This value is not permitted in the recent versions of MySQL. You must disable the two modes: NO_ZERO_DATE and NO_ZERO_IN_DATE by adding the following line at the end of the mysql.cnf file:

sql-mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

Important

You must restart the MySQL service and re-log in to MySQL.

Warning

The time zones of the Incorta server and the metadata database server should be the same to avoid errors when creating or editing schema versions.

Browser Requirements

You can use Incorta on the following browsers:

  • Chrome
  • Safari
  • Firefox

Port Requirements

The following table is a list of the ports required by the Incorta Direct Data Platform at startup. Using these ports will significantly help avoid startup issues. You set up some of these ports during the installation process. Others are fixed values and cannot be changed. Using the recommended ports will significantly help avoid startup issues.

Certain ports must be open and reachable through the network, and these are indicated in the table below.

The table below references file names. You can find the catalina.properties file and the server.xml file at the path: <INSTALLATION_PATH>/IncortaNode/services/<SERVICE_FOLDER>/conf/. Other files mentioned in the table begin can be found under: <INSTALLATION_PATH>/IncortaNode/.

Port NumberAccess TypePurposeInstall Parameter?Where to change itNotes
80Incoming/ OutgoingHTTP traffic Apache Web Server (if installed)NAdmin TaskIf installing Apache, ports 80 and 443 should be open by default.
2181InternalZookeeperN/zookeeper/conf/zoo.cfgDO NOT CHANGE.Internal coordinator of High Availability (HA). Incoming and outgoing traffic goes through this port. Change this port only if you understand how Zookeeper interacts with Incorta.
4040-4045Incoming/OutgoingJob Detail Web portsN/A
4500InternalNode Agent PortY/nodeAgent/nodeAgent.cfgInstalled on each node to connect that node to the CMC
5442InternalSQL Interface (SQLi) portNTMT/Cluster Management Console (CMC)If the client (e.g., Tableau) exists on a remote server, this port must be open for remote access.
5436Incoming/ OutgoingIncorta (memory)NTMT/Cluster Management Console (CMC)If the client (e.g., Tableau) exists on a remote server, this port must be open for remote access.
8005Incoming/ OutgoingTomcat shutdown portY/services/ <SERVICE_FOLDER>/conf
8080Incoming/ OutgoingTomcat HTTP portYserver.xml
8443Incoming/ OutgoingHTTPS traffic, Tomcat HTTPS for SSLYserver.xml
8009Incoming/ OutgoingTomcat AJP portYserver.xml
6060Incoming/ OutgoingHTTP PortYcatalina.properties
6443Incoming/ OutgoingHTTP/AJP redirect PortYcatalina.properties
6005Incoming/ OutgoingServer PortYcatalina.properties
6009Incoming/ OutgoingAJP PortYcatalina.properties
7077Incoming/ OutgoingSpark Master PortNSpark configurationIf Spark exists on a remote server, this port must be open for remote access.
7078Incoming/ OutgoingSpark Worker PortNSpark configurationIf Spark exists on a remote server, this port must be open for remote access.
7777Incoming/ OutgoingAccessed locally by the Incorta Analytics Server Phantom JSN/start-exportserver.shDO NOT CHANGE.This port is currently hard-coded in the server. Any changes will break the send-dashboard-by-email feature.
9091Incoming/ OutgoingSpark Master Web UI PortNspark-env.shFor Spark master, this port must be open for remote access to monitor the Spark jobs and logs.
9092Incoming/ OutgoingSpark Worker Web UI PortNspark-env.shFor Spark worker, this port must be open for remote access to monitor the Spark jobs and logs.
30000+Incoming/OutgoingJob portsN/ASpark dynamically selects ports in the high range. See troubleshooting section for more information.

Additional Considerations

  • The Shutdown Port 8005 is the shutdown port for the Incorta Direct Data Platform, and it needs to be accessed by incoming and outgoing data. This port can be configured during the installation process, or changed in the catalina.properties file.
  • The HTTP Port 8080 can be configured during the installation process. If it is configured on the Incorta Direct Data Platform, then it should be made available at startup. You can change the value in the catalina.properties file.
  • The HTTPS Port 8443 can be configured during the installation process, or changed in the server.xml file.
  • The AJP Connector Port 8009 is the Apache Web Server port. It can be configured during the installation process, or changed in the server.xml file.