Integrate with live JD Edwards Data in Jitterbit
Jitterbit is an enterprise iPaaS (integration platform as a service) that lets you streamline your data workflows. When paired with CData Connect AI, Jitterbit gets access to live JD Edwards data. This article demonstrates how to connect to JD Edwards using Connect AI and integrate with live JD Edwards data in Jitterbit.
CData Connect AI provides a pure OData interface for JD Edwards, allowing you to query data from JD Edwards without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to JD Edwards, leveraging server-side processing to return the requested JD Edwards data quickly.
Configure JD Edwards Connectivity for Jitterbit
To work with JD Edwards data from Jitterbit, we need to connect to JD Edwards from Connect AI, provide user access to the connection, and create a Workspace for the JD Edwards data.
Connect to JD Edwards from Connect AI
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
- Log into Connect AI, click Sources, and then click Add Connection
- Select "JD Edwards" from the Add Connection panel
-
Enter the necessary authentication properties to connect to 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.
- Click Save & Test
-
Navigate to the Permissions tab in the Add JD Edwards Connection page and update the User-based permissions.
Add a Personal Access Token
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
- Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
Configure JD Edwards Endpoints for Jitterbit
After connecting to JD Edwards, create a workspace for your desired table(s).
-
Navigate to the Workspaces page and click Add to create a new Workspace (or select an existing workspace).
- Click Add to add new assets to the Workspace.
-
Select the JD Edwards connection (e.g. JDEdwards1) and click Next.
-
Select the table(s) you wish to work with and click Confirm.
- Make note of the OData Service URL for your workspace, e.g. https://cloud.cdata.com/api/odata/{workspace_name}
With the connection, PAT, and Workspace configured, you are ready to connect to JD Edwards data from Jitterbit.
Connect to JD Edwards from Jitterbit using Connect AI
To establish a connection from Jitterbit to CData Connect AI using the OData protocol, follow these steps.
- Log into Jitterbit.
- Create a project in Cloud Studio and provide a workspace environment for it.
- click Sources and enter OData in the search bar.
- Select the OData connector.
- Enter the OData connection properties.
- Connection Name: enter a connection name.
- OData Metadata URL: enter https://cloud.cdata.com/api/odata/{workspace_name}.
- Authentication: select Basic Auth.
- User Name: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
- Password: enter the PAT you generated on the Settings page.
- Click Test to test the connection, and then click Save Changes.
- Choose the operation you want to perform and drag it to the workflow in your project.
- Double-click the query operation to see all the tables and derived views available in your OData endpoint.
- Select a table and configure the query.
You can now transform and integrate live JD Edwards data in Jitterbit.
Get CData Connect AI
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Jitterbit, try CData Connect AI today!