In the end, since we have full control over the messages' content for each machine, we decided to use a simple CBR using the order id as the "switch" variable and we're done.
Thanks for your help and for this great piece of software, Luiz 2011/9/22 Hiranya Jayathilaka <[email protected]>: > On Tue, Sep 20, 2011 at 5:35 PM, esmiralha <[email protected]> wrote: > >> >> Hi Hiranya, >> >> You are right. My intention is to use Synapse as a proxy to demultiplex the >> messages to the proper client machines. No transformations whatsoever. >> > > This can be implemented with Synapse. But I don't see a requirement to > maintain state information at Synapse. > > Thanks, > Hiranya > > >> >> Thanks, >> Luiz >> >> >> Hiranya Jayathilaka-3 wrote: >> > >> > Hi Luiz, >> > >> > How exactly do you intend to use Synapse when implementing this scenario? >> > Synapse is a mediation engine. It usually resides between the server and >> > the >> > client. It can certainly mediate all the requests and responses related >> to >> > your application. But what part of your use case do you intend to >> > implement >> > using Synapse? Do you intend to use it as some kind of a load balancer >> > (that's one scenario where you'll have to be concerned about maintaining >> a >> > session)? Or may be apply some transformation etc? >> > >> > Thanks, >> > Hiranya >> > >> > On Mon, Sep 19, 2011 at 10:50 PM, Luiz Esmiralha >> > <[email protected]>wrote: >> > >> >> This is my first question on the list and I'm a total newbie on >> >> Synapse. If the question doesn't make sense, please let me know! >> >> >> >> I'm wondering if the following use case can be implemented using >> Synapse: >> >> >> >> I have a performance test environment where multiple test clients can >> >> send/receive SOAP >> >> requests to/from a single server machine. >> >> >> >> The test scenario is like this: >> >> >> >> Client1 sends an "Open Order" SOAP request to Server. >> >> Server sends async reply to Client1. >> >> Server sends a SOAP request to Client1. >> >> Client1 sends async reply to the Server. >> >> Server sends an "Order Finished" SOAP request to Client1. >> >> >> >> The client requests are replied to asynchronously by the server. Each >> >> request spawns multiple exchanges between client and server that can >> >> be tied to the original request through an element of the message >> >> payload (the order id). >> >> >> >> Each async reply should be sent only to the client that originally >> >> sent the request. >> >> >> >> What I think I need is some sort of session context that is created >> >> when the order is sent and destroyed when the order is eventually >> >> closed. There I can store the endpoint URL of the client and route the >> >> messages accordingly. I thought about creating a Java class to serve >> >> as some sort of session context. >> >> >> >> Am I thinking right? Is this doable with Synapse without a large >> >> amount of Java code? >> >> >> >> Any help will be greatly appreciated! >> >> >> >> Thanks, >> >> Luiz >> >> >> > >> > >> > >> > -- >> > Hiranya Jayathilaka >> > Associate Technical Lead; >> > WSO2 Inc.; http://wso2.org >> > E-mail: [email protected]; Mobile: +94 77 633 3491 >> > Blog: http://techfeast-hiranya.blogspot.com >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Session-context-spanning-multiple-SOAP-requests-tp32497167p32501064.html >> Sent from the Synapse - User mailing list archive at Nabble.com. >> >> > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com >
