| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| when to use property co-ordinated transaction in bar file |
« View previous topic :: View next topic » |
| Author |
Message
|
| vijayakumar |
 Posted: Mon Mar 28, 2011 10:47 pm Post subject: when to use property co-ordinated transaction in bar file |
 |
|
Centurion
Joined: 01 Aug 2010
Posts: 101
|
| which is more effective of using globally coordinated transaction or partially transaction?. In which scenario we need to use globally coordinated transaction? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Mar 29, 2011 4:27 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
In most situations, you would not turn transactionality on. You would set transactionality to off.
This is because most transactions require compensation to reverse pieces of work and this compensation is usually more complicated than a simple rollback.
Also, if you have a flow with Request-Response, where there is MQInput, MQOutput, and MQGet, you will notice it will timeout if transactionality is on. Because the flow cannot retrieve the message from the reply queue , even when it is there.
Each business case is different. Transactionality , as implemented in Broker, is a low-intelligence offering that can be used sometimes. More often than not, you need higher intelligence to figure things out and take the right actions.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Mar 29, 2011 5:25 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I have to disagree. Transactional integrity and rollback is one of the strongest features of MQ and WMB.
If you make MQ callouts inside the flow, these need to be outside the unit of work.
However most message flows should be transactional overall - certainly if you are dealing with MQ and databases, these can all take part in global unit of work (XA).
Use of non-transactional protocols is of course at your own risk.  |
|
| 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
|
|
|
|
