Build Semantic Layer Views for JD Edwards Data in APOS Live Data Gateway

Dibyendu Datta
Dibyendu Datta
Lead Technology Evangelist
Use the CData Connector for JD Edwards in APOS Live Data Gateway to build Semantic Layer Views for JD Edwards data.

APOS Live Data Gateway (LDG) is a data connection and data transformation solution that enables live data connectivity and expanded data source options for SAP Analytics Cloud and other SAP solutions. When paired with CData Connectors, users can build semantic layer views for live JD Edwards data, enabling real-time analytics on JD Edwards just like working with a relational database.

With built-in optimized data processing, the CData Connector 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.

Download and Install the Connector Files

In order to access JD Edwards data through the APOS Live Data Gateway, you will need to download the connector files from APOS and install them on the machine hosting the Live Data Gateway. An APOS representative can deliver the necessary files.

  • Install the CData DLL file (System.Data.CData.JDEdwards.dll) to the APOS Live Data Gateway installation directory (C:\Program Files\Live Data Gateway\Admin\ by default).
  • Install the CData JAR file (cdata.jdbc.jdedwards.jar) to the ConnectionTest_lib folder in the installation directory (C:\Program Files\Live Data Gateway\Admin\ConnectionTest_lib\ by default).
  • Install the CData JAR file (cdata.jdbc.jdedwards.jar) to the lib folder in the Web UI installation directory (e.g.: C:\LDG_WebUI\lib\)

Configuring the JD Edwards Connection String

Before establishing the connection to JD Edwards from the APOS Live Data Gateway, you need to configure the JD Edwards JDBC Connection String.

Built-in Connection String Designer

For assistance in constructing the JDBC Connection String, 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.

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

Your connection string will look similar to the following:


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

Connecting to JD Edwards & Creating a Semantic Layer View

After installing the connector files and configuring the connection string, you are ready to connect to JD Edwards in the Live Data Gateway Admin tool and build a semantic layer view in the Live Data Gateway Web UI.

Configuring the Connection to JD Edwards

  1. Log into your APOS Live Data Gateway Manager Logging into the APOS LDG Manager
  2. If you haven't already, update your APOS LDG license file
    1. Click File -> Configurations
    2. Click on the "..." Menu for the License
    3. Select the license file from the APOS team that includes your CData Connector license
  3. In the APOS Live Data Gateway Manager, click "Add"
  4. In the APOS Live Data Gateway On the Connection tab, configure the connection:
    • Set Data Source to "Database"
    • Set Database to "CData Drivers"
    • Set Database CData Drivers to "JD Edwards"
    • Set Connection String to the connection string configured earlier (e.g.:
      jdbc:JDEdwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;
    • Set Driver Class to "cdata.jdbc.jdedwards.JDEdwardsDriver" (this should be set by default)
    Configuring the Connection (Salesforce is shown).
  5. Click Test Connection
  6. Click Save
  7. Give your connection a unique prefix (e.g. "jdedwards")
  8. Highlight the newly created connection and click File -> "Approve Users For Web UI" Approving Users For Web UI.
  9. Approve the appropriate DB users to create views and click "Save" Configuring which DB users can create views.

At this point, we are ready to build our semantic layer view in the Live Data Gateway Web UI.

Creating a Semantic Layer View

  1. In your browser, navigate to the APOS Live Data Gateway Portal
  2. Select a Connection (e.g. "jdedwards")
  3. Set User Name and Password to the User and Password properties for JD Edwards.
  4. Click "Login" Connecting from the Web UI (Salesforce is shown).
  5. Once connected, click "Semantic Layer" to create a new semantic layer view
  6. Click "New Semantic Layer View" Adding a new semantic layer view.
  7. Set the Semantic Layer View Prefix and Semantic Layer View Name Setting the semantic layer view prefix and name.
  8. Click "Step 2"
  9. Select the table(s) and column(s) you wish to include in your view Selecting table(s) and column(s).
  10. Click "Step 3"
  11. Select the Measures from the available table columns Selecting the measure(s).
  12. Click "Step 5" (we skipped the "Extra Dimensions" step)
  13. Add any Variable Prompts
  14. Click "Step 6"
  15. Define any Table Joins
  16. Click "Review"
  17. Review you semantic layer view and click "Save" Saving the semantic layer view.

With the Semantic Layer View created, you are ready to access your JD Edwards data through the APOS Live Data Gateway, enabling real-time data connectivity to JD Edwards data from SAP Analytics Cloud and other SAP solutions.

More Information & Free Evaluation

Please visit APOS Systems - APOS Solutions - Request Evaluation Software to request evaluation software or email [email protected] for more information on working with your live JD Edwards data in APOS Live Data Gateway.

Ready to get started?

Download a free trial of the JD Edwards Driver to get started:

 Download Now

Learn more:

JD Edwards Icon JD Edwards JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with JD Edwards data including AccountLedger, ProposalofPayment, ContractRevenueSummary, EmployeeEnrollment, RentIncreaseAmounts, and more!