Build Dashboards with JD Edwards Data in Dundas BI

The CData ODBC Driver for JD Edwards enables access to live data from JD Edwards under the ODBC standard, allowing you work with JD Edwards data in a wide variety of BI, reporting, and ETL tools and directly, using familiar SQL queries. This article shows how to connect to JD Edwards data as a generic ODBC Data Provider and create charts, reports, and dashboards based on JD Edwards data in Dundas BI.

Connect to JD Edwards Data

1. If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can configure the DSN using the built-in Microsoft ODBC Data Source Administrator. 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.

2. Open the Dundas BI interface, open the menu, and click New Data Connector.
3. Configure the Dundas BI Data Connector:
   • Name the Data Connector.
   • Select "ODBC generic" as the Data Provider.
   • Check the "Use System DSN" checkbox.
   • Select the appropriate System DSN.
   

Add JD Edwards Data to a Dashboard

You are now ready to create a dashboard with JD Edwards data.

1. Navigate to the Home page.
2. Click Explore Data.

3. Expand the appropriate Data Connector.
4. Drag the relevant data from the Connector to the panel.
   • You can select an entire "table" to add, but you may need to remove Measures/Rows from the Metric Set to build an appropriate visualization. Alternatively, you can select only the fields you wish to include in the visualization.
   • With the fields selected, you can add any filters or conditions on the Measures and Rows, further customizing the visualization.

5. Click Re-visualize from the menu bar and select the appropriate visualization for the data.

6. Click Add To New Dashboard to add the visualization to a new dashboard.

7. Configure the dashboard, creating dynamic visualizations of JD Edwards data.