WebSphere MQ v7.5 announced
Ronaldo Aguiar 0600028WAX firstname.lastname@example.org | | Tags:  websphere announcement mq ibmimpact wmq
1 Comments | 3,412 Visits
Contributed by T.Rob. Follow him @tdotrob
WebSphere MQ v7.5 was announced on April 24th, for GA in June. You can expect to hear more about it at IMPACT but here's a quick preview:
Products integrated into WebSphere MQ base are:
FTE, AMS and Telemetry remain chargeable components but the tight integration with WebSphere MQ allows a single install and a level of internal interop not previously possible. This also means that application of a future fix pack will update all installed components and no worrying about whether your FTE or AMS will work with an update of MQ.
Another exciting development is the "split cluster XMitQ." Sometimes it is helpful to provide isolation between applications competing for MQ resources - i.e. the Mice & Elephants problem. This can be achieved with overlapping clusters, dedicated queue managers, dedicated P2P channels, etc. Each option provides a different level of isolation. Prior to v7.5, there has been no option for separate XMitQ queues for overlapping clusters. If one cluster became backed up and filled the XMitQ, all clusters were impacted. With WMQ v7.5, split cluster XMitQs will open up new options for tuning within a single queue manager where each cluster can have a dedicated transmit queue.
Obviously, the IBM team behind these enhancements are excited and looking forward to telling you all about them next week at IMPACT. In the meantime, please go read the announcement linked above and mark your calendar for the WebSphere MQ sessions!