Ready to get started?

Learn more about the CData JDBC Driver for Authorize.Net or download a free trial:

Download Now

Bridge Authorize.Net Connectivity with Apache NiFi

Access and process Authorize.Net data in Apache NiFi using the CData JDBC Driver.

Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.. When paired with the CData JDBC Driver for Authorize.Net, NiFi can work with live Authorize.Net data. This article describes how to connect to and query Authorize.Net data from an Apache NiFi Flow.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Authorize.Net data. When you issue complex SQL queries to Authorize.Net, the driver pushes supported SQL operations, like filters and aggregations, directly to Authorize.Net 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 Authorize.Net data using native data types.

Connecting to Authorize.Net Data in Apache NiFi

  1. Download the CData JDBC Driver for Authorize.Net installer, unzip the package, and run the JAR file to install the driver.
  2. Copy the CData JDBC Driver JAR file (and license file if it exists), cdata.jdbc.authorizenet.jar (and cdata.jdbc.authorizenet.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 Authorize.Net.

  3. Start Apache NiFi. For example:

    cd C:\nifi-1.3.0-bin\nifi-1.3.0\bin
    run-nifi.bat
    
  4. Navigate to the Apache NiFi UI in your web browser: typically http://localhost:8080/nifi
  5. Click the (Configuration) button from the Operate sidebar.
  6. In the NiFi Flow Configuration page, navigate to the Controller Services tab.
  7. Click the button to create a new controller service.
  8. In the Add Controller Service page, select DBCPConnection Pool, and then click Add.
  9. Click the gear button to configure the new DBCPConnection Pool.
  10. In the Configure Controller Service page, navigate to the Properties tab. Fill in the properties:

    PropertyValue
    Database Connection URLjdbc:authorizenet:LoginId=MyLoginId;TransactionKey=MyTransactionKey;
    Database Driver Class Namecdata.jdbc.authorizenet.AuthorizeNetDriver

    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.

    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.
  11. Click the button to enable the new DBCPConnection Pool.

Your Authorize.Net data is now available for use in Apache NiFi. For example, you can use the DBCPConnection Pool as the source for a QueryDatabaseTable processor.

Download a free, 30-day trial of the CData JDBC Driver for Authorize.Net and start working with your live Authorize.Net data in Apache NiFi. Reach out to our Support Team if you have an questions.