Thursday, October 4, 2012

Carbon 4.0.0 - JMS Address endpoint URL format


This applies when you are using WSO2 ESB 4.5.0+ and WSO2 MB 2.0+. In WSO2 Message Broker 2.0, we use Andes as the message broker, an extended version of QPid.

The format to use when defining a JMS endpoint is like follows. Remember The configuration will be different if you are not using Andes.


jms:/MaterialMasterProxy1?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&java.naming.provider.url=repository/conf/jndi.properties&transport.jms.DestinationType=queue



If you are want to create an address endpoint with JMS in WSO2 ESB 4.5.0, then it will look following.



 <endpoint name="MaterialMasterProxyEndpoint">
     <address uri="jms:/MaterialMasterProxy1?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&amp;java.naming.provider.url=repository/conf/jndi.properties&amp;transport.jms.DestinationType=queue"/>
  </endpoint>


In ESB 3.0.1, we defined the address endpoints as follows.

jms:/MaterialGroupsProxy1?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&amp;java.naming.provider.url=tcp://10.200.3.117:5682&amp;transport.jms.DestinationType=queue&amp;java.naming.provider.url=repository/conf/server.properties


Posted by Unknown at 4:52 PM
Keywords: , ,

1 comment:

  1. UnknownSeptember 23, 2013 at 9:37 AM

    This is a fantastic benefit of in the process of freight dispatcher training on the internet as well as with university since you'll be reaching real industry experts, you can question issues and become clarified without delay.

    ReplyDelete

Subscribe to: Post Comments (Atom)