Introduction

Over the years, JD Edwards has evolved and incorporated various integration technologies to facilitate seamless communication between different systems and applications. Let’s delve into the history of some key integration technologies:

1. XML CallObject:

XML CallObject is an early integration technology in JD Edwards that allows applications to communicate with each other using XML messages. It was introduced in the early 2000s and provided a way for external systems to interact with JD Edwards by passing XML-formatted data to the JD Edwards application. XML CallObject enabled basic integration capabilities and data exchange between JD Edwards and other applications.

2. XPI (XML Publisher for Interactive Applications):

XPI was introduced as an enhancement to XML CallObject, providing more advanced integration capabilities. It allowed developers to create interactive applications that could communicate with JD Edwards through XML messages. With XPI, JD Edwards could interact with external systems in real-time, making it more flexible and robust in terms of integration possibilities.

3. Files and Z / EDI processes:

Z Files are flat files used for data import and export in JD Edwards. They have been a long-standing integration method within the JD Edwards ecosystem. Z Files are usually in a fixed-length format, making them easy to generate and consume by external systems. Many interfaces with legacy or external systems were built using Z Files, especially before more modern integration technologies were introduced.

4. JD Edwards EnterpriseOne Connector (also known as JD Edwards E1 Connector):

The JD Edwards E1 Connector is a standard Java-based integration framework that allows external applications and systems to interact with JD Edwards EnterpriseOne. It provides a set of Java APIs (Application Programming Interfaces) that enable developers to integrate their applications with JD Edwards. The E1 Connector supports various integration capabilities, such as executing business functions, submitting jobs, querying data, and retrieving reports from JD Edwards EnterpriseOne. It uses web services and XML over HTTP/S as the underlying communication protocol, making it platform-independent and easily accessible from different programming languages and platforms.

5. BSSV (Business Services Server):

BSSV is a web services-based integration technology introduced in the mid-2000s. It is built on top of the JD Edwards Business Services layer, which exposes various business functions as web services. BSSV enabled standardization and simplified integration by providing a service-oriented architecture (SOA) approach. External systems could easily invoke JD Edwards business functions through BSSV web services, making it a popular choice for integrations with third-party applications.

6. JDE Orchestrator (EnterpriseOne Orchestrator):

The JD Edwards Orchestrator is a modern integration tool introduced in JD Edwards EnterpriseOne 9.1. It is a robust and flexible integration platform that enables companies to automate and streamline business processes by orchestrating various JD Edwards and non-JD Edwards applications and services. The Orchestrator uses a low-code approach, allowing business analysts and power users to create and manage integrations with little to no programming knowledge.

In summary, the history of integration technologies in JD Edwards showcases a gradual evolution from basic XML-based integration to more sophisticated web services, orchestration, and automation capabilities.

With so many options, making the right choice is critical to getting maximum value and scalability from the system. Using the latest tools, or just trying to make every interface real time is not necessarily the right answer in all cases. Some of the factors are:

– What technologies does the 3rd party system support

– Is there a middleware involved

– Which method provides good error handling for the specific use cases

– What tracing and tracking options are available

– Is there a robust way to recover in case of failed transactions

– Are the applications on premise or in cloud

– What is the volume of data being exchanged

– What kind of external dependencies are involved

Make a good analysis, so you don’t get too far down the road with a bad choice.