As explained in my previous post: http://oraclefusion1011.blogspot.com/2011/01/foriegn-jms.html
we can use Foreign JMS or Message Bridge to access remote JMS.
There is another simple way of using the remote CF JNDI to access remote JMS, here are the steps :
Server 1: This host the JMS
- Create JMS Module : MyVendorModule
- Create JMS Queue : jms/Queue/Vendor_Que
- Create Connection Factory : com.myorg.jms.VendorQueConnectionFactory
Server 2: The consumer Server
Create outbound connection pool in JMS Adapter :
eis/VendorInput/Queue , with following important properties :
ConnectionFactoryLocation : com.myorg.jms.VendorQueConnectionFactory
FactoryProperties :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://server1:8001
for clustered env
FactoryProperties :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://server1:8001,server2:8002
or
FactoryProperties :
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://server1,server2:8001
If ports are same
This option works well with SOA - Bpel , however Message bridge and Remote JMS provides more usability with heterogeneous code/Tech need to access remote JMS
Cheers !!
No comments:
Post a Comment