IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JD Edwards EnterpriseOne > Overview of WebSphere Adapter for JD Edwards EnterpriseOne > Technical overview > Inbound processing

Event store

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 keep track of 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 there is no event store for the inbound module in the IBM BPM or WebSphere Enterprise Service Bus, it automatically creates one when the application is deployed to the runtime. Each event store 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. This means that all the real-time events that the adapter subscribes to are delivered to the adapter without any loss of events. Because it is possible for the JD Edwards EnterpriseOne transaction server to send duplicate real-time events to the adapter, the adapter provides assured-once event delivery. This means that 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, you must set the AutoAcknowledge activation specification property to False. Otherwise, the assured-once delivery feature will not work.

When you set the AssuredOnceDelivery activation specification property to True, the adapter stores an XID (transaction ID) value for each event in the event store.

When a real-time event is obtained, it is processed as follows:

  1. The XID value for the event is updated in the event store.

  2. The event is delivered to its corresponding endpoint.

  3. The event entry is deleted from the event store.

  4. An acknowledgement is issued to the JD Edwards EnterpriseOne transaction server.

Inbound processing