David Currie

Thanks once again to Paul Titheridge, this time for pointing me to this technote covering the use of the WebSphere MQ Java APIs in a J2EE/JEE environment. It seems that IBM does now support the use of the WebSphere MQ Java interfaces in a WebSphere Application Server environment (check the supported software for your release) but this technote provides you with lots of reasons why you shouldn’t! The Java interfaces do have functionality that isn’t currently available in the JMS API (for example message segmentation and important parts of message grouping) but that needs to be weighed carefully against the drawbacks. JMS should always be the default option unless you have a very good reason not to use it.

This entry was posted on Wednesday, January 2nd, 2008 at 10:40 pm and is filed under WebSphere Application Server, WebSphere MQ. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.