Zoomdata Version

Adding a JDBC Driver

For certain data sources, the JDBC drivers needed are no longer included in to the installation package of Zoomdata. You need to provide your own JDBC driver for the following data sources:

Note, in releases prior to Zoomdata 2.6.5, Microsoft SQL Server also required providing your own JDBC driver. This requirement was lifted in Zoomdata 2.6.5.

This approach allows you the flexibility to add a specific JDBC driver that meets your licensing, support policies or operational needs. As a result, in order to connect to and visualize data from Zoomdata, you first need to download and install a JDBC driver.


If the JDBC driver for the Zoomdata connector is not configured, that particular connector server will not start up and the connector cannot be enabled within Zoomdata.

Refer to the article Managing Connectors in Zoomdata for additional information.

In the case where you are upgrading from a version before Zoomdata 2.5.3, this also means that any dashboards created using that particular data source are longer be available until the JDBC driver is installed and the connector enabled.

Install a JDBC Driver

In order to use any of the data sources listed above, perform the following steps to install the needed JDBC driver after successful installation of Zoomdata services:

  1. Download the required driver from the vendor’s site to the corresponding Zoomdata instance. Place the required driver in the following folder: /usr/local/share/java/zoomdata
    If this folder does not exist, you need to create it in the location mentioned above.
    See the following table for resources for vendor’s JDBC drivers.
Table 1
Connector Link to JDBC Driver License Type Supported Version
Microsoft SQL Server https://docs.microsoft.com/en-us/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-2017 Commercial 4.0.0
MemSQL http://central.maven.org/maven2/org/mariadb/jdbc/mariadb-java-client/1.3.2/mariadb-java-client-1.3.2.jar LGPL 1.3.2
MySQL http://central.maven.org/maven2/org/mariadb/jdbc/mariadb-java-client/1.3.2/mariadb-java-client-1.3.2.jar LGPL 1.3.2
Redshift* https://docs.aws.amazon.com/redshift/latest/mgmt/configure-jdbc-connection.html#download-jdbc-driver Commercial
Oracle https://www.oracle.com/technetwork/database/features/jdbc/jdbc-drivers-12c-download-1958347.html Commercial
Teradata http://downloads.teradata.com/download/connectivity/jdbc-driver Commercial

Keep in mind that the Zoomdata Administrator must have read-level access rights to the JDBC driver (JAR) file.

  1. Use the following command to access and open the configuration file:

vi /etc/zoomdata/edc-connector_name.properties

  • If you are not logged in as a root user, then you need to enter sudo vi /etc/zoomdata/edc-connector_name.properties in order to create the desired file.
  • If the configuration file does not exist, this command creates it.

  • Replace connector_name with the name of the data source driver you are configuring:
  • Table 2
    Connector Connector Property File Name
    Microsoft SQL Server edc-mssql.properties
    MemSQL edc-memsql.properties
    MySQL edc-mysql.properties
    Redshift* edc-redshift.properties
    Oracle edc-oracle.properties
    Teradata edc-teradata.properties

    1. In the edc-connector_name.properties file, add the following property:


    In case you need to add multiple paths, use a comma separated list:


    1. Save your changes to the properties file.
    2. Restart the corresponding connector by running the following command:

      • For CentOS 7 and Ubuntu v16:

        systemctl restart zoomdata-edc-connector_name

      • For CentOS 6 and Ubuntu v14:

        service zoomdata-edc-connector_name restart

    Once this is done, you need to log in as the supervisor, access the Connectors page and make sure that connector is enabled so that it appears in the Data Sources.

    After the JDBC driver has been configured and the connector enabled, users that have access privileges to connect Zoomdata to their data source will be able to do so from the Data Sources page.

    Be aware that Redshift requires more than one jar file for the JDBC Driver. Be sure to place these jars in the same location together.

Was this topic helpful?