You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Sathwik <ba...@intalio.com> on 2012/02/06 13:54:20 UTC
Re: Having a BPEL process consuming JMS messages
Hi Alain,
I suppose by specifying the endpoint in the process wsdl should do the trick.
jms:/<destination-name>?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&java.naming.security.principal=system&java.naming.security.credentials=manager
regards,
sathwik
On Wednesday 01 February 2012 01:30 AM, Alain Gilbert wrote:
> Hi,
>
> I have configured ODE (under tomcat) to publish/consume a JMS messages
> trough an ActiveMQ topic.
>
> I have a BPEL process that publish a message to a topic.
>
> Can I have another BPEL process to consume those messages? Pointers to do
> so would be greatly appreciated.
>
> I have read http://ws.apache.org/commons/transport/jms.html but I can't
> make my consumer BPEL process start when an event is published to a topic.
>
> Regards,
> Alain Gilbert
>
Re: Having a BPEL process consuming JMS messages
Posted by Alain Gilbert <ag...@gmail.com>.
Hi Sathwik,
I have setup both endpoints (producer & consumer) with this url:
Excerpt from the wsdl:
<binding name="EventSubscriberJMSBinding"
type="tns:EventSubscriberPortType">
<soap:binding style="document" transport="http://www.w3.org/2010/soapjms/"
/>
<operation name="consume">
<soap:operation soapAction="EventSubscriber" style="document" />
<input>
<soap:body use="literal" />
</input>
</operation>
</binding>
<service name="EventSubscriber">
<port name="EventSubscriberPort"
binding="tns:EventSubscriberJMSBinding">
<soap:address
location="jms:/dynamicTopics/Events.Published.Topic?transport.jms.ConnectionFactoryJNDIName=TopicConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&java.naming.security.principal=system&java.naming.security.credentials=manager"
/>
</port>
</service>
I have the same url in the endpoint files.
I have verified that the message is produced (added to the specified
topic). But the consuming process, shown above, does not start and the
message stays on the topic.
Anything else to look at?
Thanks for your help,
Alain
2012/2/6 Sathwik <ba...@intalio.com>
> Hi Alain,
>
> I suppose by specifying the endpoint in the process wsdl should do the
> trick.
>
> jms:/<destination-name>?**transport.jms.**ConnectionFactoryJNDIName=**
> TopicConnectionFactory&java.**naming.factory.initial=org.**
> apache.activemq.jndi.**ActiveMQInitialContextFactory&**
> java.naming.provider.url=tcp:/**/localhost:61616&java.naming.**
> security.principal=system&**java.naming.security.**credentials=manager
>
> regards,
> sathwik
>
>
> On Wednesday 01 February 2012 01:30 AM, Alain Gilbert wrote:
>
>> Hi,
>>
>> I have configured ODE (under tomcat) to publish/consume a JMS messages
>> trough an ActiveMQ topic.
>>
>> I have a BPEL process that publish a message to a topic.
>>
>> Can I have another BPEL process to consume those messages? Pointers to do
>> so would be greatly appreciated.
>>
>> I have read http://ws.apache.org/commons/**transport/jms.html<http://ws.apache.org/commons/transport/jms.html>but I can't
>> make my consumer BPEL process start when an event is published to a topic.
>>
>> Regards,
>> Alain Gilbert
>>
>>
>