 |
 |
 |
 |
|
|
 |
JMS Server is an API that provides support for both the point-to-point and publish/subscribe domain, guaranteed message delivery, persistent messages, and durable subscribers.
J2EE provides a standard API for developing distributed architectures, but there is no common message format supported by the vendors. The Java Message Service Specification (JMS spec) defines an interface for message services but does not define an implementation. Thus arises a need for a JMS API implementation provider to define mapping between messages and enable third-party JMS server to integrate with the Server.
The use of asynchronous messaging allows the development of loosely connected systems and applications. These systems are more resilient in the event failures, and easily extensible as new applications are developed. Additionally, messaging provides an effective means of transmitting events between applications.
JMS integration streamlines application behavior, eliminates bottlenecks and reduces wait time for the user, resulting in a better shopping experience and heightened customer retention.
Pramati exposes the SPI (Service Provider Interface) com.pramati.services.resource.spi.JMSProvider for seamless integration. Application server uses this SPI to get any information it requires from the JMS server. The JMS vendor needs to provide an implementation specific to his JMS implementation. The server creates an instance of this adapter and initializes it using the properties defined.
 |
|
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |