Install a New Zoomdata Instance
Provided below are the instructions for performing a clean installation of Zoomdata in your operating environment and is applicable for both RPM (CentOS, RHEL) and Ubuntu environments.
The installation process is automated and all you need to do is run an installer script. If installing via the installation script is not a viable option for you, you can manually install Zoomdata. This script accesses a dedicated Zoomdata repository (via the Internet) and automatically downloads all the necessary components to install your Zoomdata service. Once the installer script has completed execution, you need to (1) activate the Zoomdata services then (2) download and configure a JDBC driver if you are using one of the data sources listed below, and then (3) open a browser window and enter the specific IP address to access the Zoomdata Client. At a high level, the steps for installing are as follows:
Some SQL connectors require a JDBC driver to be configured before you can connect to your data source. You can download the driver from the vendor’s site. Be aware that you need to download and configure JDBC drivers for the following Zoomdata connectors:
If you are using one of the above data sources, you need to download and configure a JDBC driver as soon you finish the Zoomdata installation. For steps, see Adding a JDBC Driver.
RabbitMQ is used as the base for Zoomdata's streaming architecture. The installer script handles the installation and setup of RabbitMQ in your environment.
The installer script works for the following environments:
- Centos v6 and v7
- Ubuntu v14.04 and 16.04
- RHEL 6 and 7
Refer to System Requirements for the recommended settings for deploying Zoomdata on-premise.
The target server for the Zoomdata program should meet the following conditions:
- Server is connected to the Internet*
- The server does not have PostgreSQL already installed
- The server does not contain any zoomdata folders or property files (in other words, if a previous version of Zoomdata was installed in this server, ensure that all property files have been deleted before running the installer script)
- The user installing Zoomdata is able to use the 'sudo' command in the server
- *If you do not have internet connection on the server that Zoomdata is being installed, you either need to download or otherwise receive the Zoomdata installation package and load into the target server. Once this is done, you can manually install Zoomdata. Refer to the Alternative Installation Options for instructions to do this.
- If the server where Zoomdata is to be installed do not meet all of the conditions, refer to the Alternative Installation Options .
- If you are planning to use SQL-based connectors, then you need to download and configure a JDBC driver after the installation is complete
If you are installing Zoomdata in a server running either CentOS v6 or Ubuntu v14, then you need to Configure Max Open Processes and Open Files to Support Zoomdata Runtime . Be sure to complete this prerequisite setup before installing Zoomdata. If your server is running either CentOS v7 or Ubuntu v16, then you may skip this prerequisite step.
In addition, Zoomdata functionalities benefit from having time synchronization in your network. Specifically, Zoomdata leverages Network Time Protocol (NTPD), which performs time synchronization of networked servers to Coordinated Universal Time (UTC). If needed, refer to the article Using Network Time Protocol to Synchronize Time for instructions to set this up.
Once you have made any needed adjustments to your network configurations, return to this article to continue the installation process.
In order to begin the installation process, you first need to receive the installation instructions from Zoomdata Support. This email contains the installation script that you use to run in the server where the Zoomdata environment will reside.
You will receive an email from Zoomdata support with installation instructions and the command line that needs to be run. Enter the installation command into your target server to start the automated installation process. The following Zoomdata components are downloaded to your target server:
- Database for metadata store (using PostgreSQL v9.5)
- The Zoomdata Server
- Scheduler service
- Query Engine
- Upload service
- Connector services
The installation script also handles the installation and setup of RabbitMQ in your environment.
- Zoomdata uses a packaged PostgreSQL v9.5 database instance to store its metadata and strongly recommends using this instance due to the specific configuration and version employed. If you would like to use another PostgreSQL instance, contact for further guidance.
After the installation script has completed, it will take a few minutes for Zoomdata to complete its setup of the metadata store. Please wait a few minutes before accessing Zoomdata from your web browser. When you are ready to access Zoomdata, refer to the article Access Zoomdata from Your Web Browser .
Post Installation Options
By default, Zoomdata enables a http port. You can enabled https by following the steps in Configuring Zoomdata Property Files.
After Zoomdata has been installed, refer to the article Post Installation Options to set up additional features.
Logging Into Zoomdata and Resources for Using the Program
We recommend you log into Zoomdata in the browser using the 'supervisor' credentials first to review all the account-level features available. From this credential, you can activate an account to access all the 'admin' functions as well. For guidance, access the article Supervisor Functions.
You have the option to install Zoomdata without using the automated installation script. This approach lets you install and enable each Zoomdata services manually in your target server. If you need an alternative option, select from the following list:
- Installing Zoomdata manually
- Installing Zoomdata from a Tarball package (coming soon, until then contact Support for assistance )
Safari web browser: selecting any chart may result in a "Connection Closed" error. The error is a result of Zoomdata's self-signed certificate deployed on RPMs. The self-signed certificate is provided for convenience. To fix the issue, deploy your own SSL certificate on your Zoomdata installation. For the instructions, see Adding an SSL certificate to the Zoomdata Server .
Was this topic helpful?