You are viewing content for 4.9 | 4.8 | 4.7 | 4.6 | 4.5 | 4.4 | 4.3 | Previous Releases


Install or Upgrade Incorta Analytics

Before you install Incorta, consider:

How many servers will you need?

Incorta can be installed on one server (single-node, also known as a “Typical” installation) or on two or more servers (multi-node, also known as a “Custom” installation). For more about installing Incorta on one server, see Single-node Installations.

For more about installing Incorta on two or more servers, see Multi-node Installation. If this is your first time installing Incorta, we recommend starting with the example single-node installation. See Example—Deploying a Single Node System.

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). An application bundled with Incorta Analytics used to manage nodes, clusters, services, and tenants.
  • 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 server, install Incorta, and identify which services the server hosts. 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 virtual instance of Incorta Analytics that isolates and separates an analytics application and data. Each Incorta installation can support many tenants, and you choose the tenant to use when you log in to Incorta.

Upgrades

For information on how to upgrade from version 4.2 or earlier, see Migration Upgrade from 3.x to 4.6. For information on how to upgrade from version 4.3 or later, see Migration Upgrade from 4.3 to 4.6. For information on troubleshooting and known issues during installation or upgrade, see Installation and Upgrade Troubleshooting.

To learn how to upgrade from a 3.x Incorta Release by migrating your Direct Data Mapping (snapshot) files, see Upgrade from 3.x to 4.6.

To learn how to upgrade from a 4.x Incorta Release using a fresh installation, which will reload all your data sources which may take a long time if you have a lot of data, see Upgrade from 4.x to 4.6.