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 > Adapter Toolkit > Implementing code from the IBM WebSphere Adapter Toolkit > Inbound event notification > Possible event store implementations
Implementing the event store with a database
If an EIS application incorporates a database, you can use the database to store event information.
Where to store events
To locate the event store in the EIS application database, create a new, separate WebSphere event table there. The table then functions as the event store for event records. Each column of the table would reflect one of the fields mentioned in Table 1; each row would reflect a unique event.
Implementing event detection
If the application has no built-in method for detecting events and the database that the application is running on provides database triggers, you could implement row-level triggers to detect changes to application tables. When changes occur in one of these tables, the triggers would write new event records to the event table.
If possible, avoid full table scans of existing application tables as a way of determining whether application tables have changed.
Retrieving events
The EventStore implementation would need to employ the available database APIs to gain access to the contents of the event table.
Event store implementation