How to connect to JD Edwards Data with Squirrel SQL client

The CData JDBC Driver for JD Edwards enables you to execute queries to JD Edwards data in tools like Squirrel SQL Client. In this article, you will create a JDBC data source for JD Edwards data and execute queries.

Add the JDBC Driver for JD Edwards

Follow the steps below to add the driver JAR.

1. In Squirrel SQL, click Windows -> View Drivers.
2. Click the plus icon to open the Add Driver wizard.
3. In the Name box, enter a user-friendly name for the driver; for example, CData JDBC Driver for JD Edwards.
4. In the Example URL box, enter jdbc:jdedwards:
5. In the Extra Class Path tab, click Add.
6. In the file explorer dialog that opens, select the JAR file for the driver, located in the lib subfolder of the installation directory.
7. Click List Drivers to populate the Class Name menu with the class name for the driver, cdata.jdbc.jdedwards.JDEdwardsDriver.

Define Connection Properties

Follow the steps below to save connection properties in the driver alias.

1. Click Windows -> View Aliases.
2. In the pane that lists the aliases, click the plus icon.

3. In the Add Alias wizard that opens, the following fields are required for the JDBC driver:

   • Name: Enter a name for the alias; for example, CData JD Edwards Source.
   • Driver: Select the CData JDBC Driver for JD Edwards.
   • URL: Enter jdbc:jdedwards:
   
4. If you want to define any additional properties, click Properties.
5. In the Driver properties tab of the dialog that appears, select the Use driver properties checkbox.
6. In the Specify column, select the checkboxes for the required connection properties.

   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.

   Below is a typical connection string:

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

   
7. In the dialog that appears after you click OK, click connect to test the connection.

Discover Schemas and Query JD Edwards Data

After the metadata has loaded, a new tab for the JD Edwards data source is displayed. On the Objects subtab, you can discover schema information, such as the available tables and views.

To view table data, select the table on the Objects tab. The table data is then loaded in a grid on the Content tab.

To execute an SQL query, enter the query on the SQL tab and then click Run SQL (the runner icon). For example:

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