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