Load JD Edwards Data to a Database Using Embulk
Embulk is an open source bulk data loader. When paired with the CData JDBC Driver for JD Edwards, Embulk easily loads data from JD Edwards to any supported destination. In this article, we explain how to use the CData JDBC Driver for JD Edwards in Embulk to load JD Edwards data to a MySQL dtabase.
With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live JD Edwards data. When you issue complex SQL queries 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 client-side (often SQL functions and JOIN operations).
Configure a JDBC Connection to JD Edwards Data
Before creating a bulk load job in Embulk, note the installation location for the JAR file for the JDBC Driver (typically C:\Program Files\CData\CData JDBC Driver for JD Edwards\lib).
Embulk supports JDBC connectivity, so you can easily connect to JD Edwards and execute SQL queries. Before creating a bulk load job, create a JDBC URL for authenticating with JD Edwards.
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.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the JD Edwards JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.jdedwards.jar
Fill in the connection properties and copy the connection string to the clipboard.
Below is a typical JDBC connection string for JD Edwards:
jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;
Load JD Edwards Data in Embulk
After installing the CData JDBC Driver and creating a JDBC connection string, install the required Embulk plugins.
Install Embulk Input & Output Plugins
- Install the JDBC Input Plugin in Embulk.
https://github.com/embulk/embulk-input-jdbc/tree/master/embulk-input-jdbc - In this article, we use MySQL as the destination database. You can also choose SQL Server, PostgreSQL, or Google BigQuery as the destination using the output Plugins.
https://github.com/embulk/embulk-output-jdbc/tree/master/embulk-output-mysqlembulk gem install embulk-output-mysql
embulk gem install embulk-input-jdbc
With the input and output plugins installed, we are ready to load JD Edwards data into MySQL using Embulk.
Create a Job to Load JD Edwards Data
Start by creating a config file in Embulk, using a name like jdedwards-mysql.yml.
- For the input plugin options, use the CData JDBC Driver for JD Edwards, including the path to the driver JAR file, the driver class (e.g. cdata.jdbc.jdedwards.JDEdwardsDriver), and the JDBC URL from above
- For the output plugin options, use the values and credentials for the MySQL database
Sample Config File (jdedwards-mysql.yml)
in:
type: jdbc
driver_path: C:\Program Files\CData\CData JDBC Driver for JD Edwards 20xx\lib\cdata.jdbc.jdedwards.jar
driver_class: cdata.jdbc.jdedwards.JDEdwardsDriver
url: jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;
table: "AccountsPayable.AccountLedger"
out:
type: mysql
host: localhost
database: DatabaseName
user: UserId
password: UserPassword
table: "AccountsPayable.AccountLedger"
mode: insert
After creating the file, run the Embulk job.
embulk run jdedwards-mysql.yml
After running the the Embulk job, find the Salesforce data in the MySQL table.
Load Filtered JD Edwards Data
In addition to loading data directly from a table, you can use a custom SQL query to have more granular control of the data loaded. You can also perform increment loads by setting a last updated column in a SQL WHERE clause in the query field.
in:
type: jdbc
driver_path: C:\Program Files\CData\CData JDBC Driver for JD Edwards 20xx\lib\cdata.jdbc.jdedwards.jar
driver_class: cdata.jdbc.jdedwards.JDEdwardsDriver
url: jdbc:jdedwards:URL=https://your-jde-environment-app.example.com;User=admin;Password=myPassword;
query: "SELECT DocumentNumber, Amount FROM AccountsPayable.AccountLedger WHERE [RecordId] = 1"
out:
type: mysql
host: localhost
database: DatabaseName
user: UserId
password: UserPassword
table: "AccountsPayable.AccountLedger"
mode: insert
More Information & Free Trial
By using CData JDBC Driver for JD Edwards as a connector, Embulk can integrate JD Edwards data into your data load jobs. And with drivers for more than 200+ other enterprise sources, you can integrate any enterprise SaaS, big data, or NoSQL source as well. Download a 30-day free trial and get started today.