| Author |
Message
|
| RatherBeGolfing |
 Posted: Wed Mar 17, 2004 12:32 pm Post subject: MSDTC + MQClient = Unit of Work ??? |
 |
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
I have an application group who wants to write a COM+ application, which will run on a Windows 2000 server, with MQClient (V5.3). They want to GET a message from a queue and insert some data into a SQL database.
If the database portion of work fails, they want to roll the message back into the queue.
We have a similar app running on a box with MQServer and the COM object is able to enlist the MQ portion of work into the "transaction" which includes both the MQ Get and the SQL Insert.
My question is: Can we do the same thing with MQClient?
The manuals I've looked at talk about not being able to use MQClient as the transaction coordinator for nonMQ activities, but they don't address the issue of including MQClient as a participant in a transaction coordinated by a COM+ object running under MSDTC (Microsoft Distributed Transaction Coordinator - runs as part of W2K SP4).
Any and all advice appreciated!
_________________
Cheers,
Larry
MQ Certifiable |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Mar 17, 2004 1:02 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Mar 18, 2004 1:50 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
You still cannot use an MQ (Transactional or not!) Client in an MSDTC transaction yet. From the memo.ptf
| Quote: |
2. Microsoft Transaction Server and IBM WebSphere MQ Extended
Transactional Client
Unfortunately at this point in time, there are some unresolved
issues using Microsoft Transaction Server as the transaction
manager to coordinate the IBM WebSphere MQ Extended Transactional
Client, therefore this configuration is not supported at present.
For more details and any updates to the supported position, please
see APAR number II13466.
Note that when this configuration is supported, the queue manager
name you use in MQCONN or MQCONNX cannot be blank or a single
asterisk (*), nor can the name start with an asterisk.
|
|
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Thu Mar 18, 2004 7:05 am Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
So Jason, the bottom line is, if my developers want to enlist MQ into their MSDTC controlled transaction, they must use MQServer. There is not any flavor or version of Client that will accomplish this. Correct?
_________________
Cheers,
Larry
MQ Certifiable |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Mar 18, 2004 8:32 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Thats my understanding as it stands today... Dont quote me though  |
|
| Back to top |
|
|
| J0 |
| Posted: Wed May 19, 2004 8:50 am Post subject: |
|
|
Newbie
Joined: 19 May 2004
Posts: 3
|
| I don't suppose there have been any changes with the Extended Transactional Client which has resolved these issues ?? |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed May 19, 2004 11:20 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
no  |
|
| Back to top |
|
|
|
|
