Connect to JD Edwards Data in NetBeans

The CData JDBC Driver for JD Edwards integrates connectivity to live JD Edwards data in IDEs that support JDBC. The JDBC standard enables you to use built-in data access wizards and other tools supporting rapid development. This article shows how to connect to JD Edwards data in NetBeans. You will create a connection and load JD Edwards data in the Table Editor.

Create a JDBC Data Source for JD Edwards in NetBeans

To create the JDBC data source, expand the Database node in the Service window, right-click the Drivers node, and select New Driver. In the New Driver wizard that results, enter the following information:

• Driver File(s): Click Add and, in the file explorer dialog that appears, select the cdata.jdbc.jdedwards.jar file. The driver JAR is located in the lib subfolder of the installation directory.
• Driver Class: Click Find to search for the driver class inside the JAR. Then select cdata.jdbc.jdedwards.JDEdwardsDriver from the menu.
• Name: Enter the name for the driver.

Define Connection Parameters

Follow the steps below to define required connection properties:

1. In the Service window, right-click the Database node and click New Connection.

2. In the New Connection Wizard, enter the following connection properties:

   • Driver Name: In the menu, select the CData JDBC Driver for JD Edwards.
   • User Name: Enter the username. This can also be defined in the JDBC URL.
   • Password: Enter the password. This can also be defined in the JDBC URL.

   • JDBC URL: Specify the JDBC URL.

     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 JDBC URL is the following:

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

Query JD Edwards Data

To connect to JD Edwards data, right-click the connection in the Database node and click Connect. After the connection is established, you can expand it to discover schema information.

To load a table in the Data Views window, right-click the table and then click View Data..