By: founder_chen ( founder )
Message-Oriented Middleware [ reply ]
MIDDLEWARE DS HOME | ARCHIVES | ABOUT US | SUBSCRIBE | SEARCH | CART
About this area | Archives | Events | Education | Organizations | People | Projects | References | Resources | Miscellaneous
Last updated: 20-Sep-2002
Projects and organisations in Message-Oriented Middleware
WebSphere MQ (was MQSeries) holds a significant Message Oriented Middleware market share. MQSeries offers four interoperable APIs:
MQI. Full API to underlying messaging implementation.
JMS or Java Message Service. Java standard providing similar functions.
AMI or Application Messaging Interface. High-level abstraction to ease policy handling.
CMI or Common Messaging Interface. Simplifies the creation of message content.
Sun Java Message Service (JMS) Enterprise messaging provides a reliable, flexible service for the asynchronous exchange of critical business data and events throughout an enterprise. The JMS API adds to this a common API and provider framework that enables the development of portable, message based applications in the Java programming language.
iPlanet Message Queue for Java iPlanet Message Queue for Java is a software product designed to enable disparate applications across the enterprise to communicate and work together efficiently. A Message Oriented Middleware (MOM) product, iPlanet Message Queue for Java makes possible the integration of legacy, enterprise resource planning (ERP) and new applications both internal and external to the organization. Use of iPlanet Message Queue for Java frees developers from having to focus on networking details and allows them to concentrate on the business logic of their Java applications instead. As a result, organizations benefit from reduced cost of development and faster time to market.
MSMQ Microsoft Message Queue Server MSMQ offers comprehensive message queuing functionality such as reliable, resilient message delivery, cost-based message routing, and full support for transactions. MSMQ also offers seamless interoperability with the IBM MQSeries products through the Microsoft MSMQ-MQSeries Bridge and with other message queuing products through products from Level 8 Systems, Inc.
ObjectWeb (Open Source)
JORAM JORAM incorporates a 100% pure Java implementation of JMS (Java Message Service API released by Sun Microsystem, Inc.). It provides access to a MOM (Message Oriented Middleware), built on top of the Scalagent agents based distributed platform. JORAM is a free, open source initiative.
BEA Systems Inc
MessageQ A proven and widely deployed middleware solution for distributed enterprise applications, BEA MessageQ allows the reliable exchange of guaranteed application messages across heterogeneous platforms. BEA MessageQ provides a robust application integration architecture for building high-performance message-based applications using multi-mode communications.
Creative Science Systems
NetZyme Enterprise Features:
any Java (1.1.x, 2+, EJB, J2EE, J2ME)
any C (C/C++, COBOL, Ada, PalmOS C, Visual Basic)
Open Platform with Extensible API
Message-Oriented Middleware (MOM)
Object-Oriented Middleware (OOM) with messaging implementation
Mobile Access Middleware (MAM)
Serverlizer. RAD tool
Load Balancing / Fault Tolerance
RDBMS Connection Manager
Data Encapsulation Layer With C Counterpart
HTML / XML / XSL / XSD / WML Dynamic Generation
TIB/RV, MQSeries, and PalmOS S handlers
Bi-Directional CORBA 2.0
J2EE EJB Load-Balancing Container Server with JMS implementation
Support for TCP/IP, SMTP, UDP, COM/DOM, UDDI, LDAP, RMI, ROI, and SOAP
Real time system monitoring
Integrated Development Environment (IDE)
Graphic Management Console
Modular Web Application Server
TIBCO Software Inc
Rendezvous Rendezvous utilizes a distributed architecture to eliminate bottlenecks and single points of failure. Applications can select from several qualities of service including reliable, certified and transactional, as appropriate for each interaction. Messaging can be request/reply or publish/subscribe, synchronous or asynchronous, locally delivered or sent via WAN or the Internet. Rendezvous messages are self-describing and platform independent, with a user-extensible type system that provides support for data formats such as XML.
4 Tier software
OpenMOM features :
Transparent communication across operating systems and languages.
Dynamic definition of your correspondents.
Flexible approach : you move your application across systems with no interruption.
Ease of use : An application can send a message regardless of the receiver's availability or of a session's initialization.
Asynchronous messaging facility (no locked-up client).
Optional synchronous facility ( fast RPC mechanism)
Seamless communication between objects.
Performance : Parallel servers and services with dynamic load balancing.
Multiplexing of server and network communication requests.
Automatic message queuing facility for ad-hoc requests.
Fast transfer of important volumes of messages.
Small software footprint.
Stability : The server guarantees the delivery and integrity of messages ,independently of the system or network availability.
Openness : Supports the major network protocols and development languages.
Straightforward implementation : OpenMOM requires little training, programming and administration.
IBM Research - Advanced Enterprise Middleware
D-spheres (Dependency-Spheres) Conditional Messaging and Dependency-Spheres are novel extensions to standard middleware for messaging and object transaction processing.
Conditional Messaging allows an application to define, monitor, and evaluate various conditions on messages, such as time constraints on the receipt or the processing of a message by a set of final recipients who read messages from intermediary destinations like message queues. Messages can be evaluated to an outcome of success or failure based on such application-defined conditions. Dependency-Spheres extend the conventional model of distributed object transactions to include conditional messages. A D-Sphere represents a new type of gobal transaction context that includes both conventional object transactions and (conditional) messaging. Within a D-Sphere both synchronous object requests and asynchronous messaging operations may occur arbitrarily, and the final outcome of the transaction and messaging become interdependent. The D-Sphere system is a new middleware transaction service that introduces an increased level of reliability for the use of object middleware and message middleware in combination.
Gryphon Research - publish/subscribe middleware
Gryphon A key contribution of our research is to show that content-based publish/subscribe systems can be implemented efficiently and scalably in a wide-area network. This aspect of our research has been well-realized in the Gryphon system, though there is more to be done.
Although the current Gryphon system does not reflect it, we have also done research on an advanced model for publish/subscribe systems based on information flow. An information flow graph is used to model the selective delivery of events, the transformation of events, and the generation of new events as a function of states computed from event histories. A long-term goal is to merge the best features of distributed communications technology and database technology to support the requirements of message brokering.
xmlBlaster is a publish/subscribe and point to point MOM server (message-oriented middleware) which exchanges messages between publishers and subscribers. The message is described with XML-encoded meta information.
The xmlBlaster server is pure Java and under LGPL. Note that Perl, Python, C/C++ and Java (applications, applets, servlets) client demos are in the xmlBlaster distribution available.
FioranoMQ 5 FioranoMQ 5, released in February 2001, implements all of the JMS Publish/Subscribe and Point-to-Point (PTP) APIs, together with support for security, massive scalability allowing thousands of concurrent connections to the server, remote administration, guaranteed message delivery, and language interoperability. The security implementation includes integrated SSL support (with digital certificates) for encrypted data transfers with a full implementation of Java REALMS, allowing an external administrator to control access to system resources. An integrated C++ runtime library, based on JNI-bindings to the standard Java interfaces allows C++ and Java programs to communicate. Automatic store-and-forward across multiple servers ensures guaranteed message delivery across faulty networks.
Sonic MQ Application servers have cemented their place in today's business system deployments due to the scalability and security benefits they offer an enterprise. The business requirement of integrating applications both within and outside of the enterprise has highlighted deficiencies in the application server deployment model, including the expensive software components and extensive security information required on each system. Combining application servers with messaging infrastructures such as SonicMQ solves these problems. Any messaging system that requires integration with an application server must provide the following features:
Support for concurrent, asynchronous processing with the application server (through message-driven beans, server session pools, and connection consumers)
Support for distributed transactions through the XA protocol as defined by the JTA specification.
SmartSockets key benefits:
Avoid message loss with persistent interprocess communication
Optimize network bandwidth utilization with time-independent message distribution
Enhance service levels by leveraging queuing with publish-subscribe
Enable transaction-based processing
Reduce development and maintenance costs
With SmartMQ, you never have to worry about messages getting lost or accidentally deleted. SmartMQ offers added protection against message loss through persistent message queuing, store-and-forward, transactional messaging and more. It also gives you the flexibility to easily interoperate as needed with third party queue managers, using a single interface for queuing. Through its intuitive API and class libraries, SmartMQ enables the rapid development of fault tolerant distributed systems with far less time consuming configuration processes than traditional queuing products, driving down development and maintenance costs.
iBus//MessageBus is fully distributed IP Multicast JMS middleware. Zero maintenance, high-speed messaging. Light-weight, versatile and server-free message service, featuring the JMS API. Unique group coordination features for application-level clustering simplify the development of load-balanced, high available and tolerant applications. Supports IP Multicast. Free trial copy available.
DS Online ISSN: 1541-4922 • Feedback? Send comments to firstname.lastname@example.org.
This site and all contents (unless otherwise noted) are Copyright ©2002, Institute of Electrical and Electronics Engineers, Inc. All rights reserved