Introduction
- JMS stands for Java Message Service. JMS is an API that provides facility to read, create and send messages. JMS is asynchronous (To receive the message, client is not required to send request. Message will arrive automatically to the client) communication.
- JMS is mainly used to send and receive message from one application to another.
- Following are the messaging domain in JMS
Point-to-Point messaging domain: In this model, one message is delivered to one receiver only. There will be a QUEUE to hold the message until the receiver is ready.
Publisher/Subscriber (Pub/Sub) Messaging domain: In this model, one message is delivered to all the subscribers. There will be a TOPIC to hold and deliver
JMS Programming Model
JMS Queue (Point-to-Point messaging domain) configuration
In Case of Point-to-Point messaging, QUEUE will hold the message until the receiver is ready to receive the message. Here, we shall be creating two JNDI in Weblogic 12c.
- Create connection factory named queuedConnFactory
- Create destination resource named, myQueue
Once JNDI is created, server and receiver application needs to be created. Server and Receiver needs to run in two different console.
Create the following in Weblogic server
Create JMS Server
- Login to the weblogic admin console (localhost:7001/console)
- Click on JMS server as shown below and create the server called myJMSServer. Select available target in the next page
Create JMS Module
Follow the below screenshot to create JMS Module
Create Subdeployment
Follow the below screenshot to create Subdeployment
Create Connection factory
Follow the below screenshot to create Connection Factory
Create JMS Queue
Follow the below screenshot to create JMS Queue
Done with configuration
If you see below two screens that means you are done with the configuration
Connection factory and JMS Queue under JMS module will look like this
Connection factory and JMS Queue under Subdeployment will look like this
No comments:
Post a Comment