Google Translate Reporting and Star Schemas in OBIEE

The CData ODBC Driver for Google Translate is a standard database driver that can integrate real-time access to Google Translate data into your data warehouse or directly into your reporting tool. This article shows how to bypass the data warehouse and import operational Google Translate data into Oracle Business Intelligence Enterprise Edition (OBIEE).

See the knowledge base for ODBC integrations with ETL tools like Informatica PowerCenter. For an ETL solution into Oracle Warehouse Builder, use the driver with the Oracle ODBC Gateway to Access Google Translate Data as a Remote Oracle Database.

Connect to Google Translate as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Import Google Translate Metadata

Follow the steps below to use the OBIEE Client Tools to import Google Translate metadata into an OBIEE repository. You can then integrate Google Translate data into your business models.

1. Open the Administration Tool and click File -> New Repository.

2. In the Connection Type menu, select ODBC 3.5 and select the CData DSN.
3. Select the metadata types you want to import under the Relational Sources option and then select Google Translate tables.