6. Conclusion
Our aim has been to show that computer systems need an application message handling system that is independent of transactional monitors and communication access methods. Some software vendors prefer to extend the functions of their DBMS or transactional monitor by adding message handling functions, to the detriment of the openness of their system. This separation of roles does not, however, prevent message handlers from being used under the control of transactional monitors; combining the two types of handler improves their use in terms of message integrity and system performance control.
The foreseeable evolution of the MQSeries family of products will focus in particular on :
on improving performance;
support for other operating systems ;
the availability...
The Ultimate Scientific and Technical Reference
This article is included in
Software technologies and System architectures
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Conclusion
References
IBM brochures
SC33-0850 Message Queue Interface - Technical Reference
SC33-0807 MQSeries : Application Programming Guide
GC33-1349 MQSeries : Planning Guide
SC33-0806 MQSeries : MVS/ESA System Management Guide
SC33-1373 MQSeries : AIX Version 2 System Management Guide
Message manager editors
DEC MessageQ marketed by BEA
Tuxedo/Q marketed by BEA
Falcon from Microsoft
AXIME CM2
COVIA
Topend RTQ from NCR
Pipes from PeerLogic
TIB from TIBCO
VCOM from Verimation
The Ultimate Scientific and Technical Reference
