| Author |
Message
|
| gprasad |
 Posted: Wed May 20, 2009 7:50 am Post subject: com.ibm.mqetclient.jar |
 |
|
Newbie
Joined: 14 May 2009
Posts: 6
|
Hi,
Can anyone point me to where i can get com.ibm.mqetclient.jar.I have MQ6 with a fix pack 6.0.2.But i am not able to find this jar in /java/bin.
Thanks |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed May 20, 2009 8:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 20, 2009 8:11 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| gprasad |
| Posted: Wed May 20, 2009 8:25 am Post subject: |
|
|
Newbie
Joined: 14 May 2009
Posts: 6
|
Hi,
I am running MQ 6 on windows and i don't find it anywhere.I guess from the IBM notes states that "We do not need for windows".But the IBM also stated that jar comes with MQ6 which i can't find for windows.
Hope i was more elaborate. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 20, 2009 8:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Quote: |
Resolving the problem
WebSphere MQ 6.0, includes the file, however you must install the "Java Extended Transaction Support". |
  |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 28, 2010 6:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Does this jar file come with WAS 6.1? As this version of WAS is meant to include the extended transactional client function.
I want to use it on a server with WAS 6.1 installed (but not a MQ installation).
Is it part of the builtin MQ client that ships with WAS 6.1? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 28, 2010 6:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| WAS doesn't require the ETC. WAS acts as the transaction manager. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 28, 2010 10:18 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
How does WAS coordinate MQ and database transactions, when using MQ client connections to MQ (not a queue manager on the WAS box).
Are you saying that the builtin MQ client in WAS is a standard client and not a ET client?
How can a standard MQ client participate in a XA unit of work?
http://www-01.ibm.com/support/docview.wss?uid=swg21248089
The above URL page is somewhat confusing. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 28, 2010 10:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You'll need to open a PMR against the WebSphere MQ Resource Adapter to get any reliable details on this.
This is a WebSphere MQ component. What that page is telling you is, with each specific version of WAS, which specific level of the WebSphere MQ product the Resource Adapter component is bundled from. So if you see an APAR for MQ 7.0.0.2 against the resource adapter that is fixed in 7.0.1.0, you can use that page to figure out that you need to be at WAS 7.0.0.5 to get the MQ 7.0.1.0 Resource Adapter (and thus the fix). |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Sep 28, 2010 10:57 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's this statement that I am not sure about
| Quote: |
WebSphere Application Server Version 6 (all releases) also provides the ability for JMS applications to participate in XA-transactions that use multiple transactional resources (e.g. databases as well as JMS destinations) in a single transaction without the need to install the WebSphere MQ Extended Transactional Client.
|
So we have a JMS application within WAS using MQ client to connect to MQ on another host. Can this be XA or not? If so where is the mqetclient.jar file!
What confuses me is the mention of the ET client, implying that client mode is supported with XA. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 28, 2010 11:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In "normal" XA, using bindings mode, the queue manager acts in two roles: - the XA transaction manager
- A resource manager
This can be done because the application using the database is on the same machine, and the state of the transaction with the DB can be reliably monitored.
When using ETC, the ETC engine itself acts as the transaction monitor, leaving the queue manager to only be a resource manager.
When using WAS, the WAS engine acts as the transaction monitor. |
|
| Back to top |
|
|
|
|
