Saturday, July 9, 2011

Weblogic JMS Basics

Slide 28
    The Java Messaging Service (JMS) is a Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. To use JMS, we should have a JMS provider that can manage the sessions and queues. In OSB, weblogic server is the JMS provider.
JMS Provider - An implementation of the JMS interface for a Message Oriented Middleware (MOM)
JMS Client - An application / process which can either produce or consume messages
JMS Message - The data which is transferred between JMS clients
JMS Queue - A space where the messages will be saved for sending or receiving. It will be either saved in the  Filestore or JDBC store.

JMS Topic - A mechanism for delivering messages to multiple subscribers.
JMS Point-to-Point model - Here the sender posts messages to the receiver queue.
JMS Publish/Subscribe Model - Here the message will be posted to multiple subscribers. We use 'topic' rather that 'queue' here.
JMS Server – To host different set of modules and any associated persistent storage that reside on a weblogic server instance. 
lJMS Modules – Contains configuration resources like queues, topics and connection factories 
lConnectionFactory – encapsulates connection configuration information , and enables JMS applications to create a connection 
lJNDI (Java Naming and Directory Interface) – resource lookup of JMS resources like connection factories and destinations (queues or topics) which are configured with a JNDI name. 
lWeblogic persistent storage – To store persistent message data.
     Eg : Filestore or JDBC-accessible. 

Logical diagram

JMS API architecture diagram

How to create a distributed JMS Queue

 I have seen a very good topic for this. Go through the below link

How to create a distributed JMS Queue


1 comment: