Hi,
In our project we are maintaining some data in httpsession as per some requirements. Now we are facing session issues while moving the project to Qual environment.
We have multiple dispatchers and each one pointing to different publisher (one to one) in Qual environment and routing is happening in round robin fashion at load balancer level. When request is served by one of the server which is setting some data in session and in the subsequent request we are loosing the session data if the next request is being served by other sever.
I have tried configurations mentioned in below forum but it did not solve the issue.
https://docs.adobe.com/docs/en/aem/6-1/administer/security/encapsulated-token.html
Can anyone let me know how to over come this issue.
Thanks in advance.
Views
Replies
Total Likes
Look at this thread - HTTPSessions not recommended with AEM.
Views
Replies
Total Likes
Hi,
Encapsulated tokes allow a user to be authenticated on each publish instance with their token, hence they do not need to log into every new publish instance and you do not require sticky connections.
If you are using data in HTTPsessions, as Scott mentioned it is not recommended, then you require sticky connections. Could you not store the information in a cookie on the client browser?
Regards,
Opkar
Views
Replies
Total Likes
See this doc topic:
https://docs.adobe.com/docs/en/aem/6-2/develop/platform/cookie-optout.html
Also - we just had a session by experts that talked about large scale architectures among AEM instances that may be very beneficial to you:
http://scottsdigitalcommunity.blogspot.ca/2016/09/comparative-architecture-analysis-of.html
Views
Replies
Total Likes