| Author |
Message
|
| PlatinumBay |
 Posted: Mon Nov 24, 2003 8:57 am Post subject: .NET Two-Phase Commit |
 |
|
Newbie
Joined: 22 Nov 2003
Posts: 4
Location: Philadelphia, PA
|
I am building a .NET COM+ application which needs to do two-phase commit between MS SQL 2000 and MQSeries (currently 5.3 CSD04 on production). I have the 5.3 CSD05 client installed on my dev box, and I have the SQL code worked out. Any thoughts on implementing the MQ Series 2-phase commit in .NET? Are the 5.3 CSD05 drivers XA-Compliant?
Thanks 
_________________
got dotNet? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Nov 24, 2003 9:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You cannot do Two-Phase commit with a normal client, regardless of what platform.
You can only do XA transactions with either a server application or with the Extended Transactional Client (which is not free).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PlatinumBay |
| Posted: Mon Nov 24, 2003 10:01 am Post subject: |
|
|
Newbie
Joined: 22 Nov 2003
Posts: 4
Location: Philadelphia, PA
|
Thank you. A straightforward reply is a breath of fresh air, and just the answer I needed.
We are looking into the Extended Transactional Client.
| JeffLowrey wrote: |
| ...You can only do XA transactions with either a server application or with the Extended Transactional Client (which is not free). |
To clarify, how are you defining a Server Application? Are you referring to the MQ Server product, or a custom application?
_________________
got dotNet? |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Nov 24, 2003 12:03 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| A server application is one that has to run on the same machine as the queue manager and connects in 'bindings' mode rather than client mode. |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Nov 24, 2003 12:14 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Note the 5.3 extended transactional client still does not support mts/com+ transactions |
|
| Back to top |
|
|
| PlatinumBay |
| Posted: Mon Nov 24, 2003 7:18 pm Post subject: |
|
|
Newbie
Joined: 22 Nov 2003
Posts: 4
Location: Philadelphia, PA
|
 We are willing to build a custom application, though our production MQ is on an AIX box. I am not an MQ guru, I am more in the Microsoft Programming camp, but diverse-systems compatibility is everyones game, and to everyones benefit.
Here is the basic project synapsis:
I need to pull from MQ Queues, run checks in the middle, and deposit in SQL 2000 for our web app, using two-phase commit. It is the MQ part that I am having difficulties architecting.
So for the million dollar question (monopoly money  )
What options are available to perform XA-Compliant transactions with MQ Series from VB.NET?
_________________
got dotNet? |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Nov 25, 2003 2:47 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Since SQL isnt listed as one of our supported databases on
http://www-3.ibm.com/software/integration/mqfamily/platforms/supported/wsmq_for_winnt2000_5_3.html
you cant use strict XA (database) support, but you mention that an SQL server can be involved in a DTC transaction in COM+/MTS? (I dont know this, never used SQL server). If so, since you can only do COM+ DTC coordination if you are coordinating to an MQ server, I suspect you need a server installed on the Windows machine and work out a way of routing messages appropriately.
Sorry its not much help. |
|
| Back to top |
|
|
|
|
