Hello, With WAS v6, a new JMS provider has been introduced to replace the MQ-based default JMS provider supplied with WAS v5. As a JMS provider, there are many MQ things that it cannot do (segmented messages, distribution lists, COA/COD messages, etc, etc). Also, message producers and consumers must be JMS (no C client support, etc). Interoperability with WMQ is supported, though, so you could implement a message bus in a WAS cell using the default JMS provider, and flow messages to/from an MQ queue manager network.
If your messaging requirements can be satisfied with a JMS-only provider, WAS Messaging might suit your needs. See the WebSphere v6 InfoCenter for more information about it - http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp. Search the InfoCenter for "service integration". Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -------------------------------------- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] [EMAIL PROTECTED]@LISTSERV.MEDUNIWIEN.AC.AT> on 03/17/2005 03:43:19 PM Please respond to MQSeries List <[email protected]> Sent by: MQSeries List <[email protected]> To: [email protected] cc: Subject: WAS 6 question I am just starting a project that is scheduled to use WAS 6 on AIX. A couple of individuals have commented that "this seems like a good way to replace MQSeries" which caught my attention. Can someone help me understand/breakdown WAS 6 vs. WebSphere MQSeries? Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
