We had similar issue with similar environment This worked for us: try: Websphere: In the Websphere Admin Console, choose WebSphere Application Servers > serverName > Session management > Enable Cookies. Make sure that the path is set to the context root of the mid tier. To ensure that users can log in successfully, create a new NoAdditionalSessionInfo property: Choose WebSphere Application Servers > serverName > Web Container > Custom Properties. Create a new NoAdditionalSessionInfo property, and set it to true. Restart the IBM WebSphere server.
https://kb.bmc.com/infocenter/index?page=content&id=KA377228&actp=search&viewlocale=en_US&searchid=1368038699602 Thank you, Pascale Sterrett Kenavo ar wech all [email protected] Sent by: [email protected] 05/20/2013 10:58 AM Please respond to [email protected] To [email protected] cc Subject Midtier 7.6 sp 4 on websphere 8 is not working, any suggestions? Good Morning List, We are using Back end - ARS 7.5 P4 on Unix 6.1.7 with 11g Currently - We have a functioning 7.5 P4 MT 32 bit environment connected to the back end. This new MT 7.6 SP 4 is our attempt to upgrade the MT environment, then do the back end. New MT env, UNIX 6.1.7 Websphere 8 64 bit Deployed 7.6 SP 4 Able to login in to config http://new_httpserver:port1/arsys/shared/config.jsp http://new_httpserver:port2/arsys/shared/config.jsp - and add the backend server, and the report and log filesystem. I'm currently not going thru the loadbalancers. (installed tomcat on win7 pc , and deployed 7.6sp4 mt against 7.5p4 backend, works fine) New MT: new_httpserver >-F/W- http port1, port2--> new_websphere_app_MT7.6SP4_server_1---> F/W- http port1, port2, 80, 8080, TCP_1 ->Backend_ARS_7.5P4_server new_httpserver >-F/W- http port1, port2-->new_websphere_app_MT7.6SP4_server_2 ---> F/W- http port1, port2, 80, 8080, TCP_1 -> Backend_ARS_7.5P4_server New MT: old_httpserver:port3>-no firewall --> old_websphere_app_MT7.5p4_server_1 >-F/W- http port3, port4, 80, 8080, TCP_1 ->Backend_ARS_7.5P4_server old_httpserver:port4>-no firewall -->old_websphere_app_MT7.4P4_server_2 >-F/W- http port3, port4, 80, 8080, TCP_1 ->Backend_ARS_7.5P4_server issue: http://new_httpserver:port1/arsys/shared/login.jsp http://new_httpserver:port2/arsys/shared/login.jsp after entering id and password it returns the below page and not getting authenticated and same login page appears with below url - http://httpserver:port1/arsys/shared/login.jsp?/arsys/forms/server/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db http://httpserver:port2/arsys/shared/login.jsp?/arsys/forms/server/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db However, the user is logged in, per the license usage or being prompt to logout user when try to log into old http servers. http://old_httpserver:port3/arsys/shared/login.jsp http://_oldhttpserver:port4/arsys/shared/login.jsp This is the closest to the our issue I have looked at for references, please let me know if i'm on the the right track.. http://ars-action-request-system.1093659.n2.nabble.com/Midtier-Loadbalancer-is-not-working-Any-suggestion-URGENT-td7586174.html MT Logs May 20, 2013 1:46:18 PM - INFO (com.remedy.log.CONFIG) : (Thread 22) com.remedy.arsys.config.ConfigProperties save Saved properties file /usr/WebSphere/AppServer/profiles/Custom01/installedApps/TEST/Internal_Arsys.ear/midtier_aix.war/WEB-INF/classes/config.properties May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 22) com.remedy.arsys.session.DefaultAuthenticator redirectToLogin DefaultAuthenticator.redirectToLogin: url=/arsys/forms/arsserver/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 22) com.remedy.arsys.session.DefaultAuthenticator getAuthenticatedCredentials DefaultAuthenticator: Credentials requested May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 22) com.remedy.arsys.session.Login establishSession Login: establishing Session May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SERVLET) : (Thread 22) com.remedy.arsys.stubs.GoatServlet setupSessionData GoatServlet: No session or new session May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SERVLET) : (Thread 22) com.remedy.arsys.stubs.GoatServlet postInternal cookie=MJUID=-1969732504; G=53bc19dc72f2b37f:36e3b1a2:13eb3ea9f96:-7ffd; JSESSIONID=gQ-xOUSE5MkhH5v_UBBxraT; s_vi=[CS]v1|28B7F2B2851D1BDE-6000012F000116C9[CE]; __unam=772d877-13cdf94f23c-35c71d87-7; fpl.smartHomePageInfo=EBL1%7CABP2%7CPOL1%7CBBL2; rsi_segs=H11232_10025|H11232_0; s_nr=1366810903654; s_vnum=1369402843142%26vn%3D4; JSESSIONID=0000gQ-xOUSE5MkhH5v_UBBxraT:17q2c61va; P=1; st=3600; lt=60 May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SERVLET) : (Thread 22) com.remedy.arsys.stubs.GoatServlet postInternal GoatServlet: url=http://httpserver:port1/arsys/forms/arsserver/Remedy+Home+Page+2/Default+Admin+View/?cacheid=d74a89db May 20, 2013 1:45:05 PM - INFO (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet doThePost User exg0test on IPAddress 10.122.2.51 May 20, 2013 1:45:05 PM - INFO (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet doThePost Context path is/arsys May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet doLogin LoginServlet: Authentication status: 16 May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet authenticate LoginServlet: Authenticating exg0test against server arsserver May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.DefaultAuthenticator getAuthenticatedCredentials DefaultAuthenticator: Using credentials from login page - exg0test May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet doThePost LoginServlet: locale=en_US May 20, 2013 1:45:05 PM - FINE (com.remedy.log.SESSION) : (Thread 21) com.remedy.arsys.session.LoginServlet doThePost LoginServlet: url=http://httpserver:port1/arsys/servlet/LoginServlet?null _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" If you are not the intended addressee, please inform us immediately that you have received this e-mail in error, and delete it. We thank you for your cooperation. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
