Connect to JD Edwards Data in RapidMiner

This article shows how you can easily integrate the CData JDBC driver for JD Edwards into your processes in RapidMiner. This article uses the CData JDBC Driver for JD Edwards to transfer JD Edwards data to a process in RapidMiner.

Connect to JD Edwards in RapidMiner as a JDBC Data Source

You can follow the procedure below to establish a JDBC connection to JD Edwards:

1. Add a new database driver for JD Edwards: Click Connections -> Manage Database Drivers.
2. In the resulting wizard, click the Add button and enter a name for the connection.
3. Enter the prefix for the JDBC URL:

   
   jdbc:jdedwards:
   

4. Enter the path to the cdata.jdbc.jdedwards.jar file, located in the lib subfolder of the installation directory.
5. Enter the driver class:

   
   cdata.jdbc.jdedwards.JDEdwardsDriver
   

   
6. Create a new JD Edwards connection: Click Connections -> Manage Database Connections.
7. Enter a name for your connection.
8. For Database System, select the JD Edwards driver you configured previously.
9. Enter your connection string in the Host box.

   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.

   

   A typical connection string is below:

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

10. Enter your username and password if necessary.

You can now use your JD Edwards connection with the various RapidMiner operators in your process. To retrieve JD Edwards data, drag the Retrieve operator from the Operators view. With the Retrieve operator selected, you can then define which table to retrieve in the Parameters view by clicking the folder icon next to the "repository entry." In the resulting Repository Browser, you can expand your connection node to select the desired example set.

Finally, wire the output to the Retrieve process to a result, and run the process to see the JD Edwards data.