why JDBC Notifications support LOCAL_TRANSACTION mode only ?

, ,
1

I am not able to create jdbc adapter notification using a JDBC adapter connection (Transaction Type =NO_TRANSACTION ) . It is throwing below error

ART.116.3038] Adapter Runtime (Notification): Error in Notification Callback:enableCallback notification “NotificationName”

[ADA.1.337] Notification should not be configured on a connection with “NO_TRANSACTION”.


why Insert Notifications, Update Notifications, Delete Notifications, and Ordered
Notifications support LOCAL_TRANSACTION mode only ??? :roll: .

2

Hi Chethan,

Yes you are right, Insert Notifications, Update Notifications, Delete Notifications and Ordered
Notifications support LOCAL_TRANSACTION mode only.

Thanks,
Vicky

3

@chethan,

In addition to that,

Ref: http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/adapters_estandards/Adapters/JDBC/JDBC_6-5/6-5_JDBC_Adapter_Install_and_Users_Guide.pdf
Page: 81
If you are configuring a Basic Notification and using the Exactly Once Notification and Delete selected records options, you must configure the notification to use a LOCAL_TRANSACTION connection.

Notifications require a control over transactions so that documents are published successfully. In case of failure it has to manage the buffer table, other related resources accordingly, so the in next cycle all unprocessed docs are picked up and published.

That’s why basic notification does not require this. You have to manage the buffer table row statuses.

HTH.

Thanks,
Rankesh

4

Hello,
we are using WM 9.9 with JDBC adapter JDBC_9.0_Fix15. We have tried to configure a Basic Notification with Exactly Once and Delete Records options to use a MSSQL NO_TRANSACTION connection, and the notification seems to work correctly.
Can you please describe in more detail what is the problem of this approach, and in what situations it might not work correctly?
Thank you.
Richard