Connect to JD Edwards Data as an External Data Source using PolyBase

PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for JD Edwards, you get access to your JD Edwards data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live JD Edwards data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above.

CData Connect AI provides a pure SQL Server interface for JD Edwards, allowing you to query data from JD Edwards without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to JD Edwards, leveraging server-side processing to return the requested JD Edwards data quickly.

Configure JD Edwards Connectivity for PolyBase

Connectivity to JD Edwards from PolyBase is made possible through CData Connect AI. To work with JD Edwards data from PolyBase, we start by creating and configuring a JD Edwards connection.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "JD Edwards" from the Add Connection panel

3. Enter the necessary authentication properties to connect to JD Edwards.

   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.

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add JD Edwards Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to JD Edwards data from Polybase.

Create an External Data Source for JD Edwards Data

After configuring the connection, you need to create a credential database for the external data source.

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to JD Edwards data.

NOTE: Set IDENTITY to your Connect AI username and set SECRET to your Personal Access Token.

CREATE DATABASE SCOPED CREDENTIAL ConnectAICredentials
WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';

Create an External Data Source for JD Edwards

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for JD Edwards with PolyBase:

CREATE EXTERNAL DATA SOURCE ConnectAIInstance
WITH ( 
  LOCATION = 'sqlserver://tds.cdata.com:14333',
  PUSHDOWN = ON,
  CREDENTIAL = ConnectAICredentials
);

Create External Tables for JD Edwards

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to JD Edwards data from your SQL Server instance. The table column definitions must match those exposed by CData Connect AI. You can use the Data Explorer in Connect AI to see the table definition.

Sample CREATE TABLE Statement

Execute a CREATE EXTERNAL TABLE SQL command to create the external table(s), using the collation and setting the LOCATION to three-part notation for the connection, catalog, and table. The statement to create an external table based on a JD Edwards AccountsPayable.AccountLedger would look similar to the following.

CREATE EXTERNAL TABLE AccountsPayable.AccountLedger(
  DocumentNumber COLLATE [nvarchar](255) NULL,
  Amount COLLATE [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='JDEdwards1.JDEdwards.AccountsPayable.AccountLedger',
  DATA_SOURCE=ConnectAIInstance
);

Having created external tables for JD Edwards in your SQL Server instance, you are now able to query local and remote data simultaneously. To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect AI today!