Connect to Adobe Target Data from a Connection Pool in Jetty

The CData JDBC driver for Adobe Target is easy to integrate with Java Web applications. This article shows how to efficiently connect to Adobe Target data in Jetty by configuring the driver for connection pooling. You will configure a JNDI resource for Adobe Target in Jetty.

Configure the JDBC Driver for Salesforce as a JNDI Data Source

Follow the steps below to connect to Salesforce from Jetty.

1. Enable the JNDI module for your Jetty base. The following command enables JNDI from the command-line:

   java -jar ../start.jar --add-to-startd=jndi
   

2. Add the CData and license file, located in the lib subfolder of the installation directory, into the lib subfolder of the context path.

3. Declare the resource and its scope. Enter the required connection properties in the resource declaration. This example declares the Adobe Target data source at the level of the Web app, in WEB-INF\jetty-env.xml.

   
   <Configure id='adobetargetdemo' class="org.eclipse.jetty.webapp.WebAppContext">
       <New id="adobetargetdemo" class="org.eclipse.jetty.plus.jndi.Resource">
       <Arg><Ref refid="adobetargetdemo"/></Arg>
       <Arg>jdbc/adobetargetdb</Arg>
       <Arg>
         <New class="cdata.jdbc.adobetarget.AdobeTargetDriver">
           <Set name="url">jdbc:adobetarget:</Set>
           <Set name="Tenant">mycompanyname</Set>
           <Set name="InitiateOAuth">GETANDREFRESH</Set>
         </New>
       </Arg>
     </New>
   </Configure>
   

   To connect to Adobe Target, you must provide the Tenant property along with OAuth connection properties mentioned below. Note that while other connection properties can influence processing behavior, they do not affect the ability to connect.

   To determine your Tenant name:

   1. Log in to Adobe Experience. The URL will look similar to: "https://experience.adobe.com/#/@mycompanyname/preferences/general-section".
   2. Extract the value after the "/#/@". In this example, it is "mycompanyname".
   3. Set the Tenant connection property to that value.

   User Accounts (OAuth)

   You must set AuthScheme to OAuthClient for all user account flows.

   Note: Adobe authentication via OAuth requires updating your token every two weeks.

   All Applications

   CData provides an embedded OAuth application that simplifies OAuth authentication. Alternatively, you can create a custom OAuth application. Review Creating a Custom OAuth App in the Help documentation for more information.

   Obtaining the OAuth Access Token

   Set the following properties to connect:

   • InitiateOAuth: Set to GETANDREFRESH to automatically perform the OAuth exchange and refresh the OAuthAccessToken as needed.
   • OAuthClientId : Set to the client Id assigned when you registered your app.
   • OAuthClientSecret : Set to the client secret assigned when you registered your app.
   • CallbackURL : Set to the redirect URI defined when you registered your app. For example: https://localhost:3333

   With these settings, the provider obtains an access token from Adobe Target, which it uses to request data. The OAuth values are stored in the location specified by OAuthSettingsLocation, ensuring they persist across connections.

4. Configure the resource in the Web.xml:

   
     jdbc/adobetargetdb
     javax.sql.DataSource
     Container
   
   

5. You can then access Adobe Target with a lookup to java:comp/env/jdbc/adobetargetdb:

   InitialContext ctx = new InitialContext();
   DataSource myadobetarget = (DataSource)ctx.lookup("java:comp/env/jdbc/adobetargetdb");
   

More Jetty Integration

The steps above show how to configure the driver in a simple connection pooling scenario. For more use cases and information, see the Working with Jetty JNDI chapter in the Jetty documentation.