An event-notification mechanism enables a connector to determine
when an entity within an application changes. Implementation of an
event-notification mechanism is a three-stage process, as Table 39 shows.
Table 39. Stages of an event-notification mechanism
Stage of event-notification mechanism | For more information |
---|---|
Create an event store that the application uses to hold notifications of events that have changed application business entities. | "Implementing an event store for the application" |
Implement an event detection mechanism within the application. Event detection notices a change in an application entity and writes an event record containing information about the change to an event store in the application. | "Implementing event detection" |
Implement an event retrieval mechanism (such as a polling mechanism) within the connector to retrieve events from the event store and take the appropriate action to notify other applications. | "Implementing an event store for the application" |
In many cases, an application must be configured or modified before the connector can use the event-notification mechanism. Typically, this application configuration occurs as part of the installation of the connector's application-specific component. Modifications to the application might include setting up a user account in the application, creating an event store and event table in the application database, inserting stored procedures in the database, or setting up an inbox. If the application generates event records, it might be necessary to configure the text of the event records.
The connector might also need to be configured to use the event-notification mechanism. For example, a system administrator might need to set connector-specific configuration properties to the names of the event store and event table.