Build Authorize.Net-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Authorize.Net enables users to access live Authorize.Net data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Authorize.Net data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from Authorize.Net to Google BigQuery,

Upload the CData JDBC Driver for Authorize.Net to Google Data Fusion

Upload the CData JDBC Driver for Authorize.Net to your Google Data Fusion instance to work with live Authorize.Net data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdataauthorizenet-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver 👁 Image
   
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.authorizenet) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.authorizenet.AuthorizeNetDriver)
   👁 Configuring the driver (Salesforce is shown.)
   
5. Click "Finish"

Connect to Authorize.Net Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Authorize.Net data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver 👁 Adding a database source
   
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-authorizenet)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Authorize.Net. For example:
     
     jdbc:authorizenet:RTK=5246...;LoginId=MyLoginId;TransactionKey=MyTransactionKey;

     You can obtain the necessary connection properties on the Security Settings -> General Settings page after logging into your Merchant Account.

     • UseSandbox: The Authorize.Net API to be used to process transactions. If you are using a production account, this property can be left blank. If you are using a developer test account, set this to 'TRUE'.
     • LoginID: The API login Id associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions. Note that this value is not the same as the login Id that you use to log in to the Merchant Interface.
     • TransactionKey: The transaction key associated with your payment gateway account. This property is used to authenticate that you are authorized to submit website transactions.

     Built-in Connection String Designer

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

      java -jar cdata.jdbc.authorizenet.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.)
     
   • Set Import Query to a SQL query that will extract the data you want from Authorize.Net, i.e.:
     SELECT * FROM SettledBatchList
   👁 Configuring the database source
   
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like authorizenet-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert Authorize.Net data into
   👁 Configuring the BigQuery sink
   

With the Source and Sink configured, you are ready to pipe Authorize.Net data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Authorize.Net and import it into Google BigQuery. 👁 Image

While this is a simple pipeline, you can create more complex Authorize.Net pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Authorize.Net and start working with your live Authorize.Net data in Google Data Fusion today.