This chapter contains the following topics:
The JD Edwards EnterpriseOne Orchestrator is an integral part of an Internet of things (IoT) configuration with EnterpriseOne and supports other various integrations such as integrations with Cloud services, third-party applications, custom programs, and more. The Orchestrator uses the JD Edwards EnterpriseOne Application Interface Services (AIS) Server as its foundation. It processes orchestrations saved to the AIS Server to transform external data into actionable business processes in EnterpriseOne.
The JD Edwards EnterpriseOne Orchestrator Studio is an intuitive, easy to use web-based application that business analysts can use to create orchestrations and notifications.
The combined power of the JD Edwards EnterpriseOne Orchestrator and AIS Server enables your organization to:
Connect IoT data to your business data. The Orchestrator enables customers to collect, filter, analyze, and act on real-time data as it is being transmitted by IoT devices. JD Edwards EnterpriseOne customers benefit by eliminating costly and error-prone manual processes, by reacting to—or avoiding—business disruptions in real-time, and by analyzing historical data for continuous process improvement.
Extend integrations to other solutions. Starting with EnterpriseOne Tools 22.214.171.124 and Orchestrator Studio 5.1.0, the Orchestrator functionality has expanded to support various integrations including integrations to Cloud services, third-party applications, custom programs, and many more.
Transform how you use your entire JD Edwards system. The Orchestrator enables you to free your EnterpriseOne users from tedious tasks by transforming manual EnterpriseOne business processes into automated operations that meet your specific business needs.
Starting with EnterpriseOne Tools 9.2.3, EnterpriseOne provides the B98ORCH business function for invoking an orchestration or notification from an event in EnterpriseOne. This capability enables developers to configure EnterpriseOne to automatically launch an orchestration or notification from one of the following events:
A table trigger
A button on a form
Changing the status of an event
With the B98ORCH business function, you can extend EnterpriseOne applications beyond transactional boundaries by linking disparate ERP tasks into a single, automated business process. Or you can enable an EnterpriseOne application to automatically pass data to a REST-enabled third-party application via an orchestration. Or you can enable an EnterpriseOne application to automatically send notifications to a group of users.
Beginning with EnterpriseOne Tools Release 126.96.36.199, you can use the form extensibility framework to invoke orchestrations from an interactive application by associating orchestrations with the events on an EnterpriseOne form. Beginning with Release 188.8.131.52, you can also associate notifications with the events on a form, invoke orchestrations in the synchronous mode, and map orchestration outputs to the form controls if any output has been defined for the orchestration. For more information, see "Extending EnterpriseOne Forms by Associating Orchestrations with Events (Release 184.108.40.206)" in the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide.
Companies use devices such as sensors and beacons ("things") to monitor everything from the performance of machinery, temperatures of refrigerated units, on-time averages of commuter trains, and so forth. Capturing the data from these devices traditionally involves a complex integration using specialized hardware, expensive network connectivity, and high system integration expenditure to build the machine information into an enterprise business process. Even with a complex integration in place, an operations manager or controller still might have to manually enter the data into a spreadsheet, a software program, or an application in an ERP system. Regardless of the method used, it takes time to transfer the raw data into information that can be acted upon in a way that provides value to the business.
With the JD Edwards EnterpriseOne Orchestrator Studio, you can create orchestrations that enable the transformation of data from disparate devices into actionable business processes in JD Edwards EnterpriseOne. For example, you can create orchestrations that enable EnterpriseOne to:
Alert users to a required activity.
Alert users to perform preventative maintenance to reduce equipment downtime.
Provide audit data for safety compliance and security.
When a new orchestration is saved in the Orchestrator Studio, the name of orchestration is used to define an endpoint on the AIS Server. The endpoint URL is:
To invoke an orchestration, calling applications or devices use a post operation to this URL, where
<orchestrationname> is the name of your orchestration. The post operation must include security parameters that enable access to the orchestration and any EnterpriseOne application invoked by the orchestration. See Orchestration Security Considerations for more information.
The illustration in Figure 1-1 shows how the EnterpriseOne Orchestrator processes orchestrations. The illustration depicts processing an orchestration designed to receive data from external devices in an IoT configuration, but you can also use orchestrations to consume and provide data to Cloud services, third-party applications, custom EnterpriseOne programs, and more.
Third-party devices and a gateway collect and process information from one or more devices, converts the information to a platform-independent format and communicates this information over the internet. The gateway typically deploys intelligence to filter sensor data, secure data transfer, automate software updating, run diagnostics, start or stop the device, and support other features.
The Orchestrator uses the following orchestration components, created in the Orchestrator Studio, to transform incoming raw data into data that can be used by EnterpriseOne:
Orchestration. The master process that defines the inputs for the orchestration and provides a unique name for the orchestration process in the Orchestrator. An orchestration uses the next four components in this list to run a single orchestration instance.
Service request. An invocation of a JD Edwards EnterpriseOne interactive application or a Java application via a REST service call to the EnterpriseOne Application Interface Services (AIS) Server.
Rule. Contains a set of conditions against which the orchestration input is evaluated to produce a true or false state. Rules can be nested to produce complex evaluations. Rules determine how the orchestration is processed at runtime. You can also use custom Java to define additional rules.
Cross reference. A set of data relationships defined by the designer of the orchestration that enriches the minimal input from devices. For example, a device's serial number can be cross-referenced to a JD Edwards EnterpriseOne Equipment Number for use in service requests.
White list. An initial rudimentary pass/fail check of the incoming message's device signature against a predefined list of signatures. A white list provides an additional layer of security to the Orchestrator security.
You can also use custom Java to create custom client applications (that run on the AIS Server) for viewing and working with the filtered data. You can create a custom Java application to perform a specific business process or a process for storing the data in another database outside of EnterpriseOne.
The Orchestrator uses the JD Edwards EnterpriseOne Application Interface Services (AIS) Server as its foundation. The AIS Server is a REST services server that when configured with the EnterpriseOne HTML Server, enables access to EnterpriseOne forms and data. The Orchestrator processes orchestrations saved to the AIS Server to transfer data between EnterpriseOne and third-party applications and devices.
For an illustration of the AIS Server architecture, see "AIS Server Architecture" in the JD Edwards EnterpriseOne Tools System Overview Guide.