An event store, also known as an event component, is a business component in Siebel where entries for each event are stored until they are processed by the adapter.
The back-end enterprise information system generates the events in the form of event records. These records are stored in the Siebel event component configured earlier. This event information is used by the adapter during event subscription to build the corresponding business objects and send them to their registered endpoints.
With inbound processing, the adapter polls the event records from the event component 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 an event is successfully posted, the entry is deleted from the event table. For failed events, the entries remain in the event table. For the event type, Delete, the keys are set on the data object, the business graph is created and published to the endpoints, and the object is not retrieved from Siebel.
The structure of the Siebel event table, used internally 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 Siebel |
Event time stamp | The time stamp for the event. The format is mm/dd/yyy hh:mm:ss. | 02/24/2005 11:37:56 |
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. The object key format for the Siebel business object is id=XXXX. | ID=1-CT8 |
Object name | The business graph for which the event was detected. | EAIAccountInterfaceBG |
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 |