1 Understanding the JD Edwards EnterpriseOne Application Interface Services (AIS) Server

The JD Edwards EnterpriseOne Application Interface Services (AIS) Server is the communication interface between JD Edwards EnterpriseOne and various AIS Server clients. The AIS Server provides a JSON over REST interface (HTTP), a light-weight interface that enables AIS clients to interact with EnterpriseOne applications and forms. Any client or software language that uses JSON over REST can interface with the AIS Server.

Some of the clients that use the AIS Server to interact with EnterpriseOne include:

  • EnterpriseOne applications created with Oracle Application Development Framework (ADF), otherwise referred to as EnterpriseOne ADF applications.

  • Applications created with the AIS Client Java API.

    The Application Interface Services (AIS) Client Java API enables developers to use any development tool that works with Java APIs to create custom applications that interact with EnterpriseOne. For example, you can create a simplified kiosk application for your warehouse, an application that combines features from multiple EnterpriseOne applications into a single purpose-built interface, or an application for the latest wearable device.

  • Internet of Things (IoT) devices.

    The AIS Server enables the transfer of data from third-party IoT devices to EnterpriseOne. The EnterpriseOne IoT Orchestrator processes orchestrations on the AIS Server that contain instructions for transferring third party data to actionable business processes in EnterpriseOne.

  • Components created using Oracle Java Extension Toolkit (JET) that can run inside EnterpriseOne UX One pages.

  • EnterpriseOne mobile enterprise applications created with Oracle Mobile Application Framework (MAF).

  • Starting with EnterpriseOne Tools 9.2.3, developers can configure EnterpriseOne to automatically launch an orchestration or notification on the AIS Server from an EnterpriseOne interactive or batch application.

The interaction with EnterpriseOne requires an AIS Server configuration with the EnterpriseOne HTML Server. Figure 1-1 illustrates how the AIS Server functions as the interface between AIS clients and JD Edwards EnterpriseOne.

Figure 1-1 EnterpriseOne Architecture with an EnterpriseOne AIS Server

Description of Figure 1-1 follows
Description of ''Figure 1-1 EnterpriseOne Architecture with an EnterpriseOne AIS Server''

Note:

EnterpriseOne ADF applications and the EnterpriseOne Orchestrator Studio (which is built with Oracle ADF) also require an Oracle WebLogic Server with ADF runtime (not depicted in illustration).

1.1 Additional EnterpriseOne HTML Server Instance for Processing AIS Requests

You can set up an additional HTML Server instance for processing AIS Server requests only. This is recommended so that the performance of the EnterpriseOne HTML Server used by EnterpriseOne web client users is not impacted by AIS Server requests.

With this configuration, make sure that you select the "Enable AIS Watchlist Execution" check box in the Form Service section of the HTML Server Web Runtime settings in Server Manager. This option applies only to an EnterpriseOne configuration with an AIS Server. If you select this check box, you must configure the settings for the AIS Server in the same Form Service section.

Figure 1-2 shows the EnterpriseOne architecture with an additional, dedicated HTML Server instance for processing AIS Server requests. The illustration also depicts the configuration files that enable the communication between servers.

Figure 1-2 Dedicated HTML Server for AIS Processing Architecture

Description of Figure 1-2 follows
Description of ''Figure 1-2 Dedicated HTML Server for AIS Processing Architecture''