Re: JDBC MQ Driver
Hi Mike, That brings back memories - I wrote a JDBC wrapper for MQ when I was trying out the first versions of XA support for MQJMS :) In general there should be no need to do that now, the provided integration of MQJMS with WebSphere should provide adequate pooling. Cheers, James. Mike Hamner wrote: >We have a contractor who is proposing use of an MQ JDBC driver that >works like a DB2 JDBC driver with Connection, Statement and Resultset >objects. It will be implemented as an MQ Datasource under the Websphere >application server. The primary intent of this approach is to avoid >writing pooling functions that JDBC already provides. Does anyone have >experience/comments concerning this proposed architecture that they >would be willing to share. > >Thanks, > >Mike Hamner >MQ Admin >BCBSGA > >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 > > > 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
Re: JDBC MQ Driver
Mike I suspect that you are referring to the Java Connector Architecture (JCA) implementation for MQ - if so and you have WAS 5 then I would agree with your contractor I am currently confused about what is available to connect WAS to MQ There are certainly the following 1. MA88 implementation of JMS/MQ - folded into MQ5.3 - J2EE developers like this 2. MA88 implementation of Java MQ - MQ developers like this 3. Enterprise Access Builder for Transactions (EAB) for MQ - precursor to JCA generates MQ access codes I think with WSAD 4. WAS 5 supports J2EE 1.3 and EJB 2.0 including message driven beans 5. JCA for MQ - this is the implementation that I am least sure of - it became available with WAS 4.03 ? but never seemed to get to a production release. For WAS 5 I cannot find any definite documentation that it is available - there is certainly a third party product that supports it. JCA for MQ would certainly appear to be the preferred future direction - high volume, standard architecture, connection pooling, transaction support etc. Connection pooling and transaction support (JTA) are available under certain circumstances in MA88 Perhaps James Kingdon could clarify Brian S. Crabtree EAI Consultant - Original Message - From: "Mike Hamner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 05, 2003 5:01 PM Subject: JDBC MQ Driver > We have a contractor who is proposing use of an MQ JDBC driver that > works like a DB2 JDBC driver with Connection, Statement and Resultset > objects. It will be implemented as an MQ Datasource under the Websphere > application server. The primary intent of this approach is to avoid > writing pooling functions that JDBC already provides. Does anyone have > experience/comments concerning this proposed architecture that they > would be willing to share. > > Thanks, > > Mike Hamner > MQ Admin > BCBSGA > > 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 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
Re: JDBC MQ Driver
Hello Mike, I have never heard about such a driver, so I cannot comment on that. You might have already known that, but just in case you haven't: the recent versions of MQSeries classes for Java offers quite a bit of connection pooling functionality "out of box" (see the documentation for MQSimpleConnectionManager methods and related in com.ibm.mq package). Pavel Mike Hamner <[EMAIL PROTECTED]To: [EMAIL PROTECTED] OM> cc: Sent by: MQSeries Subject: JDBC MQ Driver List 02/05/2003 05:01 PM Please respond to MQSeries List We have a contractor who is proposing use of an MQ JDBC driver that works like a DB2 JDBC driver with Connection, Statement and Resultset objects. It will be implemented as an MQ Datasource under the Websphere application server. The primary intent of this approach is to avoid writing pooling functions that JDBC already provides. Does anyone have experience/comments concerning this proposed architecture that they would be willing to share. Thanks, Mike Hamner MQ Admin BCBSGA 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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
JDBC MQ Driver
We have a contractor who is proposing use of an MQ JDBC driver that works like a DB2 JDBC driver with Connection, Statement and Resultset objects. It will be implemented as an MQ Datasource under the Websphere application server. The primary intent of this approach is to avoid writing pooling functions that JDBC already provides. Does anyone have experience/comments concerning this proposed architecture that they would be willing to share. Thanks, Mike Hamner MQ Admin BCBSGA 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
