The JD Edwards Orchestrator: how it works
Recently, Oracle introduced the JD Edwards Orchestrator. The tool is a more complete version of the previously introduced IOT Orchestrator and functions as a layer on top of the Application Interface Services (AIS) Server. The Orchestrator is developed to make raw data from external tools, systems and applications ready for usage within JD Edwards. While the Orchestrator retains the simplicity required for business analysts to create orchestrations, the inclusion of Groovy scripting and REST calls to external systems gives programmers limitless possibilities for more complex orchestrations. This coincides entirely with the Citizen Developer-concept. The Orchestrator is now part of the standard license and therefore available free of charge.
While the process of transferring data via the AIS Server can be puzzling, the JD Edwards Orchestrator makes managing input and output much easier. The tool also helps you to automate the various steps in the data transmission process. Additionally, you can build in logic and conditions to incoming data streams. The administration resides completely within JD Edwards, which makes the usage of external systems for transferring data obsolete.
Simplified management of input and output
The configuration and management of the AIS Server can be complex at times. To generate the right output, you need to enter a large amount of values. The output that you receive is often difficult to read and interpret. The JD Edwards Orchestrator simplifies this process and gives a clearer visualization. The result is a more user-friendly data transmission process.
Merging and automating separate calls
To achieve a certain outcome, you usually need to perform different calls in the AIS Server. With the Orchestrator, you can reduce this variety of calls to a single call. This makes the transfer of data much easier and more efficient.
Easily add conditions and logic
The Orchestrator also helps you to add logic to the incoming raw data. For example, you can add certain conditions to data derived from a machine’s temperature gauge. As soon as the temperature indicates a deviating value, this is automatically notified. This allows you to take the appropriate follow-up actions.
A few other examples:
- A new data request service allows users to create orchestrations that retrieve data from JD Edwards’ tables and business views. The returned data can also be aggregated, for example as a sum, average, or count. This new feature gives users access to the wealth of data stored in JD Edwards.
- Users can now include an orchestration step that invokes another JD Edwards orchestration, thus allowing orchestrations to be “chained” together. For example, an orchestration might be designed to automatically generate a purchase order when inventory quantity reaches a reorder point level.
- Users can now employ output mappings to have more control over the format of the data that is returned in the orchestration’s REST service response. This enhancement allows the external systems that invoke orchestrations to more easily discover and understand the expected response from the orchestration.
Would you like to learn more about the possibilities of JD Edwards Orchestrator? We are happy to help you get started. Get in touch by filling in the form.
Go back to the overview