Using JD Edwards EnterpriseOne as a XAPI Executor

This diagram illustrates the flow of a XAPI event when JD Edwards EnterpriseOne functions as the XAPI executor.

In summary:

1. The XAPI originator sends the XAPI XML request document to the XML Dispatch kernel through JDENET.

2. The XML Dispatch kernel receives the document and sends the event request and routing information to the XML Service kernel.

3. The XML Service kernel stores the document and creates a file handle for the XAPI request.

   The XML kernel also creates XML-based routing information. The XML Service kernel uses the F907012 table to find the business function that will process the request.

4. The XML Service kernel invokes the business function with the XML request handle and the routing information handle.

5. The business function uses XAPI APIs to parse and process the document. XAPI APIs load the XAPI XML request document into memory.

6. The business function processes the XAPI event request.

   The business function also creates a XAPI response. The message type for the response must be xapicallmethod. The business function also passes the routing information handle.

7. The business function uses XAPI APIs to send the XAPI response data including the routing information, to the Transaction server.

8. The Transaction server creates the XAPI XML response document and uses the routing information to send the response document to the XAPI originator.

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