Access JD Edwards Data in Mule Applications Using the CData JDBC Driver

The CData JDBC Driver for JD Edwards connects JD Edwards data to Mule applications enabling read functionality with familiar SQL queries. The JDBC Driver allows users to easily create Mule applications to backup, transform, report, and analyze JD Edwards data.

This article demonstrates how to use the CData JDBC Driver for JD Edwards inside of a Mule project to create a Web interface for JD Edwards data. The application created allows you to request JD Edwards data using an HTTP request and have the results returned as JSON. The exact same procedure outlined below can be used with any CData JDBC Driver to create a Web interface for the hundreds of available data sources.

1. Create a new Mule Project in Anypoint Studio.
2. Add an HTTP Connector to the Message Flow.
3. Configure the address for the HTTP Connector.
4. Add a Database Select Connector to the same flow, after the HTTP Connector.
5. Create a new Connection (or edit an existing one) and configure the properties.
   • Set Connection to "Generic Connection"
   • Select the CData JDBC Driver JAR file in the Required Libraries section (e.g. cdata.jdbc.jdedwards.jar).
   • Set the URL to the connection string for 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.

     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.

   • Set the Driver class name to cdata.jdbc.jdedwards.JDEdwardsDriver.
   • Click Test Connection.
6. Set the SQL Query Text to a SQL query to request JD Edwards data. For example:

   SELECT DocumentNumber, Amount FROM AccountsPayable.AccountLedger WHERE BusinessUnit = '100'

   
7. Add a Transform Message Component to the flow.
8. Set the Output script to the following to convert the payload to JSON:

   %dw 2.0
   output application/json
   ---
   payload
           

   
9. To view your JD Edwards data, navigate to the address you configured for the HTTP Connector (localhost:8081 by default): http://localhost:8081. The JD Edwards data is available as JSON in your Web browser and any other tools capable of consuming JSON endpoints.

At this point, you have a simple Web interface for working with JD Edwards data (as JSON data) in custom apps and a wide variety of BI, reporting, and ETL tools. Download a free, 30 day trial of the JDBC Driver for JD Edwards and see the CData difference in your Mule Applications today.