Connect to Google Translate Data from a Connection Pool in Jetty

The CData JDBC driver for Google Translate is easy to integrate with Java Web applications. This article shows how to efficiently connect to Google Translate data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Google Translate in Jetty.

Configure the JDBC Driver for Salesforce as a JNDI Data Source

Follow the steps below to connect to Salesforce from Jetty.

1. Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:

   java -jar ../start.jar --add-to-startd=jndi
   

2. Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.

3. Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the Google Translate data source at the level of the Web app, in WEB-INF\jetty-env.xml.

   <Configure id='googletranslatedemo' class="org.eclipse.jetty.webapp.WebAppContext">
    <New id="googletranslatedemo" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg><Ref refid="googletranslatedemo"/></Arg>
    <Arg>jdbc/googletranslatedb</Arg>
    <Arg>
    <New class="cdata.jdbc.api.APIDriver">
    <Set name="url">jdbc:api:</Set>
    <Set name="Profile">C:\profiles\GoogleTranslate.apip</Set>
    <Set name="AuthScheme">OAuth</Set>
    <Set name="InitiateOAuth">GETANDREFRESH</Set>
    <Set name="OAuthClientId">your_client_id</Set>
    <Set name="OAuthClientSecret">your_client_secret</Set>
    <Set name="CallbackUrl">your_callback_url</Set>
    </New>
    </Arg>
    </New>
   </Configure>
   

   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

4. Configure the resource in the Web.xml:

    jdbc/googletranslatedb
    javax.sql.DataSource
    Container
   
   

5. You can then access Google Translate with a lookup to java:comp/env/jdbc/googletranslatedb:

   InitialContext ctx = new InitialContext();
   DataSource mygoogletranslate = (DataSource)ctx.lookup("java:comp/env/jdbc/googletranslatedb");
   

More Jetty Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.