Hi all, Currently I'd like to test one scenario where I need the sticky endpoint feature of WSO2 (Loadbalancing Group with Session Management). On of our backend applications requires, that all subsequent communication between a client and this application has to be served via the exact same instance of this service. So the loadbalancer is free to choose any of the defined endpoints on the first invocation (in fact it should vary the chosen endpoints) but stick to this physical endpoint on subsequent invocations of that client.
As I have seen I can choose between three options for session management Transport, SOAP, and ClientID. Unfortunately I don't know how to configure and handle them. Also I'm not sure about the implied advantages and disadvantages of these options. I would be really happy if you could shed some light on this. Thanks a lot! Another thing I'm wondering is where to set the load balancing policy and other parameters to influence the load balancing strategy. I guess the default will be round robin. I'm referring to the following sentence of the Administration Guide: "Distributes the arriving messages (load) among the set of listed endpoints by evaluating the load balancing policy and other parameters" Regards, Eric -- Eric Hubert Software Architect Associate Director Research & Development _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
