I have an ear application deployed on two logic Application servers of Websphere (on two different nodes).
When the user open a browser for each application (server - different port) on the same pc , he is logout from the previous application.
I'll explain again :
we have two urls :
if the user open two browsers and do login , he is getting session timeout in the first application (browser).
How can I prevent this session timeout , and let the user work on both apps ?
Pinned topic ear application deployed on two logic Application servers
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-05-22T08:14:23Z at 2012-05-22T08:14:23Z by gas
gas 110000E92M46 Posts
Re: ear application deployed on two logic Application servers2012-05-17T17:06:26ZThis is the accepted answer. This is the accepted answer.Hi,
You have a few options:
1) Change the session id cookie name for the second appliction
Go to applications > application_name > Session management > Enable cookies
Change default cookie name from JSESSIONID to something different.
2) Change root context of the second application during installation for example to NewInboxWeb2.
3) Access applications via different virtual hosts (or access one via ip and other via hostname) eg:
yoavgo 270005BTP52 Posts
Re: ear application deployed on two logic Application servers2012-05-20T13:24:57ZThis is the accepted answer. This is the accepted answer.
- gas 110000E92M
please notice :
1."Change the session id cookie name for the second appliction"
: I have only one ear (application)
2." Change root context of the second application during installation ":
I install one ear on two servers
Sunit 100000DWFV222 Posts
Re: ear application deployed on two logic Application servers2012-05-21T15:20:33ZThis is the accepted answer. This is the accepted answer.
- yoavgo 270005BTP5
gas 110000E92M46 Posts
Re: ear application deployed on two logic Application servers2012-05-22T08:14:23ZThis is the accepted answer. This is the accepted answer.What do you want to accomplish, as it is not clear enough?
Do you want to have 2 separate apps on both servers (separate session) or you want this to act as a single app (with shared user session and single sign on)?
If you want separate sessions, then try changing sessionID cookie on the SERVER level, or access applications via different virtual hosts.
If you want shared sessions, the best way is to use WAS Network Deployment and create cluster with persistent sessions.
However you can try to enable persistent sessions and see if it is working (I never tried that on single server). This might work according to following page: