Using JD Edwards EnterpriseOne as a XAPI Originator

This diagram illustrates the flow of a XAPI event when JD Edwards EnterpriseOne functions as the XAPI originator:

In summary:

1. A JD Edwards EnterpriseOne client calls a business function on the JD Edwards EnterpriseOne server.

2. The business function uses XAPI APIs to create the XAPI request.

   The CallObject kernel in which the XAPI APIs are executing creates the XAPI request data, adding the callback function. If the XAPI executor is another JD Edwards EnterpriseOne system, the host and port of the JD Edwards EnterpriseOne server that is functioning as the XAPI originator is added to the data. The data is then sent to the Transaction server.

3. The Transaction server sends the document to the subscriber, which is the XAPI executor.

   If the XAPI executor is another JD Edwards EnterpriseOne system, the document is sent through JDENET.

4. The XAPI XML response document is sent by the XAPI executor through JDENET to the XML Dispatch kernel of the XAPI executor.

5. The XML Dispatch kernel receives the response XML document and sends the response to the XML Service kernel.

6. The XML Service kernel stores the response document and creates a file handle.

7. The XML Service kernel invokes the callback business function with the file handle.

8. The business function parses the response document using XAPI APIs, which use the XML Service kernel to load the document into memory.

9. The business function uses XAPI APIs to process the response and send it to the JD Edwards EnterpriseOne client.