| Author |
Message
|
| HubertKleinmanns |
 Posted: Fri Feb 06, 2009 7:36 am Post subject: XA transactions with WMQ clients, WAS and UDB |
 |
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Hello everybody,
I have the following situation:
Environment with WebSphere application server (WAS) as the transaction manager, MQ clients and UDB as ressource coordinator. I would expect, that I have to use the transactional client to have a XA transaction with MQ. But I heard from a guy, who heard this from IBM, that he only needs the normal MQ client.
My questions:
1. Is it correct, that the normal MQ client is able to take part at XA transactions together with WAS?
2. If yes, how does this work, because normal MQ clients only do single phase commits, but no two phase commits?
3. Wherefor do I need the transactional client?
I am awaiting an interesting discussion  .
_________________
Regards
Hubert |
|
| Back to top |
|
 |
| zpat |
| Posted: Fri Feb 06, 2009 7:42 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
| You need the ETC to take part in external units of work with MQ client using XA. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 06, 2009 7:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| markt |
| Posted: Fri Feb 06, 2009 7:50 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 504
|
From the V7 announcement letter:
| Quote: |
Extended Transactional Client
In addition to the MQ clients, WebSphere MQ delivers an extended transactional client for each client platform. If you choose to use an extended transactional client, you must purchase a WebSphere MQ license for the machine on which you are running the client. The only exception is if the transaction manager you are using is provided by WebSphere Application Server, WebSphere ESB, or WebSphere Process Server, which include extended transactional client capability.
|
|
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 06, 2009 8:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
But you still can't use the standard MQ client to do this.
The way I read that statement is that if you have WAS, ESB or WPS on the same platform as your application, it includes the ETC function. |
|
| Back to top |
|
|
| markt |
| Posted: Fri Feb 06, 2009 8:54 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 504
|
| I don't understand your comment. Clearly the app server has to be on the same machine as where the client connection is made from. WAS ships with a copy of the MQ Java/JMS client. It's the same MQ code. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Mon Feb 09, 2009 2:06 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| markt wrote: |
From the V7 announcement letter:
| Quote: |
Extended Transactional Client
In addition to the MQ clients, WebSphere MQ delivers an extended transactional client for each client platform. If you choose to use an extended transactional client, you must purchase a WebSphere MQ license for the machine on which you are running the client. The only exception is if the transaction manager you are using is provided by WebSphere Application Server, WebSphere ESB, or WebSphere Process Server, which include extended transactional client capability.
|
|
I read it this way: WAS uses its own ETC MQ client libraries without the need of extra costs - and without telling the MQ admins?
Do I need any MQ installation on the WAS server machine?
_________________
Regards
Hubert |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 09, 2009 1:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| HubertKleinmanns wrote: |
I read it this way: WAS uses its own ETC MQ client libraries without the need of extra costs - and without telling the MQ admins?
Do I need any MQ installation on the WAS server machine? |
From WAS 6.x on, WAS comes with its own libraries for MQ preinstalled.
No need to install a java client library any more....
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
