ETL Authorize.Net in Oracle Data Integrator

Leverage existing skills by using the JDBC standard to connect to Authorize.Net: Through drop-in integration into ETL tools like Oracle Data Integrator (ODI), the CData JDBC Driver for Authorize.Net connects real-time Authorize.Net data to your data warehouse, business intelligence, and Big Data technologies.

JDBC connectivity enables you to work with Authorize.Net just as you would any other database in ODI. As with an RDBMS, you can use the driver to connect directly to the Authorize.Net APIs in real time instead of working with flat files.

This article walks through a JDBC-based ETL -- Authorize.Net to Oracle. After reverse engineering a data model of Authorize.Net entities, you will create a mapping and select a data loading strategy -- since the driver supports SQL-92, this last step can easily be accomplished by selecting the built-in SQL to SQL Loading Knowledge Module.

Install the Driver

To install the driver, copy the driver JAR and .lic file, located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\Roaming\odi\agent\lib

Restart ODI to complete the installation.

Reverse Engineer a Model

Reverse engineering the model retrieves metadata about the driver's relational view of Authorize.Net data. After reverse engineering, you can query real-time Authorize.Net data and create mappings based on Authorize.Net tables.

1. In ODI, connect to your repository and click New -> Model and Topology Objects.
2. On the Model screen of the resulting dialog, enter the following information:
   • Name: Enter AuthorizeNet.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter AuthorizeNet.
   • Context: Select Global.
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter AuthorizeNet.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.authorizenet.AuthorizeNetDriver
   • URL: Enter the JDBC URL containing the connection string.

     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.

     Below is a typical connection string:

     jdbc:authorizenet:LoginId=MyLoginId;TransactionKey=MyTransactionKey;
4. On the Physical Schema screen, enter the following information:
   • Name: Select from the Drop Down menu.
   • Database (Catalog): Enter CData.
   • Owner (Schema): If you select a Schema for Authorize.Net, enter the Schema selected, otherwise enter AuthorizeNet.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Authorize.Net, enter the Schema selected, otherwise enter AuthorizeNet.
5. In the opened model click Reverse Engineer to retrieve the metadata for Authorize.Net tables.

Edit and Save Authorize.Net Data

After reverse engineering you can now work with Authorize.Net data in ODI. To view Authorize.Net data, expand the Models accordion in the Designer navigator, right-click a table, and click View data.

Create an ETL Project

Follow the steps below to create an ETL from Authorize.Net. You will load SettledBatchList entities into the sample data warehouse included in the ODI Getting Started VM.

1. Open SQL Developer and connect to your Oracle database. Right-click the node for your database in the Connections pane and click new SQL Worksheet.

   Alternatively you can use SQLPlus. From a command prompt enter the following:

   sqlplus / as sysdba
2. Enter the following query to create a new target table in the sample data warehouse, which is in the ODI_DEMO schema. The following query defines a few columns that match the SettledBatchList table in Authorize.Net: CREATE TABLE ODI_DEMO.TRG_SETTLEDBATCHLIST (TOTALCHARGE NUMBER(20,0),MarketType VARCHAR2(255));
3. In ODI expand the Models accordion in the Designer navigator and double-click the Sales Administration node in the ODI_DEMO folder. The model is opened in the Model Editor.
4. Click Reverse Engineer. The TRG_SETTLEDBATCHLIST table is added to the model.
5. Right-click the Mappings node in your project and click New Mapping. Enter a name for the mapping and clear the Create Empty Dataset option. The Mapping Editor is displayed.
6. Drag the TRG_SETTLEDBATCHLIST table from the Sales Administration model onto the mapping.
7. Drag the SettledBatchList table from the Authorize.Net model onto the mapping.
8. Click the source connector point and drag to the target connector point. The Attribute Matching dialog is displayed. For this example, use the default options. The target expressions are then displayed in the properties for the target columns.
9. Open the Physical tab of the Mapping Editor and click SETTLEDBATCHLIST_AP in TARGET_GROUP.
10. In the SETTLEDBATCHLIST_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load Authorize.Net data into Oracle.