Event triggers and processes

Creating, updating, or deleting records in a Siebel business application is treated as an event. Siebel supports Visual Basic scripts and Siebel eScripts embedded in the Siebel business component event handlers to populate the event table.

The “IBM Resource Adapter Events” Siebel business component stores information about the event. This information is used by the 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.

Event distribution
Field Description Example
Description Any comment associated with the event. Account interface event
Event ID 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 The unique identifier which identifies 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. Name=IBM
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

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 using 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 property set are then populated into the business object.

The retrieval mechanism, defined by you, can be used to perform optimized retrievals. The adapter uses the event method 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 event method 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 automatically populated by the enterprise service discovery wizard.

An example of an event method is the QueryByExample 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, seen in the table below. This is different from the status that is maintained in the staging table.

Status of events during an event notification
Status short name Description Event table value
Error processing event There was an error processing the event. -1
Processing The event has been picked up by the adapter but not yet 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

After an event is successfully sent to the endpoints and marked as Success; the 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.

Note: WebSphere® Adapter for Siebel Business Applications does not support XA transaction or local transaction.

Terms of use |

Last updated: Sun Mar 12 11:38:27 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)