JDBC Connection

The JDBC connection enables the connection to a relational database for which no specific connection type is available. This connection type uses the JDBC driver URL provided by the database manufacturer. Supported relational databases may also be used in this connection type to modify the URL connection string in a very flexible way. See Systems Supported by Jedox Integrator for URL prefixes and driver classes.

Settings

URL The URL JDBC connection string. The correct syntax of the URL should be found in the documentation of the database vendor.
User name User name for the connection to the database (optional).
Password Password for the connection to the database (optional).
Driver class The Java class of the JDBC driver. This setting is necessary for stable usage of the JDBC driver.

Note: Additional JDBC parameters must be part of the Connection URL. Make sure you use the correct separator: ; or &.

Integration of the JDBC driver

Jedox Cloud customers should contact Jedox Customer Portal for details on integrating with JDBC.

For on-premises installations, the JDBC driver's .jar file must be copied into the Jedox Integrator installation directory: .../tomcat/webapps/etlserver/WEB-INF/lib_external (Windows) or .../tomcat-etl/webapps/etlserver/WEB-INF/lib_external (Linux). The JedoxSuiteTomcatService has to be restarted afterward.

Here is a list of some popular JDBC drivers, and the class name that needs to be used:

Database

Driver class

JDBC URL prefix

JDBC jar filename

Link

Amazon Redshift

com.amazon.redshift.jdbc4.Driver

jdbc:redshift://

RedshiftJDBC4.jar

https://s3.amazonaws.com/redshift-downloads/drivers/jdbc/2.1.0.30/redshift-jdbc42-2.1.0.30.jar

Apache SOLR

org.apache.solr.client.solrj.io.sql.DriverImpl

jdbc:solr//

N/A

http://lucene.apache.org/solr/

Firebird SQL

org.firebirdsql.jdbc.FBDriver

jdbc:firebirdsql://

jaybird-full-xxx.jar

http://www.firebirdsql.org/en/jdbc-driver/

Greenplum

org.postgresql.Driver

jdbc:postgresql://

postgresql-8.x-xxx.jdbc4.jar

http://jdbc.postgresql.org/download.html

Informix

com.informix.jdbc.IfxDriver

jdbc:informix-sqli://

ifxjdbc.jar

https://www.ibm.com/support/pages/download-informix-products

Netezza

org.netezza.Driver

jdbc:netezza://

N/A

http://www.netezza.com

Pervasive

com.pervasive.jdbc.v2.Driver

jdbc:pervasive://

N/A

http://www.pervasivedb.com/download/Pages/PDBDownloads. aspx

SAP SQL Anywhere

com.sybase.jdbc4.jdbc.SybDriver

jdbc:sybase:Tds:

N/A

https://www.sap.com/products/sql-anywhere.html

Teradata

com.teradata.jdbc.TeraDriver

jdbc:teradata://

terajdbc4.jar

http://downloads.teradata.com/download/connectivity/jdbc-driver

Vertica

com.vertica.Driver

jdbc:vertica://

N/A

http://www.vertica.com/support/myvertica/

Disclaimer: these drivers are not tested with Jedox Integrator or Jedox Cloud. The list is not complete and not necessarily up to date. The customer is responsible for the driver's provisioning and licensing.

Before a Jedox update, the customer must check the compatibility of the driver with the newer version of Jedox. Jedox cannot guarantee that the previous driver will still work after an update.

Notes:

  • User and password credentials are the only supported form of authentication for the JDBC connection, regardless of the type(s) of authentication supported in the source / target system of the connection.

  • For on-premises installations, it's also possible to use a custom JDBC driver for other connection types which are based on a relational connection. In this case, the custom JDBC driver replaces the shipped JDBC driver for these connection types. The connection must then be set to external in component.xml, for example:

Copy 
<component name="Mysql" class="com.jedox.etl.components.connection.MySQLConnection">
<parameter name="external">true</parameter>

  • The JDBC connection only allows read access (extract types Relational and RelationalTable) and usage in load type RelationalSQL. "Relational" type loads are not allowed.

 

Updated December 20, 2024