Setting Up an Alerter
An alerter on an Oracle database uses the Oracle AQ package; an alerter on a Microsoft SQL Server 2005 or above database uses the Service Broker component to exchange information between sessions, synchronously allowing two or more sessions in the same database instance to communicate.
Microsoft SQL Server 2005 or above is shortened as Microsoft SQL Server hereafter.
As shown in the following figure, when a source table is updated with data and the commit_and_notify stored procedure is run, a trigger copies the data to the publishing table and notifies Oracle AQ or Microsoft SQL Server Service Broker that the publishing table has changed. The alerter receives the notification from Oracle AQ or Microsoft SQL Server Service Broker and sends a message to the adapter to inform that a publishing table has changed. The adapter then polls all its configured publishing tables for the new data and sends it on a subject to the TIBCO transport.The following table shows the alerter process on an Oracle or Microsoft SQL Server database.
If there are multiple publishing tables under the same database account, you can use the commit_and_notify_table stored procedure to specify that only a particular table is checked by the adapter. This prevents the adapter from needlessly checking all its publishing tables for updates when only one table has been updated with new data. This notification can be sent to one or more adapter configurations.