4 Integration and Interoperability

This chapter contains the following topics:

4.1 Overview of Integration and Interoperability

Although equipped with a robust set of over eighty application modules, the JD Edwards EnterpriseOne product suite typically does not cover 100% of an enterprises's application requirements. As with any implementation of enterprise software, perhaps the most important requirement is that it integrates easily with other complementary applications. In this regard JD Edwards EnterpriseOne does not take a one-size-fits-all approach. Rather, it offers several interoperability and integration patterns to ensure that system architects can apply the appropriate technology for an optimal solution to the requirements.

JD Edwards EnterpriseOne offers the following methods for interoperability and integration with other Oracle applications and third-party products:

  • Business Services Server

  • Transaction Server

  • Connectors for point-to-point integration

  • Batch interfaces for bulk data transfer

4.2 Business Services Server

This section discusses these topics:

  • Overview of Business Services Server

  • Business Services Server Architecture

  • Business Services Server Certified Platforms

  • Additional References

4.2.1 Overview of Business Services Server

The Business Services Server provides interoperability between JD Edwards EnterpriseOne and other Oracle applications and third-party systems by natively producing and consuming web services. It can also send XML over HTTP(s) in an asynchronous request/reply model when the third party does not support web service calls. The business services server is built on top of a Java 2 Platform, Enterprise Edition (J2EE) server, which can be an Oracle WebLogic Server or a WebSphere Application Server. Applications that are developed or run on the Business Services Server are written in the Java programming language.

The business services server exposes business services as web services. A web service is a standardized way of integrating web-based applications, and in JD Edwards EnterpriseOne, web services are referred to as published business services. Business services provide operations that access the business logic in JD Edwards EnterpriseOne for many supported business transactions, such as journal entries, exchange rates, accounts payable vouchers, inventory look-ups, pricing, sales orders, etc and they enable JD Edwards EnterpriseOne to expose transactions as a basic service that can expose an XML document-based interface.

4.2.1.1 Interoperability Patterns

The business services server supports the following integration patterns for interoperating with other Oracle applications and third-party applications or systems:

  • Service provider

  • Service consumer

  • Event Notification

4.2.1.2 Business Services Lifecycle

The lifecycle of a business service is similar to the lifecycle of a business function. A business service is created on the development client as a JD Edwards EnterpriseOne object using both JD Edwards EnterpriseOne tooling and JDeveloper. Object Management Workbench (OMW) controls the artifacts for add, check-in, check-out, get, restore, and delete. The business service is compiled and assembled into a deployable artifact during the package build process. Server Manager uses that deployable artifact to deploy a business services server. Subsequent client installs will include any new or updated business service artifacts.

4.2.2 Business Services Server Architecture

The following diagram depicts the relationships between the various JD Edwards EnterpriseOne servers and the Business Services Server and it also shows how the business services server provides interoperability with other Oracle applications and third-party systems:

Figure 4-1 Business Services Server Architecture

This image is described in surrounding text.

The below diagram provides an architectural overview of the business services lifecycle:

Figure 4-2 Business Services Server Lifecycle Architecture

Description of Figure 4-2 follows
Description of "Figure 4-2 Business Services Server Lifecycle Architecture"

4.2.3 Business Services Server Certified Platforms

Business Services Server is certified to run on the following platforms:

  • Linux / x86-64

  • Oracle Solaris / SPARC

  • Microsoft Windows /x86-64

  • HP-UX / Itanium

  • IBM AIX /Power

  • IBM i/Power

  • Oracle WebLogic Server

  • IBM WebSphere Application Server

4.3 EnterpriseOne Application Interface Services (AIS) Server

This section discusses these topics:

  • Overview of AIS Server

  • AIS Server Architecture

  • AIS Server Certified Platforms

  • Additional References

4.3.1 Overview of AIS Server

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. The interaction with EnterpriseOne requires an AIS Server configuration with the EnterpriseOne HTML Server.

4.3.2 AIS Server Architecture

The following illustration shows how the AIS Server functions as the interface between mobile applications and the EnterpriseOne HTML Server.

Figure 4-3 JD Edwards Mobile Architecture

Description of Figure 4-3 follows
Description of "Figure 4-3 JD Edwards Mobile Architecture"

4.3.3 AIS Server Certified Platforms

AIS is certified to run on the following platforms (operating systems and web application servers):

  • Linux / x86-64

  • Oracle Solaris / SPARC

  • Microsoft Windows /x86-64

  • HP-UX / Itanium

  • IBM AIX /Power

  • IBM i/Power

  • Oracle WebLogic Server

  • IBM WebSphere Application Server

4.4 Transaction Server

This section discusses these topics:

  • Overview of Transaction Server

  • Transaction Server Architecture

  • Transaction Server Certified Platforms

  • Additional References

4.4.1 Overview of Transaction Server

Transaction Server is a key component for the Real Time Event (RTE) notification system. RTE is an extension of the normal transaction process. This additional processing is performed to capture the JD Edwards EnterpriseOne transaction data for subsequent notification and delivery to external parties. This can also be termed as an Outbound Notification.

Transaction Server and Real time Event system consists of the following components:

  • Event - Contains JD Edwards EnterpriseOne data structure and values in binary and XML format for outbound notification in both single and aggregate format.

  • Event Category - Decides how event data is processed: for example RTE, XAPI, Z-FILE etc.

  • Transport Type - How the event is delivered using JAVA connector, COM connector, JDENET, MQ Series, JMS Topic etc.

  • Subscriber - Third party interested in receiving event and is associated with a transport type.

Following are the three life cycle events of processing in transaction server:

  • Event Generation

    Business Function calls JdeIEO_EventFinalize API - An event or set of events is inserted into F90710 table

    A JDENET message is sent to RTE server to trigger event transfer.

  • Event Transfer

    Sequencing - Provides multiple options to sequence events

    Transaction - Uses JMS Bean managed transaction.

  • Event Processing/Delivery

    Convert binary format of data structure into XML format

    Delivered to all interested subscribers based on transport type

4.4.2 Transaction Server Architecture

Figure 4-4 Transaction Server Architecture

Description of Figure 4-4 follows
Description of "Figure 4-4 Transaction Server Architecture"

4.4.3 Transaction Server Certified Platforms

Transaction Server is certified to run on the following platforms:

  • Linux / x86-64

  • Oracle Solaris / SPARC

  • Microsoft Windows /x86-64

  • HP-UX / Itanium

  • IBM AIX /Power

  • IBM i/Power

  • Oracle Weblogic Server

  • IBM WeSphere Application Server

4.5 Connectors for Point-to-Point Integrations

Connectors are point-to-point, component-based models that enable third-party applications and JD Edwards EnterpriseOne to share logic and data. JD Edwards EnterpriseOne connector architecture includes Java and COM connectors. The connectors accept inbound XML requests and expose business functions for reuse. Output from the connectors is in the form of an XML document. The connectors include:

  • Java

    Java is a portable language, so you can easily tie JD Edwards EnterpriseOne functionality to Java applications. The JD Edwards EnterpriseOne dynamic Java connector supports real-time event processing.

  • COM

    The JD Edwards EnterpriseOne COM connector solution is fully compliant with the Microsoft component object model. You can easily tie JD Edwards EnterpriseOne functionality to Visual Basic and VC++ applications. The COM connector also supports real-time event processing.

Some benefits of using connectors include:

  • Scalability

  • Multi-threaded capability

  • Concurrent users

4.5.1 Connectors Certified Platforms

The JD Edwards EnterpriseOne integration connectors run on the enterprise server. Refer to certified platforms for enterprise server for more information.

4.6 Batch Interfaces

Batch implies processing multiple transactions at the same time and usually involves movement of bulk information. Batch processing is often scheduled and is non-interactive. JD Edwards EnterpriseOne provides several model types for batch processing, and each model type has one or more capabilities that enable you to access JD Edwards EnterpriseOne data. The model types include:

  • Interface tables

  • Electronic Data Exchange

  • Table conversions

  • Output Stream Access

  • Open Data Access

4.6.1 Batch Interfaces Certified Platforms

The JD Edwards EnterpriseOne batch interfaces run on the Enterprise Server. Refer to certified platforms for Enterprise Server for more information.