## Getting Started with JD Edwards EnterpriseOne Application Real-Time Events

This chapter discusses:

- JD Edwards EnterpriseOne Application Real-Time Events overview.

- JD Edwards EnterpriseOne Application Real-Time Events implementation.

### JD Edwards EnterpriseOne Application Real-Time Events Overview

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.

Naming Conventions

Real-time events use this naming standard:

RTXXYYY where XX is the product area, and YYY is the type (for example, OUT, HDR, DTL).

Transaction-Specific Instructions

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.

Event Name | The name of the event.
Event Description | A description of the event.
Event Type | RTE for real-time events; XAPI for XAPI events.
Event Category | Defined as single or container event.
Product Code | The system code.
Reliable Delivery | Values are: 1 or Y: Reliable 0 or N: Volatile
Timeout Threshold | This field applies only to reliable events for which an initial delivery attempt fails. The value determines the maximum amount of time that has to pass from the event creation to the time when the event will be discarded if not delivered successfully. Events with a threshold of zero never expire.
Data Structure | The JD Edwards EnterpriseOne data structure that is used for the current single event.
Event Relationship | The relationship of the current single event to other real-time events.

Defining 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.

See Also

JD Edwards EnterpriseOne Tools 8.98 Interoperability Guide, “Using Guaranteed Events.”

### JD Edwards EnterpriseOne Application Real-Time Events Implementation

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 in the About This Documentation, with information about where to find the most current version of each.

#### Implementation Steps

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:

Step | Reference
1. Define and activate real-time events. | See JD Edwards EnterpriseOne Tools 8.98 Interoperability Guide, “Using Guaranteed Events” Defining Events.