Similarly, the BPM EventsEventCounter table stores the last event ID processed by BPM Events. During failure recovery, BPM Events uses this ID to query all unprocessed events and then processes them. At this point, the infopad maintained by BPM Events is synchronized with the rest of the system.
BPM EventsEventCounter table fields
The definition of the BPM EventsEventCounter table fields are as follows:
Field
Type
Description
LAST_EVENT_ID
NUMBER NOT NULL
The last event processed by BPM Events.
LAST_UPDATE_DATE
DATE
The time of the last event processed by BPM Events.
Note: The hidden parameter, bpmprocessstore.events.transaction.size is applicable only in the case of a asynchronized mode (stand-alone classic mode). If not available in bpserver.conf, then the value of this parameter is 10. This means 10 events are processed in a single transaction to improve efficiency. You can set this parameter to the value of your choice.
