Connect to Oracle Eloqua Reporting Data in RazorSQL

The CData JDBC Driver for Oracle Eloqua Reporting enables standards-based access from third-party tools, from wizards in IDEs to data management and analysis tools. This article shows how to connect to Oracle Eloqua Reporting using wizards in RazorSQL.

Create a JDBC Data Source for Oracle Eloqua Reporting Data

1. Open the RazorSQL application and, in the Connections menu, select Add Connection Profile -> Other -> JDBC.
2. In the Connection Wizard that appears, set the following properties:
   • Driver Location: Set this property to the path to the lib subfolder in the installation directory.
   • Driver Class: Set the driver class to cdata.jdbc.oracleeloquareporting.OracleEloquaReportingDriver.
   • Username: Enter the username. (This property can also be set in the JDBC URL.)
   • Password: Enter the password. (This property can also be set in the JDBC URL.)

   • JDBC URL: Enter connection parameters. The JDBC URL begins with jdbc:oracleeloquareporting: and is followed by a semicolon-separated list of connection properties.

     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.)
     

     A typical JDBC URL is the following:

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

Query Oracle Eloqua Reporting Data and Select Tables

After establishing a connection, the wizard will close and the connection will be available in the connections panel. You can then query the tables.