Art, >>>If I want to perform 2-phase commit (2PC) transactions and have WAS V5 act >>>as the transaction coordinator between the Oracle database resource and the >>>WMQ message queue resource, will the 'XA-capable' client distributed w/ WAS >>>V5 be sufficient, or do I need to install the WMQ Extended Transactional >>>Client (ETC) product offering??? (Note that the WMQ server is NOT co-located >>>w/ WAS). We've gotten mixed messages from IBM on this and I'd like to hear >>>from IBM and/or others w/ experience with this type of configuration. The >>>ETC costs as much as a WMQ server, while the WAS V5 client is bundled >>>w/ the base product (essentially, it's the old MA88 support pac).
The WAS 5.0 Embedded Messaging client can be used to make transactional connections to either the Embedded Messaging provider or to the WMQ Provider. Note that this is only true for applications using JMS, and that are operating within the WAS environment; remote transactional connections from applications outside the WAS environment or using an API other than JMS do require the use of the ETC. This might explain why you've received "mixed messages" (no pun intended). The ETC does not have these limitations. Hope this helps. Regards, Christopher Frank Sr. I/T Specialist - IBM Software Group IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -------------------------------------------- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
