JMS Queue over Cluster Server In Oracle SOA

Here in our case we have following server configuration:

1.Admin server running over 7001 port.

2.Node 1 running over IP1 and Port1.

3.Node 2 running over IP2 and Port2.

4.Load balancer running over IP2 and Port 3

5.SOA Cluster with Node1 and Node2 as HTTP port and IP of Load balancer.

Following steps need to be taken for configuration of JMS Queue in weblogic cluster, Before we start let me clear one thing, There are two types of queue one is for single admin server and other for weblogic cluster domain, In case of single node server domain we need to use queue and in case of weblogic cluster domain we need to create distributed queues over the domain:

Configures the persistence stores and targets these to the migratable targets:

Create store and forward agents for both persistence stores: Create two store and forward agents for both persistence store, repeat steps same for second.

Create the JMS servers on a migratable target and every JMS server has its own file persistence store (JMSServer_1 & JMSServer_2): Repeat same step for second JMS Server creation.

Create a JMS Module with name "JMSModule”

Create Sub-Deployment plan under with name “JMSSubPlan”

Select Services > JMS Modules > JMSModule

Create a connection factory and a distributed queue both targeted on the cluster.

Connection factory name:

1. JMSCF1 –jms/JMSCF1

Connection factory configuration:

1. Select Services > JMS Modules > JMSModule
2. Click on “New”
3. Click on “Connection factory” radio button.
4. Select advance targeting at the time of server targeting so JMS server can be mapped.

Click on advance targeting and select JMS Servers and select created subdeployment plan.

Queue Name:

1. JMSQueue1 –jms/JMSQueue1

Click on advance targeting

Create a JMS Adapter Connection Pool in WebLogic Server

The BPEL process we are about to create uses a JMS adapter to write to the JMS queue. The JMS adapter is deployed to the WebLogic server and needs to be configured to include a connection pool which references the connection factory associated with the JMS queue.

1. In the WebLogic Server Console
2. Go to Deployments > Next and select (click on) the JmsAdapter
3. Select Configuration > Outbound Connection Pools and expand oracle.tip.adapter.jms.IJmsConnectionFactory. This will display the list of connections configured for this adapter.
4. eis/sbjms/JMSQueue1
5. These JNDI names are actually quite confusing. We are expecting to configure a connection pool here, but the names refer to queues and topics.
6. Expand oracle.tip.adapter.jms.IJmsConnectionFactory again and select (click on) eis/sbjms/JMSQueue1
7. The ConnectionFactoryLocation must point to the JNDI name of the connection factory associated with the JMS queue you will be writing to. In our example, this is the connection factory called JMSCF1, with the JNDI name jms/JMSCF1, Same for remaining JMS Queue.
8. The next step is to redeploy the JmsAdapter.
   Navigate back to the Deployments screen, either by selecting it in the left-hand navigation tree or by selecting the “Summary of Deployments” link in the breadcrumbs list at the top of the screen. Then select the checkbox next to JmsAdapter and press the Update button
   
9. On the Update Application Assistant page, select “Redeploy this application using the following deployment files” and press Finish.After a few seconds you should get the message that the selected deployments were updated. The JMS adapter configuration is complete and it can now be used to access the JMS queue.

CREATE JMS COMPONENT IN BPEL AND YOU ARE READY TO USE QUEUES OVER CLUSTER.

You can check cluster queues for messages:

Select any check box and click on "Show Messages"

It's Done!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!