| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Embedded Messaging Client?? |
« View previous topic :: View next topic » |
| Author |
Message
|
| tbp3272 |
 Posted: Tue May 31, 2005 9:38 am Post subject: Embedded Messaging Client?? |
 |
|
Newbie
Joined: 21 Jun 2002
Posts: 8
|
I have an application running on a WebSphere App Server on Windows 2000. The app has a requirement for XA transactions between a MQ SQL Server database and a WMQ Queue Manager. The WAS, SQL Server database and WMQ Queue Manager each reside on separate servers. Do I have to use the WMQ Extended Transactional Client to support this XA requirement, or can I use the embedded messaging client that is provided with WAS.
http://www-106.ibm.com/developerworks/websphere/library/techarticles/0310_barcia/barcia.html
Thanks! |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 31, 2005 9:40 am Post subject: Re: Embedded Messaging Client?? |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| tbp3272 wrote: |
| Do I have to use the WMQ Extended Transactional Client to support this XA requirement |
Yes.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 31, 2005 12:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Jeff,
How does that work when you have WAS network deployment and the qmgr defined at cell level.
Do you still need to have an MQServer deployed on all the servers in the cell? Or can you do a 2 phase commit with any other WAS server as long as it is in the same cell ??
I read somewhere (possibly WAS redbook ?) that within the same cell the WAS embedded client could be used as a transactional client towards a 2 phase commit for any other resource within the same cell. This statement has me somewhat confused.
Thanks
 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 31, 2005 1:03 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The first thing to remember is that, (at least as far as I know), you can never get a reference to the Embedded Client when you look up a resource from the WebSphere MQ JMS Provider - regardless of what context that reference is defined at.
Secondly, all WebSphere MQ QCFs are resolved at the lookup context. So if you have a QCF defined in the cell level that is pointing to a qmgr on Machine B, and you look that reference up on Machine A - you won't be able to create a bindings reference (that I know of).
So, yes, it makes sense that an Embedded Client reference could be defined at the cell level and used in a two-phase commit anywhere - because it is talking to the JMSServer on some machine, possibly the dmgr? - and that does not need the same native in-memory bindings to do two-phase commit that MQ needs. It's a native Java XA implementation, not a JNI-enabled interface.
This is mostly extrapolation, so don't take it as gospel without testing it yourself.
I'm *not* an expert at this stuff.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
