Connect to JD Edwards Data in the Denodo Platform

Denodo Platform is a data virtualization product providing a single point of contact for enterprise database data. When paired with the CData JDBC Driver for JD Edwards, Denodo users can work with live JD Edwards data alongside other enterprise data sources. This article explains how to create a virtual data source for JD Edwards in the Denodo Virtual DataPort Administrator.

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

Create the JD Edwards Virtual Port

To connect to live JD Edwards data from Denodo, you need to copy the JDBC Driver JAR file to the external library directory for Denodo and create a new JDBC Data Source from the Virtual DataPort Administrator tool.

1. Download the CData JDBC Driver for JD Edwards installer, unzip the package, and run the JAR file to install the driver.
2. Copy the JAR File (and license file if it exists) from the installation location (typically C:\Program Files\CData\CData JDBC Driver for JD Edwards\lib\) to the Denodo external library directory (C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-jdedwards-19).
3. Open the Denodo Virtual DataPort Administrator tool and navigate to the Server Explorer tab.
4. Right-click "admin" and select New -> Data source -> JDBC.
5. Configure the JDBC Connection:
   • Name: your choice, e.g.: jdedwards
   • Database adapter: Generic
   • Driver class path: C:\Denodo\Denodo Platform\lib-external\jdbc-drivers\cdata-jdedwards-19
   • Driver class: cdata.jdbc.jdedwards.JDEdwardsDriver

   • Database URI: Set this to a JDBC URL using the necessary connection properties. For example,

     jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;

     

     Information on creating the Database URI follows:

     Built-In Connection String Designer

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

     
     	java -jar cdata.jdbc.jdedwards.jar
     	

     Fill in the connection properties and copy the connection string to the clipboard.

     The driver connects to JD Edwards through your Application Interface Services (AIS) Server. Set the following connection properties:

     • URL: The base HTTPS URL of your AIS Server (e.g., https://jde-ais.example.com:8300).
     • User: Your JD Edwards username.
     • Password: Your JD Edwards password.
     • Environment (optional): The JD Edwards environment to use (e.g., PD920 for production or DV920 for development). If not specified, the AIS Server's default environment is used.
     • Role (optional): The JD Edwards role for the session. If not specified, the AIS Server's default role is used.
     • DeviceName (optional): An identifier for the connecting device or application, used for auditing and logging on the AIS Server.
     • Jasserver (optional): The specific Java Application Server (JAS) instance to route requests through, useful in clustered environments.

     Choosing Which Data Is Exposed

     JD Edwards organizes tables and business views by System Code, and the driver exposes each System Code as its own schema. Use these properties to control which schemas are available:

     • DataModel: One or more ERP modules (comma-separated) whose System Codes are exposed as schemas, or All to expose every System Code in the connected instance. Defaults to FinancialManagement.
     • SystemCodes: A comma-separated list of additional System Codes to expose alongside those from DataModel (e.g., 42,43).

     When you connect, the driver sends your credentials to the AIS Server to obtain a session token and caches it. The driver requests a new token automatically before the session expires.

     
6. Click the "Test connection" button to confirm the configuration and click Save.

View JD Edwards Data in the VirtualPort Administrator Tool

After creating the data source, you can create a base view of JD Edwards data for use in the Denodo Platform.

1. Click the "Create base view" button in the newly created VirtualPort (admin.JDEdwards).
2. Expand the object tree and select the objects (tables) you wish to import.
3. Click the "Create selected" button to create views of the JD Edwards data.
   Optional: Click "Create associations from foreign keys" to define relationships between the objects.
4. With the view(s) created, navigate to a table (cdata_jdedwards_accountspayable.accountledger) in the Server Explorer and double-click the selected table.
5. In the new tab, click "Execution panel" to open a query panel.
6. Customize the query in the "Execute" tab or use the default:

   SELECT * FROM cdata_jdedwards_accountspayable.accountledger CONTEXT ('i18n'='us_est', 'cache_wait_for_load'='true')
   

   
7. Click Execute to view the data.

With the base view created, you can now work with live JD Edwards data like you would any other data source in Denodo Platform, for example, querying JD Edwards in the Denodo Data Catalog.

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