Hubert, Eric wrote:
Hi all,
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!
Have you tried the sample
http://wso2.org/project/esb/java/1.6/docs/ESB_Samples.html#Sample54
Chathura should be able to help you on this further..
Thanks for that pointer. I wasn't aware of this example. As my own
configuration didn't work out, I'll check this example and compare it
with my tests. After that I'll get back to you. Examples are always of
great value.
I promised to get back to you and in fact I do. ;-)
The example worked like a shame and I know understand how to solve my
problem using one of the above options for sticky session support,
namely the ClientID approach. As the name implies the client decides
when to create a new "session". Maybe the name ClientSessionID would
describe the usage more accurately.
Therefore one had just to include the XML-Element "ClientID" from the
Synapse-Namespace to the SOAP-Header, which then will get evaluated by
the WSO2 ESB to keep the session sticky. So this works great for the use
case I have in mind.
Just for the sake of completeness I would like to understand the other
two options (SOAP and Transport) as well. Could some please elaborate on
this!
Sorry, if I might have missed some documentation about this.
Hi Eric,
Transport session tracks sessions using HTTP session IDs. In this case,
the session ID is originated at the server side (as opposed to the
client side generated session IDs in ClientID sessions). Server
generates an HTTP session ID for the first request from the client. And
it includes that ID as a HTTP header in the response to the client. Then
client should send that session ID for all subsequent requests.
If the ESB load balancing operates in the transport/http mode, it maps
these session IDs to endpoints (servers). So the first request from a
client can be directed to any listed endpoint (under the load balancing
configuration). Upon receiving the first response from that endpoint,
the client is bound to that endpoint. So that all
subsequent requests from that client will be sent to the same endpoint.
SOAP mode load balancing also works with a server generated session ID.
Exception is that the session ID is sent as a SOAP header, instead of an
HTTP header.
Thanks,
Chathura
Regards,
Eric
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
