If you have been following recent technology trends as closely as we do, you probably realized that mobile and cloud technologies are no longer cutting edge, they are the new default. Oracle’s CEO Safra Catz thinks,
- This is a unique time in technology. Digital transformation can be done at far less cost and much faster than ever.
I recently heard another Oracle executive compare the latest cloud/mobile trends to the California Gold Rush.
JD Edwards and Mobile, Cloud Applications
Several of our Oracle JD Edwards customers are in the process of adopting this transformation by implementing Cloud Systems, Mobile Applications, IoT and other third party systems. The biggest challenge our customers run into with this transformation is the need to connect these transformative systems to the backend of JD Edwards. Fortunately for them, JD Edwards is transforming, too. In Oracle’s own language, they now provide multiple ways to spend the “Digital Gold” (JDE) in the Digital Economy of Mobile, Cloud, IoT and other external systems.
#JDEdwards now provides multiple ways to connect your external mobile, cloud applications w/ JDE in addition to the business services. Click To Tweet Let us discuss a couple of options here:
AIS Form Service
The Application Interfaces Services (AIS) Server provides a light weight interface to allow communication between mobile applications and JD Edwards EnterpriseOne.
AIS server includes support for JSON representation of form service requests, a way to interact with E1 web forms. Form service request lets developers perform various operations on a single form by sending an ordered list of commands. For example, actions such as Set a QBE value, Set Control Value, Press button etc. can be passed to AIS form service request which in turn sends those commands to the HTML server.
AIS Form Service is the most popular way for mobile applications to directly interface with JD Edwards. However, it has a few limitations. Creating an ordered list of commands can get really complex in some cases. EnterpriseOne forms typically return a lot of data that is not really used in the mobile applications.
Orchestrator (formerly called Internet of Things Orchestrator) is a catalyst for transforming how you connect external applications to JD Edwards.
Starting with JD Edwards EnterpriseOne Tools 9.2.14, Orchestrator is no longer licensed as a separate product. It is now included as part of JD Edwards EnterpriseOne core tools and infrastructure.
Among many functions, JD Edwards Orchestrator can act as:
- An interface between IoT devices and JD Edward E1
- A REST based integration platform to Cloud and Mobile applications
I was particularly impressed by some of the features of Orchestrator that can be implemented by external applications/services to enhance the user experience.
- Ability to perform Outbound REST calls. You can program an Orchestration to call an external service. That means JD Edwards now can initiate an external action such as push notifications.
- Filter data returned by JD Edwards forms. Developers can pick and choose what fields need to be passed back to a mobile app or a cloud service.
- Directly access data in JDE Tables as needed
- Send e-mail messages from the Orchestrator
- Transform/massage the data in any way you need using custom Groovy script within Orchestrations.
Companies that use JD Edwards invest heavily on the “Gold Deposits” of JDE Applications, business logic and business data. These gold deposits are of little value unless they are spent in the “Digital Economy” of Mobile Applications, Cloud Applications, IoT devices etc. In order to encourage its JD Edwards customers to become digitally connected enterprises Oracle is continually improving the functionality offered through AIS Services and the Orchestrator.
For customers who are looking at integration platforms with pre-built connectors to other Saas applications, I recommend also looking into Oracle Integration Cloud Service which I intend to cover in a future article.