Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
4 replies Latest Post - ‏2012-05-22T08:14:23Z by gas
yoavgo
yoavgo
2 Posts
ACCEPTED ANSWER

Pinned topic ear application deployed on two logic Application servers

‏2012-05-17T13:04:47Z |
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 :
http://bprtest:9085/NewInboxWeb/index.jsp
http://bprtest:9086/NewInboxWeb/index.jsp

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 ?
Updated on 2012-05-22T08:14:23Z at 2012-05-22T08:14:23Z by gas
  • gas
    gas
    44 Posts
    ACCEPTED ANSWER

    Re: ear application deployed on two logic Application servers

    ‏2012-05-17T17:06:26Z  in response to yoavgo
    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:
    http://app1.bprtest.com:9085/NewInboxWeb/index.jsp
    http://app2.bprtest.com:9086/NewInboxWeb/index.jsp
    • yoavgo
      yoavgo
      2 Posts
      ACCEPTED ANSWER

      Re: ear application deployed on two logic Application servers

      ‏2012-05-20T13:24:57Z  in response to gas
      Hi,

      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
        Sunit
        194 Posts
        ACCEPTED ANSWER

        Re: ear application deployed on two logic Application servers

        ‏2012-05-21T15:20:33Z  in response to yoavgo
        You can either install WAS ND and convert this to a WAS cluster with session replication or as suggested earlier you go to one of the two servers and change the session cookie name from JSESSIONID to something else.

        • Sunit
  • gas
    gas
    44 Posts
    ACCEPTED ANSWER

    Re: ear application deployed on two logic Application servers

    ‏2012-05-22T08:14:23Z  in response to yoavgo
    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:
    http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.express.iseries.doc/info/iseriesexp/ae/twsv_configsimplelb.html