Event store (JD Edwards)

The event store is a persistent cache where event records are saved until the polling adapter can process them. The adapter uses event stores to record inbound events as they make their way through the system.

Each time a real-time event is received, the adapter updates the status of the event in an event store. The status of each event is continually updated by the adapter for recovery purposes until the events are delivered to the endpoint. If the adapter detects that no event store exists for the inbound module in IBM® App Connect Enterprise, it creates one automatically when the application is deployed to the run time. Each event store that is created by the adapter is associated with a specific inbound module. The adapter does not support multiple adapter modules pointing to the same event store.

When the adapter polls the JD Edwards EnterpriseOne transaction server and receives a real-time event, it creates an entry in the event store for each event that matches the search criteria specified in the activation specification properties. The adapter records the status of each new entry as NEW.

If a real-time event is successfully delivered, the corresponding event store entries are deleted. For failed events, the entries remain in the event store.

Assured once delivery

The JD Edwards EnterpriseOne transaction server provides guaranteed event delivery quality of service. All the real-time events to which the adapter subscribes are delivered to the adapter without any loss. The JD Edwards EnterpriseOne transaction server can send duplicate real-time events to the adapter, therefore the adapter provides assured once event delivery; each event is delivered once and only once. To enable assured once delivery, you must set the AssuredOnceDelivery activation specification property to True.

When you set the AssuredOnceDelivery activation specification property to True, the AutoAcknowledge activation specification property is set to False automatically.

When a real-time event is obtained, it is processed in the following way.
  1. The event is delivered to its corresponding endpoint.
  2. The event entry is deleted from the event store.
  3. An acknowledgment is issued to the JD Edwards EnterpriseOne transaction server.