Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Adobe Target from a Connection Pool in WebLogic
Use the CData JDBC Driver for Adobe Target to connect to Adobe Target data from Web applications running on WebLogic.
The CData JDBC Driver for Adobe Target enables you to follow standard procedures to integrate Adobe Target data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Adobe Target 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.adobetarget.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.adobetarget.jar;%PRE_CLASSPATH%
After making these changes, restart the server.
Create a JDBC Data Source for Adobe Target
After deploying the driver, log into the WebLogic Administration Console and create the connection.
- In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
-
On the JDBC Data Source Properties page, enter the following information:
- Name: Enter a user-friendly name; for example, adobetargetjdbc.
- JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/AdobeTarget.
Database Type: Select Other.
-
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.adobetarget.AdobeTargetDriver.
URL: Enter the JDBC URL. A typical JDBC URL is below:
jdbc:adobetarget:Tenant=mycompanyname;InitiateOAuth=GETANDREFRESH
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:
- Log in to Adobe Experience. The URL will look similar to: "https://experience.adobe.com/#/@mycompanyname/preferences/general-section".
- Extract the value after the "/#/@". In this example, it is "mycompanyname".
- 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.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Adobe Target JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.adobetarget.jar
Fill in the connection properties and copy the connection string to the clipboard.
- Database User Name: Enter the username, if not specified in the JDBC URL.
- Password: Enter the password, if not specified in the JDBC URL.
After selecting the server where you want to deploy the JDBC data source, you can now connect to Adobe Target 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.