Adapter for JDBC 10.3 | webMethods Adapter for JDBC Documentation | webMethods Adapter for JDBC Installation and User’s Documentation | Overview of the Adapter | Adapter Notifications | Ordered Notifications
 
Ordered Notifications
 
Stored Procedure Notifications Transaction Processing
Considerations when Using Ordered Notifications
Configuring an Integration Server Trigger and Flow Service
Using Ordered Notifications
Ordered Notifications Transaction Processing
You use Ordered Notifications to monitor multiple insert, update, or delete operations on one or more tables for a given database by creating a single notification using the same publishable document. Similar to Insert Notifications, Update Notifications, and Delete Notifications, Ordered Notifications use triggers and buffer tables to capture events that happen on specific tables in a database.
After you enable the Ordered Notification, the trigger, buffer table, and sequence remain in the database table when you:
*Shut down Integration Server.
*Disable the package containing the enabled Ordered Notification.
*Reload the package containing the enabled Ordered Notification.
In the meantime, the trigger continues to monitor the table and to insert data into the buffer table. Integration Server invokes the enabled Ordered Notification when it restarts, or when it enables or reloads the package that contains this notification.
When you disable a notification, the adapter drops the trigger, the buffer table, and the sequence.
For more information about how Ordered Notifications work, see Ordered Notifications Transaction Processing.