Hi Isuru, Thanks for the clarification. Suppose your suggestion is to use MS/MP in a more granular manner. So if the calls to all these BE's should be reliable, does that mean at each point we need to have a MS/MP integration separately?
Thanks On Sun, May 3, 2015 at 1:23 PM, Isuru Udana <isu...@wso2.com> wrote: > Hi Hasitha, > > On Sun, May 3, 2015 at 11:42 PM, Hasitha Hiranya <hasit...@wso2.com> > wrote: > >> Hi Isuru, >> >> Above mediation flow has several BE calls. Not one. And message >> transformations in the middle of them. >> That is why I was trying to direct it to the same sequence. >> >> Is this approach is wrong? >> > Yes it is not correct. > > Basically if you need to guaranteed delivery we need to send the message > using the Forwarding message processor directly to the backend. Forwarding > message processor internally uses a blocking client to invoke the backend. > If you want to do some transformation, you can do that before putting to > the to the store. However if you have some kind of service chaining > scenario you have to re-design flows using reply sequences etc. > > Thanks. > >> >> Thanks >> >> On Sun, May 3, 2015 at 1:09 PM, Isuru Udana <isu...@wso2.com> wrote: >> >>> >>> >>> On Sun, May 3, 2015 at 11:33 PM, Hasitha Hiranya <hasit...@wso2.com> >>> wrote: >>> >>>> OK. I am trying a reliable delivery scenario. >>>> >>>> 1. Get message. >>>> 2. Go thro mediation flow. >>>> 3. If something went wrong put the original message to a queue (message >>>> store) >>>> 4. re-try the failed message (using message processor) and and let it >>>> go thro above mediation flow (it is not sending to a BE, but several steps) >>>> >>> If it is not sent to a BE, why we need reliable delivery, retry, etc. >>> here ? I mean if there is no BE, there is nothing to do with reliable >>> delivery. I think this is not a store and forward scenario. >>> >>>> >>>> @4 I need to go thro the flow again. >>>> >>>> Thanks >>>> >>>> On Sun, May 3, 2015 at 12:55 PM, Isuru Udana <isu...@wso2.com> wrote: >>>> >>>>> What's your requirement to direct to a sequence ? >>>>> >>>>> >>>>> On Sun, May 3, 2015 at 11:23 PM, Hasitha Hiranya <hasit...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Maheeka/Isuru, >>>>>> >>>>>> Yes. I need to get the JMS message from the queue/topic and direct it >>>>>> to a sequence rather than sending it to the BE directly. >>>>>> >>>>>> If so, what are the alternative options here? >>>>>> A JMS proxy? But I need reliable delivery. re-try configurations, >>>>>> re-try interval etc. >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Sun, May 3, 2015 at 12:49 PM, Isuru Udana <isu...@wso2.com> wrote: >>>>>> >>>>>>> Hi Maheeka, >>>>>>> >>>>>>> On Sun, May 3, 2015 at 11:16 PM, Maheeka Jayasuriya < >>>>>>> mahe...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Hasitha, >>>>>>>> >>>>>>>> Use the message.processor.reply.sequence property to define the >>>>>>>> forwarding sequence. >>>>>>>> >>>>>>> Reply sequence is to get the response received from the backend >>>>>>> service. I thought Hasitha's requirement is to direct the message in the >>>>>>> message store, to a sequence from the message processor. >>>>>>> >>>>>>>> >>>>>>>> In management console click on "Show Additional Parameters" and >>>>>>>> provide sequence name to "Reply sequence name" parameter. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Maheeka >>>>>>>> >>>>>>>> [1] >>>>>>>> https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor >>>>>>>> >>>>>>>> Maheeka Jayasuriya >>>>>>>> Software Engineer >>>>>>>> Mobile : +94777750661 >>>>>>>> >>>>>>>> On Sun, May 3, 2015 at 8:24 PM, Hasitha Hiranya <hasit...@wso2.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I am trying to forward a message to a sequence after receiving it >>>>>>>>> from the queue/topic using message processor. >>>>>>>>> >>>>>>>>> How can we configure this? >>>>>>>>> >>>>>>>>> I tried giving a sequence as an endpoint hoping it would work, but >>>>>>>>> did not (message processor deactivates not recognizing it) >>>>>>>>> >>>>>>>>> [image: Inline image 1] >>>>>>>>> >>>>>>>>> Is there a way to achieve this in ESB? >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Hasitha Abeykoon* >>>>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>>>>> *cell:* *+94 719363063* >>>>>>>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Isuru Udana* >>>>>>> Associate Technical Lead >>>>>>> WSO2 Inc.; http://wso2.com >>>>>>> email: isu...@wso2.com cell: +94 77 3791887 >>>>>>> blog: http://mytecheye.blogspot.com/ >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Hasitha Abeykoon* >>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>>> *cell:* *+94 719363063* >>>>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Isuru Udana* >>>>> Associate Technical Lead >>>>> WSO2 Inc.; http://wso2.com >>>>> email: isu...@wso2.com cell: +94 77 3791887 >>>>> blog: http://mytecheye.blogspot.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> *Hasitha Abeykoon* >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>> *cell:* *+94 719363063* >>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>> >>>> >>> >>> >>> -- >>> *Isuru Udana* >>> Associate Technical Lead >>> WSO2 Inc.; http://wso2.com >>> email: isu...@wso2.com cell: +94 77 3791887 >>> blog: http://mytecheye.blogspot.com/ >>> >> >> >> >> -- >> *Hasitha Abeykoon* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- *Hasitha Abeykoon* Senior Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
