We're setting this same stuff up in the transport management component IIRC. Is this for the BrokerManager component? If so do we need all this info (sorry I'm not a JMS expert)?
Sanjiva. On Thu, Dec 9, 2010 at 10:18 AM, Manjula Rathnayake <[email protected]>wrote: > Hi all, > > I was working on JMS Broker configuration in Broker component. To make > a connection to the broker, > publish and subscribe to a topic, following parameters need to be provided. > > 1. JNDI factory initial: this is used to create initial context > In Qpid broker: > > java.naming.factory.initial=org.apache.qpid.jndi.PropertiesFileInitialContextFactory > In ActiveMQ broker: > > java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory > > 2. JNDI provider url name: this is used to set the JNDI provider url > in property file to make the initial context, > but it is different in Qpid and ActiveMQ brokers. so it was > introduced as a property in broker configuration. > In Qpid broker: connectionfactory.qpidConnectionfactory > In ActiveMQ : java.naming.provider.url > > 3. JNDI provider url value: this is used to set the JNDI provider for > initial context > In Qpid broker: > amqp://guest:gu...@clientid/test?brokerlist='tcp://localhost:5672' > In ActiveMQ broker: tcp://hostname:61616 > > 4. Connection factory lookup name: this is used to get connection > factory to create a connection. > In Qpid broker: qpidConnectionfactory > In ActiveMQ broker: connectionFactory, queueConnectionFactory, > topicConnectionFactory > > In addition to above parameters, to access JNDI stores we need > authentication details if it is secured, > > 5. Principal: user name > java.naming.security.principal = username > > 6. Credential: password > java.naming.security.credentials = password > > And usually queues and topics are set in JNDI property file. Here we > do not want to use default queues > or topics, as we publish to topics, it is created. > > Qpid broker configuration: > <brokerManagerConfiguration> > <brokerConfiguraton name="JMSServer" type="jms"> > <property > > name="factoryInitial">org.apache.qpid.jndi.PropertiesFileInitialContextFactory</property> > <property > name="providerUrlName">connectionfactory.qpidConnectionfactory</property> > <property > name="providerUrlValue">amqp://guest:gu...@clientid > /test?brokerlist='tcp://localhost:5672'</property> > <property > name="connectionFactoryLookupName">qpidConnectionfactory</property> > <property name="principal">username</property> > <property name="credentials">password</property> > </brokerConfiguraton> > </brokerManagerConfiguration> > > If there are any missing parameters that need to be included in broker > configurations, please let me know. > > In broker manager admin console, we can configure brokers giving above > parameter values, and to identify each topics > we publish to topic together with broker name, eg; jms-broker/topicname > > Thank you. > > > > -- > Manjula Rathnayaka > Software Engineer > WSO2, Inc. > Mobile:+94 77 743 1987 > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
