The event store is a table that holds events that represent data changes until the polling adapter can process them. The adapter uses the event store to keep track of event entities. Each time a business object is created, updated, or deleted, the adapter updates the status of the event in an event table. The status of each event is continually updated by the adapter for recovery purposes until the events are delivered to a configured endpoint on the run time.
If the adapter detects that there no event table for the inbound adapter module in the PeopleSoft Enterprise server, it automatically creates one when the module is deployed to the runtime. Each event table created by the adapter is associated with a specific inbound module. The adapter does not support multiple adapter modules pointing to the same event table.
With inbound processing, the adapter polls the event entities from the event store at regular intervals. In each poll call, a number of events are processed by the adapter. The order of event processing is based on the ascending order of priority and the ascending order of the event time stamp. The events with the status, Ready for poll, are picked up for polling in each poll cycle. The adapter uses the object name and object key to retrieve the integration object or business object. The business graph is created from the retrieved information and is published to the endpoints.
If you set the activation specification property AssuredOnceDelivery to true, an XID (transaction ID) value is set for each event in the event store. After an event is obtained for processing, the XID value for that event is updated in the event table. The event is then delivered to its corresponding endpoint, and its status is updated to show that event delivery has been completed. If the application is stopped before the event can be delivered to the endpoint, the event might not be processed completely. In this case, the XID column ensures that the event is reprocessed and sent to the endpoint. Once the database connection is re-established or the adapter starts again, the adapter checks for events in the event table that have a value in the XID column. The adapter processes these events first, and then polls the other events during the poll cycles.
The adapter can process all events or filter events by business object type. The filter is set by use of the activation specification property EventFilterType. This property has a comma-delimited list of business object types. Only the types specified in the property are processed. If no value is specified for the property, no filter is applied, and all the events are processed. If the Activation specification property FilterFutureEvents is set to true, the adapter filters events based on timestamp. The adapter compares the system time in each poll cycle to the time stamp on each event. If an event is set to occur in the future, it will not be processed until that time.
The structure of the event table used by the adapter, is as follows.
Field | Description | Example |
---|---|---|
Description | Any comment associated with the event. | Account Interface event |
Event ID | The ID of the event row. | Automatically generated unique ID in PeopleSoft |
Event time stamp | The time stamp for the event. The format is mm/dd/yyy hh:mm:ss. | 06/24/2007 10:43:22 |
Event type | The type of event. | Create |
Object key | A unique identifier of the business object row for which the event was created. It is a name value pair consisting of the name of the property and the value. | |
Object name | The business graph for which the event was detected. | |
Priority | The event priority. | 1 |
Status | The event status. This is initially set to READY_FOR_POLL. | 0 |
XID | The transaction ID. | None. |
As events are retrieved and processed from the event table, the status of the event changes to reflect the cycle, as shown in the table below.
Status short name | Description | Event table value |
---|---|---|
Error processing event | An error occurred during event processing. | -1 |
Processing | The event has been picked up by the adapter but is not delivered to the event manager or endpoints. | 3 |
Ready for poll | The event has not yet been picked up by the adapter. The event is ready to be picked up. | 0 |
Success | The event has been delivered to the event manager. | 1 |