Access Google Translate Data in Mule Applications Using the CData JDBC Driver

The CData API Driver for JDBC connects Google Translate data to Mule applications enabling read functionality with familiar SQL queries. The JDBC Driver allows users to easily create Mule applications to backup, transform, report, and analyze Google Translate data.

This article demonstrates how to use the CData API Driver for JDBC inside of a Mule project to create a Web interface for Google Translate data. The application created allows you to request Google Translate data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData JDBC Driver to create a Web interface for the hundreds of available data sources.

1. Create a new Mule Project in Anypoint Studio.
2. Add an HTTP Connector to the Message Flow.
3. Configure the address for the HTTP Connector.
4. Add a Database Select Connector to the same flow, after the HTTP Connector.
5. Create a new Connection (or edit an existing one) and configure the properties.
   • Set Connection to "Generic Connection"
   • Select the CData JDBC Driver JAR file in the Required Libraries section (e.g. cdata.jdbc.api.jar).
   • Set the URL to the connection string for Google Translate

     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

     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.

   • Set the Driver class name to cdata.jdbc.api.APIDriver.
   • Click Test Connection.
6. Set the SQL Query Text to a SQL query to request Google Translate data. For example:

   SELECT LanguageCode, DisplayName FROM SupportedLanguages WHERE ProjectId = 'my-project-12345'

   
7. Add a Transform Message Component to the flow.
8. Set the Output script to the following to convert the payload to JSON:

   %dw 2.0
   output application/json
   ---
   payload
           

   
9. To view your Google Translate data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The Google Translate data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with Google Translate data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the JDBC Driver for Google Translate and see the CData difference in your Mule Applications today.