3rd Party Interfaces with AIS and REST APIs

Coupling ERPs with other systems has been one key aspect since multiple systems have been in existence. Interoperability, as it is called, had many options which included basic Flat file services, EDI, Batch interfaces, Messaging adaptors, Connectors, ODA (Open Data Access ), RTE, XAPI and lately Business Services (BSSV) and finally Application Interface Services (AIS).

Nevertheless, lemme start out with some basics of connecting any 3rd party system with JDE using Application Interface Services (AIS) over REST APIs.

Application Interface Services (AIS)

AISprovides the communication interface between the applications which have the ability to perform REST calls and JD Edwards EnterpriseOne

Modern day developers of Mobile, web, and IoT 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

The AIS Server provides a JSON over REST interface, which is a light-weight interface that AIS clients (including mobile enterprise applications, AIS Java API clients, and the Simplified Applications Framework) use to interact with EnterpriseOne applications and forms

With the REST based engine for JD Edwards and now having not just AIS (REST API Engine for E1) but also an IoT orchestration (IoT Orchestrator available from TR 9.1.5.5) layer on top is the best as far as it can get.

The interaction with EnterpriseOne requires an AIS Server configuration with the EnterpriseOne HTML Server

Oracle has provided prebuilt integrations with JD Edwards EnterpriseOne for the following applications:

  • Mobile Application Framework (MAF)
  • Application Development Framework (ADF)
  • IoT Orchestrator

The purpose of the red paper is to give an overview of how can you connect to JD Edwards and work on its applications to pass and retrieve data.

This will enable to develop web/mobile applications using .NET, Java or any other frameworks available.

Pre-Requisites

  1. Application Interface Services Component
  2. JD Edwards EnterpriseOne Tools Release 9.1.4.x and above

AIS Architecture

AIS and ADF

AIS Server Architecture

The Application Interface Services (AIS) Server provides a JSON over REST interface to EnterpriseOne Applications and forms through the EnterpriseOne HTML Server. The AIS Server exposes this interface to enable communication between JD Edwards Enterprise one and other applications.

The interaction with EnterpriseOne requires an AIS Server configuration with the EnterpriseOne HTML Server

Components

Details

AIS Clients The device or application which initiates the call
–        Mobile Device
–        Any application which has the ability to perform REST based calls (.net, JAVA etc.)
–        ADF/MAF based applications/IoT Orchestrator
Note: ADF (Application Development Framework) and MAF (Mobile Application Framework) have JAVA API’s which perform the AIS calls. All other applications can call AIS services through REST based services IoT
AIS Server –        AIS server exposes all the JD Edwards EnterpriseOne forms in JSON format
–        AIS server provides REST based services to perform actions on the forms
EnterpriseOne HTML Server –        The JD Edwards EnterpriseOne Server which is linked with the AIS server
–        When a call is performed on a particular application that application gets silent launched (no rendering happens, only the session opens) on the web server
ADF Server Application Development Framework
–        This provides in built API’s to perform the AIS calls
MAF Mobile Application Framework
–        All JD Edwards Mobile Apps are developed using MAF
–        Like ADF there are in build API’s to perform form request calls
IoT Orchestrator –        IoT Orchestrator processes data from external devices and transforms it into data that can be consumed by JD Edwards EnterpriseOne
–        Orchestration is a process that consumes raw data from disparate devices and transforms the data into actionable business processes in JD Edwards EnterpriseOne
–        The EnterpriseOne IoT Orchestrator processes these orchestrations to enable the immediate, real-time transformation of raw data to valuable and transaction-capable information in JD Edwards EnterpriseOne
–        IoT Orchestrator uses AIS interface to connect with JD Edwards EnterpriseOne

I shall start with how to go ahead in the next post!

Leave a Reply