Create Datasets from JD Edwards in Domo Workbench and Build Visualizations of JD Edwards Data in Domo

Domo helps you manage, analyze, and share data across your entire organization, enabling decision makers to identify and act on strategic opportunities. Domo Workbench provides a secure, client-side solution for uploading your on-premise data to Domo. The CData ODBC Driver for JD Edwards links Domo Workbench to operational JD Edwards data. You can build datasets from JD Edwards data using standard SQL queries in Workbench and then create real-time visualizations of JD Edwards data in the Domo service.

The CData ODBC Drivers offer unmatched performance for interacting with live JD Edwards data in Domo due to optimized data processing built into the driver. When you issue complex SQL queries from Domo to JD Edwards, the driver pushes supported SQL operations, like filters and aggregations, directly to JD Edwards and utilizes the embedded SQL Engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze JD Edwards data using native Domo data types.

Connect to JD Edwards as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

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.

After creating a DSN, you will need to create a dataset for JD Edwards in Domo Workbench using the JD Edwards DSN and build a visualization in the Domo service based on the dataset.

Build a Dataset for JD Edwards Data

You can follow the steps below to build a dataset based on a table in JD Edwards in Domo Workbench using the CData ODBC Driver for JD Edwards.

1. Open Domo Workbench and, if you have not already, add your Domo service server to Workbench. In the Accounts submenu, click Add New, type in the server address (i.e., domain.domo.com) and click through the wizard to authenticate.
2. In the DataSet Jobs submenu, click Add New.
3. Name the dataset job (i.e., ODBC JD Edwards AccountsPayable.AccountLedger), select ODBC Connection Provider as the transport method, and click through the wizard.
4. In the newly created DataSet Job, navigate to Source and click to configure the settings.
5. Select System DSN for the Connection Type.
6. Select the previously configured DSN (CData JDEdwards Sys) for the System DSN.
7. Click to validate the configuration.
8. Below the settings, set the Query to a SQL query:

   SELECT * FROM AccountsPayable.AccountLedger

   NOTE: By connecting to JD Edwards data using an ODBC driver, you simply need to know SQL in order to get your data, circumventing the need to know JD Edwards-specific APIs or protocols.
9. Click preview.
10. Check over the generated schema, add any transformations, then save and run the dataset job.

With the dataset job run, the dataset will be accessible from the Domo service, allowing you to build visualizations, reports, and more based on JD Edwards data.

Create Data Visualizations

With the DataSet Job saved and run in Domo Workbench, we are ready to build visualizations of the JD Edwards data in the Domo service.

1. Navigate to the Data Center.
2. In the data warehouse, select the ODBC data source and drill down to our new dataset.
3. With the dataset selected, choose to create a visualization.
4. In the new card:
   • Drag a Dimension to the X Value.
   • Drag a Measure to the Y Value.
   • Choose a Visualization.
   

With the CData ODBC Driver for JD Edwards, you can build custom datasets based on JD Edwards data using only SQL in Domo Workbench and then build and share visualizations and reports through the Domo service.