Connect to Google Translate 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 API Driver for JDBC, Denodo users can work with live Google Translate data alongside other enterprise data sources. This article explains how to create a virtual data source for Google Translate in the Denodo Virtual DataPort Administrator.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Google Translate data. When you issue complex SQL queries to Google Translate, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Translate 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 Google Translate data using native data types.

Create the Google Translate Virtual Port

To connect to live Google Translate 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 API Driver for JDBC 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 API Driver for JDBC\lib\) to the Denodo external library directory (C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-api-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.
5. Configure the JDBC Connection:
   • Name: your choice, e.g.: api
   • Database adapter: Generic
   • Driver class path: C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-api-19
   • Driver class: cdata.jdbc.api.APIDriver

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

     jdbc:api:Profile=C:\profiles\GoogleTranslate.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;

     

     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 Google Translate JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     	java -jar cdata.jdbc.api.jar
     	

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

     Authentication

     Google Cloud Translation API requires OAuth 2.0 authentication to ensure secure access to translation services, datasets, glossaries, and adaptive MT resources. This authentication method allows you to securely connect to your Google Cloud project and manage translation resources with proper authorization.

     OAuth 2.0 Setup and Configuration

     Step 1: Create Google Cloud Project and Enable API

     To set up OAuth authentication:

     1. Visit the Google Cloud Console
     2. Create a new project or select an existing project
     3. Note down your Project ID (required for all API calls)
     4. Navigate to "APIs & Services" > "Library"
     5. Search for and enable the "Cloud Translation API"
     6. Go to "APIs & Services" > "Credentials"
     7. Click "Create Credentials" and select "OAuth Client ID"
     8. Configure the OAuth consent screen if prompted
     9. Select "Desktop application" or "Web application" as appropriate
     10. Set the authorized redirect URI (CallbackURL)
     11. Copy the Client ID and Client Secret for use in your connection

     Required Connection Properties

     • AuthScheme: Set this to OAuth (required)
     • OAuthClientId: Client ID from Google Cloud Console (required)
     • OAuthClientSecret: Client secret from Google Cloud Console (required)
     • CallbackURL: Redirect URI specified in your OAuth application (required)
     • InitiateOAuth: Set to GETANDREFRESH for automatic token management (recommended)
     • ProjectId: Your Google Cloud project ID or project number (required for queries)

     Required OAuth Scopes

     The Google Cloud Translation API Profile requires the following OAuth scope:

     • https://www.googleapis.com/auth/cloud-translation - Full access to Cloud Translation API resources including translation, datasets, glossaries, and adaptive MT
     
6. Click the "Test connection" button to confirm the configuration and click Save.

View Google Translate Data in the VirtualPort Administrator Tool

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

1. Click the "Create base view" button in the newly created VirtualPort (admin.API).
2. Expand the object tree and select the objects (tables) you wish to import.
3. Click the "Create selected" button to create views of the Google Translate 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_api_supportedlanguages) 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_api_supportedlanguages CONTEXT ('i18n'='us_est', 'cache_wait_for_load'='true')
   

   
7. Click Execute to view the data.

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

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