Originally posted by Krishna Raj:
Kyle, WASQ is WAS queue as you found out. The product may have shared code base in the past but are completely different (This is apparant what you put on WAS is not visible from WMQ !) There has to be some sort of a config to link messages put into WAS queus to be visible in MQ and vise versa. WAS queus are more than stripped down versions of MQ. They actually are designed to work within J2EE and hence have lot of context info available from within WAS as against MQ that has to follow a JNI route. making it more complex.
Krishna, the embedded messaging in WAS is a stripped down version of MQ 5.3 and MQ Event Broker. Trust me on this one. All that we did is to remove many of the management pieces of MQ and forbid clustering. It's not "a shared code base in the past". It's a shared code base NOW. The development that we did to make the messaging work within the J2EE environment has been placed in the base MQ 5.3 product as well -- which is why you can use either.
MQ has for several versions supported two options on clients -- a "bound" version that uses JNI and a "thin" version that uses TCP/IP. What we did in WAS 5.0 is to make the "thin" version capable of working with XA -- which has been moved into MQ 5.3 also.
Yes, there is configuration required to let a "regular" MQ queue see information placed in a queue in embedded messaging. But that is more due to the complexities of managing multiple MQ queue managers than anything...
I'll assure you that my sources are accurate -- this information comes from the developers in IBM Hursley labs...
Kyle
------------------------------------
Kyle Brown
Senior Technical Staff Member
IBM Software Services for WebSphere