How does ADB_L_DELIVERY_STATUS work?
Article ID: KB0088360
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
| Not Applicable | - |
Description
Resolution:
These are the steps:
1. The trigger on the source table inserts the changed records into the publishing table; the initial value for ADB_L_DELIVERY_STATUS is "N", meaning NOT published.
2. The publisher adbagent polls the publishing table and sends all the records whose ADB_L_DELIVERY_STATUS are "N", to libtibrvcm layer of ADB. It then changes the ADB_L_DELIVERY_STATUS to "P", meaning Pending. The libtibrvcm layer of ADB publishes out all the messages.
3. The libtibrvcm layer of ADB receives confirmation from the subscriber.
4. The libtibrvcm layer updates the ledger file.
5. If all registered subscribers have been confirmed, the libtibrvcm generates a DELIVERY.COMPLETE advisory to the ADB layer.
6. The ADB layer receives advisory and updates the publishing table set ADB_L_DELIVERY_STATUS to 'C'.
These are the steps:
1. The trigger on the source table inserts the changed records into the publishing table; the initial value for ADB_L_DELIVERY_STATUS is "N", meaning NOT published.
2. The publisher adbagent polls the publishing table and sends all the records whose ADB_L_DELIVERY_STATUS are "N", to libtibrvcm layer of ADB. It then changes the ADB_L_DELIVERY_STATUS to "P", meaning Pending. The libtibrvcm layer of ADB publishes out all the messages.
3. The libtibrvcm layer of ADB receives confirmation from the subscriber.
4. The libtibrvcm layer updates the ledger file.
5. If all registered subscribers have been confirmed, the libtibrvcm generates a DELIVERY.COMPLETE advisory to the ADB layer.
6. The ADB layer receives advisory and updates the publishing table set ADB_L_DELIVERY_STATUS to 'C'.
Issue/Introduction
How does ADB_L_DELIVERY_STATUS work?
Feedback
Yes
No
Powered by
