Configure the CData JDBC Driver for Google Campaign Manager 360 in a Connection Pool in Tomcat

The CData JDBC Drivers support standard JDBC interfaces to integrate with Web applications running on the JVM. This article details how to connect to Google Campaign Manager 360 data from a connection pool in Tomcat.

Connect to Google Campaign Manager 360 Data through a Connection Pool in Tomcat

1. Copy the CData JAR and CData .lic file to $CATALINA_HOME/lib. The CData JAR is located in the lib subfolder of the installation directory.
2. Add a definition of the resource to the context. Specify the JDBC URL here.

   Google Campaign Manager uses the OAuth authentication standard. The data provider facilitates OAuth in various ways as described below. The following OAuth flow requires the authenticating user to interact with DoubleClick Campaign Manager, using the browser. You can also use a service account to authenticate.

   For authentication guides, see the Getting Started section of the data provider help documentation.

   Built-in Connection String Designer

   For assistance in constructing the JDBC URL, use the connection string designer built into the Google Campaign Manager 360 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

   java -jar cdata.jdbc.googlecm.jar
   

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

   👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
   

   You can see the JDBC URL specified in the resource definition below.

   <Resource name="jdbc/googlecm" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.googlecm.GoogleCMDriver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:googlecm:UserProfileID=MyUserProfileID;InitiateOAuth=GETANDREFRESH;" maxActive="20" maxIdle="10" maxWait="-1" />
   

   To allow a single application to access Google Campaign Manager 360 data, add the code above to the context.xml in the application's META-INF directory.

   For a shared resource configuration, add the code above to the context.xml located in $CATALINA_BASE/conf. A shared resource configuration provides connectivity to Google Campaign Manager 360 for all applications.

3. Add a reference to the resource to the web.xml for the application.

    Google Campaign Manager 360 data JSP
    jdbc/GoogleCM
    javax.sql.DataSource
    Container
   
   

4. Initialize connections from the connection pool:

   Context initContext = new InitialContext();
   Context envContext = (Context)initContext.lookup("java:/comp/env");
   DataSource ds = (DataSource)envContext.lookup("jdbc/GoogleCM");
   Connection conn = ds.getConnection();
    

More Tomcat Integration

The steps above show how to connect to Google Campaign Manager 360 data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.