I have the same problem but with iPlanet servers, the solution that I implemented was save the session data in database and pass the primary key across the pages as parameters. If you found a best solution please tell me.
Joined: Feb 14, 2002
This sounds like a Good solution, But for every page it has to go the DB.That's not is Good. Surely, I will let you know when I get some other better solution than this. Thank You Regards Aruna G
Yes, this is certainly application server specific. However, this is something that is covered quite well in the redbooks and documentation on WebSphere. WebSphere has a feature called "Session persistence" that will automatically store session values in the database. It also has a built-in feature called "Session affinity" that will notice which server a session is created on (based on the session id, which contains a hashed JVM id) and direct it there. However, this second feature is only used when you use the load-balancing features built into the WebSphere HTTP Server plugin. Now, I have some questions for you -- how many users are you expecting to concurrently use this application? Why did you decide to use a Cisco local director instead of the built-in load balancing at the plugin? Are you open to rearranging your network topology a little? Kyle
Kyle, To answer your questions, we expect to get over 100,000 hits per day to start once the application goes full scale. Using the Cisco Local Director was a company Network decision that we need to go along with. We want to implement something that will hopefully not slow performance. Any further advice is much appreciated.