JMS Messege Bridge between two Weblogic Servers

Everyday we look for information in the web, I hope everyone gets something which is of help to you to proceed to the next step. There might be something you can share which can helpful for others to proceed to next step. Hence please contribute to the web (blogs, forums etc.)

JMS Messege Bridge Setup steps

Scope: Between two different versions of Weblogic Server.

Steps to setup Messege bridge between Weblogic Server 9.2.2 and Weblogic Server 10.3.4

Source Queue: Weblogic Server 9.2.2
Target Queue: Weblogic Server 10.3.4

Note: The names in source server should not be there in target server. For example, the connectionFactory name, queue name, even the server name where the JMSServer is targeted should not be same.

Steps to setup JMSServer, Connection Factory and Queue in WLS 9.2.2:
1. Create or use a Weblogic Server 9.2.2 domain with the AdminServer name as AdminServer1 running on port 7001. Assuming we have only admin server and this is for testing purpose.

2. Login in to Weblogic Server 9.2.2 server console and Create a JMS Server and name it as JMSServer01 with the required persistent store and target it to AdminServer1.

3. Create JMS Module and name it as JMSSystemModule01 and target it to JMSServer01

4. Add a ConnectionFactory resource under JMSSystemModule01 with JNDI name “jms/ConnectionFactory01 and the name as ConnectionFactory01”

5. Add a Queue resource under JMSSystemModule01 with JNDI name “jms/Queue01” and the name as Queue01.

Steps to setup JMSServer, Connection Factory and Queue in WLS 10.3.4:

1. Create or use a Weblogic Server 10.3.4 domain with the AdminServer name as AdminServer running on port 8001. Assuming we have only admin server and this is for testing purpose.

2. Login to Weblogic Server 10.3.4 server console and Create a JMS Server and name it as JMSServer02 with the required persistent store and target it to AdminServer.

3. Create JMS Module and name it as JMSSystemModule02 and target it to JMSServer02

4. Add a ConnectionFactory resource under JMSSystemModule02 with JNDI name “jms/ConnectionFactory02” and the name as ConnectionFactory02.

5. Add a Queue resource under JMSSystemModule02 with JNDI name “jms/Queue02” and the name as Queue02.

Note: Its advised to setup bridging in higer version server.

Steps to setup Bridging in higer version server, in our case it is WLS 10.3.4

6. Login to weblogic 10.3.4 Server console and navigate to Services --> Messaging -->Bridges --> JMS Bridge Destinations

7. Name: SourceQueueBridge

8. Adapter JNDI name: eis.jms.WLConnectionFactoryJNDINoTX

9. Do not enter anything in Adapter classpath

10. Connection URL as http://<server-ip>:<7001>

11. Initial Context Factory:

12. Connection Factory JNDI name: jms/ConnectionFactory01

13. As we want to bridge two queues, one in WLS 9.2.2 and WLS 10.3.4, our destination is Queue and the JNDI name we need to enter is the queuename of the source.

Destination JNDI Name: jms/Queue01

14. Destination Type: Queue

15. User Name: weblogic

16. Password: <server password>

17. Confirm Password: <server password>

Creation of Source JMS Bridge is over, now we will create a bridge for target

18. Navigate to Services --> Messaging --> Bridges --> JMS Bridge Destinations

19. Name: TargetQueueBridge

20. Adapter JNDI name: eis.jms.WLConnectionFactoryJNDINoTX

21. Do not enter anything in Adapter classpath

22. Connection URL as http://<server-ip>:<8001>

23. Initial Context Factory: <no change>

24. Connection Factory JNDI name: jms/ConnectionFactory02

25. As we want to bridge two queues, one in WLS 9.2.2 and WLS 10.3.4, our destination is Queue and the JNDI name we need to enter is the queuename of the target.

Destination JNDI Name: jms/Queue02

26. Destination Type: Queue

27. User Name: weblogic

28. Password: <server password>

29. Confirm Password: <server password>

JMS Bridge Destinations to transfer messages from Source WLS922 server to target WLS1034 server are created. Now we combine the source and target JMS bridge destinations.

30. Navigate to Services --> Messaging --> Bridges --> New, to create a new Bridge

31. Source Bridge Destination: SourceQueueBridge

32. Target Bridge Destination: TargetQueueBridge

33. Leave the other fields with default values as of now.

34. Save and release the configuration.

35. Restart both the server. Restart of server where bridge setup is done alone is enough. This is just to avoid any development environment issues.

To Test the bridge:
Create a servlet to send data to “jms/Queue01”
Create a MDB to listen to “jms/Queue02”
Send a message and check the bridging.

Reference:
Configuring and Managing the Messaging Bridge- Configuring and Managing the Messaging Bridge

or http://download.oracle.com/docs/cd/E17904_01/wls.htm