How to Query JD Edwards Data in MySQL Workbench

You can use the SQL Gateway from the ODBC Driver for JD Edwards to query JD Edwards data through a MySQL interface. Follow the procedure below to start the MySQL remoting service of the SQL Gateway and work with live JD Edwards data in MySQL Workbench.

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.

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.

Query JD Edwards from MySQL Workbench

The steps below outline connecting to the virtual JD Edwards database created in the SQL Gateway from MySQL Workbench and issuing basic queries to work with live JD Edwards data.

Connect to JD Edwards through the SQL Gateway

1. In MySQL Workbench, click to add a new MySQL connection.
2. Name the connection (CData SQL Gateway for JD Edwards).
3. Set the Hostname, Port, and Username parameters to connect to the SQL Gateway.
4. Click Store in Vault to set and store the password.
5. Click Test Connection to ensure the connection is configured properly and click OK.

NOTE: When we refer to Username and Password, we mean the credentials for the user(s) created for the SQL Gateway.

Query JD Edwards Data

1. Open the connection you just created (CData SQL Gateway for JD Edwards).
2. Click File -> New Query Tab.
3. Write a SQL query to retrieve JD Edwards data, like SELECT * FROM `CData JDEdwards Sys`.AccountsPayable.AccountLedger;

With access to live JD Edwards data from MySQL Workbench, you can easily work with JD Edwards, just like you would a MySQL database. Get started now with a free, 30-day trial of the CData ODBC Driver for JD Edwards and the CData SQL Gateway.