J.D. Edwards EnterpriseOne Interoperability Framework

Topics:

J.D. Edwards EnterpriseOne provides for integration with systems through its interoperability framework. The adapter uses the EnterpriseOne framework and leverages various integration access methods to provide the greatest amount of flexibility and functionality.

The iWay Application Adapter for J.D. Edwards EnterpriseOne supports the following integration access methods:

The following image diagrams the J.D. Edwards EnterpriseOne inbound processing (from the EIS to application server) framework. It shows the EnterpriseOne components and the agent adapter in the inbound processing sequence.

The adapter uses the J.D. Edwards EnterpriseOne ThinNet API to communicate with the EnterpriseOne application. Using the ThinNet API, the adapter can invoke one or more Master Business Functions (MBFs) in a single Unit Of Work (UOW). When any of the MBF fail, the entire UOW fails, preventing partial updates. Because the adapter runs the MBF, validation of data, business rules, and communications to the underlying database are handled by the EnterpriseOne application.

J.D. Edwards EnterpriseOne Outbound Processing Framework

The following image diagrams the J.D. Edwards EnterpriseOne outbound processing framework. It shows the EnterpriseOne components and the listener adapter in the outbound processing sequence.

In the outbound process, the event starts when a specific MBF is executed in the EnterpriseOne environment. The MBF writes the required information for the event into the appropriate interface table and then notifies the subsystem Batch Function (BF) that an event occurred. The subsystem BF then places an entry about the event on the Subsystem Data Queue.

The outbound subsystem retrieves the data queue entry and looks in the Data Export Control table for the external processes to notify. The outbound subsystem then calls the iWay Application System Adapter for J.D. Edwards EnterpriseOne listener with notification. The listener passes the notification to the generator. The generator then uses the J.D. Edwards EnterpriseOne ThinNet API to retrieve the appropriate information from the interface table.