| Author |
Message
|
| Monk |
 Posted: Tue Aug 04, 2009 9:17 pm Post subject: Help with Transaction with different technologies |
 |
|
Master
Joined: 21 Apr 2007
Posts: 282
|
Hi All,
I have a enterprise system as following.
Front end apps (COM)
Middleware(COM+)(Does message transformation / routing)
Backend databases (Oracle, SQL, Mainframes,COM+ systems)
Currently the transactions from front end to backend is coordinated by COM+ MTS.
We are looking at replacing the middleware with message broker and MQ.
1.How can i achieve transaction in this scenario across all three layers because now we have MS and IBM technologies?.
2. Can MB participate in a 2PC like MQ?.
3. Is it best to have IBM technologies replace MS technologies completely
4. if I do need to bridge these MS and IBM technologies , Whats it best way, is there a standard pattern in this or something?
5. Most importantly do we need to a TP monitoring software in this scneario.
6. One solution is using WBI adapters to talk to COM application at front and back. Is this a good idea?
Thanks
_________________
Thimk |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Tue Aug 04, 2009 11:56 pm Post subject: Re: Help with Transaction with different technologies |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
My quick thoughts....
| Monk wrote: |
2. Can MB participate in a 2PC like MQ?.
|
Yes, its a property on the bar file to allow its work to be done under a distributed transaction. Do a quick search for more info on this.
| Quote: |
3. Is it best to have IBM technologies replace MS technologies completely
|
I like using one vendor for such applications because the support model becomes easier. However I dont have enough experience of COM to be able to comment. There are some limitations in the resources that can be enlisted into an XA transaction by the broker (and from memory I think SQL server is one such resource). Some MS bashing is sure to follow though.
| Quote: |
5. Most importantly do we need to a TP monitoring software in this scneario.
|
I wouldnt have said it was any more important here than usual. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Aug 05, 2009 12:57 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
WMB is not a resource manager. DB2 (or other database) and MQ are.
MQ can act as a transaction coordinator (XA). |
|
| Back to top |
|
|
| Monk |
| Posted: Wed Aug 05, 2009 2:34 am Post subject: |
|
|
Master
Joined: 21 Apr 2007
Posts: 282
|
| Quote: |
| WMB is not a resource manager |
True , MB does not store anything by itself..just process the messages..
but it can be a part of a 2PC..
so if some error or an exception occurs in the broker..there shud not be any commits to DB or MQ ..is this correct?
_________________
Thimk |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Aug 05, 2009 2:37 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Monk wrote: |
so if some error or an exception occurs in the broker..there shud not be any commits to DB or MQ ..is this correct? |
Correct (provided the transaction mode property is set to yes / automatic on your nodes and the flow throws the exception back to the input node!) |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Aug 05, 2009 2:41 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| WMB acts like an application program. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 05, 2009 3:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Nicely disguised multiple post (3 forums so far)... locking this one.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
