This topic describes event triggering and processing.
The creation, update or delete of any record in the Siebel eBusiness application is treated as an event. Siebel supports Visual Basic scripts and Siebel eScript embedded in the Siebel Business Component event handlers to populate the event table.
The “IBM Adapter Events” business component stores information about the event. This information is used by the resource adapter during event subscription to build the corresponding business object and send it to the registered Endpoints.
Inbound business objects that are returned from the adapter are of the same types as business graphs used during outbound interactions. Triggers are placed on the base Siebel business objects.
Field | Description | Example |
---|---|---|
Object key | The unique identifier which identifies the business object row for which the event was created. | 1-2ORT |
Object name | The business graph for which the event was detected. | EAIAccountInterfaceBG |
Event type | The type of event. | Create |
Priority | The event priority. | 1 |
Status | The event status. This is initially set to READY_FOR_POLL. | 0 |
Description | Any comment associated with the event. | Account interface event. |
Event ID | ID of the event row. | |
Event timestanp | The time stamp for the event. The format is MM/dd/yyy HH:mm:ss | 02/24/2005 11:37:56 |
The event is retrieved from the event table and the information is used to retrieve the integration object, which is then used to create a business graph to be published to Endpoints of interest. There are two ways in which the event can be retrieved by the adapter; the default mechanism and a user defined method that uses metadata contained in the business object.
The default retrieval mechanism uses the EAI Siebel Adapter business service to execute a Query based on the object key. The values of the resulting PropertySet are then populated into the business object.
The user defined retrieval mechanism can be used to perform optimized retrievals. The resource adapter uses the user defined “EventMethod” metadata during retrieval as the method on the business service. The business service is also metadata information on the top level business object. You can specify the “EventMethod” metadata during business object discovery at design time. The business service is also metadata but this is mandated by the business service in which this business object was generated against, and is populated by the EMD.
An example of an “EventMethod” is the QueryById method on a Siebel Application Services Interface business service such as Siebel Account.
As events are retrieved and processed from the event table, the status of the event goes through a cycle. This is different from the status that is maintained in the staging table.
Status short name | Description | Event table value |
---|---|---|
Ready for poll | The event has not yet been picked up by the resource adapter. The event is ready to be picked up. | 0 |
Processing | The event has been picked up by the resource adapter but not yet delivered to the event manager or EndPoints. | 1 |
Success | The event has been delivered to the event manager. | 3 |
Error processing event | There was an error processing the event. | -1 |
After an event is successfully sent to the EndPoints and marked as Success. The resource adapter deletes the successful event from the table.
The business graph is also populated with the event type from the table which is entered as a top level verb on the business graph. This is used by the function selector during notification.
For more information on the function selector, see Foundation Classes.
Parent topic: Outbound and inbound events
Related concepts
Outbound and inbound interactions
Asynchronous event delivery
Components