| Author |
Message
|
| Mut1ey |
 Posted: Fri Oct 07, 2005 6:15 am Post subject: MQ Server vs Extended Transactional Client |
 |
|
Acolyte
Joined: 07 Oct 2005
Posts: 74
Location: England
|
Hi
We have a set-up here that involves WAS 5 systems and a central, HA, remote qmgr, @ v5.3, csd 7. The client want to only use XA client connections, via JMS, from the WAS machines to the central MQServer as they want the transactions to fail if messages cannot reach the MQServer for whatever reason. In which case, after rolling back DB records, a different WAS instance will pick up the work. These are effectively real-time transactions.
They have the MQserver and MQclient/ MQJava components installed and being used by differnt applications locally too, but they don't need or want a local qmgr for for this particular application.
My questions are:
1) Is the ETC simply a sub-set of MQServer functions/code?
2) Does the ETC need to be installed on the WAS machine, on top of MQServer...........
2.1) If we want the Transaction Manager to be WAS?
2.2) If we want the Transaction Manager to be Oracle?
Any help greatly appreciated.
Neil |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Oct 07, 2005 9:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You can use the ETC with a client connection to give you the same multi phase commit capability as with an MQServer.
Cost is about the same...
However your sceanario is not correct. There is no guarantee that a different WAS would pick up the message from the DB.
In any case the current WAS should then try to connect to a different Server.
If you are still in dev stages I suggest you have a hard look at WAS 6.0.
It will change your paradigm and architecture.
Enjoy  |
|
| Back to top |
|
|
| Mut1ey |
| Posted: Mon Oct 10, 2005 1:08 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005
Posts: 74
Location: England
|
Thanks, fjb_saper, but that doesn't really answer my question(s).  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 10, 2005 3:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to install the ETC on any machine that you want to use a transactional client on.
It doesn't need to be installed on top of an MQServer installation - in fact, that might be kind of redundant license wise.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Mut1ey |
| Posted: Mon Oct 10, 2005 5:03 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005
Posts: 74
Location: England
|
| Thanks, Jeff. That is getting to the crux of my question. I guess I haven't explained it very well. We already have the Server installed in the WAS machine. Can I perform the same client/XA functions with JUST the Server installed as with the client + ETC installed? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 10, 2005 5:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Mut1ey wrote: |
| Can I perform the same client/XA functions with JUST the Server installed as with the client + ETC installed? |
No.
But you don't need to.
Perform XA to the local qmgr, and configure your MQ Network to move the messages to the qm you want to client-connect to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Mut1ey |
| Posted: Mon Oct 10, 2005 6:40 am Post subject: |
|
|
Acolyte
Joined: 07 Oct 2005
Posts: 74
Location: England
|
The user categorically do not want to use the MQServer. These are hard, real-time messages that they want to go to the MQServer synchronously and that means client. They cannot afford for messages to be sat on queues, irrespective of that fact the delivery is assured.
In WAS their Provider will be MQ with a Transport type of client and XA selected. Now, it may be that, under-the-covers, WAS connects to a Qmgr and uses a client conn to get to the target qmgr. However, there is no mention of a local QMGR in WAS, just the target QMGR. |
|
| Back to top |
|
|
|
|
