ESI JDE ODBC Driver icon
Integration & Data · ODBC

JDE ODBC with AIS, XML or FAT Back-Ends

Choose the JDE data-access route that fits your environment: FAT Client API, XML kernel or AIS server.

Order or Inquire

One ODBC interface, three routes to JDE

Different JDE landscapes allow different integration paths. Some environments already trust the Fat Client. Some prefer XML. Some have standardised on AIS.

The driver keeps the client interface familiar while allowing the backend route to match the technical and security realities of the site.

  • FAT for classic workstation-compatible deployments.
  • XML for lighter server-side access.
  • AIS where web-service style access is already standard.

Useful when policy changes

A driver with multiple back-ends gives you options as network policy, AIS adoption or workstation standards change. The reporting tool still sees ODBC.

Next step

See where this fits in the product.

This supporting page explains one search intent in detail. The main ESI JDE ODBC Driver page gives the full product overview, related use cases, licensing and enquiry path.

Back to ESI JDE ODBC Driver

All product names, logos and trademarks are the property of their respective owners. References indicate compatibility, not endorsement or affiliation.

Need something specific?

Tell us which application and which identity provider, or which JDE pain point you're trying to close. We'll tell you quickly whether one of our tools is a fit and what integration looks like for your environment.

Contact us Browse products