Access Live Adobe Target Data in AWS Lambda

AWS Lambda is a compute service that lets you build applications that respond quickly to new information and events. AWS Lambda functions can work with live Adobe Target data when paired with the CData JDBC Driver for Adobe Target. This article describes how to connect to and query Adobe Target data from an AWS Lambda function built in Eclipse.

At the time this article was written (June 2022), Eclipse version 2019-12 and Java 8 were the highest versions supported by the AWS Toolkit for Eclipse.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Adobe Target data. When you issue complex SQL queries to Adobe Target, the driver pushes supported SQL operations, like filters and aggregations, directly to Adobe Target and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). In addition, its built-in dynamic metadata querying allows you to work with and analyze Adobe Target data using native data types.

Gather Connection Properties and Build a Connection String

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.

NOTE: To use the JDBC driver in an AWS Lambda function, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

Built-in Connection String Designer

For assistance constructing the JDBC URL, use the connection string designer built into the Adobe Target JDBC Driver. Double-click the JAR file or execute the jar file from the command line.

java -jar cdata.jdbc.adobetarget.jar

👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)

Fill in the connection properties (including the RTK) and copy the connection string to the clipboard.

Create an AWS Lambda Function

1. Download the CData JDBC Driver for Adobe Target installer, unzip the package, and run the JAR file to install the driver.

2. Create a new AWS Lambda Java Project in Eclipse using the AWS Toolkit for Eclipse. You can follow the tutorial from AWS (amazon.com).

   For this article, set the Input Type for the project to "Custom" so we can enter a table name as the input.

   👁 Creating a new AWS Lambda Java project
   
3. Add the CData JDBC Driver for Adobe Target JAR file (cdata.jdbc.adobetarget.jar) to the build path. The file is found in INSTALL_PATH\lib\. 👁 Adding the JDBC Driver JAR file
   
4. Add the following import statements to the Java class:

   import java.sql.Connection;
   import java.sql.DriverManager;
   import java.sql.ResultSet;
   import java.sql.ResultSetMetaData;
   import java.sql.SQLException;
   import java.sql.Statement;
   

5. Replace the body of the handleRequest method with the code below. Be sure to fill in the connection string in the DriverManager.getConnection method call.

   String query = "SELECT * FROM " + input;
   
   try {
   	Class.forName("cdata.jdbc.adobetarget.AdobeTargetDriver");
   } catch (ClassNotFoundException ex) {
   	context.getLogger().log("Error: class not found");
   }
   
   Connection connection = null;
    
   try {
   	connection = DriverManager.getConnection("jdbc:cdata:adobetarget:RTK=52465...;Tenant=mycompanyname;InitiateOAuth=GETANDREFRESH;");
   } catch (SQLException ex) {
   	context.getLogger().log("Error getting connection: " + ex.getMessage());
   } catch (Exception ex) {
   	context.getLogger().log("Error: " + ex.getMessage());
   }
    
   if(connection != null)
   {
   	context.getLogger().log("Connected Successfully!\n");
   }
    
   ResultSet resultSet = null;
   try
   {
   	//executing query
   	Statement stmt = connection.createStatement();
   	resultSet = stmt.executeQuery(query);
   
   	ResultSetMetaData metaData = resultSet.getMetaData();
   	int numCols = metaData.getColumnCount();
   
   	//printing the results
   	while(resultSet.next())
   	{
   		for(int i = 1; i <= numCols; i++)
   		{
   			System.out.printf("%-25s", (resultSet.getObject(i) != null) ? resultSet.getObject(i).toString().replaceAll("\n", "") : null );
   		}
   		System.out.print("\n");
   	}
   }
   catch (SQLException ex)
   {
   	System.out.println("SQL Exception: " + ex.getMessage());
   }
   catch (Exception ex)
   {
   	System.out.println("General exception: " + ex.getMessage());
   }
    
   String output = "query: " + query + " complete";
   return output;
   

Deploy and Run the Lambda Function

Once you build the function in Eclipse, you are ready to upload and run the function. In this article, the output is written to the AWS logs, but you can use this is a template to implement you own custom business logic to work with Adobe Target data in AWS Lambda functions.

1. Right-click the Package and select Amazon Web Services -> Upload function to AWS Lamba. 👁 Uploading the function to AWS Lambda
   
2. Name the function, select an IAM role, and set the timeout value to a high enough value to ensure the function completes (depending on the result size of your query).
3. Right-click the Package and select Amazon Web Services -> Run function on AWS Lambda and set the input to the name of the Adobe Target object you wish to query (i.e. "Activities"). 👁 Entering the table name as input
   
4. After the job runs, you can view the output in the CloudWatch logs. 👁 The data in AWS CloudWatch (Salesforce is shown).
   

Free Trial & More Information

Download a free, 30-day trial of the CData JDBC Driver for Adobe Target and start working with your live Adobe Target data in AWS Lambda. Reach out to our Support Team if you have any questions.