Messaging middleware based on the Java Message Service (JMS) application programming interface is rapidly emerging as the technology of choice for application-to-application (A2A) integration.
This is according to Rick Parry, MD of Progress Software SA. Parry points out that the messaging paradigm is nothing new: it was first used in the 1970s to facilitate communication among back-office mainframe applications running on dedicated network connections.
However, it is regaining currency because it is suited to getting heterogeneous applications to communicate seamlessly with each other, a requirement faced by organisations as they build e-business systems. Messaging technology is particularly well suited to applications such as integration of disparate systems after mergers and acquisitions, communication between diverse systems used in a business-to-business (B2B) e-commerce community, and supply chain integration.
Parry says the biggest advantage messaging offers over most other types of middleware is that it supports both synchronous and asynchronous transmission of information.
Asynchronous messaging allows sending applications to generate messages at an appropriate time and handle peak processing periods as they occur.
However, messaging can also handle the instances where synchronous communication is required, such as when an application needs to wait for the result of a complex mathematical calculation before making a decision.
Parry notes: "There are other options available for A2A integration such as CORBA, DCOM, and Java`s RMI, all of which use a remote procedure call (RPC) mechanism to transfer information among applications.
"However, RPC-based solutions depend on a complex topology which couples clients and servers in a simulated process. All participants in this topology must be aware of each other and all connections must be established before communication can take place."
That means the failure of a single application client can bring the entire system down. In addition, this architecture limits flexibility and performance.
Parry says the JMS API (application programming interface) combines Java technology with enterprise messaging to offer a robust tool for A2A integration. The JMS specification is based on a common set of messaging concepts and programming strategies supported by all JMS technology-compatible messaging systems.
JMS - emerging as the de facto messaging standard - facilitates reliable asynchronous communication between software components in a distributed computing environment, which helps to simplify software development and integration.
The JMS API forms an integral part of the Java 2 Enterprise Edition (J2EE) platform, the standard for the application server market. It helps companies rapidly to build distributed applications, while retaining freedom of choice in application servers and messaging technology.
As an example of messaging technology in action, Parry points to Commerce One`s use of the SonicMQ message queuing software in its MarketSite Portal solution to support the rapid, secure exchange of data or messages over the Web via detailed routing algorithms. Message types include everything from simple purchase orders to sophisticated CAD (computer-aided design) files. The MarketSite Portal links open e-marketplaces in the food, healthcare, telecommunications, and other industries to the Commerce One Global Trading Web, an international B2B trading community.
Commerce One uses SonicMQ and an XML-based transaction infrastructure to provide seamless interaction among Global Trading Web participants. Existing members can access new marketplaces on the Global Trading Web without altering local configurations or applications. All participants experience the rapid exchange of auction, payment, logistics, and other supply chain services.
Share
Editorial contacts