This topic describes the Siebel application architecture and how it works.
Asynchronous event delivery is supported by the Siebel event component. Delivery of events to endpoints can only exist in one of four event states.
Event | Descriptions |
---|---|
Event marked as new/ready-to-be-polled in EIS | No record of the event is in thestaging table. |
Event marked as new/ready-to-be-polled in EIS | One or more records exist in staging table referring to this event. |
Event marked as in progress in EIS | One or more records exist in staging table referring to this event. |
Event marked as in progress in EIS | No record of event in staging table. |
An event is represented by a row in the event component that contains the information necessary to instantiate the business service. The event component has fields to represent the information required to process the event. The events in this component within Siebel also have a status that the resource adapter uses when processing events.
Parent topic: Outbound and inbound events
Related concepts
Outbound and inbound interactions
Components
Event triggering and processing