Java Message Service

The Java Message Service (JMS) API is a Java message oriented middleware API for sending messages between or moreclient S. JMS is a part of the Java Platform, Enterprise Edition, and are defined by a specification developed under the Java Commu Nity Process as JSR914. It's a messaging standard that allows application components based on the Java Enterprise Edition (JEE) to create, send, Receive, and read messages. It allows the communication between different components of a distributed application to being loosely coupled, reliable, an D asynchronous. It supports Models:point-to-point, Publishand subscribe.

      Using Java, JMS provides a, separating the appli Cation from the transport layer of providing data. The same Java classes can be used to communicate with different JMS providers by using JNDI information for the desired PR Ovider. The classes first use a connection factory to connect to the queue or topic, and then use populate and send or publish th E messages. On the receiving side, the clients then receive or subscribe to the messages.

      to use JMS, one must has a JMS provider that can Manag E The sessions and queues. Starting from Java EE version 1.4, JMS provider have to is contained in all Java EE application servers. This can is implemented using the message inflow management of the Java EE Connector Architecture, which was first made a Vailable in that version. There is many JMS providers such as Apache ActiveMQ, OPENJMS, JBoss Messaging and HornetQ from JBoss, Open Message Que UE from Sun Microsystems, BEA Weblogic, WebSphere MQ and so on. Asfollows, let's tell something on WebSphere MQ developed by IBM.

IBM WebSphere MQ is a family of the network software products launched by IBM in March 1992 . It is previously known as MQSeries, a trademark that IBM rebranded in 2002 to join the suite of WebSphere products. WebSphere MQ, which is often referred to simply as "MQ" by the users, is the IBM ' s Message oriented middleware offering. It allows independent and potentially non-concurrent applications on a distributed system to communicate with each other. MQ is available on a large number of platforms, including z/OS, os/400, Transaction processing Facility, Unix, HP nons Top, Linux, OS 2200 and Microsoft Windows.

     WebSphere MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never is lost if MQ is appropriately configured. It also provides application designers with a mechanism to achieve non-time-dependent architecture. Messages can sent from one application to another, regardless of whether the applications is running at the same time . IF a message receiver application is not running when a sender sends it a message, the queue manager would hold the MESSAG e until the receiver asks for it. Besides, it providers a means for transforming data between different architectures and protocols, such as Big Endian to Little Endian, or EBCDIC to ASCII. This was accomplished through the use of the message data exits. It allows receipt of messages to "trigger" other applications to run, and thus provides the framework for a message DrivEn architecture. Unlikeemail, MQ itself is responsible for determining the destination of messages by the definition of queues, so proces Sing of sent messages can be moved to a different application at a different destination.

Java Message Service