|
Topics: |
J.D. Edwards EnterpriseOne supports multiple methods and technologies to provide interoperability. The three supported entry points are:
You configure the adapter to send requests to EnterpriseOne. The adapter processes requests for EnterpriseOne Master Business Functions (MBFs), embedded in XML documents, and forwards them to a back-end EnterpriseOne system. The resulting response information is then returned and processed for further routing.
The adapter can receive an XML request document from a client and call a specific function in the target Enterprise Information System (EIS). The adapter acts as a consumer of request messages and provides a response.
You can configure a listener, known as a channel, for the adapter to receive messages from EnterpriseOne. The information the listener receives is used to build an XML record and is forwarded to any specified disposition for further processing. Listeners are consumers of EIS-specific messages and may or may not provide a response.
When integrating external listeners into EnterpriseOne using flat file input, the files are imported through a batch program and placed on an unedited transaction table. The records on the transaction table are processed by a batch program that makes calls to the appropriate MBF.
The database table method bypasses the first step in the flat file method, and records are written directly to the unedited transaction table. The records on the transaction table are processed by a batch program that makes calls to the appropriate MBF.
The third method, calling the MBF directly, bypasses the batch processing completely and provides synchronous access to EnterpriseOne.
Integrating an EnterpriseOne listener with external systems is similar to the inbound process, except in reverse. The Data Export Control table maintains the determination of whether a transaction must be integrated with an external system. When a transaction must be integrated, the MBF handles logging of all additions, changes, and deletions to the unedited transaction table. After the transaction information is written to the table, a key for that record is sent from the MBF to the subsystem data queue.
The subsystem data queue triggers the processing of the new record by launching an outbound subsystem batch process that is generic and handles all outbound transactions. The outbound subsystem then accesses the Data Export Control table to determine the configured external subscriber to run.