Installation Prerequisites


Due to the upgrade of the HashiCorp Consul (service discovery) version from 0.7.5 to 1.2.2, custom connectors built before Zoomdata 3.2 ( built for versions 3.1 or earlier versions) will not appear in Zoomdata after you migrate to Zoomdata 3.7. This is caused by incompatibilities between old connectors and the new Consul. To make your custom connectors compatible with Zoomdata 3.7 (and later versions), you must migrate them as described in Version 3.7 Custom Connector Migration Information.

This migration step is required only for custom connectors built with Zoomdata versions earlier than 3.2 or for connectors that were present before Zoomdata 3.2 but that are now deprecated (for example, the Hive on Tez connector, which was replaced by the Hive connector in Zoomdata 3.7).

If you have used Zoomdata versions earlier than 3.3, you must delete the RabbitMQ queues before you upgrade to Zoomdata 3.3 or later. In addition, an additional header specifying the media type on non-browser HTTP requests is now required. These changes are required because in Zoomdata version 3.3, we updated the Spring Cloud library underlying our application. See Version 3.3 Upgrade Information.
Zoomdata version 3.2 and later versions use headless Google Chrome instead of Firefox for Zoomdata's Screenshot service. The Chrome-based Screenshot service cannot be installed in CentOS v6 environments because the Google Chrome dependencies do not support that platform. See Setting Up the Screenshot Feature.

The installation script works in the following environments:

  • Centos v6 and v7
  • Ubuntu v14.04 and 16.04
  • RHEL 6 and 7

Read System Requirements and Sizing Guidelines for the recommended settings for deploying Zoomdata on-premises.

The target server for the Zoomdata software should meet the following prerequisites:

  • The server must be connected to the Internet.
  • The server must not have PostgreSQL already installed.
  • The server must not contain any zoomdata folders or Zoomdata property files from previous versions. If a previous version of Zoomdata was installed on this server, ensure that all property files have been deleted before running the installer script.
  • The user installing Zoomdata must be able to use the sudo command on the server.
  • If you do not have an internet connection on the server on which Zoomdata is being installed, download the Zoomdata installation package and load into the target server. Once this is done, you can manually install Zoomdata. See Alternative Installation Options.
  • If the server on which Zoomdata is to be installed does not meet all of the prerequisites, see Alternative Installation Options.

    If you are installing Zoomdata on a server running either CentOS v6 or Ubuntu v14, see Configuring the Maximum Number of Open Processes and Files. Be sure to complete this prerequisite setup before installing Zoomdata. If your server is running either CentOS v7 or Ubuntu v16, then you can skip this prerequisite step.

    In addition, Zoomdata benefits from having time synchronization in your network. Specifically, Zoomdata leverages the Network Time Protocol daemon (NTPD), which performs time synchronization of networked servers to Coordinated Universal Time (UTC). If needed, read Using the Network Time Protocol to Synchronize Time for instructions to set this up.

    Once you have made any needed adjustments to your network configurations, you can continue the installation process.