ETL Oracle Eloqua Reporting in Oracle Data Integrator

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

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

This article covers a JDBC-based ETL -- Oracle Eloqua Reporting to Oracle. After reverse engineering a data model of Oracle Eloqua Reporting 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.oracleeloquareporting.jar) and .lic file (cdata.jdbc.oracleeloquareporting.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 Oracle Eloqua Reporting data. After reverse engineering, you can query real-time Oracle Eloqua Reporting data and create mappings based on Oracle Eloqua Reporting tables.

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

     Oracle Eloqua Reporting supports the following authentication methods:

     • Basic authentication (User and Password)
     • OAuth 2.0 code grant flow
     • OAuth 2.0 password grant flow

     Basic Authentication (User and Password)

     To perform authentication with a user and password, specify these properties:

     • AuthScheme: Basic.
     • Company: The company name associated with your Oracle Eloqua Reporting account.
     • User: Your login account name.
     • Password: Your login password.

     OAuth Authentication (Code Grant Flow)

     To authenticate with the OAuth code grant flow, you must set AuthScheme to OAuth and create a custom OAuth application. For information about how to create a custom OAuth application, see the Help documentation.

     Then set the following properties:

     • InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
     • OAuthClientId: The client Id assigned when you registered your application.
     • OAuthClientSecret: The client secret that was assigned when you registered your application.
     • CallbackURL: The redirect URI that was defined when you registered your application.

     When you connect, the driver opens Oracle Eloqua Reporting's OAuth endpoint in your default browser. Log in and grant permissions to the application. When the access token expires, the driver refreshes it automatically.

     OAuth Authentication (Password Grant Flow)

     With the OAuth password grant flow, you can use your OAuth application's credentials alongside your user credentials to authenticate without the need to grant permission manually via a browser prompt. You must create an OAuth app (see the Help documentation) to use this authentication method.

     Set the following properties:

     • AuthScheme: OAuthPassword
     • Company: The company's unique identifier.
     • User: Your login account name.
     • Password: Your login password.
     • OAuthClientId: The client Id assigned when you registered your custom OAuth application.
     • OAuthClientSecret: The client secret assigned when you registered your custom OAuth application.

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.oracleeloquareporting.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.)
     

     Below is a typical connection string:

     jdbc:oracleeloquareporting:AuthScheme=Basic;User=user;Password=password;Company=MyCompany;
     

   👁 Configuring the Data Server
   
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 Oracle Eloqua Reporting, enter the Schema selected, otherwise enter OracleEloquaReporting.
   • Database (Work Catalog): Enter CData.
   • Owner (Work Schema): If you select a Schema for Oracle Eloqua Reporting, enter the Schema selected, otherwise enter OracleEloquaReporting.
   👁 Configuring the Physical Schema
   
5. In the opened model click Reverse Engineer to retrieve the metadata for Oracle Eloqua Reporting tables. 👁 Reverse Engineer the Model
   

Edit and Save Oracle Eloqua Reporting Data

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

Create an ETL Project

Follow the steps below to create an ETL from Oracle Eloqua Reporting. You will load 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 table in Oracle Eloqua Reporting:

   CREATE TABLE ODI_DEMO.TRG_ ( NUMBER(20,0), 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_ 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_ table from the Sales Administration model onto the mapping.
7. Drag the table from the Oracle Eloqua Reporting 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 _AP in TARGET_GROUP.
10. In the _AP properties, select LKM SQL to SQL (Built-In) on the Loading Knowledge Module tab. 👁 SQL-based access to Oracle Eloqua Reporting enables you to use standard database-to-database knowledge modules.
    

You can then run the mapping to load Oracle Eloqua Reporting data into Oracle.