![]() |
VOOZH | about |
Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic. When paired with the CData JDBC Driver for Google Analytics, NiFi can work with live Google Analytics data. This article describes how to connect to and query Google Analytics data from an Apache NiFi Flow.
With built-in optimized data processing, the CData JDBC driver offers unmatched performance for interacting with live Google Analytics data. When you issue complex SQL queries to Google Analytics, the driver pushes supported SQL operations, like filters and aggregations, directly to Google Analytics and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze Google Analytics data using native data types.
Copy the CData JDBC Driver JAR file (and license file if it exists), cdata.jdbc.googleanalytics.jar (and cdata.jdbc.googleanalytics.lic), to the Apache NiFi lib subfolder, for example, C:\nifi-1.3.0-bin\nifi-1.3.0\lib.
On Windows, the default location for the CData JDBC Driver is C:\Program Files\CData\CData JDBC Driver for Google Analytics.
Start Apache NiFi by running the run-nifi.bat file in bin subfolder, for example, C:\nifi-1.3.0-bin\nifi-1.3.0\bin.
(OR)
Use the command prompt to navigate to the particular directory and run the run-nifi.bat file for example:
cd C:\nifi-1.3.0-bin\nifi-1.3.0\bin .\run-nifi.bat
Navigate to the Apache NiFi UI in your web browser: It should be https://localhost:8443/nifi.
Note: If users are utilizing an older version of Apache NiFi, they should access it via http://localhost:8080/nifi. In earlier versions, HTTP was the protocol employed. However, in the most recent version, HTTPS is the standard. By default, HTTP operates on port 8080, while HTTPS uses port 8443.
When accessing Apache NiFi via a URL, it prompts you to enter a username and password for login.
π Enter Username and Password for loginTo retrieve login credentials, users should consult the 'App.log' file located within the log directory of their NiFi installation. This file typically contains the necessary details for accessing the NiFi interface.
π Retrieve login credentials from App.log fileFill in the properties:
For assistance in constructing the JDBC URL, use the connection string designer built into the Google Analytics JDBC Driver. Either double-click the JAR file or execute the JAR file from the command-line.
java -jar cdata.jdbc.googleanalytics.jar
Fill in the connection properties and copy the connection string to the clipboard.
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, set Profile to the profile you want to connect to.
This can be set to either the Id or website URL for the Profile. If not specified, the first Profile returned will be used.
π Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
Your Google Analytics data is now available for use in Apache NiFi. For example, you can use the DBCPConnection Pool as the source for a QueryDatabaseTable processor (shown below).
π Configuring a QueryDatabaseTable processor to access Google Analytics data.Download a free, 30-day trial of the CData JDBC Driver for Google Analytics and start working with your live Google Analytics data in Apache NiFi. Reach out to our Support Team if you have any questions.
Download a free trial of the Google Analytics Driver to get started:
Download NowLearn more:
π Google Analytics IconAn easy-to-use database-like interface for Java based applications and reporting tools access to live Google Analytics data (Traffic, Users, Referrals, Geo, Behaviors, and more).