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 persistence
The adapter supports event persistence for inbound processing in case of abrupt termination. Event persistence (or assured-once delivery) is a way to make sure that events are delivered once, and only once, to the endpoint in the case of a failure. During event processing, the adapter persists the event state in an event store located at the data source.
You must set up this data source using IBM BPM or WebSphere Enterprise Service Bus before you can create the event store. To use the recovery feature provided by IBM BPM or WebSphere Enterprise Service Bus, you set the AssuredOnceDelivery property in the activation specification to True. This recovery feature is set to True by default.
The adapter also provides for event persistence using an in-memory representation of the event store. When you use this feature, you need not create a JNDI data source or an external event store, and event processing is faster. However, with this feature there is no support for event recovery. In the case of server failure, the in-memory event stores are lost.
To prevent the loss of events in the case of server failure, the recommended approach is to use the database event store. To use the in-memory event persistence capability of the adapter, you must not set the EP_DataSource_JNDIName property.
When a failed event occurs and the file cannot be written to disk the JDE adapter will print the content of this failed event to a JDE trace file, to avoid event loss. The content will be between two "##########", and the trace level is INFO. The content can be copied into a new file and saved with the event ID as the file name in the directory "FailedEventFolder". When the status of the failed event record is changed from -1 to 0 in the event table the event will be handled again.