Connect to Oracle Eloqua Reporting Data in CloverDX (formerly CloverETL)

The CData JDBC Driver for Oracle Eloqua Reporting enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with Oracle Eloqua Reporting as sources. In this article, you will use the JDBC Driver for Oracle Eloqua Reporting to set up a simple transfer into a flat file. The CData JDBC Driver for Oracle Eloqua Reporting enables you to use the data transformation components in CloverDX (formerly CloverETL) to work with Oracle Eloqua Reporting as sources. In this article, you will use the JDBC Driver for Oracle Eloqua Reporting to set up a simple transfer into a flat file.

Connect to Oracle Eloqua Reporting as a JDBC Data Source

1. Create the connection to Oracle Eloqua Reporting data. In a new CloverDX graph, right-click the Connections node in the Outline pane and click Connections -> Create Connection. The Database Connection wizard is displayed.
2. Click the plus icon to load a driver from a JAR. Browse to the lib subfolder of the installation directory and select the cdata.jdbc.oracleeloquareporting.jar file.
3. Enter the JDBC URL.

   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.

   

   A typical JDBC URL is below:

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

Query Oracle Eloqua Reporting Data with the DBInputTable Component

1. Drag a DBInputTable from the Readers selection of the Palette onto the job flow and double-click it to open the configuration editor.
2. In the DB connection property, select the Oracle Eloqua Reporting JDBC data source from the drop-down menu.
3. Enter the SQL query. For example:

   SELECT ,  FROM  WHERE  = ''

Write the Output of the Query to a UniversalDataWriter

1. Drag a UniversalDataWriter from the Writers selection onto the jobflow.
2. Double-click the UniversalDataWriter to open the configuration editor and add a file URL.
3. Right-click the DBInputTable and then click Extract Metadata.
4. Connect the output port of the DBInputTable to the UniversalDataWriter.
5. In the resulting Select Metadata menu for the UniversalDataWriter, choose the table. (You can also open this menu by right-clicking the input port for the UniversalDataWriter.)
6. Click Run to write to the file.