Insider's Guide: Learn How to Use JD Edwards Orchestrator in EnterpriseOne

Guide on How to Use  JD Edwards EnterpriseOne Orchestrator

William Craig, CPA – Senior Manager – Market Research 

With JD Edwards EnterpriseOne (E1) Orchestrator, business analysts can now easily automate business processes in EnterpriseOne as well as integrate data from external applications, cloud services, custom programs, IoT devices, and more transforming external data into actionable business processes in E1. JD Edwards Orchestrator can receive, filter, evaluate and then act on this data in real-time, allowing users to easily automate the collection, processing, and exchange of data with E1, while eliminating tedious manual processes and associated errors.

A business analyst, typically without the help of a developer, can use JD Edwards Orchestrator Studio to create, test, and deploy orchestrations and notifications, using its intuitive, web-based graphical user interface. Orchestrator uses E1’s Application Interface Services (AIS) Server as its foundation, processing orchestrations saved to the AIS Server.

To process the data into EnterpriseOne, the JD Edwards Orchestrator Studio uses the following components:

• Orchestration: name for the master process in Orchestrator that leverages the following 4 components to execute an orchestration
• Service Request: invokes a JD Edwards or Java application
• Rule: evaluate incoming data against a set of conditions to determine how the orchestration will be processes
• Cross Reference: tables, setup by the user, that references incoming data to information in EnterpriseOne
• White List: initial gate to validate device against a pre-defined list
•  

Business analysts can also easily create notifications, using Orchestrator Studio’s easy-to-use web-based interface. Notifications can be created in email, text or directly in EnterpriseOne to push data or alerts to users based on watchlists thresholds.

With the release of Tools Release 9.2.3, the following enhancements have been recently added to Orchestrator:

• The ability to launch orchestrations based on events within the JD Edwards E1 system, not just external events
• A Health Monitor dashboard that provides a status of orchestrations and notifications as they run
• A new error handling feature that enables the user to specify whether an error in a step should cause the entire orchestration to fail or continue to process, as well as specify an error message and an orchestration to launch in case of failure
• Expanded Orchestrator data formats – CSV: Although JSON (JavaScript Object Notation) is the industry-standard format for sending data, many users are more familiar with CSV spreadsheet format. This enhancement enables orchestrations to read data in CSV format, simplifying the process to define and create the inputs into orchestrations.

To access Oracle’s Guide on Orchestrator, please visit - JD Edwards EnterpriseOne Tools Orchestrator Guide

In Lyle Ekdahl’s keynote address at Collaborate 19, he discussed many use cases on how JD Edwards EnterpriseOne Orchestrator is automating business processes for companies. To view Lyle’s keynote, please visit - Collaborate 19 Keynote.

Visit our on-demand webcast on Installing and Configuring Orchestrator.

JDE Orchestrator On-Demand Webcasts

Meet the Author

William Craig, CPA – Senior Manager – Market Research