Event notification

The connector relies on Siebel Visual Basic scripts embedded in business component event handlers to populate an event queue table. When an event occurs in Siebel, the Visual Basic script places the event in the event queue table. The connector polls the event queue table at configurable intervals and processes the events sequentially.

The connector uses the Siebel_CW_Event and Siebel_CW_Archive tables for event notification. You create these tables as part of the connector installation, and reside within the Siebel application. They are represented by the Siebel_BO_CWEvent and Siebel_BO_CWArchive business objects. To retrieve an event from Siebel, the connector calls the business object handler method doRetrieve() on the business object Siebel_BO_CWEvent. This business object queries the Siebel CW Events object and retrieves all events with a Status value of 0. The order in which the connector retrieves events is specified by the priority and sort properties on the Retrieve verb in the Siebel_BC_CWEvent business object. For every event the connector retrieves from the event table, it then retrieves the actual business object that triggered that event.

When the connector has processed an event, it inserts the event into the archive table by calling the business object handler doCreate() method, and it removes the event from the event table by calling the doDelete() method. When an event is processed successfully, the status field is updated to Success. If an event is not processed because of an error, the status field is updated to Failure. If an event is unsubscribed, the status field is updated to Skipped.

See "Creating the event and archive tables" for instructions on creating the queue tables.

Copyright IBM Corp. 1997, 2004