Connect to Salesforce Marketing from a Connection Pool in WebLogic

The CData JDBC Driver for Salesforce Marketing enables you to follow standard procedures to integrate Salesforce Marketing data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Salesforce Marketing 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.sfmarketingcloud.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.sfmarketingcloud.jar;%PRE_CLASSPATH%

After making these changes, restart the server.

Create a JDBC Data Source for Salesforce Marketing

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, sfmarketingcloudjdbc.
   • JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/SFMarketingCloud.

   • 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.sfmarketingcloud.SFMarketingCloudDriver.

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

     jdbc:sfmarketingcloud:User=myUser;Password=myPassword;InitiateOAuth=GETANDREFRESH;

     Authenticating to the Salesforce Marketing Cloud APIs

     Set the and to your login credentials, or to the credentials for a sandbox user if you are connecting to a sandbox account.

     Connecting to the Salesforce Marketing Cloud APIs

     By default, the data provider connects to production environments. Set to true to use a Salesforce Marketing Cloud sandbox account.

     The default Instance is s7 of the Web Services API; however, if you use a different instance, you can set .

     Built-in Connection String Designer

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

     java -jar cdata.jdbc.sfmarketingcloud.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 Salesforce Marketing 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.