Access JD Edwards Data from MySQL in HeidiSQL

Mohsin Turki
Mohsin Turki
Technical Marketing Engineer
Use CData ODBC Driver and SQL Gateway to connect and query live JD Edwards data from HeidiSQL.

HeidiSQL is an open-source database administration tool that natively supports MariaDB, MySQL, SQL Server, and PostgreSQL. When paired with the CData ODBC Driver for JD Edwards and SQL Gateway, HediSQL's reach extends to include access to live JD Edwards data. This article demonstrates how to connect to on-premise JD Edwards and query JD Edwards data in HeidiSQL.

Connect to JD Edwards Data

If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.

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.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Configure the SQL Gateway

See the SQL Gateway Overview to set up connectivity to JD Edwards data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.

Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)

To connect to the SQL Gateway from HeidiSQL, you will need to run the SQL Gateway on a web-facing machine. After configuring the SQL Gateway, make note of the following information:

  • The IP address or domain name of the machine hosting the SQL Gateway
  • The data source name (likely CData JDEdwards Sys) of the MySQL service
  • The port number of the MySQL service
  • The credentials of a SQL Gateway user with access to the service

Configure Remote Access

If your ODBC Driver and the remoting service are installed on-premise (and not accessible from HeidiSQL), you can use the reverse SSH tunneling feature to enable remote access. For detailed instructions, read our Knowledge Base article: SQL Gateway SSH Tunneling Capabilities.

Connect to JD Edwards in HeidiSQL

Once you have a MySQL Service configured for the CData ODBC Driver for JD Edwards, you are ready to connect to the data in HeidiSQL. Start by creating a new connection Session in HeidiSQL, then choose the MySQL library type.

Configure the data set using the values for the MySQL service for JD Edwards you configured in SQL Gateway (be sure to use the DSN for the database name). Validate your connection and click Open.

Configure the connection to SQL Gateway.

Query JD Edwards from HeidiSQL

  1. In the database listing on the left, find your connection to JD Edwards configured earlier.
  2. In the database listing on the left, expand the appropriate connection and to view individual tables or data objects present within JD Edwards.
  3. Write custom SQL queries targeting these tables, treating the data source like any SQL Server database, or visually explore each tabular data set by selecting the relevant tables Querying within HeidiSQL.

With the CData ODBC Driver for JD Edwards and SQL Gateway, you are able to easily query data from JD Edwards data in HeidiSQL. If you have any questions, such as needing to access your on-premises data from HeidiSQL, let our Support Team know.

Ready to get started?

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

 Download Now

Learn more:

JD Edwards Icon JD Edwards ODBC Driver

The JD Edwards ODBC Driver is a powerful tool that allows you to connect with live data from JD Edwards, directly from any applications that support ODBC connectivity.

Access JD Edwards data like you would a database - read JD Edwards AccountLedger, ProposalofPayment, ContractRevenueSummary, EmployeeEnrollment, RentIncreaseAmounts, etc. through a standard ODBC Driver interface.