Embed Size (px)
Citation preview
1
Ephlux
CX CLOUDAwesome Customer Experience
JD Edwards Internet of Things Orchestrator
"Internet of Things" for your JD Edwards E1
If you have plans for implementing IoT at your JD Edwards E1 shop, there’s a very interesting announcement from Oracle. "JD Edwards E1 IoT Orchestrator" has been launched.
The good news for those on E1 9.0 is that it also supports 9.0 along with E1 9.1 - all it requires is upgrading to the latest Tools web components 9.1.5.5 which should not be a major issue.
At Ephlux, we have nose-dived right in to it already
At Ephlux, our R&D team has jumped on it right away and we’re getting our hands dirty - we'll be relaying our findings and you're welcome to join in on our research forums. This release strongly
helps us solidify our position as as the "customer experience integrator" since many companies will continue to have JD Edwards on-prem co-exist with Oracle CX Cloud apps as well
as their mobile, social, web and location-based apps and other on-field and in-venue smart devices.
E1 – Business Services
Overview
E1 – Application Interface Services (AIS)
E1 – Internet of Things (IoT) Orchestrator
E1 IoT Orchestrator – Building Blocks
1
2
3
4
E1 – Business Services1
We are already leaders with BSSV but our millennial "chatty" app developers weren't satisfied with that alone.
We, at Ephlux, as most of you would know, are already the leaders with JD Edwards BSSV (Business Services) - the more traditional integration framework for
E1 using SOAP based web-services that help connect E1 to external applications.
Business Services Server (BSSV)
Integration Repository
SOAP
Event NotificationService Provider Service Consumer
E1 – Application Interface Services (AIS)2
However, our mobile, web and IoT developers have never been great fans of SOAP because of the extra overhead which makes it rather sluggish for the sort of
"User Experience" and agility you need on today's modern mobile, social and "chatty" apps.
They were quite eager to feast on a REST based engine for JD Edwards and now having not just AIS (REST API Engine for E1) but also an IoT orchestration layer on top of it is
simply a cherry topping for them.
Application Interface Services (AIS)
Integration Repository
REST
Event NotificationService Provider Service Consumer
Comparing BSSV with AISAlthough BSSV is a robust option for most E1 to external application integration
scenarios, the extra overhead that SOAP carries makes it inefficient and sluggish when it comes to integrating to smartphones, social networks and other modern interfaces
including smart devices and IoT.
It is for this specific purpose, Oracle released AIS - Application Interface Services to provide a more nimble, light-weight and faster REST API Engine thus opening up possibilities for high UX integration possibilities with consumer touch-points and
industrial IoT devices where the real-time OR near real-time integration speeds are critical.
E1 – Internet of Things (IoT) Orchestrator 3
Overview for JD Edwards EnterpriseOne Internet of Things Orchestrator
With this release, Oracle announces the JD Edwards EnterpriseOne Internet of Things (IoT) Orchestrator. This new product 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 manual processes, by reacting
to—or avoiding— business disruptions in real-time, and by analyzing historical data for continuous process improvement.
Application Interface Services (AIS)
Integration Repository
REST
Event NotificationService Provider Service Consumer
IoT Orchestrator
Registration (Cross Reference) Rules Engine Action (Service Request)
E1 IoT Orchestrator – Building Blocks 4
1. Registration (Cross Reference): Identifies the devices that are authorized to send data to the IoT Orchestrator and associates those devices with data stored in the JD Edwards EnterpriseOne system, such as equipment number, asset ID, location, business unit, etc.
2. Rules Engine: Establishes criteria and thresholds against which the IoT Orchestrator evaluates incoming device data to invoke the appropriate action based on conditions.
3. Action (Service Request): Defines the specific JD Edwards EnterpriseOne application form or custom Java program to be invoked as the result of a predefined condition. The IoT Orchestrator passes incoming device data into the form(s) and launches the applications. Any JD Edwards EnterpriseOne form, including customers’ customized forms, can be invoked by the orchestration.
We can’t emphasize enough as to how big this news is for E1 customers who’re looking to integrate E1 with the smart devices in their field operations, mobile apps and the enterprise cloud apps
and want to orchestrate them together through a robust SOA middleware cloud.
19
About the Author
Ali has around 14 years of experience, spanning areas of strategic technology management, product and business development for the US, UK, Middle East and South Asia regions across telecom, hospitality, healthcare and other verticals.
At Ephlux, Ali is currently focused on CX (Customer Experience) platforms and consulting, SOA, enterprise mobility, digital marketing and integration of ERPs and CRMs with customer-centric mobile, social, e-commerce, in-venue and other digital touch-points.
Ali and his company Ephlux has worked on customer experience, integration and mobility projects for large enterprises and start-ups alike, including PHILIPS, Disney, Gibson Guitars, Johnson & Johnson, IKEA and many more.Ali can be reached out on his twitter handle @m_ali_nasim and on his email at [email protected]
