I'm Copying this from TIBCO Documentation. All activities that use the same JDBC Connection shared configuration resource are part of the same transaction. It is possible to use more than one JDBC Connection in the same transaction group. However, only activities that use the same JDBC Connection are guaranteed to commit or rollback together when the transaction completes. If you have more than one JDBC Connection in the transaction group, each set of activities that uses a JDBC Connection is considered a separate transaction. Example : Lets Assume there are four JDBC update activities (1,2,3,4) in the transaction group, Each inserts a row into Table. Where, First two activities(1,2) uses a different JDBC connection to that of (3,4). When we run the process, after the 3rd activity group errored out due to some reason. In this case 1,2 activities work will be committed since they use same JDBC connection. 3,4 activities work will not be committed since they use different JDBC connection and as they are part of different transaction.
Thanks for the video..I have a question.If in another scenario 2 jdbc activities of different connection in 1 group where one fails,will the other commit?
Thank you for all your videos on TIBCO
Good one.... Simple and clear
Simple and perfect explanation
Thankq,..u explained very clearly.
Are you still working in TIBCO?
These videos are really amazing.. could you pls upload few more videos regarding webservices?
I'm Copying this from TIBCO Documentation.
All activities that use the same JDBC Connection shared configuration resource are part of the same transaction. It is possible to use more than one JDBC Connection in the same transaction group. However, only activities that use the same JDBC Connection are guaranteed to commit or rollback together when the transaction completes.
If you have more than one JDBC Connection in the transaction group, each set of activities that uses a JDBC Connection is considered a separate transaction.
Example : Lets Assume there are four JDBC update activities (1,2,3,4) in the transaction group, Each inserts a row into Table. Where, First two activities(1,2) uses a different JDBC connection to that of (3,4). When we run the process, after the 3rd activity group errored out due to some reason. In this case 1,2 activities work will be committed since they use same JDBC connection. 3,4 activities work will not be committed since they use different JDBC connection and as they are part of different transaction.
Thanks for the video..I have a question.If in another scenario 2 jdbc activities of different connection in 1 group where one fails,will the other commit?
If diff connections are used they dont become part of 1 transaction. So failure of 1 activity will not cause 2nd to roll back.