JMS
JMS (Java Message Service) is an API that provides the facility to create, send and read messages. It provides loosely coupled, reliable and asynchronous communication.
JMS is also known as a messaging service.
Requirement of JMS
Generally, user sends message to application. But, if we want to send message from one application to another, we need to use JMS API.
Consider a scenario, one application A is running in INDIA and another application B is running in USA. To send message from A application to B, we need to use JMS.
Messaging Domains
There are two types of messaging domains in JMS.
1)Point-to-Point Messaging Domain
2)Publisher/Subscriber Messaging Domain
1) Point-to-Point (PTP) Messaging Domain
In PTP model, one message is delivered to one receiver only. Here, Queue is used as a message oriented middleware (MOM).
The Queue is responsible to hold the message until receiver is ready.
In PTP model, there is no timing dependency between sender and receiver.
2) Publisher/Subscriber (Pub/Sub) Messaging Domain
In Pub/Sub model, one message is delivered to all the subscribers. It is like broadcasting. Here, Topic is used as a message oriented middleware that is responsible to hold and deliver messages.
In PTP model, there is timing dependency between publisher and subscriber.
JMS Programming Model
How to use the JMS Adapter in SOA 12c
JMS (Java Message Service) is an API that provides the facility to create, send and read messages. It provides loosely coupled, reliable and asynchronous communication.
JMS is also known as a messaging service.
Requirement of JMS
Generally, user sends message to application. But, if we want to send message from one application to another, we need to use JMS API.
Consider a scenario, one application A is running in INDIA and another application B is running in USA. To send message from A application to B, we need to use JMS.
Messaging Domains
There are two types of messaging domains in JMS.
1)Point-to-Point Messaging Domain
2)Publisher/Subscriber Messaging Domain
1) Point-to-Point (PTP) Messaging Domain
In PTP model, one message is delivered to one receiver only. Here, Queue is used as a message oriented middleware (MOM).
The Queue is responsible to hold the message until receiver is ready.
In PTP model, there is no timing dependency between sender and receiver.
2) Publisher/Subscriber (Pub/Sub) Messaging Domain
In Pub/Sub model, one message is delivered to all the subscribers. It is like broadcasting. Here, Topic is used as a message oriented middleware that is responsible to hold and deliver messages.
In PTP model, there is timing dependency between publisher and subscriber.
How to use the JMS Adapter in SOA 12c
Oracle JCA Adapter for JMS (Oracle JMS Adapter), which enables an Oracle BPEL process or an Oracle Mediator component to interact with Java Messaging Service.
Configuring JMS Resources for JMSAdapter in Oracle SOA
Before building the applications using JMS adapter we have to configure the JMS rescouces for the JMS adapter in the weblogic console.
You can refer the below link to get the steo by step process to configure the JMS adapter
http://www.soatutor.com/2013/07/configuring-jms-resources-for-jmsadapter.html
How to build the application using JMS adapter in Oracle SOA
You can refer the below link to build a sample application using JMS adapter to consume and produce a message
http://learn-oraclesoa.blogspot.in/2013/04/oracle-jms-adapter-tutorial.html
If you have any doubt in configuration or builiding the application you can ask your doubt in the comments section.
No comments:
Post a Comment