| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WebSphere MQ (MQSeries) Product History |
« View previous topic :: View next topic » |
| Author |
Message
|
| Michael Dag |
 Posted: Wed Oct 08, 2008 2:27 am Post subject: WebSphere MQ (MQSeries) Product History |
 |
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
For history purposes and future references, please add if you have any other relevant details... 
| Gary Ward on MQSeries ListServ once wrote: |
Gary Ward
Sent: Wednesday, June 11, 2003 4:28 PM
Subject: MQ software evolution - fill in the gaps?
I'm pretty sure this is the order... I've been working with MQ since
the beta in 1992. I kept the listing focused on the "big"
platforms...
MQM MVS/ESA V1.1 GA (MVS)- December 31, 1993
ezBridge Transact for MQSeries - March, Sept, Nov, Dec 1993
(different platforms)
MQM/400 V2.3 - Feb/April 1994
MQSeries for MVS 1.1.2 - June 1994
ezBridge Transact for MQSeries 3.0 - July 1994
MQM/400 V3 - 4Q 1994
MQSeries 2.0 (OS/2, AIX) - Feb 1995 (the beginning of the end of
ezBridge)
MQSeries for MVS 1.1.3 - May 1995
MQSeries 2.2 (HP, SCO) - 4Q 1995
MQSeries 2.0 Windows NT - 2Q 1996
MQSeries 2.2 (Sun OS/Solaris, DC/OSx) - June, July 1996
MQSeries for MVS 1.1.4, - June 1996
MQSeries for MVS/ESA 1.2 - August 1997
MQSeries 5.0 - October 1997 (on my birthday no less!)
MQSeries for AS/400 V4.2 - Feb 1998
MQSeries 5.1 - April (NT), June 1999
MQSeries for OS/390 V2.1 - Feb 1999
MQSeries for AS/400 V5.1 - July/Aug 2000
MQSeries for OS/390 V5.2 - Nov 2000
MQSeries 5.2 (Distributed) - Dec 2000
WebSphere MQ 5.3 (Distributed, iSeries) - June, July, Oct, Nov 2002
WebSphere MQ 5.3 z/OS - June 2002
MQSI and Workflow also made their debut in 1998 (Flowmark was
discontinued in 1999). MQSI V2 came out 2000.... WHEW someone can
finish MQSI and MQWF if they wish...
Any former employees of SSI can argue the ezBridges dates... but I
think they're accurate.
For those techies who attend the SHARE technical conference, we will
be having MQ's 10th birthday party at the February 2004 meeting!
Original link: https://listserv.meduniwien.ac.at/cgi-bin/wa?A2=ind0306&L=MQSER-L&P=R45476&D=0
|
| Dermot Flaherty, Senior Technical Staff Member and Lead Architect, IBM WebSphere MQ product and technologies wrote: |
WebSphere MQ – A short history of the past 15 years
In December 1993, the Hursley Development Laboratories released a product called Message Queue Manager for MVS/ESA which joined a small family of existing products all of which were part of the new IBM MQSeries family.
Today MQSeries is known as WebSphere MQ - or more familiarly as "MQ" and is the industry-leading provider of message-oriented middleware.
It is a key component in IBM's SOA strategy providing the universal messaging backbone across almost 80 different platform configurations, a wide range of programming languages and interfaces and is used by more than 10,000 customers across numerous industries. In 2004 it became the first Software-only product to win the prestigious MacRobert Award from the Royal Academy of Engineering.
The WebSphere MQ story is a wonderful example of collaboration between IBM Research, Development and Industry specialists as well as our customers to shape a product and a technology to achieve major success in the marketplace and this article will trace its beginnings and its evolution into not only a world-class cross-platform product but one which also exploits individual platform features to customer benefit.
There have been many significant contributors to the success of MQ and to mention them all would be extremely difficult (and run the risk of inadvertently forgetting someone) but since the focus of this article is the history of the development of MQ then I hope I may be forgiven for only mentioning three names herein – those of Rob Drew, Dick Dievendorff and C. Mohan – who were instrumental in ensuring that the very first MQ product started off with the right technical structure, thus establishing sound principles upon which subsequent releases were built. There are many more contributors in the technical design, development and business opportunity contact admin and as I have stated above, the history of MQ shows IBM and IBM-customer collaboration at its best.
In the latter half of the 1980s there was a growing realization within IBM that there was a need – especially in the Finance Industry - for what we now call Message Oriented Middleware (MOM) and unlike our competitors, IBM had no solution in this area. Accordingly a Message/Queueing/Transaction Routing Task Force was assembled to examine the problem and recommend solutions.
Note that at this time the focus here was very firmly on the MVS platform and the need for message queueing facilities between subsystems such as CICS, IMS and Batch.
At the same time there were a number of Industry pressures that led to the creation of the Systems Application Architecture (SAA) initiative with its aim to create Cross-platform Common Programming Interfaces (CPIs) to facilitate the easier deployment of applications across IBM platforms.
The result of these two initiatives was the inclusion in the late 1980s of a specific programming interface – CPI-M – within the SAA blueprint to provide the semantics for inter-process message queueing. Not only did this define an API for messaging that would instantly be recognized today by anyone familiar with MQ, but the important concepts of Message Driven Processing in a transactional context were also recognized and documented.
Having established the industry requirement and the place of transactional message queueing in the SAA blueprint, the next step was to build it and it happened that there were two U.S. assignees to CICS at that time both of whom had particularly relevant history in this area.
Rob Drew and Dick Dievendorff had worked together in the early 1980s on a number of Advanced Technology projects in the U.S. and one of the results was a prototype Queue Manager on MVS.
Another outcome was a set of infrastructure facilities – Data Systems Control Facility (DSCF) – which was extracted from the then single DB2 address space (ADMF) to form the basis of what is now the System Services Address Space in DB2 which make it a lot easier to write a "server" program on MVS and provided the perfect base to build a robust Queue Manager on MVS.
(IBM has a number of candidates for the title of "One of the Crown Jewels" and DSCF is certainly one of them).
So when the requirement to build a Queue manager accessible from CICS came to Hursley, because of the background of both Rob and Dick in the message queueing area and Dick’s particular knowledge of the DSCF code base and his previous prototype work, we had two people in the right place at the right time who knew how to build it.
So in 1990 a development team was formed to build what would be the first release of MQ on MVS and its start point was once again the DSCF infrastructure code from DB2.
With the help of the Santa Teresa Lab and the DB2 product team, approximately 100Kloc of DSCF code was ported from DB2 V2.3 to provide a hugely significant kick-start to the MVS Queue Manager Development effort.
Not only did this provide a robust base for the Queue Manager on MVS but the fact that we shared this componentry with DB2 increased the confidence in the overall robustness and integrity of the solution.
Having had great help from the DB2 Development with the DSCF code, IBM Research in Almaden and in particular C. Mohan then helped with the recovery aspects of the design and the result was an implementation of his Algorithms for Recovery and Isolation Exploiting Semantics (ARIES) which gave us an extremely robust and predictable logging and recovery methodology for persistent messages. These principles were extended to provide a novel way of implementing in-storage transactional semantics for non-persistent messages where the message data itself was allowed to age from the buffer pools to DASD but the log was in virtual storage.
While the new team in Hursley was developing the first Queue Manager on MVS, there were other developments important to the shaping of MQ.
The CPI-M proposed as part of the SAA blueprint was being refined into what would become the MQ API and at the same time it was realized that a cross-platform reliable messaging facility really needed to run on ALL customer platforms and not just those platforms supplied by IBM. (CICS had first explored this notion when their product management was looking at providing CICS on UNIX – not just AIX).
It was clear that it would take some time for IBM to produce its own version of MQ suitable for the wide range of Distributed platforms (with their different operating systems, communication protocols, etc.) and while a team was being formed in Hursley which would develop MQ on Distributed platforms, a partner was sought such that MQ could have a significant cross-platform presence from the start.
System Strategies Inc. had a product called ezBridge Transact which provided message queuing facilities across a number of platforms – both IBM and non-IBM – and the result was a partnership with them whereby ezBridge Transact would provide support for the MQ API while IBM was developing its own version.
All the pieces were now in place and accordingly in 1992 IBM announced MQSeries as a cross-platform messaging API as part of the SAA blueprint. In September 1993, MQSeries V1 became available on VSE/ESA, Digital VAX/VMS and AIX/6000 followed in December by DOS, OS/2, Windows, OS/400, System/88, and Tandem.
The above support was provided by the ezBridge Transact product and also in December they were joined by Message Queue Manager for MVS/ESA V1.1.1 – the first true MQ product.
Over the next few years, the Hursley team gradually introduced its own versions of MQ on Distributed and the first of these appeared in 1994 on the AS/400 platform.
Over the next few years, the Hursley MQ products gradually replaced the ezBridge products and as the product rapidly gained in customer acceptance (and naturally new requirements) enhancements were made that attempted to satisfy the twin goals of cross-platform functional consistency as well as specific platform exploitation where required.
Two good examples of the above are MQ Clustering technology – a very powerful and widelt-used cross-platform facility for reduced administration and workload balancing (introduced in 1999) and Sysplex Shared Queues – a features exploiting unique capability on the z/OS platform (introduced in various stages from 2000).
So as we reach the present day with MQ continuing to grow in both total number of customers and the depth of customer exploitation of MQ, what are the next challenges and opportunities?
The growing importance of Service Oriented Architecture (SOA) and the growth of Web Services and other connectivity mechanisms are clearly important developments. It is interesting and heartening that because of the loosely-coupled nature of the message queueing model, a large number of existing MQ customers feel that they are already adopting SOA principles and the recently released MQ Service definition supportpac – MA93 – allows MQ applications to be catalogued as Software assets which can then be reused and composed as Web Services.
Also with the considerable interest in the recently released HTTP-MQ bridge supportpac - MA0Y - which extends the reach of MQ into the Web 2.0 world, a new set of customers are becoming aware of what MQ can provide as a Universal Messaging Backbone capable of accessing and delivering business data with a range of Qualities of Service both inside and outside of their enterprises.
MA0Y functionality is included in the recently announced WebSphere MQ V7.0 which contains a major set of enhancements to our JMS support including a completely integrated Publish/Subscribe capability (accessible from the MQ API as well as JMS) which will be a key component in customer adoption of event-driven SOA.
In addition the growing importance of IBM’s Enterprise Service Bus (ESB) products presents new opportunities for MQ and while the proposition that MQ and ESB can access business data from any place, transform it into any format and route it to any where might sound like a nice piece of marketing jargon it is nonetheless backed up by real products and function!
And while the above movement to a more Service Oriented business occurs – at rates that vary from customer to customer - it is also clear that customers are demanding ever higher availability for their business and the IT systems that support the business.
Over the past 15 years MQ has shown considerable vitality as fresh business and technological challenges emerged and provided we continue to work across IBM and with our customers such that we not only provide the required Cross-platform functionality but also exploitation of the particular strengths of the individual computing platforms there is no reason we cannot look forward to another 15 years of success with MQ.
Original link: http://www-01.ibm.com/software/integration/wmq/MQ15Anniversary.html
|
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
 |
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
