javapandit.net
  • Home
  • Quick Java
    • Exception Handling
    • Collections Framework
  • Java Best Practices
  • Web Services
    • Web Service Basics
    • Ten Basic webservice concepts
    • XML
    • Apache Axis
    • Restful Web Services
  • JMS Concepts
    • JMS- MySQL
  • Hadoop
    • NoSQL DATABASEs
    • Apache Sqoop
    • Hadoop Interview Questions
  • Java 5
  • Java 8
    • Java 8 : Lambda Expressions
  • JDBC
  • Java Architect
    • Enterprise application re-platforming strategies
    • Java Memory Management
  • Java Programs
  • Technical Tips
    • How to set JAVA_HOME environment variable
    • How to create an auto increment field in Oracle?
    • Linux Commands
  • Best Java Interview Questions
    • Java Interview Questions- YouTube
  • Interview Questions
    • Java Tech interview Questions
    • Core Java Interview Questions >
      • core tech questions1
      • Java Collection interview questions
      • Java Concurrency
    • Servlets Interview Questions
    • JSP Interview Questions
    • Java Web Services Interview Questions
    • EJB Interview Questions
    • XML Interview Questions
    • JMS Interview Questions
  • Struts Interview Questions
    • Struts 2 Interview Questions
  • Java EE Architects Interview Questions
    • Java Architect Interview Questions
    • Top 10 reasons for Java Enterprise Application Performance Problems
    • Web Application Scalability Questions for IT Architect
  • JavaPandit's Blog
  • Web Services Interview Questions
  • Servlets And JSP
  • Oracle SOA Interview Questions
    • Open ESB /JBI
    • BPEL Language
  • Log4J
  • Ant
  • Maven
  • JMeter
  • JUnit
  • Apache POI Framework
  • ORCALE SERVICE BUS (OSB) Interview Questions
  • J2EE Patterns
    • Model-View-Controller (MVC)
    • Front Controller
    • DAO
    • Business Delegate
    • Session Facade
    • Service Locator
    • Transfer Object
    • Design Patterns >
      • Creational Patterns >
        • Singleton
      • Behavioural Patterns
      • Structural Patterns
    • Intercepting Filter
  • SQL Interview Questions/Lab
  • Best Wall Papers
    • Devotional Songs
  • Java Community
  • HIBERNATE
  • ORACLE CC&B
    • Oracle CC&B Interview Questions
  • Docker
  • Little Princess
    • Sai Tanvi Naming Ceremony Celebrations
    • Rice Feeding Ceremony
    • Sai Tanvi Gallery
  • APPSC Career Guidance
    • AP History
    • Indian Polity
    • Indian Economy
    • Science & Technology
    • Mental Ability and Reasoning
    • Disaster Management
    • Current Affairs and Events
    • General Sciences >
      • Biology
      • Physics
      • Chemistry
    • Previous Question Papers
  • About Us
  • Contact US

Java Messaging Services (JMS)

JMS  stands for Java Messaging Service. JMS is a specification that describes a common way for Java programs to create, send, receive and read "distributed enterprise messages".

Enterprise Messaging:-
Enterprise messaging is a method for transmitting data from one enterprise application to another. Its main advantage is that enterprise messaging eliminates the need to synchronize applications from multiple vendors running on different platforms.

The Java message service is a MOM (Message Oriented Middle-ware) and thus allows to decouple producers and consumers of messages.

The programmers need not to rewrite a whole application to implement JMS and will not have any dependency to a particular software vendor. So JMS will be vendor neutral.

JMS API:  JMS API communication is loosely coupled communication.

JMS API
         - defines a vendor independent access to various MOM systems.
         - is a part of the J2EE platform.
         - is defined with the javax.jms package.
JMS API is not only loosely coupled, asynchronous messaging and reliable delivery.

• Asynchronous:
 A JMS provider can deliver messages to a client as they arrive;
a client does not have to request messages in order to receive them.

• Reliable:
The JMS API can ensure that a message is delivered once and only
once.

JMS API Architecture

Picture
• A JMS provider is a messaging system that implements the JMS interfaces and provides administrative and control features.

• JMS clients are the programs or components, written in the Java programming language, that produce and consume messages.

• Messages are the objects that communicate information between JMS clients.

• Administered objects are preconfigured JMS objects created by an administrator for the use of clients. The two kinds of administered objects are destinations and connection factories (Topic or Queue).

• Native clients are programs that use a messaging product’s native client API instead of the JMS API. An application first created before the JMS API became available and subsequently modified is likely to include both JMS and native clients.

Prev 1 2 3 4 5 6 7 89 Next
Powered by Create your own unique website with customizable templates.