![]() |
VOOZH | about |
You can use Hibernate to map object-oriented domain models to a traditional relational database. The tutorial below shows how to use the CData JDBC Driver for Google Ads to generate an ORM of your Google Ads repository with Hibernate.
Though Eclipse is the IDE of choice for this article, the CData JDBC Driver for Google Ads works in any product that supports the Java Runtime Environment. In the Knowledge Base you will find tutorials to connect to Google Ads data from IntelliJ IDEA and NetBeans.
Follow the steps below to install the Hibernate plug-in in Eclipse.
Follow the steps below to add the driver JARs in a new project.
Follow the steps below to configure connection properties to Google Ads data.
Input the following values:
Connection URL: A JDBC URL, starting with jdbc:googleads: and followed by a semicolon-separated list of connection properties.
Google uses the OAuth authentication standard. To access Google APIs on behalf on 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, register an application to obtain the OAuth JWT values.
In addition to the OAuth values, specify the DeveloperToken and ClientCustomerId.
See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
For assistance in constructing the JDBC URL, use the connection string designer built into the Google Ads JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.googleads.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.)A typical JDBC URL is below:
jdbc:googleads:DeveloperToken=MyDeveloperToken;ClientCustomerId=MyClientCustomerId;InitiateOAuth=GETANDREFRESH;
Follow the steps below to select the configuration you created in the previous step.
Follow the steps below to generate the reveng.xml configuration file. You will specify the tables you want to access as objects.
Follow the steps below to generate plain old Java objects (POJO) for the Google Ads tables.
One or more POJOs are created based on the reverse-engineering setting in the previous step.
For each mapping you have generated, you will need to create a mapping tag in hibernate.cfg.xml to point Hibernate to your mapping resource. Open hibernate.cfg.xml and insert the mapping tags as so:
cdata.googleads.GoogleAdsDriver jdbc:googleads:DeveloperToken=MyDeveloperToken;ClientCustomerId=MyClientCustomerId;InitiateOAuth=GETANDREFRESH; org.hibernate.dialect.SQLServerDialect
Using the entity you created from the last step, you can now search Google Ads data:
import java.util.*;
import org.hibernate.Session;
import org.hibernate.cfg.Configuration;
import org.hibernate.query.Query;
public class App {
public static void main(final String[] args) {
Session session = new
Configuration().configure().buildSessionFactory().openSession();
String SELECT = "FROM CampaignPerformance C WHERE Device = :Device";
Query q = session.createQuery(SELECT, CampaignPerformance.class);
q.setParameter("Device","'Mobile devices with full browsers'");
List<CampaignPerformance> resultList = (List<CampaignPerformance>) q.list();
for(CampaignPerformance s: resultList){
System.out.println(s.getDevice());
System.out.println(s.getClicks());
}
}
}
Download a free trial of the Google AdWords Driver to get started:
Download NowLearn more:
๐ Google AdWords IconAn easy-to-use database-like interface for Java based applications and reporting tools access to live Google AdWords data (Campaigns, AdGroups, Performance, and more).