Connect to AlloyDB Data in the Denodo Platform

Denodo Platform is a data virtualization product providing a single point of contact for enterprise database data. When paired with the CData JDBC Driver for AlloyDB, Denodo users can work with live AlloyDB data alongside other enterprise data sources. This article explains how to create a virtual data source for AlloyDB in the Denodo Virtual DataPort Administrator.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live AlloyDB data. When you issue complex SQL queries to AlloyDB, the driver pushes supported SQL operations, like filters and aggregations, directly to AlloyDB and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze AlloyDB data using native data types.

Create the AlloyDB Virtual Port

To connect to live AlloyDB data from Denodo, you need to copy the JDBC Driver JAR file to the external library directory for Denodo and create a new JDBC Data Source from the Virtual DataPort Administrator tool.

1. Download the CData JDBC Driver for AlloyDB installer, unzip the package, and run the JAR file to install the driver.
2. Copy the JAR File (and license file if it exists) from the installation location (typically C:\Program Files\CData\CData JDBC Driver for AlloyDB\lib\) to the Denodo external library directory (C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-alloydb-19).
3. Open the Denodo Virtual DataPort Administrator tool and navigate to the Server Explorer tab.
4. Right-click "admin" and select New -> Data source -> JDBC. 👁 Creating a new JDBC data source.
   
5. Configure the JDBC Connection:
   • Name: your choice, e.g.: alloydb
   • Database adapter: Generic
   • Driver class path: C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-alloydb-19
   • Driver class: cdata.jdbc.alloydb.AlloyDBDriver

   • Database URI: Set this to a JDBC URL using the necessary connection properties. For example,

     jdbc:alloydb:User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432

     👁 Configuring the JDBC connection (NetSuite is shown).
     

     Information on creating the Database URI follows:

     Built-In Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the AlloyDB JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     	java -jar cdata.jdbc.alloydb.jar
     	

     Fill in the connection properties and copy the connection string to the clipboard.

     The following connection properties are usually required in order to connect to AlloyDB.

     • Server: The host name or IP of the server hosting the AlloyDB database.
     • User: The user which will be used to authenticate with the AlloyDB server.
     • Password: The password which will be used to authenticate with the AlloyDB server.

     You can also optionally set the following:

     • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
     • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

     Authenticating with Standard Authentication

     Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

     No further action is required to leverage Standard Authentication to connect.

     Authenticating with pg_hba.conf Auth Schemes

     There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

     Find instructions about authentication setup on the AlloyDB Server here.

     Authenticating with MD5 Authentication

     This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

     Authenticating with SASL Authentication

     This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

     Authenticating with Kerberos

     The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos. 👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     

6. Click the "Test connection" button to confirm the configuration and click Save.

View AlloyDB Data in the VirtualPort Administrator Tool

After creating the data source, you can create a base view of AlloyDB data for use in the Denodo Platform.

1. Click the "Create base view" button in the newly created VirtualPort (admin.AlloyDB).
2. Expand the object tree and select the objects (tables) you wish to import. 👁 Selecting objects to import (NetSuite is shown).
   
3. Click the "Create selected" button to create views of the AlloyDB data.
   Optional: Click "Create associations from foreign keys" to define relationships between the objects.
4. With the view(s) created, navigate to a table (cdata_alloydb_orders) in the Server Explorer and double-click the selected table.
5. In the new tab, click "Execution panel" to open a query panel.
6. Customize the query in the "Execute" tab or use the default:

   SELECT * FROM cdata_alloydb_orders CONTEXT ('i18n'='us_est', 'cache_wait_for_load'='true')
   

   👁 Configuring the query to view the data.
   
7. Click Execute to view the data. 👁 Viewing the data.
   

With the base view created, you can now work with live AlloyDB data like you would any other data source in Denodo Platform, for example, querying AlloyDB in the Denodo Data Catalog.

Download a free, 30-day trial of the CData JDBC Driver for AlloyDB and start working with your live AlloyDB data in Denodo Platform. Reach out to our Support Team if you have any questions.