Connect to Oracle Eloqua Reporting from a Connection Pool in WebLogic

The CData JDBC Driver for Oracle Eloqua Reporting enables you to follow standard procedures to integrate Oracle Eloqua Reporting data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Oracle Eloqua Reporting in WebLogic Server.

Deploy the JDBC Driver in WebLogic Server

To deploy the driver, add the driver JAR to your classpath. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory.

If you want to add the driver to all domains, prepend the path to the JAR to the WEBLOGIC_CLASSPATH environment variable in WL_HOME\common\bin\commEnv.cmd/sh. This script is located in WL_HOME\common\bin\. For example:

set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.oracleeloquareporting.jar;%WEBLOGIC_CLASSPATH%

In WebLogic 12.2.1 if you want to add the driver to a specific domain, you can simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.

Earlier versions require that you manually add the driver to the classpath: Prepend the following to the PRE_CLASSPATH environment variable in setDomainEnv.cmd/sh. This script is located in the bin subfolder of the folder for that domain.

set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.oracleeloquareporting.jar;%PRE_CLASSPATH%

After making these changes, restart the server.

Create a JDBC Data Source for Oracle Eloqua Reporting

After deploying the driver, log into the WebLogic Administration Console and create the connection.

1. In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
2. On the JDBC Data Source Properties page, enter the following information:
   • Name: Enter a user-friendly name; for example, oracleeloquareportingjdbc.
   • JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/OracleEloquaReporting.

   • Database Type: Select Other.

   👁 A user-friendly name and the path to bind to. (Salesforce is shown.)
   

3. Click Next to use the default options. On the last page, enter the following information and click Test Configuration:

   • Driver Class Name: Enter the driver class, cdata.jdbc.oracleeloquareporting.OracleEloquaReportingDriver.

   • URL: Enter the JDBC URL. A typical JDBC URL is below:

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

     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.)
     
   • Database User Name: Enter the username, if not specified in the JDBC URL.
   • Password: Enter the password, if not specified in the JDBC URL.
   👁 Driver connection properties. (Salesforce is shown.)
   

After selecting the server where you want to deploy the JDBC data source, you can now connect to Oracle Eloqua Reporting data.

More WebLogic Integration

The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the WebLogic Data Sources chapter of the Oracle Fusion Middleware documentation.