8.0 Tutorials

You can translate the document:

Connecting from your application - JDBC Clients

JDBC (Java DataBase Connectivity) is a Java data access technology from Oracle Corporation. JDBC provides an API for the Java programming language for database-independent connectivity, and it is based on the use of drivers for each database. A client application requires separate drivers, usually vendor supplied, to connect to different types of databases.

Denodo includes a JDBC driver jar file named denodo-vdp-jdbcdriver.jar, and it is located under the <DENODO_HOME>/tools/client-drivers/jdbc/ directory.

Accessing Denodo using a JDBC client

In this section, you are going to see how to access to the Denodo server using a JDBC client. This information is valid for any Java-based application. For the example, we will use DBVisualizer (a generic database management tool for developers) but feel free to use any other JDBC client.

The first thing that you have to do when connecting using JDBC is to add the Denodo's JDBC driver to the client application.

To use the JDBC driver in your client, you have to add the .jar file to the classpath of your application.

In DBVisualizer, you have to go to Tools > Driver Manager... and in the Driver Manager window go to Driver > Create Driver and then browse to the VDP's driver file. Use the following driver settings and close the window to save the configuration:

  • Name: Denodo 8.0
  • URL Format: jdbc:vdb://<hostname>:<port>/<database>
  • Driver Class: com.denodo.vdp.jdbc.Driver
Create Driver

Now that you have added the driver, you can configure a connection to your Denodo virtual database. Go to Database > Create Database Connection and use the following settings for the connection:

  • Driver (JDBC): Denodo 8.0
  • Database URL: jdbc:vdb://localhost:9999/tutorial
  • Database Userid: admin
  • Database Password: admin
New connection

Click on the Connect button, and you will establish a connection to the tutorial database. In the left panel of the window, you will see that the base views are listed as tables and the derived views are listed as views.

If you run any query from the SQL Commander, you will get the same results that you were seeing before from the Administration Tool. Try, for example:

SELECT * FROM client

CODE
Query results