Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Configure the CData JDBC Driver for BigQuery in a Connection Pool in Tomcat
Connect to BigQuery data from 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 BigQuery data from a connection pool in Tomcat.
About BigQuery Data Integration
CData simplifies access and integration of live Google BigQuery data. Our customers leverage CData connectivity to:
- Simplify access to BigQuery with broad out-of-the-box support for authentication schemes, including OAuth, OAuth JWT, and GCP Instance.
- Enhance data workflows with Bi-directional data access between BigQuery and other applications.
- Perform key BigQuery actions like starting, retrieving, and canceling jobs; deleting tables; or insert job loads through SQL stored procedures.
Most CData customers are using Google BigQuery as their data warehouse and so use CData solutions to migrate business data from separate sources into BigQuery for comprehensive analytics. Other customers use our connectivity to analyze and report on their Google BigQuery data, with many customers using both solutions.
For more details on how CData enhances your Google BigQuery experience, check out our blog post: https://www.cdata.com/blog/what-is-bigquery
Getting Started
Connect to BigQuery Data through a Connection Pool in Tomcat
- 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.
- Add a definition of the resource to the context. Specify the JDBC URL here.
Google uses the OAuth authentication standard. To access Google APIs on behalf of individual users, you can use the embedded credentials or you can register your own OAuth app.
OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, you will need to register an application to obtain the OAuth JWT values.
In addition to the OAuth values, you will need to specify the DatasetId and ProjectId. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the BigQuery JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.googlebigquery.jar
Fill in the connection properties and copy the connection string to the clipboard.
You can see the JDBC URL specified in the resource definition below.
<Resource name="jdbc/googlebigquery" auth="Container" type="javax.sql.DataSource" driverClassName="cdata.jdbc.googlebigquery.GoogleBigQueryDriver" factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" url="jdbc:googlebigquery:DataSetId=MyDataSetId;ProjectId=MyProjectId;InitiateOAuth=GETANDREFRESH" maxActive="20" maxIdle="10" maxWait="-1" />
To allow a single application to access BigQuery 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 BigQuery for all applications.
- Add a reference to the resource to the web.xml for the application.
BigQuery data JSP jdbc/GoogleBigQuery javax.sql.DataSource Container -
Initialize connections from the connection pool:
Context initContext = new InitialContext(); Context envContext = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/GoogleBigQuery"); Connection conn = ds.getConnection();
More Tomcat Integration
The steps above show how to connect to BigQuery data in a simple connection pooling scenario. For more use cases and information, see the JNDI Datasource How-To in the Tomcat documentation.