Event store structure, WebSphere Adapter for Email

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 > Email > Reference
Event store structure

Each time an email is read by the adapter during inbound communication, 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 a configured export on the run time.

When event persistence is optionally configured, the adapter implements the event store in an Email-specific relational table called EmailEventTable. This table is tied to event recovery operations. When event persistence is not configured, the adapter determines which events need to be recovered based on the emails present in the staging directory. The event recovery feature is activated when the adapter terminates abruptly. Upon termination, events that are still being processed, or processed but not completely posted to the service, still require completion. The adapter reads the event store to determine which events still need to be processed and then facilitates their completion. The event persistence framework takes care of delivering the event only once to the target service.
Each inbound module has a unique connection and is associated with one event store. Multiple modules pointing to the same event store is not supported
The following table illustrates the structure of the WebSphere Adapter for Email event store.

Event table structure
Column name Property type Description
EVNTID Varchar (255) The event ID associated with the polled inbound event. The ID is taken from the message ID of the polled email.
EVNTSTAT Integer
The status of the event as it moves through the system. Valid values are NEW(0), FETCHED(3), PROCESSED(1) and FAILED(-1).
An event is logged in the event store as NEW(0), when the adapter discovers a new email on the mail server that meets the specified search criteria noted in the activation specification properties.
When the adapter starts fetching an event from the mail server to the local system in RFC822 format, it is logged in the event table as FETCHED(3) with the value Null XID. For an event, FETCHED(3) with some XID value (not NULL), the XID is created with transaction in progress and ready to be delivered (in this situation, event can be recovered).

Event status values:

NEW(0): The event is ready to be processed.
FETCHED(3): The event is picked up for processing.
PROCESSED(1): The event is processed and delivered successfully.
FAILED(-1): The event is not processed due to one or more problems.

XID Varchar (255) It is used by the adapter for assured event delivery and recovery.
BQTOTAL Integer Not used by the adapter.
BQPROC Integer Not used by the adapter.
EVNTDATA Varchar (255) Stores the name of the folder on the mail server where the email event was polled.

Reference information

Related concepts:

Event store

Column name	Property type	Description
EVNTID	Varchar (255)	The event ID associated with the polled inbound event. The ID is taken from the message ID of the polled email.
EVNTSTAT	Integer	The status of the event as it moves through the system. Valid values are NEW(0), FETCHED(3), PROCESSED(1) and FAILED(-1). An event is logged in the event store as NEW(0), when the adapter discovers a new email on the mail server that meets the specified search criteria noted in the activation specification properties. When the adapter starts fetching an event from the mail server to the local system in RFC822 format, it is logged in the event table as FETCHED(3) with the value Null XID. For an event, FETCHED(3) with some XID value (not NULL), the XID is created with transaction in progress and ready to be delivered (in this situation, event can be recovered). Event status values: NEW(0): The event is ready to be processed. FETCHED(3): The event is picked up for processing. PROCESSED(1): The event is processed and delivered successfully. FAILED(-1): The event is not processed due to one or more problems.
XID	Varchar (255)	It is used by the adapter for assured event delivery and recovery.
BQTOTAL	Integer	Not used by the adapter.
BQPROC	Integer	Not used by the adapter.
EVNTDATA	Varchar (255)	Stores the name of the folder on the mail server where the email event was polled.