If you want to use the automatic notification feature of the adapter, you will have to configure three notification operations for each monitored table - one for DELETE, one for INSERT, and one for UPDATE. I do not recommend going this route, because the adapter will not process notifications in historical order across multiple operations. I.e. if you do an INSERT followed by an UPDATE on the same row, you can receive the update notification before the insert notification.
The alternative is to use basic notification, with three handwritten triggers that all insert into a common buffer table. One additional column for the operation type should be included. That could be a CHAR(1) column, set to ‘D’, ‘I’, or ‘U’, for DELETE, INSERT, or UPDATE. On the receiving side, check this value first, and then branch to an appropriate operation.
#Adapters-and-E-Standards#webMethods#Integration-Server-and-ESB