Posted: Thu Mar 04, 2004 7:45 am Post subject: two-phase commits with Domino
Novice
Joined: 09 Feb 2004 Posts: 20
I have a Java application which GETs a message and then loads it into a Domino db with an SQL statement. I would like to use a two-phase commit, but I'm not sure how to get the feedback from the db, other than any errors that my Java app may catch. Is this sufficient? Or do I need some kind of XA resource manager as I've read about? Does such a thing even exist in Domino?
Domino SQL cannot take part in an XA coordinated transaction and I am fairly certain that it has no two phase commit either. In other words it is non-transactional (at least until IBM start using a RDB in Notes version 7).
However you can still code the application to use MQ transactions so that you get the messages under syncpoint, and only when Domino has stored the data (document) successfully do you commit the MQGET.
That way you should not lose the data although there is a small chance that a system crash could result in data in both the message queue and the database. If your application can cope with that situation then you have all the angles covered (for example check the message backout count and if greater than zero check to see if you have already updated the database for this message).
You can use SQL to access Domino - or you could use the Notes APIs from Java. You may get better return code info from the API calls. We have written a similar application and it works fine with JDBC calls but we later converted it to use the Notes Java APIs for better control.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum