You get to create the buffer table(s) and trigger(s) to populate them manually. Often, you can use buffer tables, triggers and sequences created by the Insert, Update and Delete notifications as templates.
Once your triggers are populating the buffer tables correctly, you can create the BasicNotification to poll it on some regular frequency. When the notification finds documents in the buffer table it publishes a notification document for each row with the columns you specify. After the document is published the row is deleted (unless you specify otherwise).
One reason for using BasicNotifications is that the DBA’s in some IT shops do not allow webMethods developers to create database objects. By using a BN, you have to manually create and deploy the database. This can be done by the DBA where required.
Another advantage of using BasicNotifications is that these database objects are not deleted when the notification is disabled. Disabling the notification simply stops the polling of the buffer table. When the notification is enabled again, polling resumes and notification documents are published for any rows in the buffer table.
To build your own triggers, you need to be reasonably proficient in the procedural SQL language provided by your DBMS vendor. Examining the triggers generated by WM for Insert/Update/Delete/Ordered notifications can help get you started.
HTH,
Mark
#webMethods#Integration-Server-and-ESB#broker#Universal-Messaging-Broker