1. Home
  2. On-premises 5.2
  3. Guides
    1. Start
    2. Administer
    3. Analyze
    4. Configure
    5. Deploy
    6. Install
      1. Installation Requirements
      2. Install on a Single Node
      3. Finish Installing Incorta with the CMC
      4. Installation Troubleshooting
      5. Install in the Cloud
    7. Migrate
    8. Secure
    9. Upgrade
    10. Content Manager
  4. Tours
  5. Concepts
  6. Tools
  7. References
  8. Integrations
  9. Data applications
  10. Releases

Install Incorta

Before you install the Incorta Direct Data Platform, consider:

How many servers will you need?

The Incorta Direct Data Platform can be installed on one host with a single Incorta HA Node (single-node, "Typical" installation) or on two or more hosts (multi-node, also known as a “Custom” installation). For more about installing Incorta on one host, see Single-node Installations.

Note

"Typical" installation is not recommended for production environments, as you cannot extend a typical installation to include more nodes or services in the future.

For how to install a multi-node Incorta cluster, review the AWS High Availability Incorta Cluster Guide

Note

If this is your first time installing Incorta, we recommend starting with the example single-host installation as a test run.

Should you use the bundled packages?

Incorta leverages a couple of popular open-source packages which are, by default, bundled with the installation. We recommend you use these bundled versions that come with Incorta. It is also possible to use existing instances of these packages if required in your environments:

  • Zookeeper
  • Spark

Does your host meet Incorta installation requirements?

See Installation Requirements.

Concepts in Incorta Installation

Incorta uses the following terms in specific ways during the installation process:

  • Cluster Management Console (CMC). The CMC manage nodes, clusters, services, and tenants in the Incorta Direct Data Platform.
  • Analytics Service. Manages the Incorta UI, processes queries sent from Incorta, and manages report schedules and data and image exports.
  • Loader Service. Manages data loading activities, creates Parquet files, and creates materialized views.
  • Incorta Node. A physical or virtual server on which you install at least one Incorta service (analytics or loader service). During installation, you log into a hosts, install Incorta, and identify which services that the Incorta Node manages. You can set up HTTP ports, heap size, email configurations, Spark settings, and administrator credentials on an Incorta Node.
  • Incorta Node Agent. A lightweight process that manages the communication between the CMC and an Incorta node. Each node connects to only one node agent.
  • Incorta Cluster. A grouping of Incorta nodes. You can configure which services reside on which nodes within a cluster.
  • Incorta Tenant. A organizational unit that isolates and separates users, groups, schemas, business schemas, alerts, schedules, session variables, and data sources from other tenants.. Each Incorta installation can support many tenants, and you choose the tenant to use when you sign in to Incorta.