Integrating Gumloop with JD Edwards Data via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Leverage the CData Connect AI Remote MCP Server to enable Gumloop to securely access and act on JD Edwards data within automated workflows.

Gumloop is a visual automation platform designed to create AI-powered workflows by combining triggers, AI nodes, APIs, and data connectors. By integrating Gumloop with CData Connect AI through the built-in MCP (Model Context Protocol) Server, workflows can seamlessly access and interact with live JD Edwards data.

The platform provides a low-code environment, making it easier to orchestrate complex processes without heavy development effort. Its flexibility allows integration across multiple business applications, enabling end-to-end automation with live data.

This article outlines the steps required to configure JD Edwards connectivity in Connect AI, register the MCP server in Gumloop, and build a workflow that queries JD Edwards data.

Step 1: Configure JD Edwards Connectivity for Gumloop

Connectivity to JD Edwards from Gumloop is made possible through CData Connect AI's Remote MCP Server. To interact with JD Edwards data from Gumloop, we start by creating and configuring a JD Edwards connection in CData Connect AI.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a Connection
  3. Select "JD Edwards" from the Add Connection panel
  4. Selecting a data source
  5. 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.

    Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab in the Add JD Edwards Connection page and update the User-based permissions. Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Gumloop. It is best practice to create a separate PAT for each service to maintain granularity of access.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. Creating a new PAT
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the JD Edwards connection configured and a PAT generated, Gumloop is prepared to connect to JD Edwards data through the CData MCP server.

Step 2: Connect to the MCP server in Gumloop

The MCP server endpoint and authentication values from Connect AI must be added to Gumloop credentials.

  1. Sign in to Gumloop and create an account
  2. Visit the Gumloop Credentials page to configure MCP server
  3. Click on Add Credentials and search and select MCP Server
  4. Configuring MCP server MCP server app
  5. Provide the following details:
    • URL: https://mcp.cloud.cdata.com/mcp
    • Label: A descriptive name such as JD Edwards-mcp-server
    • Access Token / API Key: leave blank
    • Additional Header: Authorization: Basic YOUR EMAIL:YOUR PAT
    • Configuring to CData MCP server
    • Save the credentials
    • Saved MCP Credentials

The MCP server is now available to build workflows in Gumloop.

Step 3: Build a workflow and explore live JD Edwards data with Gumloop

  1. Visit Gumloop Personal workspace and click on the Create Flow
  2. Create Gumloop workflow
  3. Select the icon or press Ctrl + B to add a node or a subflow
  4. Add a node
  5. Search for Ask AI and select it
  6. Select Ask AI
  7. Click Show More Options and enable the Connect MCP Server? option
  8. Enable
  9. From the MCP Servers dropdown, choose the saved MCP credential
  10. Add a Prompt and Choose an AI Model according to your requirements
  11. Add Prompt
  12. After configuring the required details, Click Run to run the pipeline
  13. Example 1: Gumloop workflow execution Example 2: Gumloop workflow execution

With the workflow run completed, Gumloop demonstrates successful retrieval of JD Edwards data through the CData Connect AI MCP server, with the MCP Client node providing the ability to ask questions, retrieve records, and perform actions on the data.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial