Connect to Google Translate Data from a Connection Pool in JBoss

CData JDBC drivers can be configured in JBoss by following the standard procedure for connection pooling. This article details how to access Google Translate data from a connection pool in JBoss applications. This article details how to use the JBoss Management Interface to configure the CData JDBC Driver for Google Translate. You will then access Google Translate data from a connection pool.

Create a JDBC Data Source for Google Translate from the Management Console

Follow the steps below to add the driver JAR and define required connection properties.

1. In the Runtime menu, select the Domain or Server menu, depending on whether you are deploying to a managed domain or to a stand-alone server, and click "Manage deployments" to open the Deployments page.
2. Click Add. In the resulting wizard, add the JAR file and license for the driver, located in the lib subfolder of the installation directory. Finish the wizard with the defaults, select the driver, and click Enable.
3. In the Configuration menu, click Subsystems -> Connector -> Datasources. This opens the JDBC Datasources page.
4. Click Add and, in the resulting wizard, enter a name for the driver and the JNDI name. For example:

   java:jboss/root/jdbc/API

5. Select the driver that you added above.

6. Enter the JDBC URL and the username and password. The syntax of the JDBC URL is jdbc:api: followed by a semicolon-separated list of connection properties.

   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.

   

   A typical connection string is below:

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

7. Test the connection and finish the wizard. Select the Google Translate data source and click Enable.

More JBoss Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more information, refer to the Data Source Management chapter in the JBoss EAP documentation.