Configuration of JMS Adapter in SOA Suite 12C

Introduction:

JMS (Java Message service) is an application program interface that enables communication between applications. FMW (Oracle Fusion Middleware) supports scalable enterprise messaging system. JMS producer creates JMS messages and JMS consumer consumes JMS messages. JMS interface use Extensible Markup Language (XML) for communication purpose. JMS supports two messaging paradigms a�� queue (point to point) and topic (publish/subscribe).

Queue: In queue messaging system, the messages will be saved in the queue, until the messages are consumed. Once the message is consumed, that will not be available in the queue again for consumption.

Topic: In topic messaging system, the messages will be published by producers and those will be subscribed by consumers. The messages will be available in the topic after consuming by one consumer also. Topic message paradigm is opposite to Queue paradigm.

Configuration of JMS adapter includes 6 major setups a��

1. JMS Server a�� JMS server is a container of resources in JMS module. It manages and maintain the persistence and state of messages.
2. JMS Module a�� This is a container of JMS resources like connection factory, queue, topic etc.
3. Subdeployment a�� Subdeployment is a grouping of targets. It creates connection between JMS server and JMS module
4. Connection Factory a�� It enables JMS client to create connection to the JMS destination
5. Queue/Topic a�� actual destination of the messages
6. Connection Pool a�� Connection pool represents a physical connection to the JMS provider

Configuration of JMS adapter will be cleared from the below diagram.

Follow the below steps to configure JMS resources in the weblogic server.

1. Navigate to Services -> Messaging -> JMS Servers in the Administration Console. Click on New
2. Enter JMS server name and select DefaultServer as Target in the next window.
3. Create JMS module in the admin server. Navigate to Services -> Messaging -> JMS Modules
4. Click on New. Enter JMS module name and select target server in the next window. Click on Finish button
5. Open testJMSModule and navigate to Subdeployments Enter subdeployment name
6. Click on Next button and select target JMS server
7. Navigate to Configuration tab to create Connection Factory and Queue. Click on New
8. Select Connection Factory as resource type
9. Enter connection factory name (testConnectionFactory), JNDI connection name of connection factory (jms/ testConnectionFactory) and select XA Connection Factory Enabled. A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A� A�JNDI (Java Naming and Directory Interface):The most common use case is to set up a connection pool on a Java EE application server. Any application that’s deployed on that server can gain access to the connections without knowing the details about the connection. A� A� A� A� A� A� A� A� A� A� A� A�XA Transaction:You can access multiple databases in XA Transaction. It has a Transaction Manager.A�But Non XA Transaction does not have these facilities.
10. Click on Next button and select target server.
11. Click on Finish button. Connection Factory will be created successfully.
12. Again click on New button and select Queue as resource type
13. Enter queue name (testQueue) and JNDI name of queue (jms/testQueue)
14. Click on Next button and select subdeployment from the drop down listA�and target JMS server
15. Queue will be created successfully and successful message will be displayed.
16. Now navigate to Deployments -> JMS Adapter -> Configuration -> Outbound Connection Pools
17. Click on New button to create new connection pool and select outbound connection group
18. Enter JNDI name for outbound connection instance (eis/jms/testConnectionPool)
19. Click on Finish button and then select the connection pool which is created in the previous steps. Check the below screenshot
20. Navigate to Properties tab and enter connection factory name in the ConnectionFactoryLocation property. You have to explicitly press enter button after entering connection factory name.
21. Click on Save button and you will get successful message as shown in the below screenshot.
22. Update JMS adapter deployment file (JMSPlan.xml). Navigate to admin console -> Deployments -> select checkbox of JMS adapter
23. Click on Update button and select redeploy this application Click on Finish button.

Now you can use eis/jms/testConnectionPool in your SOA composite.

You can refer my next posts on JMS adapter to see the usage of connection pool for messaging service.