| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How 2 maintain trans. integrity when updating ext. db? |
« View previous topic :: View next topic » |
| Author |
Message
|
| durkoi |
 Posted: Mon Apr 07, 2003 12:26 am Post subject: How 2 maintain trans. integrity when updating ext. db? |
 |
|
Newbie
Joined: 07 Apr 2003
Posts: 1
Location: Hungary or elsewhere
|
Guys,
My question is how is it possible to maintain transactional integrity when performing an update type operation on an external database from WMQI via a compute node?
If the processing of the message fails, how can I roll back the e.g insert operation on the database that already returned a success flag?
Some say, if I set the transactional integrity flag in the input node, then it will also take care of any subsequent db operations when rolling back the processing, I am not convinced though.
Can anyone please let me know how to handle this?
Cheers,
durkoi |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Apr 07, 2003 6:44 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
To achieve this functionality you should use 2-phase commit protocol. In this case, your queue manager will act as transaction manager and your database manager will participate in global transaction as resource manager. You will have to configure your message flow to run in Global Coordinated Transaction mode. By default your transactions are broker coordinated.
You may search for "Transaction" in this forum to find relevant topics.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
