Connecting to JDBC


1. Overview

The JDBC generic data provider option lets you connect to data sources that have a JDBC driver. Since there are drivers available for a wide range of database systems, this means that Dundas BI has the ability to connect to numerous types of data sources out-of-the-box. Using JDBC is a viable alternative to writing a custom data provider, which requires programming expertise.

Here are some examples of data sources that have a JDBC driver:

  • Amazon Athena (Amazon S3)
  • Apache Phoenix
  • Hive
  • Impala
  • H2
  • Confluence

There are some limitations to be aware of when connecting via ODBC. See Dundas BI - Product Notes for more details.

There is a wide range of available third-party JDBC drivers, each of which may have different levels of quality and compatibility with Dundas BI. Even for the example data sources listed above, Dundas cannot guarantee any specific third-party JDBC driver will work perfectly with Dundas BI. If you do encounter connection issues with a specific driver, feel free to contact Dundas Support and we'll do our best to help you investigate the problem.

2. Install

3. Connect

Set up a Data Connector in Dundas BI to connect to your data with a JDBC driver.

From the main menu, click New, and then select Data Connector.

In the New Data Connector dialog, click inside the File Name box. Enter a name for your data connector.

Click the data Provider dropdown and choose JDBC.

Create a new data connector for JDBC
Create a new data connector for JDBC

 Next, supply the required credentials:

  1. Enter the JDBC URL. This will be different for every database and depends on the JDBC driver. For example, the JDBC URL for Amazon Athena is jdbc:awsathena://
  2. Enter the User Name for your database account.
  3. Enter the Password for your database account.

3.1. Driver Properties

Some connection properties cannot be included directly in the JDBC URL and have to be provided separately, in this field. Similar to the URL, the list of properties and their format are different for each database and are typically documented by the JDBC driver provider.

For example, as documented by Amazon, the Amazon Athena JDBC driver can take parameters as part of the JDBC URL:


But also requires the s3_staging_dir to indicate a location to which the query output is written:


Provide driver properties that cannot be included in the URL
Provide driver properties that cannot be included in the URL

3.2. Driver Class Name

Older JDBC drivers may require a class name to enable the classes in the JAR file. For example, the main JDBC driver class for Amazon Athena is com.amazonaws.athena.jdbc.AthenaDriver.

4. Java VM Path

Some JDBC drivers require additional binary libraries (examples include the DB2 and SQL Server databases when using Windows Authentication).

To indicate the location of such libraries, click Admin from the main menu and select Config from the Setup section.

Enable Show Advanced Settings.

Find the configuration setting JVM Library Path and edit it to indicate the folder path.

Indicate the path to libraries that are used by the JDBC drivers
Indicate the path to libraries that are used by the JDBC drivers

5. See also

Dundas Data Visualization, Inc.
500-250 Ferrand Drive
Toronto, ON, Canada
M3C 3G8

North America: 1.800.463.1492
International: 1.416.467.5100

Dundas Support Hours: 7am-6pm, ET, Mon-Fri