This chapter contains the following topics:
Section 3.1, "JD Edwards EnterpriseOne Application Real-Time Events Overview"
Section 3.2, "JD Edwards EnterpriseOne Application Real-Time Events Implementation"
A real-time event (RTE) is a notification to a third-party system that a business transaction has occurred in the JD Edwards EnterpriseOne system. Third-party systems can subscribe to the JD Edwards EnterpriseOne system to receive notification when a specific transaction occurs. You can use any JD Edwards EnterpriseOne interface, such as HTML, WIN32, and terminal servers to generate real-time events. Real-time events can be used for both synchronous and asynchronous processing.
A XAPI event is similar to a real-time event in that an outbound notification is sent to subscribers when a specified transaction occurs in the JD Edwards EnterpriseOne system. The difference between a real-time event and a XAPI event is that the subscriber to a XAPI event returns a reply to the originator. XAPI events use the same infrastructure as real-time events. XAPI events also provide a way for two different JD Edwards EnterpriseOne systems to communicate with each other.
The purpose of this guide is to provide information about the JD Edwards EnterpriseOne real-time and XAPI events.
Real-time events use this naming standard:
RTXXYYY where XX is the product area (for example AB, PO, or SO), and YYY is the type (for example, OUT, HDR, DTL).
The discussions of the real-time events in this guide include a table similar to this table. This table explains the data that is contained in these tables.
The name of the event.
A description of the event.
RTE for real-time events; XAPI for XAPI events.
Defined as single or container event.
A single event is defined as one data structure. For example, RTABHDR (D0100085A), whereas a container event is a group of single events that are included in the RTE output. For example, RTABOUT may include the single events RTABHDR, RTABEAOUT, and RTABPHOUT.
The system code.
The JD Edwards EnterpriseOne data structure that is used for the current single event.
The relationship of the current single event to other real-time events.
Events are defined in the Interoperability Event Definition table (F90701). You use the Event Definition Workbench program (P90701A) to add new single and container events to the Interoperability Event Definition table and to review the existing events. You add single events by event name. When you add a single event, you must include the JD Edwards EnterpriseOne data structure. A container event contains single events, aggregate events, or both.
|
Note: The system publishes container events, which contain the data from the contained single events, rather than publishing the single contained events. You can use the Connector Events Client to view published events. |
|
Note: The real-time events that are described in this guide have already been set up in the data that is shipped with the software. You can use the Event Definition Workbench program to review these real-time events. |
This section provides an overview of the steps that are required to use application real-time events.
In the planning phase of your implementation, take advantage of all JD Edwards EnterpriseOne sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface with information about where to find the most current version of each.
Implementing any application real-time events must be preceded by setting up the corresponding JD Edwards EnterpriseOne system.
The Getting Started chapter in the implementation guide for each of these systems contains specific implementation information for that system.
After you have set up the relevant JD Edwards EnterpriseOne systems for the application real-time events you are using, you must complete this step to set up the application real-time events:
Define and activate real-time events.
See JD Edwards EnterpriseOne Tools Interoperability Guide, "Using Guaranteed Events," Defining Events.