JMS Configuration in SOA Server

 Step1 Start your WebLogic Server an Login to the AdminConsole.

 Step2 Creating JMS Server

Creating JMS Server-2

Selecting JMS Server Store Type

Configuring JMS Store

Choosing JMS Store for JMS Server

Targeting to the JMSServer

Activating the JMS Server Configuration

Step3 Configuring JMS Module:

Creating JMS Module

Entering JMS Module Name

Targetting JMS Module

Finishing the Module Creation

Step4 Creating Connection Factory:

Creating JMS Connection Factory

Selecting JMS Module to be Created

"Providing Name/JNDIName to Connection Factory

(This will be used in the JMSAdapter configuration in the Composite)"

Targeting the CnnectionFactory

Step5 Creating JMS Queue

Selecting JMSQueue to be Created

Queue Selection

Assigning Name/JNDIName to Queue

Creating SubDeployment

Assigning Name to the SubDeployment

Targeting the JMS Queue

Activating the Final Changes

====================================================

Part1: Create JMS Server

S1: JMS Server -> new -> 

    Name: Test

"S2: Persistent Store : Create a New Store (JDBC Store

[Create a new Data source], File Store[Create a New Store], Replicated Store)"

S3: Name: TestFileStore

S4: Target (server)

Part 2: Create JMS Module

S1: Weblogic Console --> Services --> Messaging --> JMS Module --> New ->

Provide a JMS Module Name: TestSystemModule

S2: next-> Target (server) select the target server(to which you want to deploy this, usually the managed server where SOA is configured)

S3: Add resources to JMS Module.  Leave the check box(define resources in this module) --> Finish

Part 3: Creating a sub-deployment

Every JMSModule has to be targeted to a Sub-Deployment.

A Sub-Deployment is used to group targets

Click on the just created MyJMSModule --> click on Subdeployments tab at the top --> 

New --> Give name to the subdeployment --> 

"select the target (can either be a server or JMSServer. As this is specific to JMS, I've selected SOAJMSServer

(default available JMS Server. You can even create your own JMSServer))"

Part 4: (create connection Factory, Topic, Queue, DQ, DT etc)

A Connection Factory is used to create connections for the JMS Clients to interact with JMS Resources

S1: On resource screen, click on new [Click on the just created MyJMSModule]

S2: create Connection Factory

S3: Name: test/weblogic/default/cf

    JNDI Name: test/weblogic/default/cf

Ex: 

Name: test/weblogic/default/cf

JNDI Name: test/weblogic/default/cf

Name: test/weblogic/default/DQ

JNDI Name: test/weblogic/default/DQ

Name: test/weblogic/default/DT

JNDI Name: test/weblogic/default/DT

View JNDI Tree:

Server-> Default Server (admin) -> View JNDI Tree

Part5: Creating a Queue

Queue is the actual destination

Click on the just created MyJMSModule --> New

-> Queue --> Give name & JNDI name --> select subdeployment --> Finish

This sets up all the JMS Resources.

Part6: "You are still left with one configuration to be done to use this queue with a JMS Adapter, 

which is creating an outbound connection pool"

go to Deployments --> JMSAdapter --> Configuration --> Outbound Connection Pools --> New -->

oracle.tip.adapter.jms.IJmsConnectionFactory --> Next --> 

"Provide JNDI Name(Queue JNDI Name) for the Connection Pool(This will be used in the JMSAdapter configuration in the  Composite)"

This will create a Connection Pool, but Connection Factory(the resource used to connect to Queue) 

is not yet configured

Click on the just created connection pool -->

"enter the ConnectionFactoryLocation as the JNDI name that you've created  (which is jms/myConnFactory and hit Enter)"

-> Save

Update the JMSAdapter deployment

Console --> Deployments --> click on JmsAdapter checkbox --> Update --> select defaults --> Finish

JMS Module(Optional) Is a definition that contains various JMS Resources like queues, topics, etc.

sub-Deployment(Optional) used to group target servers

Connection Factory is a Weblogic resource that enables JMS clients to create connections to JMS destinations

Queue / Topic the actual destination of the message, either a queue(point to point) or topic(publish-subscribe)

Connection Pool Create a pool of connections for the JMSAdapter application

Where actually jms used

Ex: wats app,skype

JMS service is unique.

Note:

1) A jms server can be target to strictly one weblogic single server instance only.(It cant be target on cluster or multiple server)

2) Managed server can have multiple jms server  but one jms  server is targeted to one managed server.

MS1- jms1,jms2…n

Note:

Any sender or receiver want to communicate with jms server then it has to go through submodule, It can’t communicate directly.

Jms server uses connection factory to communicate with file-store.

Managed server can directly write to a file store bcz we have created persistent store and targeted to managed server

Flow 

sender/receiver-> queue(any module) -> jmsserver1- managedServer(weblogic server) -> pick data from file store.

Once the data is picked by receiver from file store then msg will be deleted from filestore because it is one to one communication.