DataBind Controls to JD Edwards Data in C++Builder

Dibyendu Datta
Dibyendu Datta
Lead Technology Evangelist
DataBind to JD Edwards data in C++Builder with standard components and controls.

The CData ODBC driver for JD Edwards makes it easy to integrate connectivity to live JD Edwards data with standard data access components in C++Builder. This article shows how to create a simple visual component library (VCL) application in C++Builder that connects to JD Edwards data, executes queries, and displays the results in a grid. An additional section shows how to use FireDAC components to execute commands from code.

Create a Connection to JD Edwards Data

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.

You can then follow the steps below to use the Data Explorer to create a FireDAC connection to JD Edwards.

  1. In a new VCL Forms application, expand the FireDAC node in the Data Explorer.
  2. Right-click the ODBC Data Source node in the Data Explorer.
  3. Click Add New Connection.
  4. Enter a name for the connection.
  5. In the FireDAC Connection Editor that appears, set the DataSource property to the name of the ODBC DSN for JD Edwards.
A FireDAC connection to the ODBC data source. (Salesforce is shown.)

Create VCL Applications with Connectivity to JD Edwards Data

Follow the procedure below to start querying JD Edwards data from a simple VCL application that displays the results of a query in a grid.

  1. Drop a TFDConnection component onto the form and set the following properties:

    • ConnectionDefName: Select the FireDAC connection to JD Edwards.
    • Connected: Select True from the menu and, in the dialog that appears, enter your credentials.
  2. Drop a TFDQuery component onto the form and set the properties below:

    • Connection: Set this property to the TFDConnection component, if this component is not already specified.
    • SQL: Click the button in the SQL property and enter a query. For example:

      
      SELECT DocumentNumber, Amount FROM AccountsPayable.AccountLedger WHERE BusinessUnit = '100'
      
    • Active: Set this property to true.
  3. Drop a TDataSource component onto the form and set the following property:

    • DataSet: In the menu for this property, select the name of the TFDQuery component.
  4. Drop a TDBGrid control onto the form and set the following property:

    • DataSource: Select the name of the TDataSource.
  5. Drop a TFDGUIxWaitCursor onto the form — this is required to avoid a run-time error.
Components in FireDAC used to databind an editable grid to the data source. (Salesforce is shown.)

Execute Commands to JD Edwards with FireDAC Components

You can use the TFDConnection and TFQuery components to execute queries to JD Edwards data. This section provides JD Edwards-specific examples of executing queries with the TFQuery component.

Connect to JD Edwards Data

To connect to the data source, set the Connected property of the TFDConnection component to true. You can set the same properties from code:


FDConnection1->ConnectionDefName = "CData JD Edwards ODBC Source";
FDConnection1->Connected = true;

To connect the TFDQuery component to JD Edwards data, set the Connection property of the component. When a TFDQuery component is added at design time, its Connection property is automatically set to point to a TFDConnection on the form, as in the application above.

Create Parameterized Queries

To create a parameterized query, use the following syntax below:


FDQuery1->SQL->Text = "select * from AccountsPayable.AccountLedger where businessunit = :BusinessUnit";
FDQuery1->ParamByName("businessunit")->AsString = "100";
FDQuery1->Open();

The example above binds a string-type input parameter by name and then opens the dataset that results.

Prepare the Statement

Preparing statements is costly in system resources and time. The connection must be active and open while a statement is prepared. By default, FireDAC prepares the query to avoid recompiling the same query over and over. To disable statement preparation, set ResourceOptions.DirectExecute to True; for example, when you need to execute a query only once.

Execute a Query

To execute a query that returns a result set, such as a select query, use the Open method. The Open method executes the query, returns the result set, and opens it. The Open method will return an error if the query does not produce a result set.


FDQuery1->SQL->Text = "select * from AccountsPayable.AccountLedger where businessunit = :BusinessUnit";
FDQuery1->ParamByName("businessunit")->AsString = "100";
FDQuery1->Open();

Related Articles

Below you can find other articles for using the CData ODBC Driver with RAD Studio, Delphi, and C++ Builder.

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.