Configuring JMS Resources for JMSAdapter

"please note this document is generic please follow the name and other details as per as your configuration or
requirement following proper naming convention. ; for example soa_server1 is used as soa server name in
this docs if in your configuration soa server name is wls_soa1 than consider the same and for all"
Configuration of various JMS resources in WLS
1-JMS Module(Optional) : Is a definition that contains various JMS Resources like queues, topics, etc.
2-Sub-Deployment(Optional) : used to group target servers
3-Connection Factory : is a Weblogic resource that enables JMS clients to create connections to JMS destinations
4-Queue / Topic : the actual destination of the message, either a queue(point to point) or topic(publish-subscribe)
5-Connection Pool : Create a pool of connections for the JMSAdapter application

Start :1) Login to Weblogic server console using - http://<hostname>:7001/console.

name and other details as per as your configuration)

(please provide the host

2) Go to the Domain structure as shown in the screen print

Prepared by Abhishek Ajral

3) In order to enable the buttons click on the Lock & Edit button under Change Center on the top left
corner.

Resource Configuration:-

1-JMS Module(Optional)
This step is not mandatory, one can use the default module 'SOAJMSModule' or can create new as described
here.
Weblogic Console --> Services --> Messaging --> JMS Module --> New --> Provide a JMS Module Name --> select
the target server(to which you want to deploy this, usually the managed server where SOA is configured) -->
Leave the check box (Would you like to add resources to this JMS system module?) --> Click Finish

Prepared by Abhishek Ajral

Prepared by Abhishek Ajral

Please target to appropriate server as per as your configuration

Prepared by Abhishek Ajral

Click Finish

This step creates a new JMSModule 'MyJMSModule'.

2-Sub-Deployment(Optional)
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
Subdeployments --> select the target (can either be a server or JMSServer. As this is specific to JMS,
SOAJMSServer is selected(default available JMS Server. You can even create your own JMSServer))

Prepared by Abhishek Ajral

Prepared by Abhishek Ajral

3-Connection Factory
A Connection Factory is used to create connections for the JMS Clients to interact with JMS Resources
Click on the just created MyJMSModule --> New --> Connection Factory --> Give name & JNDI name -->
soa_server1(selected by default) --> Finish

Prepared by Abhishek Ajral

Prepared by Abhishek Ajral

4-Creating a Queue
Queue is the actual destination
Click on the just created MyJMSModule --> New --> Queue --> Give name & JNDI name --> select
Subdeployments --> Finish

Prepared by Abhishek Ajral

This sets up all the JMS Resources.

Prepared by Abhishek Ajral

5-Connection Pool
For this, go to Deployments --> JMSAdapter --> Configuration --> Outbound Connection Pools --> New -->
oracle.tip.adapter.jms.IJmsConnectionFactory --> Next --> Provide 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, which is done in the next step

Prepared by Abhishek Ajral

Now
Click on the just created connection pool --> enter the ConnectionFactoryLocation as the JNDI name that is
created in Step 2 (which is jms/myConnFactory and make sure to hit Enter) --> Save

Update the JMSAdapter deployment

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

Make sure you see a message at the top of the screen saying, Selected Deployments were updated.

In the Change Center panel in the upper left corner of your screen, click Activate Changes
Prepared by Abhishek Ajral

Again, ensure that the message that the top of the screen reads, All changes have been activated. No restarts
are necessary.

Now, the ConnectionPool name eis/jms/myConnPool can be used in the JMSAdapter in your SOA Composite
If you get any error saying the connectionPool not found, restart the SOA Server

End

Prepared by Abhishek Ajral