Hi, We Have a Peoplesoft App (lets Say App1) running on WebLogic Server and a Hyperion App (Lets Say App2) running on a different WebLogic Server. Both the systems have their own Sessions and are Managed internally and independently. The Issuse is , we are trying to create a Single Sign On Application between these two systems. We could come up with some customized code for passing the login credentials from App1 to App2's login Jsp but are not sure how to synchronize the sessions between these two systems. (If App1 Logs off we should log off App2 but NOT vice versa.) The restriction is we cannot change any of the mostly delivered jsp pages in both the applications, so we should come up with some global session synch mechanism. Is there anybody who can give pointers towards the solution.... Any help greatly appreciated....
Hi Sat, One way to accomplish this would be to use an http session management module such as Coherence*Web included in the latest build of Coherence. This allows the use of all the different caching strategies supported by Coherence (i.e. Replicated, Distributed/Partitioned, Near/Distributed, Overflow to Disk, Write-Behind to a datastore, etc.) to manage/store you session data concurrently in a cluster. Later, Rob Misek
<a href="http://www.tangosol.com" target="_blank" rel="nofollow">www.tangosol.com</a><br /><a href="http://www.tangosol.com/coherence.jsp" target="_blank" rel="nofollow">Coherence:</a> Easily share live data across a cluster!
Hi, I have the similar query. If we are doing the load balancing in the weblogic 7.1 application how to handle the session management? Regards, M.S.Raman.
Joined: Dec 23, 2003
I think webLogic Provides Persistent Session Managment System using (JDBC) for Storing Sessions to table. They also specify in the WebLogic documentation about the Load Balancing / Clustering Session Management.
Joined: Sep 24, 2002
> I think webLogic Provides Persistent Session Managment System using (JDBC) > for Storing Sessions to table. Absolutely, but with this mechanism you must make a round-trip to the datastore on session modification. This, typically, is more expensive then relying on in-memory management of session state. > They also specify in the WebLogic documentation about the Load Balancing / > Clustering Session Management. I could be wrong but I do not believe that there is a default mechanism for handling the management of http session across multiple applications. Later, Rob Misek
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Session Mgmt Across Multiple WebLogic Systems