ETL Adobe Target in Oracle Data Integrator

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

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

This article walks through a JDBC-based ETL -- Adobe Target to Oracle. After reverse engineering a data model of Adobe Target 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 (cdata.jdbc.adobetarget.jar) and .lic file (cdata.jdbc.adobetarget.lic), located in the installation folder, into the ODI appropriate directory:

• UNIX/Linux without Agent: ~/.odi/oracledi/userlib
• UNIX/Linux with Agent: ~/.odi/oracledi/userlib and $ODI_HOME/odi/agent/lib
• Windows without Agent: %APPDATA%\Roaming\odi\oracledi\userlib
• Windows with Agent: %APPDATA%\odi\oracledi\userlib and %APPDATA%\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 Adobe Target data. After reverse engineering, you can query real-time Adobe Target data and create mappings based on Adobe Target 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 AdobeTarget.
   • Technology: Select Generic SQL (for ODI Version 12.2+, select Microsoft SQL Server).
   • Logical Schema: Enter AdobeTarget.
   • Context: Select Global.
   
3. On the Data Server screen of the resulting dialog, enter the following information:
   • Name: Enter AdobeTarget.
   • Driver List: Select Oracle JDBC Driver.
   • Driver: Enter cdata.jdbc.adobetarget.AdobeTargetDriver
   • URL: Enter the JDBC URL containing the connection string.

     To connect to Adobe Target, you must provide the Tenant property along with OAuth connection properties mentioned below. Note that while other connection properties can influence processing behavior, they do not affect the ability to connect.

     To determine your Tenant name:

     1. Log in to Adobe Experience. The URL will look similar to: "https://experience.adobe.com/#/@mycompanyname/preferences/general-section".
     2. Extract the value after the "/#/@". In this example, it is "mycompanyname".
     3. Set the Tenant connection property to that value.

     User Accounts (OAuth)

     You must set AuthScheme to OAuthClient for all user account flows.

     Note: Adobe authentication via OAuth requires updating your token every two weeks.

     All Applications

     CData provides an embedded OAuth application that simplifies OAuth authentication. Alternatively, you can create a custom OAuth application. Review Creating a Custom OAuth App in the Help documentation for more information.

     Obtaining the OAuth Access Token

     Set the following properties to connect:

     • InitiateOAuth: Set to GETANDREFRESH to automatically perform the OAuth exchange and refresh the OAuthAccessToken as needed.
     • OAuthClientId : Set to the client Id assigned when you registered your app.
     • OAuthClientSecret : Set to the client secret assigned when you registered your app.
     • CallbackURL : Set to the redirect URI defined when you registered your app. For example: https://localhost:3333

     With these settings, the provider obtains an access token from Adobe Target, which it uses to request data. The OAuth values are stored in the location specified by OAuthSettingsLocation, ensuring they persist across connections.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.adobetarget.jar
     

     Fill in the connection properties and copy the connection string to the clipboard.

     

     Below is a typical connection string:

     jdbc:adobetarget:Tenant=mycompanyname;InitiateOAuth=GETANDREFRESH
     

   
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 Adobe Target, enter the Schema selected, otherwise enter AdobeTarget.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Adobe Target, enter the Schema selected, otherwise enter AdobeTarget.
   
5. In the opened model click Reverse Engineer to retrieve the metadata for Adobe Target tables.

Edit and Save Adobe Target Data

After reverse engineering you can now work with Adobe Target data in ODI. To view Adobe Target 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 Adobe Target. You will load Activities 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 Activities table in Adobe Target:

   CREATE TABLE ODI_DEMO.TRG_ACTIVITIES (NAME NUMBER(20,0),Id 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_ACTIVITIES 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_ACTIVITIES table from the Sales Administration model onto the mapping.
7. Drag the Activities table from the Adobe Target 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 ACTIVITIES_AP in TARGET_GROUP.
10. In the ACTIVITIES_AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab.

You can then run the mapping to load Adobe Target data into Oracle.